Showing posts with label bureaucrats. Show all posts
Showing posts with label bureaucrats. Show all posts

Thursday, 15 January 2009

Commons RFA is turning into English Wikipedia RFA

Yes, you read right. It's a bit of a late post really because it's been happening slowly but surely for months, but I thought I'd write about it now. People try to promote the idea that Commons is a lovely place to work, where everyone works together in peace and harmony. Frankly, I prefer English Wikipedia. This is one of the reasons I resigned on Commons. While English Wikipedia is far from perfect, its community is larger so there are a larger variety of people.

While not strictly an RFA, ABF is having an RFB on Commons. People make a huge deal out of bureaucratship. I wish I knew why. Perhaps it's because they have the only irreversable action that can be given to just anyone (as opposed to Checkuser/Oversight where one must be identified and over 18). I have never understood why bureaucrats do not have ability to reverse +sysop. So much so, I managed to get the ability added on Meta-Wiki.

Anyhow, this RFA has had three opposes in particular that bother me, all by respected admins on the project, one a bureaucrat, two checkuser and two steward. Such people have influence, and they know it. So it is very important they use it wisely. Let's look at the opposes in question:
Oppose. ABF is a very good contributor to Wikimedia Commons, but I feel unsure about giving him the big mop. While I have no reason to believe he'd be unfit for user renaming or SUL stuff, I am really uncomfortable with giving him the ability to promote sysops. Nothing personal, I think ABF is a good sysop, but I happen to think we have much better candidates for bureaucratship. guillom 19:14, 14 January 2009 (UTC)
What's wrong with this? There's no evidence or examples. Not a single one. While RFA is of course about giving ones opinion on a candidate, it would be immensely helpful for the rest of us to give some kind of reason for this "bad feeling". Guillom has simply not explained how ABF would be bad choice, just that he would be.

Oppose I believe ABF is a hard worker and I am grateful for all the time he puts into Wikimedia Commons. I wish, however, he would have asked the advice of sitting bureaucrats before accepting this nomination. This is a completely different role than sysop; and while I trust ABF's abilities for the sysop role, I have to oppose his nomination for bureaucrat. This is not personal, nor is it an indictment of my faith in ABF's good faith and honest intent. Bastique demandez 19:18, 14 January 2009 (UTC)
What's wrong with this? Since when do people need to ask advice before nominating? We don't ask before making an admin nomination - why are bureaucrats so special? Bureaucratship is indeed a completely different role, but only as an historical accident. If things had gone differently, admins and bureaucrats could share the same abilities. It does not require any better judgement than an admin, even less so. I trust ABF to evaluate consensus on RFDs, as we should since he's an admin. Therefore, he should be trusted to evaluate consensus on RFAs, which are really a vote count anyway. Any sensible person with a calculator can do it. Bastique continues, explaining he trusts ABF as an admin, but not bureaucrat. He neglects to explain why though, and that it isn't personal (though of course it is personal, it's ABF's RFB...)

Oppose - ABF is a fine administrator but simply is not the best choice for this role. Despite ABF's activity in nominating users for adminship (and his participation in other RFAs where they are not the nominator), I do not think they have the requisite judgement to perform promotions. This is not to say that they are untrustworthy per se, however they are not well suited for this role. I too wish ABF had consulted some trusted users (whether bureaucrats or not) prior to this request. I would have much preferred to avoid making such statements in public, however given that this is a live request, I find myself unable to support this candidate. — Mike.lifeguard | @en.wb 20:16, 14 January 2009 (UTC)

Mike does not think he has the necessary "judgement" to perform promotions (though promotions are not difficult at all). As with the other two, he does not explain how he gets that idea, just that he does. And again, who is to suggest that ABF didn't contact anyone first (not that it's necessary)? He is supported by Cecil, a bureaucrat, who clearly thinks differently to the others. And there are other trusted people supporting him.

I am currently supporting him. I don't have issues with people opposing, but opposing with improper or lack of reasoning is unhelpful to the candidate, other voters, and merely looks like well-poisoning. Being opposed is not a pleasant thing, I assure you, especially from well-respect users. Pull your finger out and oppose properly if you have to do it.

Wednesday, 7 January 2009

Enigmaman's RFA

The latest drama to hit enwiki RFA is Enigmaman's RFA. It's his second RFA, that was apparently going well. Very well actually, at 46/0/1 when it was put "on hold". Last month, a record 12 admins resigned, as well as two bots, so I'm not exactly sure if we do have enough admins at the moment. Anyway, Deskana put the RFA on hold, and posted the following message to the talk page:

I have placed this RFA on hold.

During the course of a checkuser investigation into an IP that would be editing in violation of Wikipedia:Requests for arbitration/Privatemusings#Sockpuppetry if it belonged to a user that was editing while logged out, it became apparent that this IP was infact owned by Enigmaman.

I strongly suspected that many of the supports in this RFA would be retracted if they could see the edits in question, but the privacy policy prevents me from disclosing the IP without the permission of Enigmaman. It does not seem appropriate for me, as a bureaucrat, to allow this RFA to continue when many of the supporters were unaware of the entire situation regarding Enigmaman. Therefore, I see two options.

  1. Enigmaman refuses to allow me to disclose his IP. This means that I restart the RFA with a note that the user has been making inappropriate edits while logged out, but am unable to provide diffs due to the privacy policy.
  2. Enigmaman allows me to disclose his IP, meaning the RFA can be restarted with the diffs in question in plain view for people to review.

The edits themselves aren't actually that bad, but I know the RFA crowd can be quite scrutinous when it comes to incivility. I actually think option 2 would work out better for Enigmaman, but that's just my opinion. The edits themselves were probably not blockable, but I imagine people would oppose his RFA for the edits. I probably would.

I hope people understand my actions here. They're not normal bureaucrat actions, but desperate times...

--Deskana (talk) 21:54, 6 January 2009 (UTC)

He actually took a while to post this, so people were fairly curious at to what the issue was. On IRC I asked Deskana jokingly if this was going to cause drama, he said "maybe". I think that was an understatement.

I was fairly surprised when I saw what was written. It was then revealed that Deskana had not contacted Enigmaman in private first, before posting this statement. This is similar to an incident I was involved with in 2007, when Deskana publicly pointed someone out as a sockpuppeteer, without discussing with them in private. While Deskana has not revealed any private information himself, this whole fiasco has indirectly lead the IPs to be revealed by others, through pressure, something which is explicitly forbidden in the checkuser policy. It is my firm belief that checkuser is most certainly a big deal, unlike adminship, and even oversight. Oversight is mostly random phone numbers, addresses, and libellous information about people. Nothing about the actual editors, for the most part, and when it is there is trouble (think Zoophilia). Checkuser is for making catching sockpuppets easier, not publicly humiliating good editors. Deskana's post suggests that many people would switch to oppose if they could see the edits made. This is not the case, at least so far. Several have stated they will be switching from support to strong support (as I shall be). I had a look at the edits, of course. I certainly do not see them as problematic in a way to make me oppose. They aren't Enigmaman's greatest moment, but then who am I to say anything? :-)

The whole thing was handled extremely poorly. It is obvious to all that Deskana should have contacted Enigmaman in private before publicly humiliating him on the RFA. I do not believe Deskana has the integrity skills required for the checkuser role. Tiptoety comments, asking "You feel he should resign because of this single incident? I see no pattern of mistakes or breaches of policy by Deskana, let's not get ahead of ourselves". Yes, I do. Checkuser is not like adminship or bureaucratship, where a few mistakes may be tolerated. I'm afraid this one mistake could have cost EM adminship, which he was easily on the way to getting at the time the RFA was paused. He was put under a lot of pressure, basically forced to reveal his IP, and has been unnecessarily embarrassed and humiliated on-wiki, in a situation that could have been solved without the general wiki population knowing about it. Surprising as it may seem, I agree with Jennavecia's post. The whole thing was a lot of shit-stirring for very little benefit indeed - and it looks like it'll have the opposite affect of what Deskana intended, because people will support because of how poorly Deskana handled this, and how well EM handled it. The whole thing was biased, as Deskana holds both checkuser and bureaucrat right, and apparently used both to unilaterally put a stop to EM's RFA, merely because he "suspected" a lot of people would switch if they saw the edits. I've seen the edits. My opinion has not changed at all. Well, it has - of Enigmaman, my opinion of him is higher. Of Deskana, he's a nice person with good intentions, but I feel he is not suited to continue with Checkuser.

Tuesday, 8 April 2008

Bot Approvals Group

Something that really irritates me is the Bot Approvals Group (or BAG). The job of the BAG is to basically, as the name states, approve (or not approve) bots. I don't know if this is still the case, but the BAG are a self-appointed little group who basically control which bots do and don't get to do stuff on Wikipedia. At one point, there were "mini-RfAs" that allowed people to join this little group. Following an MfD, they promised reform (much like Esperanza lol) and made the process more open - anyone can simply add themselves to the list. But it appears they've reverted back to the old "vote for me" way. I think bots that do get approved need some sort of technical knowledge in some ways, but I think bots and the approval process are one of the most overlooked features on Wikipedia. Why would that be? Well, most bots go unnoticed (with perhaps the exception of vandalbots and archivebots). We just take all their hard work for granted (well, the coder's hard work, but you know what I mean). The approvals take part on this page. You may notice the lack of voting and the very few editors participating in the discussion. Indeed, the page cries out "Please remember that all editors are encouraged to participate in the requests listed below. Just chip in - your comments are appreciated more than you may think!" Right, unless you have a BAG badge, and then your comments aren't considered
nearly as important. Consider the stark contrast to RfA - people are literally falling over one another to vote on as many RfAs as possible. Why is this? Is the bot page not advertised, or well known? Could it be that people are scared to comment on bots, because bots are "scary and evil" and if you let a bad one slip through it could destroy the wiki? On Commons, the bots are done on the same page as the RfAs. This makes sense to me - it's a bureaucrat's job either way, and having them in one place seems pretty sensible. Maybe to keep the page's loading time low, the transclusions could be turned to links? I just think the BAG is an utterly pointless waste of space. I'm currently participating in the discussion here, where I have proposed it be disbanded. Please comment there if you agree with me.

Wednesday, 26 March 2008

Single user login

Single user login has finally been implemented (for admins only). This is where it is possible to have the same user name on every project even if you haven't registered. Eventually being able to have the same preferences such as email address will be implemented. Now with a username like "Majorly", and having registered previously across multiple projects, this wasn't a problem to me since I now own every single instance of "Majorly" across Wikimedia. I feel sorry for other users, particularly those who usurped first names on English Wikipedia (Alison, Daniel, Riana and Sarah come to mind here) since these are names in common use elsewhere, and there will be conflicts. I hope that all these usurpation requests don't drive the stewards crazy :-) Yes, only stewards can usurp accounts that have been linked, by unlinking them. Normal bureaucrats like myself end up with an error message saying the account is reserved. I think the next big thing development-wise will be implementing stable revisions. I personally feel they are a good idea in many ways, but a bad idea in many others. I might write a post on it if and when they are implemented.

Wednesday, 19 March 2008

Species bureaucrats

Something funny I noticed whilst browsing around today here. If you don't get it, there's 6 (5 if you don't count Maxim) RfBs up, and they are all passing!!! Not only this, they are proposing *gasp* that all admins should be bureaucrats! Wow, oh wow! This is the kind of thing that certain individuals would retire over on English Wikipedia should such a thing be implemented. I mean, gosh, RfAs and user renames might get done a bit faster! It sounds dreadful! I wrote a short essay here that I think everyone should read. Basically, it sums up how it is easier to be a bureaucrat than an admin. I am a bureaucrat on Meta-wiki (amazing I know...) and trust me, it means basically nothing. I mean, it's Meta-wiki, hardly one of the major wikis (although we do host a lot of potential WP:BEANS pages). But if someone was to propose all admins became bureaucrats, I'd strongly support it. Bureaucratship is not a big deal at all, and those that think it is need to get their facts straight. If we trust someone as an admin, we can trust them as a bcrat, simple as that.