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

Document the actual current implementation requirements of the MSC process #2058

Open
HarHarLinks opened this issue Jan 15, 2025 · 3 comments
Labels
spec-bug Something which is in the spec, but is wrong

Comments

@HarHarLinks
Copy link
Contributor

Link to problem area:
https://spec.matrix.org/proposals/

Issue
As far as I know, the actual process is to require an implementation before FCP.
According to documentation, the implementation is required only after FCP, before merging the spec PR.

Expected behaviour
Alignment of documentation and practice. Imo, favor the actual process.

@HarHarLinks HarHarLinks added the spec-bug Something which is in the spec, but is wrong label Jan 15, 2025
@HarHarLinks HarHarLinks changed the title Document the actual current implementation requirements Document the actual current implementation requirements of the MSC process Jan 15, 2025
@turt2live
Copy link
Member

We changed the process to require implementation prior to FCP, but forgot to update large swathes of the documented process.

The change was made because we were finding that a lot of MSCs required changes after implementation actually happened, so wanted to frontload that for a more streamlined FCP review.

@richvdh
Copy link
Member

richvdh commented Jan 16, 2025

https://spec.matrix.org/proposals/ is quite a big page. If there are particular bits which are wrong, it would be helpful to point them out

@turt2live
Copy link
Member

About half the page talks about implementation post-FCP still.

https://spec.matrix.org/proposals/#process is wrong
https://spec.matrix.org/proposals/#lifetime-states for finished-final-comment-period is wrong
etc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
spec-bug Something which is in the spec, but is wrong
Projects
None yet
Development

No branches or pull requests

3 participants