Filip/matrix-spec
1
0
Fork 0
mirror of https://github.com/matrix-org/matrix-spec synced 2026-02-22 05:53:42 +01:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Clarity + adjust to use dedicated labels

Browse source
This commit is contained in:
Travis Ralston 2025-07-03 13:23:16 -06:00
parent 3014a2bea9
commit 8a68e4e67e
1 changed files with 7 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
content/proposals.md
View file

@ -508,7 +508,9 @@ a placeholder MSC is required, it may be opened as such.
There are a few expectations attached to placeholder MSCs:
* They are tagged as WIP drafts ahead of receiving real content.
* They have a title which marks them WIP, and are in the "draft" state.
* They have the following labels: `[proposal-placeholder, action-required, needs-implementation]`.
* Notably, *not* `proposal`.
* They are relatively short-lived (ideally less than 6-12 months in placeholder).
* They propose solutions which are reasonably likely to be accepted. If a placeholder
needs to be closed because the idea won't work, isn't needed, etc, then the MSC's
@ -516,8 +518,10 @@ There are a few expectations attached to placeholder MSCs:
* When they are updated to receive real content, the following happens:
1. The Spec Core Team or the author leaves a comment to cause a notification
that the MSC has been replaced with real content.
2. The `proposal` label (or its equivalent) is removed and re-applied to trigger
chat notifications in the public Matrix rooms.
2. The `proposal` label (or its equivalent) is added to trigger chat notifications
in the public Matrix rooms. The `proposal-placeholder` and `action-required`
labels should be removed at this stage as well. Other labels are removed/applied
per normal process.
* The Spec Core Team is aware of the intended MSC's title and purpose. This is
especially important if the Security Team approved the use of a placeholder MSC.