Wikipedia:Village pump (proposals)/Archive 74

Welcome/how to edit template on talk pages
A discussion has been raised on the foundation-l mailing list about welcoming new users to highly trafficked pages regarding helping new users. The point brought up indirectly that I noticed is that we do not have a bot or AWB added a template assisting in talk pages and editing, welcoming IPs and new users on talk pages that offer assistance. Instead, we plaster pages with Projects and class and stub et.al templates. Would anyone care to modify the welcome template to talk pages and not just user talk pages, and can we just add the template at whim as we do other talk pages? Keegan (talk) 06:29, 7 June 2011 (UTC)


 * I hijacked hello world and adapted it a bit for this purpose. There is a generic talk page template that has existed for years as well. It's not very friendly, though. --MZMcBride (talk) 06:39, 7 June 2011 (UTC)


 * I think talk page is an excellent header for talkpages, containing a few helpful links but not being overwhelming. I don't understand why you would prefer the basic hello world template over it. You weren't thinking of adding an abomination such as Welcomeg were you? I would give my strongest possible oppose to that. Yoenit (talk) 08:36, 7 June 2011 (UTC)


 * The talk page template is dreadful at addressing the need here - that is, telling completely new users what a talk page is for. Even for those of us who know what it's for, it is yet-another-brown-box-to-ignore, and certainly doesn't stand out.
 * I note, BTW, that these proposed changes have been reverted without discussion. Charming.
 * James F. (talk) 09:09, 7 June 2011 (UTC)
 * Adding the standard welcome template is even worse, for it does not even mention talkpages. How is that supposed to help new users? I would be open to an alternative template on top of talkpages, but hello world is not it. Yoenit (talk)09:17, 7 June 2011 (UTC)
 * (addendum) Also, why are you whining about that revert? A reason is given in the edit summary and it is standard practice following the BOLD, revert, discuss cycle. Yoenit (talk) 09:26, 7 June 2011 (UTC)

Talk header (for it is he - talk page is a redirect) has the header This is the talk page for discussing improvements to the Foo article. and the first item in the list of information is This is not a forum for general discussion of the article's subject.. That seems to cover the main requirements. As to eye-catching prominence: in a while we'll be able to add CSS specific to new users, so we could (if we wanted) make it all bigger and more eyecatching just for them. In the interim, we could, if we wanted, add a |big=yes parameter to the template to make it So Annoying You Can't Miss It. PS Looking at it through experienced-user eyes is probably not the best judgement of its visibility, since we're used to ignoring those brown boxes to look for the content. Rd232 talk 09:35, 7 June 2011 (UTC)
 * I also think that adding a template of some kind to talk pages should be done to inform out users and if we did it as a standard we could implement it on meta and let it be static without having to add it manually to pages as an edit. IMO we should not be waiting till something goes wrong to tell them not to bicker. Just my opinion. --Kumioko (talk) 23:27, 7 June 2011 (UTC)
 * I agree. The work could be put on the MediaWiki code of the talk page, similar to our warnings and whatnot when you click "edit" but instead be static on the talk page itself.Keegan (talk) 04:58, 8 June 2011 (UTC)
 * There is MediaWiki:Talkpageheader which I think would do the job, but it would be displayed on every single talk page. mw:Extension:PageNotice (referenced in, for per-namespace sitenotices) would provide more control, but isn't currently installed. Rd232 talk 10:14, 9 June 2011 (UTC)

Talk header says "New to Wikipedia? Welcome! Ask questions, get answers." What more do we actually need on every single page? WhatamIdoing (talk) 01:46, 10 June 2011 (UTC)

User pages
Let me know if I'm missing something here as IM new herebut should all user pages be configured so no one can ed it it unless it is their user page? Would this work out? Heyitsme22 (talk) 22:06, 9 June 2011 (UTC)
 * Not really. Sometimes people leave bad categories on their userpage, or deleted files, redlinks, etc. In those cases someone might want to edit it for maintenance purposes. Someone could also create their userpage with vandalism/spam, and that would need to be tagged for deletion (or it could be reported somewhere, I guess). At any rate, if your userpage is being vandalized you can request that it be protected from editing for a while. Ajraddatz (Talk) 23:36, 9 June 2011 (UTC)


 * Some people also use them as sandboxes for writing articles, and they may invite others to help them, or need to move the page. It's not really "yours".  WhatamIdoing (talk) 01:58, 10 June 2011 (UTC)

Proposal at WikiProject Articles for Creation
Hello, there is currently a dicussion at WikiProject Articles for Creation which may interest you. The discussion's topic is on whether or not the Userspace draft option in the article wizard should be removed, relocated, or replaced. The discussion is located here. Thank you, Alpha Quadrant    talk    23:08, 9 June 2011 (UTC)

OTRS Noticeboard
Wikimedia commons has a Noticeboard for OTRS members to answer questions asked by other users.(Commons:Commons:OTRS/Noticeboard) The advantage of this is that a user can get a quicker response to any questions regarding a ticket. I think it would be just as useful to have the same thing on Wikipedia. Morgan Kevin J (talk) 16:13, 27 May 2011 (UTC)
 * Strongly support. I've discussed the need of such a board with other users in the past, and I'm glad to see somebody's taken the initiative to propose it. :) It would be a much simpler matter for getting feedback on OTRS tickets. --Moonriddengirl (talk) 16:28, 27 May 2011 (UTC)
 * Strong Support - from me as well. We should also make sure it gets added to Template:Noticeboard links. --Kumioko (talk) 16:51, 27 May 2011 (UTC)
 * Strong Support - This beats my current system of hopping onto the IRC, asking around in hopes that someone might have access, getting a person with OTRS access but who can't answer my question, being told to go to the OTRS channel, asking there, unsucessfully waiting for 30 minutes for the room to break its perpetual silence, and then finally PMing Keegan for the answer (Keegan only appears after I've tried all the other steps, I blame dark magic.)  S ven M anguard   Wha?  17:06, 27 May 2011 (UTC)
 * Comment Before this noticeboard goes up a decision needs to be made as to whether or not users can use that board to request OTRS access for themselves. That answer needs to be up in a divbox from the start. Personally, I am not in favor of allowing users to request OTRS access on this board, as it would clog an otherwise useful resource.  S ven M anguard   Wha?  17:17, 27 May 2011 (UTC)
 * A link can be added on the noticeboard to OTRS/volunteering, where users should request access. Morgan Kevin J (talk) 03:26, 28 May 2011 (UTC)
 * Given that OTRS is a "global" system and administered by the foundation, I don't think the enwiki community is in a position to determine where users can ask for access. Mr.Z-man 03:33, 28 May 2011 (UTC)
 * OTRS access most certainly should not be request-able here. As Z-man said, it's a global thing, and there is no need to take that to a local level. Ajraddatz (Talk) 03:50, 28 May 2011 (UTC)
 * Agreed. The volunteer OTRS admins have a system already in place, and decisions to change it should be made centrally. --Moonriddengirl (talk) 22:53, 28 May 2011 (UTC)
 * Support - a good idea, one of those that you think must already exist as it is a good idea. MilborneOne (talk) 17:21, 27 May 2011 (UTC)
 * Support. Much better organization this way. Ajraddatz (Talk) 20:52, 27 May 2011 (UTC)
 * Support, would be much more efficient than the current system, good idea. doom gaze   (talk)  22:43, 27 May 2011 (UTC)
 * Support better. Also, started it in userspace here.   EBE123  talkContribs 13:19, 28 May 2011 (UTC)
 * Question: What does OTRS think of it?  — Arthur Rubin  (talk) 22:40, 28 May 2011 (UTC)
 * Depends who you mean by that. I'm an OTRS volunteer, and I love it. :) I'm not an OTRS admin, but seeing as how there's a board on Commons already, I can't imagine why they'd have a problem with it. --Moonriddengirl (talk) 22:53, 28 May 2011 (UTC)
 * As an OTRS volunteer who handles a great many Commons and enwiki permissions tickets, my only concern is that I am commonly at Commons and watch the OTRS noticeboard there. I'd have to remember to come here and check for changes.  I can also see confusion arising, where the mirroring of files gets OTRS questions asked here for files actually at Commons.  If the OTRS volunteer who tagged such a file only participates at Commons, well, they're not going to be providing any information on it from their perspective. – Adrignola talk 14:48, 30 May 2011 (UTC)
 * I'd be perfectly fine with doing a soft redirect to your noticeboard; you guys are really on the ball over there. :D But if the board also covers other issues, that could be a problem. :/ --Moonriddengirl (talk) 00:41, 31 May 2011 (UTC)


 * OTRS noticeboard was nominated for deletion at Wikipedia:Miscellany for deletion/Wikipedia:OTRS noticeboard. Cunard (talk) 00:26, 30 May 2011 (UTC)
 * Strong Oppose That page is public, and there are good reasons why ORTS is NOT public! Just look at the deletion discussion.--Müdigkeit (talk) 19:00, 30 May 2011 (UTC)
 * Commons:Commons:OTRS/Noticeboard has evidently managed just fine for about two years in spite of that. :) I also see quite a bit of support at the deletion discussion, although there are some opposers. --Moonriddengirl (talk) 00:34, 31 May 2011 (UTC)
 * I also think this would be fundamentally different - the main arrangements for deletion were It's targeted at non-editors and handles non-public data. Looking at the Commons board, it seems like it is targeted to editors, and I don't see any non-public data posted there. Avic ennasis  @ 18:12, 27 Iyar 5771 / 31 May 2011 (UTC)


 * Support Seems like a good idea - would save some editors the hassle of bothering people in the IRC channel. :-) Avic ennasis  @ 18:12, 27 Iyar 5771 / 31 May 2011 (UTC)
 * Support – Definitely seems to be a good idea. — mc10 ( t / c ) 04:10, 2 June 2011 (UTC)
 * Support If it means things will be done more efficiently. — James (Talk • Contribs) • 10:14pm • 12:14, 2 June 2011 (UTC)
 * Support But I think we should keep the old IRC if people like to use that better --Superlightoftruth (talk) 20:40, 6 June 2011 (UTC)
 * Support. As long as there are enough people looking after it, I don't see why it would be bad. Reh  man  08:40, 9 June 2011 (UTC)
 * Note. The deletion discussion made clear that the main issue was the original draft wording, which was extremely wide and unrestricted compared to the actual uses and safeguards proponents had largely envisaged. I've reworded the board header to allow for these and it's now probably safe(ish). Eyeballs requested on the wording to ensure as far as possible, the wording has had careful scrutiny and that the most likely routes for serious issues have been accounted for in the directions. FT2 (Talk 09:11, 10 June 2011 (UTC)

bAck to top
a bac to top button at the beginning and end of every section would be nice expecially for navigating long articles. thoughts? Heyitsme22 (talk) 15:18, 9 June 2011 (UTC)


 * The "Home" button works perfectly fine in this page. Cambalachero (talk) 15:25, 9 June 2011 (UTC)


 * I brought up something similar a while ago (see Wikipedia talk:Help desk/Archive 9) and I would support such an addition. Toshio Yamaguchi (talk) 15:31, 9 June 2011 (UTC)


 * Easy to implement as a script so users who choose to have this feature can install it for themselves. Gary King  ( talk  ·  scripts )  19:53, 9 June 2011 (UTC)

First of all, I am wondering whether the initiator of this speaks English as a first language, as I did notice there were several mistakes in the English -  it should have been headed "Back to Top" (or maybe the person was just tired). Enough of that - I just wanted to point out that, using most, if not all, web browsers, you can go to two arrow keys at the head of the page, in the top left hand corner. Clicking on the arrow that points back will, I think, achieve what you want to do. ACEOREVIVED (talk) 20:21, 9 June 2011 (UTC)


 * It will if you've clicked in the table of contents to get where you are, but if you've scrolled down you'll have to scroll back up again. Peter jackson (talk) 10:13, 10 June 2011 (UTC)


 * Oppose There is a "Home" button on your keyboard for a reason. Yoenit (talk) 11:02, 10 June 2011 (UTC)
 * Comment Using the "Home" and "End" buttons on the keyboard works fine. However, then we should remove the "Skip to bottom" button for consistencies sake. Having one button but not the other one appears to be an incomplete implementation, that should either be completed or removed alltogether. Toshio Yamaguchi (talk) 11:13, 10 June 2011 (UTC)
 * There is no "skip to bottom" button. Some pages (like this one) implement it with a   link.  This does not really have anything to do with the MediaWiki interface. —Tim Pierce (talk) 11:27, 10 June 2011 (UTC)
 * And the reason it's on village pump pages is because people typically want to see what the latest discussions are. Gary King  ( talk  ·  scripts )  17:27, 10 June 2011 (UTC)

Recommend we switch the default for the EMAIL option of talk page messages
Although I like the notification I have seen a lot of discussions about it not being wanted by some. It also seems to me that we might not need it for all the blocked accounts and such so I would like to offer a recommendation. I recommend we turn it off by default and let the users and editors choose wether they want it.

I decided to submit this because I heard this being discussed in public away from Wikipedia by someone who confessed to being blocked but could not turn the EMAIL notification off so they were getting "useless" messages every other day. --Kumioko (talk) 17:45, 9 June 2011 (UTC)
 * I agree these should have defaulted to off, but that ship has already sailed. Now, why is this person unable to turn the email notification off? It's at Special:Preferences. – xeno talk 17:47, 9 June 2011 (UTC)
 * Well the ship can always get new directions and change course but true on the second point. Would someone who has been banned or blocked (say for Vandalism or Sockpuppetry for example) be able to do that? --Kumioko (talk) 17:50, 9 June 2011 (UTC)
 * A blocked user can still change their account preferences. If they "scrambled" their password, they can recover their password if they are getting notification emails. --Tothwolf (talk) 17:55, 9 June 2011 (UTC)
 * Should be possibly even for blocked users, yes. And banned has no technical implications. - Jarry1250 [Weasel? Discuss.] 18:21, 9 June 2011 (UTC)
 * I agree with Xeno... I found the messages a little annoying and would have preferred an "opt-in" method, but now that it's already implemented and easy enough to opt-out of, it might be even more annoying to change it at this point. Those who wanted to opt-out (like me) have already changed our prefs, now we'd need the people who do like the notifications to change their prefs too. 28bytes (talk) 18:04, 9 June 2011 (UTC)
 * I agree with both the original position of opt-out, and the thought already outlined that the horse has already bolted. No point doing anything now. - Jarry1250 [Weasel? Discuss.] 18:21, 9 June 2011 (UTC)
 * Ok fair enough I just thought I would throw it out there. It makes sense what you all are saying. --Kumioko (talk) 19:07, 9 June 2011 (UTC)

On a related point, some wikis have such email notification for watchlists, but WP doesn't seem to have that option. Peter jackson (talk) 10:15, 10 June 2011 (UTC)
 * Probably because that would be sending thousands upon thousands of mails a day :) I'd be getting about 500 emails a day at the moment :) --Errant (chat!) 13:10, 10 June 2011 (UTC)

Signatures
I added some text to WP:SIGNATURE about discouraging confusing use of nicknames, only to discover that this is the default behaviour of the signature field in the preferences. This is controlled by MediaWiki:Signature, which does exactly the Nickname (if nickname is provided) which I thought was confusing and is/should be discouraged. This could be changed in MediaWiki:Signature, eg to become name/Nickname, and perhaps MediaWiki:Tog-fancysig tweaked to match. Rd232 talk 16:20, 11 June 2011 (UTC)
 * I...almost understand what you're saying here? Did you type too fast and miss about three sentences perhaps? Not being a bitch, you're usually one of the more clear Wikipedians around. → ROUX   ₪  16:28, 11 June 2011 (UTC)
 * I think this is about the "If unchecked, the contents of the box above will be treated as your nickname and link automatically to your user page" option, which would make it possible to simply enter another name to use with a high level of simplicity. Grandiose (me, talk, contribs) 16:30, 11 June 2011 (UTC)
 * I'm also slightly confused, but maybe because I've always had that "Treat the above as wiki markup" box checked. Frankly, we don't need that nickname feature—it's confusing (especially to a new user) and you can use wikicode to make a sig with a nickname, anyway. Although I definitely agree with the addition to WP:SIGNATURE about nicknames being confusing if there's no mention of the actual username in the sig. / ƒETCH COMMS  /  18:39, 11 June 2011 (UTC)

OK, I guess I was pretty hasty, let's try and clarify: Better? Rd232 talk 19:24, 11 June 2011 (UTC)
 * 1) I made an addition to WP:SIGNATURE here to clarify that poor use of nicknames in signatures (without including the actual username somehow) can easily be confusing. I think this is widely understood, but I have seen it done occasionally.
 * 2) However it turns out that this confusing practice is strongly encouraged by the user preferences setup. At the moment, if you enter a nickname without ticking the "raw signature" box, the result is that confusing practice.
 * 3) This can be fixed by editing MediaWiki:Signature. The current Nickname would become Example/Nickname in the event the user enters a nickname in preferences without checking the "raw signature" box.
 * Hence we get periodic moments of hilarity like this (from my alternate account) and this (from an admin, no less). It took me a few tries to figure it out with this account, so if you look at my contribs around mid-July you can see the same thing happened a few times before I checked the box. Ticking the box as the default would probably make things easier. The Blade of the Northern Lights  ( 話して下さい ) 19:33, 11 June 2011 (UTC)

Essay elevation to Guideline proposal
You are invited to join the discussion at Wikipedia talk:WikiProject Military history/Notability guide. RightCowLeftCoast (talk) 21:33, 12 June 2011 (UTC) (Using )

Conflict of Interest Essay idea
You are invited to join the discussion at Wikipedia talk:Conflict of interest. RightCowLeftCoast (talk) 21:53, 12 June 2011 (UTC) (Using )

Suspend sysop rights after 1 Year of inactivity

 * Lengthy discussion moved to Village pump (proposals)/suspend sysop rights of inactive admins.

Brainstorm over increasing privileged account security
Seeing as a lot of this is revolving around a concern for admin account security, I'd like to briefly mention a few different ways/possibilities that could possibly be done while maintaining anonymity, privacy, and the like&mdash;at least within reason. Keep in mind that I'm not talking about bulletproof security, but simply a second factor of authentication that could be used to practically verify identity or secure logins as general (and possibly optional) practice. Using these methods, you wouldn't necessarily have to authenticate with them regularly (which might be a total pain), but it might be an idea to do something similar to what the toolserver does when it comes to account renewal: after a period of time (say in this case 1 year or after a stretch of inactivity), ask people with extended permissions to visit a site and "renew" their permissions using one of several methods of advanced identification that would be on file. That way, if someone loses their private key, they can answer their security questions instead; if they forget their account security questions, they could use their token or their private key instead; etc....
 * Public key infrastructure &mdash; It might be a good idea to ask users with enhanced permission sets to use a free, basic PKI package (e.g., GNUPG) to generate and publish a strong (>=4096 bit) public key set to expire within a practical period of time so as to help negate long-term key attacks. Only problem is that keys can be lost in hard drive crashes or just by accident. Within reason, though, if someone is active and then loses their private key, one could probably judge by their behavior whether or not they're who they're claiming to be.
 * Token-based auth &mdash; Several technologies exist that would enable this. SecurID and related technologies cost money, but might be available at a discount or something for a non-profit. There are also software-based versions of hardware tokens, and there are free implementations of otherwise proprietary implementations. eTokens are fairly cheap, too, but do still require buying something.
 * Account security questions &mdash; Everyone's had to deal with these, but we could make something reasonable that would allow you to create your own questions (very important) and supply your own answers.

All of these would also help get around cases where someone forgets their password, someone maliciously changes it on them, or whatever other scenarios might arise.

Anyway, t'was just brainstormin'.

Cheers =) -- slakr \ talk / 22:22, 9 June 2011 (UTC)


 * That's really more Village pump (proposals)/Account security territory. Perhaps you could move your thoughts there, as this thread is already quite long enough. Rd232 talk 00:05, 10 June 2011 (UTC)
 * Tokens work well, untill this happens (sorry, it was too tempting). -- Chris 13:51, 13 June 2011 (UTC)

Offensive usernames of blocked sockpupets
Would it be a good idea to hide usernames which attack individuals or groups, or are generally disruptive or offensive ? In particular I wonder whether it might be appropriate to hide the name of this this sockpuppet, simply because if such content was in mainspace or userspace it would be deleted per our policy on attack pages. Would there be technical issues with giving such blocked user's pages generic titles such as "Blocked user" or "Blocked sockpuppet of user x" ? Although I can't find a Wikipedia template which does it, there are some on other Wikia projects (see, for instance ). I am not suggesting that the usernames be changed, simply that they should be replaced by a template. It seems hypocritical that we would delete such content if it was placed anywhere else, yet we allow it to stay clearly visible due to it being part of the user's name. Anthem 19:57, 6 June 2011 (UTC)
 * If the title is a BLP violation or attacks someone I would agree and support this. I would say though that if it just contains a swear word or something that might just offend a few folks or is a general irritation then no. --Kumioko (talk) 20:25, 6 June 2011 (UTC)
 * I think if a username just contains a swearword, there's no obvious reason for hiding the name. There should be a case for hiding the username when there is a BLP violation/attack usernames (such as the one linked to), and what might be considered "hate speech" (ie. extremely misogynistic or racist usernames). --Anthem 20:53, 6 June 2011 (UTC)
 * Usernames can be revision deleted from page histories and even user creation logs etc, if necessary. Requests can be made via CAT:REVDEL. Rd232 talk 21:29, 6 June 2011 (UTC)
 * The issue is the presence of the offending username on the user's userpage. --Anthem 21:30, 6 June 2011 (UTC)
 * Well in extreme circumstances the user might possibly be renamed (WP:CHU). Note that such accounts will often be tagged with a template which NOINDEXes them (eg sockpuppet). Rd232 talk 21:52, 6 June 2011 (UTC)
 * Hmm, I was thinking it would be simpler to have a template an admin (as opposed to a bureaucrat) could apply. --Anthem 03:20, 7 June 2011 (UTC)
 * There could be a template requesting a rename (modelled on the WP:Edit request system), for bureaucrats to act on, but I'm not sure it's worth it. Rd232 talk 10:22, 9 June 2011 (UTC)
 * FYI Usernames can now be oversighted locally by any oversighter (in application of Oversight §4 "blatant attack usernames") or globally at all projects by any stewards. Regards, --m:dferg 21:23, 10 June 2011 (UTC)


 * Note Anthem of joy has been indef blocked as a sockpuppet of Claritas . --Tothwolf (talk) 04:19, 15 June 2011 (UTC)

Force IPs to use edit summaries
Whenever I look at a page's revision history, most IPs consistently fail to use edit summaries, this would help RCPs to determine how appropriate an edit is. For example, if the edit summary contains "BLARGHFSUDFSHKGS" that's indicative of the edit, statistically this is the case most of the time, other times the editor using such an edit summary is one who can't be arsed to insert a proper edit summary. Thoughts? — James (Talk • Contribs) • 9:38pm • 11:38, 12 June 2011 (UTC)
 * This is Perennial proposal territory, though I suppose a short-term test for IPs might be worth a try. I wonder though if the new Default Edit Summaries gadget couldn't be made available by default (via Commons.js) so that IPs can use it too. Rd232 talk 11:45, 12 June 2011 (UTC)
 * It would be great if a registered user could tick off IP edits as constructive in the history list so other users do not waste the time double-checking if they do not want to. --Squidonius (talk) 21:39, 12 June 2011 (UTC)
 * I thought we had a discussion recently over edit summaries, did that amount to something? I know some people supported a dropdown box of common edit summaries, but will that be implemented? '''/[[User:Fetchcomms|ƒETCH ]] COMMS / ''' 00:58, 13 June 2011 (UTC)
 * I think it  would be a good idea. I've noticed a change in  the edit summaries -  there's now an automatic dropdown but  I  can't  figure out  whether they  are standard suggestions or somehow stored .js versions of my  own es. --Kudpung กุดผึ้ง (talk) 04:48, 13 June 2011 (UTC)


 * Well I certainly think ips should be strongly encouraged to put in summaries.
 * I like the other idea above too. I guess it would take a lot more work but the general idea of people signing that they like a particular edit sounds like it could lead to something useful. Not just cutting down checking but other things. Like the perennial problem of which edit to lock when there is dispute or finding a version suitable for publication on a schools CD. Dmcq (talk) 06:32, 13 June 2011 (UTC)
 * This idea is in Perennial proposal territory as stated above, and I could have sworn I participated in a discussion on this before. I believe requiring an edit summary may discourage anonymous users from trying out editing, and I'm not sure how helpful a edit summary would be anyways if they are forced just to type something in.AerobicFox (talk) 06:55, 13 June 2011 (UTC)

We did have a recent discussion on this, and it can be found here:

I don't expect to get much support for this one. But I want to propose it anyway. I often see new accounts make big bold edits without leaving edit summaries, and I assume good faith of course, but I still don't know why they boldly removed that certain paragraph or sentence, or changed that date or statistic, or whatever. I don't know how many times I've had to leave an extended message on new users' talk pages explaining why they need to use edit summaries. Better to get them in the habit early, then once they get autoconfirmed they can have the option to turn it off. -- &oelig; &trade; 09:29, 11 March 2011 (UTC)
 * I like it, can we set a trial to test this out? I think use of edit summaries would reduce the number of good faith edits reverted as vandalism. Yoenit (talk) 09:40, 11 March 2011 (UTC)
 * Agreed. I've often reverted silent deletions due to lack of an edit summary (they're indistinguishable from vandalism or POV-zealotry). Occasionally I've inferred "lack of references" as the reason and not reverted, but requiring an edit summary would significantly help in distinguishing nonconstructive deletions from good-faith ones. --Cyber cobra (talk) 09:59, 11 March 2011 (UTC)
 * WP:PEREN. (But I'm not sure I agree with the “[r]easons for previous rejection”: after all even most e-mail clients warn you if you're trying to sent a message with an empty subject line.) --A. di M.(talk) 11:35, 11 March 2011 (UTC)
 * Do we have evidence that this is even a true perennial proposal? It seems to have been added back in 2006, but has it ever been the subject of discussions? Yoenit (talk) 12:07, 11 March 2011 (UTC)
 * What about turning on the prompt gadget by default?  Kayau  Voting  IS   evil 12:44, 11 March 2011 (UTC)
 * Right. The gadget is already there, but only registered users can turn it on in their preferences setting. If turned on, an attempted save of a summary-less edit does initially not succeed but instead displays a conspicuous warning banner: "Reminder: You have not provided an edit summary. If you click Save again, your edit will be saved without one." (See it atMediaWiki:Missingsummary.) Unregistered users and most new users don't get to see this, as it is turned off by default. Although enabling this by default is not exactly forcing unconfirmed users to use edit summaries, it most definitely will help encourage them to do so. --Lambiam 14:02, 11 March 2011 (UTC)


 * Could we change the text to something like "Reminder: You have not provided an edit summary. Edit summaries help other users understand the intention of your edits. Please enter one before click Save again, or your edit will be saved without one."? I am afraid the default text is not really helpfull to a newbie and is more seen as annoying. Yoenit (talk) 14:27, 11 March 2011 (UTC)
 * I've put this proposal up at MediaWiki messages. Please discuss it there. --Lambiam 23:22, 11 March 2011 (UTC)


 * I'm definitely all for trying to get people to put in edit summaries and I haven't the foggiest why ips aren't prompted to do so. It should be like that by default. Dmcq (talk) 16:13, 11 March 2011 (UTC)

I really dislike this proposal. What are the new users supposed to do say they are for instance, just trying to get a piece of wiki code to work, or making minor edits. Forcing them to write a summary of everything they do seems like a hassle for new users.AerobicFox (talk) 17:27, 11 March 2011 (UTC)

I would weakly support a dismissible reminder for anons and new users (weakly because of AerobicFox's concerns), but I would oppose forcing users to provide one. Mr.Z-man 17:38, 11 March 2011 (UTC)

I've had other users ask me how to leave an edit summary before, so I do suspect that many just can't see the bar right above the "save page" button. How about we just move the edit summary above the edit box, make it some obnoxious color, and render "Edit summary (Briefly describe the changes you have made) " as " Edit summary (Briefly describe the changes you have made) " and/or (along Mr. Z-man's suggestion) if they try to save a page without putting an edit summary, a prompt comes up saying "are you sure you don't want other editors to understand what you're doing?"Ian.thomson (talk) 17:50, 11 March 2011 (UTC)
 * If you use an obnoxious colour then the message could use the same colour so they can easily spot where the place to insert a summary.Dmcq (talk) 13:13, 15 March 2011 (UTC)

I would oppose compulsary edit summaries. The last thing we need is another hoop for new users to jump through before they can edit. Support a reminder, which would leave it firmly in their hands while still encouraging them to use the tool and educating them about its use. Interesting to note that of the eleven of us involved in this discussion, only four used edit summaries on the first edit, and none on all of the first ten. Would it be right for us to force new users to do something that we failed to?Alzarian16 (talk) 13:27, 15 March 2011 (UTC)

Support the default reminder in article space for non auto-confirmed users. It's no great imposition and should reduce misunderstandings and possible summary reverts due to misjudging new editor's intentions, particularly if edit is not well formulated. It should also serve to highlight intentional disruption. RashersTierney (talk) 13:45, 15 March 2011 (UTC)

Oppose. As Alzarian helpfully pointed out this is not something we should hassle newbies about. I would be more tolerant of something along the lines of "congratulations on your 100th edit, may we now introduce you to the idea of the edit summary", but as for newbies I'm much more concerned about getting them to tell us their source. DE wiki has a referencing prompt and I would like that to be trialled here.  Ϣere Spiel  Chequers  14:00, 15 March 2011 (UTC)

The last thing we need are more barriers, especially those requiring a degree of technical aptitude, to new editors contributing. Would not object to a dismissible prompt after 20 or so edits though along the lines of the comments by MuZemike and WSC above. Skomorokh 18:33, 15 March 2011 (UTC)

Much as I appreciate that this proposal was made with good intentions, I for one would quite strongly oppose it. Many newcomers to Wikipedia probably are just getting the hang of editing it, and are not even at the stage of thinking about edit summaries. My guess is that, every day, there are probably numerous edits which lack an edit summary which are perfectly good edits. This proposal does have shades of the perennial proposal (which seems unlikely to work - ever) of only allowing logged in registered users to edit Wikipedia. People who are new to Wikipedia are probably learning how to edit it before doing edit summaries - after all, one must crawl before one can walk. ACEOREVIVED (talk) 00:44, 23 March 2011 (UTC)
 * Well it seems to me the point is to help OTHERS recognize those good faith edits. The question of if newbies will be turned off by the summeries more than they are currently by their good faith edits being reverted (I've even seen plenty of seemingly good faith edits directly called vandalism...at least with an edit summery it's easy to tell if the reverter is in the wrong) ♫ Melodia Chaconne ♫ (talk) 02:15, 23 March 2011 (UTC)

Oppose mandatory edit summaries, support default reminders. ACEOREVIVED said it best - "one must crawl before one can walk". Let's not give newbies more hoops to jump through by forcing them to write an edit summary before their edits can go through, but rather let's encourage them to provide summaries with friendly reminders and a brief explanation of the benefits of providing summaries. Aside from discouraging participation from new users, another potential drawback to requiring edit summaries is that some - who don't care to be bothered with providing a summary but want to see their edit(s) materialize - may be tempted to write nonsensical gibberish or some kind of wisecrack in the summary space just to satisfy the "write something" requirement. And, of course, such summaries would unhelpful and counterproductive, as they would likely seen by patrollers as a sign of vandalism when this may not be the case at all. No, better to focus on ways to more effectively encourage edit summaries. The ideas proposed above by Yoenit and Ian.thomson are very good ones that should be given strong consideration.--JayJasper (talk) 03:51, 23 March 2011 (UTC)

JayJasper, thank you for your comment. Your comment about another difficulty here being that if we force people to write an edit summary, they might start writing nonsense is well taken - I had not thought about that, but it is an excellent point!ACEOREVIVED (talk) 19:32, 23 March 2011 (UTC)

I think that a prompt for, but not enforced edit summary, is a brilliant idea. I have a terrible history of not giving edit summaries, and have only recently discovered the pref where I could ask for a prompt! Since when, I've begun to get into the habit without having to be prompted. Pesky ( talk ) 05:07, 29 March 2011 (UTC)

This is actually at Wikipedia Village Pump Proposals Archive 70 at the time of typing. I think you can see why this should be considered a perennial proposal. As you can see, the discussion was in March at the time of typing. ACEOREVIVED (talk) 21:20, 14 June 2011 (UTC)
 * Why not wikilink to the archived proposal section instead of pasting in 12K of text? -- John of Reading (talk) 21:36, 14 June 2011 (UTC)

I oppose this idea, because if we want to identify vandalism, are we going to put a dropdown selection for vandalism to make changes patrolling easier? I don't think so, and the way it stands at the moment a blank edit summary is a good clue to check out the work. Though the idea to encourage more registered users to use or force use the edit summary has merit. It is already difficult enough for new people to edit here without making them think of an explanation of what they are doing. Graeme Bartlett (talk) 21:44, 14 June 2011 (UTC)

Random articles
Just for the hell of it, today I clicked on "random article" to see what would come up. I was quite disappointed to get not an article, but a disambiguation page. Is there some way of limiting random articles to just that - articles - by somehow disabling it from fetching any page that has a dab template on it? Grutness...wha?  11:44, 14 June 2011 (UTC)
 * This is possible using a script; see Enhanced Random Article. -- John of Reading (talk) 12:08, 14 June 2011 (UTC)
 * Ah - thanks! Grutness...wha?  02:00, 15 June 2011 (UTC)

Tool for WebCite archiving
I request that a semi-automated tool be created that helps editors to quickly archive references with WebCite. Going through an article with lots of citations and archiving them all case by case per hand is really annoying and wastes time that could otherwise be spent on improving article content. This tool ideally should make it possible to archive all references at once, with only one click. Again, going through an article with hundreds of references and archiving them all on a case-by-case basis is extremely ineffective and time-consuming. And linkrot is a serious enough problem that justifies the creation of such a tool. And while WebCite might not be ideal to archive all kinds of content, it would still be better than having no such tool at all. Toshio Yamaguchi (talk) 11:40, 1 June 2011 (UTC)
 * Please see Gadget/proposals Morgan Kevin J (talk) 21:01, 1 June 2011 (UTC)
 * One of the Wikimedia Foundation's Google Summer of Code projects is about this, see, and also the links there. Regards, HaeB (talk) 02:01, 3 June 2011 (UTC)
 * Hey I'm the developer for the above GSOC project. I just wanted to say hi and get a feel for what kind of features the community would like to have for an external link archival extension in mediawiki. I notice from the currently stalled RFC on whether to implement wikiwix there appears to be significant disagreement over how external links should be modified in articles. The path I am thinking of going would modify links and add a link to take you to the cache for the page for every external link. I was wondering if the community would like the ability to limit this to say a specific category out of the box as consensus for implementation seems to be difficult to get. --Kevin Brown (talk) 21:38, 6 June 2011 (UTC)
 * What exactly do you mean by "Specific category"? Toshio Yamaguchi (talk) 00:20, 9 June 2011 (UTC)
 * Like where the feature is only enabled on a certain category that could be configured. For instance something like Category:Pages that use automated archival. --Kevin Brown (talk) 00:29, 9 June 2011 (UTC)
 * That sounds good to me, if there is consensus to do this. What about drafting an RfC? However I think we should try to reach consensus here first. So maybe you should outline here, what exactly you have in mind, probably as a subsesction of this section? Toshio Yamaguchi (talk) 00:45, 9 June 2011 (UTC)
 * What I was thinking of doing was basically this:
 * On page save all the links from the article are retrieved from the parser
 * if have already been archived nothing is done


 * if they have not yet been archived they are added to a queue for a web bot to come by and archive them if they are not blacklisted
 * Sometime later a web bot comes by and attempts to retrieve the web page
 * if the archive is successful it is saved and displayed on request
 * if the web site is down the page is readded to the queue to be checked later, or if the page is still down after a certain number of attempts the the link is assumed to be dead and we stop trying
 * if the web site is up but the link can't be archived due to robots.txt, nocache, or noarchive tags automatically blacklist the site for a certain amount of time
 * if the web site is up but the page comes back as a 404 or a redirect assume it as a failed attempt, note it, and blacklist that link
 * Add a hook to the parser to display a link to access the cached version of the page for every external link on the wiki, or possibly configurable options, this will be done on parse so the link may link to stuff that has not yet been archived or where the archive was unsuccessful
 * That's basically it in a nutshell. The actual framework of getting done is really the easy part. The hard part is sanitizing everything to make sure this can be done without any security holes. Due to this it is unlikely that I will be storing java script or flash objects as they are difficult to sanitize. Images are mostly secure but you can have some security vulnerabilities there as well. As far as changing stuff and linking to stuff that may not exist I realize that some people in the community had a problem with this but this is far less intensive than trying to do queries to figure out what has/hasn't been archived yet. Not to mention that since pages are cached for a significant amount of time (as far as I'm aware it's a week here) it could be a long time before we check back to see if the archive actually exists. It's because of this that I think just linking to stuff that may not exist is the best option. --Kevin Brown (talk) 00:39, 10 June 2011 (UTC)
 * That sounds good. I think perhaps we should simply wait if some other people comment on this and if there is support for this. Nearly everything is better than the current situation: having no tool for archiving citations, so I generally support anything that brings us nearer to a working solution. Toshio Yamaguchi (talk) 01:00, 10 June 2011 (UTC)
 * This is something I will be working on regardless of if there is support to implement it on the English Wikipedia. I would however like to see this deployed here, so I would like to seek the communities input to see if there is are any features (within reason) they want out of the box in the software. I can't guarantee I will be able to fulfill every feature request, but if there is something that people really want I will try to get it implemented. Obviously getting working secure archival is my number one priority and everything else takes a back seat to that. --Kevin Brown (talk) 01:49, 10 June 2011 (UTC)
 * You might also want to take a look at a recent bot request I filed at WP:BOTREQ, where I listed some of the functionality I would expect from a WebCite bot. Toshio Yamaguchi (talk) 10:00, 10 June 2011 (UTC)
 * At the current time this will probably be for all external links and not just what is in references. I would like to add something later to limit this to references but there are three problems with it:
 * it's not as easy to get as it is all external links, for instance the external links table contains no data to tell me if the link is a reference or not
 * The Cite extension is not part of media wiki core and thus requiring it would create an unnecessary dependency.
 * Some editors use parenthetical references in MLA or APA style by hand and not tags, thus those links would not get archived if you were only archiving stuff in ref tags.
 * As far as submitting stuff automatically to web cite that really wouldn't be that hard to do, but given webcite's current infrastructure I'm not sure that's practical, due to the fact that they require an email address and send emails to it for every archival request (this means tens of thousands of mostly useless emails). --Kevin Brown (talk) 11:58, 10 June 2011 (UTC)
 * Toward the end of last year I archived a big chunk of links (parsed out of a db dump) to WebCite, I never got beyond doing that, but the way I handled the emails was just to feed it it a googlemail address. And set up a filter to simply delete the "it worked" emails. --Errant (chat!) 13:05, 10 June 2011 (UTC)
 * Something like that could work but sounds like a "ur doin it wrong" kind of way to do things. It works, yes, but it's horribly inefficient, and on a large scale it makes no sense and may potentially lead to scalability problems. Really web cite needs to do stuff on their end to use API keys rather than an email address. --Kevin Brown (talk) 02:35, 11 June 2011 (UTC)
 * Please note that in some countries long time archival will make it necessary to get a permission from the sources in question if this shall be legal in those countries. There are (probably?) possible to make some kind of fall-back strategies that make this legal if the archived pages isn't available for general use somehow, that is a search engine will not index the page and you can't just construct a get-request to access the page. If the request emerge from the user, then I think the user will be responsible. If the request emerge from the software after an edit the I think WMF is responsible. In some jurisdictions the first one is the troublesome, in other the last one. Jeblad (talk) 12:30, 10 June 2011 (UTC)
 * As far as I'm aware the only jursidiction we have to worry about is the United States, since that is where the servers are hosted. That being said I am in the process of seeking a formal opinion from the Foundation's legal counsel, the copyright problems shouldn't be too bad as long as DMCA takedown requests are obeyed due to the safe harbor provision in the DMCA. --Kevin Brown (talk) 19:59, 10 June 2011 (UTC)
 * Its the uploader which publish and will be at risk, and if wmf act on behalf on some other party then they are at risk. Its similar to PirateBay and linking to copyrighted material on that site. In some jurisdictions that would be legal, in other its not. Jeblad (talk) 18:00, 14 June 2011 (UTC)
 * Given that Google and the Internet Archive are able to do caching I do think it's possible. However I'm not totally sure of the specifics of the legal stuff. You may be right, but I can tell you that the Foundation's lawyer is researching it and all legal issues will be looked at before full deployment. --Kevin Brown (talk) 22:34, 15 June 2011 (UTC)

I'd like to voice my support for moving this idea forward as dead links in citations are a major issue for Wikipedia. Any progress in this area would be greatly welcome. I should also mention that Gunther Eysenbach of WebCitation.org is wanting to work with Wikipedia to help get citations archived. He can whitelist Wikipedians so they can perform high-speed archiving. He may be willing to modify the email requirement for certain operations associated with Wikipedia. I'll ask for his input. - Hydroxonium (T•C• V ) 00:38, 12 June 2011 (UTC)
 * See my last information : We started yesterday caching the content of the English Wikipedia external links, so that, while waiting for the decision to be taken, all information sourcing work could be backed up.
 * Therefore, since yesterday, we're archiving all new links introduced in Wikipedia. For those introduced before yesterday, we'll try to archive them as well, and for those that return an error 404, we'll try to get them from webarchive.org. Cheers, Pmartin (talk) 01:43, 15 June 2011 (UTC)

Jumping To Histories
We should be able to type into the search box and jump to the history's page.

For example, we can type wp talk:table if we wanted to to go the table's talk page, but we can't do this for the talk page's history or the "article"'s history, so I am proposing this to be added.Curb Chain (talk) 07:05, 13 June 2011 (UTC)
 * Oppose. Readers should care about history pages, but they don't. Adding what will be UI clutter for 99% of our millions of visitors to save a click for the other 1% is unlikely to be worth it (and that's assuming this is realistically feasible from a technical POV.) Might be more useful if restricted to logged-in users only? Perhaps a gadget/user script would be a good idea. - Jarry1250 [Weasel? Discuss.] 11:26, 13 June 2011 (UTC)
 * Comment - the major piece that is missing in your proposal is "Why". You say we should be able to do it, but why should we be able to do it?  I do not see any benefit to be able to go directly to the history of a page from the search box.  GB fan (talk) 11:38, 13 June 2011 (UTC)


 * Strong support - This is a great idea for sourcing, it would make linking to an article's history intuitive and make it easier for sites reusing our content to comply with the license. The only simple way I can think of to do this is with a new namespace, and the problem there is that we'd end up with "Template talk history:", which is a mouth keyboard-full. We could make a pseudo-namespace only for articles, but that would mean that it wouldn't show up in the URL so it might be confusing, and its usefulness would be minimized. So, while I think this is an awesome idea, I can't think of a realistic way to implement it. If someone thinks of a way, great. ▫  Johnny Mr Nin ja  22:17, 14 June 2011 (UTC)
 * Comment: if technically possible, seems most sense as a script, or potentially a gadget. Hard to see the use of rolling it out to readers in the main, perhaps after use as a script or gadget this would be easier to assess. Grandiose (me, talk, contribs) 20:46, 15 June 2011 (UTC)

Request to re-activate WikiProject General Audience
I noticed that Make technical articles understandable has been revised thoroughly (I was very impressed!) Many articles on mathematics are difficult for even well-educated readers to understand. There are a number of reasons why one might want to provide more background information in the leads of such articles, as well as add analogies (such as the [ airplane analogy] in &#8220;limit of a function&#8221;):


 * A knowledge of mathematics is essential for one to understand science.
 * Many scientific topics are relevant to public policy debates, and full participation of the general public in public policy debates is desirable.
 * When members of the general public &#8220;google&#8221; something, Wikipedia is often the first &#8220;hit.&#8221;
 * The benefits of full public participation in public policy debates may increase as the knowledge level of the general public increases.
 * Many people feel aversion or fear towards mathematics, and the difficulty level of Wikipedia articles tends to reinforce this.
 * A good level of scientific knowledge is useful in solving many real-world problems.
 * Wikipedia seeks to be a high-quality general encyclopædia.

The purpose of relisting this proposal is not, however, to debate policy, but rather, to request users who are knowledgeable in science and math to volunteer to impart their knowledge to those of us who are less knowledgeable about their subjects of expertise (here are some specific examples of articles to look at).

As stated in the guideline, &#8220;the sun is of interest to more than just astronomers and diseases to more than just physicians.&#8221; I realize, of course, that many subjects by their very nature require a certain pre-existing level of knowledge, and I certainly do not think that existing content should be &#8220;dumbed-down,&#8221; but such principles as &#8220;Write one level down&#8221; are good rules of thumb.

69.251.180.224 (talk) 13:13, 13 June 2011 (UTC) 

Relisted from archives[11][31][37][28]; please add new comments below this notice. Thanks, 69.251.180.224 (talk) 13:13, 13 June 2011 (UTC)
 * Support, but we'd need people who can actually understand the articles... which at times can be difficult. Category:Wikipedia articles that are too technical has a backlog from 2007, which is not a good sign. Crisco 1492 (talk) 02:21, 14 June 2011 (UTC)
 * Comment. I think the idea of making Wikipedia articles more approachable to a general audience is widely agreed to be a good idea, and requires no justification, but in order to do it we need a more systematic way of going about it. A Wikiproject like this should list articles to target and endeavour to recruit people in each area. Dcoetzee 20:25, 14 June 2011 (UTC)


 * See WP:REVIVE. You don't need permission to revive a dormant WikiProject.  WhatamIdoing (talk) 16:41, 15 June 2011 (UTC)

Moving pages and categories
I think it would be useful to have page moves automatically add the article page redirects to Category:Redirects from moves; the category is quite underpopulated since it has to be added manually at the moment. Would the software support that? Would the community? Crisco 1492 (talk) 09:36, 10 June 2011 (UTC)
 * Proposal change That the software automatically add Template:R from move when moving pages, except if the redirect is not created when moving. Crisco 1492 (talk) 23:14, 12 June 2011 (UTC)
 * The software wouldn't, though it could be done using some JS or an extension. I personally don't see much of a need, since all broken/double redirects appear on maintenance pages anyways. Besides, do you really want a category with thousands upon thousands of items in it? Ajraddatz (Talk) 13:56, 10 June 2011 (UTC)
 * The software could pretty easily do it as part of creating a redirect when moving a page. That, I think, is what Crisco was getting at, and it would be the most efficient method. Rd232 talk 14:46, 10 June 2011 (UTC)
 * Yes, it was. Thank you. Crisco 1492 (talk) 16:04, 10 June 2011 (UTC)
 * What is the point of the category? Or of the R from move template, which merely puts a page in that category, along with a brief message? The benefit of this escapes me. Rd232 talk 14:44, 10 June 2011 (UTC)4
 * I was going to say the same: I'd have no problem with a bot doing it, I just have no idea why one would want to. Grandiose (me, talk, contribs) 14:45, 10 June 2011 (UTC)
 * To quote:
 * "'This is a tracking category. It builds and maintains a list of pages primarily for the sake of the list itself. Pages are added to tracking categories through templates.'"
 * and
 * "Administration categories, intended for use by editors or by automated tools, based on features of the current state of articles, or used to categorize non-article pages."
 * My interpretation is that it is just meant to exist and grow bigger, to index the pages and perhaps serve as an list of pages that have been moved. However, it may be also be useful for people who work at Redirects for discussion and are looking for useless redirects. Crisco 1492 (talk) 16:13, 10 June 2011 (UTC)
 * Yes, but, tracking categories should actually be useful as well. What purpose would a tracking category for pages that have been moved serve? Page moves and redirect pages are tracked by the software regardless, so how is a category not redundant? — V = IR (Talk&thinsp;&bull;&thinsp;Contribs) 16:18, 10 June 2011 (UTC)
 * That would be a question for CFD, I think. I noted one, namely that people who regularly look for useless redirects could easily find them if all moves added the redirects to a category. For example, we have Can dogs see ghosts?, which I saw while looking through that category. Crisco 1492 (talk) 16:34, 10 June 2011 (UTC)
 * How is this a question for CFD? What possible use is a category to them? You can find all redirects already, without any category. — <span style="font-family: Courier New, monospace ;font-style:italic">V = IR (Talk&thinsp;&bull;&thinsp;Contribs) 16:50, 10 June 2011 (UTC)
 * This discussion is not; the usefulness of the category might be. Crisco 1492 (talk) 16:59, 10 June 2011 (UTC)
 * I aupport this for one reason; having the cat without this tempts people to add the cat to such redirects, which means one has to go through WP:RM to reverse the move. Often one shoud; but not always.


 * One alternative is to delete the cat. But that decision should also be taken at WP:CFD. Septentrionalis PMAnderson 04:57, 11 June 2011 (UTC)
 * If no-one can come up with an actual reason, in the next couple of days, why this category serves any purpose, then someone should CFD it. You've just given a good reason why it shouldn't exist. Rd232 talk 05:42, 11 June 2011 (UTC)
 * To quote Template:R from move: "Category:Redirects from moves, ... is used to track all moves that might result in the breakage of links, both internal and external, if a redirect is not installed properly." Seems somewhat reasonable. Crisco 1492 (talk) 23:17, 12 June 2011 (UTC)

Incidentally, the R from move template does serve a purpose, to help protect redirects from deletion which people may not see a use for (see template talk page). However it would serve that purpose better if the text in it actually appeared on the redirect page; for some reason, for me at least, it doesn't, and I can't see why. Rd232 talk 15:16, 12 June 2011 (UTC)
 * I think that's a technical limitation of the software. I've been cleaning up the classification backlog at WikiProject Indonesia and quite a few problems have been on pages that have been redirected without removing the WikiProject box; it doesn't display the box, but everything is still read by the software. Crisco 1492 (talk) 23:22, 12 June 2011 (UTC)
 * We might benefit from a WikiProject template bot that corrects the class to |class=Redirect on all such pages. It shouldn't be too hard to do; MZMcBride kindly generated a list like that for me a while ago.  Bad class assessments could be a significant problem for the WP:1.0 team.  WhatamIdoing (talk) 23:44, 12 June 2011 (UTC)
 * Agreed. Where would we make such a proposal? Here? In a new section, of course Crisco 1492 (talk) 23:58, 12 June 2011 (UTC)
 * WT:COUNCIL might be a good option, since that's a central meeting point for WikiProjects. I believe that WP:BOTREQ is the usual place to find bot owners who might write a script for you.  I'd start with WikiProject Council; you'll be able to get a full list of requirements.  WhatamIdoing (talk) 16:39, 15 June 2011 (UTC)
 * Request made at BOTR; I'd make the request at WP:COUNCIL but I will not be very active for the next few weeks so I wouldn't be able to participate. Crisco 1492 (talk) 09:06, 16 June 2011 (UTC)
 * Actually, automatically adding that template when moving would be better. According to the documentation, it populates Category:Redirects from moves and would let editors know the purpose of the redirect. I think I will change my proposal. Crisco 1492 (talk) 23:14, 12 June 2011 (UTC)

Advice on blacklisted external links
Recently, I had to change an edit before it could be saved. I was told that my external link has been blacklisted. This was not a vulgar site - just one on possible links between Asperger syndrome  and eating disorders. Do you think we should be given more advice on what websites have ben blacklisted, especially if they seem innocuous?15:59, 15 June 2011 (UTC)
 * Do you mean advice which pages are blacklisted or advice what to do if you if you want add a link to a blacklisted site? The first is bad idea per wp:DENY and also not practical as the lists are massive (see for yourself Spam blacklist and MediaWiki:Spam-blacklist). If you meant the second, the requirements for delisting are very strict, so if you don't know where to find it already you are not gonna stand a chance at requesting a delisting either. Yoenit (talk)

All I really meant there is perhaps we could have a few words at the top of articles on the type of external links which had been blacklisted. This was really stimulated when what, to me, seemed a very innocuous and quite academic external link seemed to get the blacklist tag. However, I appreciate your point that there is probably a very long list of blacklisted external links, so your point (if I understood your comment correctly) that listing blacklisted external links would not be practical is well taken. ACEOREVIVED (talk) 19:36, 15 June 2011 (UTC)
 * If you want more information on why a specific link is blacklisted, look it up on the MediaWiki talk:Spam-blacklist/log (local blacklist) or Spam blacklist/Log (global blacklist). 99% of the time there will have been problems with dedicated spammers, but it might be a special case or a false positive. Yoenit (talk) 07:58, 16 June 2011 (UTC)

Discussion at WP:MEASURE#A template for physical constants?
You are invited to join the discussion at WT:MEASURE. ― A. di M.​<i lang="ga" xml:lang="ga">plé​dréachtaí</i> 14:34, 16 June 2011 (UTC) (Using )

Deprecate the term "autoconfirmed" in favour of something meaningful
I just came across the term "autoconfirmed user" (referring to WP:AUTOCONFIRM) and found myself looking at it through newbie eyes and thinking WTF? It's a technical term without any obvious meaning for a newcomer to get a handle on. I propose deprecating its use throughout Wikipedia in favour of "established user" or something which similarly gives a flavour of what the thing being described means. The deprecation would be painless in that old shortcuts etc would work, but terminology in help pages, templates aimed at newbies etc would be rapidly standardised in favour of the new term. Rd232 talk 20:34, 8 June 2011 (UTC)
 * I frankly don't think this is a good idea. "Autoconfirmed" is a very objective term, whereas there's no implication with "established user" that there are a set of criteria which need to be met. In any case, many autoconfirmed users aren't "established" at all, and the term is a subjective overload. --Anthem 21:47, 8 June 2011 (UTC)
 * Note Anthem of joy has been indef blocked as a sockpuppet of Claritas . --Tothwolf (talk) 04:21, 15 June 2011 (UTC)
 * I wouldn't exactly call a user of 4 days / 10 edits "established"... --KFP (contact | edits) 22:00, 8 June 2011 (UTC)
 * I tend to agree. "autoconfirmed" is certainly jargon, but it's so well established now that trying to change it seems like unneeded effort to me. Just for the heck of it though, "verified" would be a better choice then "established". — <span style="font-family: Courier New, monospace ;font-style:italic">V = IR (Talk&thinsp;&bull;&thinsp;Contribs) 21:58, 8 June 2011 (UTC)
 * "well established" isn't much of an argument; no-one stopping oldtimers from using it, the issue is documentation. "Verified" is no good, that's actively misleading in suggesting some kind of verification (=checking) process. Rd232 talk 22:04, 8 June 2011 (UTC)
 * Well, that's where the objections to "established" are coming from as well. There's nothing about being autoconfirmed that makes a user "established". Maybe just dropping the "auto", so that the term is "confirmed", but again I don't really see the point of doing that now. I just think that this ship has sailed. — <span style="font-family: Courier New, monospace ;font-style:italic">V = IR (Talk&thinsp;&bull;&thinsp;Contribs) 22:53, 8 June 2011 (UTC)

Support heartily: Well, maybe I'm very different from other editors, but the whole gamut of Wikipedianese is something I've treated like reading a foreign language text or an alien slang: I just pass over many obscure terms because it would be impossible to read if I had to search for every definition; I just hope I pick up the vocabulary en passant and from context. That meant it was months, even years, before I fully grasped what dab, Prod, autoconfirmed, deprecate, RfA, XfD, RFC, ANI, CSD, FAC, CC-BY-SA, GFDL, etc., etc., meant. Surely there's a better term than "autoconfirmed": the question should rather be what's the best substitute: one that's clear, accurate and reasonably unambiguous. ¶ And, no, "autoconfirmed" doesn't necessarily mean what it says, any more than "Prod" or "Dab" do; to me (instead of being, presumably, a contraction of "automatically confirmed") it means "self-confirmed", which fits the minimum time and edits requirement in only in the vaguest and most indirect way —— Shakescene (talk) 06:47, 9 June 2011 (UTC)
 * Autoconfirmed is one of those weird wiki terms, and I personally see no need to change it. We aren't the simple english wikipedia here, people. I'm 99% sure that any newbie (like myself when I was one) gets the idea that autoconfirmed is some sort of status that a user gets automatically after a bit. Besides, what are we going to rename it to, "user with 10 edits and four days experience"? Ajraddatz (Talk) 22:10, 8 June 2011 (UTC)
 * I would prefer the term "editor" instead of autoconfirmed. Many other wikis have editor as what autoconfirmed on enwiki is. — Croisés Majestic (sur nous mars) 22:16, 8 June 2011 (UTC)
 * A solution looking for its problem. No need for change - a well 'established' Wikipedia term. Kudpung กุดผึ้ง (talk) 17:16, 9 June 2011 (UTC)
 * There's a difference between "well-established" [but only on the inside of Wikipedia] and comprehensible, especially to newcomers off the street who come across something that says a process is confined to Autoconfirmed Users. —— Shakescene (talk) 21:27, 9 June 2011 (UTC)
 * It reads intuitively to me, considering what it describes—a techie name for a techie threshold. The alternatives suggested do nothing to make the meaning comprehensible because the only way to do that is if the name states the threshold itself since there's not term for what this is in English, barring a description, and were not going to rename it "four days, ten edit barrier." Accordingly, no matter what the name, in order to learn what it is an unfamiliar user will still have to be told or visit the description page. If we change it, it will also conflict with the identical term used on many other projects; it is the same name used at Commons, at Wiktionary, at Wikinews, etc.--Fuhghettaboutit (talk) 22:33, 9 June 2011 (UTC)


 * Respectfully, I disagree that it's a "techie threshold" and therefore doesn't require explaining to non-techies. Autoconfirmed status represents a set of wiki privileges (uploading files, renaming pages, editing semiprotected pages) that new users regularly want. New users regularly come to #wikipedia-en-help asking why they can't do these things, and the answer -- "your account isn't autoconfirmed yet" -- doesn't really help them understand. If we were coming up with this feature for the first time right now, I would recommend "editor" for new accounts and "full editor" for autoconfirmed users. —Tim Pierce (talk) 22:54, 9 June 2011 (UTC)
 * Sounds like a good idea. -- Eraserhead1 &lt;talk&gt; 23:37, 9 June 2011 (UTC)


 * @Tim Pierce But I don't see any clarity provided by the rename that you seem to think is provided by it. Let's make it concrete. New User : " " Helper : " " New User : " " Helper : " " Do you see what I'm getting at? I'm not saying at all that because it's techie it "doesn't require explaining to non-techies". I'm saying that "your account isn't autoconfirmed yet" is exactly as opaque as "you aren't a full editor yet." Both require the same explanation (or a good link) in order for the person to know what the word/phrase means; no clarity is provided by the name change.--Fuhghettaboutit (talk) 23:40, 9 June 2011 (UTC)


 * Thanks for explaining your point a little more. Point taken: I agree that no matter what terms are used, they will require some explanation in order to understand exactly what that means.  But I don't agree that the term itself is irrelevant.  Users would still need an explanation to understand exactly what separates an "editor" from a "full editor", but the words' intrinsic meaning at least gives them a clue what kind of a difference it is.  Changing this term would be a subtle change, but I think it would be an important one. —Tim Pierce (talk) 02:03, 10 June 2011 (UTC)
 * Autoconfirmed gives clues: that it's some sort of access level, that it's a technical thing and that it's automatic. By contrast full/senior/established all could give the impression a person must earn a next level by being judged be fellow editors through some sort of process. I don't think that's a good impression to give. So, though no matter what the name it will need explanation, to the extent clues are provided by the title, I think the current is superior to the suggested.--Fuhghettaboutit (talk) 11:38, 10 June 2011 (UTC)
 * I agree with the last comment. I'm all in favour of eliminating wiki-jargon from our discourse, but in this case I don't think anything else we might think up would work any better.--Kotniski (talk) 11:42, 10 June 2011 (UTC)
 * Probationary? Provisional? ---— Gadget850 (Ed)  talk 17:06, 10 June 2011 (UTC)


 * We don't have to change the word "autoconfirmed". We can just change all the relevant help-/project-space pages from "autoconfirmed user" to "user account that is at least four days old and has made ten or more edits". Longer, yes, but more clear. If someone comes into #wikipedia-en-help asking how to move a page, there's no point in saying "you need to be autoconfirmed/other term" and then explaining what that term means. I've found it just saves time to say, "your account needs to be at least four days old and have made ten edits, now tell me what page you want to re-title so I can do it for you". In this manner, we can eliminate the jargon for new users trying to find help, but still keep the technical name when dealing with discussions on, well, technical stuff. / ƒETCH COMMS  /  18:32, 10 June 2011 (UTC)
 * This is a great idea. More clear for new users without having to actually change the name ("full editor" just doesn't cut it—it even sounds like it's something you have to pay for to become). Well done. Guoguo12  <font color="blue" size="1">(Talk)  18:50, 10 June 2011 (UTC)
 * I agree, this is the best possible course of action that we could take (at least out of what has been mentioned thus far). Ajraddatz (Talk) 23:03, 10 June 2011 (UTC)
 * That's the best solution so far, I think; and unlikely to be bettered by something that might actually reach consensus. Rd232 talk 05:45, 11 June 2011 (UTC)
 * Yup, but I would still put "autoconfirmed" in parentheses after the long phrase, wikilinked to wherever the concept is best explained - that way people have a chance to learn the jargon (which is actually useful in discussions among experienced editors where everyone knows what's meant) without being baffled by it.--Kotniski (talk) 10:11, 11 June 2011 (UTC)
 * Oppose rename as every comprehensive term would need explanation. Every other option thus far has flaws. For example I think "established user" isn't the same as 4 days and 10 edits and if an unregistered user edits with the same IP over many years, than it may be possible, that he becomes more established then a registered user. 82.131.238.34 (talk) 17:39, 12 June 2011 (UTC)


 * Support. It's a crufty term...I have 10,000 edits and still don't know what it means (honest).  TCO (talk) 23:23, 18 June 2011 (UTC)
 * Oppose, at least any term that would makes it explicitly look like brand new users and IPs are getting shafted from the get-go. Moreover, the above IP makes a good point about the one proposal. –MuZemike 09:29, 20 June 2011 (UTC)
 * Oppose. I always make a piped link to WP:AUTOCONFIRM when I say autoconfirmed to new users and so do many help pages. Those that don't, should. No term can convey the meaning accurately without actually saying "at least 4 days and 10 edits" (and that limit may change and doesn't apply to everybody). "autoconfirmed" gives clues to many people and it gives the right impression that it is a technical term so people can ask or look it up if it isn't linked. "Established" and other common words don't sound technical so many people will not realize it has a precisely defined meaning. "autoconfirmed" is also known by many from other wikis and written by the software in many places so we would need strong reasons to make up our own terminology. PrimeHunter (talk) 22:35, 20 June 2011 (UTC)

Change TfD to use subpages
Currently it is really hard to follow a specific discussion at WP:TFD. The page should be modified to use subpages like AfD does. This would make following a specific TfD a lot easier. Toshio Yamaguchi (talk) 18:35, 20 June 2011 (UTC)
 * Nah... the activity at TFD ebbs and flows, it's not normally as active as it seems to have been this past week or so. Besides, you are aware that you can watch a single day's worth of nominations at a time, correct? You don't have to watch the whole TFD page. — <span style="font-family: Courier New, monospace ;font-style:italic">V = IR (Talk&thinsp;&bull;&thinsp;Contribs) 18:47, 20 June 2011 (UTC)
 * It's really hard to scroll to one of perhaps four sections on a pretty short page and see if anybody has commented since you last looked? I admit that it is very distressing to be in such a scenario, but as Ω's law says, there really aren't enough TfDs – certainly not enough lengthy TfDs – to make such a change remotely worthwhile. <font color="#A20846">╟─TreasuryTag► consulate ─╢ 18:50, 20 June 2011 (UTC)
 * Ok, it is not "really hard". It is just a bit inconvenient. However I agree Wikipedia has more serious issues to focus on than this. So regard this as resolved per WP:DONTFIXIT. :) Toshio Yamaguchi (talk) 18:57, 20 June 2011 (UTC)

Several changes to file naming
I have identified several issues with file naming on Wikipedia, and believe that it should be made a priority that they are fixed. They are:


 * Case sensitivity in image names: As it stands, three separate users could upload three separate images of three separate subjects called File:TestImage.jpg, File:TeStImAgE.jpg, and File:Testimage.jpg. There is no reason why file names should be case sensitive.


 * Multiple filetype extensions for the same filetype: As it stands, two separate users could upload two separate images of two separate subjects as File:TestImage.jpg and File:TestImage.jpeg. There is no reason for this.


 * Case sensitivity in filetype extensions: As it stands, and as I have seen at least twice recently, two separate images can be uploaded as File:TestImage.jpg and File:TestImage.JPG. This has the potential to cause even more problems that the above situations. There is no reason why filetype extensions should be case sensitive.

Why does this matter? This has and will continue to cause confusing situations. People upload multiple copies of the same image because they are looking for it and cannot find it under what is essentially an almost identical name. It is counter-intuitive for someone who has uploaded File:TestImage.jpg to, upon not finding the image, look for it at File:TestImage.JPG. Instead, time after time users, especially new users, assume that the upload didn't stick and they then re-upload the same image. They get a notice that the image is already there, which is confusing to them because they already looked and already couldn't find it. I've also seen cases where someone tries to put an image into an article, gets the case wrong somewhere, and then panics because the image dosen't show up.

I don't know if it's feasible, but if the community decides that it's worth doing and the coders determine that it's feasible, I'd like to remove case sensitivity in both image names and filetype extensions. I would also like for some sort of patch to be put in so that all iterations of a given filetype extension (JPG, jpg, Jpg, JPEG, jpeg, JpEg, etc.) function interchangeably.

Thoughts?  S ven M anguard  Wha?  08:24, 31 May 2011 (UTC)

Addendum: If implemented here, this would not affect files from Commons. Therefore at the conclusion of this discussion, if it is successful, I will either ask the developers if this could be implemented WMF wide or, if they want it, start an identical thread on Commons. I didn't think of that until now. Sorry  S ven M anguard   Wha?  19:05, 31 May 2011 (UTC)

Agree I agree with all of these points - especially number 2 which has potential to cause much confusion. Oddbodz (talk) 08:35, 31 May 2011 (UTC)


 * Totally agree. There is no reason why we must force article functionality onto files, and now that filemoving is enabled, it would be simple to fix project wide. ▫  Johnny Mr Nin ja  09:20, 31 May 2011 (UTC)
 * I would hope that a bot would be able to check for naming conflicts and then once those are taken care of backend code would be able to do the rest. I see that File:Example.jpg and Image:Example.jpg work interchanabally in the articlespace, so I was hoping, at least for the second of the three points here, that an identical situation (all forms of a filetype being capable of being used interchanabally) could be done up.  S ven M anguard   Wha?  18:54, 31 May 2011 (UTC)


 * Support 2,3. Case-sensitive and "synonym" extensions can only serve to confuse and have no real benefit. I am unsure if it will be feasible at this point to have case-insensitive file names. I'm sure there are plenty of cases where File:AIR.jpg and File:Air.jpg stand for some organisation AIR and the other for air component chart or something. The mess and workload it will create may overweight the actual benefits. But I'm educated guessing, someone working a lot with images/moving should comment. — HELL KNOWZ  ▎TALK 09:41, 31 May 2011 (UTC)
 * If there are too many conflicts, one solution might be to make it so that current files are uneffected, while files in the future cannot be uploaded if an identical name exists in a different case configuration (similar to how users can no longer upload images with names like File:IMG0002.jpg, however the files already named like this are unchanged. I know that implementing it here would require a different solution, but the concept is the same.)  S ven M anguard   Wha?  18:59, 31 May 2011 (UTC)


 * Support 2,3 per H3llkn0wz. I suspect retrospectively adding full filename case insensitivity is too much of a headache. [Addendum: Sven's suggestion on point 1 of making it apply only to new uploads would be fine.] Rd232 talk 09:52, 31 May 2011 (UTC)
 * Support - I have thought the same thing. --Kumioko (talk) 11:14, 31 May 2011 (UTC)
 * If there is such a file on upload the user should at least get a prominent warning so that they can be aware of a preexisting file. Graeme Bartlett (talk) 23:38, 31 May 2011 (UTC)
 * Shouldn't this discussion be on meta or commons? Changing this just for the English Wikipedia would be mostly pointless and inconsistent. Mr.Z-man 00:11, 1 June 2011 (UTC)
 * Yeah, I thought of that just recently. Let's let it get some support here though, as developers rightly tend to like to see consensus before they change anything, so the more consensus we can show them, the more likely they will implement a solution.  S ven M anguard   Wha?  00:40, 1 June 2011 (UTC)

FYI: I was told to post at BugZilla bug 4421 and have done so.  S ven M anguard  Wha?  05:39, 1 June 2011 (UTC)


 * Support fixes for all 3 cases specified. H3llkn0wz has a reasonable concern about<tt> AIR.jpg </tt>vs.<tt> Air.jpg </tt> but Sven's suggestion to grandfather in existing conflicts of that nature until they can be resolved eases my concern about that. Allowing separate images to be uploaded as (to make up an example) both<tt> Disney Logo.png </tt>and<tt> Disney logo.png </tt>is just asking for headaches and confusion. 28bytes (talk) 05:49, 1 June 2011 (UTC)
 * As far as I know, we also have a similar block of uploading files that conflict with Commons, but existing conflicts remain until fixed. ▫  Johnny Mr Nin ja  06:07, 1 June 2011 (UTC)
 * I intend on fixing the commons conflicts, just as soon as I'm done fixing the bad image names (there are 3000 of them, see user:Chzz/dsc0511 for a sample of what I'm dealing with now) . If this is approved, and the number of conflicts is reasonably sized, I'll work on that before I get to the commons conflicts too. The great thing about filemover is that there are a half dozen people that are actively helping to clean out these massive backlogs, a task previously inaccessible to non-admins. I don't see the naming conflicts as being a long term headache, they can get cleaned up rather quickly if this goes through.  S ven M anguard   Wha?  23:45, 1 June 2011 (UTC)
 * Support to all 3 above. Case in point being file:Miranda Kerr.jpg vs file:Miranda Kerr.JPG. At present, it's just luck that we do not have file:Miranda Kerr.jpeg and file:Miranda Kerr.JPEG too ;-) Illogical! -- Ohconfucius  ¡digame! 08:00, 2 June 2011 (UTC)
 * Support 2&3, some files do need to have their names distinguished. — James (Talk • Contribs) • 10:08pm • 12:08, 2 June 2011 (UTC)
 * Support I have been the victim of similar mistakes, and it is frustrating how long it takes to sort it out, because I essentially assumed case wouldn't matter, so it never occurred to me to track that down.-- SPhilbrick  T  22:29, 2 June 2011 (UTC)
 * Comment - The above linked bug was first brought up in 2005. If you'd like to see it implemented, don't just show your support here, but login to 4421 and vote there too. This will let the devs see how much support it has. ▫  Johnny Mr Nin ja  08:04, 3 June 2011 (UTC)
 * Support, I don't like to add images and have to look multiple times for the uppercased letters. <b style="font-family:Courier New; display:inline; border:#009 1px dashed; padding:1px 6px 2px 7px; white-space:nowrap; color:#000000; font-size:smaller;">mabdul</b> 08:52, 4 June 2011 (UTC)
 * Support 2 and 3, because they are fairly logical; I'm not so sure about 1, given that there may be legitimate reasons to upload different files under different casings. — mc10 ( t / c ) 00:56, 7 June 2011 (UTC)
 * Support if this change is made on all projects, particularly Commons. We don't need different functions on different projects. Also, we need to discuss how the mass renaming would be handled; add a "1" at the end of the newer file name before extension maybe? Reh  man  08:37, 9 June 2011 (UTC)
 *  Oppose 2,3  - file name extensions are not gospel. MIME associations determine the type of file. Users may have good reasons to name their files the way they do. Jason Quinn (talk) 07:49, 16 June 2011 (UTC)
 * You lost me. Wikipedia treats Foo.JPG and Foo.jpg and Foo.jpeg the same, as all three are the same file type. Good reason for choosing one of those over the others or not, if those three Foo are three totally different things, and the only way to tell between them is file type extension, well that's just absurd.  S ven M anguard   Wha?  08:31, 16 June 2011 (UTC)
 * I see. I misunderstood the intention. I thought you meant using only one extension type exclusively. I retract my oppose. Jason Quinn (talk) 05:53, 17 June 2011 (UTC)
 * Support if all projects - Oppose if only this one - Points 1 & 3 are simply a matter of converting the name to lower or uppercase before checking if it already exists. Point 2 won't be much more work. Arlen22 (talk) 18:32, 22 June 2011 (UTC)

Permanently protect closed AfD discussions
A closed AfD discussion carries the following message on top:

''The following discussion is an archived debate of the proposed deletion of the article below. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the article's talk page or in a deletion review). No further edits should be made to this page.''

Wouldn't it be better if the closing admin simply redlocked the discussion? Toshio Yamaguchi (talk) 14:11, 9 June 2011 (UTC)


 * I don't see the need for that. Even if some people added opinions after closure, nobody noticed that, and then they tried to act as if there was a different consensus, the page history would reveal the trick Cambalachero (talk) 15:09, 9 June 2011 (UTC)


 * Sometimes archived discussions have to be changed for renamed editors or for moved articles, to change the links. Fram (talk) 15:14, 9 June 2011 (UTC)


 * Another posible case is when people cite a category during a discussion. Sometimes they mention rather than Category:Foo (with : before "Category") The discussion is thus categorized there, and someone checking the categories would need to clean it from unwanted entries. Cambalachero (talk) 15:23, 9 June 2011 (UTC)

No. Sometimes closers make technical mistakes in closing. Sometimes, a post-close comment,made under "no further comments" line, outside the coloured section, are appropriate. Sometimes, there is a subsequent XfD, or DRV, and it is very helpful for this to be noted, but for reviewers of the history down the tract, and for participants who keep the XfD page watchlisted for this very reason.

Is there a problem with edits to closed XfD pages? I think I have thousands of such pages watchlisted, and I check my watchlist regularly, and I don't see problems with edits to old pages. Instead, I think people can be trusted if you trust them. --SmokeyJoe (talk) 13:19, 12 June 2011 (UTC)


 * I don't think it's necessary. If there's a serious problem with closed AfDs being edited in problematic ways, and such edits are significantly more frequent than good edits to these pages (such as the types mentioned above by and ), then it ay be necessary; however, I don't think these problems are, in fact, there. עוד מישהו Od Mishehu 07:36, 13 June 2011 (UTC)
 * Really, there should be a MediaWiki plugin for AfDs (and many of our other internal processes) so that their pages aren't just vanilla wikipages, but instead have a proper custom workflow. One of legion MediaWiki nice-to-haves. --<b style="color:#3773A5;">Cyber</b> cobra (talk) 22:22, 19 June 2011 (UTC)

I would oppose redlocking of closed deletion discussions, simply because when it says "An article was cited for deletion" and then says the result was keep, it is quite interesting to go to discussion. Only my humble view - let me know if I have misunderstood anything here. ACEOREVIVED (talk) 20:08, 22 June 2011 (UTC)

Warn about special editing restrictions
I just recently inadvertently broke a one-revert restriction. The problem is that though the warning comes up at the top of an edit page it doesn't come up if one just presses the rollback button when looking at an edit diff. It is reasonable to put up the restriction on a page that shows buttons for reverting or else after pressing such buttons? Thanks. Dmcq (talk) 22:45, 18 June 2011 (UTC)
 * I'm not trying to be a jerk here or anything but... if you're under an editing restriction of any kind, what in the world are you doing using rollback? O_o — <span style="font-family: Courier New, monospace ;font-style:italic">V = IR (Talk&thinsp;&bull;&thinsp;Contribs) 23:30, 18 June 2011 (UTC)
 * I think the general sanctions/ arb com rulings in the area are being referred to (climate change etc.). As is theres a warning on the talk page, a warning on the edit screen and a policy of not dishing out blocks without clear warnings first - it seems like probably enough to me. Regards, Bob House 884 (talk) 23:32, 18 June 2011 (UTC)
 * OK, I can understand that. However, I'd think that begs the question even more. If you're working on a page that is under restrictions of any kind, what in the world are you doing using rollback? And, I doubt that any admin or arbitrator will object to rolling back a series of blatant vandal edits, regardless of whether or not the page is under restrictions. — <span style="font-family: Courier New, monospace ;font-style:italic">V = IR (Talk&thinsp;&bull;&thinsp;Contribs) 23:38, 18 June 2011 (UTC)
 * What should one use if a person sticks in something silly in an article? The talk page does not say 1rr and the link on the talk page does not point to anywhere that talks about 1rr. The warning does not appear if one uses rollback. What I'm talking about is a warning if one uses rollback. And in fact there doesn't seem to be a blanket 1rr restriction on such articles, it just was stuck on that particular article for some reason and not noted anywhere that I know of. Anyway does your question have anything to do with what I was proposing? Do you want to hide such things like land mines? Dmcq (talk) 11:34, 20 June 2011 (UTC)
 * They're not hidden though, a warning pops up on the edit screen and the talk page makes it clear that there are some sanctions on the article (and a rollbacker should probably know that any sanctions on the article warrants extreme caution with rollback). Even then you can't be blocked for violation of it without a warning - the warning itself isn't a sanction, it's there to make absolutely clear that you are aware of the 1RR. The result is that nobody can be blocked for a 1RR violation unless its shown that they knew, or should have known, about the sanctions. In this case, even though you skipped out the edit screens and talk page notes, you were obviously made aware of the special rules on the article and no administrative action has been taken. You might disagree but that seems pretty tight to me. Regards, Bob House 884 (talk) 14:33, 20 June 2011 (UTC)
 * How exactly should I have found out about it before doing the rollback? Dmcq (talk) 18:18, 20 June 2011 (UTC)
 * By looking first? I don't understand where the mix-up is, here. There may not be warnings plastered all over the article, but... I mean, you could take 10 seconds to look at the talk page. Why is everyone always in such a hurry to use rollback, undo, and similar things? — <span style="font-family: Courier New, monospace ;font-style:italic">V = IR (Talk&thinsp;&bull;&thinsp;Contribs) 17:48, 22 June 2011 (UTC)
 * You don't necessarily need to look at the talk page to figure out whether blatant vandalism like "I LOVE CHEESEBURGERS!!!!!!!" should be reverted. If you're doing recent changes patrol work, your goal is to get vandalism removed now, not after several more readers have seen it—even if that means removing it before you carefully study whether there are unusual situations at the article.  WhatamIdoing (talk) 22:00, 22 June 2011 (UTC)
 * Covered above, though. No? — <span style="font-family: Courier New, monospace ;font-style:italic">V = IR (Talk&thinsp;&bull;&thinsp;Contribs) 22:57, 22 June 2011 (UTC)

If it's blatant vandalism, I doubt anyone would object per 1RR. If it's not... you should be investigating the edit & the talk page, not automatically rolling back the edit. &mdash;  The Hand That Feeds You :Bite 22:59, 22 June 2011 (UTC)

Tagged hotlinks in photos
http://en.wikipedia.org/wiki/Riviera_Maya it would be useful to be able to click elements of a map/diagram/photo to link to the entry for the tagged object (eg. the cities in the Riviera Maya map). Doc Martian (talk) 09:52, 22 June 2011 (UTC)
 * You can create an WP:image map, which has a similar effect. - Jarry1250 [Weasel? Discuss.] 15:56, 22 June 2011 (UTC)

RfC on minimum prep-time for main-page blurbs
Editors are welcome to discuss this proposal here. Tony  (talk)  11:07, 22 June 2011 (UTC)

equations translated to english
I saw this idea on the village pump ideas lab at [|(link)]. it would be really useful for me and at least one other person in trying to learn math from Wikipedia. Σ
 * I suppose you could have a user/browser plugin which explains the meaning of mathematical operators when selected, but a general translation of math to english? Sure 1+1=2 can be written as "one plus one equals two", but try doing the same with the Navier-Stokes equations in spherical coordinates. Your "translation" would become so long it would impossible to understand, which is probably why people invented math in the first place. Yoenit (talk) 07:41, 20 June 2011 (UTC)
 * You can use the  attribute:   gives . It is, in fact, recommended, for screen readers and other browsers which don't support inline images. ― A. di M.​<i lang="ga" xml:lang="ga">plé​dréachtaí</i> 20:38, 23 June 2011 (UTC)

Improve all performance information for cars with automated tools
I have noticed that most articles does not provide very confident information about performance, I even notice that there is no a defined writting style for this performance information.

I would like to propose a little fact information that should be included at performance section of all cars, or at least sports cars, I think that could provide useful information to a lot of car enthusiast people, in a single place you could find all that information

Performance facts: Time to Speed (mph or km/h does not matter) Time to Distance (or distances in meters, does not matter)
 * Enviroment conditions: Temp: Xc, Humidity: Y%, Altitude: Z meters
 * 0-30 mph
 * 0-60 mph
 * 0-100 mph
 * 0-200 kmh
 * 0-100 m
 * 0-1/8 mile
 * 0-1/4 mile
 * 0-1 km

Top Speed: W mph (or km/h)

It could be done very easy with car performance simulators like the one I am working on (www.nxgtrsim.com) or any other that could be used for Free, which I think gives very real results and it is the only option that is Free + Online + Advanced in whole internet, and could help to wikicars a lot.
 * Why do you consider these simulators to be reliable sources? And if they aren't reliable sources, their info should not be included in Wikipedia. Fram (talk) 09:28, 23 June 2011 (UTC)
 * I think this is one area standardisation is not necessary. We can cite what we think is appropriate. It's clearly possible to accurately (and usefully) describe the performance of cars is a useful way, and I don't think Wikipedia gains much from all articles being the same. Infoboxes, however, use of and data used, would be more feasible a standardisation. Grandiose (me, talk, contribs) 19:19, 23 June 2011 (UTC)
 * Something like that would make an excellent tool for an automotive review program/magazine-- which we could then potentially cite as a WP:RS. If your simulator is any good, I'd suggest you talk to those sorts of groups. If we used it, it would almost certainly be WP:OR. Wabbott9 (talk) 00:21, 24 June 2011 (UTC)

List of Wiki internal linking
Hello,

I oftentimes skim through artikels. Often i spot interesting Wiki Links (http://en.wikipedia.org/wiki/Wikipedia:Linking) but i dont open them, forget where they were or simply forget what artical i wanted to open. :) so i thought it would be nice, for many more reasons (also to keep track), to see an alphabetical list of all the links within that articel.

for example http://en.wikipedia.org/wiki/Computer now i want a list of all links, i.e. related articels

progammable machine memory data

and so on.

194.9.246.48 (talk) 13:18, 24 June 2011 (UTC)


 * If you are looking for all the articles that link to Computer that is here, Special:WhatLinksHere/Computer. You can find this list on the left side of the article in the toolbox under "What links here".  If you are looking for an alphabetical list of all the articles that Computer links to, I don't think that is done anywhere.  GB fan (talk) 13:31, 24 June 2011 (UTC)


 * Hello.
 * Thanks for your kind reply. Highly appreciated.
 * I was actually looking for the second, as this would give you like a mindmap/network of related topics/articels which would be awesome. Surely there must be a way to implement that.
 * I have to add though, that I am thankful for your tip with that "link to".
 * Have a good one.

194.9.246.48 (talk) 14:48, 24 June 2011 (UTC)


 * Though one could use WP:AWB to see all the pages that Computer links to. <sup style="color:red;">Avic <sub style="color:blue;">ennasis  @ 11:21, 14 Av 5771 / 14 August 2011 (UTC)

RFC: implementing Manual of Style restructure
Editors may be interested in revisiting this RFC, now that there is discussion of its implementation: "Should all subsidiary pages of the Manual of Style be made subpages of WP:MOS?" It's big; and it promises huge improvements. Great if everyone can be involved. N oetica Tea? 00:58, 25 June 2011 (UTC)

Dispute resolution noticeboard
<div class="boilerplate metadata" style="background-color: #edeaff; padding: 0px 10px 0px 10px; border: 1px solid #8779DD;">
 * The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page.  No further edits should be made to this discussion.

Have moved this over from the Idea lab to garner some consensus on giving this trial an idea. Part of this comes out of from comments and suggestions on the RFC on dispute resolution.

It seems to me that disputes on Wikipedia are all over the place, as in, they are not where they should be. We have people filing mediation cases for conduct issues, and vice versa. Some users don't seem to realise the best forum for getting their dispute resolved. Others just prefer to go to ANI directly. As a result disputes often get disjointed, and it becomes quite hard for mediators / "helpers" to keep track of, as well as ANI getting clogged up with disputes that sometimes either just don't belong there, or would be better suited at a proper dispute resolution forum. Perhaps, to try and counter this, we could create a new noticeboard, say Dispute resolution noticeboard where we would have users being able to post their enquiry there and get some dispute resolution there on the spot by a mediator, or in disputes where it is evident the matter is detailed or one that does not have a simple resolution, could be referred to a proper forum, say an RFC, RFC/U or mediation. This noticeboard would exclude matters that should automatically go to arbitration, and standard stuff that should be at ANI, like block appeals etc. All other threads that are clearly dispute related that are posted at ANI could be closed, and sent to the disputes noticeboard instead. Additionally we could post a link on all present DR pages with a link to the noticeboard if the user is not 100% certain if that is the correct forum.

While I do see the potential for this noticeboard to get clogged up if not managed properly managed, I think that if correctly managed this idea could help reduce ANI getting clogged up with disputes that just don't belong there, and streamline the dispute resolution process in that we could point disputes in the right direction as opposed to being posted in 10 different places before finding the correct one. It could also help resolve low-level disputes, and nip them in the bud, so to speak.

To keep discussions on the page focused, we could have a similar format to SPI (with mediators or "clerks" to make sure discussions don't get out out of hand, stay civilized) but with users not having to post with funky templates. A simple comment about what the dispute is, who is involved, what has been happening, and then we can point them in the right direction, or get some basic DR underway. While I realise this is a new idea, I don't see any harm in giving it a trial go. ANI is far too clogged up nowadays with disputes that don't belong there, and disputes are often all over the place. Some forums for DR nowadays (WQA being a good example) work poorly and I think giving this idea a go might work. If it doesn't work, it doesn't work, but at least we will have given it a go. Steven Zhang <sup style="color:#FFCC00;">The clock is ticking....  23:37, 1 June 2011 (UTC)
 * That sounds like a bloody good idea. -- Eraserhead1 &lt;talk&gt; 23:39, 1 June 2011 (UTC)
 * Support. —<b style='color:#464646'>[d'oh]</b> 00:23, 2 June 2011 (UTC)
 * Support + improve WP:DR. A noticeboard is a good idea, but important to make sure it helps and doesn't just try to absorb every other issue. Specialist noticeboards and talk pages have their place too. In some cases it may need to point users to other venues. I made a start on restructuring WP:Dispute resolution a while ago to give much-needed better guidance, which might help too. (Link to draft - feedback welcome). FT2 (Talk 01:23, 2 June 2011 (UTC)
 * The noticeboard is more designed to be a starting point for disputes to go to, as opposed to a replacement for the noticeboards that already exist. That said, some disputes are trivial and a quick discussion or some advice is all that's needed, which would prevent clogging up a noticeboard like ANI, and would also aid in resolving the dispute, as DRN would be watched by those that actually resolve disputes (or learning to) as opposed to ANI. It's a specialised noticeboard for a specialised problem. There are other times where new users just aren't aware of basic policies and need these explained, ie, they file a medcab case because a user keeps removing their unsourced info from an article. The main aims of this noticeboard are to a) Help keep track of disputes b) Act as a starting point for most disputes in the resolution process, ensuring they actually get directed to the best forum where they can be addressed properly and c) Aid in resolution of small disputes and trivial matters such as examples I listed above. It's designed to be a central point for the DR process, not a replacement for the existing processes. WQA has some severe issues, as most matters that get sent there end up with parties slinging mud at each other. Perhaps WQA could be marked historical with disputes starting at DRN and either finding quick resolution or referred to RFC/U. This way we can also keep discussions civilised and properly address disputes that have genuine issues, but nip in the bud "this user reverted my edit/I don't like them" type disputes that we too often see at WQA. Steven Zhang  <sup style="color:#FFCC00;">The clock is ticking....  03:03, 2 June 2011 (UTC)
 * Support. This makes sense.  DR is policy and next to RS, NPOV, and BLP is the most common and most disruptive part of Wikipedia.  (While we're at it we should get rid of Content noticeboard and maybe merge this eventually with Wikiquette Noticeboard, which is a giant waste of finger-pointing time). The board would work to help navigate all aspects of disagreements and complex issues.  It could be staffed by mediators and focus on compromise and building consensus.  It would be an ideal complement to multi-factoral debates which don't fit neatly at any one board, but without necessitating an RfC.  A good idea. User:Ocaasic 03:46, 2 June 2011 (UTC)
 * Question. Does this proposal differ substantially from formal mediation? Maybe it just makes mediation more prominent as a dispute-resolution opportunity? —Tim Pierce (talk) 03:49, 2 June 2011 (UTC)
 * Yes. This noticeboard is not designed to replace any of the major dispute resolution processes (except perhaps WQA) but to complement the existing processes, clarify the disputes, resolve little ones that referring to a different process would be a waste of time or unnecessary, and point users in the right direction as to where the best place to sort out the dispute is, as currently, and often, disputes get sent to the wrong place. This noticeboard would aim to fix that. A noticeboard monitored by those who have experience in DR, getting little disputes resolved quickly, and referring others to the correct forum for resolution. Steven Zhang  <sup style="color:#FFCC00;">The clock is ticking....  03:55, 2 June 2011 (UTC)


 * Support. Proposal is very reasonable. AGK  [</nowikI>&bull; ] 10:20, 2 June 2011 (UTC)
 * Support Long overdue IMO. — James (Talk • Contribs) • 10:03pm • 12:03, 2 June 2011 (UTC)


 * Support sounds reasonable.Theo10011 (talk) 13:19, 2 June 2011 (UTC)
 * Support so long as scope is clear, and matters are speedily sent to the appropriate venue if necessary. Grandiose (me, talk, contribs) 13:36, 2 June 2011 (UTC)

I have submitted a rough draft of the noticeboard. It is at Dispute resolution noticeboard. I still haven't finished off the edit notice yet. Steven Zhang <sup style="color:#FFCC00;">The clock is ticking....  14:42, 2 June 2011 (UTC)


 * Support Although the existing noticeboards suffer from understaffing, I would still support this if traffic could be redirected from ANI. That will take merciless clerking, however, so I hope volunteers will be willing to step up to the plate. <font face="New York">Skomorokh  15:47, 2 June 2011 (UTC)
 * Is there/could there be a technical way to move a thread to a different venue with only a click? (I'm thinking user-enabled, to help volunteers.) Grandiose (me, talk, contribs) 15:52, 2 June 2011 (UTC)
 * I don't know of any current thread-moving tool, but it would be both feasible (going on the way Twinkle expedites multiple edits to different pages in the deletion process with a single click) and to me welcome, if you can find someone to code and maintain it. <font face="New York">Skomorokh  16:06, 2 June 2011 (UTC)
 * (Reply to Skomorokh) - I'm hoping that with this noticeboard admins will direct stuff that doesn't belong at ANI but does belong at the dispute noticeboard, to this noticeboard. It will be partly up to clerks to monitor ANI, partly up to admins to move threads there. There has to be a way in script to move pages from one page to another. I'll have a look into it. I know there's a script that does voting on AFD, I'll see if I can modify it to have it move sections. Or there might be a way a bot can move sections that are tagged with a certain template, say, move to DRN, to the disputes noticeboard. Will try to get some input on this. Steven Zhang  <sup style="color:#FFCC00;">The clock is ticking....  23:54, 2 June 2011 (UTC)


 * Support Seems reasonable and worth a try. I'd love to have comments segregated into Involved and Uninvolved sections and have the clerk be able to enforce this.  A Quest For Knowledge (talk) 15:59, 2 June 2011 (UTC)
 * Question Looking at the present state of WP:ANI, what proportion of the threads there would you envisage ought to start at the dispute resolution noticeboard in future? Most of the discussions revolve around inter-editor disputes – would this noticeboard swallow most of ANI? <font face="New York">Skomorokh  16:13, 2 June 2011 (UTC)
 * If that meant that ANI did a better job of handling admin issues, which in my experience it handles very poorly, that would be a bonus. -- Eraserhead1 &lt;talk&gt; 17:56, 2 June 2011 (UTC)
 * Skomorokh, stuff that is still within the scope of ANI would stay at ANI. Stuff like sockpuppetry, block evasion, edit warring etc, stays at ANI. Other stuff is to the discretion of admins and clerks as to whether to move it over to DRN. It's not going to be 100% clear right off the bat. Our aim should be to encourage users with content and conduct disputes that does not fit within ANI's scope (stuff that would normally go to WQA, RFC, third opinion) to DRN to assist in the clarifying what the actual dispute is to make it easier to resolve, what the best forum for resolution is, or in limited circumstances providing resolution on the spot. Stuff is still going to get posted to ANI that probably belongs at DRN. It will take time to get familiar with what should be moved to DRN and what shouldn't, but like I said it's worth a go. We can learn as we go along. Steven Zhang  <sup style="color:#FFCC00;">The clock is ticking....  23:54, 2 June 2011 (UTC)
 * Support. At least it's worth a try. Two suggestions: make it clear that other DR venues should not require attempting to resolve the issue here first (since it may only be a place where you get told where to go next), and make sure the format of the page does not lend itself unduly to just posting someone's name in a flaming manner (like using it to post the names of users one doesn't like; in other words, there should be some indication of a dispute, not just a name or list of names). --Tryptofish (talk) 18:57, 2 June 2011 (UTC)
 * In regards to your first point, no, if a dispute clearly belongs at mediation, a user does not have to go to DRN first. Other issues, sure. If the user feels that the DR avenue they have selected is best, they can use it. This comes with two caveats. One, if a user files a dispute on a page, and it does not belong there, they can be directed to DRN to find the best forum, and two, what the dispute about is should be clear. If, on the page they posted the dispute, it is not clear what the dispute is, they could also be directed to DRN. The main aims of this noticeboard are to a) Have the topic of disputes clearly clarified, to aid in resolution and b) Ensure that disputes are sent to the right forum. So, while using DRN will not be required before other DR forums, but it is recommended, especially if it is not clear who/what is in dispute, or where it should go to, in the case of mixed content-conduct issues.
 * In regards to your second point, with having clerks patrol the page, unlike WQA at present, the aim is to not have this sort of behaviour allowed. No longer will these sort of noticeboards be a place to flame users, rather, it will be the first location to bring up new disputes in regards to legitimate conduct issues, discussed in a civilised manner, as well as content issues, also in a civilised manner. Clerks will not be civility police, but bad conduct will not be tolerated. We've dealt too long with flaming at places like WQA and ANI, and it does not help resolve the issues. Time to make a change for the better. Steven Zhang  <sup style="color:#FFCC00;">The clock is ticking....  23:54, 2 June 2011 (UTC)
 * I agree. Those are good answers, very well thought out. --Tryptofish (talk) 18:52, 3 June 2011 (UTC)
 * Very cautious support The idea is pretty good, but it's also delicate. We have to balance helping new users with not creating a new layer of bureaucracy or adding an additional venue to forum-shop at. Also, clerking/mediating is reasonable, but good mediators are not every user, and making it excessively formal like ArbCom only makes dispute resolution take longer. / ƒETCH COMMS  /  23:11, 2 June 2011 (UTC)
 * The noticeboard's main aims are to move disputes away from ANI where they don't belong, and disputes where the situation or scope is not clear, to this noticeboard, for clarification and direction to the best place for resolution. Forum shopping, not allowed, which would be enforced. I agree that bureaucracy is bad, and that allowing everyone to clerk would not be the best idea. Perhaps the user could demonstrate some experience with dispute resolution in order to clerk? We don't want to make the process to bureaucratic, but at the same time need to ensure the people directing users to other DR forums actually know what they are doing. Steven Zhang  <sup style="color:#FFCC00;">The clock is ticking....  23:54, 2 June 2011 (UTC)
 * Support and highly encourage editors who make posts at the more specialized boards (NN, AN*, 3RR, BLPN, etc.) that are less experienced to come here first. Obviously if an established editor creates a thread at those other locations, they know what they are doing and don't need to come here to get their post at the other location. I can think of 30 or so threads in the past few weeks on ANI that should have been resolved elsewhere. Hasteur (talk) 20:31, 2 June 2011 (UTC)
 * Sure, experienced users don't have to post here first if they know exactly which forum to take the dispute to. This noticeboard is not designed to be an extra hoop people have to jump to, it is more designed as a mail sorter. Clarify what the dispute is and what needs to be resolved, and direct them to the best forum for resolution. With the two caveats I listed above. If a user files a dispute at a DR forum and it's the wrong place, they can be directed to discuss the dispute at DRN, two the dispute needs to be clarified in a way that is clear for helpers to aid in resolution. Otherwise it might have to be sent here. If an RFC/U is posted with the user stating "User Y keeps reverting my edits, I don't like it" etc, then sure, that needs to go to DRN. Steven Zhang  <sup style="color:#FFCC00;">The clock is ticking....  23:54, 2 June 2011 (UTC)
 * Support DISPUTE should be updated accordingly, the last line of DISPUTE, should also be emboldened in some way with a link to the new noticeboard. The  Helpful  One  00:01, 3 June 2011 (UTC)
 * The relevant DR pages will need to be updated if consensus for this idea goes ahead, but I want to wait until that first. We might need to also analyse where users who have the disputes find the forums they go to, and see if there's a way to direct them to the new noticeboard if they're unsure of the best forum. See my above comments. Steven Zhang  <sup style="color:#FFCC00;">The clock is ticking....
 * Support &mdash; but jokingly oppose as it'll reduce the overall drama level at WP:ANI and therefore hurt sales at my Torch and Pitchfork Emporium. -- slakr \ talk / 00:07, 3 June 2011 (UTC)


 * Comment - Not dealing with this much, I don't have much of an opinion. I'd just like to point out that this is the second SUPPORTed noticeboard on this page right now, and we have a good-many noticeboards out there already. I just hope that the maintainers will do their best to advertise this board, and will have the guts to shoot it if the time comes. ▫  Johnny Mr Nin ja  00:34, 3 June 2011 (UTC)
 * Support - This is an awesome idea. There are numerous times when I find a content dispute that has been brought to a noticeboard (especially ANI) and I've directed people to WP:DR. Being able to direct someone to an actual board would be much better than just a policy page (especially since they've already reached out to one noticeboard, they'd be more inclined to try another). I might even try my hand at helping support such a board. --  At am a  頭 16:48, 3 June 2011 (UTC)
 * Support proposal is reasonable and well-formulated. Would be useful and helpful to new & experienced WP users alike.--JayJasper (talk) 17:02, 3 June 2011 (UTC)
 * Support - useful board.Anthem 19:11, 3 June 2011 (UTC)
 * Note Anthem of joy has been indef blocked as a sockpuppet of Claritas . --Tothwolf (talk) 04:17, 15 June 2011 (UTC)
 * Support. A reasonable proposal that could help things, and seems unlikely to harm anything; worth trying, at least. 28bytes (talk) 20:32, 3 June 2011 (UTC)

Summarised proposal
It seems to me like there is a fair bit of consensus to giving this idea a go and seeing how it will work. So we are entirely clear on the functions of this noticeboard, I have compiled a summary of what the noticeboard would do, and what noticeboards it would replace, and a summary of how it would function. Comments on the summary are welcome.


 * 1) This noticeboard would primarily be used for users to post a brief summary of the dispute/issue, and can either get some on the spot resolution by a "clerk" (I use that term sparingly) or mediator in situations where it is either a small dispute, a trivial one, or one that resolving on the spot as opposed to referring to a proper forum would be a waste of time (see examples above). In disputes where it is evident the matter is detailed or one that does not have a simple resolution, could be referred to a proper forum, say an RFC, RFC/U or mediation. This noticeboard is not designed to replace all other DR noticeboards, except to absorb, as a trial, the sorts of comments that would go to WQA and Content noticeboard. This noticeboard would not be mandatory to use, as in, it would not be a "hoop" people have to go through to pursue other dispute resolution. This would come with two caveats. One, if a user files a dispute on a page, and it does not belong there, they can be directed to DRN to find the best forum, and two, what the dispute about is should be clear. If, on the page they posted the dispute, it is not clear what the dispute is, they could also be directed to DRN. The reasons for this are to a) Have the topic of disputes clearly clarified, to aid in resolution and b) Ensure that disputes are sent to the right forum to ensure resolution is actually possible.
 * 2) Update - A trial would be undertaken to implement the noticeboard in two stages. In stage one, discussions on WQA and the content noticeboards would still occur on those noticeboards, but a notice would be posted on the pages to suggest DRN as an alternate forum. This could be used to parallel the good and bad aspects of the new noticeboard, and compare with the good and bad aspects of existing noticeboards. This trial would last a month, and at the end of the month a discussion would take place outlining the results of the first trial. Stage two would involve the WQA and Content noticeboards closed, with posts directed to the Dispute resolution noticeboard. This aspect of the trial would also last a month, and the main purpose of this trial is to assess what would things be like if these boards were permanently closed. I've proposed this idea as a) Content noticeboard deals with largely the same issues and b) WQA at the moment has some severe issues, as most matters that get sent there end up with parties slinging mud at each other. While I realise that this is quite a major change, I feel that giving this idea a shot is worth a go. The new noticeboard would have little effect if users could go to WQA and still have shouting matches. Conduct disputes at DRN would aim to be civilized, with while this not being "policed", will be enforced. There is a difference between expressing one's opinion and calling someone an asshat. Resolution at DRN for these sorts of disputes would either find quick resolution, or being referred to RFC/U. This way we can also keep discussions civilised and properly address conduct that has genuine issues, but nip in the bud "this user reverted my edit/I don't like them" type disputes that we too often see at WQA. While WQA is a high traffic noticeboard, it also is deeply flawed, and something needs to be done to still address valid conduct issues, but prevent the cesspit that WQA has become, and I propose this noticeboard, which would be monitored by mediators and "clerks" (I hate that word) who have demonstrated some experience in DR to ensure discussions don't get out of hand, offer advice and point people in the right direction in terms of the best avenue for further dispute resolution. At the end of this trial, results would be compared to what we found in the first trial, and a discussion would take place outlining the results of both trials and the best course of action moving forward.
 * 3) Disputes that do not belong at ANI would be closed, and redirected to DRN. While severe and urgent conduct issues do belong at ANI, like as I posted above, a lot that ends up at ANI does not belong there. While it may take some time to get a hang of what belongs at ANI in terms of disputes and what does not, a main aim of the board to reduce clogging up ANI with disputes that do not belong there. Additionally, disputes posted at incorrect forums (for example only conduct issues being presented at a mediation case) could be sent to DRN for clarification as to what the dispute is, and how to resolve it.
 * 4) Traffic at Editor_assistance/Requests that involves content and conduct disputes would also be directed to DRN. While a lower traffic noticeboard, this noticeboard is not really designed for dispute resolution, more so for assistance and questions about editing.

There are further details on the proposal further up the page, feel free to review that as well, as it has a bit more information as to the details of this proposal. The dispute resolution noticeboard is most designed to act as a mail sorter, resolve small issues on the spot, direct larger and more complex issues to the most appropriate forum for resolution, and ensure that discussions stay civilised and reasonable. Steven Zhang <sup style="color:#FFCC00;">The clock is ticking....  13:40, 4 June 2011 (UTC)


 * I will be implementing these changes, starting with a notice on Content noticeboard and WQA for the new noticeboard, as well as to ANI for dispute discussions to be sent to DRN. Will also update some DR pages to reflect this new option. Steven Zhang  <sup style="color:#FFCC00;">The clock is ticking....  15:33, 16 June 2011 (UTC)

Oppose Why is this here instead of the already open RFC? I've already commented there and don't care enough to reiterate myself.
 * Support - what an excellent idea. Without getting to arbcom-formal, perhaps a simple structural thing like "Your complain needs to be 300 words or less, and must include diffs of alleged behaviour" or something (with help given to people, I guess; maybe 'should include'), would help things get more expeditiously disposed of. Either way, I think this is a great idea--and anythingt hat lances the boil that is WQA would be great. Admin involvement needed, of course; one of WQA's failings is that there's no teeth, just people yelling. → ROUX   ₪  08:46, 5 June 2011 (UTC)
 * That's a really good idea. I think being a little more lax on content disputes would be OK. The main issues with content disputes at present are either the scope and details of the content dispute being unclear, or the dispute being posted at the wrong forum, so this noticeboard aims to help resolve small issues but point larger ones to the proper forum for resolution. That said, discussions on the page should be short, regardless of content or conduct issues. Perhaps a word limit could work, especially for conduct disputes. In regards to "teeth", I do see the need for some enforcement of reasonable discussion, as opposed to the yelling and bickering that goes on at WQA. Perhaps the mediators/"clerks" that patrol the page can do what they need to do to keep discussions civilised, failing that notify users they need to keep things civil etc, and failing that close the discussion and refer that matter to an RFC/U or ANI? I'm really not sure on this part. Steven Zhang  <sup style="color:#FFCC00;">The clock is ticking....  10:39, 5 June 2011 (UTC)
 * Support - As before. --  At am a  頭 10:09, 5 June 2011 (UTC)
 * Support - I had come her thinking, "not another bloody noticeboard", but saw the note about interim folding in two noticeboards whose briefs overlap and am cheered up immensely. I approached this problem from a different way and this is much better. Is it too late to add Third opinion to be marked (for the interim) historical? It is a fairly low traffic broad with a somewhat nebulous brief, whose roles I feel overlap with WQA and also RfC in some way? Casliber (talk · contribs) 10:36, 5 June 2011 (UTC)
 * Added to the list, I had been thinking about adding it and it is quite low traffic. Also added a clause about redirecting conduct and content disputes from Editor_assistance/Requests to here, as while somewhat a low traffic noticeboard, the issue we have here is disputes spread out everywhere. While I agree consolidating everything together is a bad idea, the main purpose of this board is to fix small issues, direct others to the best forum for resolution. If managed well, I can't see this board turning into another ANI. Steven Zhang  <sup style="color:#FFCC00;">The clock is ticking....  10:46, 5 June 2011 (UTC)
 * Support this seems like a good step forward for dispute resolution, hopefully it'll take some of the drama away from ANI. -- Eraserhead1 &lt;talk&gt; 10:56, 5 June 2011 (UTC)
 * Overall, I like this for the reasons I already stated above. I'm ambivalent, however, about going so far as trial-ing those other boards as historical. So long as the trial is clearly spelled out, in advance, as being brief, with a pre-defined end date, and leaves open the possibility of promptly re-opening the other boards, then I can Support, but I'd be very wary without that caveat. --Tryptofish (talk) 17:33, 5 June 2011 (UTC)
 * The noticeboards will have an initial trial of closure for say, two months, sufficient time to sort out any teething problems with the transition (One month might be insufficient) and yes, if the noticeboard turns out to be a total failure then we could re-open the old noticeboards. That's why there will be a trial, it's something that has never been done before so we need to see how it goes. I feel that if managed well this noticeboard could work quite well, but we have to give it a go and see first. Steven Zhang  <sup style="color:#FFCC00;">The clock is ticking....  22:00, 5 June 2011 (UTC)
 * Reading the discussion since my last comment, I now have to Oppose closing the other boards during the trial. Certainly, two months is way too long. I still support the overall idea of the trial, but not that aspect of it. I've thought carefully about the argument that we need to prevent users from forum-shopping from one place to another, but that is not a valid reason to close the existing boards. In fact, if one really wants to test the hypothesis that this new board will be an improvement—and testing that hypothesis is exactly what the trial should aspire to accomplish—then the best way to do that is to leave all existing boards open. That way, we can actually collect data on whether the new board does or does not accomplish what it proposes with respect to cutting down on subsequent forum-shopping, as well as data about whether cases that originate at the new board get resolved more efficiently than do cases that start out somewhere else. Closing the other boards skews the trial to give an advantage to the proposal, and we shouldn't do that. Depending on the outcome of the trial, there could subsequently be a separate RfC about closing other venues. --Tryptofish (talk) 19:22, 6 June 2011 (UTC
 * We could perhaps do a trial of all noticeboards that exist at present just encourage traffic to be posted at DRN, and offer it as an alternative to the existing noticeboards, and see how it goes. After this trial we could assess the results, then do a second trial with the noticeboards closed and discussions directed to DRN. This way we can gether data on the successes of the noticeboard without skweing results. I've updated the proposal accorcingly. Steven Zhang  <sup style="color:#FFCC00;">The clock is ticking....  01:33, 8 June 2011 (UTC)
 * Thanks, that update is a significant improvement. With the understanding that "phase two" of the trial will, of course, depend upon the results of "phase one", I am now comfortable Supporting the proposal in full. --Tryptofish (talk) 18:19, 8 June 2011 (UTC)
 * There's a fallacy here that the dispute issues WP has are due to lack of organization or can be fixed due to reorganization. Remember in the midst of WP-this and WP-that, there are but five pillars Read through this mess if you think organization, or admins instead of (mere) editors facilitating resolution is the issue.
 * The issue, vis-a-vis civility is lack of consensus. Without consensus, you can rearrange deck chairs all you want and it doesn't matter.
 * Clerk and procedures and all that are contrary to one of the pillars. The "cure" could easily be worse the problem.
 * Disputes occur because when a POV pushing editor uses suspect RS engages and edit wars, sometimes on BLP, with other editor(s) that they're insulting ... which dispute board does that go to? Gerardw (talk) 23:02, 5 June 2011 (UTC)
 * Hi Gerard. Thank you for your comments here. To respond to each of your points
 * I realise that there is an already open RFC, and I left comments there as well. This proposal came out of an idea I got from reviewing the RFC, mainly, a lot of disputes end up at ANI, or a miscellany of other boards that they don't belong at, and as a result it is somewhat harder to a) Keep track of issues and b) Ensure they're actually posted at the right forum. There are the five pillars, but most people that have a dispute won't go and read the five pillars, or at times even read WP:DR. Most just go to ANI for content, WQA for conduct. Both forums turn into a shouting match. While I realise this would be a major change, I feel the major consensus at present is that there is an issue, and it needs to be addressed. This is my proposed resolution.
 * Consensus will generally form from undertaking dispute resolution. Or it will not. Dispute resolution has to be tried first. But a major barrier to actually resolving disputes at times is incivility. It's quite hard to resolve the issues at hand if people are calling each other asshats. It works at MedCom, I feel it could work on this noticeboard.
 * I'm not a big fan of the clerks idea either. That said, ArbCom has clerks, who also enforce good conduct on discussion pages, and it seems to largely work. I'm not suggesting that "clerks" of this noticeboard will hold any official role, their task would only be to ensure discussions stay reasonable and focused on the issues at hand, and help direct complex queries to a targeted DR forum, ie an RFC, RFC/U or mediation.
 * That sort of issue would be posted to the noticeboard, a brief summary of the issues would be posted. It seems like that example you present is mainly a conduct issue, so an RFC/U would be the best avenue, and if edit warring was active, referred to 3RR. Once the conduct issues are resolved, the sources could be discussed on the article talk page. This noticeboard is not designed to resolve all disputes. It's designed to help discuss them to figure out exactly what is going on, resolve minor ones and recommend the best avenue to resolve larger, more complex ones. Steven Zhang  <sup style="color:#FFCC00;">The clock is ticking....  23:37, 5 June 2011 (UTC)


 * Conditional support: i) not replacing any existing boards to begin with; if it works well enough that other boards become defunct, great, but don't force it. ii) minimal formality. No "clerks" or requirements of diffs, etc. The main objective should be to help newcomers figure out how to handle a dispute (probably boilerplate responses will evolve as the WP:helpdesk has) and point them in the right direction. It's fine if it evolves a little more formality in response to need, but starting with that is a bad idea. Keep It Simple. Rd232 talk 23:20, 5 June 2011 (UTC)
 * Part of the issue with not moving traffic from other noticeboards is that if a user is not satisfied with a response at one noticeboard, they can simply go back to the other noticeboards and post the same issues all over again. I'm not suggesting that suggestions on DRN should be final, but a user shouldn't be allowed to bring up a trivial conduct dispute matter, be told it's not an issue, and have them raise it again on WQA. My points stand in regards to the idea of clerks. They're designed to assist and keep discussions focused. In content disputes, sure, diffs maybe not required. For conduct, important to have diffs. Otherwise people could post anything they like on the noticeboard without substantiating evidence. The new board is designed to reduce these sorts of reports, as I've listed above, as opposed to increasing them. Helping out new users is important, but this needs to be balanced with the potential for the board to be used by anyone that has a beef with another editor. Steven Zhang  <sup style="color:#FFCC00;">The clock is ticking....  00:16, 6 June 2011 (UTC)


 * Support Comment, Whilst the DRN is, at worst, a harmless idea and a best a brilliant one, closing WP:3O, even for a trial, is completely uncalled for and unneccessary. I don't believe there is, or has ever been, any consensus to scrap or even to substantially change it - 3O works, it's a great way of getting a dial-out consensus to a low visibility topic area and finding solutions to problems which couldn't really be aired without a fully fledged RFC. Volunteers there tend to be well informed and genuinely helpful (myself excluded of course) and the project operates with a remarkable level of efficiency (admittedly in part due to the low traffic). It would be a crying shame to shut it down for an unspecified trial period - if anything we should take this as an oppurtunity to redirect more traffic to 3O (or at least inform them of the discussion). I'm happy to support if we strike that off the proposal. Bob House 884 (talk) 23:37, 5 June 2011 (UTC)
 * Yeah, might try that avenue. Moved back to original idea without removing 3O. While 3O might be low traffic, I do realise now that it is an area that helps, so sure, happy to remove it from the proposal. Steven Zhang  <sup style="color:#FFCC00;">The clock is ticking....  00:16, 6 June 2011 (UTC)
 * Thanks. I do like the proposal - I'm sure we've all been in situations where we've had a dispute and just thought "where the heck do I post this?" and a board where you can just post any problem and have it sorted to the right noticeboard seems like a great idea. A possible problem may be keeping disputant from following the poster straight over to DRN and creating a shouting match before anyone can shift it - we can see if that materialises. One issue I'd be interested in seeing in the trial is the impact of having designated clerks deal with the 'cases' compared to just letting anybody do it. There are pros and cons for each but it's perhaps something that can be investigated. I am now happy to support the proposal. Regards, Bob House 884 (talk) 00:30, 6 June 2011 (UTC)
 * It wouldn't be formal, but users would need to demonstrate at least some knowledge or experience in the DR process in order to direct users to the proper forum. While this adds a layer of bureaucracy, it would also help ensure brand new users don't direct equally new users to mediation for a conduct dispute. I don't see major harm in letting anyone give advice and help, but actually closing a discussion (unless plainly unhelpful) and moving the dispute to different forum, would best be done by someone who is familiar with DR processes. Steven Zhang  <sup style="color:#FFCC00;">The clock is ticking....  00:55, 6 June 2011 (UTC)

Support. While (of course) not making every conflict go away, I really think this will help.TCO (talk) 23:19, 18 June 2011 (UTC)
 * Strong support. A great idea, as I've mentioned before, centralized and staffed by mediators and policy generalists.  No need to ditch 3O, but WQA and content noticeboard have seen their days come and go. Worth clarifying that DRN is not the place to blame everybody, but to lay out issues and see where discussion should focus. Ocaasit 03:26, 6 June 2011 (UTC)
 * Support. Seems reasonable and worth a try. I still think that comments should be segregated into Involved and Uninvolved sections and have the clerk be able to enforce this. A Quest For Knowledge (talk) 18:52, 7 June 2011 (UTC)
 * Support. The mess WQA sometimes becomes has been accurately described and such a noticeboard would hopefully be better "staffed" and provide results instead of fueling further uncivil dispute. Guoguo12  <font color="blue" size="1">(Talk)  19:46, 7 June 2011 (UTC)
 * Support as above. — James (Talk • Contribs) • 4:19pm • 06:19, 11 June 2011 (UTC)
 * Support A board specifically designated for drama? Yes please.  <font face="Old English Text MT">Swarm  <font face="old english text mt">X 21:16, 16 June 2011 (UTC)
 * Oppose We emphatically do not need more noticeboards. We emphatically do need more experienced editors staffing the noticeboards we have. Go to any one of our existing noticeboards and note the number of unanswered or perfunctorily answered requests. Note how the requests are formatted– often by new editors who are still figuring out how to edit, period, and certainly aren't going to read through the arcana of WP:Diff. If we need anything, it's a good way to move dispute threads around noticeboards, perhaps using a bot and a template that functions like Anomiebot on WP:PUF. But I don't see how more efficient shuttling is going to help with unanswered and unresolved disputes and queries. (Although if an editor is told enough times "This isn't the correct board for that. Post there instead." they may give up... which I suppose does solve part of the problem.) --Danger (talk) 04:53, 18 June 2011 (UTC)
 * To reply to your comments here, I realise that having "just another noticeboard" isn't going to help much. This board would after trials absorb some existing noticeboards, namely WQA, content noticeboard, as well as having content/conduct disputes from editor assistance and inappropriate content/conduct disputes from AN and ANI closed and directed to this new board. Some boards at present just don't work well, main example being WQA which often turns into a brawling pit. This new board is not just designed to point users to other forums, as if that was the only purpose of the board we could just use WP:DR instead. It's also designed to help resolve content and conduct disputes, but disputes that fall outside of the scope of the board (large or complex disputes) could be directed to an alternative forum. I realise that this idea is not fully fine tuned, but it will take some time to get the noticeboard working properly, and to feel out as to what can be solved on the spot, what can't, but if the idea is shot down before it's even attempted, we will never know if a change could be for the better. All I'm suggesting is we see how things go. Steven Zhang  <sup style="color:#FFCC00;">The clock is ticking....  12:35, 18 June 2011 (UTC)
 * Comment, per Danger. Noticeboard creep is an issue. Stuff at WP:BLPN does get ignored and that is suppose to be highly sensative stuff. So maybe review what is going on with noticeboards before going further with them. Regards, SunCreator (talk) 01:40, 23 June 2011 (UTC)


 * The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page, such as the current discussion page. No further edits should be made to this discussion.

Add link to new pages to sidebar
Hi, I propose that a link to Special:Newpages is added to the interaction section of the sidebar. We currently have recent changes linked, and I think it would be useful to compliment it with pages too. AD 19:19, 7 June 2011 (UTC)
 * I've wanted that for months; I think it would help attract more users to start NPP, which until we get the changes implemented we still badly need. The Blade of the Northern Lights ( 話して下さい ) 21:44, 7 June 2011 (UTC)
 * I wholeheartedly agree; when I used to do NPP, I installed a gadget that displayed new pages in the sidebar because typing it in the search bar every time was annoying. / ƒETCH COMMS  /  03:28, 8 June 2011 (UTC)
 * Couldn't you just put it on your watchlist? Peter jackson (talk) 14:50, 8 June 2011 (UTC)
 * You can't watchlist any of the Special:SpecialPages, nor edit them for that matter. Yoenit (talk) 14:55, 8 June 2011 (UTC)
 * That hadn't occurred to me. My list includes a category & some pages in project space, so I sort of vaguely assumed you could have anything. Peter jackson (talk) 15:21, 9 June 2011 (UTC)
 * Good idea. I'm so used now to tying WP:NEW and hitting the first link on that page that I don't really need it, but I would have appreciated it a few years back.--Fuhghettaboutit (talk) 22:41, 8 June 2011 (UTC)
 * Sounds like a great idea, to me. — <span style="font-family: Courier New, monospace ;font-style:italic">V = IR (Talk&thinsp;&bull;&thinsp;Contribs) 23:03, 8 June 2011 (UTC)
 * Yes, I think this would be useful. Killiondude (talk) 23:07, 8 June 2011 (UTC)
 * How many of the en.wp visitors are looking for special:NewPages ? I never visit it. Doubt my mom does either. The sidebar is precious space and it should be used for the most required or most useful links for ALL readers. I'm not really sure if NewPages qualifies for that. —Th e DJ (talk • contribs) 16:47, 9 June 2011 (UTC)
 * As User:Fuhghettaboutit mentioned above, new page patrollers rely on it extensively. One more link in the Interaction section isn't going to swamp the sidebar, and it's not as though Special:Newpages is soe off the wall page. — <span style="font-family: Courier New, monospace ;font-style:italic">V = IR (Talk&thinsp;&bull;&thinsp;Contribs) 16:55, 9 June 2011 (UTC)
 * I find the live feed in the sidebar perfectly adequate. See User:TheJosh/Scripts/NewPagePatrol.js. Kudpung กุดผึ้ง (talk) 17:07, 9 June 2011 (UTC)


 * @TheDJ: how many visitors, if any, are looking for Recentchanges, which has been there forever? AD 17:13, 9 June 2011 (UTC)
 * I have no reason to believe a reader would view RecentChanges over NewPages. They could both be presented. I think it would be intriguing to visitors to view new pages being created on Wikipedia. Just because they aren't looking for it now doesn't mean they won't click the link when presented with it. Killiondude (talk) 17:25, 9 June 2011 (UTC)
 * Recent changes is one thing, but let's not forget that the Wikipedia is read by even more people than those who edit and patrol it. The term New Pages is misleading: 80% of 'new pages' are the inapropriate ones that are going to be deleted - do we really want to draw the general readership's attention to them? Kudpung กุดผึ้ง (talk) 18:20, 9 June 2011 (UTC)
 * 80%? Where'd you get that from? Recent changes is designed for editors, not readers, and contains things like vandalism that we are drawing attention to. New pages is an accurate name, it says exactly what it is. I still don't see any argument against including it when we have Recentchanges there. AD 18:51, 9 June 2011 (UTC)
 * You mean "change bad" is not a good argument here? Say it ain't so! ;) — <span style="font-family: Courier New, monospace ;font-style:italic">V = IR (Talk&thinsp;&bull;&thinsp;Contribs) 20:09, 9 June 2011 (UTC)


 * Aiken, we've done some work on determining what happens to pages, and ~80% of the mainspace pages written by new editors end up deleted within ~6 months (most within a week). WhatamIdoing (talk) 01:52, 10 June 2011 (UTC)
 * Doesn't surprise me at all, but how good the pages are isn't relevant to whether or not it would make a useful link - which it undoubtedly would. AD 21:51, 10 June 2011 (UTC)
 * I made a .js script for that. It's in userspace.   EBE123  talkContribs 20:01, 14 June 2011 (UTC)
 * I still don't see why it can't be the default. AD 12:59, 18 June 2011 (UTC)

I would like a link New Pages to be added to the sidebar. I agree with this proposal.James500 (talk) 08:15, 23 June 2011 (UTC)
 * Oppose, there's probably already too much stuff in the sidebar for the casual reader. Recent changes is enough (and a standard link on most wikis), and has the new page link on top. For editors, it is easy to add New pages links to their userpages. —Kusma (t·c) 08:28, 23 June 2011 (UTC)
 * If your computer was as slow as mine is, you would realise why I don't consider the link to new pages on my user page to be of much practical use. James500 (talk) 06:13, 26 June 2011 (UTC)

Suggestion - How about allowing users to enable a link to Special:NewPages by using the gadgets section of Special:Preferences. James500 (talk) 06:25, 26 June 2011 (UTC)

Block log annotation
Following a recent Idea Lab discussion, there is now a means to annotate the "block a user" page (eg Special:Block/Rd232), by creating a page with a specific name in the relevant user's userspace. The idea is that this page would be fully protected and could be used by admins to provide clarifying links and notes for future reference. This could be particularly useful for warnings, edit restrictions, exonerations, and other things that might be relevant. Note: at present the code (at MediaWiki:Blockiptext) only displays the annotation page if it exists. This could be changed to provide a link to create the page, if the approach is thought desirable. PS If I'm correct in thinking admins can create pages protected by the MediaWiki:Titleblacklist, that could be used to fully protect this type of page, including against creation by non-admins. PPS Current downside would be not showing the annotation page on the user's block log (i.e. Special:Log), but that's less important, and possibly fixable with JavaScript, or else in software (cf ). Rd232 talk 21:50, 9 June 2011 (UTC)
 * Perhaps a useful idea, but on Monobook it forces the sidebar at least one complete pagelength down (when I visit Special:Block/Rd232). Killiondude (talk) 21:59, 9 June 2011 (UTC)
 * That was a template issue (from cot/cob); I've fixed it temporarily by removing the template. I wanted the transcluded annotation page hatted though so as not to push the log entries too far down the page. Perhaps someone more template-techy can fix it. Rd232 talk 22:21, 9 June 2011 (UTC)
 * I think this is a good idea. The block log (and all logs, for that matter) can't have links to specific versions of pages, spercific deleted pages, or log entries of specific users or pages. עוד מישהו Od Mishehu 18:39, 14 June 2011 (UTC)
 * Yes they can. Copy/paste works wonders. The problem was the character limit. Killiondude (talk) 18:45, 14 June 2011 (UTC)
 * Should non-admins be able to view the page? -- Eraserhead1 &lt;talk&gt; 19:09, 20 June 2011 (UTC)
 * ...no. — <span style="font-family: Courier New, monospace ;font-style:italic">V = IR (Talk&thinsp;&bull;&thinsp;Contribs) 22:01, 20 June 2011 (UTC)
 * Yes, for transparency. The aim is a clearer understanding of a user's block history; there's no reason to limit that understanding to admins. (In any case, AFAIK there's no current way to enforce admins-only viewing a page.) Rd232 public talk 00:13, 26 June 2011 (UTC)
 * Um... it;s already inaccessable to non-admins. It's a page in the Special namespace, which requires sysop permissions to view or edit. — <span style="font-family: Courier New, monospace ;font-style:italic">V = IR (Talk&thinsp;&bull;&thinsp;Contribs) 01:39, 26 June 2011 (UTC)
 * Well I guess it wasn't clear enough from the above, but the Special:Block bit is just loading a page from somewhere else, for convenience. That somewhere else is a page in the relevant user's userspace Special:Mypage/Blocklogannotation (which is why I suggested using Titleblacklist to prevent creation, so users can't go around creating these things willynilly; and then when the page is created by an admin it can be protected). Rd232 public talk 02:15, 26 June 2011 (UTC)

Page moves from userspace
Proposal: allow editors the option to suppress the creation of a redirect when moving a page out of userspace into mainspace (which would normally be a userspace draft-type page). That's probably harmless, is a common task, and prevents useless cross-namespace redirects. It's also a task which will likely become more common when the limitations on non-autoconfirmed users creating articles goes live, since many will be creating userspace drafts instead. Rd232 talk 02:20, 6 June 2011 (UTC)
 * I know nothing about the technicalities of this while still not allowing suppression of redirects with other page moves. If it is technically feasible though, I would support it. It seems quite silly for people to have to request deletion of a cross namespace redirect that they didn't want in the first place. Lady  of  Shalott  03:38, 6 June 2011 (UTC)
 * It's a good idea, but it widens a loophole. Moving pages from userspace means that any editor can easily create an article and get around WP:NPP. Suppressing redirects would make it less likely that an admin is going to come across it. I don't know if that's a reason to vote it down, I'm just pointing it out. ▫  Johnny Mr Nin ja  04:38, 6 June 2011 (UTC)
 * "Moving pages from userspace" existed for centuries, well before NPP. In my past experience, existence or deletion of user-to-mainspace redirects did not affect visibility of articles in any way. There were, however, two drawbacks: (a) no NPP = less exposure (b) it's easy to mess up by editing mainspace article thinking that it's one's userspace draft. Deletion of a redirect removes the latter, but it's no big deal really, and then anyone who ran into redirect-related troubles will soon learn to db-user it, won't they? NVO (talk) 05:03, 6 June 2011 (UTC)
 * Well that just points up an obvious flaw in NPP! Moves from userspace to mainspace ought to show up at NPP. Shall we make that a separate proposal? Rd232 talk 12:04, 6 June 2011 (UTC)
 * It's a bug in bugzilla, but I don't have the bugnumber right now. Anyway, if you find it, vote for it in bugzilla! Fram (talk) 12:14, 6 June 2011 (UTC)
 * Ah yes: . I've voted for it. Rd232 talk 13:06, 6 June 2011 (UTC)
 * And I've just created to cover redirects - a similar NPP loophole. Rd232 talk 16:28, 6 June 2011 (UTC)
 * I brought up that exact problem in the idea lab (here) a few days ago but no-one has responded so far. The same issue also exists for articles expanded from redirects. doom gaze   (talk)  12:15, 6 June 2011 (UTC)

Back to the question: if/when the NPP loophole for moves from userspace is fixed, do we want this to happen? Rd232 talk 10:26, 9 June 2011 (UTC)
 * We have a proposal for a pagemover group. It may be useful.   EBE123  talkContribs 19:59, 14 June 2011 (UTC)


 * I wasn't aware that  new page moves from user to  mainspace don't  feed into  NPP. I thinks it's absolutely  essential they  should, because if this loophole gets more widely  known, it  will  be massively  exploited. Not by  the vandals, hoaxers, and attack pages, which  are more spontaneous, but  by  the hard nosed SEO agents, corporate spammers, soccer fans, garage bands, and autobiographers promoting  their first  book or candidacy  to  the village council. Kudpung กุดผึ้ง (talk) 07:40, 19 June 2011 (UTC)

I question whether it is a useless cross-domain redirect. If the content existed in userspace, and now exists in mainspace, someone may have linked to the userspace version, so those links should redirect to mainspace. —Tom Morris (talk) 19:13, 27 June 2011 (UTC)
 * The only links that its important to maintain are those in the mainspace, and there are no mainspace articles linking to userspace articles, any links that are added are removed on a weekly basis (From Database reports/Articles containing links to the user space)--<font color="Blue">Jac <font color="Green">16888 Talk 19:19, 27 June 2011 (UTC)
 * You misunderstand. Links from outside Wikipedia to the user version. —Tom Morris (talk) 21:34, 27 June 2011 (UTC)

"All other namespace" tab in dropdowns
Currently, dropdown menus like the ones in "user contribution" pages allow you to search by individual namespace of by all namespaces overall. With many users, more than half of user contributions are in the article namespace. Is it possible to add an item in the dropdown menu allowing you to - at one go - search all contributions other than those in the article space? This sort of addition would also be useful in the similar dropdown menus in "new pages", "what links here", "related changes", etc. Grutness...<small style="color:#008822;">wha?  02:13, 26 June 2011 (UTC)
 * I think this is a good idea; it's been around a while. The relevant bug is, from June 2008; it has 4 duplicates. Voting for it can't do any harm.... Rd232 public talk 11:17, 26 June 2011 (UTC)

Category →'s at the bottom of articles
A major pet peeve of mine are laundry lists. Oh boy do I hate them! Why is it that so many articles are categorized inside categories to which they are also categorized? To look at what should be done, here is a good example: Category:Rivers. So how do we get people to not overcategorize? Imagine the following scheme at the bottom of each categorized page:

Categories:
 * Contents → Articles → Main topic classifications → Geography → Places → Fluvial landforms → Rivers → Rivers by continent → Rivers of Europe → Rivers of Albania
 * Contents → Articles → Main topic classifications → Geography → Geography-related lists → Lists by continent → Europe-related lists → Albania-related lists

Ideally, the shortest path between the top category Category:Contents and any category selected should be chosen.

And of course, in practice, only the first parent level should be shown. Example:

Categories: Rivers of Europe → Rivers of Albania | Europe-related lists → Albania-related lists

In general, only one parent level need be shown.

This would prevent people from over-categorizing articles. This would also make for a much nicer and functional outline to be the pervasive norm.

Signed, a laundry list hater, <span style="display:inline-block; margin-bottom:-0.3em; vertical-align:; line-height:1.2em; font-size:85%; text-align:;">siNkarma86—Expert Sectioneer of Wikipedia undefined 03:24, 27 June 2011 (UTC)


 * Comment This would be technically impractical: Graph traversal is generally a hard thing to do right and would require significant work from MediaWiki developers to implement and significant system resources. More detailed reasoning than "Oh boy do I hate them!" is needed to justify the technical and human resources needed to implement this. —Tom Morris (talk) 10:20, 27 June 2011 (UTC)
 * Comment: wouldn't it be more practical to come at the problem more directly? The issue is page or category A appearing in both category X as well as in category Y, the parent of X. (Sometimes this behaviour is desirable, but usually it isn't.) Perhaps HotCat could somehow flag such cases when a HotCat user visits A. Rd232 public talk 10:59, 27 June 2011 (UTC)
 * As long as users were made very aware of the cases when that behaviour is desirable (such as the much-discussed and occasionally understood eponymous categories question).--Kotniski (talk) 11:14, 27 June 2011 (UTC)
 * Are they identified in some way that HotCat could feasibly do that? Rd232 public talk 21:49, 28 June 2011 (UTC)

Removing edit conflict notice from the sandbox
I am not sure that there is the technology to do this, but here goes!! Tonight (June 28 2011) I had been trying out citation methods on Sandbox, and got the message - "Some one else has been starting to edit this since you began, resulting in an edit conflict". My plea is for there to be a removal - if this is technologically possible  - of the edit conflict tag from the sandbox, as surely, it is more than likely that there will be several people editing there simultaneously. ACEOREVIVED (talk) 19:18, 28 June 2011 (UTC)

In fact, I remember some one raised the question of edit conflicts some time ago earlier this year (2011) - did anything come of it? ACEOREVIVED (talk) 19:19, 28 June 2011 (UTC)
 * I don't know about that, by I do know that reasonably experienced users needn't be using the main WP sandbox. I've knocked up a userbox Mysandbox which makes it easy to create a user subpage sandbox. (This could probably be linked from some relevant help pages etc, if anyone can think of where.) PS I did a while ago suggest using Javascript to give every user easy access to their own subpage sandbox, by adding an extra tab on their user and user talk page. Rd232 public talk 21:38, 28 June 2011 (UTC)

Thank you for that - giving people the right to use their own personal sandboxes on their own userpages seems a marvellous idea! ACEOREVIVED (talk) 23:08, 28 June 2011 (UTC)

Page mover
<div class="boilerplate metadata discussion-archived" style="background-color: #f5f3ef; margin: 2em 0 0 0; padding: 0 10px 0 10px; border: 1px solid #AAAAAA;">
 * The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.
 * There may be a rough consensus for Sven's counter-proposal, but realistically speaking more editors need to provide their opinions before any action is taken. Ed [talk] [majestic titan] 08:24, 30 June 2011 (UTC)

<span id="rfc_C4B9A2F" > <span id="rfc_A6D3672" > (moved to village pump to generate more consensus, please continue the discussion there.) This is a proposal for a new user right called the. Propose that this new user right would be able to move pages that have been move protected and the ability to suppress redirects. Those are pretty much the main idea I have but it was suggested that the  user right be include which is something i am not totally for. I would also like for  to be included which would give users with the pagemover user right to move pages with their associated subpages. As with any user right, there must be baseline requirements. What I propose is that the requirements for the pagemover right is that: Let me just brief you of the benefits of having a pagemover. It would make the job of administrators a little easier by having someone else to userfy pages. It would also give users other than administrators the exclusive right of moving pages with their subpages. I myself am in opposition to the idea of pagemovers having the ability to move files as there are already two groups that can do that and their is no need for three. This could be done in a trial (Of Lord, the evil Trial word comes back) to see if it is a good idea or not. And with that I leave it to the community.<font face="times new roman"> maucho eagle   (c) 03:31, 21 May 2011 (UTC)
 * You must have some formal experience with moving pages.
 * You must have at least 500 edits.
 * At least 1 month experience


 * While I'm generally supportive, let me ask you the question that I foresee will ultimately shoot this proposal down. If someone can be trusted enough to be given this user right, why can't they be trusted to be an administrator? — <span style="font-family: Courier New, monospace ;font-style:italic">V = IR (Talk&thinsp;&bull;&thinsp;Contribs) 03:52, 21 May 2011 (UTC)
 * Alot of respected users of the community were completely shot out of the water (eg My76Strat, Ancient Apparition and Chzz) and this sort of user right would touch the things that admins do without you actually becoming an admin. <font face="times new roman"> maucho eagle   (c) 16:02, 21 May 2011 (UTC)


 * Why is this needed? The number of move-protected pages that need to be moved on any given day is vanishingly small; there's not a huge backlog of such pages waiting around to be moved.  Why does a special user right need to be granted where "ask an admin to do it" would work just as well?  -- Jayron  32  04:17, 21 May 2011 (UTC)
 * As I mentioned above, another user right to performs such tasks could take a load off of administrators. And the proposal above is not only moving protected pages it also can move pages with there associated subpages and help with userfies. It always helps to have someone else to do a task, such as userfying, when you come accross pages that need to be userfied almost every day. In my experience with new page patrol, I see them alot. <font face="times new roman"> maucho eagle   (c) 15:55, 21 May 2011 (UTC)
 * There isn't much of a load to take off though. Most pagemoves that require an admin aren't moves of protected pages, they're moves over an existing page; completing these moves requires the ability to delete pages. Pages with subpages are typically established pages (subpages are most frequently used for discussion archives) and are rarely moved. Userfication is really the only one done on a regular basis, but is it that difficult to just move it yourself and put a speedy tag on the redirect? Mr.Z-man 16:59, 21 May 2011 (UTC)


 * Weak Support - Although I think that there is very little need for this I can see it could be useful. As one user who has basically lost interest in attempting a run through the gauntlet to become an administrator and who considers the process of choosing one completely and utterly broken (although good folks do become admins so no disrespect intended to them) I think this is a good step towards decoupling the various roles an admin does. In my experience most admins deal in specific things anyway and few use the whole suoite of tools so this would allow those interested in moving pages to do so. --Kumioko (talk) 13:03, 2 June 2011 (UTC)

Counter-proposal: Do not allow the right to move move-protected pages, only allow, and up the requirements
This version would only allow suppressredirect, as moving protected pages seems like a bad idea. The requirements would be:


 * You must have a demonstrate history of constructive moves.
 * You must have at least 3 months of experience.
 * You cannot have a history of using moves to vandalize or content war pages.
 * You should have a communicable reason for wanting the right.

As one of the more prolific filemovers (currently knee deep in a list of 3000 files that all have to be renamed) this user right would allow me to do my job better, and would save the admins that I work with a great deal of time. If it's never been used in an article, there's no need to keep as a redirect a page named File:DSC01234.jpg or File:IMG02468.jpg when the image itself has been moved to something that's more descriptive. There are plenty of other people that work in plenty of other areas that could all benefit from this.

I do not, however, see any reason why allowing non-admins to move a move protected page around is a good idea. For the very tiny number of instances where it would be constructive, an admin is just a template posting or IRC chat away.

Thoughts?  S ven M anguard  Wha?  20:45, 27 May 2011 (UTC)
 * What are your thoughts on the  right? <font face="times new roman"> maucho  eagle   (c) 20:56, 27 May 2011 (UTC)
 * I see all three components as having the potential for chaos should a vandal get a hold of the right, however from personal experience (someone moved my userpage to the mainspace once) I can tell you that an admin can fix straight up move vandalism in less than 30 seconds. I see no reason why it would take any longer to fix move vandalism if the subpages are also taken for a ride. The only component I specificly object to giving out as a right is the ability to move the move-protected pages. Especially when we get into template dependencies and trasnclusions, this could cause serious, widespread damage with a minimal amount of vandalism actions, and is much harder to clean up.
 * To some degree, the other issue is that I fully expect admins to grant rights to people that in no way deserve those rights, either in willful disregard for the guidelines, or because they don't care enough to even check the guidelines. I saw it with filemover. I'm not going to pretend that this isn't going to be given out like candy to both trustworthy people that will never use the right and untrustworthy people that just keep asking until they get lucky.  S ven M anguard   Wha?  22:21, 27 May 2011 (UTC)

One possibility which might be useful is to allow editors to suppress the creation of a redirect when moving a (userspace draft) page out of their own userspace into mainspace. That's probably harmless, is a common task, and prevents useless cross-namespace redirects. This would require a software change of some sort, but once done it wouldn't require any management. Rd232 talk 15:18, 28 May 2011 (UTC)
 * Oppose. "suppress-redirect" is a mere convenience for admins, to save having to create a redirect page as part of a move and then delete it after when it's not needed. Particularly for admins doing a lot of a certain type of work, it saves quite a bit of time, and is a bit neater. I'm sceptical about the proliferation of user rights generally (given the misuse issues Sven mentions above), and this one just doesn't seem worth the hassle of managing, and the associated risks. Risks being, most notably, that abuses of suppress-redirect can make inappropriate page moves (or even page move vandalism) harder to catch. Users can just CSD the redirect. Moving subpages is needed less often, and probably carries less risk, but again it doesn't seem worth the trouble to separate it out, especially if it doesn't come with suppress-redirect. Rd232 talk 10:04, 28 May 2011 (UTC)
 * Moving subpages carries less risk? That's a good one. Some rather nasty pagemove vandals have been known to use that option on things such as userpages with lots of subpages, and are thus able to vandalize upwards of twenty pages within a minute. Moving subpages is a right which is hardly used anyways, and has a massive potential for abuse. Ajraddatz (Talk) 14:59, 28 May 2011 (UTC)
 * Fair enough. I did say probably... I was thinking it's no harder to undo than ordinary pagemove vandalism, and the subpages (especially of non-move-protected pages) aren't normally of particular prominence. Rd232 talk 15:12, 28 May 2011 (UTC)
 * Much harder to revert, considering that most people don't recognize it as that type of vandalism, and revert each one separately - then users without the noratelimit right get stuck by a rate limit after two reverts. Ajraddatz (Talk) 03:45, 31 May 2011 (UTC)
 * If this was going to be devolved from admins then it sounds like one of the least controversial accesses. move without creating a redirect, and move subpages, override title black list, and no rate limit on moves sounds like a reasonable package to grant as a right. However there must be some limit to the number of different rights before it just gets too confusing for people to understand. Graeme Bartlett (talk) 10:01, 31 May 2011 (UTC)
 * Support this would make files work so much better. --Guerillero &#124; My Talk  21:45, 6 June 2011 (UTC)
 * Support I'm not normally one to support new userrights, but for those of you who don't do NPP you'd be shocked at the absolutely horrific page titles we come across sometimes. I've got hundreds of page moves in my log, and a good number of them are 1. names like BANURI VILLAGE (HIMACHAL PRADESH) from non-native speakers whose often horrendously mangled English isn't confined to the article body and/or 2. titles with missing or extra spaces.  This would make it far more efficient; it wouldn't entirely do away with R3, as it seems many NPPers are not very experienced, and sometimes people create redirects that don't quite meet G3 but are clearly implausible anyways (Media shitstorm being created as a redirect to Media circus or Aught-six being redirected to 1906, for instance), but it would definitely help streamline NPP for those of us who know what they're doing. The Blade of the Northern Lights  ( 話して下さい ) 04:22, 7 June 2011 (UTC)
 * Support Although I might also suggest simply adding this to the filemover user right, as file redirects should be deleted anyway. Alpha Quadrant    talk    22:44, 9 June 2011 (UTC)
 * Support per Alpha Quadrant. @Alpha Quadrant: not all redirects are invalid though, common misnomers and so forth are worth retaining. — James (Talk • Contribs) • 4:00pm • 06:00, 11 June 2011 (UTC)

Another counter-proposal
We allow, and. We also merge it with.


 * At least 2000 edits;
 * Knows all applicable policies;
 * Good reason for wanting the right;
 * No vandalism or edit-war from past 2 months history.

Thoughts? EBE123 talkContribs 18:21, 14 June 2011 (UTC)
 * I don't know; suppress-redirect and move-subpages don't entail quite the same things. I'd certainly qualify for the first two, but I do essentially no image work so I wouldn't be good for the third.  On NPP, I could definitely use the ability to move without a redirect, for reasons I detailed above; I don't need the ability to move files.  But perhaps I'm the exception; if that proves to be true, it would make more sense to combine them. The Blade of the Northern Lights  ( 話して下さい ) 01:17, 15 June 2011 (UTC)
 * OK, I am lost; why, would  be needed with File mover? Kind lost in space there. — Croisés Majestic (sur nous mars) 01:37, 15 June 2011 (UTC)
 * Ha haha haa, I press the stop button in my browser and edit conflicted my-self. — Croisés Majestic (sur nous mars) 01:40, 15 June 2011 (UTC)


 * Comment I can't really think of a reason a non-bureaucrat would need . The   flag is mainly used in user renames and renaming Templates or WikiProjects. There isn't really a backlog in this area either, as normal users can still move sub-pages one by one.  Alpha Quadrant    talk    04:44, 15 June 2011 (UTC)
 * It would be to save lots of time. Did you see my move log?  There is a reason that screams out loud!   EBE123  talkContribs 20:42, 15 June 2011 (UTC)
 * Point taken. Support either proposal. Alpha Quadrant    talk    06:38, 17 June 2011 (UTC)

Question Are these rights, or any others, ones that appropriate admins could just give on a case-by-case basis? If it's just a matter of a few people working on particular tasks that would be facilitated by these kinds of rights, maybe an admin or some other appropriate person could simply bestow them. this may require some sort of software change, though-- I don't know how rights and abilities are handled software-side, so I don't know if it's possible to make someone and editor with extra powers. Wabbott9 (talk) 02:15, 22 June 2011 (UTC)
 * Oppose all We do not need more new userflags. Either we add userrights to existing flags, or we leave them to the admins like it is currently. Otherwise, we create more fodder for the rights-hungry annoyances that haven't be blocked yet. This is a particularly trivial userright (suppressredirect) that should either go to all, say, rollbackers (as I think I proposed last year), or stay with the sysops. / ƒETCH COMMS  /  01:22, 22 June 2011 (UTC)
 * No, we can't give out  or anything like that unless we create a new flag for it, which is essentially what this proposal is for. / ƒETCH  COMMS  /  16:14, 22 June 2011 (UTC)
 * I understand. Oh, well. worth asking, to see if this sort of thing could be done less formally, but it looks like it would be just about the same. Wabbott9 (talk) 19:05, 22 June 2011 (UTC)


 * Support While I don't agree with the limits, file-redirect cleanup is really annoying, this would speed things up. — James (Talk • Contribs) • 3:06pm • 05:06, 26 June 2011 (UTC)
 * The above discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.

Install extension Pchart4mw - for charts drawing
Since we only have the ''' doesn't apply).  cera  don  21:08, 3 July 2011 (UTC)
 * Comment I think the dispute resolution noticeboard is working quite well. Disputes seem to be getting resolved there. I think you do actually need ANI to handle matters involving admins misbehaving, but given in my experience ANI fails to do that so maybe getting rid of it is OK. I'd still like to keep the dispute resolution noticeboard though. -- Eraserhead1 &lt;talk&gt; 21:18, 3 July 2011 (UTC)
 * Comment Part of the problem to why stuff is still going to ANI that doesn't belong there is a) There's no notice at the top of the page to indicate there's an alternative place to take the issues and b) Issues which don't belong at ANI are being discussed there anyway, because no one is doing anything about these threads. It would take some admin enforcement, namely, closing threads that don't belong at ANI and pointing them to other forums, such as DRN. Otherwise, nothing is going to change. Steven Zhang  <sup style="color:#FFCC00;">The clock is ticking....  21:51, 3 July 2011 (UTC)
 * I would say that rather than just closing the threads, that the admins should move the conversation to the appropriate forum, and notify the poster that they have done so. But otherwise, I agree with you. The only way the problem is going to be fixed is to a) provide an alternative and b) make sure that people use it. ~ Mesoderm (talk) 22:06, 3 July 2011 (UTC)


 * Oppose because the Village Pumps are the actual community forums. 'WP:Community forum' should redirect to WP:VP.  ANI is supposed to be for incidents (not chat, questions, or discussion) that require attention specifically from admins (not everyone).  Renaming is only going to make it harder for people to figure out the purpose of that page.  WhatamIdoing (talk) 23:48, 3 July 2011 (UTC)
 * Oppose pretty much for the same reason as WhatamIdoing - we need more streamlining and organising of boards, and clarifying and delineating what their function. This goes in the opposite direction. Sorry. I'd support of merging some boards though. Casliber (talk · contribs) 00:06, 4 July 2011 (UTC)


 * Oppose also as per WhatamIdoing. We need to  stress more clearly  across the site that  ANI  is specifically  for issues that  require admin  comment  and intervention. The current  name of the noticeboard is the most  apt. We  should be more bold about  redirecting  the plaintifs to a more appropriate noticeboard. Kudpung กุดผึ้ง (talk) 13:54, 4 July 2011 (UTC)

Limit the Wikilove feature to specific user groups
I'm sure that this should be disallowed for non-autoconfirmed users, and only in an opt-in basis for non-admins, since Wikipedia isn't a social networking site.Jasper Deng (talk) 22:02, 30 June 2011 (UTC)


 * Oh, lighten up... Next thing you know we can't even say 'hello' anymore. <span style="font-family:'Trebuchet MS',sans-serif"> — Edokter  ( talk ) — 22:25, 30 June 2011 (UTC)


 * Actually I think Jasper's right, and it's only a matter of time before you see why. Malleus Fatuorum 22:28, 30 June 2011 (UTC)


 * We may not a be social network, but we are a community. I don't believe in blocking features for beginning editors, especially those that promote collaboration. <span style="font-family:'Trebuchet MS',sans-serif"> — Edokter  ( talk ) — 22:35, 30 June 2011 (UTC)


 * That's not what you'll be blocking Edoktor; have you looked at the "make your own" option? Malleus Fatuorum 22:48, 30 June 2011 (UTC)
 * Yes, I suspect we'll come to rue that one.-- SPhilbrick  T  01:49, 1 July 2011 (UTC)
 * That was a seriously Californian off-the-wall crazy idea. I quite like it though, better than all the gooey "love" stuff. Malleus Fatuorum 01:58, 1 July 2011 (UTC)
 * Obviously jealous of California MF? The 7th largest economy in the world.  Almost all development and manufacturing of anything important in medical devices, telecommunications, social networking (though I might consider it a negative), Wikipedia (OK, another negative), automobile design, venture capital, computer devices, and gorgeous, intelligent women.  In other words, without California, the US would be a backwards, Republican-run, anti-science, fascist religious state, pretty much laughed at by Californians.  And we wouldn't let you have our excellent pot.   Orange Marlin  Talk• Contributions 03:09, 1 July 2011 (UTC)
 * Why would anyone be jealous of California? A state that appears to have more lawyers per square mile than any other place on Earth? Malleus Fatuorum 03:14, 1 July 2011 (UTC)
 * Actually, it's 12th on the list of US states for active attorneys per square mile, being preceded (in order) by New Jersey, Massachusetts, Connecticut, New York, Rhode Island, Maryland, Delaware, Illinois, Pennsylvania and Florida. Additionally, the District of Columbia and Puerto Rico both have far more attorneys per square mile than California.  WhatamIdoing (talk) 14:51, 2 July 2011 (UTC)


 * The reason I opened this thread was because of some recent trolling incidents with things related to Wikilove (like this IP). Besides, many non-autoconfirmed users don't know the meanings of barnstars, etc. Therefore, I think it's reasonable if non-autoconfirmed users can opt in to Wikilove by applying for Confirmed status. It's too risky to allow IPs to opt in.


 * "...can we all get along?" Bus stop (talk) 04:17, 1 July 2011 (UTC)
 * I'd like to point out that Orangemarlin is wrong about, well just about everything to do with California. Not only is Wikipedia NOT from California, worse- it's from Florida; the state of NY has developed more medical devices (in particular the Glens Falls, New York area) than California, the largest private sector construction project in the US is in Malta, New York eg-the newest most advanced chip fab in the US being developed by AMD; Sematech the international consortium of computer chip companies is in Albany, New York; and of course Wall Street, Madison Ave, and the news headquarters of all major networks is in the City of New York (which is twice the population of California's largest city, while being in a smaller geographic boundary). Tech Valley in Upstate NY is in a better healthier economic condition than Silicon Valley. Oh, yea and California has a bigger budget problem than just about any other state. Let California go its own way.Camelbinky (talk) 01:04, 6 July 2011 (UTC)

Opt out?
How about a way to opt out of receiving these unwanted advances? Apparently there's a way to opt out of the button to give these silly notices, but recipients has no such option. Short Brigade Harvester Boris (talk) 02:14, 1 July 2011 (UTC)


 * IMO the opt-out checkbox should block both sending and receiving -- it's highly unlikely that someone would opt out from sending but want to receive. For users who've disabled it, we could visibly disable the heart symbol to other users to make it clear what's going on.


 * I think it's inevitable that a small but vocal faction of users will dislike this feature, and this is a simple way to mitigate conflict about it.--Eloquence* 02:54, 1 July 2011 (UTC)
 * Well, if Wikipedia is anything like Facebook, then they will opt us in automatically, and make it impossible to figure out how to opt out! :)   Orange Marlin  Talk• Contributions 03:10, 1 July 2011 (UTC)


 * It is impossible to truly opt out. It is possible to make the button not appear to a user that has opted out; I can think of one fairly simple way that would work. But since anyone could manually type out any message they want I don't see a point in opting out of receiving the messages. Removing the button to send, on the other hand, could be useful and indeed I have done that for myself. Prodego  <sup style="color:darkgreen;">talk  03:26, 1 July 2011 (UTC)


 * I think removing the button for opted-out users is good enough, since most of the Wikilove materials are hard to find for users who aren't familiar with what they are.Jasper Deng (talk) 04:09, 1 July 2011 (UTC)


 * It sounds like people also want an automated reply. I guess appropriate ones might be to
 * A rabbit icon 'I freeze like a rabbit when given wikilove'
 * A boiled rabbit icon 'I get obsessed when given wikilove, look out'
 * A rabbit pie 'We can share a meal and be friends'
 * I'm sure the Wikipedia software could look for a list of automated responses associated with a user and pick out the appropriate one for edits about to make to a users page so these could be shown in the preview. Hmm if they change their edit correspondingly then a different message might come out - one could almost work in a whole Eliza type conversation here ;-) Dmcq (talk) 07:58, 1 July 2011 (UTC)

Proposals for closing projects/Closure of Old English Wikipedia
Per the new Meta:Closing projects policy, I have proposed Ang Wikipedia, the Old English Wikipedia, for deletion. My reasons are numerous, but the main issue is that information on a dead language makes sense, information in a dead language does not. Please voice any opinion at Meta:Proposals for closing projects/Closure of Old English Wikipedia. ▫  Johnny Mr Nin ja  06:10, 4 July 2011 (UTC)
 * why are you posting this here? Choyoołʼįįhí:Seb az86556 > haneʼ 09:29, 4 July 2011 (UTC)
 * Perhaps because both this project and that project's languages include the word "English" in them. Just a shot in the dark. Killiondude (talk) 06:37, 5 July 2011 (UTC)

So would you then wish to close down the Wikipedias in Latin, Sanskrit or Old Church Slavonic? I respect your view, but I disagree - I think it is of interest to keep these Wikipedias. ACEOREVIVED (talk) 14:30, 5 July 2011 (UTC)


 * "Wikipedia is not a junkyard", but to get to a different language you actually have to look for that language (i.e. it is not in the way), so there is no harm in keeping it and, contrary to what is said above, one it is actually useful in learning the language. Just because Mitsubishi, Toyota and other car companies have no qualms in butchering Latin (viz. plural of Prius), it does not mean dead languages are useless waste of a dozen megabytes out of terabytes. --Squidonius (talk) 18:54, 5 July 2011 (UTC)

Why do you not say "Anglo-Saxon Wikipedia" which is the name given to this Wikipedia at List of Wikipedias?ACEOREVIVED (talk) 19:54, 5 July 2011 (UTC)


 * For discussion about this proposal, follow the link above. Writing here will just ensure that nobody sees your comments. Jafeluv (talk) 20:12, 5 July 2011 (UTC)

Revisiting the proposal to give bureaucrats the technical ability to remove the admin bit

 * Retitled from "Revisiting Requests for adminship/Bureaucrat Unchecking"

Following the successful RFC at Village pump (proposals)/suspend sysop rights of inactive admins, some editors (including myself) are wondering whether we should revisit the Requests for adminship/Bureaucrat Unchecking proposal to give bureaucrats the technical ability to perform the removal of the tools for inactive admins as required by the aforementioned RFC. As such I wanted to ask here for input whether to start a new RFC on this proposal. Regards  So Why  21:23, 4 July 2011 (UTC)
 * I for one would support this. Every other user right granting is reversible by the person who did it. In fact, everything admins/bureaucrats do is reversible and this is the only exception. It is only an accident that bureaucrats do not have this ability. AD 21:29, 4 July 2011 (UTC)
 * I have supported this proposal in the past and would support it again. Acalamari 21:31, 4 July 2011 (UTC)
 * Yes, of course crats should have this ability. → ROUX   ₪  21:35, 4 July 2011 (UTC)
 * Sounds good to me. -- Eraserhead1 &lt;talk&gt; 21:42, 4 July 2011 (UTC)
 * I supported this before, and still do. Since desysoppings are now going to start happening more frequently with the inactive admin removal process, it makes even more sense to have trusted local users do it instead of going to the stewards every time. We can assume bureaucrats to have knowledge about the policy and standard procedures, something of which many stewards may be unaware. Many Wikimedia projects have already added this right to the bureaucrat package: meta, simple.wikipedia, en.wikinews, hi.wikipedia, fi.wikipedia, etc. While bureaucrats weren't exactly selected for this task, I have no problem trusting them with an additional responsibility which is closely related with their current job. Jafeluv (talk) 23:38, 4 July 2011 (UTC)


 * Lest we get ahead of ourselves, rather than expressing support for the idea itself, perhaps we should discuss how an RfC would proceed. Past discussions have shown considerable support for the idea, but have foundered on claims that consensus was insufficiently strong, the question posed wasn't clear enough, and/or participation wasn't broad enough. Therefore, I would recommend the following specific steps: 1) Start a clear RfC on a distinct question. For example, "Should bureaucrats be given the technical ability to remove the admin bit?" No additional options (such as ability to remove the bureaucrat bit) or mention of other topics that have confounded past discussions (such as community de-adminship). 2) Advertise the RfC widely. Notices on the relevant Village Pump pages, T:CENT, WT:RFA, WP:BN, WP:AN, WT:ADMIN and other pages as appropriate. Ask for a mention in the Signpost. If possible, get a watchlist notice for it. 3) Hope for as clear a consensus as possible. --RL0919 (talk) 23:56, 4 July 2011 (UTC)


 * I would support  this if it is limited to, and only, to procedural desysopping  as per the new '12-month' resolution,  To  succeed, The RfC proposal  should be as short  and concise as possible, and should not  only  state what  it  is for, but also state clearly  what  it is not  for -  otherwise there will  be a pile on  of 'views from  User:X' and alternative suggestions, and requests for additional tool-removal  circumstances. The RfC should be widely  advertised. Kudpung กุดผึ้ง (talk) 01:12, 5 July 2011 (UTC)
 * What about self-requests and Arbitration Committee remedies, both of which go to SRP at present? – xeno <sup style="color:black;">talk 01:41, 5 July 2011 (UTC)
 * @Kudpung: I think that's exactly the problem RL0919 mentioned. Imho, the RFC should only be about the technical ability to do so. We can discuss specific cases, such as procedural desysopping or the cases xeno mentions once there is a consensus that crats should have the ability. Like with any other userright, the question whether a group should have it (like the delete-flag for admins) is separate from the question in which circumstances they may use it (e.g. WP:DEL for the delete-flag). Regards  So Why  07:33, 5 July 2011 (UTC)

Set up TWO RFCs. Seriously, it's the only way to stop the issue of policy polluting the discussion on the technical ability. Requests for comment/Bureaucrat technical ability to remove sysop bit and Requests for comment/policy on bureaucrat removal of adminship. For the latter, self-requests, temporary suspension under the new "inactive admin" approach, and arbcom remedies ought to be non-controversial - but regardless, the discussion has to be kept separate. Rd232 public talk 09:44, 5 July 2011 (UTC)


 * True but I'm unsure as to how to have them open at the same time, since the second RFC requires the first to be successful to make any sense. And if we cannot have them open at the same time, how can we stop people from polluting the first RFC with discussions that should be held in the second one? One idea would be to ask one or more respected neutral editor(s), possibly from ArbCom, to moderate the RFC and remove all discussion that's outside the RFC's scope but I'm unsure whether all editors will accept such moderation... Regards  So Why  10:34, 5 July 2011 (UTC)
 * We can perfectly well have the second open at the same time as the first, it's by far the simplest solution. All the second RFC needs to do is say at the top something like This RFC is about the policy which will be required if Requests for comment/Bureaucrat technical ability to remove sysop bit succeeds. And the first will say This RFC is purely about giving bureaucrats the technical ability to remove the sysop bit. Use of this ability would be governed by whatever policy the community determines. A potential policy is under discussion at Requests for comment/policy on bureaucrat removal of adminship. The technical ability, if activated, may not be used unless or until a specific policy has been approved by the community. That way, moderation by any editor should be acceptable, since there's a good place to move any misplaced comments to (but the existence of that place should anyway minimise the problem). Rd232 public talk 12:06, 5 July 2011 (UTC)
 * Indeed, recently parallel discussions were running simultaneously on adding the technical ability for CU/OS to function without administrative rights concurrent with the more general policy discussion on whether adminship should be a prerequisite for those roles. – xeno <sup style="color:black;">talk 12:23, 5 July 2011 (UTC)
 * Good points, I'm convinced. As such, I started two RFCs at:
 * Requests for comment/Granting bureaucrats the technical ability to remove the admin flag
 * Requests for comment/Bureaucrat removal of adminship policy
 * As I am not experienced in creating RFCs, I would invite everyone here to help expanding those pages with proposals and structure, so we can start those RFCs soon. Regards  So Why  13:43, 5 July 2011 (UTC)
 * I added some background and structural tweaking to the technical one. I think that will be the easier of the two since it is a pretty simple yes/no situation. The policy one may be a bit more complicated, since potentially people might have different opinions on bureaucrats acting in different cases (self-requests vs. ArbCom rulings vs. inactives). We may want different sections to discuss each to make consensus easier to determine in case it differs from one situation to another. --RL0919 (talk) 21:16, 5 July 2011 (UTC)
 * I created a separate section for each situation where a removal might be required, so that people can support one situation while opposing others. Then, when the RFC is closed, all situations with consensus in their favor can be added to the policy. Regards  So Why  21:25, 5 July 2011 (UTC)