Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAAL6JQijkxr48FdX3H9U+aOociuy+s5MM8EiJjNh7-c9k+qA_w@mail.gmail.com>
References: 
 <CAJNb-9pRGw11-Ajo2Tu5COrdLsVEZUEDy9q5qPAMby_zx4WLsQ@mail.gmail.com>
	<CAPaJBx79zV1JSNL5BnPF_TxYEaW-2ZpLf+WAi6wa4QA94mFSmA@mail.gmail.com>
	<CAJNb-9qWecvR3hiv9i_U0aOqqOn6yvXvEf6fmpw4DHH91LJDfQ@mail.gmail.com>
	<CAPaJBx7nE_oLQ0q1S8zUZek=RS8m2YgUfr=2QfCmEjBtEjA8ng@mail.gmail.com>
	<CAJNb-9qhPHBFiB1ocXByGCHi3=2F19PcPQHir-p5TRR15Yz1-Q@mail.gmail.com>
	<CAPaJBx6aeBgGrngZichzArr30jwBG+JDE0uqEgnHVNmngnPi1Q@mail.gmail.com>
	<CAJNb-9psGxtYHCwV9uvgD-ZjHpw2sQRyDYd5O5NawZ6+_fJO8A@mail.gmail.com>
	<CAPaJBx41gVHvcfbGkWYUFU5oFLpPVSwxvZgUpXLO=WbNAyWQ=A@mail.gmail.com>
	<CAJNb-9pL6LAuqb-gfVFiNg9XfExRSYBSsOp+9AderZ_wNME4TQ@mail.gmail.com>
	<3E30B4E7-CE71-4007-A59C-C68A422C5E54@apache.org>
	<CAPaJBx6M6=kHcARhci6d35_sMvpCTJKuD4+bKDFSYH6Myf-0FQ@mail.gmail.com>
	<CAAL6JQi2CLVEsBBxdcMU86dB8VOr4tz-xqjhfPwRnxOauUeZjQ@mail.gmail.com>
	<CAPaJBx7wXhTOGA5GvxGzefQKi+rsJQyoyE4kQvMkMH9BG9bdCg@mail.gmail.com>
	<CAAL6JQijkxr48FdX3H9U+aOociuy+s5MM8EiJjNh7-c9k+qA_w@mail.gmail.com>
Date: Fri, 10 May 2013 21:16:03 +0100
Message-ID: 
 <CAPaJBx6oNOyEvUdyHiYDBC3rqryTPN78458Emnm68L6SEkL+qw@mail.gmail.com>
Subject: Re: [DISCUSS] dont't abuse of "lazy concensus" on mail tagged
 [DISCUSS]
From: Noah Slater <nslater@apache.org>
To: "dev@couchdb.apache.org" <dev@couchdb.apache.org>
Content-Type: multipart/alternative; boundary=20cf307cfeb21939e204dc62d6b4

--20cf307cfeb21939e204dc62d6b4
Content-Type: text/plain; charset=ISO-8859-1

On 10 May 2013 20:39, Randall Leeds <randall.leeds@gmail.com> wrote:

> So I'd prefer to see [DISCUSS] and [URGENT] used and just be mindful
> that discussion suggests ample allotment of time for discussion. I
> don't believe we need a specific tag for lazy consensus because I
> agree with you that it's the default operating mode.


Randall,

My only issue here is that I think "URGENT" misses the mark also.

There are several community / project-level things that one might want to
do where all you really ought to do is notify dev@ that you're about to do
it. Some examples I can think of:

* Big changes to the website
* Big changes to the wiki
* Changes in stuff like release procedure
* Archiving releases
* Planning marketing activity
* Getting approval for small events
* Getting branding approval

There are plenty more.

So, I guess what I'm trying to say is that I'm more than happy only using
"DISCUSS" to mean "here's an open ended discussion", but I want a tag that
means "here's something I'm about to do".

I agree that we don't need a specific tag for lazy consensus, simply
because lazy consensus is the default. But if "DISCUSS" is causing some
people to think "oh well, I'll read that next week when I have time" then
it would be handy to be able to explicitly tag a thread with "this is
something that is about to happen, so speak up now". And I don't think
"URGENT" is the right tag. Because archiving a release isn't urgent. But I
 _will_ be moving ahead if I don't hear any objections about it. Do you see
what I mean?

On 10 May 2013 20:45, Benoit Chesneau <bchesneau@gmail.com> wrote:

> I'm not sure what yo mean by-laws here. But I will draft a set of
> rules I have in  mind. Not until next week anyway since I am working
> on some other topics right now.
>
> - benoit
>

Starting points:

http://hadoop.apache.org/bylaws.html
http://hc.apache.org/bylaws.html
http://struts.apache.org/release/1.2.x/bylaws.html

-- 
NS

--20cf307cfeb21939e204dc62d6b4--