Re: Some improvements suggested for emeritus work flow

2020-07-07 Thread sebb
ue: 'request_emeritus' > end > elsif committer.member.status.include? 'Emeritus' > _button.btn.btn_primary 'request reinstatement', > name: 'action', value: 'request_rei

Re: Some improvements suggested for emeritus work flow

2020-07-07 Thread Craig Russell
us_person_name:@@person.public_name, name: 'action', value: 'request_emeritus' end elsif committer.member.status.include? 'Emeritus' _button.btn.btn_primary 'request reinstatement',

Re: Some improvements suggested for emeritus work flow

2020-07-07 Thread sebb
rlier versions if really necessary. > Thanks, > Craig > > > On Jul 6, 2020, at 10:13 AM, Craig Russell wrote: > > > > Just one final observation. > > > > The emeritus work flow once this PR is merged: > > > > Member decides to go emeritus, naviga

Some improvements suggested for emeritus work flow

2020-07-07 Thread Craig Russell
would use a tool to make the member emeritus. Tooling is not the important feedback request here. Anyone have an opinion? Thanks, Craig > On Jul 6, 2020, at 10:13 AM, Craig Russell wrote: > > Just one final observation. > > The emeritus work flow once this PR is merged: > >

Re: Emeritus work flow

2020-05-06 Thread Bertrand Delacretaz
Hi Craig, On Wed, May 6, 2020 at 2:36 AM Craig Russell wrote: > ...The member who wishes to go emeritus can use the roster/_self_ page, double > click on Member status, click "request emeritus status", click (Submit) and > be done... I like that, especially as you also mention the Secretary lat

Re: Emeritus work flow

2020-05-05 Thread Craig Russell
ike to see the full current documentation on the emeritus work flow. > Here's what I understand: > > User fills emeritus request, signs, and sends email to Secretary. > > Secretary uses whimsy workbench to file the document under > documents/emeritus-requests-received >

Re: Emeritus work flow

2020-05-05 Thread Craig Russell
I'd like to see the full current documentation on the emeritus work flow. Here's what I understand: User fills emeritus request, signs, and sends email to Secretary. Secretary uses whimsy workbench to file the document under documents/emeritus-requests-received At least ten days

Re: Emeritus work flow

2020-05-04 Thread Sam Ruby
On Mon, May 4, 2020 at 8:05 PM Craig Russell wrote: > > Double clicking on the roster member status enables a menu with options: > move to active > move to deceased > move to emeritus > > To add "request emeritus" and "rescind emeritus request" I need to know > whether there is already an emeritu

Re: Emeritus work flow

2020-05-04 Thread Craig Russell
Double clicking on the roster member status enables a menu with options: move to active move to deceased move to emeritus To add "request emeritus" and "rescind emeritus request" I need to know whether there is already an emeritus request pending. This could be done by having the committer.membe

Re: Emeritus work flow

2020-05-03 Thread Sam Ruby
On Sun, May 3, 2020 at 7:22 PM Craig Russell wrote: > > I'd like to start with something that should be trivial: > > When the user presses "move to emeritus" or "deceased" the action is > immediate. I'd like to change these buttons to raise a dialog box with > (submit) and (cancel) buttons. In g

Re: Emeritus work flow

2020-05-03 Thread Craig Russell
I'd like to start with something that should be trivial: When the user presses "move to emeritus" or "deceased" the action is immediate. I'd like to change these buttons to raise a dialog box with (submit) and (cancel) buttons. In general, this is my own preference and better UX and I think muc

Re: Emeritus work flow

2020-05-03 Thread Sam Ruby
On Sun, May 3, 2020 at 5:06 PM Craig Russell wrote: > > 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 c

Re: Emeritus work flow

2020-05-03 Thread Craig Russell
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

Re: Emeritus work flow

2020-05-03 Thread Matt Sicker
Sounds like a great idea so far! On Sun, 3 May 2020 at 09:22, Craig Russell 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 thr

Emeritus work flow

2020-05-03 Thread Craig Russell
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 M