Wikifunctions:Bots

This page is currently a draft. More information pertaining to this may be available on the talk page.

Translation admins: Normally, drafts should not be marked for translation.

Bots are accounts which hold the bot user group. There are currently 6 bots on Wikifunctions.

Overview

Bots (also known as robots) are automated tools used to make edits without the necessity of human decision-making.

How to request bot status

Main page: Wikifunctions:Requests for user groups

Users may apply for an account to be in the bot group at Wikifunctions:Requests for user groups#Miscellaneous requests. However this user group is unlikely to be given out until a process for granting is developed.

Requirements

Due to Wikifunctions being a new project, there are no requirements or guidelines that the community have decided on.

Granting

Presently, only stewards can grant or remove bot status from an account.

Permission to run a bot

All bots running on Wikifunctions must have advance permission to do so. Permission is needed whether or not the bot requires a bot flag.

Permission will be granted only in respect of the tasks that are listed in the bot request (tasks can be fairly general). Bots must not be used to carry out different tasks for which permission has not been granted. Of course, bot operators are not expected to re-apply every time they want to implement a small alteration, but if the bot's functionality has been changed to carry out some significant new task then a new request should be filed.

MediaWiki software-defined bots

Some bots are used by the MediaWiki software itself and not managed by any user.

MediaWiki message delivery: provided by MediaWiki's MassMessage extension and Special:MassMessage
FuzzyBot: provided by MediaWiki's Translate extension, performing automated tasks for translation administrators
WikiLambda system: re-orders approved implementations of a function to prioritize the fastest ones first

Bot accounts

Bots must be run from a separate user account from that used for general editing by the bot operator. In order to identify the account as a bot account, the username should normally include the word "bot".

The contributions of a bot account remain the responsibility of its operator, who must be prominently identifiable on its user page. The bot operator is responsible for the prompt repair of any damage caused by a bot which operates incorrectly. Bot operators must ensure that they make themselves available for dealing with user queries relating to the bot, and that they promptly fix any identified bugs. Bot operators are encouraged to use a secure login method.

Information on bots

The bot's user page should identify the bot as such, preferably using the {{bot}} template. The following information should be clearly provided on that page, or on a page linked to it. Please make sure you have listed all this information before requesting bot permission.

Who the creator/operator is and how they can best be contacted
Details of the bot's task or tasks
Whether the bot is manually assisted or runs automatically
When the bot operates (continuously, intermittently, or at specified intervals)
The bot's maximum edit rate (e.g. edits per minute)
The language and/or program that it is running

Posting the source code of the bot is strongly encouraged.

Bot speed

Bot operators should recognize that a bot making many requests or editing at a high speed has a much greater effect than the average contributor. Bots should therefore be conservative in their editing speed. A bot carrying out non-urgent tasks should not edit more frequently than once every 5 seconds. Bots carrying out urgent tasks, such as reverting vandalism, may edit faster. Unflagged bots should edit more slowly than flagged bots as their edits are visible in watchlists, and high-speed editing will swamp other users' lists.

Blocking of bots

Any admin may block a bot – without the autoblock option set – that is misbehaving if the operator is not immediately available to deal with the issue. In principle, an unapproved bot may be blocked, though in practice unless the bot is doing harm the operator should normally be asked to submit a retrospective bot request. If it is noticed that a bot is being used for tasks which are significantly different from those specified in the original bot request, the bot operator should be asked to make a fresh bot request which specifies the new tasks.