C’Mon Get Meta!
What’s the first rule of Stack Overflow Club?
You don’t talk about Stack Overflow on Stack Overflow.
We have this policy not because we are jerks (or at least, not just because we are jerks) but because we believe meta-discussion kind of gets in the way. As the faq explains:
Also, try to refrain from asking questions about Stack Overflow itself unless you absolutely, positively have to. Most programmers don’t come here to learn about the intricacies of Stack Overflow; they come here to get answers to their programming questions. Let’s try to help them out by not cluttering up the system with navelgazing meta-discussion. If you want to suggest a feature or discuss how Stack Overflow works, visit our UserVoice site.
Despite this rule, the desire for an “official” meta-discussion site has been strong. Lots of community members want to discuss Stack Overflow itself, the community as a whole, how it works, topics on the blog, the website, and so forth. It’s come up many times on UserVoice, and is currently the #3 ranked UserVoice request:
I know this has been declined multiple times, but I really think it’s time to consider the problem of meta-discussions on the site. To understand why something else is needed, let’s look at what doesn’t work:
Meta-questions? Closed moments after they are asked rendering them useless.
Meta-answers? Assuming a question is available to attach to, these questions clutter up the answer stream.
Comments? word and formatting limitations prevent any meaningful discussion.
- Third-party site? Unlikely to be seen by a critical mass of users to be worthwhile.
The current system completely cuts off meta-conversations to the detriment of the SO community.
The desire for meta-discussion is so fervent that some enterprising members of the SO community got sick and tired of waiting for us to listen to them and set up their own meta-discussion site. I applaud this initiative. Good programmers get off their butts!
They have the right idea: create a separate area for meta-discussion. That way, everyone wins: people who are interested in community building can pitch in together, and the vast hordes of programmers who just want some freakin’ answers to their questions don’t have to wade through a lot of extra noise to get there.
That said, the limitations of phpBB (and their ilk) are fairly painful, and felt like stepping back 10 years in time compared to the Stack Overflow engine. So instead of an unofficial, old-and-busted forum, how about an official meta-discussion outlet based on the Stack Overflow engine you’ve come to know and love?
We’re a little unsure how well the current SO engine will map to discussion-y topics. Remember, we designed explicitly around Questions and Answers — specifically, questions around a theme that can be (mostly) answered! Launching our own internal meta-discussion site is one way of finding out.
I’ve made Kyle Cronin and Tom Ritter moderators on the meta.* site, as they already went to such great lengths to create their own community sites around Stack Overflow. I think they’ve earned it.
It’s also looking more and more like meta will replace our UserVoice site, so our adjunct UserVoice moderators, Joel Coehoorn and Sean Massa, will of course be invited to moderate meta.stackoverflow.com as well.
Kyle had some ideas about changes to the SO engine to help it adapt from the Q&A; format discussion:
bounties make little sense on a discussion site
wording needs to be tweaked (i.e. questions->topics, answers->replies)
need to be able to follow questions/get notices of additional replies
remove notion of community wiki, as discussion sites have a stronger sense of ownership, plus nothing will be off-topic
ensure that chronological ordering is the default, if not the only, sort order, both for replies and comments
remove accepting an answer
- some of the close reasons will have to be removed or tweaked
We’ve made a few of the easier changes already that were based on (groan) meta-data. Others will be tougher. We won’t know until we try, so …
C’mon get meta!
… and see what happens.