-
Notifications
You must be signed in to change notification settings - Fork 48
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
consensus decision making #113
consensus decision making #113
Conversation
All content from the design document. Minor fixes to formatting and organization, and minor wording corrections, but no changes to the actual process.
The current set of examples only shows "reversible" and "irreverisble" based solely on rustbot inferring it (based on whether it is looking at a stabilization proposal). I think there should be a concrete example of a team member using the command syntax that changes the state of the reversibility of a decision. |
I found the use of the terms "mutable" and "immutable" confusing.
Assuming I am right about their role: Why have these synonyms? I think it would be clearer to pick one pair of terms and use them consistently. |
Co-authored-by: Felix S Klock II <[email protected]>
Co-authored-by: Felix S Klock II <[email protected]>
Generalize to "does not speak for the entire team" rather than tabooing the word "we". But also, rephrase to use "I think" phrasing instead of "we have".
…ncerns Try to make it clearer that we can and do still make irreversible decisions. Focus on how we handle dissent in such cases, and what we can do in those circumstances.
@pnkfelix Mostly, I think those terms felt both playful and memorable, given Rust's own use of mutability. I would still like to keep those synonyms in bot commands, but I'll switch to consistently using |
Keep "mutable"/"immutable" (and unambiguous prefixes) as synonyms, but favor the more self-documenting terms in documentation.
(I don't mind playfulness; see e.g. the plethora of puns and/or cultural references I try to stuff into documents I write. But in the end, I also think "reversible/irreversible" are more precise, in terms of what we expect the state transitions to be, so 1. I wouldn't want to choose mutable/immutable over reversible/irreversible, and 2. I do think consistency is more important than playfulness.) In any case, keeping the synonyms is fine, but please do document their existence as synonyms, so that people who use this as a reference document won't be as mystified as I am when they encounter their usage in the wild. |
I did add them to the documentation as synonyms. |
hup, yes you did! Sorry for responding before reading the current content. This all looks great. r+ from me. |
Add the decision-making process from the 2021-07-21 design meeting
All content from the design document. Minor fixes to formatting and
organization, minor wording corrections, and some clarifications and FAQ
entries. No changes to the actual process.