UDWiki:Administration/Protections/Archive/2011 06

Shortcut:
A/PT

This page is for the request of page protection within the Urban Dead wiki. Due to philosophical concerns, the ability to protect pages is restricted to system operators. As such, regular users will need to request a protection from the system operators. For consistency and accountability, system operators also adhere to the guidelines listed here.

Guidelines for Protection Requests

All Protection Requests must contain the following information in order to be considered:

• A link to the page in question. Preferably bolded for visibility.
• A reason for protection. This should be short and to the point.
• A signed datestamp. This can be easily done by adding ~~~~ to the end of your request.

Any protection request that does not contain these three pieces of information will not be considered, and will be removed by a system operator.

Once the protection request has been entered, the request shall remain on this page, where it will be reviewed by a member of the Sysop team, and action taken accordingly. Once action has been taken, the system operator will add a comment including a signed datestamp detailing his course of action, and the request will be moved into the Recent Actions queue, where it will remain for one week. After that week is up, it may be moved to the archive (see navigation box below). If the Protection has been granted, the system operator should place the tag {{protect}} on the page(s) that have been protected.

In the event of a system operator requesting a Protection, all the previous points will apply, excepting that a system operator other than the requestor shall review and take action on the request.

Pages in the Protection Queue may already be scheduled protections. For a list of scheduled protections, see here.

Protection Queue

Main Page

This isn't a request so much as a discussion: I notice that I protected the page with the reason "Emergency Protection" about 3 years ago and that it was never unprotected. Given that the emergency is decidedly over I thought we should put this through the "normal" protections process.--The General ^{T Sys U! P! F!} 11:59, 17 June 2011 (BST)

I'm for keeping it protected. It's the most high profile page on the wiki (it has the most views anyway) and I think it's pretty standard practice to protect a wiki's main page. ~ _{14:49, 17 June 2011 (UTC)}

yeah... A bit surprised it needed an emergency to be protected in the first place, thought it would have been one of the first things protected on the wiki. -- ϑ^anceϑ^anceℜ^evolution 15:06, 17 June 2011 (BST)

The main page used to be kept protected a long long time ago. I find it odd that it was unprotected and you had to emergency protect it --hagnat 15:08, 17 June 2011 (BST)

Requested Edits

Place pages requiring editing here.

Recent Actions

Template:Bid

Could someone add a link to Misconduct archives for the candidate to it (ideally for both A/PM and A/RE bids)? Basically, just [[UDWiki:Administration/Misconduct/Archive/{{{1}}}]] somewhere in the line with the rest of the links. —Aichon— 23:26, 10 June 2011 (BST)

I don't mind doing it but there was some discussion on Template talk:Bid as to why it isn't there. Basically, misconduct links are visible when transcluded on A/RE but not on A/PM. I think the idea was that not all prospective sysops (indeed probably the majority of them) are former ops and would not likely have misconduct cases. ~ _{23:48, 10 June 2011 (UTC)}

I'd also like to think that if a sysop is coming back after a long break, then past misconducts wouldn't really be an issue, given that they'd taken time away (other than with obviously massive gross misconduct, in which case most people know anyway).--Yonnua Koponen ^{T G P} ^^^ 23:53, 10 June 2011 (BST)

I couldn't find any relevant discussion about Misconduct links and why they aren't included on the talk page, Vapor. And while I do agree 100%, Yonn, I think that should be up to the people voicing their opinions to decide. The template should merely provide them with all available information regarding the candidate, else we wouldn't also include A/VD links either, since those are equally irrelevant more often than not. —Aichon— 00:20, 11 June 2011 (BST)

I actually thought we'd removed Vd links (I personally quite liked the version with more links) and left it with just talk and contribs.--Yonnua Koponen ^{T G P} ^^^ 00:27, 11 June 2011 (BST)

The VD links are still in it. I prefer more links as well, for the reason I stated above, even though many of them are useless at times. —Aichon— 00:52, 11 June 2011 (BST)

Sorry the relevant discusiion was at Template talk:vndl#Use on A/PM and A/RE. Like I said I don't mind either. We've had several oldschool ops returning and running again so it couldn't hurt. ~ _{02:12, 11 June 2011 (UTC)}

Well, your guys' call. You have my preferred choice, but I won't take it personally if you all decide to deny the request. :) —Aichon— 02:30, 11 June 2011 (BST)

It will take a bit of coding but I can make it work. Alternatively, you can get misconduct to show if you use the variable 2=RE. ~ _{06:36, 11 June 2011 (UTC)}

Sorry for not getting to this sooner. I've been away from wiki since this came through. After reviewing it, I've decided to cycle unedited. The template was specifically designed so that different code would be output depending on which page it was transcluded on. Misconduct links can however be included through the use of a different variable. I'd suggest any returning ops running on A/PM to use the variable. I have however edited the variables section of the template's instruction for use so that it is a bit more evident that the variable can be used for that purpose. ~ _{15:11, 17 June 2011 (UTC)}

Known Bugs

Because I'm sick of muppets posting their shit directly on here like they're FUCKING TOLD NOT TO.
Basically, this should be reserved for bugs which have been confirmed. A fix of the entire bug system is on my to-do list: this is a temporary stopgap measure. ᚱᛁᚹᛖᚾᚨᚾᛏ 04:13, 9 June 2011 (BST)

This may be better resolved with a massive massive red notice at the top that people can't possibly miss... If people wanna sort out this monstrosity the more power to them (I had a go once at archiving the bugs pages, fun), but perhaps it's best not limiting it to sysops? -- ϑ^anceϑ^anceℜ^evolution 04:30, 9 June 2011 (BST)

First off, wow Rev. I wasn't even actually aware of that functionality with semicolons. Second, DDR, I'm not sure it's particularly an issue. Known bugs shouldn't be being edited by the average user anyway and we should probably be treating it like the Main page or something. Seems like a very important resolution place for bugs. Although, yes, the whole system needs to be changed. It should really only be two pages with maybe a template on the main page that shows new bugs reports or something but that can be discussed somewhere else. If you really feel strongly about it being unprotected we can leave it but, I don't really see what the harm is in doing it so that requests to move have some level of peer review first(even if it's just being posted here).--Karek^{maps 2.0?!} 08:54, 9 June 2011 (BST)

Meh, sup to you guys. I personally don't think it needs protection at all (semi protection I could go for) but if you guys want to do it and there's little opposition then go ahead. -- ϑ^anceϑ^anceℜ^evolution 09:28, 9 June 2011 (BST)

How about putting in semi-protection? That'll let experienced users maintain it but (hopefully) prevent newbies from dumping bugs straight onto the page.--The General ^{T Sys U! P! F!} 09:05, 9 June 2011 (BST)

^ -- ϑ^anceϑ^anceℜ^evolution 09:28, 9 June 2011 (BST)

Done that way for now. --Karek^{maps 2.0?!} 09:42, 9 June 2011 (BST)

As a quick note, this is probably the best solution, since protecting it entirely would prevent instances where feedback is beneficial during the bug fix process. For instance, with at least one bug, Kevan thought he had fixed it, but had it pointed out to him that the fix wasn't working, allowing him to act on the feedback and put out a better fix within the day. With protection in place, we'd have to have sysops post such feedback on the behalf of users. —Aichon— 05:00, 15 June 2011 (BST)

Sacred Ground Policy

Sacred Ground Policy but NOT the /People and /Groups subpages. Those I'd like to leave open for people to add to. Basically, I'd like to protect the policy as I wrote it and block watering-down and meddling should I be re-permabanned or if I get hit by a truck or simply stop coming by. -- ™ & © Amazing, INC. All rights reserved. Replying constitutes acceptance of our Terms of Service. 02:01, 31 May 2011 (BST)

Also leave the corresponding talk page open if possible. -- ™ & © Amazing, INC. All rights reserved. Replying constitutes acceptance of our Terms of Service. 02:07, 31 May 2011 (BST)

I'mma refuse for two reasons. 1) it's more of a community page now, like other tactics. 2) it's got portions for general user editing on the main page. --Karek^{maps 2.0?!} 05:01, 31 May 2011 (BST)

Can I reply, or is that forbidden? Anyway, taking the risk... 1.) It might be a dangerous precedent to say a page is community property because the owner can't access it. I never gave permission as such, so I don't understand how it can just... be that way. History also directly supports my case, as McZeds was reverted and protected as per my request while I was still permabanned. McZed's was open to user editing and was around long after I left, but it was still protected. And... 2.) The portions for user editing are actually on the /People and /Groups sub-pages. -- ™ & © Amazing, INC. All rights reserved. Replying constitutes acceptance of our Terms of Service. 06:37, 31 May 2011 (BST)

The bigger issue is it was a public policy and the community continued on with it after your absence. It's more of a representation of the game then an owned idea. --Karek^{maps 2.0?!} 07:31, 31 May 2011 (BST)

I done been robbed! :O Seriously, though, in my personal estimation (just to explain the request) it's complete the way it is, as a policy, and I didn't see the need to keep it open for people to add, say, anti-SGP policies and various errata. But whatevs. It's there for people to enjoy the benefit of, just didn't want it watered down and obfuscated at some future date. -- ™ & © Amazing, INC. All rights reserved. Replying constitutes acceptance of our Terms of Service. 18:35, 31 May 2011 (BST)

Even if this was fulfilled I'm quite sure the [edit] sections of the subpages you have there will disappear on the main page even though the subpages aren't protected... I'd recommend adding a workaround edit button if the protection goes through. -- ϑ^anceϑ^anceℜ^evolution 06:43, 31 May 2011 (BST)

I'd have no problem with that. Wiki rustiness causes me to miss factors like that. -- ™ & © Amazing, INC. All rights reserved. Replying constitutes acceptance of our Terms of Service. 06:45, 31 May 2011 (BST)

Case is no longer active and isn't being pursued, so I've moved it to recent actions.--Yonnua Koponen ^{T G P} ^^^ 22:45, 8 June 2011 (BST)

I've gone halfway and put in semi-protection. Anyone disagree?--The General ^{T Sys U! P! F!} 09:06, 9 June 2011 (BST)

Looks good.--Yonnua Koponen ^{T G P} ^^^ 11:28, 9 June 2011 (BST)

UDWiki:Projects/UHUB Discussion

Was requested on my talk page. Added requested category. ~ _{19:46, 1 June 2011 (UTC)}

---

e Protections Archive

2005 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec 2006 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec 2007 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec 2008 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec 2009 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec 2010 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec 2011 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec 2012 Jan Feb Mar Apr May Jun Q3 Q4 2013 Q1 Q2 Q3 Q4 Years 2014 2015 2016 2017 2018 2019