User:Matthewedwards/FL

These step-by-step instructions show the FL directors and their delegates the exact steps to maintain Featured lists, Featured list candidates and Featured list removal candidates, their subpages and logs, and how to close and archive FL nominations.

Incorporates bits from my old FLC and FLRC closing instructions, Featured list removal candidates/Closing instructions, and User:SandyGeorgia/FA_work, User:SandyGeorgia/sandbox.

FLC maintenance

 * Nothing in this section is essential to the FL process; it's just routine "stuff". The only thing that determines whether a list is FL is whether it was added to or removed from WP:FL by the Featured list directors or their delegates. The rest is for the convenience of other editors.

New FLC listings
All new WP:FLC listings should be checked:
 * 1) If there is one, the previous FLC should be listed and pipe-linked with the standard terminology "previous FLC" (to work with scripts).
 * 2) Check the talk page of every new FLC for:
 * 3) the FLC template at the top of the page (many nominators forget, and it should be the template, not a subst.
 * 4) old peer reviews archived and closed (if not, leave a note either at the talk page, at the FLC page, or both)
 * 5) articles may not be at PR, GAN and FLC at the same time
 * 6) convert old DYK templates (example)
 * 7) general talk page cleanup, banners, dykdate added to articlehistory if present, and all templates needed to complete articlehistory in place and complete, old afds dealt with (sample). Clean up missing TOC when needed, example.  Update depending on GimmeBot, who will build articlehistory?
 * 8) Notify the WikiProjects mentioned on the talkpage of the FLC, and any logical ones not posted at talk page -- We're low on reviewers, so their input could be valuable, esp. regarding style guidelines. Should expect more drive-by votes, though, so have to be vigilant.

Ongoing FLCs
Check WP:FLCs regularly for
 * 1) Unsigned entries (surprisingly frequent, a sig needs to be attached to every declaration, add unsigned as needed, and often, when discussion gets long, the  template is needed to attach a declaration to its owner, sample).
 * 2) Graphics (see the WP:FLC instructions, they slow down the page and often need to be removed)
 * 3) Sub-sections (see the WP:FLC instructions, they need to be removed when inserted)
 * 4) Inappropriate strikes and caps (see the WP:FLC instructions, nominators should not strike others' comments, and caps should be used sparingly).
 * 5) Monitor for double declarations of Support or Oppose, or unbolded and almost hidden supports or opposes.
 * 6) Update Featured list candidates/backlog/items

Promoted nominations

 * 1) Remove the transcluded discussion from WP:FLC. While removing it, mention the name of the list in the edit summary that it is being promoted.
 * 2) Transclude the discussion to this month's promotion log
 * 3) Update the log tallies in Featured list log.
 * 4) Update Featured lists, including the count at the top.
 * 5) Update Former featured lists, including the count at the top (rarely necessary)
 * 6) Add a notice to Template:Announcements/New featured pages, cycle the entries, removing as many as has been added.
 * 7) Add a notice to Goings-on.
 * 8) Update Featured list candidates/backlog/items
 * 9) Update Featured list candidates/Closure log
 * GimmeBot will complete the closure by updating the list's talk page, adding the FL star, archiving the FLC page and adding a closure box.

Failed nominations

 * 1) Remove the transcluded discussion from WP:FLC. While removing it, mention the name of the list in the edit summary that it is being archived.
 * 2) Move the transcluded flc page to the top of the current month's failed log
 * 3) Update the log tallies in Featured list log.
 * 4) Update Featured list candidates/backlog/items
 * 5) Update Featured list candidates/Closure log
 * GimmeBot will complete the closure by updating the list's talk page, archiving the FLC page and adding a closure box.

Withdrawals

 * 1) Remind the nominator not to remove the FLC template, with a link to WP:FLC/ar by adding FLCClosed to the bottom of the nomination.

Nominator-withdrawn FLCs containing Opposes: to be recorded in articlehistory

 * 1) Make sure there's a note on the FLC, linking to the request to withdraw from the nominator
 * 2) Remove transcluded FLC page from WP:FLC. While removing it, mention the name of the list in the edit summary that it is being archived.
 * 3) Move the transcluded FLC page to the top of the current monthly failed log, with an edit summary saying withdrawn (for my future stats, distinguish from a fail).  Moving it to the monthly archive file will trigger GimmeBot to do the rest.
 * 4) Make sure the  template is still on the article talk page, so Gimmebot won't stall.
 * GimmeBot will complete the closure by updating the list's talk page, archiving the FLC page and adding a closure box.

Premature FLCs withdrawn with no opposes, or no opposes of substance

 * Complete sample
 * It's a judgment call as to whether the FLC should be recorded into articlehistory.
 * 1) Remove transcluded FLC page from WP:FLC
 * 2) Do NOT move to monthly archive page
 * 3) Move the FLC page to the next open N, /archiveN
 * 4) Re-open the original FLC file to (a) remove the redirect, (b) prep it ready for next submission by adding the page header ===Article name=== and (c) link to previous FLC withdrawn (no uppercase "p" all uppercase "FLC", this is for some other scripts)
 * 5) Go to the article talk page. (a) Remove the FLC template from the article talk page, (b) leave a comment on the talk page in a new section noting that the flc was withdrawn, with a link to the archive file.
 * 6) If necessary, notify the nominator with the FLC withdrawn template or a customized message.
 * GimmeBot will not do anything with this closure

New FLRC listings
All new Featured list removal candidates listings should be checked:
 * 1) Make sure the FLRC is actually a Featured list (sometimes nominators meant to submit to Peer review or WP:FLC) and complies with the instructions about three to six months between promotion and review and several days after mainpage appearance:
 * If it doesn't belong at FLRC:
 * Remove the transclusion from Featured list removal candidates
 * Remove the template from the article talk page
 * Leave a note for the nominator
 * Decide if the FLRC has to be maintenance or author-deleted, or moved to a FLC or PR file, and transcluded there.
 * 1) Make sure notifications are done per the Featured list removal candidates instructions, if not, prompt the nominator to do so.
 * 2) Make sure the templates are in order on the article talk page, including FLRC at the top of the page (the template, not a subst).

Ongoing FLRCs

 * 1) Monitor for premature declarations of Keep/Remove and remind that Keep/Remove !votes should be made after concerns have been met or sufficient time has passed where concerns have gone ignored
 * 2) Monitor daily for requests for feedback and more information
 * 3) Prompt the nominator if needed to return to the FLRC for feedback.

Keeps

 * 1) Transclude the discussion to the current month's Kept section of the removal log
 * 2) Update the log tallies in Featured list log.
 * 3) GimmeBot will complete the closure by updating the list's talk page, archiving the FLRC page and adding a closure box.

Delists

 * 1) Remove the transcluded discussion from Featured list removal candidates. While removing it, mention the name of the list in the edit summary that it is being delisted.
 * 2) Transclude the discussion to the current month's Delisted section of the removal log
 * 3) Remove the list from Featured lists, and update the count in the project page's introduction.
 * 4) Add the list to Former featured lists under the same section heading it was under at Featured lists, and update the count in the project page's introduction.
 * 5) Update the log tallies in Featured list log.
 * 6) GimmeBot will complete the closure by updating the list's talk page, archiving the FLRC page and adding a closure box.
 * 7) Update Featured list candidates/Closure log

Other FL-related tasks

 * Nothing in this section is essential to the FL process; it's just routine "stuff". The only thing that determines whether a list is FL is whether it was added to or removed from WP:FL by the directors or delegates. The rest is for the convenience of other editors.

Sync FLC and FLRC categories

 * Check Category:Wikipedia featured list candidates and Category:Wikipedia featured list removal candidates to make sure they agree with WP:FLC and WP:FLRC.
 * If the numbers don't match:
 * 1) look for the nontranscluded entry.
 * 2) Often, the nontranscluded entry will be a driveby nom from a new editor who hasn't returned.
 * 3) If so, a decision has to be made about whether to transclude it to FLC or FLRC, or leave a note to the editor about possibly maintenance deleting the page.
 * If the page is maintenance deleted, be sure to also remove the or  template from the talk page.
 * 1) If not, transclude the FLC or FLRC to WP:FLC or WP:FLRC, and notify the nominator.  The nominator should be reminded to update the timestamp to reflect when the FLC was actually submitted, or add a note to the FLC to that effect.

Monthly
Open new monthly archive files at Featured list candidates/Featured log, Featured list candidates/Failed log, and Featured list removal candidates/log, adding featured list log to the top of each.

GimmeBot steps
'''GimmeBot steps for archive/promote FLCs and Keep/Remove FLRCs. Blue text is links to examples and edit summaries'''

If GimmeBot ever retires

 * Uncertain still who will pick up GimmeBot tasks.

Other things to consider
 * Manually archive WP:GO every Saturday night/Sunday morning UTC (the instructions are in the page). Otherwise, close and tag WP:GO as Historical, see this discussion. Gimmetrow had just coded GimmeBot to do the weekly archiving at WP:GO, agreeing to do it after years of Raul and Sandy searching for someone who would take on the weekly archiving of that page. Shortly after he wrote the code, an unannounced change was made at the Wikimedia level. In the discussion that ensued, it was found that WP:GO isn't really used by anyone, is info that is duplicated elsewhere anyway, and probably isn't worth the maintenance effort. As of September 2013, however, it is still being used.
 * FLC and FLRC archiving without GimmeBot, either manually complete the steps as above, or go back to the old (pre-GimmeBot) method:
 * 1) As now, FLC and FLRC directors/delegates indicate when a FLC/FLRC has closed by moving the transcluded file to archive and adding/removing the article at WP:FL and WP:FFL.
 * 2) Tag closed processes as in Step 1.
 * 3) Move, archive and clear redirects per Steps 2–7.
 * 4) Add/remove FL stars per Step 8
 * 5) Step 9 is replaced.  See Template talk:ArticleHistory/work.
 * 6) After a FLC/FLRC is closed by moving it to archive, replace the FLC or FLRC template on the talk page with the appropriate template:  FL, FLCfailed or FFL.
 * 7) Another editor or new bot will have to later convert the templates to articlehistory.
 * 8) Update WikiProject class-assessments per Step 10
 * 1) Who will check for renames on WP:FLs, failed FLs and WP:FFLs so the talk page links correspond with the FLC and FLRC logs?
 * 2) Who will update articlehistory?