Thank you Sam. This is very much appreciated. I've been even more swamped than usual this last couple of weeks. I'll use this pretty much verbatim as I don't think I'm going to have time to fully review the archives tonight.
Item 1) is a little confusing as the Infra report states "Currently ~1/2 of Whimsy committers do not have commit access to the repository because they have not enabled MFA." I've come to this too late to resolve this apparent contradiction. Ross -----Original Message----- From: Sam Ruby [mailto:[email protected]] Sent: Friday, January 15, 2016 1:32 PM To: Ross Gardler <[email protected]> Cc: [email protected] Subject: Whimsy board report input Items that may be worth including in the board report... 1) Many/(most?) committers are now authorized to push to the GitHub repository. MATT is now online, but there appears to still be a manual step required to identify which GitHub ID is to be associated with your Apache account. This presumably will be ironed out over time, and at the moment only represents a point of confusion, not a stumbling block. 2) In addition to myself, two committers (Chris and Sebb) have succeeded at actually pushing to GitHub. Also two committers (Craig and Sebb) are able to run individual tools on their own development machines[1]. Their changes are automatically deployed, without human intervention[2]. 3) Set up of the whimsy-test VM has begun in earnest. To the extent humanly possible, everything is either provisioned through Puppet or deployed automatically from the GitHub repository[3]. 4) Status monitoring is beginning to be roughed in[4]. At the moment, it is a simple ping endpoint. This will be expanded to provide fine grained status of the various applications, coupled with infrastructure alerts. 5) A replacement for the Secretary mail tool is nearing completion. It should be considerably more responsive and reliable than the current tool[5], which required multiple manual cleanup of intermediate svn directories this month. The hope is that with this version of the tool, Craig will be able to develop, locally test, and deploy improvements such as adding buttons and tweaking the content of emails produced. 6) Additional items planned for the next month (or so) include: a) Flipping the "big switch" to enable synchronization between GitHub and ASF hosted repositories. b) Moving the board agenda tool over to what is now called whimsy-test. c) Changing the DNS so that that what is not whimsy-test will become the new whimsy. The old whimsy will remain around under a new name for a few months. - Sam Ruby [1] https://github.com/apache/whimsy/blob/master/README.md [2] https://github.com/apache/whimsy/blob/master/DEVELOPMENT.md [3] https://github.com/apache/whimsy/blob/master/DEPLOYMENT.md [4] https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fissues.apache.org%2fjira%2fbrowse%2fWHIMSY-35&data=01%7c01%7cRoss.Gardler%40microsoft.com%7cc67097ef81ff41f3bd0308d31df35224%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=sAoFdqM0a5DXgiQJ3xD0sbRPqoqhGR7j09espelI5IM%3d [5] https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fmail-archives.apache.org%2fmod_mbox%2fwhimsical-dev%2f201601.mbox%2f%253C5693CEFE.9020608%2540intertwingly.net%253E&data=01%7c01%7cRoss.Gardler%40microsoft.com%7cc67097ef81ff41f3bd0308d31df35224%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=c%2fMsYsUbULzrmKx5FpupQlMNi6vhp7chvPBxiRuo3jk%3d
