I officially vote +1 on this document. A reminder, from my initial email on this round of updates:
> At this point, the bylaws are mostly stable, but there may remain some > tweaks to the text necessary to ensure they match how we have been > running the project for some time now. We (the PMC) acknowledge that > they are not perfect, but we do not want to let the perfect to be the > enemy of the good (thanks to Voltaire), so we're moving ahead with them > in the state they're in. This stands - minor changes should be queued up for later, we can put together a diff and adopt that as a simple majority vote once these rules are in effect. For reference, the edits referred to were pasted in came directly from ASF documents - I made no personal changes and I think we make our own changes at our own peril, especially of bikeshedding this to death. https://www.apache.org/dev/pmc.html -Joan ----- Original Message ----- From: "Noah Slater" <nsla...@apache.org> To: dev@couchdb.apache.org Sent: Monday, July 21, 2014 9:24:35 PM Subject: Re: [VOTE] [REVISED] Official CouchDB bylaws Two minor quibles. <rnewson> I mean that we say Lazy C is our main thing, but we later say that RTC is. I think it's just a consequence of the doc's evolution, and perhaps nothing more than reorg is needed ^ I agree with this, and the wording should be fixed to clarify that Lazy C is default for non-technical decisions, and RTC is default for tech decisions (i.e. code changes). I would change your added text from: > Remember that, as in any meeting, the chair is a facilitator and their role > within the PMC is to ensure that everyone has a chance to be heard and to > enable meetings to flow smoothly. There is no concept of "leader" in the > Apache way. To: > Remember that, as in any meeting, the Chair is a facilitator and their role > within the PMC is to ensure that everyone has a chance to be heard and to > enable things to flow smoothly. It is primarily an administrative role. We mention the "no leader" thing in the opening para. :) Neither of these things are blocking. I will vote +1 on the bylaws as they stand now, and move these suggestions to a buffer, for the next round of edits we inevitably make (at some point in the future). On 22 July 2014 03:12, Joan Touzet <jo...@lrtw.org> wrote: > **REVISED BYLAWS DOCUMENT VERSION** > > Voting period starts 02:00:00 UTC on Tuesday, July 21, 2014 > Votes must be received by 23:59:59 UTC on Sunday, July 27, 2014 > > > INTRODUCTION > ============ > This Call For Votes is for voting in an official set of Apache CouchDB > bylaws. This vote is being conducted as required by the proposed bylaws > themselves. For voting questions or problems, contact the PMC at > priv...@couchdb.apache.org. > > The intent is to make this an official document of Apache CouchDB. > > To cast a binding vote, you need to be a CouchDB PMC member. > > As this is the first vote of its kind, and this document is foundational > to our decision-making process in the future, _the PMC is asking all > active committers to cast voluntary, non-binding votes as well_. > > > HOW TO VOTE > =========== > First, read the full text of the proposal. > > The text of the bylaw document being voted on can be found at: > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=40511017 > > The vote is on version *89* of this document as displayed in the document > page history at: > > https://cwiki.apache.org/confluence/pages/viewpreviousversions.action?pageId=40511017 > > The page has been locked for edits until the vote is concluded. > > To cast a vote, it is necessary to reply to this email, at > > dev@couchdb.apache.org > > with your vote as outlined under Section 3.3 of the Bylaws. As a > reminder, for the purpose of tallying, all values will be counted as +1, > -1 or nothing. -- Noah Slater https://twitter.com/nslater
