On 14 February 2016 at 13:39, Sam Ruby <[email protected]> wrote: > On Sun, Feb 14, 2016 at 4:54 AM, sebb <[email protected]> wrote: >> On 13 February 2016 at 12:06, Sam Ruby <[email protected]> wrote: >>> On Sat, Feb 13, 2016 at 5:57 AM, Sebastian Bazley <[email protected]> wrote: >>>> Commit 5c4d6510288da6e6aac76693606b6fc6e427668f: >>>> Revert sort - does not seem to work >>>> ... >>> --- >>> >>> Where am I going with this? Simply put, React+Bootstrap rocks. The >>> board agenda tool is an example of both being able to update data that >>> is being shown in the browser, and to have interactive dialogs. If >>> you are chair of a committee, you will soon be able to see buttons >>> that will add or remove member and committers of that committee. This >>> will invoke code on the server that will look something like the >>> existing code in the board agenda tool: >>> >>> https://github.com/apache/whimsy/blob/master/www/board/agenda/views/actions/todos.json.rb >>> >>> The code on the server will be able to update LDAP, update SVN, and >>> send emails. So when we get there, we should have lots of interesting >>> discussions as to who should be able to do what actions, what should >>> be updated, and who should be notified when those actions occur. >>> >>> Example: adding a committee member should probably notify board@ and >>> set an effective date of three days from now in committee-info.txt. >> >> Not sure that this will work in most cases. >> >> A person only becomes a PMC member after all the following have occurred: >> - they have an Apache id >> - there was a successful vote NOTICE received by the board mailing >> list and 72 hours have elapsed >> - they have been invited and have accepted >> >> Some PMCs vote to add new people to the PMC before they have Apache accounts. >> Most PMCs don't send the invite until the 72 NOTICE has expired, but >> even for those that send a conditional invite, there is still a wait >> for the candidate to reply. This may take days or weeks. >> >> So I don't think in general the update of committee-info.txt can >> automatically occur 72 hours after the NOTICE is received. > > I look forward to hearing (or better yet: seeing!) what you think will work.
I don't see how it's possible to automate the whole process. However individual stages could be automated. For example: * Sending the NOTICE e-mail. * Updating CI and LDAP to add a user * Updating CI and LDAP to remove a user. The NOTICE button would prompt for the required info, and then save the relevant data somewhere (as well as in the mailbox!) If the user already has a login id, that could be validated (it's not unknown for the wrong id to be used). This could be used for validation later; potentially also to send a reminder to the PMC. The confirmation box could remind the PMC what further stages are needed. Adding a PMC member would prompt for required info such as: has the invitee accepted. It could use the NOTICE data for validation. The CI commit message could include a reference to the NOTICE e-mail and any other relevant info. Similarly for removals; it would ask for the mail id of the resignation (which would be added to the commit message). > - Sam Ruby
