Infrastructure: Mailing lists
brianwarner opened this issue · 4 comments
I'm taking care of some administrative tasks, like setting up the mailing lists on the "@lists.openjsf.org" subdomain. I'm looking for input on what lists we will need to support the various governance structures, and how they should be configured.
I'm assuming that the CPC will use GitHub for most things. However, there may be certain scenarios where a team requires a private channel. For example, moderation discussions.
This is an open call for input on what lists I should create, and how they should be configured. Please propose lists as comments to this issue, and please provide this information:
- Which group will use it?
- Should it be listed on https://lists.openjsf.org?
- Is self-subscription allowed?
- Are the archives public, or for members only?
- Can non-members email the list (e.g. to file reports)?
- Can members email the list, or is it announce-only?
We can discuss these further in the bootstrap calls.
Maybe start with
- cpc-private
- report
- coc-escalation
@brianwarner below are bullet points from the last meeting notes. Can you confirm and add any updates if there are any? Part of why I ask is because coc-escalation@ is referenced in #147. Thanks!
- Infrastructure: Mailing lists #134
- Brian having been working on getting pieces in place
- Current lists:
- announce@
- report@
- coc-escalation@
- projects@
- cpc-private@
- Also created announcement list for key interested parties in the project. Once get list
of current people that she is emailing.