72 hours rule.

--047d7b673bda9d905e04ed943ebc
Content-Type: text/plain; charset=ISO-8859-1

Hi.

I am not sure if this is the right place for such a question/suggestion,
but better here than nowhere :-)

I have lately been meet with confusion in 2 situations, both at ASF
community level (at least if you look from a distance).

Lazy consensus defines "silence is consensus", but projects (like e.g.
labs) tends to redefine this rule:

"Every ASF committer can ask for one or more labs. The creation of the lab
requires a PMC lazy consensus vote (at least three +1 and no -1, 72 hours)"

In my mind this sentence is hard to understand, does it mean:
a) PMC who dont send an explicit +1/-1 cast a +1 == "silence is concensus"
or
b) 3 +1 pmc votes is needed, so the rules of  "lazy consensus" does not
apply

The people who wrote the lines I quote are all much more experienced in
"the apache way" than I am, but I believe its important that newcomers
(like myself) can read and understand what is written, without having to
read "between the lines".

I suggest, that we make an effort to at least at ASF community level, not
to confuse, but to be precise. I believe it would be correct to append [1]
with:

"Lazy consensus cannot be used, if the project requires a minimum number of
+1 for the proposal to be accepted"

@labs, please dont feel targeted, I am not picking on your project (which I
happen to believe is VERY important, and much too unknown"), but allowing
myself to use your good website as documentation for my point.

rgds
jan I.


[1] http://community.apache.org/committers/lazyConsensus.html<http://community.apache.org/committers/lazyConsensus.html>

--047d7b673bda9d905e04ed943ebc
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div><div><div><div>Hi.<br><br></div>I am not su=
re if this is the right place for such a question/suggestion, but better he=
re than nowhere :-)<br><br></div><div>I have lately been meet with confusio=
n in 2 situations, both at ASF community level (at least if you look from a=
 distance).<br>
<br></div>Lazy consensus defines &quot;silence is consensus&quot;, but proj=
ects (like e.g. labs) tends to redefine this rule:<br></div></div></div><br=
>&quot;Every ASF committer can ask for one or more labs. The creation of
              the lab requires a PMC lazy consensus vote
              (at least three +1 and no -1, 72 hours)&quot;<br><br></div><d=
iv>In my mind this sentence is hard to understand, does it mean:<br></div><=
div>a) PMC who dont send an explicit +1/-1 cast a +1 =3D=3D &quot;silence i=
s concensus&quot;<br>
</div><div>or<br>b) 3 +1 pmc votes is needed, so the rules of=A0 &quot;lazy=
 consensus&quot; does not apply<br><br></div><div>The people who wrote the =
lines I quote are all much more experienced in &quot;the apache way&quot; t=
han I am, but I believe its important that newcomers (like myself) can read=
 and understand what is written, without having to read &quot;between the l=
ines&quot;.<br>
<br></div><div>I suggest, that we make an effort to at least at ASF communi=
ty level, not to confuse, but to be precise. I believe it would be correct =
to append [1]<br></div><div>with:<br><br></div><div>&quot;Lazy consensus ca=
nnot be used, if the project requires a minimum number of +1 for the propos=
al to be accepted&quot;<br>
</div><div><br></div><div>@labs, please dont feel targeted, I am not pickin=
g on your project (which I happen to believe is VERY important, and much to=
o unknown&quot;), but allowing myself to use your good website as documenta=
tion for my point.<br>
</div><div><br></div><div>rgds<br>jan I.<br></div><div><br><br><a href=3D"h=
ttp://community.apache.org/committers/lazyConsensus.html">[1] http://commun=
ity.apache.org/committers/lazyConsensus.html</a><br><br></div></div>

--047d7b673bda9d905e04ed943ebc--