ArchStudio Community Consensus Process
Any changes must be proposed on the archstudio-dev mailing list.
Community consensus is required for:
- Merging code with the stable trunk
- Preparing a release
- Modifying an end-user-facing documentation resource.
- Changing any ArchStudio policy
We have decided to basically follow the Apache model of lazy consensus, where a proposal is put to the community on the mailing list with a deadline for approval. This initial deadline will be no less than 72 hours. Within this period, each ArchStudio committer may cast one of three votes:
- +1: Approval of the change.
- 0: Indifference toward the change.
- -1: Veto of the change.
Other votes, such as "-0.9" or "+0.9" are not allowed at this time. If a community member requests more time for voting, the community should accommodate these requests to a reasonable extent. Changes are only approved when there are no veto (-1) votes. As with the Apache process, all votes (particularly vetoes) should be accompanied by a technical explanation of the reasoning behind the vote. Due to the notion of 'lazy consensus,' silence is interpreted as a '0' (indifferent) vote - tacit approval. Non-committers are free to participate in the discussion, but their votes are non-binding.
Unlike the default Apache process:
- In the ArchStudio community, a -1 is always a veto vote, even on procedural issues, unless the vote is a non-binding opinion poll.
- Lazy consensus is the default model - no minimum amount of +1 votes is required for a change to be accepted.
In all cases, the community should attempt to resolve all issues without employing explicit dispute resolution procedures. However, should a particular issue come to an impasse, any participant can request explicit dispute resolution, which will proceed according to ArchStudio dispute resolution policy.
Communication among Community Members
The primary vehicle for communication among community members will be the archstudio-dev mailing list. Longer-lived topics should be added to this wiki. Community members are not responsible for monitoring the entire wiki for your changes, so if you want other community members to know about something you have changed on the wiki, you must post it to the archstudio-dev list. A link and summary of changes is sufficient, as well as any necessary action items (requesting consensus, for example).
