User:NoSeptember/adminbots

Ideas on the procedures we should use with respect to the sysopping of adminbots:

1. Approve the sysopping of the underlying code, not the specific bot or the specific admin that is to run it.
   • First the functionality is approved by the bot approval procedure, then an RfA would be conducted for sysopping bots with the approved code, not limited to the one bot of the user that created the code or on which computer that code would be located.

   • Example: AdminA writes and gets approval for the code for AdminABot. Other admins agree to support bots with the same code. Once the RfA for the specific code is approved, AdminABot, AdminBBot and AdminCBot are all sysopped as bots for that specific function. If AdminABot has hardware issues, AdminB can promptly take over the job with AdminBBot.
   • Should the code become obsolete or the community decides that the bots should stop running this task, all bots sysopped for the purpose of running that code would be desysopped (done with a simple request to a Steward by a bureaucrat).

   • Adminbots would be restricted to a single purpose and would not run any unrelated jobs.
   • If the community feels it is necessary, it can define which admins will be (or not be) permitted to have adminbots for each approved adminbot code.
2. Adminbot code would have to be resubmitted to RfA for routine reapproval, creating a standard that unlike for admins, RfA approval for bots is for a fixed term (6 months or a year perhaps).
3. Additional unique RfA standards or procedures that would make the approval of needed adminbot code run more smoothly and pass more easily should be adopted.

Others are invited to add more ideas, and comment on these.