Meta:Requests for adminship

From Meta, a Wikimedia project coordination wiki
Jump to: navigation, search
Requests and proposals Requests for adminship on Meta Archives
This page hosts requests for administrator access on the Meta-Wiki; for requesting administrator access on any other wiki, please see the index of request and proposal pages, where a Steward can do the job if required. Bureaucrat, checkuser and bot requests are also made here. Before making a request here, please see the administrator policy.

Requests should be listed here for at least seven days; bureaucrats should only close after this minimum time. Adminship will be granted by a support ratio of at least 75%. If a request hasn't been addressed by a bureaucrat after a lengthy period of time, please leave a note at Requests for help from a sysop or bureaucrat. Requests may be extended, or put on hold by bureaucrats, pending decision or finding of consensus.

Requests for temporary adminship and bot requests may be less formal and often go for a shorter duration if consensus becomes clear after only a few days of discussion.

All editors with an account on Meta, at least one active account on any Wikimedia project, and a link between the two, may participate in any request and give their opinion of the candidate. However, more active Meta editors' opinions may be given additional weight in controversial cases.

See below for information on prerequisites on submitting a request, and how to add a nomination.
Wikimedia Meta-Wiki

Participate:

This box: view · talk · edit

Information

Note that this page is for access on Meta only. See the Steward requests/Permissions page for adminship/deadminship requests on other projects.

Regular adminship

  1. Before requesting admin access, please ensure you meet all of the minimum criteria:
    • Have a user page on Meta, with links to the user pages on other participated projects. This can state that SUL is activated or be provided via a Wiki matrix if that is not possible.
    • Have a valid contact address (either a confirmed email address in preferences, or a valid email address on the user page).
    • Be a currently active contributor on Meta. This is a subjective, not an objective, measure and there is no official post count.
  2. As Meta has a cross-wiki role, admins here are expected to have cross wiki experience. SUL confirmation or a matrix will ensure that editing on other wikis can be easily seen. It would be expected that those seeking adminship here would have both reasonable experience here and on other wikis.
  3. Given the multi-lingual nature of Meta, {{#babel:}} information will be of use to others.
  4. Place a request on this page, by transcluding a subpage, for example {{Meta:Requests for adminship/Example}}. Please put the newest request on the top. Bear in mind that even if you do meet the criteria above this does not mean that the community will automatically approve a request. Please add a minimum ending date to the election, allowing a full 7 day period from the first timestamp:
    ''Ending {{subst:#time:j F Y H:i|+1 week}} UTC''
    

Please note: Ill-considered nominations for adminship can be draining and deflating to both the community and the candidate. Any successful candidate will need to be able to demonstrate sufficient experience within the Wikimedia community, in addition to a familiarity with Meta-Wiki. If a candidate is not already a local administrator or holder of advanced permissions on a Wikimedia content project, he or she is less likely pass a request for adminship here at Meta-Wiki.

Bureaucratship

Add your request below under the bureaucratship section. Please note:

  • Only active administrators can become bureaucrats, and only after at least 6 months of regular adminship.
  • User is endorsed by two current bureaucrats after he/she nominates themselves here.

If you fail any of these requirements, you will not be assigned the bureaucrat flag. For more information see Meta:Bureaucrats.

Other access

For these types of access, create a subpage just as you would for regular adminship and add it to the appropriate section of this page.
  • Temporary adminship: If you need temporary sysop access for a particular reason (such as ability to edit protected pages), you may request temporary adminship on meta. In this case, adminship shall be granted with no requirements and approval, but the user will promise to limit their activity to the necessity of what they asked for. Temporary sysop access will normally be valid for one month.
  • Bot: Please read the bot policy. This wiki allows global bots and automatic approval of certain types of bots; for other bots, add your request below under the bot section, in the same way as an admin request.
  • CheckUser: please read the CheckUser policy and add your request below under the checkuser section, in the same way as an admin request.
  • Oversight: please read the Oversight policy and add your request below under the oversight section, in the same way as an admin request.
  • Translation administrator: please read Meta:Translation administrator and Meta:Translate extension. No fixed time limit for these requests is defined, and there are no particular requirements; if you provide a valid reason your request will be granted.
  • Centralnotice administrator: was added as a way to avoid granting the full administrator rights package to those who primarily only need to edit banner campaigns. Because of the potentially huge impact of banners on the wikis, this should be granted carefully and sparingly.
For these types of access, just ask on Meta:Requests for help from a sysop or bureaucrat.
  • MassMessage sender: please read about MassMessage, and provide a clear reason for requesting access. Specify a duration, or specifically request ongoing if needed.
  • Uploaders

Requests for regular adminship


None currently

Requests for limited adminship

Dschwen

  • At least 100 valid contributions on another Wikimedia project: about 14000 across different projects (mainly commons, de, en)
  • >350 valid contributions on the Meta-Wiki: Check
  • Administrator and Bureaucrat of another project: commons:User:Dschwen
  • Meta userpage: User:Dschwen, with a matrix of links to other projects.
  • Valid contact address: Special:Emailuser/Dschwen, active and validated.
  • Have read (and understand) Meta admin policy: Yes.

Per Meta:Requests_for_adminship/Dschwen and Meta:Requests_for_adminship/Dschwen 2 and Meta:Requests_for_adminship/Dschwen 3 and Meta:Requests_for_adminship/Dschwen 4 I'd like to reapply for a limited adminship solely used for the purpose of editing Mediawiki:Wikiminiatlas.js, the centrally hosted clientside part of the WikiMiniAtlas. I'm the creator of the WikiMiniAtlas, a drag- and zoomable map plugin for wikimedia projects. The WikiMiniAtlas is activated by default at least ten Wikipedias and on Commons. I need to be able to update the javascript part, requiring me, as the maintainer, to have admin privileges. Updates include new translations, feature requests and bug fixes. When updates have to be made, they have to be made quick.

I would like to note that I have had a limited adminship for this exact purpose for about seven years, and have lost it on April 8th because I missed the inactivity procedure due to extraordinary real life business (moving). I would also like to point pout that despite having made less than the required 10 edits on the clientside script, I am anything but inactive. In the last 6 months I spent most of my WMA time on porting the WikiMiniAtlas over to Wikimedia Labs due to the impending shutdown of the toolserver. It has only been for a few days that Labs does offer me everything that I need to operate the WMA. I am fully set up on Labs now, and losing the sysop bit could not have come at a worse time. I need it more than ever right now to start limited testing of the Labs instance to make sure it holds up to the traffic, and to have ample time to fix potential issues before the Toolserver goes down once and for all.

Per Meta:Requests_for_adminship#Other_access I would like to have my sysop bit reinstated as soon as possible (while this RfA plays out), and I would like the temporary adminship to be replaced by a limited adminship should this RfA be successful. Thank you in advance. --Dschwen (talk) 15:07, 15 April 2014 (UTC)

  • Support - I don't see why it was removed. However, would it be possible to host the code in your own personal js file? That way, admins could still edit it, but you could as well (but nobody else). It seems a bit strange to grant the entire sysop toolkit to maintain one page. Ajraddatz (talk) 15:22, 15 April 2014 (UTC)
    • Meta:Administrators#Inactivity: "Any sysop inactive on Meta will be desysopped." --MF-W 15:29, 15 April 2014 (UTC)
      • It seemed to be explicitly granted to avoid that rule, and common sense would suggest that he is still as active as he needs to be to maintain the wikiatlas script, which is his scope. Oh well. Ajraddatz (talk) 15:34, 15 April 2014 (UTC)
        • It might seem illogical here, but since temp. adminship can also be for "sometimes an indefinite period", I'd say that it is only appropriate to check these sysops in the activity runs. --MF-W 17:14, 15 April 2014 (UTC)
          • Sure, but making a few hours break 7 years of adminship is the illogical part. I think I have made it clear that I am still active and do still need the sysop bit. --Dschwen (talk) 17:17, 15 April 2014 (UTC)
            • That is a problem of the definitions of the inactivity policy then. --MF-W 23:52, 15 April 2014 (UTC)
  • supportDerHexer (Talk) 15:23, 15 April 2014 (UTC)
  • Support. In the meantime I gave you temporary adminship under this rule "[...] you may request temporary adminship on meta. In this case, adminship shall be granted with no requirements and approval, [...] Temporary sysop access will normally be valid for one month." (WM:RFA). --MF-W 15:29, 15 April 2014 (UTC)
  • Support. 7 years seems to be a reasonable time span. Vogone talk 15:31, 15 April 2014 (UTC)
  • Strong support, per above. Thank you for your work on WMA. PiRSquared17 (talk) 17:27, 15 April 2014 (UTC)
  • Support This seems a better solution than odd temporary use of the tools. As this would require Dschwen to use the tools at least 10 times every six months, they may end up doing a wider variety of helpful things here too. -- (talk) 18:03, 15 April 2014 (UTC)
    Please note that he does not request "normal" adminship since he specifically added a section for "limited adminship" on the RFA page. --MF-W 23:52, 15 April 2014 (UTC)
    Ah, this seems a missed opportunity. -- (talk) 10:29, 16 April 2014 (UTC)
  • Support Trusted --Steinsplitter (talk) 20:43, 16 April 2014 (UTC)
  • Support --Kolega2357 (talk) 20:46, 16 April 2014 (UTC)
  • Support -- Wagino 20100516 (talk) 09:02, 17 April 2014 (UTC)
  • Support --KTo288 (talk) 09:33, 17 April 2014 (UTC)
  • Support Courcelles 18:34, 19 April 2014 (UTC)
  • Support - Sure. --Goldenburg111 18:36, 19 April 2014 (UTC)
  • Support It's weird why it's not permanent :/ oh well the inactivity policy...--AldNonUcallin?☎ 18:52, 19 April 2014 (UTC)
Comment - my comment above seems to have been missed, so I'll repeat it again here - why not host the wikiatlas code in Dschwen's personal js file? Mediawiki:Wikiminiatlas.js could then be replaced with an importscript command which takes the code from User:Dschwen/Wikiminiatlas.js. This would mean:
  1. There would be no disruption in usage since anything drawing from Mediawiki:Wikiminiatlas.js would still work.
  2. Dschwen would not need to worry about the local sysop package at all, especially inactivity procedures which will most likely be repeated in the future.
  3. We wouldn't need to grant the full sysop kit to someone who wants to maintain one js page.
IMO this is the best solution, and will result in no future conflict over this. If ever Dschwen goes inactive, the code can be transferred back to Mediawiki:Wikiminiatlas.js. Admins can also edit the code in his personal JS file so that isn't a problem. Thoughts? Ajraddatz (talk) 18:57, 19 April 2014 (UTC)
Sounds like a good idea to me.--AldNonUcallin?☎ 19:07, 19 April 2014 (UTC)
the import command would add yet another http request, which at the current level of use would make it a bad idea. The decision was made NOT to host the script in user space (were it was before it got moved to meta) as the script is very high profile. I don't see why we should change this back. It worked pretty well for the past seven years. --Dschwen (talk) 21:09, 19 April 2014 (UTC)

Requests for temporary adminship


None currently

Requests for bureaucratship


None currently

Requests for CheckUser access

"Meta:Requests for checkuser" redirects here. To request checkuser information, see Meta:Requests for CheckUser information.

None currently

Requests for Oversight access


None currently

Requests for translation adminship


None currently

Requests for CentralNotice adminship


None currently

Requests for bot flags


None currently

See also