Makes lots of sense - I love the idea. Hen
On Sun, May 22, 2016 at 6:00 PM, Sam Ruby <ru...@intertwingly.net> wrote: > As I am working my way through this code, it occurs to me that much of > what I am finding could apply to termination of projects. For > example, if the secretary adds the PMC to LDAP for 'Establish' > resolutions at the end of the board meeting it might make equal sense > for the secretary to remove the PMC (and committers) for 'Terminate' > resolutions. > > Thoughts? > > - Sam Ruby > > On Tue, May 17, 2016 at 6:51 PM, Sam Ruby <ru...@intertwingly.net> wrote: > > Statement of the problem (by Chris Lambertus): > > > > Our process for tlp creation is to run the script, figure out why half > the > > steps failed, re-run it a few times until it works, then go do all the > > manual mailing list creations and jira and conflience etc. etc. > > > > General outline of the solution being explored (by Sam Ruby): > > > > The goal is to make it so that asf-secretary and pmc-chair people can do > > most of the work themselves. The first step will be to have me do the > the > > tlp requests manually this month (I'm in both groups) with the > > infrastructure contractors (primarily @fluxo and @pono) providing > guidance > > and adjusting the authorizations as required. As soon as it becomes > > possible for the secretary and pmc chairs to execute these tasks, focus > will > > turn to automation and providing a web interface. > > > > Current code base: > > > > https://svn.apache.org/repos/infra/infrastructure/trunk/tlpreq > > > > Secretarial tasks will likely be merged into the board agenda tool, pmc > > chair tasks will like be merged into the roster tool. > > > > - Sam Ruby >
