Set up communication for Jupyter Foundation

[jasongrout]

To propose at the next Jupyter Foundation meeting: largely follow the conventions we have for the EC:

1. Set up private governing board mailing list
2. Set up private Foundation member mailing list
3. Set up team compass repo
4. Set up Google Drive for Jupyter Foundation (or perhaps a folder in the EC drive?)
5. Update the Jupyter Foundation members in the Jupyter governance.

Questions:

1. Should we create a new GitHub org? That makes the permissions cleaner.
2. Where to store the assets from Jupyter Foundation (logo, website, etc.)?
3. Should we set up a Google drive, or just a folder in the EC drive with appropriate permissions?

[Carreau]

1. Should we create a new GitHub org? That makes the permissions cleaner.

Pleeeeeease no.

Yet again today the pain of N orgs got pain painful with https://thanks.dev.

[jasongrout]

I also hesitate to create a new org, but could see pros and cons to doing so, hence why it is a question. Thanks for your feedback and continued push to simplify things!

Pros to creating new org:

• JF is a separate legal entity under the LF c6, so it may be cleanest to have separate permissions and ownership of a separate github org (but still under the project jupyter enterprise org).

Pros to locating materials under this jupyter-governance org:

• Since the EC are members of the JF governing board, it may be sufficient to having any materials living in this EC-controlled jupyter-governance org. The ramifications of living here is that anything that the JF owns on github, the EC can administer, which I think is okay. But it's a decision for the JF governing board as a whole.
• Of course, administering a new org is one more friction point, as @carreau points out.

In the end, it will be a decision for the JF governing board, but I think I'm leaning towards proposing that the materials be located in this org.