Thanks, Jason! This is a great start. I made a bunch of comments, and just a few edits. I think it would be good to have a few more of the "core developers" (our de facto PMC I guess) read through this before advertising it more widely---Ali, Andreas *, Nilay, Joel, Brad, Nate, etc. I see some value in getting to the point where we have a formal structure that allows us to vote on issues where we can't reach a consensus.
Steve On Fri, Jun 19, 2015 at 2:59 PM Jason Power <[email protected]> wrote: > Hi all, > > At the gem5 users workshop, I brought up the importance of creating a > governance document (and other processes) for gem5. I have created an > initial proposal for the governance document. The link to a google doc is > below. Assuming no on on this list has any objections, I will also send > this out to the gem5-users list tomorrow (or when I get around to it). > > gem5 governance document > < > https://docs.google.com/document/d/12X3YHGJShUS34sorQJIvcr5NUssZcmMIJovD9I3w0Ns/edit?usp=sharing > > > > I propose we spend one week in "free-for-all" mode and allow the community > to update and add to what I've started. Feel free to remove/totally change > what I have written so far. I'll keep up with what's going on, and if there > is a particularly contentious passage, I'll make sure that it's presented > to the whole community. > > Timeline of things that need to be done by the community: > 1) Make radical changes to governance document. (~1 week) > 2) I will remove the option to edit, and we will only accept comments. This > will allow us to finalize the document. (~1 week, though this is probably a > little aggressive). > 3) From this document, we will need to write some others (e.g., how to > commit and roadmap according to my draft). And of course these will also > need to go through some process as well. (~2 weeks?) > > Specific parts of the document that need significant updates or may be > contentious: Creating a "Project management committee", Committer > responsibilities (commit-then-review vs. review-then-commit), and the > Philosophy. *Please feel free to totally do away with what I currently > have.* It's mostly just a placeholder. > > Finally, here are some good links to read about what a governance document > is: > http://oss-watch.ac.uk/resources/governancemodels > http://oss-watch.ac.uk/resources/meritocraticgovernancemodel > http://www.apache.org/foundation/how-it-works.html#meritocracy > http://www.apache.org/foundation/governance/ > http://oss-watch.ac.uk/resources/sustainableopensource > > TL;DR > Actionable items: > 1) Reply if you do NOT want me to send this to the user's list. > 2) Reply if you disagree with the process I've outlined above. > 3) Edit the document > < > https://docs.google.com/document/d/12X3YHGJShUS34sorQJIvcr5NUssZcmMIJovD9I3w0Ns/edit?usp=sharing > > > as you see fit. > > Cheers, > Jason > > Link again: > > https://docs.google.com/document/d/12X3YHGJShUS34sorQJIvcr5NUssZcmMIJovD9I3w0Ns/edit?usp=sharing > _______________________________________________ > gem5-dev mailing list > [email protected] > http://m5sim.org/mailman/listinfo/gem5-dev > _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
