Either you draw the parallels to the TLPs or you don't.

If you do, TLPs don't have Mentors, but they do have a PMC, typically with
engaged members and a 'phone line" to the board in forms of a Chair. If the
"Chair" goes AWOL, then either the PMC members request help from the board
to appoint a new Chair, typically by submission of a resolution, or the
board notices that the phone is no longer ringing, in which case the PMC is
asked if it has died or not.

Translate;
PMC -> Podling committers
PMC Chair -> Mentor
Board -> Incubator PMC

Now, we have the complication that there are 3 mentors, sometimes all
assuming that the "others" will handle it, and podlings are unwise about
what is expected.

I have argued before for a single Mentor, with responsibilities just like
the PMC Chairs and if failing the duties, duly replaced by IPMC. The
counter-argument to single Mentor is that podlings need 3 binding votes,
and I suggest to change the role names here to perhaps "Supporter" and the
Mentor simply emeritus any Supporter that is absent too long, and come to
IPMC to request more help.

Hopefully, we can get to a position where podlings are not asking for IPMC
release votes, just like TLPs are not asking for Board's approval of
releases.

And I think that if the Mentors are then keeping a up-to-date rooster on
Supporters, we have a pretty good overview of podlings' health.


Cheers
Niclas



On Wed, Apr 26, 2017 at 1:37 PM, Bertrand Delacretaz <
bdelacre...@codeconsult.ch> wrote:

> On Wed, Apr 26, 2017 at 5:47 AM, P. Taylor Goetz <ptgo...@gmail.com>
> wrote:
> > ...I mostly agree, but would hesitate with the idea that a podling be
> responsible for raising a red flag
> > when mentors are inactive. If the IPMC isn’t doing it’s job, that’s on
> us, not the projects we incubate....
>
> The IPMC will typically not know before it's too late, so it's good
> for the podlings to raise those red flags - and ask the IPMC for help.
>
> -Bertrand
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
Niclas Hedhman, Software Developer
http://polygene.apache.org - New Energy for Java

Reply via email to