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
Set up default email aliases if not already done:
privacy@ (required contact in some jurisdictions)
security@ (private reporting for now)
support@ (already exists, I believe)
postmaster@
aspirepress.org
It would be good to include a few others:
partners@ (i.e., reach to this address about setting up a node etc)
sponsors@ (being hopeful)
complaints@ (or something better for community issues needing responses).
sysadmin@ (infra/devops team)
Noted that many/most of these will go to the same place right now, but we can publish them this way and redirect or add to the alias later without remembering where we have to update documents. Some of these relate to infra and some to management roles. Not sure if we have/need an info@ or admin@ but some form of general inbox would be good.
Document the list with current target name(s) for each email alias when complete. (e.g., "privacy@ => Sarah Savage" etc.)
The text was updated successfully, but these errors were encountered:
I'm happy to add any "group" you like. I just need to know who to add to each group. They will need to validate their emails. Please send me an email directly with the group name and the members.
Set up default email aliases if not already done:
privacy@ (required contact in some jurisdictions)
security@ (private reporting for now)
support@ (already exists, I believe)
postmaster@
aspirepress.org
It would be good to include a few others:
partners@ (i.e., reach to this address about setting up a node etc)
sponsors@ (being hopeful)
complaints@ (or something better for community issues needing responses).
sysadmin@ (infra/devops team)
Noted that many/most of these will go to the same place right now, but we can publish them this way and redirect or add to the alias later without remembering where we have to update documents. Some of these relate to infra and some to management roles. Not sure if we have/need an info@ or admin@ but some form of general inbox would be good.
Document the list with current target name(s) for each email alias when complete. (e.g., "privacy@ => Sarah Savage" etc.)
The text was updated successfully, but these errors were encountered: