Code of Conduct/Bots: Difference between revisions

From MusicBrainz Wiki
Jump to navigationJump to search
Line 16: Line 16:


==Bot code==
==Bot code==
We encourage that the code for every bot is open-sourced or at least made public, and that it is linked from that bot's user page. Other bot owners, and the community in general, are encouraged to check, review and (if necessary) propose patches for them. If the bot owner won't make the code available for checking from the beginning, and the community is unhappy with the edits the bot makes, the source code may be called into question. If the owner is unable to provide this, the bot account may be terminated.
We encourage that the code for every bot is open-sourced or at least made public, and that it is linked from that bot's user page. Other bot owners, and the community in general, are encouraged to check, review and (if necessary) propose patches for them. If the bot owner doesn't make the code available for checking from the beginning, and the community is unhappy with the edits the bot makes, the source code may be called into question. If the owner is unable to provide this, the bot account may be terminated.

Revision as of 01:28, 23 July 2012

Proposed rules for bots:

Edit limits

Open edits

There is a recommended limit of 2000 open edits and a hard limit of 2500 open edits per bot at the same time. Any bot which goes over the hard limit will be blocked.

Daily edits

Bots shouldn't make more than 1000 edits (be it normal edits or autoedits) per day - that allows users that want to check them all to do so.

Voting

Bots themselves are not allowed to vote on any edits (to be implemented via code).

Yes-voting on bot edits is discouraged unless the voter can 100% confirm they're correct, since it helps them to go through with less eyes on them. If a bot edit gets rejected, a non-bot user can always re-enter it if he feels it's correct - reverting the edit is much more difficult, especially for removals and merges. This also applies to the bot owner: no matter how much you trust your code, manually verify everything before voting yes.

Bot owners should read and react to edit notes on their bot edits in a reasonable amount of time. If you're not going to be able to do so, don't run your bot until that changes. Ignoring editor votes and comments on your edits is a great way for your bot to quickly lose the support of the community.

Bot code

We encourage that the code for every bot is open-sourced or at least made public, and that it is linked from that bot's user page. Other bot owners, and the community in general, are encouraged to check, review and (if necessary) propose patches for them. If the bot owner doesn't make the code available for checking from the beginning, and the community is unhappy with the edits the bot makes, the source code may be called into question. If the owner is unable to provide this, the bot account may be terminated.