People who are very good at finding spam only really need permission to block the spammers, not edit any node on drupal.org. I uploaded a module I built that will add a link that merely toggles roles and active/blocked to my sandbox: http://cvs.drupal.org/viewvc.py/drupal/contributions/sandbox/deekayen/mo...
It's not exactly ideal for d.o, but might be a start. User Read-Only might be another option to start from. The complex issue in this is that the spam hunters need to be able to edit profiles, to delete profile spam as well, which is what User Read-Only could help with. I have a loose policy on adding maintainers - so if someone wants to take this task up for d.o, just tell me when you add yourself as a maintainer if you hop on User Read-Only.
Comments
Comment #1
gerhard killesreiter commentedprofile spam does not need to be deleted, it is inaccessible once the user account is blocked.
Comment #2
bonobo commentedIIRC, fasttoggle is used to do this on g.d.o -- http://drupal.org/project/fasttoggle
Comment #3
gregglesYeah, +1 for fasttoggle and for this concept in general. Just give "spam fighters" the ability to use fasttoggle to block users.
Comment #4
silverwing commentedIs fasttoggle something still worth going forward with?
Comment #5
silverwing commentedclosing as a duplicate of #558858: Deploy fasttoggle to drupal.org for user blocking and node unpublishing