Wikipedia:WikiProject Guild of Copy Editors/Blitzes/October 2015


 * 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.

This Copy Editing Project Blitz is a one-week-long effort of the Guild of Copy Editors to reduce the backlog of articles listed on the GOCE Requests page. It will begin on 18 October 2015, at 00:00 (UTC) and will end on 24 October 2015, at 23:59 (UTC).

The theme of this blitz is:
 * To reduce the number of outstanding requests on our requests page. Good Article nominations (GANs) and Featured Article candidates (FACs) require careful editing by experienced copyeditors, with the prose bar higher for FACs than for GANs.

Blitz participants can earn barnstar awards based on the number of articles—and the word counts of the articles—they copy edit. Awards will be given out once the blitz has finished.

The blitz is open to all; you don't have to be a member of the Guild of Copy Editors to participate. You must, however, be competent in your use of English grammar, spelling and punctuation. We strongly advise you to read Wikipedia's guide to basic copy editing before you begin working. If you're unsure about spelling, grammar or punctuation, consult the Wikipedia Manual of Style. Skilled use of English is especially important for articles listed on the Requests page.

Blitzes are under the purview of the Guild's coordinators. The blitz's lead coordinator is Jonesey95 (talk), who is assisted by Baffle gab1978 (talk), KieranTribe (talk), Miniapolis (talk) and Pax85 (talk). If you have any questions, leave a message on the blitz's talk page.

For brief instructions on how to record your work, see below. For full instructions, visit the main blitz page.

Full instructions, tips, and awards
Full instructions for participants, tips, help for new copy editors, useful tags, and details of the many barnstars available for the blitz can be found on the main blitz page. Please read this page carefully before you begin. To sign up, please use the form in the Signing up section below.

Reviewing
GOCE coordinators and other experienced Guild members will carry out random checks to ensure that copy edits are of a satisfactory standard. If you are willing to help with reviewing, please sign up below.

10% of each participant's copy edits from the backlog should be checked, and all copy edits from the Requests page should be reviewed, time permitting. Please choose articles at random and do not inspect your own copy edits. After checking articles, place a checked template after the article on the listing and sign your username with four tildes. If a rough consensus finds that a copy edit is not of an acceptable standard, the tag will be re-added and the word count of the reviewed article will be deducted from the editor's total. The reviewer may give advice on how the edit could have been improved without penalizing the editor. Please raise any questions on the Coordinators' talk page.

Signing up
To sign up for the blitz, click the button below. This will create a subsection in the Totals section for you to record your copy edits. The previous blitz's rollover totals are located here.

=Totals= How to record articles you have copy edited:
 * Remove any extant copyedit tags from the article.
 * When you sign up, your section is automatically populated with and :
 * Article titles go in wikilinks . List the article's full title, not an abbreviated version.
 * Article word counts go in round brackets : use this script to get the page's word count.
 * Place articles you're working on on the Working line. When you've finished your copy edit, change Working to Completed
 * Place any comments between the article title and the word count.
 * Do not list articles on which you have placed GOCEreviewed instead of copy editing them, or which needed no copy editing.
 * If you want your work checked, you can request it on the blitz talk page.

Properly completed records look like this in the edit window:

and like this on the rendered page: