RE: [proposal:PMC] Member and Chair elections

> From: Nicola Ken Barozzi [mailto:[email protected]]
> 
> > 
> > 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 
> [email protected], 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 :(