12

Let's say there's a site that I'd like to see graduate into a full SE site (I'm not going to mention Code Golf here). Now, I'm aware that the answer to "when will we graduate" is "when you're ready."

However, what if I have the question "what do we need to do to graduate?" What if I think we're ready to graduate, and I want to know why we're not? What is the process for asking that?

  • Do I ask on its per-site meta? If I do this, I'm not sure it will get the attention by the Official SE Graduation Committee of Officialness™.

  • Ask on meta.SO (meta.SE soon)? This doesn't seem right either though, since it's site-specific.

  • Something else?

2
  • I think the problem is that if the community consciously does something to "meet the requirements" for graduation it will not be self-sustaining once it graduates and the community goes back to being itself.
    – Mysticial
    Commented Feb 26, 2014 at 23:49
  • @Mysticial Well, in this specific case I actually think we're quite ready to graduate, and I want to know why we're not ready, but I tried to make the question more general. Of course, this would only apply once the community thinks graduation is near or they are ready. Edited post to be clearer
    – Doorknob
    Commented Feb 26, 2014 at 23:51

1 Answer 1

10

Do I ask on its per-site meta? If I do this, I'm not sure it will get the attention by the Official SE Graduation Comittee of Officialness™.

This is it. The community team monitors all per-site metas and will respond as needed. In theory, you could also email the team via the "contact us" link at the bottom of any page on your site, but it's best to have this sort of discussion in public where it can benefit everybody.

That said... in most cases, there isn't a clearly defined set of steps. There are no hard numbers that, if you hit them, will guarantee graduation. We constantly monitor various site metrics and pay attention to the periodic site evaluations that happen via the Site Evaluation review queue. In many cases, graduation is a "we know it when we see it" (where "it" is a healthy, self-sustaining, active site) kind of deal.

There are a couple blog posts that touch on this as well:

7
  • Alright, thanks. So, if I posted on a per-site meta and then emailed the team with that post, that would work? (I'm really not expecting the team to relentlessly patrol every single per-site meta, so I'm kind of uncertain that they'll notice the post.)
    – Doorknob
    Commented Feb 26, 2014 at 23:57
  • @Doorknob This kind of request is what I'd call "important but not urgent", so give them some time. Maybe a few days. Otherwise you're just going to come across as impatient. The team is pretty on-the-ball when it comes to checking up on metas, in my experience.
    – Adam Lear StaffMod
    Commented Feb 26, 2014 at 23:58
  • 2
    @Doorknob: My daily schedule includes: patrol a bunch of per-site metas. Commented Feb 26, 2014 at 23:58
  • @Jon: Lol, okay, thanks. Anna: Alright, I shall post on the per-site meta soon (when I have more time).
    – Doorknob
    Commented Feb 27, 2014 at 0:01
  • 2
    @LowerClassOverflowian There isn't really a well-defined right-or-wrong there.
    – Adam Lear StaffMod
    Commented Feb 27, 2014 at 0:23
  • Is there any specific tag we should use when requesting feedback?
    – Troyen
    Commented Mar 5, 2014 at 0:53
  • @Troyen There's no specific tag, no. I'll ping someone on the comm team to take a look.
    – Adam Lear StaffMod
    Commented Mar 5, 2014 at 16:46

Not the answer you're looking for? Browse other questions tagged .
https://meta.stackexchange.com/questions/223281/is-there-any-way-to-request-official-feedback-on-what-to-do-in-order-to-graduate
meta.stackexchange.com
CC-MAIN-2024-38
122929
application/http; msgtype=response
sha1:YNNEK7YB4GYGOWWMQG7DLQCHKHWDNSLW
<urn:uuid:2bc11633-6259-4e4d-81ed-236148ce8cb0>
2024-09-13T21:27:47Z
104.18.43.226
text/html
sha1:SC6VFNZNPCPPO6VIBAFSEACAWCUNTN6H
<urn:uuid:77b879a3-a461-48a8-a6f8-9c99ef0ee436>
https://meta.stackexchange.com/questions/223281/is-there-any-way-to-request-official-feedback-on-what-to-do-in-order-to-graduate
response
<urn:uuid:27384969-63cc-4b2c-be79-d12f1b1444dd>
isPartOf: CC-MAIN-2024-38
publisher: Common Crawl
description: Wide crawl of the web for September 2024
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-192
software: Apache Nutch 1.20 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.5-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/