Board Thread:Consensus Track/@comment-25356303-20180124194156/@comment-26074798-20180219045940

Atvelonis wrote: I suppose we could require both a certain number of bot edits and a certain number of functionally unique and productive tasks (perhaps 5–10) accomplished with the bot. This would ensure that the operator has the technical know-how to do several kinds of tasks. The only problem I can see with a user trying to prove they can do a task with a certain number of productive tasks is if the user only edits here, which I guess isn't a very big problem.

Flightmare wrote: From my point of view, it's best to achieve community approval per use, not per account. For any task, the bot should edit a single page (or maybe 10) to test if it is working as intended (yes, for every task). That raises one problem though, to kind of hop on what Atv said, all it takes is one look at Atv's bot task list shows a ton of things that have to be fixed; are we going to have to get Atv to check with the user base for things that are basic and rudimentary to fix, such as basic formatting issues and page renames?

If the bot is doing format changes to a new format, unless the change is extremely minor, odds are it's going to be in the moot anyway. It's not something we'd have to make a topic for.

To kind of backtrack a bit, I'm going to post a list of what seems to be generally agreed with for everyone so far. Call me out if I miss something/add something you guys disagree isn't kind of agreed on.
 * The community will vote on an application, with the following requirements and recommendations:
 * Being a staff member on the wiki, and or a helper is highly recommended.
 * The user who wants to run a bot should have experience editing here, in order to know the S&F. The number range so far is 2000-5000 for required edits, with 2000-3000 seeming to be more accepted.
 * To kind of copy/paste what I said: The user should be trustworthy.
 * If a user/bot meets all requirements except one, and that one is not vital, then an exception can certainly be made, just like with staff applications.

To hop on experience, which seems to be the real issue here, I think we can do both tasks completed and a set size, just like Atv said.