You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by Jacob Kjome <ho...@visi.com> on 2006/11/20 08:39:20 UTC

[VOTE][RESULT] Please welcome Elias Ross as a new Log4j committer

5 votes for Elias Ross to be elevated to committer status on the 
Log4j project, all +1's from...

Jacob Kjome
Yoav Shapira
Scott Deboy
Paul Smith
Curt Arnold


Congratulations Elias!  You are the newest committer of the Log4j 
team.  Welcome!

Yoav, Curt, or someone else in the know about infrastructure 
stuff;  can you get Elias set up properly?


Jake


---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Re: [VOTE][RESULT] Please welcome Elias Ross as a new Log4j committer

Posted by Yoav Shapira <yo...@apache.org>.
Hi,

On 11/20/06, Jacob Kjome <ho...@visi.com> wrote:
> Congratulations Elias!  You are the newest committer of the Log4j
> team.  Welcome!
>
> Yoav, Curt, or someone else in the know about infrastructure
> stuff;  can you get Elias set up properly?

Welcome aboard Elias! ;)

The rough order of infrastructure things is like this:
-- Elias needs to accept the invitation and let us know of his
preferred apache.org user ID and a backup user ID in case the primary
one is taken already (not done yet)
-- Elias to sign and fax CLA (done)
-- Jim (Jagielski, the ASF secretary) to receive and acknowledge CLA
(done, as one can verify at
http://people.apache.org/~jim/committers.html)
-- The Logging PMC chair (Curt) to send an email to root@apache.org,
CCing the Logging PMC, asking for an account to be created for Elias
(this takes a couple of days typically)
-- Once Elias received an email from root@apache.org with his initial
password, he should login and follow the directions at
http://www.apache.org/dev/new-committers-guide.html#committer-what-is
to set up his account
-- Once Elias' account is active, the Logging PMC chair (Curt) needs
to give Elias logging commit karma by editing the infrastructure
svn-authorization file (I technically have access to this file due to
other non-Logging work I do at Apache, but it's really the PMC chair
who should do the editing for his/her PMC permissions)

Yoav

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


[VOTE][RESULT] PMC vote on Elias Ross as a new Log4j committer

Posted by Curt Arnold <ca...@apache.org>.
Vote called on 21 Nov 2006:

Three binding +1 votes:

Curt Arnold
Yoav Shapira
Scott Deboy

No other votes.


Project bylaws (was Re: [VOTE] PMC vote on Elias Ross as a new Log4j committer)

Posted by Curt Arnold <ca...@apache.org>.
On Nov 21, 2006, at 4:02 PM, Yoav Shapira wrote:

> Hi,
>
> On 11/21/06, Curt Arnold <ca...@apache.org> wrote:
>> Per the project bylaws (http://logging.apache.org/site/bylaws.html),
>> it appears that both a subproject (described in the actions section)
>> and PMC vote (second paragraph after Committers) are required to
>> grant new commit rights.  This message is to inform the PMC of the
>> results of the subproject vote and to initiate a PMC vote to confirm
>> the log4j vote.
>
> This is kind of surprising.  I thought the bylaws say lazy consensus
> of the PMC, not a formal vote, so all that was required is a message
> from one of the log4j committers to the logging PMC saying "hey, we've
> voted this guy in, so unless you have any objections, please send an
> email to root@apache.org asking for his account..."
>
> But if a vote is required, here's my +1 again.

The description of "Lazy Consensus" in the bylaws says that it  
requires "3 binding +1 votes", so I don't see how you could have a  
Lazy Consensus of PMC members without having a call for a vote by  
that definition.  The definition of "Lazy Consensus" is different at  
http://www.apache.org/foundation/glossary.html#LazyConsensus.   
However, as all the log4j votes were from PMC members and the only  
abstaining PMC members (Mark and Ceki) have been quiet for a while,  
it should be a only a formality.

> On a separate note, we should remove these bylaws altogether.  We just
> had a discussion about this on general@incubator.a.o (see
> http://marc.theaimsgroup.com/?l=incubator- 
> general&m=116405409724466&w=2
> for the key message).   Apparently project-level bylaws, like
> Jakarta's from which we copied ours, are invalid in the formal sense
> that we seem to be applying them here.
>
> Yoav

I could support that.  I've proposed modifying the bylaws a few years  
ago to streamline the double votes required for releases among other  
things.  Eliminating the project bylaws altogether would likely  
accomplish all the benefits that a streamlining would and would  
eliminate the possibilities for conflicts between LS definitions and  
ASF definitions.  I think it would essentially make everything  
requiring a vote (like a release) a single PMC vote.  Let's make it  
open for discussion for a little while and if it still seems like a  
good idea, let's put it to a PMC vote.




Re: [VOTE] PMC vote on Elias Ross as a new Log4j committer

Posted by Yoav Shapira <yo...@apache.org>.
Hi,

On 11/21/06, Curt Arnold <ca...@apache.org> wrote:
> Per the project bylaws (http://logging.apache.org/site/bylaws.html),
> it appears that both a subproject (described in the actions section)
> and PMC vote (second paragraph after Committers) are required to
> grant new commit rights.  This message is to inform the PMC of the
> results of the subproject vote and to initiate a PMC vote to confirm
> the log4j vote.

This is kind of surprising.  I thought the bylaws say lazy consensus
of the PMC, not a formal vote, so all that was required is a message
from one of the log4j committers to the logging PMC saying "hey, we've
voted this guy in, so unless you have any objections, please send an
email to root@apache.org asking for his account..."

But if a vote is required, here's my +1 again.

On a separate note, we should remove these bylaws altogether.  We just
had a discussion about this on general@incubator.a.o (see
http://marc.theaimsgroup.com/?l=incubator-general&m=116405409724466&w=2
for the key message).   Apparently project-level bylaws, like
Jakarta's from which we copied ours, are invalid in the formal sense
that we seem to be applying them here.

Yoav

[VOTE] PMC vote on Elias Ross as a new Log4j committer

Posted by Curt Arnold <ca...@apache.org>.
Per the project bylaws (http://logging.apache.org/site/bylaws.html),  
it appears that both a subproject (described in the actions section)  
and PMC vote (second paragraph after Committers) are required to  
grant new commit rights.  This message is to inform the PMC of the  
results of the subproject vote and to initiate a PMC vote to confirm  
the log4j vote.

Here is my +1, the second time around.


The summary of the log4j vote from log4j-dev:

> From: Jacob Kjome <ho...@visi.com>
> Date: November 20, 2006 1:39:20 AM CST
> To: Log4J Developers List <lo...@logging.apache.org>
> Subject: [VOTE][RESULT] Please welcome Elias Ross as a new Log4j   
> committer
> Reply-To: Log4J Developers List <lo...@logging.apache.org>
>
>
> 5 votes for Elias Ross to be elevated to committer status on the  
> Log4j project, all +1's from...
>
> Jacob Kjome
> Yoav Shapira
> Scott Deboy
> Paul Smith
> Curt Arnold
>
>
> Congratulations Elias!  You are the newest committer of the Log4j  
> team.  Welcome!
>
> Yoav, Curt, or someone else in the know about infrastructure  
> stuff;  can you get Elias set up properly?
>
>
> Jake