Reconcile spam report instructions

This issue is to advocate some unification of instructions for d.o spam reporting, in the interests of prompting users to report spam consistently and reduce the burden on admins/maintainers.

The overall answer may be a single page providing instructions on how to report spam for each category that needs different handling, probably:

• d.o Docs article edit spam
• d.o Docs comment spam
• groups.d.o all spam?

Instructions could include:

Before reporting

• Search for a spam report for that user

When reporting:

• Put "Spam" and offending user name in the Summary field, to allow easy search
• Use Component = Spam

... and so on. Then all project or issue pages where a spam reporter might go could include a link to that spam instructions page.

In the interim, here are some problems I encountered:

"Documentation issue reports" conflicting instructions

I see three different instructions on where to report spam.

1. Page drupal.org/node/24565 "Documentation issue reports" says "The documentation issues page (d.o/project/issues/documentation) is used [for] Documentation page [...] report of spam".
2. Later on the same page, the instruction is to start the issue report at a different page: d.o/node/add/project-issue.
3. Then in http://drupal.org/node/1471514 jhodgdon says "please report spam to the Drupal.org webmasters project".

I suspect the idea is really to report Documentation spam as follows:

• Article content spam edit: report to d.o/project/issues/documentation.
• Comment spam: report to webmasters project

Anyhow, I think d.o/node/24565 "Documentation issue reports" could be revised to prompt spam reporters to report in a maximally helpful way.

/project/documentation

Paralleling the comments above, again spam reporters could report more helpfully if page drupal.org/project/documentation spelled out where to report spam for article bodies vs comments.

/project/webmasters

This page mentions "issue tracker that you can use to report spam", but then provides no link to do so. Instead, one must read all over the page to find the very-light-font text which hints "please search before submitting a new issue". OK, search for... "spam"... which fetches a list of issues ordered by "relevance" (possibly years old). Yes, with more fiddling you can get a list in reverse-chron order, and maybe it'll occur to you to search on spammer username... but the semi daunting nature of the issue search form works to put off a reporter, or put off their searching for a duplicate.

If webmasters is the official place to report spam, then it would benefit from
-- instructions I described above (put spammer username in Summary; Component=Spam).
-- A search slot specifically for spam:
Button: [Search for spam] [Enter username]
... which would return the issue list, using Component=Spam, reverse-chron, and Search for=username