(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)
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?
1 Like
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.
(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
1 Like
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!
1 Like