Last modified: 2008-09-17 23:37:25 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 14507 - Allow Commons CheckUsers & bureaucrats to grant and revoke ipblock-exemption
Allow Commons CheckUsers & bureaucrats to grant and revoke ipblock-exemption
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
Site requests (Other open bugs)
unspecified
All All
: Normal enhancement with 4 votes (vote)
: ---
Assigned To: Brion Vibber
http://commons.wikimedia.org/w/index....
: shell
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-06-11 12:49 UTC by Herby
Modified: 2008-09-17 23:37 UTC (History)
7 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Herby 2008-06-11 12:49:04 UTC
Specifically this will allow project checkusers to block Grawp ranges while allowing the legitimate users on Commons access and given the recent activity of this vandal it would be good if this could be done quite quickly.

Commons users generally do not have a great interest in vandalism so we would not expect a lot of people to comment.  All project checkusers are aware of this suggestion.  Longer term it will allow the project to deal with range based vandalism more effectively.  Allowing bureaucrats to deal with this too would mean that there would be others available to deal with issues if required. Thanks
Comment 1 Herby 2008-06-24 15:04:47 UTC
I confess I took this a fairly straightforward.  The issue has been solved for en wp with admins able to allow BlockExempt.  Any chance this could get done for Commons so that we can control some of the hard core vandals better?  Cheers
Comment 2 Cometstyles 2008-08-10 12:31:06 UTC
it has also been implemented successfully on Meta too, no need to delay this request :)
Comment 3 Herby 2008-08-10 13:03:06 UTC
Yes - given the Commons request was in sometime before the Meta one some action on this would be appreciated/appropriate.

Thanks
Comment 4 Herby 2008-08-16 07:58:36 UTC
Can I ask nicely why - given the same thing has been done for Meta - this has not been done for Commons yet?

Thanks
Comment 5 Casey Brown 2008-08-16 13:38:16 UTC
I'm sure jeluf just overlooked it... *makes some noise so that JeLuF sees it the next time he does shell/root requests*
Comment 6 Larry Pieniazek 2008-09-14 12:44:20 UTC
Bump. (I know, bumps are bad form but this should be an easy tweak, right?... Commons could REALLY use this. Thanks!)
Comment 7 Herby 2008-09-15 12:44:24 UTC
I have had an email from an en wp user who has block exempt there who wishes to edit on Commons (they are on Grawp's range).

Can we get something done about this please.
Comment 8 Cometstyles 2008-09-16 02:50:29 UTC
I asked brion to personally look into this today and he said he might do it soon..  *fingers crossed*
Comment 9 Herby 2008-09-17 10:57:04 UTC
User:Suntag is unable to create an account on Commons because he edits from Grawp's range.  They have blockexempt on en wp
Comment 10 Herby 2008-09-17 10:58:27 UTC
User:Slakr requires blockexempt on Commons.  The range they edit from requires blocking per cross project CU issues.  I have block exempted them on Meta.
Comment 11 Cary Bass 2008-09-17 23:11:46 UTC
I would like to add that often there are open proxies and TOR nodes that are blocked on Commons that are in use by contributors in blocked areas like China (sometimes) and Iran (sometimes) and elsewhere.
Comment 12 Brion Vibber 2008-09-17 23:37:25 UTC
Done.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links