On Oct 3, 2006, at 1:55 PM, robert burrell donkin wrote:
That's why we created the PPMC == the entire set of committers of the
podling and the Mentors.

this is not policy ATM

Yes it is -- it was formally voted on during the Geronimo incubation.

They do have binding votes on everything
*except* releases because we delegated that to them, right?

i don't understand how this can work with the current structure. AFAIK
PPMCs have no organisational standing (they are no official
committees) and are not recognized by the board. AIUI they cannot take
decisions binding on apache. their main role ATM seems to be as a
training exercise.

How can they avoid making decisions that are binding on Apache?
Importing code into subversion is a decision that is binding on Apache.
It just isn't a very important decision.  The PPMCs are making binding
decisions every day -- the only condition we placed on them was that
at least three +1 votes had to come from the PMC (whether or not those
people happened to be Mentors) for releases and adding new committers.
That does not mean the other votes are ignored.

The only reason PMCs have organizational standing is because they
are a group of named individuals on a committee that has been
assigned a task by the board in accordance with the bylaws.  A PPMC
becomes an official committee as soon as the Incubator creates it,
since its creation is well within the scope given by the board to
the incubator project and the individuals are named in the status file.
The only question is what authority is granted to the PPMC by the
Incubator, and every podling since Geronimo has acted according to
the policy that all decisions are made by the PPMC with a minimal
quorum of three PMC +1 votes.

bootstrapping is simply a description of the only process available
ATM. the mentors (as incubator pmc members) are the only ones on the
project who have the binding votes required to take decisions (such as
appointed PPMC members).

That just isn't true.  Somebody took a thread out of context and
applied it where it doesn't make any sense.  The restriction that
only a PMC can release software has very little to do with all
of the other decisions a project might make.

....Roy


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to