incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From robert burrell donkin <robertburrelldon...@gmail.com>
Subject Re: [doc] podling software releases
Date Wed, 15 Feb 2006 13:59:17 GMT
On 2/9/06, Roy T. Fielding <fielding@gbiv.com> wrote:
>
> On Feb 9, 2006, at 10:27 AM, Jean T. Anderson wrote:
>
> >> dev list or ppmc list?  Only PMC members' votes are binding for
> >> full TLPs; I suggest having the vote on the dev list as mentioned
> >> but only the PPMC members' votes being binding.
> >
> > it should be public vote, so on the public -dev list.  Here's a
> > suggested refinement:
> >
> > "Therefore, should a Podling decide it wishes to perform a release,
> > the
> > Podling SHALL hold a vote on the Podling's public -dev list and notify
> > the Podling's PPMC list that the vote has been called. At least
> > three +1
> > votes are required (see guidelines at
> > http://www.apache.org/foundation/voting.html), and only the PPMC
> > member
> > votes are binding. If the majority of all votes is positive, then
> > send a
> > summary of that vote to general@incubator and formally request the
> > Incubator PMC approve such a release. Three +1 Incubator PMC votes are
> > required."
>
> There is no need to "notify the PPMC".
>
> PMC == Project Management Committee == the people who make decisions
> for a project == the people with binding votes in public decisions
> == the people on the dev list we listen to when they vote.


that's true but there are reasons why copying the email to the PMC is good
practice:

1 the PMC may contain people (such as officers and members) who are not on
the dev lists.
2 the PMC list should provide a permenant record of the official actions of
the committee.
3 PMC members can provide oversight in the event of a VOTE being disputed.

- robert

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message