There is a lot of talk about merging sites, but I can't find anywhere any explanation of this process. I have read the FAQ, and as many of the questions on this topic as I can find, but nowhere can I find definitive answers to these questions.

  • Does merging really exist?
  • How do we trigger a merge?
  • Who can trigger a merge? A Moderator, or does the community have to vote?
  • What happens to all of the Followers, Commiters and Questions of the two merged proposals? Are they all combined, or are some of them lost?
  • If two sites both have more than 50% of the required followers and definition questions, then does the merged site instantly go into commitment?
  • If two sites both have more than 50% of the required committers etc, then does the merged site instantly go into beta?
  • Is all of this in a FAQ somewhere? If not, why not?
  • This looks like a duplicate of discuss.area51.stackexchange.com/q/6062/34267
    – 410 gone
    Aug 29, 2012 at 18:26
  • @EnergyNumbers - That question has some of the content of this question, but this question contains more specific questions. Also, that question was never answered properly. That single answer doesn't address his points or mine, nor do any of the links. Aug 29, 2012 at 20:37

1 Answer 1


The original design was for the Area 51 community to handle these issues through the mechanisms outlined here:

How will the Area 51 discussion proceed?

But Area 51 needs a bit more manual intervention as the process has started to outgrow its original audience. So, while we gear up to replace it with a next-generation Area 51, this is how we implement mergers and other change requests:

So how do change-requests happen?

Shortly after a proposal reaches 45% commitment, that is our cue to consider the specific details of the proposal before moving on towards launch. This is when we consider (and conclude) many of the on-going discussions about scope, naming, and consider if there are other proposals blocking it from going further.

It's actually pretty rare that we physically merge proposals. Thrusting proposal supporters into another proposal doesn't typically end well. We found it better to pick the best proposal with the strongest chance of adoption, and encourage others to support the one proposal to get it launched.

That sometimes means closing other proposals if they are blocking… and possibly expanding or altering the scope of the leading proposal to accommodate the key discussions and ideas raised by the group.

This is why it is really important to continue the discussions inside Area 51 throughout the process and try to reach an unambiguous and clear majority consensus before we have to make these preparations. If the consensus is not clear, we will raise the issues in a proposal discussion. Otherwise, we tend to break things and that makes everyone unhappy.

  • 2
    Thank you for this answer. So merging effectively doesn't exist. The only real option is to grow one proposal to about 45% commitment, and maybe the rivals will get deleted. Aug 29, 2012 at 21:54
  • 2
    @Rocketmagnet That's a distortion of what I said; but sure, if you see on-going discussion, collaboration, and consensus as "rivals" and "deletions", that's fine. The glass is half empty. Aug 30, 2012 at 13:02
  • 1
    Sorry, what I meant was that merging was so rare that it's basically pointless for us to talk about merging two proposals, where at least one is still in definition. Aug 30, 2012 at 13:55
  • 2
    @Rocketmagnet Yikes, but merging is not pointless to discuss. It is very important. It's a community saying "these two communities need to become one." If you are focused on database queries rather than building a site, then you are technically accurate, but that doesn't make it sensible. Aug 30, 2012 at 14:30

You must log in to answer this question.

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