You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue describes the MVP for erlef.org mailing addresses for and is the initial body of work to pave the way to support completing #10.
In short :
Provide a way for paying members to opt in to getting an erlef.org address (form on site, only accessible by paying members)
Requests would go to the infra group
First member of infra group able to fulfill the request should respond to the group stating that they are fulfilling the request
Infra member would create the email address with a temporary password and respond to using infra@ or infra-request@ to the requestor providing basic details of getting going (template required) with the temporary password.
Infra member follows up with the group stating the request has been fulfilled.
The text was updated successfully, but these errors were encountered:
Having a moment to re-think this... I think we should just put the queue in the website app. Admins can login and see outstanding requests and click a "Process" button on individual requests. This way we avoid the pitfalls of having to have a protocol for email inboxes (which is usually a mess) and can keep the requests more zero-knowledge (i.e., the admin doesn't have to know temporary password set for the requestor's newly created email address).
This requires :
making a simple jmap client for fastmail, this is simple
database table to hold the requests (no PII at all)
crud pages, controllers, etc. for processing
This issue regardless of the above is blocked by no consensus. It also blocked by adding fields to wildapricot resources that would have to be updated when a member has an address added, etc.
This issue describes the MVP for erlef.org mailing addresses for and is the initial body of work to pave the way to support completing #10.
In short :
infra@
orinfra-request@
to the requestor providing basic details of getting going (template required) with the temporary password.The text was updated successfully, but these errors were encountered: