Create process for managing @innersourcecommons.org emails about infrastructure HOT 5 OPEN

Google groups can be private. I would expect the [email protected] group to be private, with access controlled by the group. But having all e-mail archived will let the group members (which will likely change over the years) still access all communications.

from infrastructure.

Should we establish a google group for the main [email protected] so that all the traffic is maintained?

from infrastructure.

Sounds like an idea. Do we expect any sort of more confidential / non-public inquiries there that would warrant using something non public?

from infrastructure.

Sounds like an idea. Do we expect any sort of more confidential / non-public inquiries there that would warrant using something non public?

Since much of our work is covered under Chatham House rule, I would say yes. In addition, functions like finance or legal would also need the ability to have multiple people involved in a non-public way.

from infrastructure.

Created a first draft of project concerns here: https://github.com/InnerSourceCommons/infrastructure/blob/master/projects/email.md

Please comment on the process here and PR changes to the document. We'll capture the discussion of options in the project itself.

from infrastructure.