incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Harui <>
Subject Re: Cultivating Outstanding IP Stewards
Date Sun, 17 Nov 2013 04:59:24 GMT

On 11/16/13 8:47 AM, "Upayavira" <> wrote:

>I'm not sure I see the difference between a release auditor and an IPMC
>member. If someone is sufficiently clued up to audit a release, then
>they're surely ready to join the Incubator PMC. Am I missing something?
To me, there is more responsibility in being on the IPMC, like reviewing
proposals for new podlings and voting on their graduation and becoming a
mentor.  Personally, that's why I don't want to be on the IPMC, but I
might be willing to help IP audit a podling's release.  Just like some
projects don't have all committers on the PMC, a Release Auditor is just
someone who can do that specific task, and there is no need to vote them
in if they are already on some other TLP PMC because any member of a TLP
PMC supposedly knows how to do release auditing.

>My interest is in a lesser level of involvement, where someone has shown
>merit within their own PPMC and can get a binding vote there, but
>no-where else. That feels to me like a very useful intermediate step to
I agree, except for the no-where else part.  If you know how to check a
RAT report and have an idea of what should be in the NOTICE files, you
should be able to help out any other podling by reviewing their release
and casting a binding vote so they can learn how to do that.  I'd say that
3 IPMC members must vote to give a person Release Auditor status if they
are not already on a TLP PMC.  Consider this:  I am an the Flex PMC but
not the IPMC, but if I join the PPMC of some new podling, why shouldn't I
be able to cast a binding vote for that podling's releases?


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

View raw message