-
Notifications
You must be signed in to change notification settings - Fork 139
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Proposal: Completely disable "Discussions" within nodejs/node #918
Comments
cc @nodejs/tsc |
In #771, the proposal was to migrate nodejs/help to Discussions, though that has not happened. |
Welp, I believe that said issue should be superseded with this. We can indeed migrate those discussions as issues on nodejs/help, for any open discussion if needed and then disable discussions. |
IMO, |
Have you read my thread at all? 😅🥲 ... I explicitly said that current discussions tab are not used for discussions but help questions (or at least this is my perception of the current usage of it) Having that said, I believe that both GitHub issues + slack are the places where discussions happen today. |
(I updated my prior comment adding some clarifications) |
so, if we want the discussions to be better discoverable within the org, I agree that currently the actual discussions get spread thin all over the place. |
I still don't think you get it or I may be missing your point. Actual discussions right now happen either within issues on nodejs/node or on issues or discussions tab from other repositories for their respective WGs/teams. But never within nodejs/node discussions tab. Hence since we have dedicated places for discussions, and the discussions tab for nodejs/node is not used, it does make sense (imo) to shut it down. |
only discussions pertinent to node/node are scoped under node/node discussions, right? so discussions happening in issues or discussions tab in other repos are fair? either way, I agree with your proposal to shut down the discussions tab. |
Just remember that the discussions tab on nodejs/node is a redirect to the global discussions tab of the entire org. |
I don't think so. They are their own discussions tab, the only difference is they are marked as the default one. That can be disabled too. |
I tried it before posting my comment. They point to the same page. |
Relevant discussion regarding nodejs/help vs "Discussions" #802 (comment) Relevant discussion regarding org discussions vs repo discussions: #679 (comment) |
Yes, but global discussions is not a thing -- you can configure to one of your repositories to be the default "discussions" tab that shows up on your org. |
+1 to disabling discussions. |
+1 to disable, I never found particular value in them |
+1 to disable, I can't really follow any relevant discussions in them. |
+1 to disable discussions |
I believe we got consensus here? Should we proceed then? |
I think there is consensus and we can disable them |
Did someone disable the feature? cc @nodejs/tsc |
|
They can still be disabled if the org-wide feature gets disabled |
It is no mystery that on the Node.js project, we use solely "issues" (within nodejs/node) to propose RFCs, new features, and general discussions surrounding the Node runtime.
Issues are also used for help requests, although people get redirected to nodejs/help for help with Node.js;
The nodejs/node repository has a discussions tab that is rarely used (very few threads are posted). It does feel like a duplication of nodejs/help and isn't being used for what it was intended to be used for.
Let's disable the Discussions tab altogether for "nodejs/node." That said, there are WGs or other projects within the Node.js org that pretty well use discussions, such as nodejs/collaborators, nodejs/nodejs.org, and others.
Although having a "Discussions" tab can be seen as a positive thing, it requires extra moderation; it is often just misused and, at the moment, doesn't bring anything to the table.
The text was updated successfully, but these errors were encountered: