Timeline for Design-Independent Graduation is on for early September!
Current License: CC BY-SA 3.0
51 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 3, 2020 at 13:30 | history | edited | CommunityBot |
Commonmark migration
|
|
| Mar 20, 2017 at 10:30 | history | edited | CommunityBot |
replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
|
|
| Oct 5, 2015 at 22:21 | comment | added | Ana | @Zizouz212 Answer: Not really. Sites will graduate faster than they have been recently, but they will basically never be in the 90 days timeframe that we first talked about all those years ago. Turns out that it just takes longer than that for communities to reach the graduation criteria outlined by @Pops in basically every case imaginable. Between those two opposing forces acting on each other, we expect it'll mostly break even. | |
| Sep 9, 2015 at 19:11 | history | edited | Ana | CC BY-SA 3.0 |
removed item mentioning the addition of site links to the footer and added an explanation
|
| Sep 4, 2015 at 21:19 | comment | added | Ana | Hey @Catija the "beta" label will be dropped on newly graduated sites. We are not currently slated to give newly graduated sites an interim design because it would have caused delays in getting this thing underway, but I feel it may be a good future adjustment. If you a) think there's widespread confusion about when/whether the "beta" label is being dropped or b) would like to add another voice in support of an interim design, I encourage you to ask a new question. | |
| Sep 3, 2015 at 20:51 | comment | added | Catija | I know that next week is the week this is supposed to happen but do you have any info for us about when/whether the "beta" part of the logo is going to be dropped or if design-independent sites will get a different design than the currently-beta sites? If you like, I'm happy to address this in a question, not certain if it's been addressed yet, though. | |
| Aug 21, 2015 at 23:05 | history | edited | Ana |
removing [featured] tag
|
|
| Aug 21, 2015 at 11:44 | comment | added | Dɑvïd | It would be interesting to know what this might imply for the so-called "beta-forever" sites. I understand the attention given to what used to be called "graduation", but "removing the 'beta' label" could/should also apply to these "stable" sites. | |
| Aug 21, 2015 at 2:02 | comment | added | Zizouz212 | @Ana This sounds great! My only concern is that sites will now be "graduating" much faster, and beta's moving on at the previous 90 day threshold will be much more common (Do you think it will be more common?). As such, the design backlog will likely grow exponentially, as before, sites would wait for quite a while before entering the log, and now, sites will be added to this log at a much faster pace. | |
| Aug 20, 2015 at 19:36 | comment | added | PearsonArtPhoto | @Ana: Good point, as it's really a slight variation of my previously posted concern, I've just added it to that answer. | |
| Aug 20, 2015 at 19:36 | history | edited | Ana | CC BY-SA 3.0 |
altered language to clarify the distinction between the graduation backlog and the sites approved for graduation in the future
|
| Aug 20, 2015 at 19:26 | comment | added | Ana | @Undo Absolutely. | |
| Aug 20, 2015 at 19:21 | comment | added | Ana | @PearsonArtPhoto I want to be upfront, this iteration of changes to the site life cycle isn't being altered, and will be in effect for at least a few months so that we can observe the results. But you bring up an interesting notion here, one we hadn't considered. If you wanted to write up a separate post sharing more thoughts about why that's a concern, it may influence our tweaks in the future. | |
| Aug 20, 2015 at 18:28 | comment | added | PearsonArtPhoto | I highly recommend not setting up migration paths without the additional reputation required for privileges. It seems like it will be more subject to abuse... | |
| Aug 20, 2015 at 15:06 | comment | added | Undo | @Ana So if a site has >10 q/day, and isn't ready to graduate, can we expect a meta post stating that (and ideally why)? It'd sure be nice not to have sites in a limbo. | |
| Aug 20, 2015 at 14:55 | answer | added | PearsonArtPhoto | timeline score: 4 | |
| Aug 20, 2015 at 14:15 | comment | added | Ana | @Undo We tell them. Most of the sites in the backlog have either been told by us many months ago, or are being notified now -- see Pops' announcement on Magento. | |
| Aug 20, 2015 at 13:13 | comment | added | Undo | How does a site know if it's 'waiting to graduate'? | |
| Aug 20, 2015 at 9:36 | answer | added | Ian Ringrose | timeline score: 8 | |
| Aug 20, 2015 at 0:35 | comment | added | ChrisW | I still don't understand why "privilege thresholds are increased" is in Phase 2. If a site wants its thresholds increased, can't or won't SE provide that in Phase 1? Is there any reason why SE defers that to Phase 2? I can understand delaying site design/redesign (i.e. lack of design team bandwidth), but changing privilege thresholds is surely just a per-site config change? | |
| Aug 19, 2015 at 22:27 | comment | added | chirlu | @Ana: Ah, OK; so the “becomes available” phrasing only refers to the first bullet point following it. | |
| Aug 19, 2015 at 22:24 | comment | added | Ana | @chirlu The factor determining the timeline is the rate at which the Stack Exchange design team can complete site designs. | |
| Aug 19, 2015 at 22:00 | answer | added | Monica Cellio | timeline score: 47 | |
| Aug 19, 2015 at 21:53 | comment | added | Vogel612's Shadow | @chirlu maybe relevant: Did all sites just graduate? | |
| Aug 19, 2015 at 21:26 | comment | added | chirlu | I’d like to repeat the question that was originally asked by @200_success, because I don’t see it answered: What does it mean for the privilege threshold increase to “become available”? Is there development work necessary for each separate site to implement it? | |
| Aug 19, 2015 at 19:39 | answer | added | hairboat | timeline score: 61 | |
| Aug 19, 2015 at 19:22 | comment | added | durron597 | @abbyhairboat Haha, yes. You can see why that was my first reaction to reading this post :) | |
| Aug 19, 2015 at 19:20 | comment | added | hairboat | @durron597 That's true. This isn't the only area in which we've failed to communicate clearly. (I was just going to link you to this to demonstrate until I realized you're the one who asked that question.) | |
| Aug 19, 2015 at 18:13 | answer | added | Vogel612's Shadow | timeline score: 69 | |
| Aug 19, 2015 at 17:57 | comment | added | Ana | @otus We just made this change, and I don't have that kind of information for you yet. We're trying this out, and there's also been a lot of interest in even further adjustments/deconstructions of graduation and the site life cycle. What we're announcing here, for sure, makes all that easier. But that's the best I've got right now. | |
| Aug 19, 2015 at 17:51 | comment | added | durron597 | @abbyhairboat If the 'lot of time and energy' doesn't result in communication and instead results in many years of promises without results, is it a surprise that many users think that you don't care or don't consider it? Note: I am not saying that you don't care nor don't consider it. Nor do I believe it. I am simply saying, lack of communication leads to a perception of these things among many users. | |
| Aug 19, 2015 at 17:50 | comment | added | otus | Does this mean that while phase 1 is going forward you are still considering whether to decouple the phase 2 changes? Or that unless something changes, two phases it is? I'm having trouble parsing the "for now..." paragraph. | |
| Aug 19, 2015 at 17:45 | comment | added | Malachi | What is the hold up on Designs ? | |
| Aug 19, 2015 at 17:16 | comment | added | hairboat | @200_success: Come on. You know we hear you. We are listening. We can't implement every piece of feedback we receive, and we can't customize every process for each community. But that doesn't mean we don't care, or don't consider it. The team has spent a lot of time and energy trying to understand Code Review's concerns and it's unfortunate that we're still not in a position to allay them. To imply that we aren't listening or don't care about them is just disingenuous. | |
| Aug 19, 2015 at 17:11 | comment | added | Rory Alsop | I'm interested for Music as well - have asked Pops the specific question about any lessons learned | |
| Aug 19, 2015 at 17:11 | comment | added | 200_success | @Catija It's the "we heard you" but we-aren't-really-listening aspect that concerns me. Code Review has… um… very mixed feelings about this, which is why I'm probing to see exactly what this announcement means. | |
| Aug 19, 2015 at 17:10 | comment | added | Zizouz212 | Out of curiosity, will it be more common for beta sites to be graduating (if they satisfy the requirements) to be graduating near the previous 90 day threshold? | |
| Aug 19, 2015 at 17:08 | comment | added | hairboat | @HDE226868 There's no list at this point, simply because we haven't made one yet (not because it's some big secret). We'll make announcements on site metas when they enter the process. | |
| Aug 19, 2015 at 17:07 | comment | added | HDE 226868 | @abbyhairboat Is there an official list of sites available yet, or will sites find out on a case-by-case basis? | |
| Aug 19, 2015 at 17:06 | comment | added | hairboat | @Catija Yes, ELL will be part of the batch that starts the process next month (after we work out the kinks on Magento). | |
| Aug 19, 2015 at 17:03 | comment | added | Catija | @200_success What antecedent? The previous post was a question asking whether the community supported the concept and this is telling us that "we've heard you and we're implementing it"... | |
| Aug 19, 2015 at 17:01 | comment | added | Catija | @abbyhairboat Is ELL on that list? | |
| Aug 19, 2015 at 17:00 | comment | added | Ana | @200_success This is different in that it provided the information that this, in its current form is moving forward. We're also aware that some of the community requested and would have preferred the rep levels be decoupled from site designs, but we weren't able to do that at this point. (Of course, I said all that above but hey, I don't mind reiterating.) | |
| Aug 19, 2015 at 16:55 | comment | added | 200_success | I'm reading and re-reading this post, and don't understand how this is not a duplicate of the antecedent. Has anything changed? Or are you just reaffirming that no changes need to be made based on the feedback? | |
| Aug 19, 2015 at 16:54 | comment | added | Ana | @200_success I appreciate that you do not, in any sense, want to be strung along. We have one designer working on site designs these days at any given time. Does this allow me to tell you what and when? No, I'm afraid not. One of the main goals here in breaking this down into smaller components is to allow us to better see and alleviate bottlenecks. I can't give you a more specific answer, but I'm glad you're keeping us accountable. | |
| Aug 19, 2015 at 16:50 | comment | added | hairboat | @Catija: Yes... sort of. One of the reasons we started working on design-independent graduation was the growing list of sites that were cleared to graduate and whose moderator teams needed some extra support. Rather than select more pro-tem moderators while they waited for designs, it seemed best to give them elections ASAP. | |
| Aug 19, 2015 at 16:48 | comment | added | Catija | Curious... how does this affect sites like Anime, which is currently going through elections but don't have a site design? You say it's starting in September but... is some of it already rolling out a bit right now? | |
| Aug 19, 2015 at 16:48 | history | edited | Ana |
edited tags
|
|
| Aug 19, 2015 at 16:46 | comment | added | 200_success | In Phase 2, please clarify what you mean by "as it becomes available". In particular, when do you expect privilege threshold increases to be "available"? | |
| Aug 19, 2015 at 16:39 | comment | added | M.A.R. | I have nothing to say, but "yay"! | |
| Aug 19, 2015 at 16:38 | history | asked | Ana | CC BY-SA 3.0 |