Create a team compass for the Jupyter Foundation governing board

[choldgraf]

Jupyter uses the pattern of a "Team Compass" to give its team members all the information they need to meaningfully participate, and to help newcomers understand the structure, dynamics, and goals of the project. A few examples:

• Executive Council Team Compass
• JupyterHub team compass

If the Governing Board has enough of its own processes, planning, etc, then it might help to define a Team Compass for this team as well. This is an issue to:

1. Decide whether we want a team compass for the JFGB
2. Decide where we'd want to host it (e.g., either in a standalone repository, or as a sub-page of https://github.com/jupyter-governance/ec-team-compass)
3. Decide what minimal structure we want to add for boostrapping it

[sagelywizard]

1. Sounds good to me.
2. No opinion.
3. Seems like we could just copy the structure https://executive-council-team-compass.readthedocs.io/en/latest/

If nobody has any dissenting opinions, what's the next step? Making a draft and sharing it at the meeting for approval?

[choldgraf]

Give that we're all very busy and largely asynchronous except for once a week, I suggest we try to follow a lightweight model like:

1. Describe the intent in an issue (which you've done above, we might want to add more detail like "will we create a new repository"). This should include a time-box for the decision ("If there aren't objections in X days we will action this", choose X with your best judgment based on complexity of the ask)
2. Define a place for the governing board to "watch" for actions that will happen without objections.
3. Put the issue in that place and field any questions / iterate on the idea / etc.
4. At the end of X days, if there are no objections, then act on it.
5. Once the action is done, close the issue.

I also suggest that we define basic working principles like "Trust one another's judgment, provide transparency about intent and rationale, and bias towards action when in doubt" so that we recognize that we might not get it perfect, but the important thing is to iterate and trust that we're all doing our best to move forward.

this became a broader comment about decision-making practices for this group, I'm happy to move to a new issue if that's better

[sagelywizard]

Yeah, that sounds great! Definitely worth another ticket to discuss. You want to create it? I'd be happy to too.

[choldgraf]

@sagelywizard go for it!

[Zsailer]

1. I concur.
2. I vote for a new repo to keep things separate.
3. I echo what Ben says here.

[sagelywizard]

Created an issue here: #8

[choldgraf]

This team compass now exists! It's hosted at this repository and has a URL linked from the landing page of the repo