7

This is not a duplicate of this question, it's a feature request!
Please do not close it, leave the possibility for the staff members to answer this question (and not to just comment one of the answers on this topic, because comments are not for posting answers)!

Along with many users of the Stack Exchange sites, I was shocked that all the progress in getting the not-yet-received signs for reviewing the "First posts" queue has now actually been canceled.

This may not be an unsolvable problem on more popular sites like Stack Overflow, but it actually kills years of effort on less popular sites, where the path from "Custodian" to "Steward" can take many years. For example, it took me almost three years of daily monitoring the queue on rus.stackexchange.com to make 921 reviews. And now it's all gone? And it seems to me that I am not alone in this situation!

I understand that this task probably has a number of hidden obstacles to its solution, but if you just leave everything as it is, you will kill the long-standing hope of many and the motivation to continue further reviews.

After all, many people here are programmers. If you do not know how to overcome the problems with the splitting of the queue, ask the community, and we will be happy to provide you with all possible assistance. After all, helping is what we are here for (so, I hope, are you).

8
  • 5
    Already addressed here, including staff responses.
    – Ryan M
    Aug 27 '21 at 0:35
  • 1
    @RyanM, in comments to one of the answers to this question, staff said that it is possible to create a separate feature-request for it. Aug 27 '21 at 0:38
  • 5
    If you're referring to Yaakov's comment, that was asking for that answer to be reworded as a feature request, which has been done.
    – Ryan M
    Aug 27 '21 at 0:40
  • 3
    @RyanM, but it's a very important thing for many, so please it will be a question, not an answer. Aug 27 '21 at 0:44
  • 6
    A staff member has already said "We'll give some thought to a solution and reply back to this post." Why do we need another post? There are lots of important issues raised in the answers there. Some of them haven't even gotten staff responses.
    – Ryan M
    Aug 27 '21 at 0:47
  • 2
    @RyanM, to make it possible for staff members to write answers to it, not just the comments. Aug 27 '21 at 0:48
  • 7
    @RyanM The staff responses are in comments. Comments are not for posting answers. Aug 27 '21 at 1:17
  • 13
    There's absolutely nothing wrong with staff responding to things in that manner, and it has been done that way many dozens of times in past announcements of that type. We generally prefer to keep all things related to a major change in one place (in answers on that announcement) because it is easier to track.
    – animuson StaffMod
    Aug 27 '21 at 4:12