Please add "Discussions"
See original GitHub issue- Discord Community Chat: https://discord.gg/G7Qnnhy
- StackOverflow: https://stackoverflow.com/questions/tagged/nestjs using the tag
nestjs
- Twitter: If it’s just a quick question you can ping our Twitter: https://twitter.com/nestframework
Hi @kamilmysliwiec I have seen a lot of question topics that mainly are closed and people are referred to use discord, the issue is, the knowledge generated in discord is not searchable, another dev might have same question and discord support team needs to answer same question over and over.
Today I wanted to send a question on another repo and they had solved this issue pretty good. if you click on “Question and help” on this link, it takes you to Discussions, which is pretty good, and are not mixed with bug reports.
It would be great idea to enable this feature.
What do you think?
Issue Analytics
- State:
- Created 2 years ago
- Reactions:11
- Comments:7 (3 by maintainers)
Top Results From Across the Web
please add me in discussion or please include ... - TextRanch
please add me in discussion is the most popular phrase on the web. More popular! please add me in discussion. 648,000,000 results on...
Read more >How do I enable Discussions on a repo? #24 - GitHub
Could you please enable discussions for the public repo arithmetric/aws-lambda-ses- ... Can you please add this repo under the beta program?
Read more >How to Write Discussions and Conclusions - PLOS
A successful discussion section puts your findings in context. It should include: the results of your research,; a discussion of related ...
Read more >How to add to discussion forum - YouTube
Your browser can't play this video. Learn more. Switch camera.
Read more >Connect with your community with GitHub Discussions
GitHub Discussions is out of beta presented by ... as: ✔️ Connect with your community ✔️ Use categories ✔️ Add labels and more!...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
We’ve floated the idea of discussions a few times with other members of the team. I think the eventual goal is to have both Discord and Discussions as an option. The difficult part there is how do we decide what needs to be a discussion, what needs to be a Discord conversation, and how do we make users aware of both possibilities.
Personally, I’m all for discussions, I’m using them for some of my other open source libraries and love how they function. I think the searchability will bring a lot of value for those looking for answers.
I’ll admit, I end up answering the same question a lot, not matter how clearly we think the docs state it. Someone, somehow, always misinterprets the writing and the examples.
The biggest pain point, I think is what Reza brought up, searchability. Not being able to search for past issues and seeing the result of the conversation. The second biggest issue, in my opinion, is blaming the framework for an issue when it’s really the underlying library that is a problem.
Personally, I’ve loved using Discord for support, it’s quick and easy, the formatting support is great, and now that threads are added the main chats stay a lot cleaner, which is really nice. But in the end, the answers aren’t searchable. I think the use of Discord is great when it comes to discussions about how to implement advanced functionality and bouncing ideas off of other devs, but I do see the draw of using GitHub Discussions for Knowledge Sharing.