Archive 20

←

Archive 24

Archive 25

Archive 26

Archive 27

Archive 28

→

Archive 30

Once the current Arbcom closes, one way or another, I suggest we carefully look at:

• WP:ADMIN
• WP:BUR
• Wikipedia:Under a cloud
• WP:FORMER
• WP:RIGHTS
• WP:FORMER/I

to see what, if anything, needs to be amended. I'd be very happy for other editors to add other policy pages to that list. --Dweller (talk) 15:18, 14 November 2012 (UTC)

I added a couple. MBisanz ^talk 17:32, 14 November 2012 (UTC)

My guess is that the regranting of tools to bureaucrats might need revisiting as well in a RFC. --Rschen7754 17:58, 14 November 2012 (UTC)

• Wikipedia:List_of_users_resysopped_by_the_Bureaucrats - It has three more crats to review and then regular maintenance. MBisanz ^talk 02:31, 15 November 2012 (UTC)

• Wikipedia:Requests for comment/Arbitration Committee Elections December 2012/Electoral Commission

As of this posting, there are currently only 4 people running for a committee of 3. As bureaucrats tend to be among the most trusted individuals we have, I thought I would ask if any more of you would come volunteer to help out : ) - jc37 04:11, 11 November 2012 (UTC)

• OK, I'll volunteer. Thank you. -- Avi (talk) 17:52, 15 November 2012 (UTC)

Per some prodding, I've compiled a new list of previous resysoppings at Wikipedia:List of users resysopped by a bureaucrat. If all crats could add to it in the future when resysopping, I would appreciate it. Also, if I could ask users to help finish it by:

1. Adding the page to the appropriate instructions/See also sections of other pages;
2. Adding annotations linking to Arbcom/Reconfirmation RFA;
3. Adding cross-references to renamed users;
4. Adding resysoppings I missed in the logs or the WP:CRATLOG.

I would appreciate it. Thanks. MBisanz ^talk 18:53, 15 November 2012 (UTC)

Wow, I've often thought the tasks you do are undervalued. But wow, another big example of it... - jc37 20:03, 15 November 2012 (UTC)

Thanks, I think I've finished all of the above tasks. MBisanz ^talk 02:10, 17 November 2012 (UTC)

I just got an email from a user asking to vanish on another project (not in another language, so the usual suite of interwikis wouldn't help). Is anyone familiar with the vanishing process on other projects? Is there a vanishing process on other projects?

I'm specifically thinking of sites like Commons or Meta, which are more likely to also have cross-wiki contributions from English Wikipedia editors. If we could toss a note at the end of WP:VANISH so that we can direct requests elsewhere, that would be lovely. (I had to direct the vanishing editor to the project's bureaucrat mailing list and basically say "good luck", which struck me as a sub-otimal solution) EVula // talk // ☯ // 16:17, 26 November 2012 (UTC)

Commons bureaucrat here, but unfortunately I have no experience on our vanishing process. But I'm definitely interested in hearing about this. Searching through archives at commons it seem that there is not much we can to, except for user and talk page deletion. Meta states that signatures will not be substituted, and the consensus on commons seems(!) to be that files will not be re-uploaded (unless someone wants to take responsibility for the uploads of the vanishee). --Dschwen 17:03, 26 November 2012 (UTC)

I'm an admin who was de-sysoped due to inactivity. I want to get back into Wikipedia again, can I have the mop back? Thanks! Borisblue (talk) 14:04, 25 November 2012 (UTC) Borisblue (current rights · rights management · rights log (local) · rights log (global/meta) · block log)

I see nothing which would prevent the return of the admin bit (and I see a lot which would encourage me to be bold and just return it). ···日本穣^? · 投稿 · Talk to Nihonjoe · Join WP Japan! 23:08, 25 November 2012 (UTC)

I also see nothing which would prevent the return of the bit. A third bureaucrat may see it differently. The Rambling Man (talk) 23:19, 25 November 2012 (UTC)

No "clouds" or controversial circumstances on the horizon that I can see.... Newyorkbrad (talk) 23:43, 25 November 2012 (UTC)

I looked briefly as well ;) No admin actions since 2007, so a refresher is likely due, but I didn't find anything but good in the history. Dennis Brown - 2¢ © Join WER 23:58, 25 November 2012 (UTC)

Having now been 26 hours since the request was filed and finding no evidence to prevent the return of the admin userright, I have granted Borisblue (talk · contribs) adminship. MBisanz ^talk 16:14, 26 November 2012 (UTC)

I'm not around much these days, but I wanted to make sure I was on the same page, for future reference. Looks like we did go ahead with the philosophy that we wait 24 hours after a re-sysop request, is that right? Useight's Public Sock (talk) 21:47, 27 November 2012 (UTC)

Yes, there is an imminent policy change supported by an overwhelming majority that puts in place a minimum 24 hour waiting period. MBisanz ^talk 21:55, 27 November 2012 (UTC)

Kilo-Lima (current rights · rights management · rights log (local) · rights log (global/meta) · block log) I am requesting a de-sysop due to inactivity. I have received the emaIl warning me the date is approaching and I am fine with this, so I guess you could wait until it happens itself or remove the privileges just now. I do, however, plan to return to the project at a later date. Thanks, KiloT 19:42, 26 November 2012 (UTC)

 Done. I hope to see you back when you're able. 28bytes (talk) 19:45, 26 November 2012 (UTC)

In a strange twist of reasoning, the above post would have prevented the automatic removal as it would count as activity. ···日本穣^? · 投稿 · Talk to Nihonjoe · Join WP Japan! 17:01, 27 November 2012 (UTC)

A fair point. Perhaps "inactivity" should be "admin inactivity"? The Rambling Man (talk) 17:07, 27 November 2012 (UTC)

That is how Commons defines it, but sadly I suspect it would be an uphill battle to get that as the en.wiki definition. MBisanz ^talk 17:16, 27 November 2012 (UTC)

I'd oppose it.There are admin tasks which do not necessarily require the tools. Imagine a very active admin who never manages to delete a page over a year's time. Do we want them to make a token deletion merely just because they need to to keep adminship? (Or blocking or protecting, or...) And would editing the mediawiki count, since only admins can do that. but it isn't an admin "logged action", per se. and and and : ) - jc37 18:27, 27 November 2012 (UTC)

At Commons, editing the MediaWiki space counts and they even have a fancy tool for tracking admin activity. MBisanz ^talk 18:52, 27 November 2012 (UTC)

What about the closing of XFD & RFC? While in some cases, this can be done by non-admin, the majority of cases are per norm reserved for admins. There will be no logged action there. (Yes, Snottywong's Tools exist for AfD, but it's not perfect.) While I would support the idea of the proposal, I don't think it's doable in practice. KTC (talk) 21:44, 27 November 2012 (UTC)

An activity measure couldn't possibly include things like viewing deleted pages, which isn't logged at all. Hut 8.5 15:51, 28 November 2012 (UTC)

Could a bureaucrat please examine the recent behaviour of Joefromrandb (talk · contribs) on Wikipedia:Requests for adminship/Harrias? Thanks — Martin (MSGJ · talk) 18:05, 28 November 2012 (UTC)

I read some of this earlier on. My initial instinct is to say "don't worry", the closing 'crat will clearly have a close look at the decision-making process behind the !voting and judge accordingly. Naturally, if behaviour deemed by the community to be disruptive at RFA continues, that would be a different matter, but probably one for an RFC, probably not for 'crats. The Rambling Man (talk) 18:14, 28 November 2012 (UTC)

The special authority of Crats with respect to RFA is almost entirely limited to closing them. There have been proposals to give Crats the authority to moderate RFAs, but they have never gone anywhere. Monty₈₄₅ 18:27, 28 November 2012 (UTC)

I agree with TRM that the closing crat will take a hard look, but in my administrative capacity and in light of prior threads on this board urging strict enforcement to prevent disruption, I'm inclined to blok Joe until the end of the RFA to prevent disruption. MBisanz ^talk 18:29, 28 November 2012 (UTC)

I considered that, but I'm not entirely convinced he's really disrupted Wikipedia that much. He's asked an awkward and loaded question. It would have been better (in my dreams) for the community to have just ignored it. The Rambling Man (talk) 18:32, 28 November 2012 (UTC)

My thought is that his failure to remove it once the disruptive nature was noted by NYB is further disruption. Obviously if he asks it again (at this RFA or another), I'll block him until he agrees to stop asking disruptive questions. MBisanz ^talk 18:36, 28 November 2012 (UTC)

Agreed. The Rambling Man (talk) 18:40, 28 November 2012 (UTC)

I'd be minded to agree, provided we're referring to question asked as number 6, and the same rationale would apply to others asking that same question if previously told it was inappropriate. I'm struggling however to see anything egregious about the question asked as number 4. WJBscribe (talk) 23:10, 28 November 2012 (UTC)

I don't see a problem with #4. I agree that anyone asking disruptive questions at RFA who should know better should be blocked. MBisanz ^talk 01:00, 29 November 2012 (UTC)

Yes, Q4 is/was just fine. The Rambling Man (talk) 17:43, 29 November 2012 (UTC)

I'm of the opinion that I'm no longer fit to be administrator. This is done under a cloud. I would like to keep rollback privileges. CharlieEchoTango (contact) 03:07, 29 November 2012 (UTC)

We can certainly remove your flag if you're certain that's what you want, but would you like to sleep on it first? 28bytes (talk) 05:13, 29 November 2012 (UTC)

Very kind of you to ask, but yes, I'm certain. There's no way I can legitimately continue on as an administrator after betraying the trust of the community like that. Regards, CharlieEchoTango (contact) 05:43, 29 November 2012 (UTC)

 Done. Thank you for your service. I look forward to your future editing after your break. MBisanz ^talk 05:47, 29 November 2012 (UTC)

He really ought to have been emergency desysop'd the moment he acknowledged as much as he did. For the protection of the project, alone, I think there ought to be a significant fear that there could be more here than he's admitted at this point. He's acknowledged using multiple accounts abusively and then using his administrator account to protect those edits, in at least one case to disrupt a blp. I've raised the issue at wp:spi so that someone can be certain the rabbit hole doesn't go deeper than he's said. jæs (talk) 05:49, 29 November 2012 (UTC)

ArbCom has been notified by Guerillero. --Rschen7754 05:55, 29 November 2012 (UTC)

We saw the post on his talk page, and this request. Gathering three votes to order an emergency desysop and THEN get the flag removed here would have been adding insult to injury and have taken more time than letting the crats process Charlie's request. Anything that happened in the small interval would have been watched like a hawk, anyhow. Courcelles 06:15, 29 November 2012 (UTC)

(edit conflict) Tangent, but why would you have to come here if it was an "emergency desysop"? I thought stewards were allowed to handle emergency requests. Legoktm (talk) 06:20, 29 November 2012 (UTC)

(edit conflict) I understand, in that case, Courcelles. Whether through the existing sockpuppet investigation request (which was just, rather inexplicably, declined and closed) or through whatever other processes the Committee would normally use, I sincerely hope there is a conclusive determination that this was, indeed, as far as the abusive sockpuppeteering went. jæs (talk) 06:22, 29 November 2012 (UTC)

(edit conflict)The stewards are hesitant to do things when there are local users with the ability to do. I meant "come here" more in the sense of finding a crat than posting on BN. Courcelles 06:23, 29 November 2012 (UTC)

Makes sense. Thanks, Legoktm (talk) 06:32, 29 November 2012 (UTC)

There's a different threshold of emergency for ArbCom passing a motion and a 'crat implementing it than for Jimbo Wales or the stewards to act on their own authority. That is, stewards will desysop pretty much only when it's needed to stop a current abuse of administrative tool that a local block has failed to stop. Snowolf ^{How can I help?} 06:40, 29 November 2012 (UTC)

• Also, I'll say so here, I ran the CU before even looking at the SPI -- there's clearly grounds to do so. I found no other accounts. Courcelles 06:29, 29 November 2012 (UTC)

• Heya Courcelles, a few minutes before your comment the SPI case was approved for a check. Assuming you're willing to do so, could you cross-post to there confirming the check as completed with no further accounts found? Many thanks, Spitfire^Tally-ho! 06:33, 29 November 2012 (UTC)

• No problem whatsoever, done. Courcelles 06:39, 29 November 2012 (UTC)

Would someone be good enough to remove the bit from Franamax (talk · contribs) please. I've just be advised by his sister that he has died. Thanks. CambridgeBayWeather (talk) 21:12, 30 November 2012 (UTC)

• Done, with much sadness. Terrible news, rest in peace Franamax. WilliamH (talk) 21:38, 30 November 2012 (UTC)

Six pending desysoppings for inactivity this month:

• Arjun01 (talk · email · contribs · deleted · logs · last entry · listuser · centralauth · target logs · userrights)
• Friday (talk · email · contribs · deleted · logs · last entry · listuser · centralauth · target logs · userrights)
• Hdt83 (talk · email · contribs · deleted · logs · last entry · listuser · centralauth · target logs · userrights)
• Karada (talk · email · contribs · deleted · logs · last entry · listuser · centralauth · target logs · userrights)
• Lightdarkness (talk · email · contribs · deleted · logs · last entry · listuser · centralauth · target logs · userrights)
• Solipsist (talk · email · contribs · deleted · logs · last entry · listuser · centralauth · target logs · userrights)

Regards, — Moe Epsilon 20:48, 1 December 2012 (UTC)

Done. Not my favourite bureaucrat task, but for once it's pleasing to note that nearly as many new admins were created through RfA as had their permissions remove for inactivity this month. WJBscribe (talk) 10:26, 2 December 2012 (UTC)

Hello. I have a bit of an odd request to make; when I was quite a bit younger and less mature, I used three particular user accounts, one of which reveals personal information. I was strongly advised by family to drop editing until I was old and mature enough to use it more wisely (not that I edited unconstructively under the 3 original accounts, just that I was a bit young). I recently noticed that they are still floating around, and was wondering if perhaps "right to vanish" or "cleanstart" could be applied retrospectively, in part to erase the personal information. I will supply the user account names upon a response or suggestion here. dci | TALK 02:12, 2 December 2012 (UTC)

For clarifactory purposes, I did not edit using my current account until some time after I "retired" the other three; I was also not entirely aware that socks are frowned upon, and, to the best of my knowledge, didn't pretend that the three were unrelated. I would just like to have them "closed up" now that I've moved on. dci | TALK 02:42, 2 December 2012 (UTC)

You should probably enable email first. -- King of ♥ ♦ ♣ ♠ 04:21, 2 December 2012 (UTC)

I have done so. dci | TALK 05:27, 2 December 2012 (UTC)

• On second thought, I suppose being open here won't hurt, given that though one revealed my name, it revealed nothing else about me. this, this, that, and that are the ones in question; I probably will not continue the email listing. dci | TALK 16:57, 2 December 2012 (UTC)

• I've gone ahead and done the appropriate renames. I did this because there is no obvious problems with your current account and it seems unlikely that abuse with result from granting this request. Feel free to disable your email again, unless others thing otherwise. MBisanz ^talk 20:42, 2 December 2012 (UTC)

• Thanks for your assistance; however, the pages still come up when clicking the links. dci | TALK 23:45, 2 December 2012 (UTC)

•  Done King of ♥ ♦ ♣ ♠ 23:56, 2 December 2012 (UTC)

• Your assistance is much appreciated! Thanks again to both of you, dci | TALK 00:06, 3 December 2012 (UTC)

Now that the proposal has passed in support, are we giving a grace period for admins who would permanently lose adminship under the proposal? I know this was discussed, but never came to a conclusion. --Rschen7754 01:08, 3 December 2012 (UTC)

And notification. Fairness dictates that those affected are notified, with a reasonable period for action. (I now see that this is the plan)--SPhilbrick(Talk) 13:05, 3 December 2012 (UTC)

Sorry, I only saw the section below and not this one. I agree we need a short grace period and no one seemed really opposed to the idea of non-canvassing notice at the discussion. The message that I've asked Mabdul to send to those affected would give them until the end of the year (about 25 days) to request return of the tools. MBisanz ^talk 13:09, 3 December 2012 (UTC)

Thanks for handling this. I was envisioning a minor mess if a year from now, someone asks for their bit back, and learns a new policy applies to them, but they were never informed. --SPhilbrick(Talk) 14:05, 3 December 2012 (UTC)

Exactly, I'd rather deal with any edge cases now, while people are current with the discussion and can explain how their views should be interpreted, then wait and risk confusion. Once these notices are done, I'll make another notice to put desysopped admins who are not yet disqualified by reason of inactivity on notice as to the change, but that can wait a few days. MBisanz ^talk 14:40, 3 December 2012 (UTC)

While I very much agree with the proposed grace period, I also don't have a problem if that didn't exist. If someone haven't edited for at least 3 years, then they have to expect that some policies would have change and new policies created. -- KTC (talk) 16:24, 3 December 2012 (UTC)

I normally would agree that users are expected to remain current with policy and can't expect it will remain static in their absence, but it was specifically communicated to them at the time of their desysopping that it would not be permanent and it was a longstanding policy of the type that people wouldn't expect to change (like how we had to do so many NFCC notifications back in ~2007). I thought about doing the notifications before the RFC closed so that it wouldn't be a grace period, but someone rightly pointed out that it could be seen as canvassing, so this way seemed preferable. MBisanz ^talk 16:28, 3 December 2012 (UTC)

I suppose all the users who have been gone between 1 and 3 years should be notified, and the notices used changed too... --Rschen7754 16:57, 3 December 2012 (UTC)

Yep, that's my plan for the middle of December. Unless you have time and interest before then. MBisanz ^talk 17:16, 3 December 2012 (UTC)

FYI: Delivering job was finished. All former admins (listed at Wikipedia talk:Administrators#Notifications) were informed. mabdul 23:54, 3 December 2012 (UTC)

Thank you Madman. MBisanz ^talk 00:00, 4 December 2012 (UTC)

All desysopped admins have been notified of the change. Policy has been changed (presumably) and the monthly notice should be changed, so all future desysops should be on notice as to the effect. MBisanz ^talk 02:21, 4 December 2012 (UTC)

Has the notification also been sent by email? WJBscribe (talk) 00:38, 5 December 2012 (UTC)

It has not. I confused Madman and Mabdul and contacted the latter instead of the former. I could contact Madman and ask him to do it if you think it would be prudent. MBisanz ^talk 02:52, 5 December 2012 (UTC)

Per this RfC the community has agreed to the following policy changes regarding administrators and bureaucrats:

1. Any admin that voluntarily, involuntarily, or due to inactivity, had their bit removed must wait 24 hours upon requesting them back to allow for a thorough examination. Any discussion currently going on regarding resysopping of the editor in question must be concluded first before any action be made.
2. Regardless of how or why the tools were removed, if an editor makes 0 edits throughout a continuous three years, they are required to go through a reconfirmation RfA, should they wish to have their tools back. That means a total of 3 uninterrupted years must have passed, with 0 edits from this user, for a reconfirmation RfA to become mandatory if the user wishes to have their tools back.

The following changes in the appropriate policy pages will be made to reflect this consensus.—cyberpower _Online^{Merry Christmas} 01:17, 3 December 2012 (UTC)

This is good and I'm glad to see these changes. I'm going to notify Mabdul to get notices sent out to those who are effected by this change before the policy is edited, so they can request the bit back if they want. MBisanz ^talk 04:19, 3 December 2012 (UTC)

"Any discussion currently going on regarding resysopping of the editor in question must be concluded first before any action be made." - we'll need to be vigilant against filibustering. --Dweller (talk) 13:02, 4 December 2012 (UTC)

[1] Gerrymandering would have been somewhat more fun and interesting, especially to see how it would happen on Wikipedia. =) Ks0stm ^{(T•C•G•E)} 13:20, 4 December 2012 (UTC)

{{discussion top}} works wonders. MBisanz ^talk 13:11, 4 December 2012 (UTC)

I have started a RFC regarding allowing bureaucrats to remove the bureaucrat bit, and regarding the regranting of the bureaucrat bit (to bring it into line with the recently-passed policies for administrators). Please see Wikipedia talk:Bureaucrats#2012 bureaucrats RFC. --Rschen7754 01:47, 3 December 2012 (UTC)

Proposal has been withdrawn. Useight's Public Sock (talk) 17:28, 3 December 2012 (UTC)

only part of it has. --Rschen7754 17:30, 3 December 2012 (UTC)

Indeed. Thanks for the clarification. Useight's Public Sock (talk) 16:15, 4 December 2012 (UTC)

I edited heavily between 2004 and 2010 and was admin from 2005. I have not been active recently but would like to resume. I am responding to the notice on my talk page that i need to request reactivation of my adminship. What's the procedure? Thanks. alteripse (talk) 05:06, 4 December 2012 (UTC)

Since you were active in the last three years, the policy change shouldn't affect you. I expect a bureaucrat to come by any minute now. -- King of ♥ ♦ ♣ ♠ 05:11, 4 December 2012 (UTC)

The procedure is that we wait 24 hours and unless someone presents evidence that you were desysopped under a cloud, you get the tools back. However, as King of Hearts said, as long as you remain active, you can request the tools back a anytime. It's only if you are inactive for three years while desysopped that you would lose the ability to request return. MBisanz ^talk 05:17, 4 December 2012 (UTC)

OK, I'll resume. Perhaps I misunderstood the notice of "desyssoping" on my Talk page. It seemed like something had been deactivated for me and I needed to request reactivation. alteripse (talk) 14:36, 4 December 2012 (UTC)

Okey, someone will get to it this evening then. Yeah, it wasn't a notice of desysopping, just a notice that policy had changed so that desysopping become permanent after a period of inactive time. Good to see you back. MBisanz ^talk 14:38, 4 December 2012 (UTC)

A kindly note if I'm not around when all these resysops are done, please don't forget to update WP:FORMER and WP:RESYSOPS. Thanks. MBisanz ^talk 16:34, 4 December

I confirm no evidence of a cloud. --Dweller (talk) 19:24, 4 December 2012 (UTC)

Thanks. alteripse (talk) 10:51, 5 December 2012 (UTC)

•  Done --Dweller (talk) 13:40, 5 December 2012 (UTC)

I gave my bit up voluntarily a few months back to concentrate on writing articles and other things. Here's my desysop request. After my time away, I'm feeling recharged and ready to help out in admin areas again, so if nobody has any objections I'd like to be an administrator once more. Cheers, BigDom (talk) 11:45, 4 December 2012 (UTC)

Looks fine to me. Someone will do after the 24 hour waiting period. MBisanz ^talk 12:51, 4 December 2012 (UTC)

No clouds on the horizon or pending controversies at the time of departure known to me. Newyorkbrad (talk) 14:37, 4 December 2012 (UTC)

No clouds I'm aware of. ···日本穣^? · 投稿 · Talk to Nihonjoe · Join WP Japan! 17:01, 4 December 2012 (UTC)

 Done MBisanz ^talk 14:49, 5 December 2012 (UTC)

I was inactive from September 2009 to August 2012, nearly 3 years. I have not contributed nearly as much as I used to, and I doubt I will be taking many administrator actions in the short term. Nonetheless, I would like the admin bit back to be able to help out here and there. —Remember the dot ^(talk) 02:34, 5 December 2012 (UTC)

Looks uncontroversial to me. Welcome back. If no-one finds an issue in 24 hours from your request, you should get your tools back. --Dweller (talk) 13:54, 5 December 2012 (UTC)

I recollect no reason to deny this request. MBisanz ^talk 14:52, 5 December 2012 (UTC)

Not seeing any issues here. ···日本穣^? · 投稿 · Talk to Nihonjoe · Join WP Japan! 17:17, 5 December 2012 (UTC)

No problems from this quarter. The Rambling Man (talk) 17:40, 5 December 2012 (UTC)

 Done bibliomaniac15 02:29, 6 December 2012 (UTC)

Thank you! —Remember the dot ^(talk) 03:04, 6 December 2012 (UTC)

Doing a rename, I now get the following notice:

User centralauth-renameuser-merged has been migrated to the unified login system. Renaming it will cause the local user to be detached from the global one. User $2 is reserved for a global account.

I think the changeover today reassigned some variables. MBisanz ^talk 23:34, 3 December 2012 (UTC)

I tried changing the $2 at MediaWiki:Centralauth-renameuser-reserved to a $1, but it just spat out the name of the MediaWiki: page (centralauth-renameuser-reserved), and I even tried changing it to $3 and $4, and it gave nonsense. So I'm not sure this can be fixed by fiddling with MediaWiki: pages, but maybe someone who knows what they're doing better than me could fix it that way. Maxim_(talk) 23:46, 3 December 2012 (UTC)

Could someone file a Bugzilla for this? It's still not fixed. MBisanz ^talk 21:46, 5 December 2012 (UTC)

I filed a request at Bugzilla:42788. MBisanz ^talk 17:00, 6 December 2012 (UTC)

I requested removal of sysop rights in March 2010. I hope to have more time now to contribute, so please re-enable the tools if you would. Tom Harrison ^Talk 15:49, 4 December 2012 (UTC)

Woah, three people requesting re-sysop in the same day? Nice. Anyway, there is a 24 hour waiting period, so as long as everything checks out, you will be re-sysopped after that. Useight's Public Sock (talk) 16:20, 4 December 2012 (UTC)

I did notify all 460 desysopped admins of the change in policy yesterday. Not shocking that it nudged some out of their slumber. MBisanz ^talk 16:24, 4 December 2012 (UTC)

I've scanned a fair bit of complex ancient history from March 2010 and I don't find any reason to withhold the bit, after the 24 hour wait period. --Dweller (talk) 19:30, 4 December 2012 (UTC)

I agree with Dweller's review. MBisanz ^talk 19:30, 4 December 2012 (UTC)

I also concur. The Rambling Man (talk) 19:50, 4 December 2012 (UTC)

No problems I can see. ···日本穣^? · 投稿 · Talk to Nihonjoe · Join WP Japan! 17:16, 5 December 2012 (UTC)

 Done Finding no reason to not re-grant, I have resysopped Tom. MBisanz ^talk 18:31, 5 December 2012 (UTC)

I have a pretty damn good reason concerning his more recent behavior, but I didn't know about this until after his resysopping. Can me weighing in on the request make any difference at this point?--The Devil's Advocate (talk) 07:09, 6 December 2012 (UTC)

I think what's done is done, but if you haven't already voiced your concern to the user in question, you could bring it up to them. bibliomaniac15 08:16, 6 December 2012 (UTC)

Perhaps another crat can say something, because what I have in mind is pretty serious and concerns recent behavior regarding the very matter he mentioned in his resignation back in 2010.--The Devil's Advocate (talk) 08:57, 6 December 2012 (UTC)

There's nothing for a crat to say currently. You've said you have grave concerns about the user. I'm not sure what we can say in response to that other than what bibliomaniac already said. --Dweller (talk) 11:19, 6 December 2012 (UTC)

I agree with Dweller. Besides userrights granting being a one-way street, recent behavior isn't taken into account when re-granting. Also, you haven't disclosed what the alleged present bad behavior is, which I would suggest you do to Arbcom if you feel it is of sufficiently grave nature as to interfere with the execution of his admin duties. MBisanz ^talk 13:41, 6 December 2012 (UTC)

What about a reconfirmation RfA? Could that be done? Is that something that he would have to agree to do since he has already been resysopped?--The Devil's Advocate (talk) 16:06, 6 December 2012 (UTC)

No, "reconfirmation" RFAs are only done if the user himself submits himself to one. The bureaucrats cannot force one on him. Reaper Eternal (talk) 16:08, 6 December 2012 (UTC)

If an admin submits himself to a reconfirmation RFA, a bureaucrat would close it. The decision of submission to a reconfirmation RFA is solely with the admin. The bureaucrats cannot compel or initiate a reconfirmation RFA. MBisanz ^talk 16:13, 6 December 2012 (UTC)

(ec) As mentioned above, if you feel something serious was missed during the 24-hour wait period, the only real option is to submit a case to ArbCom. The tasks done by bureaucts are quite limited and relatively rigid, so ArbCom is really the only route available here if you feel the situation has sufficient gravity. Useight's Public Sock (talk) 16:22, 6 December 2012 (UTC)

If you have reason to believe that the admin resigned under a cloud, really the only reason to turn down a resysop request, then you might want to ping the admin on his/her talk page and explain your reasons before escalating it to ArbCom. If there was no cloud, then there's not much you can do (since any recent actions would, obviously, not involve the misuse of admin tools).--regentspark (comment) 16:55, 6 December 2012 (UTC)

The policy at WP:INACTIVITY mentions only inactive admins. I seem to recall a discussion about what to do with inactive crat accounts and I think it was decided they should be "decratted" too, but the policy really ought to include this, preferably with a link to the consensus. Clarity welcomed. --Dweller (talk) 00:22, 6 December 2012 (UTC)

Found it here. Might be worth a cross link? --Dweller (talk) 00:24, 6 December 2012 (UTC)

There's also a related RFC linked to a few sections above. --Rschen7754 01:42, 6 December 2012 (UTC)

Perhaps a cross-link at WP:INACTIVE, as well. Or just some text at the top noting that the policy is also applicable to bureaucrats. Useight's Public Sock (talk) 16:06, 6 December 2012 (UTC)

Hello! I used to get involved a fair amount, now just pop back in every now and again - one day I hope I'll get more heavily involved again, so would appreciate being "resysopped" if that's okay so I can help out more when I do come back. I've never been involved in any particularly unusual controversy and I promise I'm me! Cheers! Khendon (current rights · rights management · rights log (local) · rights log (global/meta) · block log) Khendon (talk) 20:51, 7 December 2012 (UTC)

I see no prior problems, so looks good after 24 hours. MBisanz ^talk 23:24, 7 December 2012 (UTC)

I don't see any concerns, either. ···日本穣^? · 投稿 · Talk to Nihonjoe · Join WP Japan! 04:56, 8 December 2012 (UTC)

"one day I hope I'll get more heavily involved again" - if you do ever intend to return to actual contributing why not then ask the community for your advanced permissions back , requesting them now with such a declaration seems simply wanting them for the sake of having them, not to use them, you "hope one day" - This user has not used his admin advanced permissions since 2006 and then he has only ever used them seven times - see Special:Log/Khendon - basically as an administrator he is absolutely unexperienced in the last six years - and I object to his being given advanced permissions with such a history and such a statement that "one day he hopes to get more heavily involved again" - as an admin he has has never been involved at all - Can a link be provided ot his RFA as Wikipedia:Requests for adminship/Khendon seems a redlink - Thanks - Advanced permissions should not be given to users without there being a clear benefit to the project, in this request and coupled with the users editing history there is no clear benefit to the project and the users contributions with advanced permissions are so minimal and so historic he should be advised to first return to contributing and after some time return to the community to request support for his obtaining advanced permissions and tools. Youreallycan 06:03, 8 December 2012 (UTC)

Khendon's gaining of adminship preceded the RFA system. He was made admin as a result of a request on the mailing list in November 2002. I agree his lack of activity is of concern, but I don't think the bureaucrats have any discretionary ability in regards to this.-gadfium 06:20, 8 December 2012 (UTC)

Thank you Gadfium for the detail . I think there is community support in the recent discussions that the bureaucrats' do have a discretionary ability in such a clear case as this. - Youreallycan 06:24, 8 December 2012 (UTC)

There is no such discretion at all. Recent discussions concerns only whether there were a cloud when adminship was resigned, and not granting of adminship without a new RFA for those who have had zero edits for 3 years. Current policy and consensus clearly dictate that crat must return adminship rights up to the 3 years mark assuming no cloud once the policy becomes active. With Khendon, who have been editing, the inactivity changes doesn't apply anyway. -- KTC (talk) 10:59, 8 December 2012 (UTC)

(edit conflict)While you have a decent argument, the other side is that we grant the mop to members of the community we trust. Inactivity does not diminish that trust. To the extent an admin has lost track of changes in policy/practice, they can familiarize themselves before actually wielding the mop. That is not really the issue though; as far as I know, the consensus for allowing inactivity de-sysops also requires returning the bit on request, with discretion only to determine if there was a cloud. Now we have the long term inactivity, and identity doubt justifications, but that is it. There is no consensus for additional denials. If you want to change that, an RFC would be the place. (Though of course there is nothing wrong with asking the editor to consider your argument and withdraw the request) Monty₈₄₅ 06:25, 8 December 2012 (UTC)

That is a very fair point. This request really followed from the new policy of permanent deactivation - I was happy to be temporarily suspended, but I'm proud of my (modest) contribution to wikipedia from the early days and I would like to retain the association. I really do intend to properly "come back" one day, and I like to think the same principles of wikipedia will apply even if the details of the processes and policies have changed. All that said, if there's a consensus that this is an inappropriate request I'll happily withdraw it. Khendon (talk) 09:09, 8 December 2012 (UTC)

Well, it's appropriate per policy, but if you decide to reactivate your adminship, please take things slowly; there's a lot that has changed on this site since 2002. --Rschen7754 11:06, 8 December 2012 (UTC)

Under present policy, the grounds for denying a resysop request are:

1. User has been inactive for three year period of time which includes or is subsequent to the date of desysopping (details vary);
2. User resigned the tools in a manner so that it appears he did so to avoid scrutiny that has a high probability of leading to desysopping (such as a pending RFC or RFAR);
3. The reviewing bureaucrat is not satisfied that the person requesting resysopping is the original owner of the account or that the account's security has not been compromised;
4. Subsequent to desysopping, the user engaged in conduct of an extreme and egregious nature such that no reasonable person could doubt they would have been desysopped should they have done it while an admin (socking, severe copyvios, etc.).

Those are the only reasons provided in policy to deny a resysop request and the community explicitly rejected giving the bureaucrats discretion to adopt further policies in this area.

I've reviewed Khendon and it appears to me that none of the above reasons apply to him. Absent evidence to the contrary that is disclosed in the next five hours, it would be appropriate and required under policy to resysop him. MBisanz ^talk 16:52, 8 December 2012 (UTC)

I've resysopped him as the waiting period has elapsed without new evidence coming forward. MBisanz ^talk 21:47, 8 December 2012 (UTC)

Thanks! As it happens, I'm thinking the "eventual" return I talked about might be now in any case :-) Advice about taking note of changes since I was last active fully noted. Khendon (talk) 00:17, 9 December 2012 (UTC)

A suggestion to propose clerking for RfA is currently being revisited. It has been suggested that bureaucrats might be the people to approve requests for 'clerkship'. If the proposal were to go ahead, would the bureaucrats be prepared to accept this minor additional task? For more background information, please see:

• Wikipedia talk:RfA reform (continued)/Clerks
• Wikipedia:RfA reform (continued)/Clerks
• Wikipedia:RfA Clerks noticeboard (draft)

Kudpung กุดผึ้ง (talk) 01:28, 8 December 2012 (UTC)

My personal view? Whatever tasks the community decides the Crats should take on, I'm happy that we should take on. --Dweller (talk) 08:53, 10 December 2012 (UTC)

If the community wants clerks, I'll happily take on whatever process it creates. I do think though that we don't need RFA clerks, given the low level of activity at RFA. MBisanz ^talk 12:50, 10 December 2012 (UTC)

The RFA process I've been working on makes reasonably good use of Clerking (✉→BWilkins←✎) 13:03, 10 December 2012 (UTC)

The purpose of clerks in both the arbitration and checkuser processes is to do work that the arbitrators and checkusers would ideally do for themselves if they had (a lot) more time. I don't see how that applies itself to our situation, as there is no shortage of bureaucrats. There are many bureaucrats like myself that could easily pick up the slack at RfA if there were less active bureaucrats. Of course, as MBisanz said, if this is what the community wants then I would happily go with it. --(ʞɿɐʇ) ɐuɐʞsǝp 13:34, 10 December 2012 (UTC)

• I think it is far from clear that the community wants another layer of hats for people to collect on wikipedia. This seems a severe case of cart before horse. Or perhaps an attempt to garnish support by trying to obtain a veneer of 'crat legitimacy to the idea. No ta. Spartaz ^Humbug! 14:06, 10 December 2012 (UTC)

• That is why this isn't a hat and doesn't use a lot of bureaucracy, it just barely formalizes what should already be happening, and makes it clear that non-admin are just as welcome to help as admin. Dennis Brown - 2¢ © Join WER 14:10, 10 December 2012 (UTC)

• If that is a point that needs to be made (and I'm not sure it is, I thought this was already obvious), then there are much simpler ways to make it than to introduce official clerking to RfA. --(ʞɿɐʇ) ɐuɐʞsǝp 16:30, 10 December 2012 (UTC)
• Honestly Dennis, are you really that unworldly? If you call it a clerkship than its a hat and a status that gives users the chance to lord it over other users. No matter how well intentioned you are the obstacle that is human nature will still subvert this to the detriment of the project. Spartaz ^Humbug! 16:36, 10 December 2012 (UTC)

• Surely you can find a less abrasive way to express yourself. That you have a lower opinion of human nature than I do doesn't make it factual, just opinion. Clerking would be a simple thing, not requiring the person to be an admin. You make it sound bigger than it is. Dennis Brown - 2¢ © Join WER 18:54, 12 December 2012 (UTC)

• So in fact anyone could do it, if a comment or question was sufficiently out of line. Which the proposal acknowledges - on the face of it, this seems to be merely adding "focus". Which doesn't need to be approved by a crat, in my opinion. --Demiurge1000 (talk) 20:16, 12 December 2012 (UTC)

(od) Hmm. Warn users that their questions may be off-topic. Speedily remove such questions. Speedily remove uncivil !votes. Close the voting after 168 hours. None of these seem like clerical tasks to me. Not, in my opinion, a very good idea. --regentspark (comment) 16:39, 10 December 2012 (UTC)

• Can we get back on track please? This was a simple question asked of the 'crats on their board. It was not intended to be a parallel discussion on the merits of clerking. That discussion is elsewhere and has not even reached debate stage yet - that will happen when we have formulated a proposal. Thanks. Kudpung กุดผึ้ง (talk) 18:29, 10 December 2012 (UTC)

  I'm not sure that the question, as asked, is meaningful. Do bureaucrats get to decide what tasks they are willing or not willing to do? That decision should lie with the community. --regentspark (comment) 19:34, 12 December 2012 (UTC)

  Well, we all get to decide what to do or not do! If someone is thinking about assigning a new task to group X, it is courteous to ask group X if they'd mind doing it. (For my part, I agree with the other crats who've weighed in: I'd be happy to help with the new task if the consensus of the community is that it's needed and they want the crats to do it.) 28bytes (talk) 19:38, 12 December 2012 (UTC)

  I'll grant you the courtesy part. But I'm not sure it is particularly meaningful since the set of bureaucrats can change over time. I guess I misunderstood this as a 'permission to go ahead' thing. --regentspark (comment) 20:03, 12 December 2012 (UTC)

  Agreed, the community does not need the permission of the current crats to expand, limit, or otherwise redefine the role, although a heads-up that they're considering it is always appreciated. 28bytes (talk) 20:39, 12 December 2012 (UTC)

I agree with Deskana. Can't see why clerking would be necessary considering the low number of RFAs, but I wouldn't mind going along with it, if that's the consensus. bibliomaniac15 19:26, 12 December 2012 (UTC)

This is why it needs to not be a major program, just a simple thing with the goal of only keeping RfAs consistent. There is a problem with that and a very informal system is the least offensive way I can think of to maintain consistency. Whatever the community decides the rules are, I really don't care, as long as they are exercised in every RfA. Dennis Brown - 2¢ © Join WER 19:39, 12 December 2012 (UTC)

• I would like to thank the bureaucrats for their input. Your comments will be taken into consideration if and when a proposal for RfA clerking goes forward. Kudpung กุดผึ้ง (talk) 23:32, 12 December 2012 (UTC)

Hey guys... I got up this morning to find that my gmail/Google account had been hacked; so it's prolly best if you remove my bits for a bit until I make sure everything is secure. Also - since I'm pretty sure it's wiki related, who should I email? Arbs? I think I have the Google account back under control, but I'm pretty sure this was wiki related. Looks like both posts and logs are ok (mine), but I'd rather play it safe. I'll request the bits back once I make sure everything is secure. Thanks folks. — Ched :  ?  12:05, 14 December 2012 (UTC)

Desysopped. Arbcom or the WMF would be the best people to contact. MBisanz ^talk 12:44, 14 December 2012 (UTC)

Thanks Matt. (do you ever sleep? :)). I'll get back to you in the next couple days. — Ched :  ?  13:12, 14 December 2012 (UTC)

Can I block you Ched? Can I? Can I? (✉→BWilkins←✎) 13:20, 14 December 2012 (UTC)

LOL ... I'm tellin ya BW, this whole "cloud computing" and Windows 8 and tying accounts together really has me goin back to school. Starting to think I really miss the old rotary dial phone days. What's REALLY sad is that my first thoughts were "OMG - that's tied to my wiki admin account" (it's a freakin website .. wtf?). At least I have some tech tracing skills and tools - so I can get some specific info to Arbs/WMF. Hey - block if you must - but I haz open proxy and hot spot stuff skillz ... lol. .... sigh - technology huh? — Ched :  ?  13:45, 14 December 2012 (UTC)

Hmm, that's interesting. I had an e-mail in my junk Gmail account this morning tellig me that Google prevented a hijacker from getting into my account. The attacking IP address was from Taiwan. Did you also get an e-mail like that? Useight's Public Sock (talk) 14:47, 14 December 2012 (UTC)

Hey Useight .. yep, and a few other things too. The thing is that the last couple days I've been setting up some cloud stuff, and tying a new Windows 8 laptop and droid tablet to it too - so the timing had me a bit concerned. Just glad I didn't login to Wiki and see that I had deleted the main page and blocked Jimbo, Risker, and NYB .. so after I get some security stuff tightened down I stop back here. You folks have a good weekend. — Ched :  ?  21:10, 14 December 2012 (UTC)

Noting that a checkuser shows nothing suspicious whatsoever, though I'd still advise the normal steps of a through spyware/malware check and a new password before asking for your mop back. Courcelles 01:31, 15 December 2012 (UTC)

I'm still willing to block his sorry ass as per WP:GOTHACKED ;-) (✉→BWilkins←✎) 01:43, 15 December 2012 (UTC)

I cannot confirm the gmail incident as my spam folder is spotless and I have gotten no suspicious emails on that account. Could you two tell from who the email was from. I can do some digging around to come up with some answer. I have a feeling that your accounts were not hacked, but rather an attempt to get you to spill your password and allow yourself to get hacked. — Preceding unsigned comment added by Cyberpower678 (talk • contribs) 04:30, 15 December 2012 (UTC)

No, it's the real deal, I'm sure. The e-mail telling me about it was from "accounts-noreply@google.com" and my Gmail account has a red bar across the top that says, "Warning: Google prevented a suspicious attempt to sign in to your account. Was it you?" Not to mention that the same e-mail address also sent the e-mail to my backup Hotmail account that I told Gmail to use if I forget its login credentials. Fortunately, this particular Gmail account is my junk one that I use to send résumés, so I'm not worried about it. And it looks like the hacker didn't get in. Useight's Public Sock (talk) 15:32, 15 December 2012 (UTC)

Ched didn't sign his comment! Clearly we should take this as a sign that he has been hacked and should be blocked. EVula // talk // ☯ // 05:45, 15 December 2012 (UTC)

That wasn't Ched's comment. Reaper Eternal (talk) 05:59, 15 December 2012 (UTC)

So you say. Maybe you got hacked, too! ···日本穣^? · 投稿 · Talk to Nihonjoe · Join WP Japan! 19:27, 15 December 2012 (UTC)

The following changes have been made to the policy according to the community:

1. De-crated editors must wait 24 hours upon requesting the bit back to allow the community to assess if the removal of the tools was under the cloud. This change will take effect immediately.
2. If a former crat has been inactive, that is absolutely no edits or logged actions, for 3 total years regardless of how or when the bit was removed they are required to go through a mandatory RfB. This change will take effect February 1, 2013. Former crats should be notified of this change before policy takes effect.

Appropriate changes to the policy pages should be made to reflect this change.—cyberpower _Online^{Merry Christmas} 16:01, 20 December 2012 (UTC)

Life has moved forward and my commitments have changed. I would like the admin tool returned please. Viridae^Talk 11:21, 19 December 2012 (UTC)

Welcome back. I'm not aware of any circumstances that would prevent me actioning this request. However, it has become standard practice for bureaucrats to wait 24 hours to make sure that no one has something to bring to our attention that we are not aware of, or have overlooked. Please bear with us. WJBscribe (talk) 16:55, 19 December 2012 (UTC)

Yep, nothing to be concerned about here. As we 'crats are now less trusted members of the community than we were, we now have to wait. While I'm guessing it's not a big deal for you, I'm still sorry about that. The Rambling Man (talk) 19:34, 19 December 2012 (UTC)

Thirded. --Dweller (talk) 22:27, 19 December 2012 (UTC)

"less trusted members of the community"? .. I apparently missed a HUGE discussion. — Ched :  ?  22:45, 19 December 2012 (UTC)

I suspect TRM is referencing the recent Polarscribe RFAR where the Arbcom showed themselves willing, and even eager, to second-guess the crats when they think we made an erroneous decision. MBisanz ^talk 22:52, 19 December 2012 (UTC)

I suspect the same thing. And yes, it was a very huge discussion. ···日本穣^? · 投稿 · Talk to Nihonjoe · Join WP Japan! 08:24, 20 December 2012 (UTC)

There certainly was no comment that Buro's were "less trusted" - the community merely put into law what was originally in-practice because of kerfluffle when someone didn't follow that practice. (✉→BWilkins←✎) 10:56, 20 December 2012 (UTC)

I don't agree, I think it was pretty clear the community said we don't trust you enough to make the call so we are going to mandate it. -DJSasso (talk) 13:30, 20 December 2012 (UTC)

Stating that we want the opportunity to express any reservation or history that the crats might not been aware of doesn't mean we don't trust them. KTC (talk) 13:34, 20 December 2012 (UTC)

Stating that you don't trust them to do that check for themselves certainly does say that. -DJSasso (talk) 13:40, 20 December 2012 (UTC)

I for one welcome input on these matters. Not everything is always as it seems. Yes, it looks as if nothing bad would have happened had I returned Viridae's tools immediately. But the weight has resulted in nothing bad happening either. It's good to take a bit of time to make sure we get these things right. WJBscribe (talk) 23:44, 20 December 2012 (UTC)

Yes, 'crats are not as trustworthy as they used to be, hence the policy change that 24 hours should elapse before a re-sysop. This has devalued the position of 'crat, for better or for worse. That's the kind of thing I was referring to. Not much left for 'crats to do these days, renames can be basically automated, re-sysops are subject to community panic, sysops are few and far between.... Last 'crat out turn the lights out please. The Rambling Man (talk) 19:05, 20 December 2012 (UTC)

Sorry, but I disagree. TRM, you and I became bureaucrats at around the same time, and I for one I don't think our role (or how the community regards us) has changed much. The 24 hr rule is designed to make sure we have all the information we should and that nothing has been overlooked - it's common sense. Once that time has elapsed, any of us can make the decision, there's not requirement of a group decision between us etc. We have to operate within boundaries, and if we get it wrong there will be consequences. Like for anyone else. I really don't think anything has changed. Bureaucrats have a some additional rights, which we exercise within defined parameters. Sorry you're disillusioned with how things are, but I don't really see any significant change in how the community regards bureaucrats. WJBscribe (talk) 23:44, 20 December 2012 (UTC)

No hurry. Thanks. Viridae^{DON'T PANIC} 00:02, 20 December 2012 (UTC)

I see no issues here. ···日本穣^? · 投稿 · Talk to Nihonjoe · Join WP Japan! 08:24, 20 December 2012 (UTC)

 Done - a few minutes early, because I messed up on UTC. Please excuse me. --Dweller (talk) 11:05, 20 December 2012 (UTC)

Thanks. Viridae^{DON'T PANIC} 08:19, 21 December 2012 (UTC)

Hi, I was told to post this request here before time expires due to my inactivity. Thank you for considering, --PeaceNT (talk) 20:41, 20 December 2012 (UTC)

I can see no controversial circumstances but you have been inactive for more than 3 years. See Wikipedia_talk:Administrators#Restoration_of_the_tools_.28proposal.29. Fellow crats, has this new policy come into effect yet? I can't see any mention of a wait period there or on the policy page (Wikipedia:ADMIN#Lengthy_inactivity) --Dweller (talk) 21:18, 20 December 2012 (UTC) And by the way, you are definitely welcomed back! Good to have you. --Dweller (talk) 21:20, 20 December 2012 (UTC)

It was decided by the crats that the 3 year takes effect New Year's Day to allow those who have been inactive for more than 3 years to request the tools back as they left the project thinking, they would always have the ability to request it back.—cyberpower _Online^{Merry Christmas} 21:23, 20 December 2012 (UTC)

Smashing. So, I have no objections to PeaceNT being resysopped after 24 hours from the time of the request. --Dweller (talk) 21:25, 20 December 2012 (UTC)

Me neither. Looking forward to 2013 already. The Rambling Man (talk) 21:51, 20 December 2012 (UTC)

I agree. He was one of the admins I notified of the short grandfathered period and he made the request before that period expired. MBisanz ^talk 01:10, 21 December 2012 (UTC)

 Done MBisanz ^talk 22:38, 21 December 2012 (UTC)

Thanks everyone --PeaceNT (talk) 02:36, 22 December 2012 (UTC)

Hi all, I'm trying to get back into the swing of things after an almost 2 year break from Wikipedia, and so I'd like to be re-adminned (but not re-bureaucratted). I retired because life was getting too busy for me and I needed a break. Thanks in advance! (X! · talk)  · @814  ·  18:32, 12 December 2012 (UTC)

Welcome back! Apparently there's a 24-hour wait now, but once that's up I'll re-flag you if no one beats me to it. 28bytes (talk) 18:44, 12 December 2012 (UTC)

Good luck, X! Jared Preston (talk) 18:48, 12 December 2012 (UTC)

I concur with 28 that I know of nothing that would preclude resysopping (or re-cratting if he wanted it) after the 24 hour waiting period. MBisanz ^talk 18:51, 12 December 2012 (UTC)

Thirded. Your return is most welcome. --Dweller (talk) 06:29, 13 December 2012 (UTC)

Oh man, if I was ever tempted to go rogue with a repromotion, now's the time. :) Welcome back, man. EVula // talk // ☯ // 16:49, 13 December 2012 (UTC)

I agree with everyone else: there are no issues with this one, and certainly many positives. Welcome back, X! ···日本穣^? · 投稿 · Talk to Nihonjoe · Join WP Japan! 17:00, 13 December 2012 (UTC)

24 hours are up, give him the bit back. Wikipedia is nothing without X!—cyberpower _{Limited Access}^{Merry Christmas} 18:09, 13 December 2012 (UTC)

Ahem, 23 more minutes. MBisanz ^talk 18:27, 13 December 2012 (UTC)

You have my official permission, as GodKing-in-waiting of Wikipedia, to resysop 21 minutes early. --Floquenbeam (talk) 18:30, 13 December 2012 (UTC)

 Done MBisanz ^talk 18:32, 13 December 2012 (UTC)

Hey, wow! X! is back. That's good news. Useight's Public Sock (talk) 19:48, 13 December 2012 (UTC)

Exactly 24 hours to the minute. Impressive. (X! · talk)  · @903  ·  20:39, 13 December 2012 (UTC)

Additional unrelated comment: I made this resysop request exactly 6 years (to the day) after I joined Wikipedia. Interesting. (X! · talk)  · @910  ·  20:50, 13 December 2012 (UTC)

We created our accounts ten days apart? That's a crazy happenstance. Useight's Public Sock (talk) 22:46, 13 December 2012 (UTC)

December 2006 was a very popular time for signing up, apparently. 28bytes (talk) 04:14, 14 December 2012 (UTC)

Three eventually-to-become bureaucrats created accounts within a twelve day period? Wow. Is there a chart out there somewhere that shows a month-by-month count of number of accounts created? Useight's Public Sock (talk) 14:53, 14 December 2012 (UTC)

I was a March 2K6 Wikibaby (✉→BWilkins←✎) 12:52, 14 December 2012 (UTC)

You should refer to this, Useight. bibliomaniac15 19:44, 14 December 2012 (UTC)

The first thing I noticed from that is that the youngest crat account is from 2007. Old men's club! KTC (talk) 20:02, 14 December 2012 (UTC)

Interesting that "Sort by creation date" gives January 2002, June 2002, October 2002, February 2002, November 2002, February 2002... 28bytes (talk) 20:40, 14 December 2012 (UTC)

2002 was a really weird year. I remember the Smarch weather was especially bad. EVula // talk // ☯ // 20:57, 14 December 2012 (UTC)

It's probably a MediaWiki bug dealing with really old accounts. If you look at this, all the early accounts are out of order. Legoktm (talk) 21:22, 14 December 2012 (UTC)

Before late 2005, there was no log entry made when a user registered, so there was no date of registration. After 2005, all accounts have a log entry for their registration. For people who registered pre-September 7, 2005, the software estimates a registration date from the date of their first edit. But, special:listuser sorts based on User ID, which is and always has been assigned at the time of registration. For example, my User ID means I registered in mid-2004, but I didn't make my first edit until mid-2005, which is the date listuser assigns as my registration date. MBisanz ^talk 22:38, 14 December 2012 (UTC)

Also, the date of the first edit for many early users is wildly inaccurate due to a bug mentioned in the second-last paragraph of the documentation on moving over a redirect. Graham87 16:39, 15 December 2012 (UTC)

The most accurate method of estimating a user's creation date before 2005 is to look at the users table on toolserver. At some point, the creation dates got filled with the first edit fields for the pre 2005/09/07 users, so you can easily look at the users table on toolserver sorted by user_id and find the closest user after you with the earlier creation date and assume your account was created before them. That is how I know that for example my account is from autumn 2003, tho I can't remember the month. This does not work well for the first X users (where X is a relatively small number that I have long forgotten) because their user_id is not based on account creation but it's 100% random. Snowolf ^{How can I help?} 12:47, 20 December 2012 (UTC)

Those users are probably the first handful of users whose accounts were created after the Phase II software was installed. Dates of edits from January/February 2002 (and occasionally up to July of that year) are incredibly flaky, so that's why the creation dates from that period could seem random. If user ID numbers were in fact assigned randomly at any time, that field wouldn't have been a very good primary key at all. Graham87 15:07, 22 December 2012 (UTC)

They weren't assigned at random. My memory again fails me, I recall discussing the matter a few years ago with the user that has userid #1, I think there's was some db failure/corruption that forced a restore with some issue, or it happened in a migration or they weren't using userids as primary key to being with. I really can't recall the details but I'm pretty sure that at one point all of the first say, 1000 users got randomly assigned userids, which is why neither Jimbo nor Larry is user no 1 / 2. Snowolf ^{How can I help?} 03:01, 23 December 2012 (UTC)

1 is User:Damian Yerrick. MBisanz ^talk 03:05, 23 December 2012 (UTC)

Looked into the archives, I did point out to him that he was #1 but I guess the discussion was with somebody else, *shrugs* it's been too long I guess, I'm going gaga xD Snowolf ^{How can I help?} 03:08, 23 December 2012 (UTC)

Jreferee (talk · contribs) contacted me via email to request resysopping. He used email as he has forgotten his Wikipedia password and the email account associated with his Wikipedia account has been deactivated. While I figure out if and how we can verify the person who contacted me is the original Jreferee, I wanted to post here to start the 24 hour due diligence period. Thanks. MBisanz ^talk 15:44, 22 December 2012 (UTC)

Hmm, even if we could verify that the person is the original Jreferee, I'm not certain that we'd be able to reset their password to allow them to access their account. Although this is technically possible by WMF sysadmins, most are presently on a break for the Christmas holidays and even if they could, I'm not sure that they would, has this ever happened before? Thehelpfulone 15:52, 22 December 2012 (UTC)

I have the same concerns expressed by Thehelpfulone. Unless we can clear those hurdles, he may just need to create a new account and run a new RfA. ···日本穣^? · 投稿 · Talk to Nihonjoe · Join WP Japan! 15:55, 22 December 2012 (UTC)

If I can prove his identity and he passes due dilligence, my thought was to rename the present account out of the way and create a new account, which I would give sysop to. WP:RESYSOPS and WP:FORMER indicate that such moves are allowed by practice. MBisanz ^talk 15:58, 22 December 2012 (UTC)

I was going to say the same as MBisanz.—cyberpower _Offline^{Merry Christmas} 16:01, 22 December 2012 (UTC)

If it can be definitely established that this is the correct person, then I have no problem with that. This one just has more hurdles than most requests given that the editor in question can't access his account. ···日本穣^? · 投稿 · Talk to Nihonjoe · Join WP Japan! 16:07, 22 December 2012 (UTC)

Ok, I've managed to properly corroborate his story to verify his identity. The address of the person who emailed me this morning is the same as the email address used in this December 23, 2006 post to the wikitech mailing list. That mailing list post was claimed by User:Jreferee in this December 23, 2006 edit to the RefDesk. I find that to be sufficient corroboration to prove the person who emailed me this morning is User:Jreferee. Once the 24 hour review period expires, I'll rename the account, create a new account with the password mailed to him, and sysop that new account. MBisanz ^talk 18:07, 22 December 2012 (UTC)

That's impressive work, no doubt aided by the skills you've developed in your checkuser work! I'm going to ask a sys admin to see if they can reset the password or put in the new email address for that user account so that the user will still be able to keep their edits under one name, I'll post an update soon if I get a response. Thehelpfulone 18:27, 22 December 2012 (UTC)

Reedy (talk · contribs) just did it. So no need to rename once the 24 hours have passed. MBisanz ^talk 18:32, 22 December 2012 (UTC)

Reedy (talk · contribs)'s change didn't appear to take, so I did this again. --Ori.livneh (talk) 21:50, 22 December 2012 (UTC)

Bah, if somebody last edited in 2007, hasn't logged in so long that the password is long forgotten and the email address is no longer active then perhaps it would be proper to have them start editing again on a new account, gain the community's trust and then run for a new RfA. Snowolf ^{How can I help?} 20:27, 22 December 2012 (UTC)

At Wikipedia_talk:ADMIN#Notifications and Wikipedia:Bureaucrats'_noticeboard/Archive_26#Inactivity_proposal_for_admins_concluded, people generally agreed with a brief notification period to let people reclaim it if they would otherwise be affected by the new policy. MBisanz ^talk 20:31, 22 December 2012 (UTC)

I am aware it is allowed by policy. Merely commenting that an admin that stopped contributing 5 years ago when he was blocked for a spamming multiple pages and didn't bother to came back in 5 years probably should be active a little bit before requesting a sysop flag. Regardless, I am aware that this is merely a personal opinion and that the policy allows for such request. It merely reflects badly on the individual requesting this, and it is in no way the bureaucrats' fault. Snowolf ^{How can I help?} 20:34, 22 December 2012 (UTC)

I understand. But, we did just have a debate on it and the community rejected my more restrictive proposal on regranting in favor of the three year proposal, so I don't think there's support for a narrow interpretation, even if it would be logical. MBisanz ^talk 20:37, 22 December 2012 (UTC)

Yikes, this was a day before the admin left for good. This should definitely be examined. --Rschen7754 20:36, 22 December 2012 (UTC)

I saw a lot of edits right before they left and sent a flag up on crat-l asking for more help examining that aspect of it, once I had solved the verification part. MBisanz ^talk 20:37, 22 December 2012 (UTC)

I am not in any way advocating that you should disregard the policy and decline to resysop the user. I am merely noting my two $0.02 and it's more directed at the user and that other former admins who act like this than to the 'crats. I am in no way implying any criticism of your actions nor am I suggesting that my comments should influence your decisions. Snowolf ^{How can I help?} 20:40, 22 December 2012 (UTC)

Don't worry, I don't feel criticized. I know we're stuck with the current policies and I fully expect this particular matter to be examined before we regrant. MBisanz ^talk 20:42, 22 December 2012 (UTC)

I agree with Snowolf here, my experiences with Jreferee was mostly mixed but edited in good faith, but disappearing right after a 15 minute block. He probably purged his password because of that incident and got frustrated, but this should be considered more carefully before giving the tools right away. Secret ^account 20:55, 22 December 2012 (UTC)

The related thread is here on AN/I (shockingly, I commented on it and I don't even remember doing so) FWIW, his fifteen minute block wasn't entirely controversial; he was blocked for sending a list of administrators a link to a page to be categorized on. No admin actions or whatnot were the result of the block. Regards, — Moe Epsilon 21:13, 22 December 2012 (UTC)

The activity that led the block doesn't bother me so much, as it wasn't malicious even if it wasn't a good idea. It does raise yet one more issue of how the Crats define "under a cloud" if the editor leaves and is later de-bitted solely due to inactivity, although I gather that the "cloud" would be irrelevant in those cases. (assuming they didn't leave to avoid process) Dennis Brown - 2¢ © Join WER 21:16, 22 December 2012 (UTC)

I would use the standard of whether they became inactive to avoid scrutiny that has a high probability of leading to desysopping (such as a pending RFC or RFAR). I don't think a 15 minute block for excessive talk page messages would meet that threshold. MBisanz ^talk 21:32, 22 December 2012 (UTC)

In this case, I think the overwhelming majority would agree with your assessment here. The block was relatively trivial, and wasn't even a sanction really. The fact that he lost the account and password and stuff worries me a little, but I don't have a problem trusting you or the other Crats to have done due diligence in insuring this really is him. Like Sno, I worry about having the bit with no recent experience, but during this grace period, we knew we would get some of these, as they can't wait due to the 3 year portion of the policy. FWIW, I don't see any policy based reason to deny the bit. Dennis Brown - 2¢ © Join WER 22:04, 22 December 2012 (UTC)

I would support notifying admins in resysop requests like these that Wikipedia has changed since they left, and that they should read up on current policies and take things slowly to prevent further issues. --Rschen7754 22:07, 22 December 2012 (UTC)

Or in short, what TRM is doing. :) --Rschen7754 23:37, 22 December 2012 (UTC)

Procedurally, I'm sure this resysop is a mere 8 hours away. But, for my sake, just a question: he made precisely zero edits here in the past five years, why would he need to use the admin tools and is he aware of everything that's happened with relation to admins on English Wikipedia in his preceding five years of absence? The Rambling Man (talk) 23:02, 22 December 2012 (UTC)

Was the block or other actions prior to leaving related to the tools and responsibilities of adminship? If not, then "under a cloud" doesn't apply. Because said scrutiny is of that, not of actions any editor may perform. - jc37 23:25, 22 December 2012 (UTC)

I didn't mention anything about a cloud. My question was standalone. I wanted to know why an editor who hasn't made a single edit for five years would wish to retain admin rights, and why our community would have any trust in an editor who has made made no contributions. I'm entitled to ask a question. It doesn't mean that our current procedures won't still resysop him, don't worry. The Rambling Man (talk) 23:33, 22 December 2012 (UTC)

My apologies, my comments weren't to you specifically, just concerning the discussion in general (the threading is starting to get more complex, so I didn't even try to insert my comments within above : )

I was merely commenting on a principle of policy, as I was/am concerned as to how the discussion was starting to appear to "lean" concerning "under a cloud". and so wanted to ask if others had seen any "admin-related" issues, rather than just editor-related ones.

and no, I haven't taken a look at the editor's contribs yet, this was merely concerning a principle of policy.

And I should hope that you (and anyone) can ask questions. - jc37 00:04, 23 December 2012 (UTC)

Wikipedia has a normal ebb and flow - IRL interferes with edits, that changes, and people come back. Not remembering a password after five years of not using it is not surprising. WP needs good admins - most of the current admins are classified as not active. Apteva (talk) 23:51, 22 December 2012 (UTC)

But this admin hasn't even edited once in over 5 years, so we have no idea how good they are in this environment. I started in 2006, and Wikipedia is a completely different place, and expectations are completely different for admin now. It has been so long ago, we really don't know what kind of an admin he will be, or that he will even contribute at all. TRM's question is certainly a reasonable one. Dennis Brown - 2¢ © Join WER 23:59, 22 December 2012 (UTC)

Just an FYI that while the email has been reset, the account won't let a password reset happen for 24 hours, so he can't log into it yet. He is following this thread though and did let me know that he intends to read up on policy changes and take it slow once he's resysopped. MBisanz ^talk 02:19, 23 December 2012 (UTC)

• Thank you for relaying and posting my request for restoration of the tools, MBisanz. I affirm the above request and appreciate consideration of my request. -- Jreferee (talk) 23:07, 23 December 2012 (UTC)
  • Okay, would you be kind enough to answer my questions I posed above please? The Rambling Man (talk) 23:10, 23 December 2012 (UTC)

•  Done Please do answer TRM's question however. MBisanz ^talk 03:44, 24 December 2012 (UTC)

I'm seeing a couple points of contention come up - among crats - repeatedly in these discussions about resysops, and I wonder whether it might be worth discussing them separately from any particular request for re-adminning.

First, there's "what constitutes 'under a cloud'?" I see some crats interpreting this as "A cloud exists if there is evidence that the user would have been desysopped had they remained active", and others as "A cloud exists if there is evidence that the user left to evade scrutiny of their actions." The actual wording of policy appears to be "[...]that they may have resigned (or become inactive) for the purpose, or with the effect, of evading scrutiny of their actions that could have led to sanctions." It might be (very) worthwhile for either the crats, or the community + the crats, to determine exactly what types of cases are intended to be caught by this. A user who quit just before an Arbcom motion-to-desysop went through? A user who got blocked and handed in their bits in response? A user who survived an arbcom case with sanction but without desysop? A user who survived an arbcom case with no sanction, and then quit? A user who was involved in an ANI discussion when they left? A user who knew an ANI discussion or arbcom case was coming down the pike, and left rather than deal with it?

Second, the issue of crat discretion. I'm seeing a number of crats commenting here (in various cases) that they simply have no choice, no matter what the waiting period turns up, they must restore the bit. Other crats seem to feel they're allowed some amount of discretion, either by virtue of "not obligated to act" or because the now-mandatory waiting period was put in place on the assumption that crats would be allowed to analyze the evidence that's provided to them during that time.

These seem to be points of intra-crat disagreement, and I think it would smooth things out quite a bit if you guys could reach something resembling an internal consensus about what you feel your discretion and job title allow, and/or what you would prefer them to allow. It may be that you guys can all get on the same page with a bit of a chat, and it may be that that page actually calls for community discussion of what it wants crats doing. Or it may be that you can't agree, and it comes down to which crat attends which case. Either way, the community seems to be having a hard time understanding exactly what you guys understand, and it would be helpful to get that ironed out. A fluffernutter is a sandwich! (talk) 19:22, 23 December 2012 (UTC)

The canonical example of departure under a controversy/cloud is an administrator who retires (or arguably, under the new policy, becomes completely inactive) while an arbitration case is actually pending against him or her or while a request for arbitration is under serious consideration. One purpose of the rule, which was actually crafted by the Arbitration Committee itself (before I was a member) as far as I know, but has long been accepted by the community and included in policy, is to help ensure administrator accountability. Another was to avoid the need for long, bitter arbitration cases to decide the status of administrators who were prepared to resign the tools. (There had been a couple of very lengthy and bitter arbitration cases involving admins who had already agreed to resign adminship or were willing to do so, and this was detrimental for a number of reasons.)

I don't believe it was ever intended that the controversy/cloud exception to resysopping on request would apply to less weighty challenges to administrators, such as an ANI thread about an isolated incident, or a 15-minute (or even a significantly longer) block, or even an arbitration case in which the administrator is involved only tangentially. Of course one can imagine borderline situations, such an arbitration case in which the administrator's level of culpability is debatable, or an admin-conduct RfC pending at the time of the retirement. The general rule is that the bureaucrats have discretion in these circumstances. Whether these cases should be handled by an individual bureaucrat or by group consultation is a question for the 'crats.

The other area in which some editors were concerned that the 'crats were disclaiming any discretion was with regard to retired or inactive administrators who returned and sought to reclaim adminship after an exceptionally long time had passed. As to this concern, I think the community's adoption of the new policy putting a time limit on automatic resysoppings has addrssed the issue (at least once we get past the next week or so before the new policy kicks in). Newyorkbrad (talk) 21:40, 23 December 2012 (UTC)

Hi all, I have been too busy lately to participate that much, but now that I finally have time to return, I would like to have my sysop privileges returned. Thanks.TSO1D (talk) 20:03, 22 December 2012 (UTC)

You were desysopped for inactivity and I know of no particular controversy which would preclude return, so a crat will get around to this request after 24 hours. Thank you. MBisanz ^talk 20:33, 22 December 2012 (UTC)

Procedurally, I'm sure your resysop is a mere 22 hours away. But, for my sake, just a question: you made one edit here in the last four years, namely the edit to request your admin tool back. Why would you suddenly need to use the admin tools and are you aware of everything that's happened with relation to admins on English Wikipedia in your preceding four years of absence? The Rambling Man (talk) 22:09, 22 December 2012 (UTC)

24 hours having elapsed and discovering no new information, I have resysopped. Please do drop TRM a note to answer his question though. MBisanz ^talk 21:17, 23 December 2012 (UTC)

Or simply don't answer the question since it's loaded and assumes bad faith. Andrevan@ 22:36, 24 December 2012 (UTC)

Or simply do answer a simple question which was... a simple question. And assumes no bad faith contrary to whatever Andrevan believes. In fact, Andrevan's assertion is a clear bad faith assertion. My question was very straightforward and didn't need to invoke the wrath of Andrevan et al. The Rambling Man (talk) 22:40, 24 December 2012 (UTC)

Indeed, there's nothing wrong with asking questions that seek to understand what brings contributors inactive on the project for years to requests their bits as their first action(s) in a very long time. It is obviously their right not to answer these questions under the current policy. Snowolf ^{How can I help?} 00:33, 25 December 2012 (UTC)

I would like to request my admin status be restored. I now have time to return to wikipedia after a successful re-location to China, and I hope to start being productive again, mostly on the Cheshire WikiProject, but also more widely. I also note that some of the concerns that I voiced when I resigned before have been addressed. Thank you.  DDStretch  (talk) 12:39, 23 December 2012 (UTC)

I've looked over your background and see no problems. We'll get to this as soon as the 24 hour period passes. Good to see you back. MBisanz ^talk 18:36, 23 December 2012 (UTC)

FWIW, I also looked and everything looked good. Dennis Brown - 2¢ © Join WER 23:14, 23 December 2012 (UTC)

Nothing to prevent this occurring as far as I can see. The Rambling Man (talk) 00:05, 24 December 2012 (UTC)

 Done It's been 24 hours and nothing new has been raised nor has my subsequent review returned new information. MBisanz ^talk 15:18, 24 December 2012 (UTC)

Please re-sysop..

KnightLago (current rights · rights management · rights log (local) · rights log (global/meta) · block log)

KnightLago (talk) 22:29, 23 December 2012 (UTC)

Former arb, last edits summer 2011. --Rschen7754 public (talk) 23:36, 23 December 2012 (UTC)

• Can't see a problem with restoring bit after 24 hour wait period. You'd be most welcome if you returned to activity. --Dweller (talk) 10:41, 24 December 2012 (UTC)

•  Done MBisanz ^talk 23:24, 24 December 2012 (UTC)

A Bureaucrat to sit ex-officio on Arb Com

I suggest, for both pragmatism and symbolism, that one bureaucrat should be an ex-officio (& non-voting) member of the Arbitration Committee.

The bureaucrats are charged with privilege issues, especially adminship.

Arb Com is charged with ruling on editors' disputes (behavioural, not editorial disputes), and is to resolve the most complex or intractable disputes that may arise within the community, and to oversee the few areas where access to non-public information is a prerequisite.

The two have overlap, from two very different directions.

A bureaucrat ex-officio member symbolically asserts the strained theory that Arb Com is a committee with terms of reference and not the project's ultimate authority.

As Arb Com members are not (generally) bureaucrats, some inside expertise on their role is desirable.

I would have the Bureaucrats choose their representative by a method of their own choosing, subject to approval of their representative by Arb Com. --SmokeyJoe (talk) 00:01, 24 December 2012 (UTC)

Hersfold is a bureaucrat and ArbCom member. --Rschen7754 01:24, 24 December 2012 (UTC)

So he is. So another bureaucrat would be chosen for the non-voting ex officio role. --SmokeyJoe (talk) 02:21, 24 December 2012 (UTC)

So what's the problem that would be solved by this? --Rschen7754 03:36, 24 December 2012 (UTC)

• The perception that Arb Com is a superior body that may override bureaucrat decisions.
• The perception that Arb Com as a body doesn't necessarily understand bureaucrat policy.

Arb Com may not always have a qualified bureaucrat present, and indeed, past non-secret arb com votes have indicated preference against a person being both a bureaucrat and arb ("hat collector"). --SmokeyJoe (talk) 03:55, 24 December 2012 (UTC)

Bureaucrats have always been allowed to comment on ArbCom pages. I don't see this being helpful, and would violate confidentiality (that whole arbcom-l thing?) --Rschen7754 03:57, 24 December 2012 (UTC)

How would the 'crat member to ArbCom be elected? By the community or by his colleagues? What would be the purpose of his membership of the ArbCom if he cannot vote? That is, the "privileges"/"rights" of ArbCom members consist of: voting in motions and cases, access to arbcom-l, access to arbcomwiki, access to functionaries-en. If you cut out voting in motions and cases, you end up just with one appointed 'crat to do what? Monitor ArbCom's internal discussions? If the is cross-pollination, then surely you'd want an arbcom member on the crats' mailing list. Regardless, I don't really understand the purpose and benefits of the idea. Snowolf ^{How can I help?} 03:32, 25 December 2012 (UTC)

How elected? See my "I would have" paragraph above. 

Purpose?  To alter some perceptions, which may or may not be accurate. Generally, non-voting ex officio committee members pretty much only to give specialist or alternative perspective advice when asked or when needed. 

The "privileges" I mention are user rights, adminship & bots especially. 

Monitor ArbCom's internal discussions? Yes, and maybe participate sometimes. 

An arbcom member on the crats' mailing list?  Maybe. 

You don't really understand the purpose and benefits of the idea?  

Have you ever served on a committee that included ex officio members?  It's really an idea for the crats, especially crats who feel arb com is impinging on crat territory, I think.  --SmokeyJoe (talk) 13:57, 25 December 2012 (UTC)

I've just read on my talk that automatic resysopping is going away, and if I don't ask for it by December 30, I'd have to go through RFA again. I hereby affirm that this seems sane, logical and altogether a good idea to me, and I wouldn't want to be resysopped just because I used to qualify for adminship in the past. In the unlikely case I'll ever return, I'll run for administrator like everyone else. Happy editing! JRM · Talk 18:46, 23 December 2012 (UTC)

Thanks for your work! MBisanz ^talk 19:16, 23 December 2012 (UTC)

Yes, thank you for your work, and thank you for your view on the resysop process. Indeed, your suggestion that you would prefer to regain the admin bit via RFA is quite noble. The Rambling Man (talk) 00:04, 24 December 2012 (UTC)

Interestingly, someone else (outside the wiki) has flat-out called me nuts for doing this, because (quote) "RfA is the worst thing" and "we need active admins far too much than to risk that scenario". Huh. I didn't know things where that dire. My decision still stands, of course, if anything it shows it's more appropriate now than ever. JRM · Talk 15:54, 25 December 2012 (UTC)

An attitude like that at RfA will get you nothing but supports. --64.85.215.128 (talk) 18:13, 25 December 2012 (UTC)

This is probably going to happen a lot in the next few days...

Taking extreme pains to not try to assign blame or criticize decisions that have already been made: It's sort of bad form to send someone an email saying they can get their bit back by posting here, and then argue with them when they do it. Kind of makes us look like we don't know what we're doing. I suppose it won't always result in pissing people off, but it sure isn't going to make them feel welcome to re-engage. There are more than enough poor current admins to get stressed out about; I don't think our biggest problem is going to be a handful of old admins who've been avoiding drama for years, and who will very likely either (a) not return to activity after the re-sysop, and have the bit removed again in a year; or (b) come back, and probably do occasional maintenance stuff when they see a need, but not be involved in the political side of this place, and therefore not screw things up. Also, the longer it's been since they were sysopped, the more likely that they're now responsible adults and unlikely to cause drama. Catching up on current policies is not really rocket science. And finally, it seems to me like there used to be a lot more clueful people around than there are now; we should encourage oldtimers with clue, not try to talk them out of coming back.

I really recommend if an old admin asks for their bit back before the deadline (or even a few days after it), we just check to see that they didn't resign under a cloud (or whatever PC term we're using for that), and convince ourselves they're the same person. If they meet the two criteria, give them back the bit and thank them for their interest. -Floquenbeam (talk) 03:05, 24 December 2012 (UTC)

• Agree with multiple points here by Floquenbeam. --SmokeyJoe (talk) 03:16, 24 December 2012 (UTC)
• Perhaps a more gentle tone is called for, but there are some legitimate questions to be asked in some circumstances. Most requests have been uneventful, but when the admin says "I would not pass an RFA anymore ever. I think I wouldn't even try anymore. My request is indeed to avoid a new RFA." and "I don't really think I need those rights right now, but I think I'd frankly like to avoid going through another RFA." I think questions are reasonable. It was made pretty clear that they wouldn't be denied the bit based on answers, and they were welcomed and offered assistance. When they are asking for the bit back, we are assuming they are an admin and just don't have the bit assigned to them. They should be able to handle a couple of good faith questions, same as you or I would be expected to, particularly when it is made clear it won't affect the outcome, and they should know they can ignore if they should choose to. We shouldn't badger anyone, but politely asking a few questions isn't badgering. Dennis Brown - 2¢ © Join WER 03:25, 24 December 2012 (UTC)
  • I'm particularly surprised to find behavior like the one shown by you, especially for an admin. It is quite obvious that Dennis disagrees with WP:ADMIN and that he apparently tries to do forum shopping by turning resysoping requests into RFA's where the requesters have to explain why they want the bits back and having a debate about whether they are capable, and a repeating debate about WP:ADMIN. The rules at WP:ADMIN are quite clear and simple. Some people have assumed me of perhaps not being able to read and follow policy. I note it is you who are not following policy. I would also politely like to ask you to stop spreading lies about what I said. You said "..and likely won't use the bits anytime soon". I never claimed that. Please stop telling such stupid lies. Ligulem (talk) 13:21, 25 December 2012 (UTC)
• I would agree with Floq. Particularly because Ligulem had never been notified of the initial removal for inactivity because of a Steward oversight, I find it wrong that we quizzed him at greater length than we have other returning admins. Also, if people are upset with the current policy, they should seek to amend the policy, not make pointy examples at the expense of returning users. MBisanz ^talk 03:52, 24 December 2012 (UTC)
• I'm just asking a few basic questions. I'm also making it clear that the resysop will doubtless go ahead in every case under current policy. I'm not trying to score points or go on some kind of crusade, but I'm interested in why people who are entirely absent for year after year really need their admin flag and why they would go to such an extent to avoid being re-examined by an entirely different community to the one that "elected" them (I say that because in some cases, older admins weren't even elected). It must truly suck when trying to run at RFA these days when people have contributed tens of thousands of good edits and get opposed based on failure to maintain 100% edit summaries or something equally trivial, who see editors who have been entirely absent for half a decade just pop by and get their admin flag back while declaring a positive desire to avoid an RFA. In future, to be clear, I'll guarantee that any questions I ask of this nature will be in the capacity of a concerned editor, not a 'crat. The Rambling Man (talk) 08:14, 24 December 2012 (UTC)
• May I suggest that you folks simply stop "notifying" people like me. And change the rules to honestly state what they really are: a new RFA is required after inactivity. That would have saved me from wasting my time again here. Ligulem (talk) 08:23, 24 December 2012 (UTC)
  • Please read my comments carefully. I said you would most likely be procedurally resysoped in 24 hours regardless of my questions (to whit: "While procedurally you'll probably be re-sysoped in the next 24 hours..."). Cheers. The Rambling Man (talk) 08:26, 24 December 2012 (UTC)
    • I agree that questions are worth asking, but perhaps we can be more gentle in how they are asked? Asking too aggressively might make a question look like an inquisition. Dennis Brown - 2¢ © Join WER 16:41, 24 December 2012 (UTC)
      • I'm not sure how much more gently I could have asked the questions... after all, these are seasoned admins who are fully aware of how it all works around here. I would have hoped, at the very least, that they would have had the courtesy to just decline to answer my questions rather than remain as silent as they had for the previous four years. Those who have ignored the questions, well how very unbecoming of people in such a lofty position as an admin............ ;) The Rambling Man (talk) 17:26, 24 December 2012 (UTC)
        • Please don't take offense when I say that I agreed with the relevance of your questions, but think the tone was more harsh than you realize. I think redoubling the effort to be cordial when asking the questions would go a long way towards addressing some of the concerns expressed here. We are better served by being as welcoming as we are inquisitive, so our questions don't come across as an unexpected pop quiz. Dennis Brown - 2¢ © Join WER 19:00, 24 December 2012 (UTC)
          • I don't take offence from you Dennis, you seem to be one of the few with some common sense here! I'll do my best to "cordialise" my comments. Although as I've said, we're dealing with battle-hardened, experienced admins here who probably should understand that my concerns are simply posited for the best, most certainly for the best of Wikipedia. In any case, best seasonal greetings to you. The Rambling Man (talk) 19:40, 24 December 2012 (UTC)
• My 2p is in the section above. I agree with the OP here and if I had read it before posting above I wouldn't have bothered since it expresses my thoughts on the subject comprehensively. Leaky Caldron 12:35, 24 December 2012 (UTC)
• I agree we should not interrogate inactivity re-sysops. Andrevan@ 22:31, 24 December 2012 (UTC)
  • Asking them a couple of questions is "interrogation" these days? What the .... The Rambling Man (talk) 22:33, 24 December 2012 (UTC)
    • Webster's: "Ask questions of (someone, esp. a suspect or a prisoner) closely, aggressively, or formally." I think your questions are loaded and assume bad faith. We apparently agreed to a policy that these users would be entitled to resysops, no questions asked, and your questioning makes it seem like they are neither routine nor uncontroversial. Andrevan@ 22:39, 24 December 2012 (UTC)
      • You're funny, seriously. A "suspect or a prisoner"?!! That's clearly not the case. Nor was it aggressive or formal. Honestly, re-read it. No bad faith. I wanted to know what editors who haven't done for four years would need to retain their admin flag for. A simple question. In fact, your aggressive and bad faith approach to my simple question is very educational, thanks. The Rambling Man (talk) 22:43, 24 December 2012 (UTC)
        • First of all, the operative logical operator in the definition is "OR," meaning only some portion of the definition needs to match. I think it would be tough to argue that you were not "asking closely." That is sufficient but I would also argue "suspect"," i.e. you suspect this old-time editor not to have a need or dare I say ability to edit and use admin tools. So I think you were actually assuming bad faith into my comment, which I can understand because your actions are under something of a cloud currently, and you might feel defensive or attacked. I would say the best way to salvage your position is to simply stop asking the re-sysop gatekeeper questions. I've been an admin since 2004, and I think someone who was trusted to wield a mop in 2008, would do fine here in 2012. But my opinion isn't strictly relevant, as the policy consensus supported a non-controversial routine resysop without close, formalized (by which I mean repeated or copypasta'd) questioning. Andrevan@ 22:56, 24 December 2012 (UTC)
          • Pardon? My "actions are under something of a cloud"? What the hell are you talking about? I'm not here to "salvage" anything. Your stats are fascinating, but I'm talking about people who haven't actually made any edits for four or five years. Formalised doesn't equate to copy-and-paste, nor did I, check it closely. If you have a problem with me asking questions of people here, fine, talk to me about it, but don't go around claiming I have some kind of "cloud". Happy Christmas. The Rambling Man (talk) 23:03, 24 December 2012 (UTC)

As other have mentioned above I also agree with Floq, unfortunately though being an admin is more about politics and peopleskills these days than about wether they know what to do. I have seen several RFA's over the last few months, mine included, from people who know what to do but have ruffled too many feathers to ever get the tools. So although I agree with what they said, its just not realistic to the current state of things on WP. Until we change the climate and attitude that getting Adminship is akin to becoming Governor of the wiki, we will see things continue to slip and slide down hill. Also unfortunately resysopping has also become a hot potato. I do understand though that most who have been through RFA and passed would not want to endure it again and many who previously passed would not likely pass today, particularly with a long period of inactivity. There is no doubt in my mind that if an RFA were opened for a newly returning former admin, it would be summarily shot down by the community until they get some recent edits under their belt again. Kumioko (talk) 22:49, 24 December 2012 (UTC)

I agree. And I entirely feel sorry for those going through RFA right now watching editors with no edits in four years just popping by to claim their flag back and actually stating they're avoiding community scrutiny in doing so. The Rambling Man (talk) 22:51, 24 December 2012 (UTC)

I feel for this user but the fact remains as you stated in your questions. They haven't edited in 3+ years, what do they need the tools for right now? IMO there is nothing wrong with having them edit for a little bit to get their wheels again. A lot has changed in three years (we used to link all the dates for one). I'm not saying that a user would intentionally do something wrong, but they might do something they think is right, based on three year old knowledge, and it turn out to be wrong. Kumioko (talk) 23:02, 24 December 2012 (UTC)

What you are doing with this is discouraging user activity. If our email campaign brings back some old editors to help out with backlogs, that is fantastic. We should be encouraging readminning. If a user comes back after 4 years inactivity, asks for his admin tools back, and then contributes to the project, that's great! The difficulty of RFA essentially equates to an optimization problem. It's tough to separate out users who will make good admins from those who are simply passing through, and this problem has become tougher over the years as Wikipedia has become more prominent -- which is why RFA has become so cutthroat. Most people consider RFA to be somewhat unforgiving, but the system is reflecting the will of the community. However, a delicate policy decision was reached on the inactivity resysops, which as a bureaucrat you must recognize and honor. We agreed not to make these users go through RFA again, just as no user is required to submit to a recall request for re-RFA unless the arbitration committee has determined there is a policy violation in editing. Andrevan@ 23:28, 24 December 2012 (UTC)

Just to clarify I am absolutely not saying they should have to go back through RFA, because that is not something I would wish on my worst enemy. What I am saying is after more than a year of inactivity and especially when you get into the 3+ years range, some minimal new edit history would be a positive. I also agree that if we can get some folks back that would be great as well but at the same time we need to be addressing the things that made them leave in the first place (but that is another discussion). As far as I can tell there has been almost no effort put into doing this. Also on the just passing through comment. That has nothing to do with it. I have been here for years and have amassed more edits spread across more areas than all but a few users (like 10 I think last count) and I have been told repeatedly I don't have the right temperment for admin because I have no problem telling users that don't listen the to the polite way where they can stick it, that they are wrong and I have no problem telling people they should be enforcing policy rather than covering for their buddy. Because of that I am as well liked as a Raggae band at a Klu Klux Klan rally. That is largely the reason I don't edit much anymore. This place is too emotionally draining and more and more a waste of time if I am expected to do all the work so that others can implement the changes and take the credit. Especially with a large number of admins having SHS (Swelled Head Syndrome) (not all of course, there are a lot of good ones too). Back to the point. TRM already stated that the user would most likely get the tools back after the 24 hours so this is all really just extra banter. Kumioko (talk) 23:48, 24 December 2012 (UTC)

Just noting I'm not familiar with your case and I didn't intend to imply you were unfit for RFA. My general free advice is to keep editing and work on whatever it is that rubs people the wrong way. Andrevan@ 23:51, 24 December 2012 (UTC)

No offense taken. Its not your fault. I was born without that filter most people have between the brain and the mouth. :-) Kumioko (talk) 23:53, 24 December 2012 (UTC)

Those who feel the need to question note (and state), quite correctly, that the responses to the questions do not affect the procedure of the resysop. Why then, is it necessary to ask those questions before the resysop is completed? Whether or not you believe that the questions asked above were overly confrontational, surely everyone can agree that the same questions asked on a user talk page just under the "here's your bit back" message would be much less so? The only reasons I can think of are if the questioners wish the answers would affect the process, which is not the correct way to alter policy, or that the questioners don't want to wait for the returning admin to potentially go inactive again, which makes the 'it's just a friendly question, you don't have to answer' ethos ring a bit hollow. Why is it necessary to ask these questions during the period when it could be (mis)interpreted as interrogation? Happy‑melon 19:17, 25 December 2012 (UTC)

• Well I didn't think the questions were a big deal. Clearly the resolute silence from those being resysopped and the accusations levelled at me by a number of editors and other 'crats here seems to indicate otherwise. As I've said a few times, I did, on each occasion when asking these questions, reassure the candidate that the procedural resysop was still likely to go ahead. Of course, one could argue that these candidates should be fully commensurate with our current policies and would know that the questions were simply that, questions, not an inquisition or an interrogation or whatever other hyperbolic description of the simple questions have been so far, and that answering them would be polite, or even declining to answer them would be polite (and admin-like), not just to stonewall them. Not to worry, I'll avoid the board from now on until things calm down a bit, although it seems from the various comments above, I'm not alone in wondering what the answers to the questions were, and why they weren't answered at any point. The Rambling Man (talk) 21:41, 25 December 2012 (UTC)

I'm drafting an RFC at User:MBisanz/Resysopping to help fix some of the concerns regarding the "under the cloud" standard. I'll probably move it somewhere in the projectspace in the coming week, but wanted to drop a note here so people can have a chance to add to it before I do so. MBisanz ^talk 18:49, 25 December 2012 (UTC)

Well, it was bound to happen, we can't have bureaucrats without bureaucracy!:-) Kumioko (talk) 01:15, 26 December 2012 (UTC)

It's now live at Wikipedia:Requests for comment/Resysopping practices. MBisanz ^talk 18:45, 29 December 2012 (UTC)

Fellow Wikipedians, I'm asking to be resysopped. I used to be a very active Wikipedian, but the distractions of life got in the way in the last few years. I intend to return to the project in the near future and I would hate to not have the admin tools. I don't want to feel that I have to "start all over" if you can understand that. Thanks! MatthewUND^(talk) 22:31, 28 December 2012 (UTC)

Don't see any issues, per the current resysop approach. The Rambling Man (talk) —Preceding undated comment added 22:50, 28 December 2012 (UTC)

I agree with TRM that I know of no issue under the present policy that would preclude resysopping. MBisanz ^talk 02:41, 29 December 2012 (UTC)

I see no issues which would prevent the bit being returned. ···日本穣^? · 投稿 · Talk to Nihonjoe · Join WP Japan! 18:55, 29 December 2012 (UTC)

•  Done We'd be delighted to have you back as a contributor, not to mention administrator. --Dweller (talk) 23:40, 29 December 2012 (UTC)

Thank you very much! MatthewUND^(talk) 07:32, 30 December 2012 (UTC)

• - Wikipedia:List of users resysopped by a bureaucrat

Hi - good to see this list being updated. Please continue to add all users given/returned advanced permissions to the list - Many thanks - the list is a very helpful investigative tool - regards Youreallycan 23:45, 30 December 2012 (UTC)

I see it as very beneficial for timeline investigations and had done a fair bit of work on that and would like to find time soon to finish that work - User:MBisanz reverted all my efforts on 6th Dec to an ABC list diff- such a list removed the ease of seeing the recent resyops - since these are the changes which are important to investigate - on a timeline - I intend to revert to the timeline and finish the work - if you guys are happy with that to just add a user to the end of the list, easy - thanks - If User:MBisanz , who I am sure can do it in a couple of seconds with a script or a bot would do it for me, I would really appreciate that - or if he, or others, would please explain why he/they think an ABC list is more beneficial, thanks Youreallycan 23:38, 30 December 2012 (UTC)

The reason I reverted was because it was more difficult for resysopping crats to add to the timeline because it's the third item in the template. I balanced it with the fact the sort feature at the top of the table means that anyone who wants to create a timeline can click the sort feature and it will display them in that order. MBisanz ^talk 00:11, 31 December 2012 (UTC)

third item in the template? anyone who wants to create a timeline can click the sort feature and it will display them in that order - I want to do that - please provide a diff or a link to help me do that? - IMO your revert hides recent activity, which is why the list was created, and makes it much more difficult to see what is going on - - Youreallycan 00:15, 31 December 2012 (UTC)

@MBisanz, "anyone who wants to create a timeline can click the sort feature and it will display them in that order? " - Where is that then? Youreallycan 00:22, 31 December 2012 (UTC)

See the red circle on File:Resysops-help.png. MBisanz ^talk 00:25, 31 December 2012 (UTC)

I think the discussion that led to the creation of this list was quite clear - that it is the recent :Bureaucrat permissions that are valued to investigate not the years old ones - as such - ABC is detrimental to assist investigations of the permission returns - Red flag is perhaps something you are knowledgeable about but I have been here years and have no idea - your revert of my work was and is detrimental to investigation of the Bureaucrats activity/actions and as such please revert to a timeline - thanks - Youreallycan 00:29, 31 December 2012 (UTC)

Erm, Help:Sorting? It looks fairly well documented. I don't have a script to sort it by date, which is another reason why I picked alphabetical order when trying to figure out how to do it. MBisanz ^talk 00:35, 31 December 2012 (UTC)

Just because you had a script for ABC was not an excuse to revert my work or a reason to see it as beneficial - In regards to the reason the list was created, it wasn't - It more serves to hide the recent returns of privileges by the Bureaucrats. Please revert my work to the list back in, if you have time to help complete the timeline I would also appreciate that Youreallycan 00:40, 31 December 2012 (UTC)

I found someone who thinks they can fix it, although I fear it will quickly become mangled in periodic updating. MBisanz ^talk 00:47, 31 December 2012 (UTC)

Great - thank you - Youreallycan 00:51, 31 December 2012 (UTC)

The three year rule has now gone into effect. The grace period for all former admins that we're inactive for more than three years is now over. The grace period for all former crats is still in effect until February 1, 2013.—cyberpower ^Chat_Offline 00:24, 31 December 2012 (UTC)

I'm so happy that's over. Thanks. MBisanz ^talk 01:23, 31 December 2012 (UTC)

Please see Wikipedia_talk:Bot_Approvals_Group#Recruitment. Thanks. MBisanz ^talk 01:40, 31 December 2012 (UTC)

• - Hi, I was thinking a bit of feedback from you guys about how you all feel about having no discretion at all in the current resyopping procedure, perhaps you feel unable to opine so as to avoid involvement? diff - Youreallycan 14:04, 1 January 2013 (UTC)

The community has been outstanding at selecting Crats who respect or respond to the community's consensus. MBisanz's initiative, which I welcome, will help us determine what that consensus is. I'm speculating here, but I'm not sure that any of us are avoiding involvement, and I definitely don't think any of us feel "unable" to be involved. It can definitely be argued that MBisanz is more "involved" in the RfC than any other editor, though perhaps not in the manner you had in mind. --Dweller (talk) 20:42, 1 January 2013 (UTC)

Thanks for responding - If any Bureaucrats feel able to comment there that would be great - if any of you feel strongly about the issue I hope you will - thanks - Youreallycan 20:49, 1 January 2013 (UTC)

Yeah, I'm involved :) I'm not going anywhere near any functions besides RFC opener. I do hope other people step up to comment so that the RFC closers have lots of material to work with. MBisanz ^talk 21:08, 1 January 2013 (UTC)

Hi Bureaucrats. I resigned my tools during about of frustration a year ago and I think that I would like them back now. Specifically because I have just found out that all of the editors with whom I had a frustrating experience were in fact sock puppets of banned users (three different ones!). In the course of my frustration I did behave in a decidedly ungentlemanly fashion, for which I have apologized [3], and which I have not repeated in the year that has passed since then.·ʍaunus·snunɐw· 23:43, 1 January 2013 (UTC)

You will need to wait 24 hours before getting the tools back so the community can assess if you resigned under a cloud. If no issues are found, you will be promptly resysoped.—cyberpower _Offline^{Happy 2013} 00:13, 2 January 2013 (UTC)

• I did notice the quote "My knowledge of the situation is limited to what is on this page, but, at face value, someone who got involved in a dispute about one of his or her blocks, got into a heated argument, and then decides to take some time off to cool down does not appear to be "resigning the tools to evade scrutiny"". by User:Avraham, echoed by others, so there seems to have been a general consensus at that time that a cloud did not exist. Will look deeper, but not expecting to find anything problematic. Dennis Brown - 2¢ © Join WER 00:19, 2 January 2013 (UTC)

I am happy to wait and let the community decide, but I would like to note that at the time of my resignation 4 bureaucrats agreed that it was not to be considered under a cloud as can be seen here Wikipedia:Bureaucrats'_noticeboard/Archive_23#Hi.·ʍaunus·snunɐw· 00:20, 2 January 2013 (UTC)

I'm not a Crat, and my opinion plus $2 will get you a cup of coffee, but I feel like I have to just ask. I'm guessing you expect to be a little less blunt than you were during that time? [4] I haven't looked at all the diffs, but I'm guessing that is the stress you wanted to get away from, and this isn't your normal methods? Dennis Brown - 2¢ © Join WER 00:29, 2 January 2013 (UTC)

That is what I meant by my initial statement in which I also supplied the link to that case. I would like to note that all of that happened after I resigned my tools, and that I would never have done that while being an administrator. I have been reluctant to reclaim the tools because of what I did and how out of character it felt for me, but since I now know that I was correct in my initial suspicion of foulplay, and that I had simply gotten caught up in a showdown between puppets of three different banned editors (JackMerridew, SkagitRiverQueen and Mattisse) and my thesis defense, I now feel that at least there was a good reason that I lost my cool that day. I am not going to promise it won't happen again since wikipedia is a weird place sometimes, but I do promise that I will always take responsibility for my actions. If the bureaucrats decide that the best thing is to request community input then I will fully accept that, but I would respectfully decline going through and RfA. ·ʍaunus·snunɐw· 00:38, 2 January 2013 (UTC)

My limited interaction with you have been positive, which is why that one diff kind of threw me for a loop. It wasn't what I was expecting to see. I'm not saying it should disqualify and I doubt it would, but I'm sure you understand why I was concerned, and I appreciate your honesty here. Dennis Brown - 2¢ © Join WER 00:42, 2 January 2013 (UTC)

To be more clear, I would offer no objection to resysoping. Dennis Brown - 2¢ © Join WER 20:19, 2 January 2013 (UTC)

• I see no reason Maunus should not be resysopped once the standard 24 hour waiting period has elapsed. 28bytes (talk) 01:11, 2 January 2013 (UTC)
• After a brief review, I know of no evidence that would preclude resysopping after a 24 hour waiting period. MBisanz ^talk 01:43, 2 January 2013 (UTC)
• Manus is an all round good egg. Rich Farmbrough, 01:46, 2 January 2013 (UTC).
  
• I stand by what I said when Manus took his extended wikiadminbreak; there is no reason not to return the tools after the prescribed waiting time. -- Avi (talk) 01:58, 2 January 2013 (UTC)
• No issues for me, and I'd love to use some discretion to "just do it" but I'm sure it'd create even more unnecessary dramaz if I resysoped three hours too early. Ho hum. The Rambling Man (talk) 20:36, 2 January 2013 (UTC)

 Done. 28bytes (talk) 23:22, 2 January 2013 (UTC)

Thanks!·ʍaunus·snunɐw· 23:25, 2 January 2013 (UTC)

As of January 2, the following should be desysopped per the inactivity administrators policy:

• ClockworkSoul (talk · email · contribs · deleted · logs · last entry · listuser · centralauth · target logs · userrights)
• CloudNine (talk · email · contribs · deleted · logs · last entry · listuser · centralauth · target logs · userrights)
• Dsmdgold (talk · email · contribs · deleted · logs · last entry · listuser · centralauth · target logs · userrights)
• Jtdirl (talk · email · contribs · deleted · logs · last entry · listuser · centralauth · target logs · userrights)
• Kakofonous (talk · email · contribs · deleted · logs · last entry · listuser · centralauth · target logs · userrights)
• Lifebaka (talk · email · contribs · deleted · logs · last entry · listuser · centralauth · target logs · userrights)
• Qwghlm (talk · email · contribs · deleted · logs · last entry · listuser · centralauth · target logs · userrights)
• Redwolf24 (talk · email · contribs · deleted · logs · last entry · listuser · centralauth · target logs · userrights)
• The-G-Unit-Boss (talk · email · contribs · deleted · logs · last entry · listuser · centralauth · target logs · userrights)
• UberScienceNerd (talk · email · contribs · deleted · logs · last entry · listuser · centralauth · target logs · userrights)

Regards, — Moe Epsilon 02:10, 2 January 2013 (UTC)

 Done Please let me know if there is any paperwork I missed. MBisanz ^talk 02:17, 2 January 2013 (UTC)

Wow that sucks. We lost 10 here and only promoted about 8 in the last 4 months. Not counting the ones we lost over the last 4 months. I hope this trend doesn't continue or Jimbo might need to grab a mop and bucket and help out at AFD! I just looked and if I include February 2013 we lost about 49 and only gained 8 since September, plus the 2 or 3 we might get this month. Thats a 4-1 loss. Yikes. Kumioko (talk) 02:27, 2 January 2013 (UTC)

It's worse for the whole year of 2012, don't look (for your own sake). Regards, — Moe Epsilon 02:40, 2 January 2013 (UTC)

Remember that none of these admins edited in the past year, so it's not as though we lost a net 2 admins. (X! · talk)  · @168  ·  —Preceding undated comment added 03:01, 2 January 2013 (UTC)

It is important to note that despite it not effecting active administrators in that sense, we still lost around 70 admins total from 2012 to 2013 (it would have been more, but the long-term inactive policy drove quite a few administrators back). Regardless of how they were desysopped, or how active they were a month ago, any year where we desysop more than we promote is bad. Regards, — Moe Epsilon 03:20, 2 January 2013 (UTC)

There is another perspective here. According to my own magic numbers, between December 2011 and today there was a 7.2% drop of Registered active users; in that same period, there was a drop of 4.0% in the Sysop group. To be (mathematically) equivalent, the Sysop group would need to drop by ~109, not the 61 it actually dropped by --Senra (talk) 19:58, 3 January 2013 (UTC)

Firstly you are measuring total admins rather than active admins, and when it comes to issues such as whether we have sufficient people to do various things the active figure is the more relevant one. Secondly the expected pattern in a maturing and stabilising community is that as the proportion of newbies falls so a rising proportion of our regulars would be admins, and we should be in a "too many chiefs" situation but clearly aren't. Thirdly the critical minima for the admin corps include our ability to cover key admin functions at acceptable frequency. That means a 24/7 coverage at AIV; Many other areas are less time sensitive, it wouldn't be a problem if all AFDs were closed in the US evening - but our minimum need for admins is linked to the times we need coverage for as well as the amount of work we want our admins to do. Arguably it is also linked to total editing levels, I suspect that it isn't closely linked to the number of active regulars as hopefully they won't be vandals or even creating articles that merit deletion. ϢereSpielChequers 20:28, 3 January 2013 (UTC)

Hello, I was just told that my admin rights are going to be permanently lost if I don't manually request them restored, so I'd like to do so in the hopes I can find time to get back to work soon. InShaneee (talk) —Preceding undated comment added 22:36, 22 December 2012 (UTC)

Procedurally, I'm sure your resysop is a mere 23 hours away. But, for my sake, just a question: you made one edit here in the last five years, namely the edit to request your admin tool back. Why would you suddenly need to use the admin tools and are you aware of everything that's happened with relation to admins on English Wikipedia in your preceding five years of absence? The Rambling Man (talk) 22:41, 22 December 2012 (UTC)

Noting Wikipedia:Requests for arbitration/InShaneee, but also noting that ArbCom did not desysop and that was roughly 6 months before editor left altogether. --Rschen7754 22:42, 22 December 2012 (UTC)

Noted. My question notwithstanding, I feel uneasy about this resysop given the unanimous conclusions of Arbcom "back in the day" about inappropriate behaviour as an admin. Back then, a ten-day suspension of sysop ability would these days most likely equate to being removed of the bit, more importantly the behaviour of this editor was noted as exhibiting "substantially similar previous behavior" which "was discussed at length by the community" which revealed " the community was concerned about InShaneee's use of blocks and lack of willingness to discuss them"..... The Rambling Man (talk) 22:50, 22 December 2012 (UTC)

Sounds like "a cloud" to me ... (✉→BWilkins←✎) 22:52, 22 December 2012 (UTC)

(edit conflict) Actually, part of the sanction was "InShaneee's admin privileges are suspended for a period of ten days." I count 41 edits after that Arb hearing, scattered over a few months before leaving. I will leave the interpretation up to the Crats. Dennis Brown - 2¢ © Join WER 22:54, 22 December 2012 (UTC)

To answer your question, yes, I have been periodically reading what's been going on behind the scenes over the last few years, so I'd like to think I'm still pretty up to date. The reason I'd like my privileges back is because, as my edit history shows, most of the work I did here was simple reversions from the 'recent changes' list, uncontroversial speedy deletions, and other 'mop' type activity. I had always planned to come back after a break (and had been told that wouldn't be an issue), so when I do come back, that'd likely be where I'd want to pick up at. InShaneee (talk) —Preceding undated comment added 23:26, 22 December 2012 (UTC)

It's a no from me. Other 'crats may see if differently, of course, but I can't see the purpose in re-promoting this editor based on no activity for five years and a cloudy past including admonishment from Arbcom (albeit back in the day). Suggest the editor submits himself to RFA, like other candidates, so the community can assess his ability in the current climate (i.e. understand the five-year gap and whether or not the editor meets current standards). The Rambling Man (talk) 23:15, 22 December 2012 (UTC)

Reading WP:CLOUD is quite enlightening in this case. I quote:

A user whose hidden conduct, questionable good faith, or other uncertain behavior comes to light, and steps down before it can be fully examined, may not be seen as appropriate to resume the role at will once it has become "stale".

The concern also arises because resignation may be seen as having resolved the issue and therefore the matter may have been dropped by others rather than examine an issue that is no longer in need of remedy.

Accordingly a user who steps down in such a way that it seems they have evaded their conduct being actually assessed by the community, or their fitness to the role being affirmed, may be refused the right to automatically reclaim that role later without going through the usual process again to confirm they do in fact have the community's trust.

Given these definitions, InShaneee does not meet the definition of having resigned under a cloud. The resignation was not before the user's conduct was fully examined, and was not done to evade assessment of their conduct as the Arbitration case was completed. If InShaneee had remained active then they would likely still have their administrator rights. As such, do we have the right to decline the request? I do not know the answer to these questions yet. I will need to think more about this issue. --(ʞɿɐʇ) ɐuɐʞsǝp 23:18, 22 December 2012 (UTC)

Okay, well rather than just blindly following the guidelines, I'm suggesting an editor with no edits for five years and who had an Arbcom case admonishing them for dubious admin behaviour in the past is not a suitable candidate for immediate re-sysop. If this is the kind of candidate we blindly re-sysop "per policy" or "per guideline" then we've got it wrong. How can the community have faith in this kind of candidate? The Rambling Man (talk) 23:23, 22 December 2012 (UTC)

I'm not sure how I'm "blindly following guidelines" when I quite clearly stated I've not even made my mind up about what I think is the correct course of action yet. All I was doing was giving some points for consideration. That is allowed, yes? --(ʞɿɐʇ) ɐuɐʞsǝp 23:25, 22 December 2012 (UTC)

I think we need to be a little careful of how these essay (not policy) pages spring into existence and who edits them. That pages contains some sensible points (and some less sensible points IMHO), but is basically one contributor's viewpoint and is far from an exhaustive account of the factors that have been (or should be considered) in these cases. WJBscribe (talk) 00:14, 23 December 2012 (UTC)

Ok, my fault, I didn't mean to single you out here, my apologies. I meant, instead of "us" (i.e. crats) blindly re-sysopping, this case seems more contentious than most. I see no good reason to resysop someone who hasn't made a single edit in five years but suddenly gets an email telling him he's not going to be an admin any more, just for him to show up here asking for his bit back. When we rename people, we often ask questions like "are you sure you won't edit on behalf of others" or "are you sure you're not editing with a conflict of interest", but with this resysop process, we're just saying, sure, after five years without a single edit, you can just become an admin again. Seems anomalous. I would like these candidates for re-sysop to dedicate themselves to some kind of editing, rather than just give them the admin tool back after five years of inactivity barring a single edit to say "I need it back....". The Rambling Man (talk) 23:30, 22 December 2012 (UTC)

Fair enough, and fair point. I need to think about this. --(ʞɿɐʇ) ɐuɐʞsǝp 23:34, 22 December 2012 (UTC)

To be fair, the e-mails sent out for were that exact reason: to notify of the impending lengthy inactivity policy going into place on January 1 and to see if they were interested in the tools being restored under the former process (with the 24 wait, now). On that note, I would be very weary of a resysop in this case, 'crats. Regards, — Moe Epsilon 23:36, 22 December 2012 (UTC)

Weary or wary? The Rambling Man (talk) 23:37, 22 December 2012 (UTC)

Typo, sorry. Being wary can make you weary. Regards, — Moe Epsilon 23:40, 22 December 2012 (UTC)

I think this a very borderline call. On the one hand, I lean in the same direction as Rambling Man - inappropriate conduct leading to sanction followed by extended inactivity sounds like controversial circumstance / under a cloud if those words are to be given their natural meaning. On the other hand, I can see the argument that the "controversial circumstances" having been investigated and found to warrant a temporary (not permanent) removal of rights, it would be wrong for that decision to be second guessed because the inactivity of the user allows bureaucrats to do so. That doesn't necessarily strike me as what's happening here. I think the key question is: does the ArbCom decision "cleanse" the misconduct such as to prevent us weighing it in the balance when considering whether to restore the tools? On balance - I don't think it does. As I understand it, restoration of rights without RfA is meant to be available to administrators in good standing. Refusing to resysop without RfA is not a bureaucrat imposed sanction, it simply reflects our assessment that the circumstances in which a user left / became inactive were controversial such that the question of whether or not rights should be restored should be referred to the community. This seem to me to be such a case - notwithstanding the temporary desysop, I do think InShanee stopped editing in controversial circumstances. It therefore seems best to err on the side of caution and let the community decide at RfA, but I think input from other bureaucrats would be helpful. WJBscribe (talk) 00:14, 23 December 2012 (UTC)

WJBscribe excellently conveys both sides of the decision. I think ultimately we should AGF and think that the inactivity was not from the ArbCom case. I would ultimately say to resysop through AGF and go from there. They can always be desysopped through ArbCom case if they prove to misuse the tool.—cyberpower _Offline^{Merry Christmas} 00:47, 23 December 2012 (UTC)

Having thought about this for quite a while, I'm leaning towards agreeing with WJB here. I think that given the nature of the situation, RfA is the best bet. This is not us saying declining to resysop, it is us saying that in this case it is not up to us to decide. --(ʞɿɐʇ) ɐuɐʞsǝp 01:31, 23 December 2012 (UTC)

FWIW, after seeing Jreferee's request, I decided it was worth sending emails to the people I had Mabdul notify earlier this month about the change in policy; that's why the latest requests are here. My take is that the community does not want us acting with discretion in resysopping requests. The presumption is that a user can be resysopped unless a prohibition applies. The prohibitions are:

1. User has been inactive for three year period of time which includes or is subsequent to the date of desysopping (details vary): InShaneee filed this request prior to the expiration of the prior policy
2. User resigned the tools in a manner so that it appears he did so to avoid scrutiny that has a high probability of leading to desysopping (such as a pending RFC or RFAR): InShaneee's conduct was scrutinized by Arbcom and his conduct subsequent to the case does not indicate he left to avoid further scrutiny
3. The reviewing bureaucrat is not satisfied that the person requesting resysopping is the original owner of the account or that the account's security has not been compromised: No one has questioned InShaneee's identity
4. Subsequent to desysopping, the user engaged in conduct of an extreme and egregious nature such that no reasonable person could doubt they would have been desysopped should they have done it while an admin (socking, severe copyvios, etc.): InShaneee made no edits subsequent to his desysopping for inactivity and no other bad acts have been alleged

Based on that analysis, I don't see on what basis we can deny a resysopping. We don't judge admin behavior, that's Arbcom's job. We only judge if a person resigned to avoid Arbcom judging their behavior. No reasonable person could find that InShaneee resigned or went inactive to avoid Arbcom judging their behavior because Arbcom actually reviewed their behavior. MBisanz ^talk 02:28, 23 December 2012 (UTC)

• What if all the Crats have looked at it and have simply decided "I won't say no, but I can't say yes"? Would the request eventually be closed out simply due to an unwillingness of a sufficient number of Crats willing to openly approve? Are Crats obligated to give a definitive opinion if they have commented? Dennis Brown - 2¢ © Join WER 03:16, 23 December 2012 (UTC)
  • I agree with Dennis here, and I think a member of ArbCom (or a couple) should comment here about whether InShaneee should be resysopped or not. It's clear that the crats disagree in this case and emotions are high, and its not worth all this drama. Secret ^account 03:33, 23 December 2012 (UTC)
    • What drama? This is a very calm discussion. --(ʞɿɐʇ) ɐuɐʞsǝp 03:34, 23 December 2012 (UTC)
    • What Deskana said. I don't have an opinion and don't see that it would be helpful even if I did here. My questions weren't rhetorical, I am genuinely curious. And this is outside of ArbCom's scope anyway. Dennis Brown - 2¢ © Join WER 03:39, 23 December 2012 (UTC)
      • Maybe drama is a poor choice of word, I'm trying to say to keep emotions low and one resysopping isn't worth so much discussion. There been way too much scrutiny on the bcrats lately and I don't think this is a case to have a long discussion over considering the circumstances. He became inactive after a RFAr over four years ago and had a RFC prior on the same concerns, I think it is one of these "exceptional cases" ArbCom should mull over to resysop or not, and not worth fighting over. Secret ^account 03:46, 23 December 2012 (UTC)
        • Actually, it is a very interesting, calm and productive conversation from my reading. Arbcom doesn't have the authority to give someone the admin bit, only Crats do. And as we have learned through my previous learning experience, Arbcom has no authority to review the Crats decision unless there is some misconduct by the Crats, and there certainly isn't. I think you are misreading this thread Secret, this is exactly how the process is designed to work, and it is working quite well: no rush, honest discussion, thoughtful review. Dennis Brown - 2¢ © Join WER 03:50, 23 December 2012 (UTC)
  • My opinion would be that the crats as a group owe it to users to decide on matters the community has entrusted to them. To simply fail to conclude on a request would be a abandonment of their responsibility. Also, I don't know why an Arb opinion would matter here. I don't see any possible question of user misconduct or uncertain identity, which is what Arbcom handles. As a practical matter a decision will occur because I'm willing to resysop and intend to do so after the 24 hour period unless another crat says they intend to make a decision to the contrary at that time. MBisanz ^talk 03:55, 23 December 2012 (UTC)

I disagree with you that Crats are required to act. There are very few circumstances where an editor, regardless of permissions, is specifically expected to act. The right to not act is essentially a soft form of WP:IAR. I think it is acceptable for Crats, or anyone else, to say that while policy dictates a specific action, 'I personally do not feel comfortable performing the action, and will leave it for others to act.' If no one can be found willing to carry out what policy calls for, it suggests the policy is sufficiently flawed that it needs to be fixed. That said, I agree with MBisanz's analysis above, (I'm not sure when the 3 year rule kicks in, but no one has claimed it applies here), policy dictates a resysop, and if MBisanz is willing to act, I also see no problem with that. Monty₈₄₅ 07:18, 23 December 2012 (UTC)

I agree no person is required to do anything on Wikipedia, but I don't think a group (crats, admins, etc) should be allowed to collude to shirk avoid fulfilling a function they were entrusted by each of them individually claiming they were uncomfortable making the specific decision. MBisanz ^talk 07:23, 23 December 2012 (UTC)

To be clear, I wasn't endorsing or even referring to colluding here. Colluding to refuse to resysop would be passive-aggressive, and distasteful. The "I won't say no, but I can't say yes" did seem to be a common theme that I took as sincere from all concerned. I've simply not seen that situation here before so it begged the question, which I think you've answered. Dennis Brown - 2¢ © Join WER 10:40, 23 December 2012 (UTC)

Oh, now I get it; that's simple. Crats are elected in part because of their individual history of not getting into fights. One way to not get into fights is to not actually say an opinion, but rather express an initial view and say you're open to more discussion. If you look at old crat chats, they're basically in the same form. I suspect it's a selection effect of the high RFC threshold. MBisanz ^talk 18:34, 23 December 2012 (UTC)

In a situation like this one, I think that one or more Bureaucrat can sincerely say "I just don't know." and mean it, which could lead to the situation I described. From your responses, I basically deduced the answer to my questions to be "Bureaucrats as a group don't have the luxury of not making a decision, and at least one must make the final call.". There is no "do nothing at all" option. Dennis Brown - 2¢ © Join WER 20:28, 23 December 2012 (UTC)

Right, if we're going to be such a small subset of the community because of the trust required, I don't think we can, as a group, avoid fulfilling the functions the community has given us. Part of this is deciding these decisions. If we want to be seen as legitimate delegates of a community function, we can't shirk the responsibility when the going gets tough. MBisanz ^talk 20:54, 23 December 2012 (UTC)

I would like to correct TRM's assumption about the ten-day suspension. It wasn't a mask for tool removal or any such thing; we desysopped plenty of administrators back then and if we thought he deserved it we'd have done so. The incident in front of us just wasn't all that serious by itself. Administrators make bad blocks all the time; if he hadn't blocked a user with stout friends it never would have come to arbitration. Having come to arbitration, we inevitably passed a remedy but it wasn't much. We deliberately did not desysop him, and we could have. I don't know if that helps your deliberations. Mackensen (talk) 05:00, 23 December 2012 (UTC)

Please note that none of the current arbitrators (either the 2012 arbitrators or the 2013 arbitrators) were part of the Committee that decided the InShaneee case in 2007. I do remember the case from the time, however, and I think it is clear that if the Arbitration Committee had thought that InShaneee should be desysopped and compelled to undergo a new RfA to become an administrator again, they would have voted that remedy. When the case closed with a 10-day suspension remedy, and InShaneee requested and was granted the tools back at the end of the 10 days, that was the end of the matter. At the time InShaneee became inactive, there were no remaining disputes open regarding him, and so from the perspective of "under controversial circumstances" or "under a cloud," I think under the current policy he is entitled to reinstatement. :

Of course, quite independent of the arbitration case, it is debatable whether an administrator who's been inactive for almost five years should be entitled to be reinstated on request. I personally have mixed feelings about that subject, but on balance I think our experience is that most of old-time administrators who came back from long breaks and reclaimed their adminships have used resumed their use of the tools in a cautious and responsible fashion. But the community has recently discussed this at length, and the consensus was to change the policy—but also to build in a grace period before the new policy took effect, for those who returned and requested adminship back before the policy change took effect. For better or worse, it seems to me that InShaneee and the others posting on this page fall into that category. Newyorkbrad (talk) 21:29, 23 December 2012 (UTC)

 Done I've gone ahead and resysopped per my analysis above. MBisanz ^talk 03:46, 24 December 2012 (UTC)

Wow, so much for discussion and consensus. Four bureaucrats have commented on this request. Two of us (Rambling Man and I) determined that resyop without RfA was inappropriate. A third (Deskana) expressed the view that he has leaning to agreeing with us. You then posted an analysis that came to the opposite conclusion and, without getting input from other bureaucrats or discussing it further with ourselves, you decided to proceed on the basis of your own analysis. Pleas explain. WJBscribe (talk) 00:16, 25 December 2012 (UTC)

So this is what happens when I leave a discussion alone for a day? How disappointing. Perhaps the term "bureaucrat team" should be reconsidered, because I see no team here. --(ʞɿɐʇ) ɐuɐʞsǝp 02:31, 25 December 2012 (UTC)

To me the recent events, both on the Polascribe matter and more recent ones seem to show that maybe we should be holding some confirmation RfBs. Snowolf ^{How can I help?} 00:19, 25 December 2012 (UTC)

A motion of no confidence in the team. Re-confirm them all? Start now in the early hours of Christmas. Close early New Years Day. Won't the editors with life-Wikipedia balance be surprised when they return? --SmokeyJoe (talk) 03:17, 25 December 2012 (UTC)

When all the bureaucrats run reconfirmation RfBs at the same time... who closes them? Hah, that's actually a pretty funny quesiton. --(ʞɿɐʇ) ɐuɐʞsǝp 03:19, 25 December 2012 (UTC)

TRM has said later that he isn't as a crat when he's asking these questions and he's stated things in this thread which presuppose a resysop will be granted. Deskana, among other comments he made, indicated he did not think InShaneee was under a cloud but then later said he thought we should not decline and not resysop. WJB, you said you wanted more input, which I and others gave. Subsequent to both your and my comments, Mackensen and NYB provided probative evidence regarding the state of affairs that existed at the time in question, which, combined with my own analysis and the other comments, I found warranted resysopping after the 24 hour waiting period. I've always thought the resysopping process involved a crat making a decision in the same way an RFA or rename involves a crat making a decision; they consult with other people, but at the end of the day, any errors in the resysopping (like if it's premature or the crat has a conflict) are the resysopping crat's responsibility. I asked if anyone felt strongly enough otherwise that they wanted to issue a decision that he should not be resysopped, but no one did. I value the collegiality of the crat team, but I've never thought of resysopping as a group decision in the same way a crat chat is. I've also commented further on my talk page to WJBscribe specifically. MBisanz ^talk 03:54, 25 December 2012 (UTC)

I would say Mackensen's comments have alleviated my concern that a grave mistake was made by resysopping InShaneee. I wouldn't say his comments made me think that we made the right decision by doing it, though. I'm still particularly disappointed that you took action when we were still discussing it. But I guess there's no point in me really thinking about it anymore... --(ʞɿɐʇ) ɐuɐʞsǝp 01:49, 26 December 2012 (UTC)

I echo Deskana's disappointment. If this was not a "group" decision, then it appears to have been an individual decision to overrule two other individual decisions. That's not the way we do things. WJBscribe (talk) 18:16, 27 December 2012 (UTC)

I'm also disappointed by the unilateral decision but from the sounds of it, I confused MBisanz into thinking I agreed with a re-sysop. I think the closest I got to that was to say that procedurally the resysop would most likely go ahead. I don't recall being any more positive than that. The Rambling Man (talk) 18:19, 27 December 2012 (UTC)

After reviewing this wall of text, I find myself leaning toward MBisanz's assessment of the situation: I don't see that he left to avoid further scrutiny, and what scrutiny there was fairly small potatoes and didn't rise to the level of "leaving under a cloud". While I can see some valid arguments on the opposing side, I don't think there is enough there to prevent the return of the admin bit (again, based on MBisanz's assessment, above). ···日本穣^? · 投稿 · Talk to Nihonjoe · Join WP Japan! 08:10, 28 December 2012 (UTC)

Same boat as Nihonjoe; I would've been supportive of the repromotion. I do think that we don't need to be beholden to the 24 hour countdown from request to restoration, though. EVula // talk // ☯ // 15:58, 28 December 2012 (UTC)

FWIW I support Matt's decision and would have come to the same myself. We bureaucrats are not ArbCom lite. There are many admins in good standing who have had ArbCom remedies placed on them in the past; when the remedy is filled, the user is reinstated back in good standing unless they exhibit behavior which indicates the remedy was ineffective, and in this I believe I respectfully disagree with Will. In this case, the user left in good standing, and thus continued with my perception that asking for tools to be removed does not mean the person stops being an admin but is taking a vacation (EXCEPT in RtV cases) and thus tool restoration in this case was warranted, IMO. -- Avi (talk) 22:57, 30 December 2012 (UTC)

Noted. FWIW, I have no issue with people reaching a different conclusion to me or necessarily with the outcome - just how we got to it. This discussion should have happened before anyone acted. WJBscribe (talk) 12:11, 4 January 2013 (UTC)