Consensus building of our community #50
Description
I would like to initiate a discussion about the ways that we build consensus in our community. Here is a short checklist:
- Public list of contributors who have decision power and documented governance process.
- Decisions made by consensus among leaders and documented on the project's main communications venue. Community opinions taken into account but leaders have final decision.
- Documented voting rules used to build consensus when discussion is not sufficient.
- Vetoes or similar overrides only valid for code commits, and justified by technical explanation.
- Important discussions happen asynchronously in written form on the project's main communications channel. Offline, face-to-face or private discussions that affect the project are also documented on that channel.
What do you think?