Memory Alpha
Register
Memory Alpha
(→‎Oppose: I was hoping to not be the first to oppose, but I gave some concrete reasons)
Line 11: Line 11:
   
 
=== Oppose ===
 
=== Oppose ===
  +
*I'm going to oppose this nomination. A lot for Cid's comments, especially about over ''directness''. I realize that as of late this is basically the pot calling the kettle black, but then I wouldn't expect to pass a nomination myself at this time. I have a much more concrete reason, mainly that he wouldn't be able to serve in the role well because of his low activity. If one looks at bp's contributions over the last few years, he goes months at a time without a single edit, and then only a handful of days in a given month with activity. One of the primary roles of administrators is to combat vandalism, and he would not be able to do so on almost any day. We don't seem to be at a shortage of admins able to delete pages, edit style sheets, or move images. At least we aren't in such an extreme shortage that someone with such low activity would give us better service then we have now. The only other major admin tool is the revert button. As far as I know, both bp and I already have the revert button, we were given it independently of admin functionality. --[[User:OuroborosCobra|OuroborosCobra]] <sup>[[User Talk:OuroborosCobra|<span style="color:#00FF00;">talk</span>]]</sup> 16:11, November 22, 2010 (UTC)
   
 
=== Comment ===
 
=== Comment ===

Revision as of 16:11, 22 November 2010

Memory Alpha  AboutPolicies and guidelinesAdministrators → Nominations for administratorship

Please read the full policy on becoming an administrator before nominating someone for administrator privileges. Nominations submitted on this page are considered for at least seven days; during this time, both Administrators and registered members may express their opinions and vote. Unregistered members may not vote. Nominations must be unanimously approved in order to be accepted. Nominations that are unresolved after fourteen days will be rejected. Past nominations, both rejected and accepted, can be viewed here.

bp

Looking over the CSS files are proof enough that bp should have admin powers. While not the most active of users, almost all his edits are on the site maintenance side, and he clearly has a grasp of MA policy, so I don't see a reason to have an admin do all his edits for him. ;) In all seriousness though, bp has been here helping to keep the site looking good and running long before I was, and I think giving him admin powers would be in the best interests for MA. - Archduk3 00:05, November 16, 2010 (UTC)

Support

Oppose

  • I'm going to oppose this nomination. A lot for Cid's comments, especially about over directness. I realize that as of late this is basically the pot calling the kettle black, but then I wouldn't expect to pass a nomination myself at this time. I have a much more concrete reason, mainly that he wouldn't be able to serve in the role well because of his low activity. If one looks at bp's contributions over the last few years, he goes months at a time without a single edit, and then only a handful of days in a given month with activity. One of the primary roles of administrators is to combat vandalism, and he would not be able to do so on almost any day. We don't seem to be at a shortage of admins able to delete pages, edit style sheets, or move images. At least we aren't in such an extreme shortage that someone with such low activity would give us better service then we have now. The only other major admin tool is the revert button. As far as I know, both bp and I already have the revert button, we were given it independently of admin functionality. --OuroborosCobra talk 16:11, November 22, 2010 (UTC)

Comment

Thanks, Archduk3. --bp 22:02, November 21, 2010 (UTC)

This is probably going to be difficult - I'm not trying to deliberately step on anyones toes, but with bp now having accepted the nomination, he of course deserves some other reply than just silence. So - should bp become an admin here? On the one hand, he has been an active contributor for years now, and has helped MA in more than one way during that time - examples are custom scripts and CSS fixes, work on several of the more arcane templates, etc.. On the other hand, being an admin is not only about doing the behind-the-scenes maintenance work, but also about accepting the explicit and implicit rules of a wiki while doing so (if nothing else, at least as a necessary evil). In that regard, I think that bp's directness (for lack of a better term) might lead to some problems down the line. Not enough to actively oppose this nomination, but enough to at least bring it up proactively and ask that this please not happen, should there be further support votes.
Also, and this is not directed at bp specifically , I have to question the reasons for this nomination: should anyone become an admin for the sole reason of giving him access to the site's "layout"? I think not. I see an increased interest in the CSS files over the last few weeks - of course, related to the skin change, but still: the more people are editing the files, and the more often they do it, the higher is the need for doing it while following the typical workflow for controversial wiki edits: discuss first, change later. If this is followed, we don't need to hand out admin access for just the reason of editing the files - and if it is not followed, this might lead to admin edit wars over the CSS files sooner or later. Not exactly what we'd want to have. -- Cid Highwind 13:32, November 22, 2010 (UTC)