Add CONTRIBUTING.md documenting working practices under SIP-000 - #273
Open
314159265359879 wants to merge 2 commits into
Open
Add CONTRIBUTING.md documenting working practices under SIP-000#273314159265359879 wants to merge 2 commits into
314159265359879 wants to merge 2 commits into
Conversation
(this is not a SIP) This document outlines the contributing guidelines for the SIPs repository, including submission processes, review etiquette, and workflow on GitHub.
This was referenced Jul 10, 2026
Closed
Add notice to replaced SIPs with new link reference.
Contributor
Author
|
@brice-stacks and @rafaelcr do you think it is okay to approve and merge this. There are no new ideas in this but it tries to capture the unwritten rules and the outcomes of past conversations about how we work in this repo. |
brice-stacks
reviewed
Sep 9, 2026
| ## SIP numbers and status labels | ||
|
|
||
| - SIP numbers are assigned once and never reused, even if the SIP never | ||
| advances past Draft. This prevents one number from referring to two |
Contributor
There was a problem hiding this comment.
Above it says that the number is not assigned until it is accepted. That conflicts with this sentence, which says that the number is never reused, "even if the SIP never advances past Draft."
brice-stacks
reviewed
Sep 9, 2026
brice-stacks
left a comment
brice-stacks
left a comment
Contributor
There was a problem hiding this comment.
This looks good. Thanks for putting it together! I just noticed some inconsistencies with the draft/number explanation.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This adds a CONTRIBUTING.md that writes down how we work in this repo: how to submit a SIP, review etiquette, how the SIP-000 statuses map to GitHub steps, what can change after a CAB vote, when a SIP PR merges, and how a ratified SIP gets updated.
Nothing in here changes the SIP process. It documents practice under SIP-000 and says so explicitly, where the two would disagree SIP-000 wins. That is also why this is a repo doc and not a SIP: these are working rules we should be able to improve with a simple PR.
Context: this came out of #241 and #228. The useful operational ideas from #241 live here now, and the answer to #228 is the last section, the replacement model is already in SIP-000. The workflow mapping builds on what whoabuddy wrote up in #145. The numbering rules and the Withdrawn Draft label come from the discussion in #260.
Feedback welcome, especially from editors and CAB members on whether this matches how we actually work.