Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

erlef.org mail for paying members MVP - manual mode #15

Closed
starbelly opened this issue Oct 21, 2020 · 3 comments
Closed

erlef.org mail for paying members MVP - manual mode #15

starbelly opened this issue Oct 21, 2020 · 3 comments

Comments

@starbelly
Copy link
Member

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.
@starbelly starbelly added this to To do in Make It Work via automation Oct 21, 2020
@starbelly
Copy link
Member Author

@benoitc did you have any problems or anything to add to this? The only thing I can think of to tweak is to use zendesk vs an email inbox.

@starbelly
Copy link
Member Author

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.

@starbelly starbelly moved this from To do to In progress in Make It Work Nov 25, 2020
@starbelly starbelly moved this from In progress to Done in Make It Work Dec 9, 2020
@starbelly
Copy link
Member Author

This was resolved and launched.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

1 participant