Jump to content

Wikipedia:Administrators' noticeboard

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Syrthiss (talk | contribs) at 17:14, 13 January 2012 (→‎User:Victoriaedwards: +rep, have there been any issues with their edits?). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

    Welcome — post issues of interest to administrators.

    When you start a discussion about an editor, you must leave a notice on their talk page. Pinging is not enough.

    You may use {{subst:AN-notice}} ~~~~ to do so.

    Sections inactive for over seven days are archived by Lowercase sigmabot III.(archivessearch)

    Template:Active editnotice


      You may want to increment {{Archive basics}} to |counter= 38 as Wikipedia:Closure requests/Archive 37 is larger than the recommended 150Kb.

      Use the closure requests noticeboard to ask an uninvolved editor to assess, summarize, and formally close a Wikipedia discussion. Do so when consensus appears unclear, it is a contentious issue, or where there are wiki-wide implications (e.g. any change to our policies or guidelines).

      Do not list discussions where consensus is clear. If you feel the need to close them, do it yourself.

      Move on – do not wait for someone to state the obvious. In some cases, it is appropriate to close a discussion with a clear outcome early to save our time.

      Do not post here to rush the closure. Also, only do so when the discussion has stabilised.

      On the other hand, if the discussion has much activity and the outcome isn't very obvious, you should let it play out by itself. We want issues to be discussed well. Do not continue the discussion here.

      There is no fixed length for a formal request for comment (RfC). Typically 7 days is a minimum, and after 30 days the discussion is ripe for closure. The best way to tell is when there is little or no activity in the discussion, or further activity is unlikely to change its result.

      When the discussion is ready to be closed and the outcome is not obvious, you can submit a brief and neutrally worded request for closure.

      Include a link to the discussion itself and the {{Initiated}} template at the beginning of the request. A helper script can make listing easier. Move discussions go in the 'other types' section.

      Any uninvolved editor may close most discussions, so long as they are prepared to discuss and justify their closing rationale.

      Closing discussions carries responsibility, doubly so if the area is contentious. You should be familiar with all policies and guidelines that could apply to the given discussion (consult your draft closure at the discussions for discussion page if unsure). Be prepared to fully answer questions about the closure or the underlying policies, and to provide advice about where to discuss any remaining concerns that editors may have.

      Non-admins can close most discussions. Admins may not overturn your non-admin closures just because you are not an admin, and this is not normally in itself a problem at reviews. Still, there are caveats. You may not close discussions as an unregistered user, or where implementing the closure would need tools or edit permissions you do not have access to. Articles for deletion and move discussion processes have more rules for non-admins to follow.

      Technical instructions for closers

      Please append {{Doing}} to the discussion's entry you are closing so that no one duplicates your effort. When finished, replace it with {{Close}} or {{Done}} and an optional note, and consider sending a {{Ping}} to the editor who placed the request. Where a formal closure is not needed, reply with {{Not done}}. After addressing a request, please mark the {{Initiated}} template with |done=yes. ClueBot III will automatically archive requests marked with {{Already done}}, {{Close}}, {{Done}} {{Not done}}, and {{Resolved}}.

      If you want to formally challenge and appeal the closure, do not start the discussion here. Instead follow advice at WP:CLOSECHALLENGE.


      Other areas tracking old discussions

      Administrative discussions

      (Initiated 18 days ago on 28 August 2024) Opinions vary; a summary of consensus (if any) as to whether there is involvement, and if so the scope, would be helpful. Thanks in advance. Levivich (talk) 03:27, 6 September 2024 (UTC)[reply]

      I'm willing to close this, but will wait a few days to see if Shushugah's new proposals go anywhere. Compassionate727 (T·C) 17:32, 8 September 2024 (UTC)[reply]
      @Compassionate727: - 8-11 editors have voted in Shushugah's proposals by now. starship.paint (RUN) 11:45, 11 September 2024 (UTC)[reply]
      I'll let them keep running a little longer. I won't realistically have time to write a closing statement before the weekend, anyway. Compassionate727 (T·C) 22:40, 11 September 2024 (UTC)[reply]
      Preemptively commenting that I have been sick for the past couple of days: not seriously, but enough that I feel like I haven't had the mental energy to give this the attention it deserves. It has not slipped my mind. Compassionate727 (T·C) 18:50, 15 September 2024 (UTC)[reply]

      (Initiated 10 days ago on 5 September 2024) Conversation seems to have ended, consensus seems to be that the user is an issue, but no clear consensus on what to do about it. --Brocade River Poems (She/They) 02:48, 13 September 2024 (UTC)[reply]

      (Initiated 8 days ago on 7 September 2024) Restored from archive. Admin closure requested. voorts (talk/contributions) 00:58, 14 September 2024 (UTC)[reply]

      Done by StarMississippi. Compassionate727 (T·C) 23:55, 14 September 2024 (UTC)[reply]

      Place new administrative discussions above this line using a level 3 heading

      Requests for comment

      (Initiated 104 days ago on 3 June 2024) Initial close has been overturned at review. A new close is required. -- LCU ActivelyDisinterested «@» °∆t° 16:36, 15 August 2024 (UTC)[reply]

      Surely someone wants to be taken to review and shouted at, even if just for the experience. -- LCU ActivelyDisinterested «@» °∆t° 16:23, 10 September 2024 (UTC)[reply]
      Anyone want a closer's barnstar? (okay but seriously maybe we should just panel close this one, if only to prevent any further disputes.) --Licks-rocks (talk) 11:46, 11 September 2024 (UTC)[reply]
      Panel close is probably a good idea if we can get a panel together. Loki (talk) 19:35, 11 September 2024 (UTC)[reply]

      (Initiated 87 days ago on 20 June 2024) RfC already expired on this very controversial article and a formal closure is needed to prevent future edit warring. Vacant0 (talkcontribs) 12:10, 13 September 2024 (UTC)[reply]

      (Initiated 85 days ago on 22 June 2024) - I thank the Wikipedia community for being so willing to discuss this topic very extensively. Because 30 days have passed and requested moves in this topic area are already being opened (For reference, a diff of most recent edit to the conversation in question), I would encourage an uninvolved editor to determine if this discussion is ready for closure. AndrewPeterT (talk) (contribs) 22:34, 22 July 2024 (UTC)[reply]

      (Also, apologies if I have done something incorrectly. This is my first time filing such a request.) AndrewPeterT (talk) (contribs) 22:34, 22 July 2024 (UTC)[reply]
      There is ongoing discussion there as to whether a closer for that discussion is necessary or desirable. I would suggest to wait and see how that plays out.--Wehwalt (talk) 14:58, 24 July 2024 (UTC)[reply]
      This is dragging on ad nauseam. I suggest an admin closes this, possibly with the conclusion that there is no consensus to change. PatGallacher (talk) 17:50, 28 July 2024 (UTC)[reply]
      Indeed. Also a discussion at Wikipedia:Discussions for discussion#Some holistic solution is needed to closing numerous move requests for names of royals, but that dates back to April. – wbm1058 (talk) 15:07, 21 August 2024 (UTC)[reply]

      (Initiated 70 days ago on 7 July 2024) Discussion has already died down and the 30 days have elapsed. Uninvolved closure is requested. Thanks a lot! Chaotic Enby (talk · contribs) 21:45, 6 August 2024 (UTC)[reply]

      @Chaotic Enby I was reviewing this for a close, but I wonder if reopening the RFC and reducing the number of options would help find a consensus. It seems like a consensus could be found between options A or D. Nemov (talk) 12:35, 14 August 2024 (UTC)[reply]
      That could definitely work! Chaotic Enby (talk · contribs) 12:41, 14 August 2024 (UTC)[reply]

      (Initiated 70 days ago on 8 July 2024). Ready for closing, last !vote was 12 July by looks of it. CNC (talk) 16:27, 9 August 2024 (UTC)[reply]

      (Initiated 62 days ago on 15 July 2024) -sche (talk) 15:19, 14 August 2024 (UTC)[reply]

      There have been only 5 !votes since end July (out of 50+) so this could be closed now. Selfstudier (talk) 10:23, 15 August 2024 (UTC)[reply]
      +1 please close it thanks. NadVolum (talk) 13:49, 25 August 2024 (UTC)[reply]

      (Initiated 53 days ago on 24 July 2024) Discussion slowed. Last comment 13 August 2024. Moderately complex RfC with multiple options. Thank you in advance to the closer. JDiala (talk) 05:46, 4 September 2024 (UTC)[reply]

      (Initiated 41 days ago on 5 August 2024) Discussion has slowed. Last comment 23/08/2027. TarnishedPathtalk 04:44, 27 August 2024 (UTC)[reply]

      (Initiated 40 days ago on 6 August 2024) Talk:Genocide_of_indigenous_peoples#RFC_Palestine Hi! calling for closers for this one, as well as interpretation of whether content should be placed back in in case of WP:NOCONSENSUS. Bluethricecreamman (talk) 02:30, 10 September 2024 (UTC)[reply]

      (Initiated 37 days ago on 9 August 2024)

      Wikipedia talk:Notability (species)#Proposal to adopt this guideline is WP:PROPOSAL for a new WP:SNG. The discussion currently stands at 503 comments from 78 editors or 1.8 tomats of text, so please accept the hot beverage of your choice ☕️ and settle in to read for a while. WhatamIdoing (talk) 22:22, 9 September 2024 (UTC)[reply]

      (Initiated 36 days ago on 10 August 2024) Another infobox image RFC winding down. Nemov (talk) 13:50, 3 September 2024 (UTC)[reply]

      Can someone close this before the opening editor pings any more projects. It's around eight so far. Nemov (talk) 14:46, 9 September 2024 (UTC)[reply]
      The opening editor needs to be warned about forum shopping. voorts (talk/contributions) 15:51, 9 September 2024 (UTC)[reply]
      They were in that very RFC and went right back to doing it within a few days. Nemov (talk) 17:02, 9 September 2024 (UTC)[reply]
      Then I think AN/I is the appropriate place for that. I'm not going to encourage this sort of behavior by closing this discussion immediately, but other closers here might think differently. voorts (talk/contributions) 17:48, 9 September 2024 (UTC)[reply]
      Ah, sorry for the confusion. I don't think it should be closed just because of the forum shopping. The RFC is nearing expiration. I just mention the pinging of projects in order to save the community time. Thanks! Nemov (talk) 18:22, 9 September 2024 (UTC)[reply]

      (Initiated 36 days ago on 10 August 2024) Hello. Please close this discussion. Prcc27 (talk) 23:05, 11 September 2024 (UTC)[reply]

      (Initiated 34 days ago on 12 August 2024) Discussion has slowed. Last comment 24/08/2024. TarnishedPathtalk 04:45, 27 August 2024 (UTC)[reply]

      (Initiated 33 days ago on 13 August 2024) Discussion has been open for more than 30 days. I believe the result is pretty clear however am involved and another editor has objected to my interpretation of the consensus. -Ad Orientem (talk) 02:44, 15 September 2024 (UTC)[reply]

      (Initiated 29 days ago on 17 August 2024) Requesting immediate procedural close for Talk:Philippe Pétain#Rfc for Lede Image of Philippe Pétain, because it is blocked on a Wikipedia policy with legal implications that no one at the Rfc is qualified to comment on, namely U.S. copyright law about an image. At a minimum, it will require action at Commons about whether to delete an image, and likely they will have to consult Wikimedia legal for an interpretation in order to resolve the issue. Under current circumstances, it is a waste of editor time to leave the Rfc open, and is impossible to reliably evaluate by a closer, and therefore should be procedurally closed without assessment, the sooner the better. Thanks, Mathglot (talk) 20:42, 24 August 2024 (UTC)[reply]

      • It's not appropriate to make an immediate procedural close in those circumstances. Wikipedians routinely make decisions about copyright, even those Wikipedians who aren't US attorneys. This is not a high-drama situation. However I'm starting to wonder if the RFC nominator might be on a crusade about our lede images for prominent WW2 figures, and if so, whether they might benefit from a sysop's advice and guidance about overusing our RFC process.—S Marshall T/C 09:16, 29 August 2024 (UTC)[reply]
        I'll do this, although I'm going to do the other close I committed to first. Compassionate727 (T·C) 16:56, 15 September 2024 (UTC)[reply]
        @Compassionate727 FWIW the image was kept at Commons and here's a bit of a follow up on the copyright stuff discussed afterward.[1] Nemov (talk) 01:02, 16 September 2024 (UTC)[reply]

      (Initiated 20 days ago on 26 August 2024) Greetings closing admins, I would like to request a closure of RfC discussion of Algeria Algeria RfC discussion as the discussion has stabilized and it is due for closure. --Potymkin (talk) 16:47, 14 September 2024 (UTC)[reply]

      @Potymkin: It's not due for closure, as it's been open for 19 days not 30. The last comment was four days ago, at 14:05, 10 September 2024 (UTC), so I also don't think that it's stabilised. --Redrose64 🌹 (talk) 18:07, 14 September 2024 (UTC)[reply]
      okay thank you for your output and also for correcting my form, I apologize for mistakes i made in the template on this form as this is my first time. I have made wrong judgement when I read " The best way to tell is when there is little or no activity in the discussion, or further activity is unlikely to change its result." I fully trust your judgement that the discussion is not yet ready for closure. the person who started the RfC @Kovcszaln6 said in UserTalk Page " In order to avoid any future trouble (see WP:INVOLVED) I decided that it's best if I don't close the RfC myself. As I have stated, I'd suggest that you request the RfC's closure at WP:RFCL" so what do you recommend I do next ?
      Delete the Template and I restate it in 11 days ?
      or keep the templete until it ticks 30 days have passed ? Potymkin (talk) 18:19, 14 September 2024 (UTC)[reply]

      (Initiated 3 days ago on 12 September 2024) There is almost unanimous consensus to close this RfC early, but I think this needs an uninvolved closer. There's currently an ongoing RFCBEFORE discussion in anticipation of a workshopped RfC on the future of ITN, so a quick review of this close request would be greatly appreciated. voorts (talk/contributions) 20:12, 12 September 2024 (UTC)[reply]

      5 to 9 (just counting heads) is not "unanimous". Neither is a list of several opposers supporting close (with one supporter "ambivalent", and one of the RFC opposers opposing the early close). And a rename proposal doesn't interfere with whatever other discussions you may be having. If some future discussion does even more - great - consensus can change, after all. RFCs run for 30 days. And this one should too. - jc37 21:01, 12 September 2024 (UTC)[reply]
      I was referring to the discussion about an early close being nearly unanimous, not the RfC itself. A closer here will weigh the arguments and make an appropriate decision. voorts (talk/contributions) 21:10, 12 September 2024 (UTC)[reply]

      (Initiated 40 days ago on 6 August 2024) Hello. Could an uninvolved editor please summarise and close this discussion. Thanks Melbguy05 (talk) 07:23, 15 September 2024 (UTC)[reply]

      Place new discussions concerning RfCs above this line using a level 3 heading

      Deletion discussions

      XFD backlog
      V Jun Jul Aug Sep Total
      CfD 0 0 8 12 20
      TfD 0 0 1 5 6
      MfD 0 0 4 3 7
      FfD 0 0 1 1 2
      RfD 0 0 27 19 46
      AfD 0 0 0 5 5

      (Initiated 66 days ago on 11 July 2024) Steel1943 (talk) 21:26, 4 September 2024 (UTC)[reply]

      (Initiated 64 days ago on 13 July 2024) Steel1943 (talk) 21:28, 4 September 2024 (UTC)[reply]

      (Initiated 55 days ago on 22 July 2024) mwwv converseedits 11:31, 11 September 2024 (UTC)[reply]

       Done Compassionate727 (T·C) 22:46, 15 September 2024 (UTC)[reply]

      (Initiated 36 days ago on 10 August 2024) HouseBlaster (talk • he/they) 03:41, 2 September 2024 (UTC)[reply]

      (Initiated 27 days ago on 19 August 2024) HouseBlaster (talk • he/they) 03:41, 2 September 2024 (UTC)[reply]

      (Initiated 18 days ago on 28 August 2024) I think this is an easy one, both to close and to implement – {{db-xfd}} is your friend for non-admins :D HouseBlaster (talk • he/they) 20:49, 14 September 2024 (UTC)[reply]

       Done Compassionate727 (T·C) 17:02, 15 September 2024 (UTC)[reply]

      (Initiated 13 days ago on 2 September 2024) HouseBlaster (talk • he/they) 20:49, 14 September 2024 (UTC)[reply]

       Done Compassionate727 (T·C) 17:02, 15 September 2024 (UTC)[reply]

      Place new discussions concerning XfDs above this line using a level 3 heading

      Other types of closing requests

      (Initiated 284 days ago on 6 December 2023) a merge discussion related to Electrogravitics and Biefeld–Brown effect now without comments for 4 months; requesting a close by any uninvolved editor. Klbrain (talk) 20:34, 9 September 2024 (UTC)[reply]

      (Initiated 133 days ago on 5 May 2024) Discussion went on for 3 months and seems to have stalled. 35.0.62.211 (talk) 16:38, 29 August 2024 (UTC)[reply]

      (Initiated 110 days ago on 28 May 2024) Latest comment: 3 days ago, 79 comments, 37 people in discussion. Closing statement may be helpful for future discussions. Gråbergs Gråa Sång (talk) 10:29, 11 June 2024 (UTC)[reply]

       Doing...— Frostly (talk) 22:35, 17 July 2024 (UTC)[reply]
      @Frostly Are you still planning on doing this? Soni (talk) 16:57, 22 July 2024 (UTC)[reply]
      Soni, yes - have drafted close and will post by the end of today. Thanks! — Frostly (talk) 17:56, 23 July 2024 (UTC)[reply]
      I wanted to note that this is taking slightly longer than expected, but it is at the top of my priority and will be completed soon. — Frostly (talk) 05:14, 27 July 2024 (UTC)[reply]
      @Frostly Just checking, would you like someone else to help with this? Soni (talk) 07:31, 11 August 2024 (UTC)[reply]
      @Frostly: also checking in. voorts (talk/contributions) 00:33, 22 August 2024 (UTC)[reply]
      Hi Voorts and Soni, thanks for the pings! I've unfortunately been in the hospital for the past week but am now feeling better. I apologize for the long delay in putting out the close and appreciate your messages! Best, — Frostly (talk) 03:59, 22 August 2024 (UTC)[reply]
      I'm sorry to hear that; a week-long hospitalization is not fun. But, I'm glad that you're feeling better. Best, voorts (talk/contributions) 19:06, 22 August 2024 (UTC)[reply]
      Ping @Frostly again (I saw you've been editing Commons). Hope your still better, and if you don't feel like doing this one anymore, just let people know. Gråbergs Gråa Sång (talk) 17:02, 3 September 2024 (UTC)[reply]
      Archived. P.I. Ellsworth , ed. put'er there 13:32, 24 July 2024 (UTC)[reply]

      (Initiated 109 days ago on 30 May 2024) Contentious merge discussion requiring uninvolved closer. voorts (talk/contributions) 01:35, 5 August 2024 (UTC)[reply]

      (Initiated 99 days ago on 8 June 2024) Since much of the discussion centers on the title of the article rather than its content, the closer should also take into account the requested move immediately below on the talk page. Smyth (talk) 15:17, 13 July 2024 (UTC)[reply]

      If the closer finds "no consensus", I have proposed this route in which a discussion on merger and RM can happen simultaneously to give clearer consensus.VR (Please ping on reply) 20:10, 13 July 2024 (UTC)[reply]

      (Initiated 77 days ago on 30 June 2024) Proposal to split RS/PS. Discussion has died down. voorts (talk/contributions) 21:39, 29 August 2024 (UTC)[reply]

      (Initiated 69 days ago on 8 July 2024) – Editors would feel more comfortable if an uninvolved closer provided a clear statement about whether a consensus to WP:SPLIT exists, and (if so) whether to split this list into two or three lists. WhatamIdoing (talk) 03:06, 9 August 2024 (UTC)[reply]

      (Initiated 35 days ago on 12 August 2024) No comments on two weeks; consensus on the merge is unclear, particularly for Effects of Hurricane Isabel in Delaware. 107.122.189.12 (talk) 19:29, 7 September 2024 (UTC)[reply]

      (Initiated 30 days ago on 16 August 2024) Discussion has slowed. No comments in a few days. TarnishedPathtalk 02:12, 11 September 2024 (UTC)[reply]

      (Initiated 24 days ago on 22 August 2024) Needs uninvolved editor or admin to close the discussion. George Ho (talk) 23:42, 8 September 2024 (UTC)[reply]

      (Initiated 20 days ago on 26 August 2024) I'd like a closure of this discussion, which was preceded by this discussion:Talk:Cobra_Crack#MOS:ITAL Gråbergs Gråa Sång (talk) 16:50, 3 September 2024 (UTC)[reply]

      (Initiated 19 days ago on 27 August 2024) Needs a closed from an experienced user. Cremastra (talk) 11:48, 15 September 2024 (UTC)[reply]

      Place new discussions concerning other types of closing requests above this line using a level 3 heading

      Please create a redirect from Klein–Gordon field (with an endash) to Klein–Gordon equation

      I tried to create

      Klein–Gordon field

      with the content

      #REDIRECT [[http://en.wikipedia.org/wiki/Klein–Gordon equation]]

      and it said the title is blacklisted (which seems rather unlikely). Note that we already have Klein-Gordon field, a redirect with the same target.

      False vacuum (talk) 17:41, 10 January 2012 (UTC)[reply]

       Done. Note that you don't need the "http://en.wikipedia.org/wiki/" business in the redirect; I'm not sure if that's why it was giving you an error message. 28bytes (talk) 17:43, 10 January 2012 (UTC)[reply]
      The incorrect format is exactly why it was giving the error message: there's an edit filter to prevent that sort of malformed redirect. --Carnildo (talk) 00:59, 12 January 2012 (UTC)[reply]
      As well there should be. Sorry for being stupid. (I've created many redirects before, so why I screwed up this one is a mystery to me.) False vacuum (talk) 03:50, 12 January 2012 (UTC)[reply]

      Question about RFC/U

      I originally posted this on Wikipedia talk:Arbitration Committee, but perhaps I am more likely to get an answer here.

      I have recently started an RFC/U for an editor with what I perceive as a pattern of problematic editing (Wikipedia:Requests for comment/Shakehandsman). After failing to have the RFC/U shut down with threads on AN and AN/I, the editor has now declared that they have left Wikipedia. I am concerned that this editor may simply wait for things to settle down and return to editing, or just create another account in order to avoid the RFC/U altogether. I suppose my question is this - if an editor ducks out of an RFC/U by falsely claiming to leave Wikipedia, can the RFC/U be re-opened once the editor commences editing again (with the same or a new account)? Delicious carbuncle (talk) 19:11, 11 January 2012 (UTC)[reply]

      Yes. I know of at least one that's being put on held indefinitely (though I don't think he'll come back, it's not impossible). There's also an arbitration case in this state as well. The Blade of the Northern Lights (話して下さい) 01:06, 12 January 2012 (UTC)[reply]
      Yes, you can put RFC/Us on hold. Despite the number of editors who think they'll just duck out until it all blows over (partly driven by their erroneous belief that there's a strict 30-day timer on RFC/Us, so if they take a 30-day wikibreak, they can ignore the whole thing), it's not commonly done, but the usual process seems to be adding a short note to the page explaining the situation and then removing the link from the list of open RFC/Us. WhatamIdoing (talk) 17:30, 12 January 2012 (UTC)[reply]
      Is it safe to assume that the same principle applies even if an RFC/U is not explicitly put on hold? If an editor returns after an RFC/U has been closed due to inactivity (i.e., the editor left), the RFC/U is no more or less resolved than one which has explicitly been put on hold. Delicious carbuncle (talk) 19:34, 12 January 2012 (UTC)[reply]
      • As the admin who placed it on hold, you might have just asked me or at least bothered to let me know about this thread. If you actually bother to read the statements I made on both the RFCU itself [2] and the talk page [3] you would find that I made all this perfectly clear when doing the close. Beeblebrox (talk) 19:39, 12 January 2012 (UTC)[reply]
        Yes, I think anyone who looks at the RFC/U which I linked above will see that. I am sorry that I didn't notify you of this thread, but although prompted by the Shakehandsman case, the question I have is more general. Delicious carbuncle (talk) 19:49, 12 January 2012 (UTC)[reply]
      It was also already answered, so I'm a little unclear on why you felt the need to ask it at all, let alone go to arbcom about it, but whatever. Beeblebrox (talk) 19:54, 12 January 2012 (UTC)[reply]
      I don't understand why you find thread annoying, but read my question above. That is the question I am asking and it has not been answered. If you believe your statements at the Shakehandsman RFC/U answer it, please spell it out for me because I can be a little slow sometimes. Thanks. Delicious carbuncle (talk) 20:12, 12 January 2012 (UTC)[reply]
      I don't think any new categories or procedures are needed. If the situation you describe were to come to pass, the old RFC could be re-opened, or a new one with links to the old one, or, more likely straight to arbcom since it would be clear they did in fact leave just to shut down the RFC. Something like that has happened, in the case of A Nobody (talk · contribs). He kept making lame excuses, first for ignoring an RFC and then an Arbcom case. When it became clear he was full of it he was banned. Beeblebrox (talk) 23:05, 12 January 2012 (UTC)[reply]

      Article Feedback Tool - additional test deployment

      Hey guys,

      Just keeping you in the loop; we're going to be testing another change to the Article Feedback Tool on starting today, January 11. So far, we've done a bit of small-scale experimentation with the actual design of the tool, as announced on the blog, the village pump, and on various mailing lists. This has all been on a tiny fraction of articles (~22k total articles, about 0.6% of the English Wikipedia), and a lot of really useful data has been gathered without bothering the vast majority of editors or readers. Ideally, that's what we'd aim for with all tests :).

      Even with Wikipedia readership reaching half a billion users per month, the feedback form its current position (at the end of the article) doesn’t see a whole lot of activity. In this test, we’ll be experimenting with a more prominent way to access to tool. When a user loads the page with the test version of the Article Feedback Tool, they will see an “Improve this article” link docked on the bottom right hand corner of the page (please see this for a mockup). Since this link is docked, it will stay with the reader while they’re reading the article. The introduction of this link will undoubtedly increase the amount of feedback. We need to, however, understand how it affects the quality of the feedback. We genuinely don't know what the impact will be, which is why we're doing these tests :). As with the last tests, it'll be on a very small subset of articles and probably won't be noticed by most people.

      If you do encounter it, and it does bug you, you can turn it off just by going into Preferences > Appearance > Don't show me the article feedback widget on pages. If you've already ticked this option, the new link shouldn't appear at all; please do let me know if it does. We are working on a way to disable it "in-line" as well so you can simply dismiss the link without going to preferences.

      We’ll also be doing some preliminary analysis on whether such a prominent link cannibalizes editing behavior. The team is very aware that the new link may compete with the edit tab and section edit links. Since the test version of the tool is deployed on a limited number of articles, we will only get a rough read on how much, if any, cannibalization takes place. Per our research plan, we’ll continue to monitor the tradeoff between giving feedback and editing.

      If any of you have any questions, please don't hesitate to contact me or drop a note on the talkpage.

      Thanks! Okeyes (WMF) (talk) 21:25, 11 January 2012 (UTC)[reply]

      Warning embedded/hidden in edit-text?

      Wasn't sure where to bring this. Can someone go Jim Rome and click edit, and tell me if the warnings embedded/hidden in the article code are normal/allowable? And, if so, under what policy or guideline would the rules regarding this be found. I see the good intentions of doing this, but I also see a large potential for vandalism if it's permissible to "hide" messages in the edit-text. Also, it's kind of bean-y to say what not to do. I mean, if I was a vandal, I would never have thought to change his name to "Pterodactyl" until seeing that. Anyway, sorry if the warnings are standard procedure, I just wasn't sure what I was looking at. Quinn WINDY 21:35, 11 January 2012 (UTC)[reply]

      Yeah, hidden text is not that unusual. Help:Hidden text gives some reasons when and when not to use it. 28bytes (talk) 21:45, 11 January 2012 (UTC)[reply]

      New format opposed

      The following discussion is closed. Please do not modify it. No further edits should be made to this discussion.


      There was a discussion about adopting a new format at http://en.wikipedia.org/wiki/Talk:List_of_active_Indian_Navy_ships. This was suggested by Rademire and was opposed by Mittal.fdk. The reason for the opposition was that "I disagree that this page is better than the former." Lately it has come to notice that the page has been changed to a different format. Can the Admins restore it?Aheadearth (talk) 03:49, 12 January 2012 (UTC)[reply]

      Note to Admins, this user passes the duck test outstandingly. Just awaiting CU to confirm as most recent sockpuppet of Chanakya.TalkWoe90i 12:34, 12 January 2012 (UTC)[reply]
      The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

      New method for article quality evaluation

      This was proposed by my 6-year old at breakfast, prompted by my "Ask Me About Wikipedia" shirt:

      Whenever I color someone's Wikipedia blue that means they didn't do a good job. They get a zero. Whenever they get a pink circle that means they did really really really bad. If they get this color [holds up yellow marker] they get a one THOUSAND.

      Fellow editors, you are placed on notice: the time for screwing around is over. I've notified the Foundation of course, in the usual way. Please, let's make this a yellow day. Drmies (talk) 14:33, 12 January 2012 (UTC)[reply]

      Is there anything to obtain "OVER 9000!"? Blackmane (talk) 16:47, 12 January 2012 (UTC)[reply]

      It is probably as good a system as the feedback tool that was introduced last year. Is she open to bribery? Something that would survive a journey across the Atlantic? - Sitush (talk) 16:49, 13 January 2012 (UTC)[reply]

      Username issue - grandfather rights?

      Today, I came across Teskey@btinternet.com (talk · contribs). Noticing the username was in violation of WP:UN I gave the user a welcome and issued a warning re the username. I did not block the editor as I wanted to give them a chance to respond. On checking whether or not Teskey had edited since I informed them of the issue, I discovered that this editor had been editing sporadically since 2006. It struck me that this could be another case similar to Rms125a@hotmail.com (talk · contribs), which was also created before the policy was formulated - see (see discussion from 2009). Therefore I would ask that Teskey is granted grandfather rights. A change of name should be encouraged, but it cannot be demanded. Mjroots (talk) 16:41, 12 January 2012 (UTC)[reply]

      If they've been editing without trouble since 2006, I'd certainly be happy to let them keep their username. 28bytes (talk) 17:02, 12 January 2012 (UTC)[reply]
      Ditto. I suspect the user may be related to be User:Teskey as there looks to be a similar editing history. If they lost the account there may be a possibility to usurp the account. --RA (talk) 17:16, 12 January 2012 (UTC)[reply]
      Is there any way of searching all registered usernames to find ones that (1) have the @ character, and (2) are not blocked? Nyttend (talk) 18:12, 12 January 2012 (UTC)[reply]
      Why? As far as I know, it is not possible any more to create user names with "@" in them, so all you'd find would be user names that have been created before the rule to forbid them was established. Therefore there'd be no reason for us to do anything about it. --Conti| 18:28, 12 January 2012 (UTC)[reply]
      I don't see any need to go there with this name, but for future reference we do have a dedicated noticeboard for such discussions at WP:RFCN. Beeblebrox (talk) 19:19, 12 January 2012 (UTC)[reply]
      My point was that we could find all the existing usernames and let their owners know that they're grandfathered, lest someone later come along and try to block them because of the policy. Nyttend (talk) 19:45, 12 January 2012 (UTC)[reply]
      Nyttend had a point there. If all user who have e-mail addresses as their username and are grandfathered in could be sought out, then the fact can be recorded on their talk page so that if another editor stumbles across them and attempts to report them, they will be aware that there will not be any action taken over the user name. Mjroots (talk) 19:55, 12 January 2012 (UTC)[reply]
      Yeah, that is a good idea. Now back to the question of how to do it.... Beeblebrox (talk) 19:58, 12 January 2012 (UTC)[reply]
      I'm not sure its a great idea. Do we have any evidence that such users are being inappropriately blocked? If they are not, I think we can leave well enough alone; this sounds like a solution in search of a problem. I patrol UAA fairly regularly, and I and several other regular admins there (AFAIK) are pretty concientious at looking for grandfather issues and are highly unlikely to block borderline cases like this outright. --Jayron32 03:56, 13 January 2012 (UTC)[reply]
      Maybe a note at WP:UN saying that it is not possible to create such usernames now and any that are found have been granted grandfather rights would suffice to cover the situation? Mjroots (talk) 08:21, 13 January 2012 (UTC)[reply]
      They are grandfathered in. I don't know where that is documented, but I know we don't do forced renames or blocks for this sort of thing. MBisanz talk 13:07, 13 January 2012 (UTC)[reply]

      Reporting Wingard

      I am reporting User:Wingard because they are continually removing commas from dates from several daytime soap opera pages, claiming they've never seen commas in dates. The commas have always been there, and it's quite disruptive. We've tried being nice, but they aren't listening. Please help, thank you! Musicfreak7676 (talk) 19:00, 12 January 2012 (UTC)[reply]

      They have been blocked for edit warring by Daniel Case. TNXMan 19:23, 12 January 2012 (UTC)[reply]

      review of some revdels requested

      See [4], the revdel done on January 3 seems highly inapropriate, the summary the admin doiong them used makes it clear that they completely do not understand what revdel is for, as they indicate that their edits were "silly mistakes" so they went and removed them entirely, even coming back and removing their own username from the page history. This is exactly what revdel is not for, I can't imagine why he thought it appropriate to use it in this manner to hide his own mistakes. I would revert the revdel myself but I recently had a minor disagreement with this admin so I'd like fresh eyes on this. I did try to discuss this with them first on their talk page but they seem to have taken a wiki-break and have not replied to my inquiries about this. Beeblebrox (talk) 19:12, 12 January 2012 (UTC)[reply]

      I agree with your interpretation. The very first warning on the revdel page reads: "Redaction to hide block log entries or hide mere poorly considered actions, criticisms, posts, etc, outside these criteria and without required consensus, or agreement by the arbitration committee, will usually be treated as improper use and may lead to arbitration and/or desysopping." (emphasis mine) TNXMan 19:18, 12 January 2012 (UTC)[reply]
      Agreed, that's not what revdel is for. It appears the admin misunderstood RD6. 28bytes (talk) 19:19, 12 January 2012 (UTC)[reply]
      Yeah, I think what we've got here is a well-meaning admin who took a long break from using their tools and came back to a Wikipedia they didn't really understand anymore. Our initial disagreement was over one revert I made of an edit of his, next thing I knew he was over at ANI accusing me of wheel warring. [5]Beeblebrox (talk) 19:25, 12 January 2012 (UTC)[reply]
      Agreed that is not a valid use of RevDel and those 3 entries should be undeleted. GB fan 19:46, 12 January 2012 (UTC)[reply]
      Would someone care to do that and then inform him of the results? I don't think he is interssted in listening to me so it would be best if someone else handled that end of it. Beeblebrox (talk) 19:50, 12 January 2012 (UTC)[reply]
      I'll do it. 28bytes (talk) 19:51, 12 January 2012 (UTC)[reply]
       Done. 28bytes (talk) 19:55, 12 January 2012 (UTC)[reply]
      Thank you. Beeblebrox (talk) 19:57, 12 January 2012 (UTC)[reply]

      Some pending RPP requests

      WP:RPP has some rather old unanswered requests waiting for someone with the mop.Jasper Deng (talk) 05:20, 13 January 2012 (UTC)[reply]

       Done TNXMan 16:21, 13 January 2012 (UTC)[reply]

      User:Matt2005

      I have noticed that many of Matt2005 (talk · contribs) edits have been disruptive, but had not been reverted. I have gone through the United Stated Network Schedules, but there are probably 250 other edits that need to be looked at.--TonyTheTiger (T/C/BIO/WP:CHICAGO/WP:FOUR) 08:12, 13 January 2012 (UTC)[reply]

      Could an admin please have a word with this user? I have tried twice [6][7] to speak to this user about using edit summaries, only to be summarily reverted. Given their penchant for multiple edits to a single page, it's rather annoying to have to look at each edit to try and figure out what they're doing. Will notify. → ROUX  17:07, 13 January 2012 (UTC)[reply]

      I guess my question would be - are there specific issues with their edits that are masked by their non-use of edit summaries? I don't believe that edit summary use is enforceable by any current policy. I didn't see that they have ever used edit summaries, and their blanking of the talk notice indicates that they have read your note. Syrthiss (talk) 17:14, 13 January 2012 (UTC)[reply]