Timeline for The December 2024 Community Asks Sprint has been moved to March 2025 (and lengthened to 2 weeks to compensate)
Current License: CC BY-SA 4.0
29 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 18, 2024 at 3:52 | comment | added | VLAZ | @AndrewMorton the definition can be found in We spent a sprint addressing your requests — here’s how it went under "Introducing the Community Asks Sprints" | |
| Dec 17, 2024 at 21:46 | comment | added | Andrew Morton | Is "Community Asks Sprint" a term-of-art specific to Stack Exchange that could be linked to a definition, please? | |
| Dec 17, 2024 at 8:28 | comment | added | Glen_b | How could the Gregorian calendar (and hence how many working days are in the month) and what normally happens on any December (people want to spend a little time with their families) and the company's own planned downtime have come as a last minute surprise to the company? This seems rather convenient, and given the past history, it only being mentioned now borders on suspicious. Like, what the heck will be happening in March that we need distracting from? | |
| Dec 16, 2024 at 23:59 | history | protected | CommunityBot | ||
| Dec 16, 2024 at 21:43 | history | edited | NoDataDumpNoContribution | CC BY-SA 4.0 |
typo
|
| Dec 16, 2024 at 6:08 | comment | added | Andreas condemns Israel | @Mentalist There's an alternative platform called Codidact. If you wish, you can contribute there instead. You may also be happy to find that the overall mood on the platform is way better, thus you don't have to be as concerned about people venting. | |
| Dec 16, 2024 at 1:52 | history | edited | JNatStaffMod | CC BY-SA 4.0 |
while we're at it, December isn't winter everywhere ;)
|
| Dec 12, 2024 at 21:29 | history | edited | TylerH | CC BY-SA 4.0 |
Updated the title to include the additional useful information *without* misrepresenting the company's internal fiscal year classification
|
| S Dec 12, 2024 at 14:36 | history | rollback | SpencerGStaffMod |
Rollback to Revision 4 - Edit approval overridden by post owner or moderator
|
|
| Dec 12, 2024 at 11:37 | comment | added | Sayse | @Mentalist - The move to cloud announcement shows that staff posts can be well received when they warrant it | |
| Dec 12, 2024 at 11:18 | comment | added | Mentalist | @VLAZ "Community blame" would be an exaggeration. There are cases when I agree that the criticism is deserved. But other times I can't help wondering if people just want to vent about something. And there are things that irk me about SE too, but rarely have I seen those things get improved. I won't spend too much energy wishing and hoping. The biggest issue may be the scarcity of alternative platforms. | |
| Dec 12, 2024 at 10:49 | comment | added | VLAZ | @Mentalist no, community sprints just suck. And removing them after mere two sucks even more. Because these sprints, while bad, are apparently the only time the company bestows us with the high and mighty quick fix for a 7+ year old problem. The announcement also sucks. I don't see it fair to shift the blame onto the community for the company failing over and over and over and over and over again. And then posting more drivel and OH LOOK, IT WAS DOWNVOTED. I'm not sure how you rationalise the community to blame for this. The answer box is below if you wish to explain. | |
| Dec 12, 2024 at 10:35 | comment | added | Mentalist | These days I feel like no matter what the staff announcement is, it's going to be downvoted and criticized. Staff: "I'm going to have a pastrami sandwich for lunch." Meta SE: "You didn't factor in enough input from the community! This sets a precedent for anti-vegan policies! You didn't even mention the farming methods used to grow the lettuce!" | |
| Dec 12, 2024 at 8:55 | history | suggested | A-Tech | CC BY-SA 4.0 |
Specified title
|
| Dec 12, 2024 at 8:22 | review | Suggested edits | |||
| S Dec 12, 2024 at 14:36 | |||||
| Dec 10, 2024 at 22:01 | comment | added | V2Blast | @Lundin: It's not that the company only listens to Meta requests made during that time. It's just a period of time dedicated to working on community requests/issues, to my understanding. Those feature requests/bug reports can have been made at any time. | |
| Dec 10, 2024 at 7:34 | comment | added | Lundin | @SpencerG Still sounds to me like "loudest on meta that week" wins. | |
| Dec 9, 2024 at 18:26 | comment | added | SpencerG StaffMod | @Lundin We incorporate various meta request into this process. There is a dedicated group working through the entire quarter to prep for the sprint week. They review the existing asks, assess what can be done, and divide them among the teams. We started taking requests last time to incorporate more current community interests so that what was being prioritized was not solely from our perspective. We still are making the decision, but we wanted it to be a mix of things that the community is currently interested in and items we think need addressing. | |
| Dec 9, 2024 at 18:21 | comment | added | SpencerG StaffMod | @NoDataDumpNoContribution not exactly. We have staff around, but it is reduced this time of year due to the holidays, so we could have run it; it just would have resulted in getting less done. The major contributor to this change is the above and the fact that internally, we asked for a two-week one to see if we could tackle some of these larger requests that are not doable in a one-week time frame. | |
| Dec 9, 2024 at 10:37 | comment | added | Lundin | Maybe I'm missing something here but why can't community input from the various metas be taken continuously throughout the year? Instead of taking some rushed decision based on input from a few, potentially misguided users during a short time window? | |
| Dec 8, 2024 at 19:37 | history | edited | Shadow Wizard | CC BY-SA 4.0 |
Winter is in different times in different parts of the world. Using a consistent term instead.
|
| Dec 8, 2024 at 18:47 | history | edited | OrangeDog | CC BY-SA 4.0 |
edited title
|
| Dec 7, 2024 at 22:17 | comment | added | NoDataDumpNoContribution | @SpencerG Wasn't already now freeing up staff at the right time an obstacle? That's why I would not be surprised if that is also the case next time but it may also only be a one time exception. | |
| Dec 6, 2024 at 19:01 | comment | added | SpencerG StaffMod | @NoDataDumpNoContribution I don't see freeing up the staff as an obstacle here as the community asks sprint is pretty important around the organization. Now we may find after this sprint that dedicating two consecutive weeks isn't sustainable, but we will see how it plays out when we get there. | |
| Dec 6, 2024 at 7:37 | comment | added | NoDataDumpNoContribution | Understandable (so +1) but also some kind of precedent for potentially giving up. Will you be able to really free up all staff for two whole weeks when there will be many other things to do (there always is)? Time will tell. | |
| Dec 5, 2024 at 17:26 | history | edited | V2Blast |
edited tags
|
|
| Dec 5, 2024 at 16:53 | answer | added | TylerH | timeline score: 66 | |
| Dec 5, 2024 at 16:49 | answer | added | VLAZ | timeline score: 28 | |
| Dec 5, 2024 at 16:39 | history | asked | SpencerGStaffMod | CC BY-SA 4.0 |