Forum:Addressing issues with rights requests
Please forgive me if I don't write an incredibly long wall of text about the recent issues we've encountered with requests for rights (i.e. TSW:RFA and TSW:RFB). I doubt I need to rehash the cluster-you-know-what we just experienced with the most recent request, and I don't want to turn this thread into a place to complain about the opinions of others in that RfA. This is the place to solve the obviously flawed RfA and RfB system. Because there are a couple things which are broken, clearly.
I would like everyone to use this thread for several goals. I would like us all to come to some general agreement on how we want to determine consensus on Requests going forward. Whether this means we stick to the idea of counting support versus opposition votes, or whether this means we somehow objectively weigh each vote on the merits of its arguments, I don't know. If we decide to stick with voting, then we should at the very least come to an agreement on whether or not votes can be struck out, and on what grounds, and following which procedures. We should also determine what margin of support needs to be attained before a request can be successful. This is going to be a difficult matter to solve, so I emphasize patience and creative ideas.
Aside from the major job of sorting out consensus, there are a few simpler fixes I think we could implement. First, I think we should add a rule on RfAs limiting them to one request at a time. This rule currently exists on RfBs, but not RfAs, I think it should be implemented on RfAs too.
Second, I think the whole process might go smoother if we implement some sort of commentary period before the clock on voting begins. To those who think that the RfA process as it is is already too slow... I believe that having a period to work out issues with a candidate before the voting begins might be able to alleviate a lot of the problems that have come up. Here's what I'm thinking:
After an RfA or RfB passes the initial nomination/request stage, the bureaucrat facilitating the discussion opens a period for public comment. This would be a time where regular users can ask the candidate questions, give input on matters and give their general opinion, but not vote. My thinking is that this period would last a week, but that the Request would progress to a vote if no user leaves a comment for at least two days. This gives the option for users to weigh in before a vote, but also ensures that a vote begins if no one really wishes to comment. This would also make it possible to determine if there was overwhelming consensus for a user before the voting even begins... in such a case, voting could be skipped entirely as it wouldn't be necessary, though this should only really happen if support for a candidate is unanimous in the comment phase.
I think having a comment period would also alleviate the issues raised with possible "weak" votes of support or opposition, since the arguments for or against a candidate could be fully flushed out without them necessarily needing to carry any weight as a vote.
Finally, on a more urgent note, I believe that we should temporarily suspend Requests for Administratorship and Requests for Bureaucratship, effective immediately. I think we can all agree that there are several issues with the system as-is, and we owe it to ourselves and to potential applicants/nominees to solve the issues before new Requests are heard. Therefore I am immediately asking for feedback on whether RfAs and RfBs should be closed. Please let me know your thoughts on that matter, on anything else I've mentioned, or on anything relevant that you'd like to discuss.
</wall of text> -- LostInRiverview talk ~ blog 06:33, May 10, 2013 (UTC)