[Commons-l] Please don't spam user-talk pages with generic warnings

Brianna Laugher brianna.laugher at gmail.com
Tue Jul 18 15:04:27 UTC 2006


Please don't spam user-talk pages with generic warnings. (No source/no
license/copyvionote)
Why? Because it's counter-productive and therefore a waste of your time.

If you notice a user already has a dozen recent warnings, or if you've
got 10 more to add, instead of adding another one which they're just
as likely to ignore, take the time to write a short sharp warning
explaining
* specifically what they're doing wrong (not "violating copyright" -
"uploading logos" "uploading screenshots" "uploading random images
from the web")
* why it's wrong (like: source is require for all images - logos are
considered unfree - screenshots don't take any new copyright)
* relevant policy pages (usually Commons:Licensing)
* where they can ask for help (their talk page, if you watch it, your
talk page, Commons:Help desk / Village pump in their language)
* the principle of WHEN IN DOUBT, ASK BEFORE UPLOADING.
* that if they upload any more files and ignore what you've taken the
time to say, then they will be blocked.

And if they do that, then block them. If you're not an admin, ask one
to block them.

While they're blocked they can still edit their talk page. This is a
good chance to drill home source/licensing requirements and the like,
if they stick around.

The aim of the warnings is to try and make users understand the
importance of various copyright requirements. Spamming their talk page
is not further to that aim, so it should be avoided. "Notifying the
uploader" is not the real aim: making them understand is.

As a rough guide, I would say first block, 1 or 3 days. Second block,
3 days or a week. Third block, a week or a month. Fourth block, I'd
want to know a very good reason why it shouldn't be permanent. It all
depends on the specific circumstances of course, like exactly how many
images they're uploading, if they're giving false licenses, if they're
responding to messages and warnings, if there's a language barrier,
etc.

regards,
Brianna
user:pfctdayelise



More information about the Commons-l mailing list