Proposal: Korean Language

Our proposal finally completed it's commitment phase and is now going into private beta

I would like to thank everyone who supported the proposal, and congratulate the community for passing the commitment phase

This is a good first step but we are not quite there yet

I would like to point out that if the site does not get enough activities during the private beta ( not sure exactly how long the private beta is), the site can still get shut down

So I urge all the members of the community to show the same interest and enthusiasm that we showed during the commitment phase, and help get this site to public beta, and ultimately get it fully launched

Please ask and answer as many questions as you can, as well as take part in other community activities, such as voting, editing and meta discussions

commitment phase에는 한국어 모국인의 관심도 많이 봤습니다. 우리 공도체의 성공을 위하여 모국이과 한국어 전문자들의 참여도 필수인데, commitment phase에처럼 앞으로 도 많은 참석부탁드립니다.

I hope everybody has fun participating in this community and we can make it a useful place for learning and finding information on Korean Language and Culture

  • also relevant to our site: discuss.area51.stackexchange.com/questions/10324/…
    – user17915
    May 24, 2016 at 13:36
  • Thanks. I am very excited by the new site. Is there any precise metrics (number of questions, votes, visits,...) to measure if the beta is a success or not?
    – Taladris
    May 24, 2016 at 14:14
  • I am not sure about that, I'm sure there is but I don't know where exactly to find it; maybe th beta pages of other proposals can give some idea
    – user17915
    May 24, 2016 at 14:17
  • 1
    For example, this one: area51.stackexchange.com/proposals/87978/deep-web
    – user17915
    May 24, 2016 at 14:17
  • this gives some idea on what the numbers of a successful beta should look like
    – user17915
    May 24, 2016 at 14:18
  • Any idea when the private beta will actually launch? May 24, 2016 at 15:31
  • 2
    "Site Launch — When a proposal hits 100% commitment, we do a final sanity check before we submit the site for launch into the private beta. Barring any technical or scheduling conflicts, private betas generally start 1-2 weeks after completion on either Tuesday or Wednesday. Anyone committed to the proposal will receive notification via email."
    – user17915
    May 24, 2016 at 15:40
  • 1
    From here: meta.stackexchange.com/a/200383/221878
    – user17915
    May 24, 2016 at 15:40

2 Answers 2


Here is the information given on the site of Deep Web, that precedes our site of a few days in Private Beta. This gives some indications on what we have to do to make our Beta successful:

  1. 10 questions per day on average is a healthy beta, 5 questions or fewer per day needs some work. A healthy site generates lots of good content to make sure users keep coming back.
  2. 90% answered is a healthy beta, 80% answered needs some work. In the beta it's especially important that when new visitors ask questions they usually get a good answer.
  3. Every site needs a solid group of core users to assist in moderating the site. We recommend: 150 users with 200+ rep, 10 users with 2,000+ rep, 5 users with 3,000+ rep.
  4. 2.5 answers per question is good, only 1 answer per question needs some work. On a healthy site, questions receive multiple answers and the best answer is voted to the top.
  5. 1,500 visits per day is good, 500 visits per day needs some work. A great site benefits people outside the community. Eventually, 90% of a site's traffic should come from search engines.

Note: thanks to @user13267 for the link.

  • 5
    Note that there's some flexibility here: the visits per day and high-rep users numbers are expected of a mature site, not one in early beta, while the expected number of answers per question depends on the nature of the site -- Law is graduating with 1.5 answers per question, while Worldbuilding had 4.7. For private beta, concentrate on building up a collection of good questions with high-quality answers.
    – Mark
    May 25, 2016 at 1:41

One of the purposes of the private beta is to 'seed' the site with representative content before the public beta.

I was going to suggest that everyone consider asking 'their' questions from the Definition phase within the first couple of days of the launch - if any good ones are missed, one we can pick those up.

You must log in to answer this question.

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