On 16 July 2017 at 03:14, Sam Ruby <[email protected]> wrote: > On Sat, Jul 15, 2017 at 7:01 PM, sebb <[email protected]> wrote: >> On 15 July 2017 at 23:19, Sam Ruby <[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? >>> >>> People with asf-secretary or root authority :-) >>> >>>> Does that require an INFRA JIRA? >>> >>> I typically do this in irb: >>> >>> $ irb -I $HOME/git/whimsy/lib -r whimsy/asf >>>> ASF::LDAP.bind >>>> ASF::LDAP.delete >>>> 'cn=incubator,ou=pmc,ou=committees,ou=groups,dc=apache,dc=org' >>> ... >> >> OK, done for pmc and unix group. > > Cool. > > The remaining cleanup and eventual conversion doesn't merit creating a > UI,
I'm not sure about that. I think the sequence for conversion is: Create and populate new project entry Update Guineapigs in source code. Wait for code to sync on Whimsy <= vital Check groups still agree Delete old LDAP groups The deletion must not be done until Whimsy has the updated code. It's possible for groups to be updated inconsistently during the time they co-exist. So ideally the obsolete groups should not be left around for longer than necessary. So I think it would make sense to do the last few steps (at least) on Whimsy. > but creation of new LDAP definitions for podlings is. When a new > podling is added to podlings.xml and prior to LDAP being set up, the > podling will appear in roster/ppmcs in red. Going to the podling > page, you will see a button: > > https://github.com/apache/whimsy/blob/41743e131f0ebe774ff4cd7bc60950db0592fab5/www/roster/views/ppmc/main.js.rb#L65 > > Clicking that button will cause the list of mentors to be sent to the server: > > https://github.com/apache/whimsy/blob/41743e131f0ebe774ff4cd7bc60950db0592fab5/www/roster/views/ppmc/main.js.rb#L209 > > Which will create the project in LDAP: > > https://github.com/apache/whimsy/blob/master/www/roster/views/actions/ppmc.json.rb#L15 > > Once that is done, the mentors and any ASF member can update the list. > > Longer term, I would love to understand and automate the entire life > cycle of a project, but meanwhile, creation of a new podling in LDAP > can be done via navigation and the pressing of a single button. > > - Sam Ruby
