Guild Wars Wiki talk:Adminship

From Guild Wars Wiki
Jump to navigationJump to search

Bureaucrats, elections, arbcomm[edit]

So, it's time for another election, but as I was starting to make the page, I couldn't help but think: it's GW2 beta weekend time, GW2 will be released some time this year, this wiki's activity level is getting lower and lower, and who cares about elections anyway. I have a feeling it's been more apathy than opposition when it comes to doing something other than voting in elections every four months, and I think with GW2 around the corner (for real this time), it'd be good to have a stable bureaucracy and more sysops.

Scrap Arbcomm, letting bureaucrats be bureaucrats+sysop in truth as well as technicality. Scrap elections, scrap terms, and choose afresh bureaucrats who will serve indefinitely. Perhaps use normal RfAs to choose them; maybe even borrow from GW2W's RfA system. Either way, I think these are things that aren't too controversial. pling User Pling sig.png 17:10, 9 June 2012 (UTC)

I've been saying this for years now. Definite support. -Auron 18:33, 9 June 2012 (UTC)
But, but, but ...all I ever do on the wiki these days is vote every 4 months :( (meanwhile, back on Earth - strongly support.) --snogratUser Snograt signature.png 21:30, 9 June 2012 (UTC)
Regarding sysops, I think each election period should be used to update the status list. Since december 2011, I have only seen 3 out of 16. Also, I would like to see those users granted with administrator tools make more use of Guild_Wars_Wiki:Sysop_guide#Cultural_reverence_of_sysops rather login to delete only. I have been checking the Recent Changes for half a year now and its non-sysops who do the explaining. Which makes me think that I know what sysop is in theory but unseen in practice. User Yoshida Keiji Signature.jpg Yoshida Keiji talk 12:02, 10 June 2012 (UTC)
Well, there was a long history of that, regarding the use of the word "janitor" being applied to the sysops on this wiki. But like pling said, it's mostly apathy now as many people have moved on.
I support (even though I'm doing what Yoshida said - deletions). If someone would actually create some drama over this, it might actually liven up the place a little. :) -- User Sig.png 15:57, 11 June 2012 (UTC)
From the 16 and even out of 3, you are the only one that actually bothered to leave messages refering to background, giving the big picture and explaining further steps to move on (that's why I was thankful). The problem Im seeing is that if regular users leave comments in new user's talk pages; it's good but...since they are not sysops, they don't need to detail or reply in dialogue. And without interaction between users the community itself cannot grow. I would like to see sysops assisting active user and /un-stuck issues that are on halt. I think "Ask a question" is a good example of how the entire wiki should be handle. There are several questions around here and there but left with no answers (same case as drop research sections without tables to fill in = show the way, and users will do). User Yoshida Keiji Signature.jpg Yoshida Keiji talk 21:00, 11 June 2012 (UTC)
Admin duties are things like warning, blocking, deleting. Stuff like talking with other users and talking about drop research aren't admin-specific things - it's something any user can do. Even if an admin gets involved in something like that, they're doing it as any normal user would, not in an admin capacity. Civil dialogue and explaining actions are things all users are encouraged to take part in, not just admins.
But this is all beside the point, as this section is about bureaucrats and elections. Feel free to create another section to discuss general admin involvement. pling User Pling sig.png 21:30, 11 June 2012 (UTC)
There have been no arbcom requests since 2010, and no accepted/resolved cases since 2009. The wiki has been quiet for a couple of years now. It's safe to that the system is dated and ready to be removed, and this isn't including any opinions of whether the arbcom system was any more effective than, say, user committees.--Riddle 22:30, 11 June 2012 (UTC)

(Reset indent) I have no opposition to anything said, and would like to say that the past 3 or 4 elections have felt one-sided with the same people being re-elected and only 1-3 people even attempting to run/being nominated. That said, I dislike seeing 75%+ of the list of admin being red in "inactive" and suggest the premise of "# months of inactivity results in revoking of seat" with someone else being put in place - be it by election or RfA. Konig/talk 04:42, 12 June 2012 (UTC)

Heh. There's your drama, Aberrant. -- FreedomBound 11:50, 12 June 2012 (UTC)
^-^ Well, the original stand was that once we've trusted someone enough to be an admin, then unless they prove themselves unable to handle being admin anymore, we just let them be, active or not. But that was when GW2 was a long way off. Now, it's highly unlikely that the majority would even consider returning to a more active role here. We could always drop a message on their talk page. Still, if we start trimming our list of admins, should we first try to get more admins? Are there admins willing to step up to maintain this wiki (instead of "stepping up" on the GW2 wiki instead)? -- User Sig.png 14:18, 12 June 2012 (UTC)
Currently we have enough active admins to keep the wiki in decent order. I would personally support the removal of inactive admins since they're not contributing so don't need the rights :p. Removal of short fixed terms, elections and arbcomm system along with longer terms sounds like a sensible idea for bureaucrats. 19px Chieftain Alex 15:24, 12 June 2012 (UTC)
If we're going for indefinite bureaucrats, I don't see a reason to not have indefinite sysops (and I don't consider trimming red blocks a valid reason). Also, Konig, there's no "place" that the inactive sysops are keeping reserved; we can add new sysops whenever we want, without having to remove any inactive ones.
But, again, that's another topic (and these arguments have already been made); this topic's about bureaucrats :P. pling User Pling sig.png 15:52, 12 June 2012 (UTC)
As one of the currently seated bureaucrats, this act to permanently install me in power is glorious. On a less power-hungry note, I think elections have become more of a hassle than a help; we're not having issues with needing bcrat turnover or fresh blood for ArbComms. To that end, we should have bcrats be permanent until they step down/drop off the face of the earth. Also drop ArbComms, since those haven't been relevant and we're now trusting in our sysops more with discretion. But, to transition things into the new system, we'll need some sort of way to establish the bcrats from here-out, and how to replace ones that step down (likely the same system with different scope). That does imply that we want 3 bcrats, but that would be fine to change or retain. --JonTheMon 16:53, 12 June 2012 (UTC)
@ping: I know sysops don't have a limit for positions, I was implying we could make. just tossing ideas about. Either way, no opposition from me about improving the admin system, especially bureaucrats. Indefinite until inactivity or stepping down sounds like a good course, for both bureaucrats and sysops. Konig/talk 17:50, 12 June 2012 (UTC)
Just my two pence: before shortening the list of admins, please announce this and allow a transition period (like 1 month?) to let people be more active if they desire. Then exclude those who don't like. --Slavic 18:34, 12 June 2012 (UTC)
@Jon; we could just have them pick "successors" when they feel they're too inactive to be of any benefit to the wiki. We're a small enough community now that everyone knows everyone, and we trust the bcrats enough to not pick dipshits to replace them. -Auron 06:39, 13 June 2012 (UTC)
Three was a good number and unless there's a compelling reason to move away from 3, let's just stick to 3. -- User Sig.png 14:22, 13 June 2012 (UTC)
The wiki has changed a lot since it started up, and the 4-monthly elections have been obsolete for a while now. As such there is no big problem with doing away with regular elections. However, the number of admins (3) has not shown any downside, so I don't think there is any reason to change that. Regarding the procedure to select bureaucrats, I am opposed to bureaucrat-self-selection. We'll have very long (infinite?) periods soon, so why change a prodecure that will not make any hassle due to overuse anymore. Given that we will not have the downside, what arguement could you possibly make against the current procedure? It works and has never selected bad bureaucrats. --Xeeron 17:18, 13 June 2012 (UTC)
The issue of inactive sysops very much revolves around how you look at sysops Koenig: If you feel that being a sysop is some kind of reward or present, then it is unfair to give that reward to inactive people. However, if it is a box of tools, then there is no problem with inactive "tool box carriers", since we have an unlimited amount of tool boxes. --Xeeron 17:22, 13 June 2012 (UTC)
Like auron and others said, this needed to be done years ago. I definitely support plings proposal. --Lania User Lania Elderfire pinkribbon.jpg23:47, 13 June 2012 (UTC)
If the entire "process" of electing/appointing "bureaucrats" and "arbcomms" was to "police" the WIKI, the GW gaming community, the "scammers" and other assorted deadbeats, then it's STILL a necessary "occupation"----------after all, "if the cat's away,the mice will surely play". The GW community (both for GW and GW2) will still need it's "won-ton" (or half-pound as the case may be) "enforcement" arm as a "last line of defense" against the "barbarians at the gate". The success that the community has had in keeping GW (and this WIKI) in a "reasonably clean" condition is, in part, BECAUSE of our elected bureaucrats and arbcomms. This game has not yet been interred, all of the questions have not been asked (or answered), and though GW2 "MAY" stand alone, it will be a far poorer place without the GW "foundation" supporting it.
My suggestion is this:
If you are going to maintain an active GUILD (or be a member of an active GUILD) in EITHER GW or GW2, that GUILD needs to maintain an ACTIVE presence on the WIKI, willing and able to serve a term as a bureaucrat OR a sysop----AS NEEDED. (meaning: you run for election AND SERVE THE TERM if elected, or are available to serve when/if a WIKI "crisis" demands additional assistance to resolve (smiting hackers, spammers, thieves and other assorted riffraff)---who knows, you too might get a "green" (energy-neutral) weapon system for your very own use!! 17:26, 24 June 2012 (UTC)
How is that supposed to be related to the changing of beaurocrats to indefinite terms, arbcomms (users being a PitA on the wiki) or elections? 19px Chieftain Alex 18:15, 24 June 2012 (UTC)

(Reset indent) I've long thought that the current system was too cumbersome for the current level of participation in the wiki. I'm not sure I like GW2W's system. But I think we either trust our admin team...or we don't. If we do, it's easy:

  • Appoint for life; the B'crat team chooses its own successors. Their only specific responsibilities are promotions/demotions and (on rare occasions) dispute resolution.
    • If there are objections, we can hold a reconfirmation.
    • If a chosen successor isn't yet a sysop, then they go through an RfA.
  • They should have the same rights/privileges as sysops.
  • Issues that require an appeals process can be handled on an as-needed basis by any three sysops. Call it an armcomm, call it a court of appeals, doesn't really matter.

Tennessee Ernie Ford (TEF) 19:52, 24 June 2012 (UTC)

Guild Wars Wiki:Appealing a block and regular ol' discussion is enough for an "appeals process". Let's not define a number required for something to be sorted out. Re choosing bureaucrat successors; I'm fine with bureaucrats choosing their own successors (either by themselves or after discussing with the other bureaucrats). But how do we choose this first group of bureaucrats who will serve indefinitely as sysops+bureaucrat? pling User Pling sig.png 17:58, 25 June 2012 (UTC)
Re: # to review an appeal: the point is we don't need to have 3 elections/year to create an independent review panel; any reasonable, but formal system of appeals will do the trick.
Re: which b'crats do we start with. The ones we have now; I don't see a material difference with our current system in which incumbents have always won (except when there was, in effect, a recall movement). Or, at worst, hold the next three elections as scheduled, but changing the terms to permanent.
One thing I forgot to mention is that there needs to be some way to determine if a b'crat has become inactive (I think semi-active is fine, as long as they respond in a timely fashion to queries). I think the easiest system is to allow anyone to suggest (based on recent contributions) that a b'crat is inactive and let the active b'crats choose a successor. – Tennessee Ernie Ford (TEF) 18:15, 25 June 2012 (UTC)
Regarding the point that incumbents usually win, while we do have a fine group of bcrats, bear in mind that there are a number of former bcrats (myself included) who simply don't run anymore because of how bcratship interferes with being a sysop. Removing that issue as suggested here would likely see a swell of interest (if perhaps a small one, as some have faded away from the wiki overall). - Tanetris 18:45, 25 June 2012 (UTC)
Fair enough. In that case, I'm agnostic about whether to hold a massive "choose three" election soonish or to stick to the current schedule and elect one at a time. (The latter has the advantage of giving different people a chance to think through their interest in the role...and allow different parts of the community a chance to choose.) – Tennessee Ernie Ford (TEF) 19:34, 25 June 2012 (UTC)

Are we ready to agree?[edit]

(Reset indent) I see widespread support and no opposition at all to the central ideas:

  • B'crats are appointed for life.
  • B'crats are special sysops with the power to promote and resolve disputes.
  • Arbcom is dismantled. Any appeals can follow the same process as Guild Wars Wiki:Appealing a block.

There are also some issues we seem to agree are beyond the scope of this discussion:

  • Do we need to purge the list of sysops so that the "inactive" section isn't so large?
  • Do we need a larger number of active/semi-active sysops?

There are some missing details:

  1. How do we select the first set of indefinite-term b'crats? One election? or use the next three in the schedule to select the people, one-at-a-time. (I don't think there's full support to grandfathering in the current group.)
  2. How do we decide when a b'crat is inactive enough that they should be demoted to sysop?
  3. How do we choose replacements?

(1) I'm okay with one big election or sticking to the current schedule to choose. The first gets it done quickly, but the second offers more opportunity for people to participate.

(2) I think we can offer two objective but arbitrary definitions: they haven't contributed at all for 6 months (or 3 or whatever) and/or on more than one occasion, the community couldn't reach them to resolve a timely issue. However, the simplest would be to let anyone propose that a b'crat is inactive and follow the existing RfR process.

(3) In choosing a replacement, I prefer to let the remaining two b'crats choose. Yeah, it lacks a classic balance of power aspect, but we're talking about the wiki, not the government of a new republic. I like the idea above of requiring a new RfA to confirm the choice: that ensures that the person becomes a sysop (as required) and it gives the community a chance to chime in, without making things too complicated. – Tennessee Ernie Ford (TEF) 09:07, 28 June 2012 (UTC)

1. If nothing else, hold 1 election and the top 3 vote counts get the seats. Still not a fan of elections though.
2 and 3. My suggestion was mostly that the bureaucrat himself would decide when he was unable to continue contributing, and would at that time appoint a successor. Some people (like poke) can get hectic real life schedules, but if called to the wiki for any specific task, would do his best to see it through - but when someone loses their desire to contribute (or oversee the project) they know it's time to pass on the torch. Most people, especially the ones actually serving as bcrat, see the position as a duty to the wiki and not as a badge of honor, and would willfully pass it on when they lose interest in performing the duties. PvX isn't the greatest example of a wiki, but that's largely what we've done over there - I stopped "caring" about the project in 2010 sometime, but I made sure bureaucrats were always around who did care, and made sure they knew to promote people if they ever went inactive. -Auron 09:44, 28 June 2012 (UTC)
I'm good with that. This revamp effectively says that we agree to trust b'crats to get things right and to take their job seriously and Auron's suggestion builds on that more so than what I proposed. (And, as a backup, RfRs are always available for any sysop, including a b'crat.) – Tennessee Ernie Ford (TEF) 09:50, 28 June 2012 (UTC)
Fully agree. One point occurred to me (not overly changed by this proposal, but still...) - what safeguards are in place for the unlikely situation that a bureaucrat turn rogue? Always wondered ^_^ --snogratUser Snograt signature.png 10:33, 28 June 2012 (UTC)
ArenaNet can make server-side changes to strip his power, and if he manages to do something bad enough, revert to a backup. Most edits/user rights changes can simply be reverted. -Auron 11:05, 28 June 2012 (UTC)
Ty, Auron :) --snogratUser Snograt signature.png 11:42, 28 June 2012 (UTC)
How am I supposed to participate in elections? How to make the right choices? If a "new" Bureacrat is to be promoted among current sysops...old election candidates seem pointless as what matters is how much active they have been as of the last months. I have been trying to understand this since the last election. Sysops are just users with three more tools: Block, Delete and Protect. Which means...these should be users who are "very active" in maintenance and bookkeeping on a "very regular" basis. Now the users who are currently doing both maintenance and bookkeeping...none are sysops. On the other hand...the sysops...are not much seen in both maintenance and bookeeping. How can regular users find out? By checking the contributions, being the most seen: Special:Contributions/Auron, Special:Contributions/ and Special:Contributions/Farlo. And also by doublechecking: Special:Log/block with Special:BlockList and Guild_Wars_Wiki:Admin_noticeboard plus Guild_Wars_Wiki:List_of_candidates_for_deletion.
How to check Bureaucrats activity? By looking Guild_Wars_Wiki:Requests_for_adminship (history) and Guild_Wars_Wiki:Arbitration_committee/Requests. Since there has been no arbitration requests for years and only one (meh) RfA... I don't know if the current Bureaucrats are perfoming (active/inactive) as expected (positive/negative). How can a regular user know if they are doing well? So that we can create an image...and then look back to sysops and think who could do better by replacing a current one? Are Bureaucrats supposed to be only 3 or could there be more of them? I don't see administrator ranks keeping the wiki organized or updating pages such as filling up articles with {{stub}}, checking revisions and fixing lazy/lame edits, participating in talk pages to discuss article issues, etc. Elections will keep coming but I still cannot take part, nor will know the how in here GWW...GW2W...GW3W... and so on...User Yoshida Keiji Signature.jpg Yoshida Keiji talk 13:00, 28 June 2012 (UTC)
You can still look at past RfAs, discussions, arbcomms, etc, to see how candidates have acted/would act, even if there haven't been any recent situations which require action. You can also ask candidates questions and base your opinion on their answers.
Regarding the three issues above: (1) like Auron, I'm not a fan of vote-based elections. However... it's quick and relatively effortless. I'm not sure whether a big to-do with RfA-style RfBs would be better than simply voting on it. I'll leave that to others to decide. If we do vote, I'd rather have them all at once; I can't see there being more or even the same level of activity after Guild Wars 2's release than there is now. (Tbh, as long as Tanetris is promoted, I'm fine with whatever.)
For (2) and (3), what Auron says sounds ok. pling User Pling sig.png 23:36, 28 June 2012 (UTC)
For what it's worth, I'm chiming my voice in to agree with Pling. -- Armond WarbladeUser Armond sig image.png 00:38, 29 June 2012 (UTC)

Edging closer to agreement[edit]

(Reset indent)

So it looks like we have agreed on:

  • B'crats are appointed for life.
  • B'crats are special sysops with the power to promote and resolve disputes.
  • Arbcom is dismantled. Any appeals can follow the same process as Guild Wars Wiki:Appealing a block.
  • The first three infinite-term b'crats are to be selected by election, with the top three vote-earners taking the role.
  • A bureaucrat stepping down chooses their own successor.

These issues remain beyond the scope of this discussion:

  • The list of sysops marked as "inactive".
  • The number active/semi-active sysops.

I think the only issues remaining are:

(4) When a b'crat steps down (and appoints a replacement), do we require an RfA?
(5) In the rare event that they don't appoint a replacement, what do we do?

I propose that (4) an RfA is only required if the person isn't already a sysop and for (5) we allow the remaining b'crats to demote (it's one of their existing duties ) and decide how to replace, i.e. instead of spelling out every possible situation, we empower the b'crats to act for the best interest of the wiki; they can decide whether to hold an election, promote an existing sysop, or even leave the position vacant, as fits the existing levels of wiki activity.

Unless there are objections to the current proposal, I think it's time to write it up formally and move on to speculating about how many editors we'll have here in September. – Tennessee Ernie Ford (TEF) 20:23, 30 June 2012 (UTC)

Draft rewrite[edit]

I've proposed a draft version of the new policy. Please make appropriate amendments and/or comment on its talk page. I think the only other change we'd need to make would be minor corrections to the election policy (since it would only be used one more time) and withdrawing the arbitration policy altogether. The original GWW:ADMIN doesn't include specific mention of GWW:BLOCK, but maybe it should. (Arguably the initial section on sysops could be rewritten for clarity/simplicity.) – Tennessee Ernie Ford (TEF) 22:44, 9 July 2012 (UTC)

Sounds good - although do we want to keep existing arbcomm rulings in effect? (PS thanks for keeping this thing moving, TEF.) pling User Pling sig.png 16:29, 24 July 2012 (UTC)
You mean the decisions made by prior arbcomms? We should absolutely keep those; they are accepted exceptions to the general policies of the wiki, carved out to handle exceptional situations or individuals. I only meant we can strike out the text of the rules governing arbcomms, since we won't be holding any more.
PS I'd like to see a few more replies to this before making such a big change. I'm hoping that some of the current admins can reply (not to mention some of our current frequent contributors). – Tennessee Ernie Ford (TEF) 16:46, 24 July 2012 (UTC)
I have no issues with the draft. This was essentially the gist of the bureaucrat role on GuildWiki until it got nerfed with the originally admin policy. -- User Sig.png 05:10, 25 July 2012 (UTC)
I don't have any problem with it. Manifold User Manifold Neptune.jpg 15:26, 25 July 2012 (UTC)
Get going with the acceptance. 19px Chieftain Alex 23:58, 28 August 2012 (UTC)
I decided to wait until the mass chaos of the GW2 launch is over before taking this up again. – Tennessee Ernie Ford (TEF) 01:50, 29 August 2012 (UTC)
You can just push it through :p -Auron 05:45, 29 August 2012 (UTC)

(Reset indent) Now it's a good time to take this discussion back. We don't need to wait for active users in GW2W who are busy there. What matters to the GWW community needs to addressed independently of GW2W contributors.

I will once again bring up the Sysop's topic...because now there is a better argument that I didn't had before. After watching to see if inactive sysops whose powers were kept in case they eventually returned back.... such theory had failed us since last time this discussion was active. Looking back at time, I think the Community should had elected new active Sysops.

These new Sysops should be able to remain active until the Guild Wars Beyond of Nightfall release and a few months afterwards...then GW itself won't have any other attraction left in my opinion, to which point I don't think the present time users will care anymore at all (at least thats my own feeling). Bureaucrats have had no need to wake-up, we had no need of them since GW2 release so I guess its congrats to the last 3 and no need to have more of them at all. But since new sysops could go inactive after some time... I think it would be wise to have them appoint other users to pass the torch in case no activity is seen from then after a certain period of time. These extra candidates should be given a reference as to why the "new" sysops would think their successors could take place. And once again... remove the inactive sysops, there are of no use to us, the Community. User Yoshida Keiji Signature.jpg Yoshida Keiji (talk) 12:59, 5 October 2012 (UTC)

There is no benefit to removing inactive sysops. New sysops can be added at any time if/when there are willing users who would make good sysops. - Tanetris 17:58, 6 October 2012 (UTC)

New bureaucrat[edit]

We didn't really go through any election/RfA process to select the indefinite-term bureaucrats (see above). I want to give my bureaucrat tools to someone else though, since I barely check the anymore (and I was expecting a fixed term when I was elected). Who do you think that should be, and how do you want to go about it? Just choose someone and discuss it here, or create an RfA? pling User Pling sig.png 19:00, 12 January 2013 (UTC)

Promote the new policy so it's official and then select someone from the current list. If they aren't an admin, call for an RfA. – Tennessee Ernie Ford (TEF) 22:17, 12 January 2013 (UTC)
Ah, did you notice that we merged your draft suggestion a while ago onto this page? Chieftain Alex 22:46, 12 January 2013 (UTC)
LoL — erm, apparently not. – Tennessee Ernie Ford (TEF) 01:24, 13 January 2013 (UTC)

Suggestions: Tanetris and/or Auron. Discuss. pling User Pling sig.png 18:08, 17 January 2013 (UTC)

I'll say that I check my watchlist on a more or less daily basis, though I don't generally actually do anything beyond a quick glance around for anything glaringly obvious that needs doing administratively. My impression is that Auron is more hands-on active, so if he actually wants bcratship, he's probably a more logical choice. That said, I'm around, I know the drill, I assume I'm still generally trusted, I wouldn't turn it down. - Tanetris 21:49, 17 January 2013 (UTC)
I'm indifferent. The role of bcrat has expanded since I last held a seat years ago, but sysop still gives me more elbow room to bash people around with. Tanetris would be a fine choice for bcrat. -Auron 05:54, 18 January 2013 (UTC)
My suggested requirements: understands the wiki and its community & rules; can manage disputes without creating new ones; is available when needed; pays enough attention to RC to understand if there's an issue. Here's what I think the role no longer requires: constant presence, frequent contributions.
Evaluating Pling's suggestions based on the above, I'd rate both Tanetris & Auron as "strongly recommended." I think both have a lot of positives and, if I were to nitpick, a few minor negatives. In particular, both know when to step in and when to let the community work things out. GWW is lucky to have them as sysops and I doubt things would change much based on choosing one or the other for b'crat.
short story for Pling: you can't go wrong flipping a coin for this one. – Tennessee Ernie Ford (TEF) 06:21, 18 January 2013 (UTC)
Gave it to Tanetris. As Auron says, being a sysop is probably less restrictive than bureaucrat (even if only a little bit), and since he's one of the more day-to-day active sysops, I suppose it makes more sense to keep him as a sysop and give bureaucratship to Tanetris. pling User Pling sig.png 14:30, 18 January 2013 (UTC)