Last modified: 2013-10-06 09:20:57 UTC
One of the things I believe are needed by many wikis is a queueing system where users can make requests for certain actions to be taken. Although it doesn't have to be limited to, I think the most common purpose of it would be performing actions that require user rights that the requesting user doesn't have. Think: * Deletion * Blocking * Moving * Adding/removing user groups (Patroller, Rollbacker, Admin, etc.) * etc. By having this in a nice interface it will provide many advantages: * It can be given an intuitive interface that users can learn to recognize across wikis. It would also have proper translation for many of the interface components. Make it easy to find the "request for deletion page" on any given wiki. * Saving time for admins ** being able to query a list of deletion request that haven't been resolved yet ** * Saving time for users ** being able to query requests by namespace, page title, user name etc. ** Finding information related to a log action (right now admins usually copy/paste permalinks into the log reason, which is annoying, time consuming and not user friendly, not to mention the fact that log reasons are not parsed which means other users then have to copy the link back from the reason into the addressbar to read it). Instead admins would be able to log with a link to something like [[Special:Requests/105123]]. Heck it could even be stored in the log_params so that it can be used to automatically mark a request as resolved once the action is performed. * Hooks for other maintenance tasks (in PHP for eg. bug 30134, but also through the API. I imagine an awesome dashboard for admins with stuff they can do!) * Uniform indication of status (perhaps even issue tracker like with status (assigned, open, resolved, etc.) * Sky is the limit :D The key is really in the details. The discussion part should probably hooked to LiquidThreads.
What's "log actions" mean here? Log items save a description of what sort of thing they were about, but that doesn't really relate to anything that would be a request queuing system.
I guess what Krinkle means is that the request queue would typically be used for actions that are also logged. But the description is indeed misleading. I suggest to change it to say "admin actions" or "privileged actions" or some such.
See https://www.mediawiki.org/wiki/Requests_for_comment/Tickets
[Removing RESOLVED LATER as discussed in http://lists.wikimedia.org/pipermail/wikitech-l/2012-November/064240.html . Reopening and setting priority to "Lowest". For future reference, please use either RESOLVED WONTFIX (for issues that will not be fixed), or simply set lowest priority. Thanks a lot!]
(In reply to comment #0) > * Saving time for admins Another time saver would be being able to mark requests as "under review" to avoid duplicating work, see https://en.wikipedia.org/wiki/User:Crazycomputers/Problems_with_WP:AIV
