Jump to content

User:MER-C/RfA Review Recommend Phase

From Wikipedia, the free encyclopedia

Welcome to the Recommendation phase of RfA Review. In this phase, you will be asked to offer suggestions and proposals to address specific concerns and problems with the current Requests for Adminship process.

The questions below are taken directly from the 209 responses from the Question phase, each of which offered editors' thoughts and concerns about RfA. Based on those concerns, we identified the most frequently mentioned problems and included them here. These are the elements of RfA that are currently under review.

Please take your time and read through the concerns below. For each item, you are invited to offer a proposal that addresses the concern. Where possible, you are encouraged to provide examples, references, diffs and so on in order to support your viewpoint. There isn't a limit on the scope of your proposals; the sky is the limit, here. The intent of this phase is to get ideas, not necessarily to write policy - recommendations that gain traction and community support will be refined during later phases.

Most importantly, Answer as few or as many questions as you wish. All responses are evaluated, so any information you provide is helpful.

If you prefer, you can submit your responses anonymously by emailing them to User:Ultraexactzz. Anonymous responses will be posted as subpages with the contributor's details removed. If you have any questions, please use the project talk page at Wikipedia talk:RfA Review.

Once you've provided your responses, please encourage other editors to take part in the review. We stress that editors who didn't participate in the question phase are encouraged to participate now - more responses will improve the quality of research, as well as increasing the likelihood of producing meaningful results.

Once again, thank you for taking part!

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: I happen to belong in this category mainly because I hate answering lots of stupid questions. RFA is not meant to be a game of twenty (or more) questions. (Of course, no question from a genuine newbie is stupid as long as the answer isn't immediately obvious).

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: Implementing suggestions in E1 might help.

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: The only problem is that of TLDR. There should be no limit as long as the nominations address different aspects of the candidate instead of regurgitating the same thing e.g. someone from Wikipedia:WikiProject Spam talks about the candidate's efforts in fighting spam, a regular from FPC talks about involvement in featured pictures and so on.

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: I've seen people throw up seven questions in one go. One or two per customer to a maximum of 10 would be a good idea. Nominees should be encouraged to write a quick paragraph or so (entirely optional, of course) about who they are, what they do around here and try to preempt some silly questions.

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: Questions should relate to the candidate somehow. Questions spammed across multiple RFAs are a waste of space, since the answers are extremely easy to obtain, are easily prepared for and the answers may not reflect reality. The nominee should have the option to remove/ignore/mock questions that they do not wish to answer. Nobody else should remove good-faith questions, while anyone can remove bad-faith questions.

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: ...

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: Status quo is fine. Default to support unless good reasons are given otherwise.

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: Absolutely. Bureaucrats shouldn't be afraid to send bad votes to /dev/null and tell the community about it. This would have the additional benefits of more accountability and possibly less stupid opposes. Detailed closing rationales are unnecessary unless the situation calls for one (which, in my experience, is almost never).

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: RFA is one of the places where canvassing is OK - it isn't overly obscure and doesn't require any specialist expertise. A notice on the user's talk page and user page is fine by me.
  • Placing an opt-in ongoing RFAs template in various well-trafficked areas (e.g. WP:AN) might be a good idea for the community as a whole.

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: What should happen is more emphasis on stuff that actually happens out there. Here's some of the things I'd get the coachee to do:
  • Close some actual debates. There are some places on Wikipedia that allow anyone to close discussions which may make ideal "training" grounds for prospective admins - just as long as you follow the instructions and don't annoy the regulars.
  • Live speedy deletions. Probably best done on live articles with real time feedback from the admin coach. (This requires the admin and the coachee to be online at the same time). The current program relies on canned examples => limited variety.
  • ...

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 complimentary? Are there common themes or elements that could be shared between the two processes, in order to improve the effectiveness of both?

  • Response: ...

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: By admin abuse do you mean "abuse by administrators" or "abuse of administrators"? If the former, nothing really needs changing except Arbcom needing to get a wriggle on in some cases.

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: Ummm, no. Mandatory recall would make a good soap opera, though.

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: I'd make it such that only uninvolved, established editors may initiate a recall request.

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: Woohoo, more drama.

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: ... for some meaning of "trust" and "competence" that may or may not be the same as yours. There should be more concrete guidelines for the assessment for administrators. We have notability guidelines for AFD, WIAF(A|P|L|T|Po|S) for the various featured content processes, GA? for good articles and various other guideline/policy pages for various other processes. Why not one for RFA?

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: September 2008 having the lowest promotion volume in the history of RFA is a good sign that the process no longer works.

Once you're finished...

[edit]

Thank you again for taking part in this review of the Request for Adminship process.

Your responses will be added to Category:Wikipedian Recommendations to RfA Review, which will be used to review the responses after this phase is concluded.

This question page was generated by {{RFAReview}} at 06:45 on 13 September 2008.

  1. ^ "Requests for adminship". 2003-06-14.