From 3c34d83082f445ea7f5bd80720f87bf2fa749721 Mon Sep 17 00:00:00 2001 From: Travis Ralston Date: Wed, 22 Apr 2020 13:37:50 -0600 Subject: [PATCH 1/2] Add some words about what categories are --- specification/proposals_intro.rst | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/specification/proposals_intro.rst b/specification/proposals_intro.rst index 82a4225b1..47cb58fca 100644 --- a/specification/proposals_intro.rst +++ b/specification/proposals_intro.rst @@ -341,6 +341,35 @@ Closed proposal-closed A proposal which Obsolete obsolete A proposal which has been made obsolete by another proposal or decision elsewhere. =============================== ============================= ==================================== +Categories +---------- + +We use category labels on MSCs to place them into a track of work. The spec core team +decides which of the tracks they are focusing on for the next while and generally makes +an effort to pull MSCs out of that category when possible. + +The current categories are: + +============ ================= ====================================== +Name Github Label Description +============ ================= ====================================== +Core kind:core Important for the protocol's success. +Feature kind:feature Nice to have additions to the spec. +Maintenance kind:maintenance Fixes or clarifies existing spec. +============ ================= ====================================== + +Some examples of core MSCs would be aggregations, cross-signing, and groups/communities. +These are the sorts of things that if not implemented could cause the protocol to +fail or become second-class. Features would be areas like enhanced media APIs, +new transports, and bookmarks in comparison. Finally, maintenance MSCs would include +improving error codes, clarifying what is required of an API, and adding properties +to an API which makes it easier to use. + +The spec core team assigns a category to each MSC based on the descriptions above. +This can mean that new MSCs get categorized into an area the team isn't focused on, +though that can always change as priorities evolve. We still encourage that MSCs be +opened, even if not the focus for the time being, as they can still make progress and +even be merged without the spec core team focusing on them specifically. Proposal Tracking ----------------- From 16905a2f5bf3cea32ee0567b8bfd4883d64bccc6 Mon Sep 17 00:00:00 2001 From: Travis Ralston Date: Wed, 22 Apr 2020 14:31:34 -0600 Subject: [PATCH 2/2] Make the spec core team the Spec Core Team --- specification/proposals_intro.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/specification/proposals_intro.rst b/specification/proposals_intro.rst index 47cb58fca..771d2d6aa 100644 --- a/specification/proposals_intro.rst +++ b/specification/proposals_intro.rst @@ -344,7 +344,7 @@ Obsolete obsolete A proposal which Categories ---------- -We use category labels on MSCs to place them into a track of work. The spec core team +We use category labels on MSCs to place them into a track of work. The Spec Core Team decides which of the tracks they are focusing on for the next while and generally makes an effort to pull MSCs out of that category when possible. @@ -365,11 +365,11 @@ new transports, and bookmarks in comparison. Finally, maintenance MSCs would inc improving error codes, clarifying what is required of an API, and adding properties to an API which makes it easier to use. -The spec core team assigns a category to each MSC based on the descriptions above. +The Spec Core Team assigns a category to each MSC based on the descriptions above. This can mean that new MSCs get categorized into an area the team isn't focused on, though that can always change as priorities evolve. We still encourage that MSCs be opened, even if not the focus for the time being, as they can still make progress and -even be merged without the spec core team focusing on them specifically. +even be merged without the Spec Core Team focusing on them specifically. Proposal Tracking -----------------