[
https://issues.apache.org/jira/browse/WHIMSY-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15234393#comment-15234393
]
Sam Ruby commented on WHIMSY-56:
--------------------------------
I think we are saying the same thing. In particular, note that I said
"conclusion of the board meeting, the secretary processes the resolutions...".
Recapping the current process:
1) Somebody (often either the outgoing or incoming chair) drafts a resolution,
mails it to the board list, and then somebody commits it to the agenda.
2) The secretary sends out emails and updates LDAP at the end of the board
meeting
3) The incoming chair updates committee-info.txt.
Proposed new flow:
1) Outgoing chair uses the roster tool to draft, send, and commit a resolution
2) The secretary updates LDAP and committee-info.txt at the end of the board
meeting.
> Project Chair change resolution
> -------------------------------
>
> Key: WHIMSY-56
> URL: https://issues.apache.org/jira/browse/WHIMSY-56
> Project: Whimsy
> Issue Type: Wish
> Reporter: Sebb
>
> Might be useful to generate (and mail) a project chair change resolution?
> The historic chair details can be derived from CI.txt and the proposed
> replacement presumably chosen from the other PMC members.
> I don't think there can be a non-PMC chair unless imposed by the board, but I
> suppose one could allow for an alternative...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
