Nest: Too much questions about how to use the framework.

[MonsieurMan]

I think there are way too much issues about this.
We could redirect to stack overflow and / or the gitter which are IMO more suited to it. It would help keeping the issues clean for features requests, bugs and discussion about the framework itself.

This could be enforced via an ISSUE_TEMPLATE.md for redirecting users to other places.

[calligraphic]

I agree. I've subscribed to notifications in my email inbox for the project the past month, since I'm considering using it in an upcoming project. I was surprised at the volume.

[adrien2p]

Yes i watch also the project, But in all issues opened i can see than a lot of them are redundant and the same question come back like how to inject in global something or in that so maybe if we look dinstinctly they are not to much questions

[MonsieurMan]

@adrien2p redundancy is also a place where SO does better than issues, there is a 'native' duplicate marker. And also when writing the title and the content of the question people will be showed with suggestion of previously asked questions.

[chanlito]

moving question to stackoverflow isn't that bright idea either.

[MonsieurMan]

@BruceHem, could you please elaborate and be a little bit more constructive ? You make no point if you don't give any argument.
The only downside I could see to it is people fearing the SO community, but with a nestjs tag they will simply pass away and not taking care of downvoting. _I wish so hard downvotes would require a reason to be applied..._

[shekohex]

What about making a new repo nestjs/discussion for discussion and help or anything else related to solving problem or How to questions ?

[cojack]

I totally agree to move questions about installation/development process to SO. Issues will be much clear with ISSUE_TEMPLATE.

@shekohex there is already Gitter for that

[wbhob]

I've created PR #246 to start a form of issue template. Looking for reviewers 😄

[MonsieurMan]

@wbhob, I see you went the SO way too, as I said in my review, we should ask users to use the nestjs tag and on the other hand we should subscribe to the tag so we can be as reponsive as we are with issue.

edit: I just saw that we need at least 1500 rep on SO to create a new tag... Does anybody have them or I am going to have to farm JS noob questions ?

[wbhob]

Hehe I have ~300 points right now. We can try though!

[adrien2p]

I need to start ro do some points too ^^

[MickL]

Imho its a good practice to answer as many questions as possible even on GitHub which should handle bugs/feature requests while StackOverflow is meant to answer questions. Anyway i think its good for a new project to help people as much as possible because exactly this persons will gain experience, come back later and answer others questions. Or they write articles about things they struggled with. Or recommend the framework to other developers because they have so much joy using it. (We all know getting stuck somewhere is sooo frustrating)

I have seen this on another new project a few years ago(Drupal Commerce). There was a contributor (@rszrama) answering questions within the issue tracker within hours. I was so happy about this and kept going and going.

I would tolerate support requests on GitHub until the community has grown(up to 10-20k stars?).

[wbhob]

I’d say 4K stars, were already getting 3 issues a day with just questions, and that can get tedious

[calligraphic]

@MonsieurMan The project owner could email SO's moderation team and request a nestjs tag added, probably with good results ([email protected]). It's a legitimate exception to the reason why SO requires 1500 rep to create new tags.

@MickL I understand, but I still think it's a bad idea to use project issues for general questions:

• It makes it difficult for developers to look at the project and get a quick feel for the status of the project when the number of open issues isn't related at all to _actual_ issues.

• It reduces the usefulness of issue tags in the Github repository, because all of the general questions stay untagged so people have to dig through them to see what they are. As an aside, it'd be nice to have a tag directed at people's first few commits to a project in general, like "easy" or something.

• There's a marketing aspect to making use of SO for questions. A lot of people there work to gain reputation - employers consider it in new hires. So building a foundation over there helps get the word out, as people who are following "javascript" and "node" tags look at the "nestjs" questions and try to answer it for gamification purposes.

• Pushing questions to SO helps with SEO on those questions. When you open and discuss a question in a project issue, the nature of the conversation is pretty free flow and disorganized. People put more time into SO questions and answers because of the gamification and concern about their rep, which in turn gives better search results in the future when people look for an answer to a question.

• Response on SO questions is often really fast, as a lot of people are subscribed to javascript and node tags. Much faster than what a repository issue queue can likely provide.

• SO has better tooling for ranking answers if it's subjective. It's hard to read through a long issue conversation and get a sense for what conclusion people are agreeing is the best way forward when it's not clear cut. Smileys help a little, but nothing like upvoting / downvoting answers.

As far as encouraging framework users to generate content like Medium articles and blog posts about their experiences, I think there's better ways to approach that. Definitely making sure they get the help they need is part of it. But using the Github wiki, and linking to a resources wiki page from the root README and listing all articles out there, and encouraging people to go star the article of something, is probably more effective.

My $0.02.

[NoNameProvided]

@MonsieurMan The project owner could email SO's moderation team and request a nestjs tag added, probably with good results

It's better to ask on https://meta.stackoverflow.com

[NoNameProvided]

Uhm, I just realized I have more than 1500 point 😄 , will create the tag for you guys. What should be the name? nestjs or nest-js or anything else? Btw there is only 2 question mentioning nestjs now on StackOverflow, so it should be mentioned at least in the docs.

[adrien2p]

I think will continue to answer both anyway ^^ but github is more about question related to the framework and SO more about problem during the usage of the framework. What do you think ? But certainty we will have both with same questions but it’s not a problem

[MickL]

Personally i would call it nest since its not really JavaScript. Angular also dropped the „js“.

The contributors may look at SO as much as possible then. I felt like the guy from Drupal Commerce was giving support as a fulltime job. And it really made the difference on success.

Probably there will be alot, or mostly, questions not related to Nest but to TypeScript, Node.js and Angular which should be answered patiently anyway. Every question could also get back into the documentation.

[NoNameProvided]

Personally i would call it nest since its not really JavaScript.

Sadly, nest has been taken already.

[wbhob]

You'd have to talk to (convince 😄) @kamilmysliwiec. I've discussed migrating to @nest/*, but that could cause issues for older codebases. I've mentally constructed a tentative plan for coordinating this type of shift:

1. Close/merge all outstanding PRs and temporarily block them for the shift
2. Move common into core and refactor index.ts files accordingly.
3. Rename package names to @nest/*
4. Publish new versions as 5.x.x
5. Provide instructions for existing forks to rebase their changes against the new setup
6. Reopen Pull Request feature
7. Profit 💰

[wbhob]

Also @NoNameProvided someone would reach out to NPM and see if the organization name is actually in use. It's entirely possible that it is not and we could take it from whoever is squatting on it.

[kamilmysliwiec]

Hi everyone,
The @wbhob PR with the ISSUE_TEMPLATE.md is merged already. 🙂 @NoNameProvided would be great to have a nestjs tag. 🎉

[NoNameProvided]

@kamilmysliwiec It has been created: https://stackoverflow.com/questions/tagged/nestjs

[kamilmysliwiec]

Great 🎉 Thanks @NoNameProvided 🙂

[wbhob]

Yipee!

[MonsieurMan]

Subscribed to it!

[wbhob]

I realized the message I sent a few days is completely irrelevant, I misread the thread. Sorry folks!

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.