3 Matching Annotations
- Feb 2021
Here's the last issue where source maps were discussed before the beta release.
- Nov 2020
In Rust, we use the "No New Rationale" rule, which says that the decision to merge (or not merge) an RFC is based only on rationale that was presented and debated in public. This avoids accidents where the community feels blindsided by a decision.
I'd like to go with an RFC-based governance model (similar to Rust, Ember or Swift) that looks something like this: new features go through a public RFC that describes the motivation for the change, a detailed implementation description, a description on how to document or teach the change (for kpm, that would roughly be focused around how it affected the usual workflows), any drawbacks or alternatives, and any open questions that should be addressed before merging. the change is discussed until all of the relevant arguments have been debated and the arguments are starting to become repetitive (they "reach a steady state") the RFC goes into "final comment period", allowing people who weren't paying close attention to every proposal to have a chance to weigh in with new arguments. assuming no new arguments are presented, the RFC is merged by consensus of the core team and the feature is implemented. All changes, regardless of their source, go through this process, giving active community members who aren't on the core team an opportunity to participate directly in the future direction of the project. (both because of proposals they submit and ones from the core team that they contribute to)
- have discussion/feedback/debate in public (transparency)
- feeling blindsided
- open-source projects: allowing community (who are not on core team) to influence/affect/steer the direction of the project
- change proposal workflow: RFCs
- build concensus
- attracting contributors
- welcoming feedback
- soliciting feedback
- allowing sufficient time for discussion/feedback/debate before a final decision is made