Last modified: 2007-11-20 05:53:47 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 12015 - Give rollback to ClueBot on enwp.
Give rollback to ClueBot on enwp.
Status: RESOLVED INVALID
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
http://en.wikipedia.org/wiki/WP:VPT#G...
: shell
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-11-17 21:42 UTC by Cobi
Modified: 2007-11-20 05:53 UTC (History)
5 users (show)

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


Attachments

Description Cobi 2007-11-17 21:42:07 UTC
There is consensus shown at the URL for this bug report that there is consensus to give w:en:User:ClueBot access to rollback.  This could be done by creating either a rollback group, or an AVBot group and assigning ClueBot to that group.
Comment 1 Aaron Schulz 2007-11-17 22:19:33 UTC
This should wait until the API branch stuff is merged. It should be using an API revert with a summary that can be send via url parameters. An 'apirollback' right for an 'AVbot' group sounds OK.

Still, it would require a steward or 'userrights' interface access unless some UI was made.
Comment 2 Cobi 2007-11-17 22:24:11 UTC
(In reply to comment #1)
> This should wait until the API branch stuff is merged. It should be using an
> API revert with a summary that can be send via url parameters. An 'apirollback'
> right for an 'AVbot' group sounds OK.
> 
> Still, it would require a steward or 'userrights' interface access unless some
> UI was made.
> 

As far as I understand it, the index.php rollback is just a GET operation as well.  And ClueBot already has to interface with index.php for editing.
Comment 3 Robert Leverington 2007-11-17 22:41:21 UTC
(In reply to comment #2)
> (In reply to comment #1)
> > This should wait until the API branch stuff is merged. It should be using an
> > API revert with a summary that can be send via url parameters. An 'apirollback'
> > right for an 'AVbot' group sounds OK.
> > 
> > Still, it would require a steward or 'userrights' interface access unless some
> > UI was made.
> > 
> 
> As far as I understand it, the index.php rollback is just a GET operation as
> well.  And ClueBot already has to interface with index.php for editing.
> 

I believe Voice of All was refering to adding the user rights, not the actual process of rollback. It would be much more efficent from a development and time of stewards\sysadmins perspective to code rollback in your back - which would not be too difficult.
Comment 4 Majorly 2007-11-18 14:36:59 UTC
(In reply to comment #0)
> There is consensus shown at the URL for this bug report that there is consensus
> to give w:en:User:ClueBot access to rollback.  This could be done by creating
> either a rollback group, or an AVBot group and assigning ClueBot to that group.
> 

I see no consensus there.
Comment 5 Daniel Cannon (AmiDaniel) 2007-11-20 05:53:47 UTC
There does not appear to be a clear consensus on enwiki for enabling a rollback-only group nor for giving the bot rollback through any other means. Marking as INVALID until a consensus can be found.

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


Navigation
Links