Contacting EC clarifications

[krassowski]

1. Are issues here monitored? If not, would adding an issue template saying "please post/send message here/there instead" be helpful?
2. What is the place I can ask for small actions which require bothering someone from EC but are not really worth (or at least in my opinion should not require) writing up an email? For example "who has merge rights and can merge a single line change over at Add 2020 Jupyter survey to README.md surveys#24.
3. Is there a guidaince on which topics should be discussed here, which in https://github.com/jupyter/executive-council-team-compass and which on discourse? Currently the documentation only mentions the team compass, issues in this repository are not mentioned at all.

[Carreau]

I have the commit rights to merge jupyter/surveys#24 if needs be. Le me know if you wish me to do it but I do not want to overstep.

[blink1073]

I'd say general governance questions should go here, and items for the EC should either be sent to our email account or raised as an issue on https://github.com/jupyter/executive-council-team-compass.

[blink1073]

@Carreau, please feel free to merge

[fperez]

Thanks @krassowski for bringing this up! This week we discussed it in the EC meeting and came up with the plan below... I'll post it here for now in case anyone has feedback, and if we all agree, we can also copy it to the main EC docs in the repo. I tried to capture our Tuesday discussion as well as additional input from @Ruv7 and @blink1073 above. Thanks all!

Contacting the Jupyter Executive Council

To contact the Jupyter Executive Council (EC), please choose the option that best fits your needs:

• Issues on the EC Team Compass repository: for open, public discussion. We monitor this repository and allocate time on our regular weekly meetings to triage open and active issues.
• EC mailing list: for private communication with the EC, email our list, which is open for public posting (with archive private to EC members).
• Bi-weekly EC Office Hours Zoom call: for synchronous, public conversation, you can join our office hours call, which is listed in the project Google Calendar. You can add topics to the agenda with additional details/references prior to the meeting.

EC members allocate time during our weekly scheduled meetings to review new issues, incoming communications, and active open issues.

Other Channels:

• Issues on the main Governance Repository: offer a space for broader discussion about Governance with the entire community, and are better suited for conversations where input from bodies like the Software Steering Council, project teams and individuals are sought. If you need to flag an issue specifically for input by the EC, please tag the team with @executive-council. The EC will move issues between this general Governance repo and the EC team compass when appropriate.
• The Governance category on Discourse: is not formally monitored by the EC, due to limited bandwidth. It is OK for the community to discuss governance topics there and EC members may occasionally post, but we can not commit to actively monitoring it.

[fperez]

This info is now captured in our docs as per this PR, closing this issue now so we track it in a more official location.