Expand the language around communicating with EC.

This copies language from https://github.com/jupyter/governance/issues/171\#issuecomment-1615249925 for communicating with the EC

Fixes #21

docs/index.md

@@ -12,11 +12,17 @@ For more details about how the Executive Council operates, see the [operational
 
 ## Contacting the Executive Council
 
-To contact the EC in a public forum, you may:
-* Join the regular public [EC office hours](office_hours/index.md).
-* Open a new issue on the [EC Team Compass](https://github.com/jupyter/executive-council-team-compass/issues/new).
+To contact the [Jupyter Executive Council (EC)](https://jupyter.org/about#executive-council-members), please choose the option that best fits your needs:
 
-To contact the EC privately, send an email to the [EC mailing list](mailto:[email protected]). Anyone can post to this list, but messages can only be read by members of the EC.
+* [Issues on the EC Team Compass repository](https://github.com/jupyter/executive-council-team-compass/issues): 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](mailto:[email protected]): for _private communication_ with the EC, email our list, which is open for public posting, but only executive council members can read messages or archives.
+* [Bi-weekly EC Office Hours Zoom call](https://zoom.us/j/2264645576?pwd=c0JZTHlNdS9Sek9vdzR3aTJ4SzFTQT09): for _synchronous, public conversation_, you can join our office hours call, which is listed in the [project Google Calendar](https://jupyter.org/community#calendar). You can add topics to the agenda (see calendar entry for link) 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](https://github.com/jupyter/governance): 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](https://jupyter.org/governance/software_steering_council.html), 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](https://discourse.jupyter.org/c/meta/governance/23): 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.
 
 ## Table of Contents