User talk:Timotheus Canens/Archives/2014/11
 | This is an archive of past discussions with User:Timotheus Canens. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
The Signpost: 05 November 2014
The Signpost: 12 November 2014
- In the media: Amazon Echo; EU freedom of panorama; Bluebeard's Castle
- Traffic report: Holidays, anyone?
- Featured content: Wikipedia goes to church in Lithuania
- WikiProject report: Talking hospitals
Copyright checks when performing AfC reviews
Hello Timotheus Canens/Archives/2014. This message is part of a mass mailing to people who appear active in reviewing articles for creation submissions. First of all, thank you for taking part in this important work! I'm sorry this message is a form letter – it really was the only way I could think of to covey the issue economically. Of course, this also means that I have not looked to see whether the matter is applicable to you in particular.
The issue is in rather large numbers of copyright violations ("copyvios") making their way through AfC reviews without being detected (even when easy to check, and even when hallmarks of copyvios in the text that should have invited a check, were glaring). A second issue is the correct method of dealing with them when discovered.
If you don't do so already, I'd like to ask for your to help with this problem by taking on the practice of performing a copyvio check as the first step in any AfC review. The most basic method is to simply copy a unique but small portion of text from the draft body and run it through a search engine in quotation marks. Trying this from two different paragraphs is recommended. (If you have any question about whether the text was copied from the draft, rather than the other way around (a "backwards copyvio"), the Wayback Machine is very useful for sussing that out.)
If you do find a copyright violation, please do not decline the draft on that basis. Copyright violations need to be dealt with immediately as they may harm those whose content is being used and expose Wikipedia to potential legal liability. If the draft is substantially a copyvio, and there's no non-infringing version to revert to, please mark the page for speedy deletion right away using {{db-g12|url=URL of source}}. If there is an assertion of permission, please replace the draft article's content with {{subst:copyvio|url=URL of source}}.
Some of the more obvious indicia of a copyvio are use of the first person ("we/our/us..."), phrases like "this site", or apparent artifacts of content written for somewhere else ("top", "go to top", "next page", "click here", use of smartquotes, etc.); inappropriate tone of voice, such as an overly informal tone or a very slanted marketing voice with weasel words; including intellectual property symbols (™,®); and blocks of text being added all at once in a finished form with no misspellings or other errors.
I hope this message finds you well and thanks again you for your efforts in this area. Best regards--Fuhghettaboutit (talk) 02:20, 18 November 2014 (UTC).
Sent via--MediaWiki message delivery (talk) 02:20, 18 November 2014 (UTC)
Thursday December 4: NYC Wiki-Salon and Skill Share
| Thursday December 4: NYC Wiki-Salon and Skill Share | |
|---|---|
 You are invited to join the the Wikimedia NYC community for our upcoming wiki-salon and knowledge-sharing workshop in Manhattan's Greenwich Village.
Afterwards at 8pm, we'll walk to a social wiki-dinner together at a neighborhood restaurant (to be decided). We hope to see you there!--Pharos (talk) 07:11, 27 November 2014 (UTC) | |
(You can unsubscribe from future notifications for NYC-area events by removing your name from this list.)
Notice of appeal
This is to notify you of an appeal against an enforcement action that was made by you: 1. Regards Mooretwin (talk) 13:16, 27 November 2014 (UTC)
The Signpost: 26 November 2014
- Featured content: Orbital Science: Now you're thinking with explosions
- WikiProject report: Back with the military historians
- Traffic report: Big in Japan