Update - October 9, 2024
We were able to work on quite a few issues during this sprint, some we previously told you about in the original post below, and others that were left over from the first Community Asks Sprint or completely new ones.
Although this was only the second ever Community Asks Sprint, we are seeing the benefits of successive sprint planning that build off one another from quarter to quarter. They allow for dedicated discovery or design effort that needs more refinement to get them ready for completion in the next sprint.
For example, some additional discovery and design work was completed on an item from the last sprint, Tell users when their edits are rejected; additional updates were made this sprint to the notice banners for suggested edits. The changes should help with banner blindness when appropriate and align better with Stack's Notice component usage guidelines. There are now five versions of this notice, depending on the user’s scenario with regard to suggested edits.
Here are some highlights of issues we were able to resolve as a part of this sprint:
- Can the new duplicate comment make “edit” a magic link
- Remove the suggestion to post a new question from the closed questions post notices
- Indicator on Meta next to the display name of former Staff and/or Mod users for actions performed with that status
- Usernames that consist solely of Zalgo text can't be clicked when associated with a post
- Gold tag badges don't apply to synonymized tags
- Half of the New Privilege message is in a language i don't speak
- Hiding downvoted questions silences important discussions on Meta
- Delete vote retraction logic is confusing
- It's not possible to unfollow a deleted discussion
- How to find a question by its old tag when that tag is synonymized with another
One issue we’d also like to call attention to is the Are there plans to switch to the current version of MathJax? in which @KyleMit spent the sprint investigating how we might go about upgrading our MathJax version from 2.x to 3.x+, as had been requested in several places explained in this post.
Although we couldn’t get to everything, we appreciate you taking the time to submit requests on this post. Moderators, thanks for tagging relevant posts as status-review and users, keep voting! We will continue to take all of these into consideration in prioritizing the backlog requests that get worked on next.
We’re excited to continue refining this into a repeatable, efficient process for subsequent quarterly sprints. Please let us know what you think of the second Community Asks Sprint and any feedback you may have. Hopefully this will continue to be a way for us to address inconveniences, bugs, and requests around the network. We’re looking forward to future iterations, and hope you are too!
Update - September 30, 2024
Last week, we completed our Community Asks Sprint! Well, mostly. There are still a few lingering items that need to be addressed to wrap it up. To that end, we won't be sharing our post-community asks sprint summary until next week, which will list everything we were able to address this time around.
Update – September 10, 2024: Thank you everyone for submitting your issues and requests; we appreciate you taking the time to raise them. Keep them coming. We will take these into consideration alongside our existing process for reviewing and prioritizing the requests that get worked on during these sprints. Expect another update a week or two after the sprint finishes; we’ll let the community know how it went and share the highlights of issues we were able to tackle.
My name is Caroline, but some of my friends call me Carot. I’m a staff member on our Product Marketing team and I work closely with the Community team here at Stack Overflow. I’m also a first time Meta poster, it’s great to connect with you all. Let’s dive in.
In June, we spent a sprint addressing your requests and introduced the “Community Asks Sprint”. The Community Asks Sprint is dedicated time, across all our public-facing developer teams, to work exclusively on requests that have come in from the community. This quarterly sprint allows us to prioritize work on requests and reports that could otherwise remain backlogged for long periods of time because they may be outside the scope of roadmap priorities.
The first sprint was well received, but we heard you in wanting a heads-up before work began for the next one, which is the purpose of this post. As this was a new initiative for our company, across many different departments, and the core team was tasked to plan and establish a process for longevity, we wanted to surprise and delight, not knowing how much we would be able to accomplish in a short period of time. However, now that we have a solid foundation in place, we are happy to announce our next Community Asks Sprint will be September 23rd - September 27th, 2024.
Here are some highlights we are hoping to work on in the upcoming sprint (note that we may or may not get to all of these, we may get to more, or we may decide to triage different issues):
- Improve onboarding guidance for new reviewers in review queues
- Hiding downvoted questions silences important discussions on Meta
- Empty content field creation bug
- Comment rate limits are not enforced
As stated in the previous announcement post - moderators, thanks for tagging relevant posts as status-review so keep it up, we’ll review those items that end up on our board. The intention is to balance age and score, so that we can ensure we are looking at issues that you still care about, now. And users, don’t forget to vote! While we won’t ever rely solely on voting to determine our priorities, votes are a critical signal that lets us evaluate how much you want us to implement a feature on the network.
Are there any issues that you’d like to see us explore either in this Community Asks Sprint or a future one? We will take these into consideration alongside our existing process for reviewing and prioritizing the requests that get worked on during these sprints.
We will provide an update to this post a week or two after the sprint finishes and let the community know how it went and the highlights of issues we were able to tackle.