On 15 July 2017 at 23:25, Sam Ruby <[email protected]> wrote:
> On Sat, Jul 15, 2017 at 6:19 PM, John D. Ament <[email protected]> wrote:
>> On Sat, Jul 15, 2017 at 6:09 PM sebb <[email protected]> wrote:
>>
>>> On 15 July 2017 at 22:51, Sam Ruby <[email protected]> wrote:
>>> > On Sat, Jul 15, 2017 at 5:36 PM, sebb <[email protected]> wrote:
>>> >> The LDAP unix and committee groups still exist for incubator.
>>> >>
>>> >> However incubator is now a guineapig, so I would expect the original
>>> >> groups to have been deleted?
>>> >>
>>> >> The LDAP project for incubator has got all the original owners and
>>> >> members from the corresponding old groups, plus a few new entries in
>>> >> each.
>>> >>
>>> >> Should the old incubator LDAP groups now be dropped?
>>> >
>>> > Sure.
>>> >
>>> >> Also some recent graduated podlings exist in both new and old forms:
>>> >> carbondata
>>> >> eagle
>>> >> fineract
>>> >> metron
>>> >> ranger
>>> >> systemml
>>> >>
>>> >> The project owner/member groups don't agree with the LDAP
>>> committee/unix groups.
>>> >> This is quite confusing...
>>> >
>>> > Unless they are listed as guineapigs, the "new" form is a leftover
>>> > from when they were a podling. The "new" forms for these PMCs
>>> > therefore should be deleted and then reconstructed from the "old" form
>>> > when the cutover happens.
>>>
>>> I see.
>>>
>>> Whose can do the deletions?
>>> Does that require an INFRA JIRA?
>>>
>>
>> Or should we auto-guinea pig them, since it's now what they're used to from
>> being a podling?
>
> I'm OK with that too.
>
> Example:
>
> ASF::LDAP.delete('cn=eagle,ou=groups,dc=apache,dc=org')
Won't that lose the list of committers?
I would expect the group and committee to be deleted only after the
project has been successfully synched...
> pmc = ASF::Committee['eagle']
> ASF::Project.find('eagle').create(pmc.owners, pmc.committers)
That looks as though it would only work if the project does not yet exist?
> (just sharing knowledge here)
>
> - Sam Ruby
