Re: [DISCUSS] : things we need to solve/decide : changes feed

Dredging this thread back up with an eye towards moving to an RFC … I was reading through the FoundationDB Record Layer preprint[1] a few weeks ago and noticed an enhancement to their version of _changes that I know would be beneficial to IBM and that I think is worth considering for inclusion

Re: [VOTE] Bylaws change: Establish a Qualified Lazy Majority vote type for the RFC process (revised)

-1 for the following reason: "https://apache.org/foundation/how-it-works.html#hats INDIVIDUALS COMPOSE THE ASF All of the ASF including the board, the other officers, the committers, and the members, are participating as individuals. That is one strength of the ASF, affiliations do not cloud

[VOTE] Bylaws change: Establish a Qualified Lazy Majority vote type for the RFC process (revised)

(Revised: The Reply-To field on the last email was incorrect. I am also including the diff of the proposed changes to this email per request.) PMC Members, This is a VOTE to create or amend our official documents. It establishes a new Qualified Lazy Majority voting type, and

Re: [VOTE] Bylaws change: Establish a Request For Comments (RFC) process for major new contribution (revised)

+1 -- Robert Samuel Newson rnew...@apache.org On Tue, 5 Mar 2019, at 20:18, Joan Touzet wrote: > (Revised: The Reply-To field on the last email was incorrect. I am > also including the diff of the proposed changes to this email per > request.) > > > > PMC Members, > > This

[VOTE] Bylaws change: Establish a Request For Comments (RFC) process for major new contribution (revised)

(Revised: The Reply-To field on the last email was incorrect. I am also including the diff of the proposed changes to this email per request.) PMC Members, This is a VOTE to create or amend our official documents. It establishes a new Request For Comments (RFC) process through

[VOTE] Bylaws change: Establish a Request For Comments (RFC) process for major new contributions

PMC Members, This is a VOTE to create or amend our official documents. It establishes a new Request For Comments (RFC) process through which all major changes to Apache CouchDB must pass. This includes modifying the Bylaws to explain the process, as well as adding the new RFC template. There

[VOTE] Bylaws change: Establish a Qualified Lazy Majority vote type for the RFC process

PMC Members, This is a VOTE to create or amend our official documents. It establishes a new Qualified Lazy Majority voting type, and amends the bylaws to use this new type for RFC votes only. This vote depends on the RFC vote passing. The git branch with the proposed further changes to the

Re: [DISCUSS] Proposed Bylaws changes

Since there isn't clear consensus on part of this, I'm going to start 2 VOTE threads for changing the bylaws, one for the RFC process which has broad-spectrum support, and one for the +1 rule change. -Joan - Original Message - > From: "Reddy B." > To: priv...@couchdb.apache.org,