User:Queerbubbles/RfA Review Recommend Phase
Questions
[edit]Selection and Nomination
[edit]A1. Editors note that the RfA process can be daunting to prospective administrators, and that the process itself may discourage otherwise qualified candidates from seeking adminship. How can this "Selection Bias" be countered?
- Response: There really isnt a good answer for that... besides running advertisements or creating a full on "So You Wanna Be An Admin??" tutorial. The way it is, its a little hidden. I dont know how I found it; I think it was because I was interested at the onset, and then once I started being a spectator, I saw that the people who comment and !vote are vicious and unless they know you personally, dont have anything constructive to say. Not all people, mind you. But alot of them.
A2. Editors expressed concern over unprepared or unqualified candidates at RfA, noting that their candidacies result in NOTNOW and SNOW closures that can be discouraging. In lieu of minimum requirements for adminship, how can prospective candidates be educated about RfA and the community's expectations of its administrators?
- Response: Make sure that before they are allowed to click the buttahn to create the page, make them go through a tutorial. Or create a screening process.
A3. 44 editors expressed concern over excessive co-nominations. Some of these editors advocated a limit on co-nominations, perhaps capping them at one or two per candidate; others recommended asking prospective co-nominators to post a Strong Support in lieu of an actual nomination statement. How can the concern over Co-nominations be addressed?
- Response: I dont honestly care if someone has "too many" Co-Noms. If you're getting to 5, yeah... its a little excessive, but I wont hold that against someone. If you have to arbitrarily pick a limit, I'd say 4. But others will say the number should be lower.
The RfA Debate (Questions, Election, Canvassing)
[edit]B1. 60 editors expressed concern over the number of questions asked of candidates, and indicated that questions should be limited in number. How can this be accomplished? What limits could be fairly imposed? Are there alternative means for the candidate to provide information about themselves without the prompting of questions?
- Response: Maybe we should have a full on questionnaire that they must create on a subpage which asks a broad range of questions from experience to their views on some things. If most things need to be asked beyond that, then the questions can be asked. But we can ask that the questions be something along the "follow-up" questions... does that make sense?
B2. Editors expressed concern over the content of questions, with 43 editors disapproving of "Trick questions", 8 disapproving of questions that require only a quotation from policy to answer, and 54 favoring questions that relate directly to the candidate and their experiences, contributions, conflicts, etc. How should the scope of possible questions be determined? Conversely, how would the decision to remove bad-faith or problematic questions be made, and by whom? What subjects should be specifically off-limits, and why?
- Response: Age should be off limits unless you want me opposing due to age. Seriously.
B3. Editors note that RfA is seen as a negative process, with issues such as badgering of opposes, personal attacks, and a general lack of civility being prominent concerns. How can the RfA process be changed to address these concerns?
- Response: You cant. You cannot make someone be nice to someone else. Its not going to work.
B4. The very nature of the RfA process was disputed. Some editors desire rationales with every vote, and favor a more discussion and consensus-based process similar to other processes on the English wikipedia. Other editors desire a more vote-based election, where the raw numbers of supports and opposes are the critical factor. Is there one of these methods that would provide a clearer consensus on the community's view of a candidate? Or, alternatively, is a hybrid of the two preferable, and how should that be structured?
- Response: I dont like full on # votes... people do decide to change their votes based on new information. I think a more discussion based, rationale needed way of voting is better.
B5. The amount of discretion held by Bureaucrats to remove or discount problem votes was also discussed, with some editors favoring increased discretion for Bureaucrats. 25 editors also favored a detailed closing rationale from Bureaucrats, detailing the specific factors that resulted in the candidate being successful (or not successful). What changes to the RfA process or format could clarify community consensus on this issue? Should Bureaucrats take a more active role in managing (or clerking) ongoing RfAs?
- Response: They should have a closing rationale just like admins have to have for closing AfDs
B6. 68 editors noted that a limited form of Canvassing or advertising would be acceptable, if such canvassing was done on-site and in a neutral fashion. How could a candidate advertise the fact that he or she is a candidate for adminship, while being completely neutral in the audience to which he or she advertises?
- Response: There should be a certain template that is created and maintained by current admins in which someone can select copy and paste. Simple, to the point, and doesnt leave any room for personal bias.
Training and Education
[edit]C1. Though 73 editors responded favorably to the Admin Coaching programme, 39 were critical of the process for "Teaching for the test", or for being an RfA preparation programme rather than an Adminship preparation programme. In what ways could Admin Coaching be improved to focus more on adminship itself?
- Response: Have it set in stone and adhere to a curriculum. And have it after the fact... like New Admin Skool.
C2. In evaluating New Admin School, some editors noted that a Mentorship element would be of great benefit to newly minted administrators - something that Admin Coaching provides in a direct one-on-one coach-coachee team. Similarly, 15 editors characterized Admin Coaching, a primarily pre-adminship process, as being invaluable after the RfA, which is traditionally when New Admin School is used for training. Are there areas where the two processes overlap, and can be made more complementary? Are there common themes or elements that could be shared between the two processes, in order to improve the effectiveness of both?
- Response: There should only be New Admin Skool.
Adminship (Removal of)
[edit]D1. Editors noted that the current voluntary Admins open to Recall process is redundant to Dispute Resolution process such as Requests for Comment and Arbitration. In the absence of Recall (i.e. if it were removed altogether), how could existing processes be adapted to more effectively deal with issues of administrator abuse?
- Response: Recall should be mandatory. And it should be based on an outside set of rules and regulations. It should not be based on a single person's ideas and whether or not they feel like participating.
D2. Editors cited the voluntary nature of the Admins open to Recall process as problematic, and 40 went as far as to recommend a mandatory process for all administrators, either as a mandatory form of Admins open to Recall, or a more formal version of the process administered by Bureaucrats. As a separate process from WP:DR, how could the current recall process be standardized for use as a mandatory process? Who would be responsible for such a process?
- Response: Oooo... I already said that! Go me! Um... B-Cats should run it. Absolutely. Too much "cronyism" going on within the admin ranks.
D3. 44 editors criticized the recall process for being too open to abuse, both through spurious or bad-faith calls for an admin to be recalled, or through administrators who fail to follow through on a commitment to stand for recall. How can the recall process be amended to address these concerns?
- Response: Be run by B-Cats.
D4. Some editors recommended that administrators be required to stand for some form of reconfirmation after a given period of time. How would such reconfirmation be structured? How long would an admin have before such reconfirmation would be required? Could such reconfirmation be triggered by an effort to recall an admin, and how would that be handled? What form would such reconfirmation take (RfA, Straw Poll, etc).
- Response: They should be. It should be a re-run for admin. For RfA but RrfA. It should be 1 year and be the same as adminship only should not include any "pre-admin" responsibilities/issues. Only those after the bit was given since we are voting on their conduct since not conduct before.
Overall Process
[edit]E1. The earliest version of the RfA policy states that adminship is granted to "anyone who has been an active Wikipedia contributor for a while and is generally a known and trusted member of the community."[1] Current policy leaves the definition of a "trusted editor" to the community. Editors offered a wide range of basic characteristics desirable of administrators, including Trustworthiness, competence, and communication skills. How could the RfA process be amended to either A) more fully ensure that editors selected as admins do indeed have the full trust of the community, or B) more fully fit the community's expectations for administrators?
- Response: Meh. Policy wording is not my thing. Sorry.
E2. Editors expressed concern over the format of the Requests for Adminship process. Some suggested that RfA has become a form of high-impact editor review, while others expressed concern over the view of Adminship itself as a goal or "trophy" that all editors should attain after a certain period of time. In taking the RfA process as a whole, what elements work well? What elements should be removed or amended?
- Response: It is a trophy. It is a goal. Its not a bad goal, though. It is a bad trophy. If your goal is to ensure the betterment of the project, then thats a good idea. Its not something that should be ignored.
Footnote
[edit]- ^ "Requests for adminship". 2003-06-14.
This question page was generated by {{RFAReview}} at 14:16 on 28 September 2008.