Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 157 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

When the SproutCore 2.0 project was renamed to Ember.js, it abandoned its old mailing list and started directing all questions to Stack Overflow.

In principle, this is not bad at all. It increases the popularity of Stack Overflow and keeps the active users of the framework from answering the same questions over and over again. It also clearly encourages a lot of new users to post very specific problems to Stack Overflow.

As an active SO user, I'm happy to help others with their questions, but since there is no mailing list at all, the tag gets flooded with a lot of one-time questions and problems which do not really fit our Q&A format (e.g. Requesting advice for "visually" filter a collection in ember.js and Rake-Pipeline cache_buster and a minifier?). It's annoying for existing users to have to flag, edit, comment on or vote to close these posts all the time when they just want to answer good questions.

What should we do when projects — not just Ember.js — rely on Stack Overflow as their only user support? How should "one-time questions" be handled?

share|improve this question
I don't consider this a duplicate of… since this project does not own a mailing list. – Steffen Jan 2 '12 at 17:11
I've seen "just use SO for support" several times in the past few days. Whether or not it's a good idea, I don't think this particular genie is going back in its bottle. The example I remember at the moment is Google Guava: "To get help on a specific question or problem, use Stack Overflow. We monitor these questions using this RSS feed.)" – Pops Jan 2 '12 at 22:02

We should handle questions for various technologies the same; regardless of whether the organization provides direct support, or refers users to SO. Supporting a technology is not the SO community's job.

If the questions don't meet SO's guidelines for good questions (too localized, too vague, a rant or open discussion), then we should vote to close for appropriate reasons.

share|improve this answer

Well, if it's a good idea for (fingers down throat) Facebook, I suppose we'll all survive emberjs.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .