Next level of architecture: Most of the work should be done in the front end with a bit of help from the server. What we need from the server are:
GET: given the apache id, return the full name, status (boolean: emeritus), the complete document if already filed under emeritus-requests-received POST: apache id, full name, filled emeritus form (if new request), rescind-requested (boolean) So what technology seems most suitable? Node can handle the http requests if we have a service running. Javascript can do the UI in the browser. How to glue all of this together? Craig > On May 3, 2020, at 7:22 AM, Craig Russell <apache....@gmail.com> wrote: > > We will create a new script at members/emeritus.cgi that will use a file > template [1] at a member-accessible location. This script will be linked from > the Members whimsy page. > > The script will have three entry points: > Member in good standing > Emeritus request has been submitted > Emeritus Member > > Member in good standing: > Emeritus status will be described, and a button enabled: > (Prepare emeritus request) > > When the button is pressed, a window pops up with the Emeritus Request form > filled from the member's information and the local timestamp (year-month-day > hh:mm:ss <timezone> <+/- offset>) and at the bottom of the form two buttons: > (Submit emeritus request) > (Cancel) > > When cancel is pressed, the popup window disappears, and the original page > redisplays. > When submit is pressed: > the filled form is filed under emeritus-requests-received > email is sent to secretary with a copy of the form, cc: the member > > Emeritus request has been submitted: > Information about the emeritus request (timestamp) is displayed, and a button > enabled: > (Rescind emeritus request) > > When rescind is pressed, a window pops up with the submitted Emeritus Request > and at the bottom of the form two buttons: > (Submit rescind request) > (Dismiss) > > When dismiss is pressed, the popup window disappears and the original page > displays. > When submit is pressed: > the file is moved to emeritus-request-rescinded > email is sent to secretary stating that the request was rescinded, cc: the > member > the Member in good standing page displays. > > Emeritus Member: > Emeritus status is described and a button displays: > (Request reinstatement) > > When request is pressed, a window pops up with text stating that the members > wishes to reinstate membership and two buttons: > (Submit reinstatement request) > (Dismiss) > > When dismiss is pressed, the Emeritus Member display is shown > When submit is pressed, email is sent to secretary requesting reinstatement, > cc: member. > > Comments? > > Craig > > [1] > Emeritus Request > > Dear Apache Secretary, > > Please change my status to emeritus. > > This request will be effective ten days after receipt. Once effective, > I understand that I will no longer be counted for quorum purposes at > Members Meetings, and I will no longer be able to vote at Members Meetings. > > I understand that my privileges to review the foundation records and > subscribe to members mail lists will continue. If I would like to become > active again, I will send email to secret...@apache.org requesting > reinstatement, and my request will be voted on at the next members meeting. > > > Apache id: __________________________________________________________ > > Full name: __________________________________________________________ > > > > > > > > Signed: __________________________________ > > > Date: ____________________ > > > > Craig L Russell > c...@apache.org > Craig L Russell c...@apache.org
