Sunset the GitHub repo jupyter/help?

Meta
1

Should we sunset the https://github.com/jupyter/help forum by writing it very clearly in the current README, and perhaps in an issue template, that we want all questions to go to Discourse instead?

It is my understanding that this repo attracts questions that most Jupyter members are unaware of. I guess based on some experience that we will get more interactions if they are written in Discourse as most of those that hold Jupyter dear and near is encouraged to hang out here.

5 Likes
2

I think it’s a great idea (partially because that repository is actively misleading people into thinking they’ll get help there).

Things to do:

  • Prevent new issues from being created there.
  • Put a big warning in the README of the document saying that the repository is deprecated and pointing to Q&A in the Discourse
  • Make sure all of our links don’t point to this help repo anymore

Optionally:

  • Write a bot to make a one-time post to all of the unanswered issues in there saying “we’re so sorry, if you still have a question, please post it to << discourse link >>”
1 Like
3

@choldgraf I’ll do the Things to do by the end of the week, allowing a few days of consideration first.

Ping @parente as I recall you brought up this for discussion initially.

2 Likes
4

Please do. We’ll need to update some of the project readmes as well at some point too.

Let’s do this:

2 Likes
5

@willingc - we recently opened up a top-level Q&A channel that is meant to be a single landing spot for user questions (and that we can add metadata/categorize/move later if need be). Would that work for your suggestion to create a specific category for support?

2 Likes
6

Note the option to archive a github repository. It might be appropriate here.

3 Likes
7

I’d +1 on the archive thing.

1 Like
8

Just apply final changes (links to here) before that. Yep, stating the obvious…

1 Like
9

I can archive the repo if we’re ready to make it permanently read-only. Any last requests?

I see @willingc has updated the jupyter/help README with a note pointing here. (Thanks, Carol.) I see the Jupyter website does have at least one reference to the jupyter/help GitHub repo. I’ll search it thoroughly and send a PR soon.

10

Hm. I just spotted that the website links to https://github.com/jupyter/help/blob/abdb7637cac0d55f2403f47c250cd86e5d3cff60/CONTRIBUTING.md which is a general guide for folks wanting to get involved in the community. We should find another place for that document to live before it becomes part of the archived repo.

Maybe a pinned post in meta here on discourse? A page on the website itself?

11

Maybe a :bangbang: to get people to read that sentence. Bold isn’t enough. :wink:

1 Like
12

I think it makes sense to move it here as a pinned post/wiki for community.

13

I just remembered that we have something like this also at jupyter.readthedocs.io…what if we moved the contributing guide there? (actually, it’d probably be merged since there is some contributing docs in this website as well)

I opened up Refactor and update the jupyter meta-docs - #2 by jhermann with a suggested path forward there, would love to hear what the community thinks!

14

I’ve gone ahead and archived the repo as suggested by @vidartf and @psychemedia. It is now read-only.

3 Likes
15

Did we add the extension for marking a topic as resolved yet? :smile:

1 Like
16

It was installed, but it had to be activated on a category by category level. I decided to let it be made available on all categories for now. Sounds ok? I think it is only the author of the topic that can select a solution as well btw.

1 Like
17

This is older - but +1 on this :wink:

1 Like