Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Comunicate next steps of an MSC better #1669

Open
uhoreg opened this issue Nov 6, 2023 · 4 comments
Open

Comunicate next steps of an MSC better #1669

uhoreg opened this issue Nov 6, 2023 · 4 comments
Labels
A-Process Related to the spec process itself (MSC process)

Comments

@uhoreg
Copy link
Member

uhoreg commented Nov 6, 2023

Contributors do not always know what they need to do to advance an MSC, and the MSC process document can be daunting. Perhaps we need a way to indicate, on the MSC, what the next steps are. Or some other way to guide contributors.

@MTRNord
Copy link
Contributor

MTRNord commented Nov 6, 2023

Related: matrix-org/matrix-spec-proposals#4061

@turt2live
Copy link
Member

For reference, we've got a private workflow board called the "SCT global workflow" which tracks every single MSC and the intended state over a given timeline. It needs a ton of work before it's remotely usable by anyone, but may help with tracking what needs to be done for the MSC to progress.

For example, it tracks where we want an MSC to end up once associated to a timeline:

image

@uhoreg
Copy link
Member Author

uhoreg commented Nov 6, 2023

One thing I was thinking of was just having a bot saying something like "Thanks for your MSC. When you think that your proposal is ready for review, please let us know in #sct-office:matrix.org"

@MTRNord
Copy link
Contributor

MTRNord commented Nov 6, 2023

One thing I was thinking of was just having a bot saying something like "Thanks for your MSC. When you think that your proposal is ready for review, please let us know in #sct-office:matrix.org"

I think this alone could be very helpful. even if just automated by a CI that does this on opening the PR. :)

Also maybe there should be some more info in the PR Template? I tend to see projects utilizing comments in those templates to link to important contribution resources.

@turt2live turt2live added spec-bug Something which is in the spec, but is wrong meta Something that is not a spec change/request and is not related to the build tools A-Process Related to the spec process itself (MSC process) labels Nov 7, 2023
@richvdh richvdh removed spec-bug Something which is in the spec, but is wrong meta Something that is not a spec change/request and is not related to the build tools labels Apr 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Process Related to the spec process itself (MSC process)
Projects
None yet
Development

No branches or pull requests

4 participants