Craig L Russell created WHIMSY-323:
--------------------------------------
Summary: Add a process for handling emeritus requests
Key: WHIMSY-323
URL: https://issues.apache.org/jira/browse/WHIMSY-323
Project: Whimsy
Issue Type: New Feature
Components: SecMail
Reporter: Craig L Russell
Assignee: Craig L Russell
Brainstorming here. The Bylaws say that 10 days after receiving an emeritus
request, the member should become emeritus unless the request is withdrawn.
Members should be able to file an emeritus request as easy as a proxy: go to a
web page, log in with member credentials, fill the form, send it. That same
page should also remember that an emeritus request was filed and give the
member the ability to withdraw the request (when the member returns to the
page, it looks up to see if there is already a pending emeritus request). So
the request should be put into a well-defined file, say
documents/emeritus-requests-received. When this is filed, a message should be
sent to secretary which will show up in the to-do secretary mail, and copied to
the member. There should be an attachment of the emeritus request that can be
verified as valid by secretary.
The subject of the email to secretary should make it clear that this email was
generated by the whimsy emeritus tool, e.g. subject: Your emeritus request has
been received
When the 10 day period is over, secretary can process the request by clicking
on the email. When the file, e.g. clr-emeritus.txt is clicked, the Categorize
menu will include the (o) Emeritus button which when clicked, displays a form
with: Member ID, Member Name, Date fields and (File) button. When the (File)
button is pressed, the svn commands to move the file from
documents/emeritus-requests-received to documents/emeritus; the update of the
members.txt to move the member to emeritus section and update the active count,
and email to the member with information how to be reinstated etc. etc.
This same tool should also allow for processing of submitted signed
(holographic or gpg) emeritus requests.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
