I run several popular open-source projects myself, with their current support forums ranging from none, github issues, and google groups. All of these are failing for one reason or the other, and the community at large is requesting moving to Stackoverflow for tag-based support to solve the issues we're facing.
Perhap's Jeff's distain could be phrased a bit better, as I'm unsure how the following is abusive:
- questions and answers / support: stackoverflow
- discussions: google group
- dev tasks: github issues
- chat: irc
As this is exactly how stackoverflow is used presently for anything that is open-source or provides a public API. I've got question and need an answer. The only difference, is that the project owners would then endorse such actions. Shopify has jumped onboard and done this and seen great results.
It seems the benefits are quite clear:
- answers by a huge active community dedicated to helping each other
versus:
- answers in a closed small community who may not even be around to check
So I really don't understand any destain for this, as it seems great on all fronts...
Update: Klement posted a comment on the question indicating that Joel Spolsky seems to agree with the use case of using stackoverflow as a support channel for projects.
Update 2: Seems Jeff has a more concise opinion about this here:
Provided that …
vendor has some tangible evidence to support the idea that this
question gets asked by real users, and isn't just them imagineering
"important" questions about their "important" product into the world
vendor is not using Stack Overflow as their primary method of support
Then it is OK.
and after reading all the trello meta complaints, it seems that as long as you make it clear that stackexchange is a community driven and generic, it is okay. If you imply that stackexchange is our dedicated support forum for any type of question, that is bad.