On Apr 10, 2007, at 6:20 PM, Jorg Heymans wrote:
(is there anything the PMC can do to make it easier to vote a release through - perhaps get a few cocoon developers on the PMC ?)

Adding people to a PMC involves

  (1) calling for a vote on [EMAIL PROTECTED]
  (2) people voting
  (3) tallying the vote
  (4) inviting the new people
  (5) chair sending an email to board@
      (6) board ACKs
          (7) chair updates a file in SVN

"get a few cocoon developers on the PMC" is slightly off, since we add people to the PMC based on merit. Of course, there are probably quite a few developers out there who have earned sufficient merit to be on the excalibur PMC, and some of them probably also are cocoon developers. The way I see it, the open invitation extended to them a year or two ago is still pretty much open, we just need to do the voting :-).

Before setting up excalibur, we did discuss with a bunch of people whether some stuff should just move out into cocoon. Back then, we decided against it.

Another related thing to do is removing people from the PMC that no longer want to be on it. This involves

(1) that PMC member sending an email to [EMAIL PROTECTED] requesting to be removed from the PMC
  (5) chair sending an email to board@
      (6) board ACKs
          (7) chair updates a file in SVN

there is an alternative here when (1) does not happen which is a lot less fun (the rest of the PMC has to vote to remove the inactive member).

(on a tangent: excalibur is one example of several mature, stable, and pretty inactive projects at apache. As a foundation, apache has not yet really figured out a 'standard way' on how to deal with projects with dwindling activity, so in the meantime it's up to each project to figure out what to do.)

cheers,

- Leo


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

Reply via email to