incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marvin Humphrey <>
Subject Re: Clarification on adding a new PPMC member
Date Thu, 15 Jan 2015 22:02:18 GMT
On Thu, Jan 15, 2015 at 1:16 PM, jan i <> wrote:
> On Thursday, January 15, 2015, Marvin Humphrey <>
> wrote:
>> General principle: inviting a PPMC member to join a podling should use
>> exactly the same routine as inviting a PMC member to join a TLP,
>> except that the entity being notified is the IPMC rather than the
>> Board.
> But a TLP  does not advice board when voting begins a podling must with
> current rules.

The rules for a TLP are defined in a Board resolution from June 2013.  Here's
the relevant passage, which is a little quirky:

     1) A notice of the appointment shall be delivered to the Board's
        mailing list and the PMC's private discussion list, as recorded
        within the Foundation's mailing list archives, at least 72 hours
        prior to the effective date of the appointment, where said notice
        may be sent by the chairman, or by any existing member of the PMC
        if it contains a link to a formal decision by the PMC approving
        of the appointment;

The quirk is, if the PMC Chair sends the NOTICE email, it doesn't need to
contain a link to the VOTE result, whereas if any other PMC member sends it
they need a link.  This means that for a TLP at least, if the PMC Chair sends
the NOTICE email, they don't have to wait for the VOTE to conclude, while
anybody else has to.

OK, whatever[1].  PPMCs don't have Chairs, so the Incubator can't mirror the
TLP procedure exactly.  But IMO the Incubator should get as close as possible
so that podlings don't have to relearn much when they graduate.

Personally, I'd like to see the Incubator drop the initial notification that a
vote is underway, leaving only the 72-hour NOTICE to the IPMC referencing the
vote result.

Marvin Humphrey

[1] I'd cite this as an example of how committing to concrete language can
    introduce unexpected complexity, as discussed in recent threads
    (<>) -- and thus an illustration of why minimizing
    absolute requirements is important.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message