A proposal for JupyterHub communications

[choldgraf]

(also just to +1 what @betatim mentioned, I’ve found that as long as the reply has the tone of “let me suggest a place where you’re more likely to find the help you need” rather than “this is the wrong place to post this”, then people respond OK)

[manics]

https://github.com/jupyterhub/jupyter-server-proxy/ is another repo that receives a lot of usage questions. @betatim would you like to copy your repo2docker issue templates there too?

[betatim]

https://github.com/jupyter/repo2docker/pull/655 is the PR to watch for what we end up with. Once it is merged someone can take the templates and make a PR for the jupyter-server-proxy repo with the tweaks that are needed.

[choldgraf]

(or we can merge them at the org level so it propagates to all of the sub repositories, as long as we’re OK not having repo-specific language in there

[ellisonbg]

I think this sounds good and it a likely model for how we will structure things with JupyterLab as well. Thanks for the thought and effort on this front!

[ondrejj]

Hello all, I can see that you are looking for communication platforms. I have to agree that all three suggestions below are good.

---

However, I see a large issue: that if you have too many platforms of communications it will become very confusing for users to get their head around and use successfully. So, my recommendation is to use a main one.

• Discourse
• (Use it as it is being used know as a Q&A) In addition, you could add more categories to meet the needs or demand. Discourse currently meets criteria of what is wanted: searchable, Archive. It should however, be kept for more General discussion Where as, other communication platforms should be used for more Serious or in-depth running of Jupyter Hub.

---

Why not try something new?

• A proposal, that I make is that you can use is something called Slack you may have already heard of it. But if you haven’t here is a little synopsis:
  

  

• channels

• Team chat | Slack

---

• Search (matches criteria)
• Knowledge sharing | Slack

---

• Integrations
• Add apps to Slack | Apps and integrations | Slack App Directory

---

• Security
• Security at Slack | Slack

---

So, with it matching some criteria it could perhaps be successful in the future
With

• Searchable history
• Made for teams
• Looks cool and organised!

---

So, I hope that I have given an insight, into something new to introduce in the future. Please PM me for information. All the best Thanks for reading this (its long (ish) )

@choldgraf

• Gitter is a great medium for fluid conversation, though it isn’t easily searchable/archivable/discoverable and so we’d like to keep content-full discussion in either GitHub or Discourse. Once conversations on Gitter start to become non-trivial (e.g. will take some thinking to resolve), we recommend that people open a thread on Discourse, or that they open an issue on a relevant GitHub repository if it’s directly related to a particular repository. The goal is that Gitter has unstructured and fluid conversation that leads to more in-depth conversations in the proper Discourse/GitHub channel .
• Discourse is a structured and community-focused platform for discussion. It is both discoverable and searchable, and can serve as a resource for past and present conversations around JupyterHub. We’d like all conversations that don’t directly pertain to the underlying codebase of a repository to happen in the Discourse page. This includes “how do I deploy?” questions, “best practices” questions, general discussions about enhancements, etc. The goal is that Discourse conversations result in actionable and specific issues in the repository.
• The Blog / Twitter are both great ways to make a one-way connection with the outside community. They can amplify our voice, but at the cost of making it harder to have in-depth two-way communication. We use the blog and twitter for large announcements, and recommend that people go to the Discourse to engage in discussion around those announcements. As a general rule, anything that we broadcast widely via these mediums will also have a corresponding place to talk about it on the Discourse.