New Per-Site Metas

by Jeff Atwood

on July 22, 2010

If you've been following our new Stack Exchange 2.0 private and public betas, you may have noticed that every new website launches with its own dedicated meta site.

If we've learned anything (and I personally had to learn this lesson by having it beaten into me), it is that meta-discussion is an absolutely integral part of any healthy community. So much so, that I question whether any community without a meta site can actually survive in the wild. It's certainly not a mistake we're ever going to repeat again.

We tried to make these new per-site metas fairly discoverable with both a site wide notification banner of the form ...

got a question about the site itself? meta.topic is the place to talk about things like what questions are appropriate, what tags we should use, etc.

... and a prominently featured link to switch between the site and the meta site at the top left of both.

(update: we've changed the layout a bit. The links to meta and parent are still at the top, but shifted over to the right as plain text links -- the stackexchange navigation takes its place on the left. And the link to meta is now in the sidebar like so, with the top weekly meta questions -- or meta questions with the special moderator-only "featured" tag.)

Click that "meta" link at the top left to go to meta (shocking, I know), and click "parent" in the same location to get back to the parent site.

However, you should know that these per-site (or "child") metas behave significantly differently than what you might be used to on meta.stackoverflow.com, if you participated there. Based on our existing experience with Meta Stack Overflow, we tried to improve and simplify in a few ways:

  1. You never have to log in to the per-site meta. It grabs the cookie from the parent site and already "knows" who you are when you visit.

  2. Identity is always inherited from the parent site. If you have an account on the parent site, you automatically have an account on the per-site meta. Your profile can only be edited on the parent site. And of course, moderators on the parent are moderators on the per-site meta.

  3. Reputation is always inherited from the parent site. You cannot gain or lose reputation* on the per-site meta. This also means that some reputation related functions like the rep graph and bounties are not enabled on the per-site meta.

  4. You must have a minimum of 5 rep on the parent site to participate on the per-site meta. In general, the more reputation you have on the parent site, the more stake you should have in its governance. And the converse is also true: if you have no reputation on the parent site (as in 1 rep, the minimum), you haven't even come of age to "vote" in governance issues, so to speak. We also expect that most established users will have the +100 network account association bonus, so they won't be affected.

  5. Voting up or down does not affect reputation. You are now free to vote purely based on post content, without worrying about how your vote might positively or negatively affect someone's reputation score.

  • however, there is one exception: extreme misbehavior on the meta site will affect your parent site reputation. And not in, shall we say, the "good" way.

In fact, we're so happy with the way these per-site metas are working on the Stack Exchange 2.0 sites, we're extending the per-site metas to Super User and Server Fault as of right now! [

meta.superuser.com

](http://meta.superuser.com)

[

meta.serverfault.com

](http://meta.serverfault.com)

For now we are leaving meta.stackoverflow.com grandfathered in, as-is, with no changes; it's still a standalone community with a standalone reputation system. We think Stack Overflow is large enough to justify this, and it just so happens that Stack Overflow is also the name of the company, too. Meta Stack Overflow will serve as the "National Capital" where we process feedback not just for Stack Overflow but for the core engine itself -- while the smaller meta sites are akin to regional or state capitals. So, in a nutshell:

  • meta.stackoverflow.com is Washington, DC

  • meta.serverfault.com is Columbus, OH

  • meta.superuser.com is Sacramento, CA

  • meta.cooking.stackexchange.com is Atlanta, GA

  • meta.gadgets.stackexchange.com is Denver, CO

  • meta.webmasters.stackexchange.com is Boston, MA

... and so forth.

But it is the exception. The per-site meta is a standard fixture of our network now, because it's how you, as a community, will own the design and governance of your site.