CZ:Bots: Difference between revisions
Jump to navigation
Jump to search
imported>Daniel Mietchen m (started) |
imported>Daniel Mietchen m (+undo option) |
||
| Line 9: | Line 9: | ||
# no bot run without bot account (however, we need a clear procedure how to apply for these accounts), though one could think of a solution in which any bot is allowed to be run from a user account if its application has been properly filed but received no opposing reaction within a week | # no bot run without bot account (however, we need a clear procedure how to apply for these accounts), though one could think of a solution in which any bot is allowed to be run from a user account if its application has been properly filed but received no opposing reaction within a week | ||
# one script per bot account (except for some well-defined minor jobs maybe that could be performed by a maintenance bot or even from some user accounts). | # one script per bot account (except for some well-defined minor jobs maybe that could be performed by a maintenance bot or even from some user accounts). | ||
# source code has to be posted on CZ before application for the corresponding bot account | # source code has to be posted on CZ before application for the corresponding bot account. | ||
# Bots should be run such that they can be undone by an existing bot, the command for which would have to be specified upon application. For scripts, this is probably too much to demand, so they should be limited in scope. | |||
# the bot approval should include a statement on the traffic volume and scope of the bot. | # the bot approval should include a statement on the traffic volume and scope of the bot. | ||
# turning user-run bot jobs into cron jobs should be a valid option for well-tested scripts, but this would require involvement of someone who actually has access to the servers. | # turning user-run bot jobs into cron jobs should be a valid option for well-tested scripts, but this would require involvement of someone who actually has access to the servers. | ||
Revision as of 03:21, 8 September 2009
As of September 2009, Citizendium does not have any official policy on running scripts or bots by means of the Python wikipedia robot framework, as explained here, though they have been run on occasion, and more frequently in recent months.
This page is intended to help draft such a policy. Feel free to rearrange or comment as you see fit. For background, see these two discussions in the Citizendium Forum.
Contact during the drafting phase: Daniel Mietchen
The main points the policy should address:
- we need more than one Citizen to administer this - we all have real-life obligations, but someone who took the time to write a bot script should be able to receive prompt reaction
- no bot run without bot account (however, we need a clear procedure how to apply for these accounts), though one could think of a solution in which any bot is allowed to be run from a user account if its application has been properly filed but received no opposing reaction within a week
- one script per bot account (except for some well-defined minor jobs maybe that could be performed by a maintenance bot or even from some user accounts).
- source code has to be posted on CZ before application for the corresponding bot account.
- Bots should be run such that they can be undone by an existing bot, the command for which would have to be specified upon application. For scripts, this is probably too much to demand, so they should be limited in scope.
- the bot approval should include a statement on the traffic volume and scope of the bot.
- turning user-run bot jobs into cron jobs should be a valid option for well-tested scripts, but this would require involvement of someone who actually has access to the servers.