On 16 July 2018 at 02:08, Hen wrote:
> +1 to automatically carried forward which I suspect is how it’s been
> handled up to now.
Before LDAP was used for podlings, committers were not distinguished
from PPMC members.
Only those in the TLP resolution were added to the PMC and committer
LDAP groups that were created as part of graduation.
It was up to the new PMC to request additional ids to be added to the
committer group.
This was a way of dropping people who would not be contributing to the
PMC (e.g. mentors may wish to drop out)
When podlings were defined in LDAP, this changed, as there was no
longer any need to create the LDAP groups on graduation.
> On Sat, Jul 14, 2018 at 4:15 AM sebb wrote:
>
>> When a podling graduates, all the people listed on the board
>> resolution become both PMC members and committers.
>>
>> What is the policy for podling committers?
>>
>> Are they all automatically carried forward as committers?
>>
>> Or does the podling need to specifically need to re-appoint the
>> committers that are not mentioned in the graduation resolution?
>>
>> S.
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
