As a practical matter the tlp migration scripts seed the committer group from the list in asf-authorization for svn. The PMC is taken directly from the resolution, but if there is no corresponding group in svn (say UCB applies to the project) then the PMC chair has to seed the committer group themselves.
It is remarkably easy for a chair to ensure that everyone on the pmc is in fact in the unix group for the project: % list_committee.pl foo | modify_unix_group.pl foo --add - the code will filter out any redundancies automatically. On Friday, April 4, 2014 7:38 AM, Bertrand Delacretaz <bdelacre...@apache.org> wrote: Hi, > >On Fri, Apr 4, 2014 at 12:29 PM, Edward J. Yoon <edwardy...@apache.org> wrote: >> ...When consider TLP graduation, all >> committers should be PPMC members?... > >At the foundation level (i.e. in the board resolution that establishes >the project) we don't care about committers, it's only PMC members >which are relevant. > >If a podling wishes to have only a subset of its committers as PPMC >members that's possible, and as I wrote earlier in this thread the >committers are not mentioned in the graduation resolution but they can >be re-established by the new PMC right after graduation. > >IOW, "PMC member" is a foundation-level status whereas it's only the >PMC who's responsible for the "committer" status. > >-Bertrand > >--------------------------------------------------------------------- >To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >For additional commands, e-mail: general-h...@incubator.apache.org > > > >
