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
Looking at the history of emeritus requests, there are a number of request
formats that we have accepted, including scribbled notes captured in jpg
format, emails saved as .eml, emails saved as text, pdfs, pdfs with associated
.asc signatures, etc.
To accommodate all of these seems beyond the s
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 elapse
A mira
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
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
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
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
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
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
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
10 matches
Mail list logo
