Re: Board agenda is still editable after the meeting

On Wed, Jul 15, 2020 at 8:38 PM Craig Russell wrote: > > I noticed a change to the board agenda after today's meeting. > > Once the meeting is done, I expect that only Secretary (team) and maybe Board > Chair should be able to edit the file (either directly via svn or from the > agenda whimsy to

Re: Architecture formerly in whimsy-board-agenda-nodejs/README.md

On Wed, Jul 15, 2020 at 8:20 PM Craig Russell wrote: > > I'm viewing the walkthrough and trying to find the architecture that used to > be in README.md. You can still find the README as it was (over two months ago!) n the version history: https://github.com/rubys/whimsy-board-agenda-nodejs/comm

Board agenda is still editable after the meeting

I noticed a change to the board agenda after today's meeting. Once the meeting is done, I expect that only Secretary (team) and maybe Board Chair should be able to edit the file (either directly via svn or from the agenda whimsy tool). Does anyone have a different view? Can this be done via svn

Architecture formerly in whimsy-board-agenda-nodejs/README.md

I'm viewing the walkthrough and trying to find the architecture that used to be in README.md. Has it been moved, or deleted? Thanks, Craig Craig L Russell c...@apache.org

Re: Secretary workbench processes emeritus requests

> On Jul 15, 2020, at 2:37 PM, sebb wrote: > > On Wed, 15 Jul 2020 at 20:10, Craig Russell > wrote: >> >> I'm now looking at how to integrate this with the workbench code. >> >> It looks like the front end does not need much work if all we do is add one >> line

Re: Secretary workbench processes emeritus requests

On Wed, 15 Jul 2020 at 20:10, Craig Russell wrote: > > I'm now looking at how to integrate this with the workbench code. > > It looks like the front end does not need much work if all we do is add one > line to the index page for each emeritus request, and highlight the requests > that are ready

Re: Secretary workbench processes emeritus requests

I'm now looking at how to integrate this with the workbench code. It looks like the front end does not need much work if all we do is add one line to the index page for each emeritus request, and highlight the requests that are ready for action. Some easy lifting is to have the front end href:

[jira] [Commented] (WHIMSY-213) Secretary workbench message hash is not guaranteed unique or stable

[ https://issues.apache.org/jira/browse/WHIMSY-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17158542#comment-17158542 ] Sebb commented on WHIMSY-213: - Also, if the message id is missing, the hash uses the entire m

[jira] [Updated] (WHIMSY-213) Secretary workbench message hash is not guaranteed unique or stable

[ https://issues.apache.org/jira/browse/WHIMSY-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated WHIMSY-213: Summary: Secretary workbench message hash is not guaranteed unique or stable (was: Secretary workbench message has

Re: Do we still need whimsy-test.a.o DNS?

On Wed, Jul 15, 2020 at 9:21 AM sebb wrote: > > I am assuming that the name is no longer needed, so it can be retired > once whimsy5 is no longer in use Sorry for not answering before. I don't think it ever was required. At the time, I thought it might be an easier way to handle the transition t

Re: Do we still need whimsy-test.a.o DNS?

I am assuming that the name is no longer needed, so it can be retired once whimsy5 is no longer in use On Wed, 8 Jul 2020 at 22:33, sebb wrote: > > whimsy-test currently points to whimsy-vm5. > > I'm not sure it's still required, but if it is, then it needs to be moved to > vm6 > > Sebb