wholetrans/docs-matrix-spec
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Add some clarifications around implementation requirements for MSCs (#1718)

Browse source 
* clarification around implementation requirement, and mention new label

* add changelog

* fix typo

* Fix typos

Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>

---------

Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
This commit is contained in:
Hubert Chathi 2024-03-13 11:28:30 -04:00 • committed by GitHub
parent 6634f73bff
commit 0b43b5a343
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 13 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

1
changelogs/internal/newsfragments/1718.clarification Normal file
View file

@ -0,0 +1 @@
Add some clarifications around implementation requirements for MSCs

15
content/proposals.md
View file

@ -380,9 +380,18 @@ As part of the proposal process the Spec Core Team will require evidence
of the MSC working in order for it to move into FCP. This can usually be of the MSC working in order for it to move into FCP. This can usually be
a branch/pull request to whichever implementation of choice that proves a branch/pull request to whichever implementation of choice that proves
the MSC works in practice, though in some cases the MSC itself will be the MSC works in practice, though in some cases the MSC itself will be
small enough to be considered proven. Where it's unclear if an MSC will small enough to be considered proven. Implementations do not need to be
require an implementation proof, ask in merged or released, but must be of sufficient quality to show that the
[\#matrix-spec:matrix.org](https://matrix.to/#/#matrix-spec:matrix.org). MSC works. Where it's unclear if an MSC will require an implementation
proof, ask in [\#matrix-spec:matrix.org](https://matrix.to/#/#matrix-spec:matrix.org).
Proposals may require both server-side and client-side implementations.
Proposals that have not yet been implemented will have the
`needs-implementation` label. After an implementation has been made, add a
comment in the GitHub issue indicating so. After an implementation has been
made, we will check it to verify that it implements the MSC. Proposals that
have implementations that have not yet been checked will have the
`implementation-needs-checking` label.
### Early release of an MSC/idea ### Early release of an MSC/idea