TPA-RFC-31: outsource email services
The proposal to host the entirety of our email services in-house, TPA-RFC-15, was officially rejected (see #40363 (closed) and wiki-replica@ea20e615 for details). Now we need to figure out which part of email we'll outsource, and to whom.
This ticket is to track the drafting and adoption of that proposal. Once that's done, new tickest should be created for those individual tasks.
quick brainstorm of a checklist:
-
brainstorm requirements here -
adopt requirements -
figure out what we'll do with the existing email services (e.g. probably retire submission?) -
personas -
list possible providers -
generic -
transactional
-
-
checkin with isa about what SLA we want -
officialize quotes, don't forget to mention SLA -
costs -
staff, setup -
staff, ongoing -
hosting
-
-
timeline -
approval: same as TPA-RFC-15? (TPA, internal, ops, in that order?) -
deadline: maybe draft this within 2-3 weeks max, adoption in 4-6 weeks? -
review TPA-RFC-15 to see if we forgot any bits
any other ideas?
draft lives in https://gitlab.torproject.org/tpo/tpa/team/-/wikis/policy/tpa-rfc-31-outsource-email
Edited by anarcat