Wikipedia talk:WikiProject Articles for creation

From Wikipedia, the free encyclopedia
Jump to: navigation, search
Main page Talk page
Showcase Assessment Participants Reviewing instructions Help desk Backlog drives
Welcome to the main Wikipedia Articles for Creation project talkpage
WPAFC talk pages: Main - AFC Helper script - Reviewer help
AfC submissions
653 pending submissions
Purge to update

Skip to the bottom
WikiProject Articles for creation (Rated Project-class)
WikiProject icon This page is used for the administration of the Articles for Creation or Files for Upload processes and is therefore within the scope of WikiProject Articles for Creation. Please direct any queries to the discussion page. WikiProject icon
 Project  This page does not require a rating on the quality scale.
Centralized discussion
Proposals: policy other Discussions Ideas

Note: inactive discussions, closed or not, should be archived.

Finding pending submissions by subject[edit]

How can I find pending AfC submissions, but subject (i.e. by the category they will end up in)? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:19, 20 March 2015 (UTC)

Step 0: Get support for some sort of categorization scheme in the templates (as we want template inhereted categories instead of explicit categories)
Step 1: Go through every pending submission and dump it into one or more of the category buckets
Step 2: ....
Step 3: PROFIT
This is a perenial suggestion/request but nobody wants to spend the time developing solving this problem so no activity gets done on it. Hasteur (talk) 18:11, 20 March 2015 (UTC)
As Hasteur points out, we can't identify submissions by subject unless someone does the work of classifying them. That time is probably better spend reviewing submissions. All is not lost though. How about control clicking on this a bunch of times
Close tabs you've opened until you find one that interests you. --Kvng (talk) 19:30, 20 March 2015 (UTC)
You could always modify the article wizard to add categories based on keywords the editors supplies in a keywords box. -- (talk) 20:25, 21 March 2015 (UTC)

Andy Mabbett, for some subjects it works well to use this custom search which only looks in draft space. By adding the words "Review waiting", you only find drafts which are up for review. For example, if you want to find submissions about politicians, try typing "review waiting politician" in the search box below. —Anne Delong (talk) 05:52, 23 March 2015 (UTC)

A solution, though a manual one, for this issue would be for an additional step to be added to the first review: "Add relevant WikiProject banners to the draft talk page with class=Draft parameter". This would help to sort those submissions that have been through the review sieve at least once. A more comprehensive process would be the equivalent of Stub sorting, replicate all the Stub categories and the associated template and icons, but replace "Stub" with "Draft". Roger (Dodger67) (talk) 06:53, 23 March 2015 (UTC)
Roger (Dodger67), I seem to recall an earlier discussion about this, and there was a problem because most Wikiprojects hadn't implemented "draft" in some process or other, what it was I can't remember. Does anyone know exactly what the problem was, and if it has been fixed? —Anne Delong (talk) 14:57, 23 March 2015 (UTC)
Yeah that would require some big collaboration to get the word spread between the 1,984 wikiprojects (not all active mind you) that exist. Also would it be added be the creator (a new/unregistered user) or the first reviewer? EoRdE6(Come Talk to Me!) 15:23, 23 March 2015 (UTC)
@EoRdE6 most newbies will have no idea at all about WikiProject banners so the task would almost always fall to the first reviewer. Most WikiProjects already have an article rating system which includes a table that lists the numbers of pages by class. The active projects would notice the appearance of Draft-class pages on the list and the curious editors among them would click to see what it means. I think a mass posting of a message on all WikiProject Talk pages would be useful. Roger (Dodger67) (talk) 12:21, 24 March 2015 (UTC)
(ec)@Anne Delong yes indeed, this issue is not new, however since we last raised it the "class=Draft" parameter has been rolled out to all WikiProjects by default, so we can and should now use it. Roger (Dodger67) (talk) 15:28, 23 March 2015 (UTC)
  • Often when I'm reviewing I'll "skip" on drafts that I either don't feel skilled enough to review, or that I don't have the time/energy to do a quality review for at that time. I suspect I'm not alone in this, drafts in the "very old" lists are likely to have been seen by quite a few pairs of eyeballs.
Though I'm not sure about reviewing these, I'm sure I'd be capable of categorizing most into broad pots (especially if one of these was "companies"). If a straightforward categorization system could be implemented in the helper script, which would tie in the necessary Wikiprojects, I reckon we could find ourselves tapping into a lot of reviewer time that currently is wasted. In a sense we'd be creating a triage system, whereby straightforward passes and fails are done quickly (which kinda happens already), and the trickier cases are categorized rather than just languishing. --LukeSurl t c 14:49, 24 March 2015 (UTC)
WikiProject tagging is already a part of the Accept "subroutine" of the script - maybe it could be made available as a separate process, like "cleanup" currently is? I know nothing about scripts, so.... Roger (Dodger67) (talk) 10:56, 26 March 2015 (UTC)
That's a cool idea. We've been making noise about shuffling around the buttons on the main menu, and this would definitely be a candidate for being on the "primary menu" (i.e. you don't have to click the << to show it). An idea I've been thinking about for a while is automating the process of sticking a notice on a WikiProject talk page about a draft and commenting on the draft with the notice; perhaps that could be somehow integrated.
Where would these WikiProject tags go on drafts? I feel like putting them on the talk pages would be a bad idea because reviewers just glancing at the draft wouldn't be able to see them. So putting them in a specialized comment - perhaps modifying {{Afc comment}} with a WikiProject tag-specific version - might be the way to go. APerson (talk!) 16:31, 26 March 2015 (UTC)
It's a perfectly standard WikiProject Banner {{WikiProject Whatever|class=Draft}} that goes on the talk page. A reviewer "just glancing" at a draft isn't interested in seeing that information anyway. The real purposes of WikiProject banners are for the project itself, the banner and its parameters create a number of categories which are used by the projects to sort and manage their articles. I'm opposed to adding even more AFC clutter to the top of drafts pages, one of the main arguments for creating Draft-space in the first place was to give each draft its own talk page, so we should use them. Roger (Dodger67) (talk) 06:22, 29 March 2015 (UTC)
I hope the proposal is to put these banners on the Draft talk: page associated with the submission. This is where they would eventually need to go. They will not further clutter the submission there. --Kvng (talk) 16:55, 29 March 2015 (UTC)
Draft talk: is the obvious place for Wikiproject banners. There could be some merit to a short {{AFC comment}} informing the submitter (who is probably unaware of the talk page), along the lines of "The subject matter of this draft is in the domain of WikiProject Z. Editors from that WikiProject may be able to help you prepare this submission". Getting new editors to talk to and potentially join WikiProjects would be good for editor retention, and should help foster collaboration on drafts. Alternatively such a notice could be delivered to draft authors' talk pages. --LukeSurl t c 17:30, 29 March 2015 (UTC)
I'll join the chorus saying that they'd go on Draft talk: like any other Wikiproject banner. I like the idea of adding adding an {{AFC comment}} as an option. --Ahecht (TALK
) 22:17, 29 March 2015 (UTC)

I need help with AFC helper script[edit]

I have been trying to work this out for 30 minutes. I checked to use helper script in my preferences and I cleared my browsers cache (Firefox). The next step says: To launch AFCH, click on the upside-down triangle icon in the toolbar on an AFC-applicable page and then on the Review (AFCH) link. There is no upside down triangle icon in the toolbar, so I am confused (and frustrated). Hopefully a patient Wikipedian can help me. Face-smile.svg Thank you. CookieMonster755 (talk) 05:56, 29 March 2015 (UTC)

Yes, I got it to work~! Thank you Afc Wikiproject! Face-grin.svg CookieMonster755 (talk) 05:58, 29 March 2015 (UTC)

IRC Nick parameter for helpees causing confusion[edit]

Hi everyone, I'm an active helper on #wikipedia-en-help connect. Many helpees reach us from their declined and/or pending drafts. In my experience, there seems to be informal consensus among helpers to remove the "WPhelp" nick parameter. I noticed this first done by User:Logan on {{Helpmessage}} not long ago. I attempted to apply this change in a bold edit to another AFC template, but I was reverted by Technical 13. I and users such as User:PhantomTech believe that we should remove the parameter and make them choose their own usernames.

I perceive the following benefits:

  1. Helpees with similar numbers would be able to easily tell themselves apart. We already have a problem with helpees thinking we are a private chat room. I have seen many helpees say "I can't tell my number apart from the other helpees unless I look closely."
  2. Conversations in IRC would be easier to follow. Currently many of us use the autocomplete function but autocomplete the wrong helpee's nick, accidentally addressing our messages to the wrong person. This inevitably creates more confusion. If we don't use the autocomplete function, and carefully copy the nick every time, we often still make typos. When we make typos, it doesn't ping the helpee about the fact that there's a message addressed to them.
  3. Ideally, helpees will choose a nick identical to their username, reducing the number of times we have to ask "What is your username?"

I know that there are some people who believe that they may end up choosing a generic name, and since enforce is set on their nicks, they will be automatically changed to Guest### or whatever, but we already experience this issue and it does not seem more problematic than WPhelp####. While it won't solve the problems behind us wanting to remove the WPHelp parameter, it won't create any more problems, either. In fact, many of the links elsewhere on the site use Freenode's webchat instead of KiwiIRC, which does not have a prefilled nick parameter at all. It is better than Freenode webchat because helpees sometimes can't figure out where to type, but they can on the user-friendly KiwiIRC.

  • User:Σ also proposed via IRC that the nick parameter could be replaced with {{#invoke:Random|item|Potato|Kartoffel|PommeDeTerre|Iwashi|Tameru|Rinngo}} creating a nickname randomizer of some sort not unlike the Google Docs-type Anonymous Cat, Anonymous Dog, etc. nicknames. So, that's also another option.

I appreciate anyone's thoughts and comments regarding this matter, especially comments from people who are active helpers in the IRC channel and familiar with the usual day-to-day events and questions that we deal with there. — kikichugirl oh hello! 21:38, 3 April 2015 (UTC)

Having helped in that channel very heavily (some years ago), I agree that having the generic nick#### can be confusing with multiple guests in the channel. I like the idea of inputting code into the link that would make a randomized nick a la Google docs. Killiondude (talk) 21:44, 3 April 2015 (UTC)
Hmm. I understand the issue, but see problems with the proposed solutions. If users are allowed to choose their own names it will typically be their own first name, and the majority of the common names are already registered on freenode. If you randomly generate them a name I can see that being confusing for them. This is another thing to add to my list of reasons we need a non-IRC live help tool though. Sam Walton (talk) 22:33, 3 April 2015 (UTC)
As Kikichugirl said, having usernames picked by users would make it a lot easier to help them. Even if they pick registered nicks and fallback to Guest#####, that's not much (if at all) worse than WPhelp#####. If possible, this is how I think IRC nicks should be set for users looking for help:
  • If the user is logged in and their username is only alphanumeric characters, it gets trimmed to 11 characters (if it's long) and "-WP##" is added to the end where ## is a random number
  • If the user is not logged in or their username has non-alphanumeric characters, a random word or name is used from a list of usernames (like Σ suggests) and "-WP###" is added to that where "###" is, again, a random number except with 3 digits this time
As long as we can get the wiki usernames checked and passed to the link we give users, this allows helpers to get helpee's usernames easily, identifies users as having come from Wikipedia and allows helpers to use autocomplete easily since the start of helpee usernames is not likely to be similar to other helpees. I've looked at Samwalton9's non-IRC live help thing and think that a similar solution could be to have an on-site chat box that connects to the current IRC channel but only shows the user their own messages along with messages that start with their nick and were sent from users with a Wikimedia/Wikipedia/etc. cloak. It's not as great of a solution but it would probably be easier to implement and would allow a wider range of people to help. A form could be filled out that would immediately send information to the channel when they connect so that when "User-WP32" connects, helpees would see:
User-WP32 has Joined #Wikipedia-en-help
User-WP32: Related article:
User-WP32: Coming from:
User-WP32: I don't understand Wikipedia's policy on being bold
"Coming from" would be what page they were on when they clicked the link, "Related article" would be optional and the last message would be whatever they put in a "What's your question?" box. This doesn't solve the issue of people being unavailable at certain times and users without enough experience might still try to help but it gives helpers a lot of the information they need to know to help people and lets helpers decide if they're familiar enough with the topic being asked about before starting to interact. PhantomTech (talk) 23:53, 3 April 2015 (UTC)
I think PhantomTech's name-picking proposal is great and should be implemented as soon as possible. APerson (talk!) 19:51, 4 April 2015 (UTC)
I second that. Primefac (talk) 20:39, 4 April 2015 (UTC)
  • Since this propsed solution would require global JavaScript and affects not only this project but all other projects that use IRC channels or have links to -help, I suggest this discussion be moved to a more global and universal discussion page to prevent a local consensus issue and the risk of this project dictating what the teahouse, help desk, reference desk, etc must have. -help is certainly not an AfC only channel. Also, the WPhelp nicks were implemented by a wider than AfC consensus on IRC in -helpers and a wider consensus would be needed to overturn that. Finally, this discussion is very fragmented with discussions also on my talk page and the templates talk page. To prevent further fragmentation by an individual discussion being started at HD/RD/THQ/Etc, I suggest moving it to WP:VPR. — {{U|Technical 13}} (etc) 22:57, 4 April 2015 (UTC)
I'm sure I must have read you wrong in reading that there was a consensus in irc that determined an onwiki change. There of course isn't any such concept. --nonsense ferret 23:20, 4 April 2015 (UTC)
  • The only onwiki discussion I can find for that specific templates was Wikipedia talk:WikiProject Articles for creation/2014 8#Template-protected edit request on 5 November 2014. Still not the point. Unless you are claiming that -help is ONLY for WP:AFC, then this discussion that changes the behavior of the visitors to that channel needs a discussion at a central location for all projects that use -help. I suggest an RfC at WP:VPR. As I've suggested multiple times, I would be happy to make changes to all of the relevant templates so that each template will pick a different nick depending on which template the user comes from. It can either set the username based on the template used or it can be make to set the user's nick to the name of the page they clicked the link on. Not entirely helpful in cases where the pagename is longer than the max nick name, but it could be truncated to fit and would offer a little more specific name to respond to. As Sam said, asking visitors to pick their own nick is a counter productive way to go. A random nick generator doesn't help much either, since it doesn't offer any information to who the user is. I'm entirely open to the idea of change, as long as it is a forward movement in making it easier to help visitors. If right now there are 7 WPhelp and 3 Guest nicks, this change will have the benefit of there being 0 WPhelp nicks and 9 Guest nicks, that doesn't help the very reason that you are asking for change here and is actually counter productive. Anyways, please ping me if you need my help in applying changes that set the nick to either AfC<template type>## or <pagename> and I'll get started or if you have another idea that helps identifying what visitors need help with, I'll happily implement that as well. Going back to 90% of visitors being Guest isn't helpful and I'm hoping to be able to back to IRC in -help soon. — {{U|Technical 13}} (etc) 15:38, 5 April 2015 (UTC)
WPhelp nicks are primarily used in these AFC templates under this project's jurisdiction. I have no interest in altering the status quo of other templates. There has not been consensus to implement the solution using JavaScript, only that there is approval for it. I still believe that the random-item solution would be best. However, I would not be opposed to having an RFC on this, providing that the people who actually participate in the RFC are people who are actually helpers on the channel and can understand pros and cons of changing or not changing. — kikichugirl oh hello! 03:31, 5 April 2015 (UTC)


I would be open to T13's above proposal that we set the default nicks to the page that the helpees came from. Here's the code, for example, I would use to replace WPhelp: {{#ifeq: {{SUBPAGENAME}} | sandbox | {{BASEPAGENAME}} | {{SUBPAGENAME}} }} This would set all nicks to the page name, except when the page is in a user sandbox, where it would default to the username. This allows for ease of finding drafts and/or usernames. The other alternative would be something like {{ifeq:{{SUBJECTSPACE}} | Draft | {{PAGENAME}} | {{BASEPAGENAME}} }} in which if the namespace is draft, then the page name is used, otherwise, the base page name is used. One more alternative would be to combine all of them to say userspace would give usernames, draft space would get draft names, and all others would give WPhelp or the base page name or something. This would be for all links under the AFC jurisdiction. Finally, User:PhantomTech seems to be almost done with a function that would allow us to grab their usernames, so I would defer if it comes to that, and works well. — kikichugirl oh hello! 20:41, 5 April 2015 (UTC)

Or maybe to simplify it all, {{#switch: {{SUBJECTSPACE}} | User = {{BASEPAGENAMEE}} | Wikipedia = {{BASEPAGENAMEE}} | Draft = {{PAGENAMEE}} | Template = T-{{PAGENAMEE}} | {{PAGENAMEE}} This is very namespace dependent, and if the namespace is not applicable, it would return the simple page name (and probably get truncated by IRC. Pinging an IRC op in invitation to comment. — kikichugirl oh hello! 21:02, 5 April 2015 (UTC)
  • I was thinking about this, and the biggest challenges would include first the IRC nick length and second the right for user's to stay somewhat anonymous (as they perceive it)(which was brought to my attention by Legoktm in a discussion someplace that I can't seem to find right now). SO, what I'm thinking is it could set the nick by default based on the following syntax: AfC|(Draft status)|(Page ID) where draft status is a one letter representation of the status of the draft based on the AfC submission codes (Declined, Reviewing, DrafT, Pending (since pending is actually no character)). {{PAGEID}} can be used with a script to quickly access the page by helpers or it can be set up with a key in -helpers to quickly get to the page. Alternatively, {{REVISIONID}} could be used and anyone could enter in the revision number using Special:Diff/659684355. I'd be happy to implement either one of these, I'm just opposed to merging all of the WPhelp nicks into the Guest nicks as that is a backwards movement. — {{U|Technical 13}} (etc) 10:01, 20 April 2015 (UTC)
Here's the important bit of the javascript to change the usernames, it would need some minor changes depending on how it was implemented
if (!mw.user.isAnon()) {
    // really this next line is the only one that's important
    var userNick = mw.user.getName().substring(0,12).replace(/\W/g, "_") + "-WP" + Math.floor(Math.random() * 89 + 10).toString();
    var ircLink = document.getElementById("ircLink").href;
    ircLink = ircLink.replace(/WPhelp\?/, userNick);
} else {
    // do something random...

PhantomTech (talk) 21:49, 5 April 2015 (UTC)

Reviewer comments lost on creation of the article[edit]

When a page passes review all the reviewer comments seem lost. I wish they could be posted to the newly created article's talk page. Is there any discussion about where these comments go, and the future development of AfC tools? I expected that at least the AfC creation template on the talk page would link to the reviewer comments, but it seems that they vanish. Blue Rasberry (talk) 11:54, 7 April 2015 (UTC)

We have had discussions in the past. I am neutral over it since the commentary exists in the history anyway. I forget whether we came to a conclusion. Fiddle Faddle 12:22, 7 April 2015 (UTC)
After the creation of Draft-space we did discuss the idea of moving the AFC "stuff" to the draft talk page but iirc the consensus was that doing so would inconvenience many (most) newbie editors as they often have no idea about Talk pages. Perhaps we could have the Accept script copy the review templates and comments to a hatted and suitably labelled section on the talk page when the draft is moved to mainspace? Roger (Dodger67) (talk) 07:00, 8 April 2015 (UTC)
I would be wholly in favour of that. It preserves in semi-plain sight but does not produce talk page clutter. Fiddle Faddle 07:58, 8 April 2015 (UTC)
I like Dodger67's idea. Onel5969 (talk) 12:22, 8 April 2015 (UTC)
I also support Roger's idea - the comments are useful if the article needs to be looked at again if it goes to AfD, for example. Ritchie333 (talk) (cont) 13:29, 8 April 2015 (UTC)
I predict it will be rare for this information to be useful to editors improving and maintaining an article. As Fiddle Faddle points out, the information is available in the submission's edit history; We just need to make it a bit easier to find. I would suggest including a link on the new article's talk page to the submission as it stood immediately prior to being accepted. Maybe the link could go in {{WikiProject Articles for creation}}. Maybe a separate info box along the lines of {{Merged-from}} is needed. ~Kvng (talk) 14:35, 15 April 2015 (UTC)
I was just about to suggest we include a dropdown box in {{WikiProject Articles for creation}} (the talk page banner for accepted submissions) that includes the reviewer comments. EoRdE6(Come Talk to Me!) 14:45, 15 April 2015 (UTC)
Before we get too excited(!) by this, do we have a willing person who can an will implement whatever solution is both neat and simple? If so we might move to pilot mode on an arbitrary version as a bold edit, quote possibly to the live script. No-one, I think, is going to be upset with a positive outcome as long as it is neat, and does not intrude. The information is not of huge use, and is simply historic. If the draft is moved without the script it will be "lost" anyway. 15:03, 15 April 2015 (UTC)Fiddle Faddle
Sure, I'd be willing to implement solutions that involve changes to the AFCH script. APerson (talk!) 16:35, 15 April 2015 (UTC)
The comments in some articles involve questions of copyright violations, often on articles being created by students using their real names to edit. I would rather not see that immortalized on the talk page of an accepted article. A choice of whether or not to include comments is one way to handle this. But I would prefer not having the mistakes of new users put on the talk page. We want to encourage new editors. StarryGrandma (talk) 21:22, 16 April 2015 (UTC)
I agree that often the comments would no longer be helpful (for example, if the page was blank the first time it was submitted). However, occasionally, a comment is still relevant, since we don't insist that drafts be perfect. Even if we don't get a consensus or an easy process for moving all the comments, a reviewer could choose to copy a specific comment to a talk page (ie: AfC comment: Please place the references as inline citations ---SomeReviewer) —Anne Delong (talk) 00:18, 17 April 2015 (UTC)
Let's not put the comments directly on the talk page of the accepted article. Let's put a link to a version of the submission that includes the comments on the talk page. ~Kvng (talk) 02:21, 17 April 2015 (UTC)
I agree we should not indiscriminately "preserve" all review commentary, most of it is meaningless once the article is accepted. Only comments that remain relevant to the mainspace article should be put on the talk page. Roger (Dodger67) (talk) 10:49, 17 April 2015 (UTC)

──────────────────────────────────────────────────────────────────────────────────────────────────── The advantage of adding a link to the last version before acceptance is that it could be done automatically, whereas reviewers' time would be taken up by selective preservation of comments. However, it may not be as straightforward as it seems at first glance. For example, will the link still work if the article is moved to a new title? Also, some of the AfC templates do something totally different when they find themselves in mainspace (here's an example: The decline reasons are no longer visible, including comments that were added to them using the custom decline. Comments saying things like "issues noted in the last decline have not been resolved" would be meaningless.—Anne Delong (talk) 11:59, 17 April 2015 (UTC)

If possible, we should modify these templates to do something more useful when they're viewed in the context of the history of an accepted submission. That may be less work and less error prone than having the script move them to the accepted article's talk page. With the templates as they are, it is difficult to interpret the development history of an AfC article and this is a problem. ~Kvng (talk) 14:18, 17 April 2015 (UTC)
The AFCH script already grabs the current revid before it makes any changes, so it shouldn't be too hard to add a link to that from the talk page. --Ahecht (TALK
) 15:20, 17 April 2015 (UTC)

I modified {{WikiProject Articles for creation}} so that it can take an optional |oldid= parameter. When this parameter is supplied, it adds a link to the last draft in the "This template was accepted..." line, as you can see at Template:WikiProject Articles for creation/testcases. This uses {{oldid2}} to bring up the old draft, so it shouldn't be bothered by things like page moves or histmerges. Is there consensus to have the AFCH tool fill in this field when placing the banner? I've mocked up the necessary patch here. --Ahecht (TALK
) 18:05, 17 April 2015 (UTC)

Ahecht, if you make a pull request, I'll merge it. APerson (talk!) 18:28, 17 April 2015 (UTC)
Yes check.svg Merged. Now all we need is for Theopolisme to get around to updating his userspace version, which will then update everyone else's version. APerson (talk!) 18:40, 17 April 2015 (UTC)
This is live; thanks for the ping. Theopolisme (talk) 21:31, 17 April 2015 (UTC)
This does the trick. Thanks Ahecht and APerson! if someone could make {{AFC submission}} do something more reasonable when it ends up in mainspace, that would be great. ~Kvng (talk) 16:53, 19 April 2015 (UTC)
Kvng, sure - do you mean something like showing the decline comments and users in a smaller font, perhaps hidden by a {{hat}} box? APerson (talk!) 18:54, 19 April 2015 (UTC)
Have a look at this example or Anne Delong's example above. The "reviewer is in the process of closing the request" message generated by the template is incorrect and I'm not sure what the purpose of this is. I think it would be fine if the template rendered as they do in Draft: or Wikipedia talk:Articles for creation/ namespaces but I'd be careful about making that change unless you understand the reason for the current behavior. ~Kvng (talk) 19:07, 19 April 2015 (UTC)
When the page is moved to mainspace, the AfC templates are supposed to be removed, but occasionally for some reason or another there is a delay or the process doesn't complete, and this prevents the decline text from showing in mainspace until the removal is done manually. Since the page is now picked up by Google, non-editors will likely start viewing it right away and may be confused by the pink decline templates. Instead they get a message that the page is new and will be fixed up shortly. Perhaps the template could be changed so that it only showed the mainspace message when it is on the current revision, and reverts to its lovely pinkness in the old revisions.—Anne Delong (talk) 23:01, 19 April 2015 (UTC)
I have proposed the change to allow the template to function in mainspace when viewing previous revisions. --Ahecht (TALK
) 17:33, 22 April 2015 (UTC)

AfC/R backlog[edit]

Wikipedia:Articles for creation/Redirects is suffering from a bit of a backlog at the moment. Could any helpers please use the script to process some requests? Rcsprinter123 (commune) @ 21:06, 9 April 2015 (UTC)

I have no idea how to do it with the script - or if it's even possible. Roger (Dodger67) (talk) 21:54, 9 April 2015 (UTC)
This requires the old script (which can be simultaneously loaded with the new script). Once at AFC/R, choosing "Review" (not Review AFCH) will load up the helpful interface. --LukeSurl t c 07:59, 10 April 2015 (UTC)
Can someone fix this backlog? Pickuptha'Musket (talk) 16:18, 17 April 2015 (UTC)


Hi, I need some advice. Do I just need to sign and I will be a participant of the project? Willy Weazley 23:51, 14 April 2015 (UTC)

First get up to 500 edits before signing up. Graeme Bartlett (talk) 00:29, 15 April 2015 (UTC)
More importantly, you need to have a good understanding of the basic article inclusion policies and guidelines on Wikipedia (primarily notability, verifiability and suitability) and the ability to communicate well with new editors. That's far more important than an arbitrary edit count, in my view. Ritchie333 (talk) (cont) 12:13, 17 April 2015 (UTC)

Notice of IRC proposal[edit]

There is a proposal related to Wikipedia's live help at Wikipedia:Village pump (proposals)#IRC help channel disclaimer. PHANTOMTECH (talk) 16:46, 15 April 2015 (UTC)


At Wikipedia:WikiProject Articles for creation#Advertisement, maybe also mention {{WPAFCInvite}}. Currently there's basically not a single WP page that mentions the template. -- (talk) 10:20, 18 April 2015 (UTC)

Yes check.svg Done ~Kvng (talk) 15:03, 18 April 2015 (UTC)

Thanks. Maybe there's a way to hide the template's "We need YOU!" heading from the Contents? Although probably not, since the heading is built in to the template and we're transcluding the whole template. -- (talk) 17:35, 18 April 2015 (UTC)
Fixed With this edit to the template, and this edit to the page. Thanks for noticing that! EoRdE6(Come Talk to Me!) 17:41, 18 April 2015 (UTC)
I've updated Template:WPAFCInvite to document your new feature. ~Kvng (talk) 19:12, 19 April 2015 (UTC)

Wikipedia talk:Proposed deletion (drafts) (Proposal to have a PROD system for drafts)[edit]

Given the work AfC does with Drafts, I thought it would be important to inform everyone there is a discussion going on at Wikipedia talk:Proposed deletion (drafts) about whether there should be a PROD system for Drafts. Interested editors are asked to respond there. Thanks! EoRdE6(Come Talk to Me!) 00:18, 20 April 2015 (UTC)


Regular reviewers will probably have encountered Buzzfeed put forward as a source for proving notability on quite a few occasions. This Reliable Sources Noticeboard search leads to some past discussion of Buzzfeed's reliability, with an overall feeling that it can be used as a source but with considerable care. However, the following article may cast further doubt on Buzzfeed's reliability, especially with regard to commercial and computing topics:

Another thing to watch out for is the text "This post was created by a member of BuzzFeed Community, where anyone can post awesome lists and creations" in Buzzfeed content. This of course indicates that the post in question cannot be used in proving notability. Such posts don't appear to be easily distinguishable by URL or title. Arthur goes shopping (talk) 09:27, 21 April 2015 (UTC)

Semi-protected edit request on 24 April 2015[edit]

it is a violent gun game (talk) 00:36, 24 April 2015 (UTC)

X mark.svg Not done as you have not requested a change. Please mention the specific changes in a "change X to Y" format. --I am k6ka Talk to me! See what I have done 02:27, 24 April 2015 (UTC)

Aging on articles[edit]

Not that it makes much difference, but there seems to be an issue on the aging for the submissions. Don't know exactly when it started, but it looks like between 2-4 days ago. There are many articles on the 0 days list which were actually submitted a couple of days ago. Onel5969 (talk) 17:07, 24 April 2015 (UTC)

@Onel5969: this is a known issue - the article's have a "null edit" every few days, which corrects the count. Mdann52 (talk) 17:10, 24 April 2015 (UTC)

Notability of sports players[edit]

I've noticed a few sports players on here, who's articles haven't been accepted due to notability concerns. However, sportspeople have their own criteria for notability, WP:NSPORT, which is generally easier to achieve than WP:GNG. Just wanted to inform reviewers that if drafts are about sportspeople, they should look at this criteria as well. Joseph2302 (talk) 15:55, 27 April 2015 (UTC)

there remains incomplete consensus on the relations of the two guidelines. While it is true that almost all AfDs for people who meet NSPORTS but not the GNG have closed as keep, results have been divided for players who meet the GNG but not NSPORTS. There might possibly be a trend to accepting them, but nobody cannot predict what the case will be in the future. DGG ( talk ) 01:46, 28 April 2015 (UTC)
I don't think we need to try and read the AfD crystal ball here. We don't need to be fully confident in articles we accept, we just need to believe they stand a >50% chance of being kept. I think it is reasonable to assume that WP:LIKELY is satisfied if either notability criteria is met. ~Kvng (talk) 14:11, 28 April 2015 (UTC)