-
Notifications
You must be signed in to change notification settings - Fork 380
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
Add an "MSC Checklist" document and link to it from various places #4061
Conversation
MSC_CHECKLIST.md
Outdated
- [ ] Does each error case have a specified `errcode` (e.g. `M_FORBIDDEN`) and HTTP status code? | ||
- [ ] If a new `errcode` is introduced, is it clear that it is new? | ||
- [ ] Will the MSC require a new room version, and if so, has that been made clear? | ||
- [ ] Is the reason for a new room version clearly stated? For example, modifying the set of redacted fields changes how event IDs are calculated, thus requiring a new room version. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think @turt2live and I had talked about something with "Be really sure everyone knows exactly how new redaction rules are handled."
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's ship it :)
I'm certain we've missed something, but we can always add to it later.
This PR adds an "MSC Checklist" to the repo. This is essentially just a list of checks to perform on an MSC before considering it accepted (or checking a box on a
@mscbot fcp merge
comment).The document is linked from various places so MSC authors are aware of it, hopefully leading to self-checks being performed.