Team communication and user support

We organize our discussions in order to help both contributors and maintainers find and choose the right communication channels and have a positive experience :-)

Types of discussions

We break down team discussions into two broad categories:

1. For specific discussions related to changing a repository’s content we use GitHub issues in the repository where they are most relevant. For example, feature requests, bug reports.

2. For general discussion, support questions, feedback, etc, use the Jupyter forum.

How to get in touch with the JupyterHub Council

There are two recommended ways to send communications to the JupyterHub Council:

1. Open an issue in our Team Compass. We use this as a space for team discussion of all kinds, and JupyterHub Council members are expected to monitor these issues. This is the preferred space for most team conversation.

2. Send an e-mail to jupyterhub-team-council@googlegroups.com. This is a shared inbox that we use for people that prefer non-public or e-mail communication instead of GitHub issues.

Gitter channels

We use several gitter channels to have synchronous conversation across projects. If a conversation will likely span multiple hours, or is relevant to many people, consider opening a thread in Discourse or the team-compass repository instead. Here are the relevant Gitters:

• The JupyterHub Gitter is for discussing JupyterHub, Z2JH, TLJH, etc.

• The Binder Gitter is for discussion with Binder users about how to use Binder.

• The mybinder.org-deploy gitter is for discussion around operating myinder.org.

Support bot

To support our efforts in organizing the communication channels and make the transition easier for both developers and users, we have plugged into the repositories of the JupyterHub organization a support bot.

---

Currently, the bot will only check the following repositories:

• binderhub

• jupyterhub

• the-littlest-jupyterhub

---

To trigger the support bot on an issue, add the support label to an issue. The bot will post a short and sweet message to inform the contributor about our communication policy and will then close the issue. This support bot will act each time the support label is added to an issue. Don’t worry if you mistakenly label an issue as support. The action is reversible and removing the label will reopen the issue.

We kindly encourage everybody to use the bot, if during this transition phase, any issues that should be on Discourse, are opened on GitHub.