A couple of thoughts: 1. It seems all rules on voting are predicated on the question being binary. Perhaps we should also tack on a section for cases where we have to pick among multiple options (a simple plurality, maybe). 2. Should this itself be a CEP? (E.g., Python's governance model was proposed in PEPs 8010 through 8016 ([1][2] etc.) and codified in PEP 13 [3], PHP's voting system was iterated upon recently in their equivalent, an RFC [4]) Or perhaps not, since the current CEP description suggests that CEPs are exclusively for code changes? (If that's the case, we could discuss that at a later date, and move on with this proposal first.)
[1]: https://www.python.org/dev/peps/pep-8015/ [2]: https://www.python.org/dev/peps/pep-8016/ [3]: https://www.python.org/dev/peps/pep-0013/ [4]: https://wiki.php.net/rfc/abolish-narrow-margins Yours, Murukesh Mohanan On Fri, 5 Jun 2020 at 01:54, Joshua McKenzie <jmcken...@apache.org> wrote: > Hello project! > > The pmc has been discussing how we make decisions as a pmc, how we make > decisions as a project of committers and contributors, what decisions are > made where, and how those decisions are ratified and by whom. We came to > the conclusion that there's value in having a more formal (though > lightweight) structure around these topics as well as start to enumerate > some expectations on how we interact with each other on the project as it > matures. > > A link to the current draft of the governance doc is here: > > https://docs.google.com/document/d/1wOrJBkgudY2BxEVtubq9IbiFFC3d3efJSj9OIrGcqQ8/edit# > > The doc is only 2 pages long; if you're interested in engaging in a > discussion about how we evolve and collaborate as a project, please take > some time to read through the doc, think through things, and engage on this > thread here. > > Thanks everyone, and looking forward to a great discussion! > > ~Josh McKenzie >
