[ 
https://issues.apache.org/jira/browse/WHIMSY-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15234379#comment-15234379
 ] 

Sam Ruby commented on WHIMSY-56:
--------------------------------

As to your last comment, I don't see a reason to optimize for the rare case.  
At a minimum, this could be done as a follow-on change.

I'd propose that this be done via the roster tool.  Proposed flow: outgoing PMC 
chair visits the page for the commitee that he/she chairs.  Double clicks on 
the new chair.  Instead of seeing only buttons describing removal actions, sees 
an additional button to draft a chair change resolution.  When that button is 
pushed, a modal dialog appears containing a draft resolution in a textarea, 
enabling changes to be made.  There are options to cancel or submit the 
resolution.

If submitted, the chair change resolution is added to the next board agenda (if 
one can be found) and the email is sent to the board list copy the private list 
for the PMC in question.

At the conclusion of the board meeting, the secretary processes the 
resolutions, which currently means updating LDAP.  That code doesn't currently 
send out emails or update committee-info.txt.  The former is just simply a 
TODO.  The latter was a conscious decision as it introduces the new chair to 
the idea of directly editing committee-info.txt.  Now that the latter can be 
done via the roster tool, it may be time to revisit that decision.

> 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)

Reply via email to