You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by Berin Loritsch <bl...@citi-us.com> on 2002/12/16 16:29:28 UTC
[proposal:PMC] Member and Chair elections
I am bringing this back up, because it seems that we are in agreement
on the PMC voting procedures. Now we need to look at the PMC
membership rules (governing future PMC membership processes).
This is only a starting point--and it is designed to get us moving
forward with PMC/Chair policies. I have changed my original
proposal on Chair term from 3 months to 6 months at the request of
several developers.
PMC Membership
--------------
* PMC members are nominated by the community, and voted in by
the existing PMC.
* The PMC nominees must be an active committer in Avalon, or a
project that depends on Avalon.
* PMC nominees that come from dependant projects must be voted
to the position by their community. The community must have
at a minimum six (6) active committers. The dependant project
must have a code dependency on Avalon (i.e. at a minimum
requiring Framework).
* The PMC votes the nominee in.
Chair Membership
----------------
* Any of the PMC members are eligible for the chair position.
* The community decides which of the PMC members are nominated
to the position.
* The PMC makes the final vote on the Chair based on the
nominated individuals.
* The chair position will be up for revote every 6 months.
NOTE: I don't want to impose any limitation on the number
of consecutive terms a chair can serve. If someone is
doing a good job and acting responsibly in the position,
then why mess with a good thing? I.e. if Nicola proves
himself to be nonpartial and really a benefit to the
community in this position I would vote for him again.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: [proposal:PMC] Member and Chair elections
Posted by Berin Loritsch <bl...@citi-us.com>.
> From: Nicola Ken Barozzi [mailto:nicolaken@apache.org]
>
> >
> > PMC Membership
> > --------------
> >
> > * PMC members are nominated by the community, and voted in by
> > the existing PMC.
>
> community = mailing list || committers || PMC members?
>
> I assume you're implying (community = mailing list) +1
Yes.
> > * The PMC nominees must be an active committer in Avalon, or a
> > project that depends on Avalon.
>
> +1 this is a rule that the PMC should apply, since it can be a bit
> subjective.
We can make some general guidelines as to what an active committer
is...
> > * PMC nominees that come from dependant projects must be voted
> > to the position by their community. The community must have
> > at a minimum six (6) active committers. The dependant project
> > must have a code dependency on Avalon (i.e. at a minimum
> > requiring Framework).
>
> Why 6? (just curious about the number)
>
> +1
Basically something with more than a couple developers. I.e. a
project with a community. I was wanting to weed out an overly
large PMC because of projects like "I started a SourceForge
account and I have some code scratchings in place. I am the only
committer, but I did it just so I can be on the Avalon PMC".
IOW, I want the projects who have representatives in our PMC
to have built some sort of following like Cocoon and JAMES.
We can lower the number, but I think that four (4) should be
the absolute minimum.
> > * The PMC makes the final vote on the Chair based on the
> > nominated individuals.
>
> +0
>
> +1 for the committers making the final vote.
>
> I would add that the PMC Chair should then be "ratified" by the
> board@apache.org, which can decide also to not accept the nomination.
>
> This is because the Chair is the reference to the board, so
> it appointed
> by the board. I would assume that 99,999% of the time the board would
> ratify it.
True.
> Please leave me out from the example.
sorry :(
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [proposal:PMC] Member and Chair elections
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Berin Loritsch wrote:
> I am bringing this back up, because it seems that we are in agreement
> on the PMC voting procedures. Now we need to look at the PMC
> membership rules (governing future PMC membership processes).
>
> This is only a starting point--and it is designed to get us moving
> forward with PMC/Chair policies. I have changed my original
> proposal on Chair term from 3 months to 6 months at the request of
> several developers.
>
>
> PMC Membership
> --------------
>
> * PMC members are nominated by the community, and voted in by
> the existing PMC.
community = mailing list || committers || PMC members?
I assume you're implying (community = mailing list) +1
> * The PMC nominees must be an active committer in Avalon, or a
> project that depends on Avalon.
+1 this is a rule that the PMC should apply, since it can be a bit
subjective.
> * PMC nominees that come from dependant projects must be voted
> to the position by their community. The community must have
> at a minimum six (6) active committers. The dependant project
> must have a code dependency on Avalon (i.e. at a minimum
> requiring Framework).
Why 6? (just curious about the number)
+1
> * The PMC votes the nominee in.
+1
> Chair Membership
> ----------------
>
> * Any of the PMC members are eligible for the chair position.
+1
> * The community decides which of the PMC members are nominated
> to the position.
+1
> * The PMC makes the final vote on the Chair based on the
> nominated individuals.
+0
+1 for the committers making the final vote.
I would add that the PMC Chair should then be "ratified" by the
board@apache.org, which can decide also to not accept the nomination.
This is because the Chair is the reference to the board, so it appointed
by the board. I would assume that 99,999% of the time the board would
ratify it.
> * The chair position will be up for revote every 6 months.
> NOTE: I don't want to impose any limitation on the number
> of consecutive terms a chair can serve. If someone is
> doing a good job and acting responsibly in the position,
> then why mess with a good thing?
+1
> I.e. if Nicola proves
> himself to be nonpartial and really a benefit to the
> community in this position I would vote for him again.
Please leave me out from the example.
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>