Skip to main content
Meta Stack Exchange

Return to Answer

replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
Source Link
Community Bot
Community Bot
  • 1

Some clarification:

This is only one step in a very long process of figuring out what it means to be what kind of site on the SE network.

We had the concept of a strict graduation for many years. You were a beta site until something mysterious happened and we descended from on high to tell you that you got to be a graduated site and then you waited around for your design and once that happened you got your election and other stuff and that was just how it worked. For years. We didn't touch the process. It chugged along and it more or less worked for a while.

But it didn't scale, and it ran into problems. A backlog built up because our network of communities is growing way faster than our design teamour design team is growing. So instead of hiring a few more contract designers to get the backlog cleared - which probably wouldn't actually work, and even if it did, would just be kicking the can down the road a few years until the scale problem reared its head again - we decided to take a step back and actually examine the concept of graduation for the first time since its inception and see what was working and what wasn't.

What we've done so far:

What we could possibly (NO PROMISES) do in the future, now that we've dismissed the notion that graduation is a single event:

  • Decouple the graduation treatment even further by defining thresholds at which each change is made (you get migration paths at X migrations/month, you get elections at Y% of the community being eligible to vote, etc)
  • Move the privileges changes into Phase 1 instead of Phase 2
  • Deprecate the terms "graduation" and "beta" and be smarter about the vocabulary we use to describe site states
  • Allow communities to choose features they want from sets of things they've become eligible for

I'm not saying we will do all or any of those things. I am saying that they're all possible because we've opened the door to discussions about what it means to graduate. This is an opportunity for all of us to figure out what comes next.

So: assume that for the next few months, graduation functions the way Ana describes above. What are the next changes you'd like to see? Write it up and let's hash it out on meta like we would with any other .

Some clarification:

This is only one step in a very long process of figuring out what it means to be what kind of site on the SE network.

We had the concept of a strict graduation for many years. You were a beta site until something mysterious happened and we descended from on high to tell you that you got to be a graduated site and then you waited around for your design and once that happened you got your election and other stuff and that was just how it worked. For years. We didn't touch the process. It chugged along and it more or less worked for a while.

But it didn't scale, and it ran into problems. A backlog built up because our network of communities is growing way faster than our design team is growing. So instead of hiring a few more contract designers to get the backlog cleared - which probably wouldn't actually work, and even if it did, would just be kicking the can down the road a few years until the scale problem reared its head again - we decided to take a step back and actually examine the concept of graduation for the first time since its inception and see what was working and what wasn't.

What we've done so far:

What we could possibly (NO PROMISES) do in the future, now that we've dismissed the notion that graduation is a single event:

  • Decouple the graduation treatment even further by defining thresholds at which each change is made (you get migration paths at X migrations/month, you get elections at Y% of the community being eligible to vote, etc)
  • Move the privileges changes into Phase 1 instead of Phase 2
  • Deprecate the terms "graduation" and "beta" and be smarter about the vocabulary we use to describe site states
  • Allow communities to choose features they want from sets of things they've become eligible for

I'm not saying we will do all or any of those things. I am saying that they're all possible because we've opened the door to discussions about what it means to graduate. This is an opportunity for all of us to figure out what comes next.

So: assume that for the next few months, graduation functions the way Ana describes above. What are the next changes you'd like to see? Write it up and let's hash it out on meta like we would with any other .

Some clarification:

This is only one step in a very long process of figuring out what it means to be what kind of site on the SE network.

We had the concept of a strict graduation for many years. You were a beta site until something mysterious happened and we descended from on high to tell you that you got to be a graduated site and then you waited around for your design and once that happened you got your election and other stuff and that was just how it worked. For years. We didn't touch the process. It chugged along and it more or less worked for a while.

But it didn't scale, and it ran into problems. A backlog built up because our network of communities is growing way faster than our design team is growing. So instead of hiring a few more contract designers to get the backlog cleared - which probably wouldn't actually work, and even if it did, would just be kicking the can down the road a few years until the scale problem reared its head again - we decided to take a step back and actually examine the concept of graduation for the first time since its inception and see what was working and what wasn't.

What we've done so far:

What we could possibly (NO PROMISES) do in the future, now that we've dismissed the notion that graduation is a single event:

  • Decouple the graduation treatment even further by defining thresholds at which each change is made (you get migration paths at X migrations/month, you get elections at Y% of the community being eligible to vote, etc)
  • Move the privileges changes into Phase 1 instead of Phase 2
  • Deprecate the terms "graduation" and "beta" and be smarter about the vocabulary we use to describe site states
  • Allow communities to choose features they want from sets of things they've become eligible for

I'm not saying we will do all or any of those things. I am saying that they're all possible because we've opened the door to discussions about what it means to graduate. This is an opportunity for all of us to figure out what comes next.

So: assume that for the next few months, graduation functions the way Ana describes above. What are the next changes you'd like to see? Write it up and let's hash it out on meta like we would with any other .

added 165 characters in body
Source Link
hairboat
hairboat
  • 15.2k
  • 7
  • 57
  • 89

Some clarification:

This is only one step in a very long process of figuring out what it means to be what kind of site on the SE network.

We had the concept of a strict graduation for many years. You were a beta site until something mysterious happened and we descended from on high to tell you that you got to be a graduated site and then you waited around for your design and once that happened you got your election and other stuff and that was just how it worked. For years. We didn't touch the process. It chugged along and it more or less worked for a while.

But it didn't scale, and it ran into problems. A backlog built up because our network of communities is growing way faster than our design team is growing. So instead of hiring a few more contract designers to get the backlog cleared - which probably wouldn't actually work, and even if it did, would just be kicking the can down the road a few years until the scale problem reared its head again - we decided to take a step back and actually examine the concept of graduation for the first time since its inception and see what was working and what wasn't.

What we've done so far:

What we could possibly (NO PROMISES) do in the future, now that we've dismissed the notion that graduation is a single event:

  • Decouple the graduation treatment even further by defining thresholds at which each change is made (you get migration paths at X migrations/month, you get elections at Y% of the community being eligible to vote, etc)
  • Move the privileges changes into Phase 1 instead of Phase 2
  • Deprecate the terms "graduation" and "beta" and be smarter about the vocabulary we use to describe site states
  • Allow communities to choose features they want from sets of things they've become eligible for

I'm not saying we will do all or any of those things. I am saying that they're all possible because we've opened the door to discussions about what it means to graduate. This is an opportunity for all of us to figure out what comes next.

So: assume that for the next few months, graduation functions the way Ana describes above. What are the next changes you'd like to see? Write it up and let's hash it out on meta like we would with any other .

Some clarification:

This is only one step in a very long process of figuring out what it means to be what kind of site on the SE network.

We had the concept of a strict graduation for many years. You were a beta site until something mysterious happened and we descended from on high to tell you that you got to be a graduated site and then you waited around for your design and once that happened you got your election and other stuff and that was just how it worked. For years. We didn't touch the process. It chugged along and it more or less worked for a while.

But it didn't scale, and it ran into problems. A backlog built up because our network of communities is growing way faster than our design team is growing. So instead of hiring a few more contract designers to get the backlog cleared - which probably wouldn't actually work, and even if it did, would just be kicking the can down the road a few years until the scale problem reared its head again - we decided to take a step back and actually examine the concept of graduation for the first time since its inception and see what was working and what wasn't.

What we've done so far:

What we could possibly (NO PROMISES) do in the future, now that we've dismissed the notion that graduation is a single event:

  • Decouple the graduation treatment even further by defining thresholds at which each change is made (you get migration paths at X migrations/month, you get elections at Y% of the community being eligible to vote, etc)
  • Move the privileges changes into Phase 1 instead of Phase 2
  • Deprecate the terms "graduation" and "beta" and be smarter about the vocabulary we use to describe site states
  • Allow communities to choose features they want from sets of things they've become eligible for

I'm not saying we will do all or any of those things. I am saying that they're all possible because we've opened the door to discussions about what it means to graduate. This is an opportunity for all of us to figure out what comes next.

So: assume that for the next few months, graduation functions the way Ana describes above. What are the next changes you'd like to see? Write it up and let's hash it out on meta like we would with any other .

Some clarification:

This is only one step in a very long process of figuring out what it means to be what kind of site on the SE network.

We had the concept of a strict graduation for many years. You were a beta site until something mysterious happened and we descended from on high to tell you that you got to be a graduated site and then you waited around for your design and once that happened you got your election and other stuff and that was just how it worked. For years. We didn't touch the process. It chugged along and it more or less worked for a while.

But it didn't scale, and it ran into problems. A backlog built up because our network of communities is growing way faster than our design team is growing. So instead of hiring a few more contract designers to get the backlog cleared - which probably wouldn't actually work, and even if it did, would just be kicking the can down the road a few years until the scale problem reared its head again - we decided to take a step back and actually examine the concept of graduation for the first time since its inception and see what was working and what wasn't.

What we've done so far:

What we could possibly (NO PROMISES) do in the future, now that we've dismissed the notion that graduation is a single event:

  • Decouple the graduation treatment even further by defining thresholds at which each change is made (you get migration paths at X migrations/month, you get elections at Y% of the community being eligible to vote, etc)
  • Move the privileges changes into Phase 1 instead of Phase 2
  • Deprecate the terms "graduation" and "beta" and be smarter about the vocabulary we use to describe site states
  • Allow communities to choose features they want from sets of things they've become eligible for

I'm not saying we will do all or any of those things. I am saying that they're all possible because we've opened the door to discussions about what it means to graduate. This is an opportunity for all of us to figure out what comes next.

So: assume that for the next few months, graduation functions the way Ana describes above. What are the next changes you'd like to see? Write it up and let's hash it out on meta like we would with any other .

Source Link
hairboat
hairboat
  • 15.2k
  • 7
  • 57
  • 89

Some clarification:

This is only one step in a very long process of figuring out what it means to be what kind of site on the SE network.

We had the concept of a strict graduation for many years. You were a beta site until something mysterious happened and we descended from on high to tell you that you got to be a graduated site and then you waited around for your design and once that happened you got your election and other stuff and that was just how it worked. For years. We didn't touch the process. It chugged along and it more or less worked for a while.

But it didn't scale, and it ran into problems. A backlog built up because our network of communities is growing way faster than our design team is growing. So instead of hiring a few more contract designers to get the backlog cleared - which probably wouldn't actually work, and even if it did, would just be kicking the can down the road a few years until the scale problem reared its head again - we decided to take a step back and actually examine the concept of graduation for the first time since its inception and see what was working and what wasn't.

What we've done so far:

What we could possibly (NO PROMISES) do in the future, now that we've dismissed the notion that graduation is a single event:

  • Decouple the graduation treatment even further by defining thresholds at which each change is made (you get migration paths at X migrations/month, you get elections at Y% of the community being eligible to vote, etc)
  • Move the privileges changes into Phase 1 instead of Phase 2
  • Deprecate the terms "graduation" and "beta" and be smarter about the vocabulary we use to describe site states
  • Allow communities to choose features they want from sets of things they've become eligible for

I'm not saying we will do all or any of those things. I am saying that they're all possible because we've opened the door to discussions about what it means to graduate. This is an opportunity for all of us to figure out what comes next.

So: assume that for the next few months, graduation functions the way Ana describes above. What are the next changes you'd like to see? Write it up and let's hash it out on meta like we would with any other .