[00:01:14] Thank you! @lucaswerkmeister :) I'm gonna go and figure out how to usurp the tool so that we have a better solution than periodically asking toolforge admins to delete the file :( [00:01:34] I was thinking in that direction as well and then discovered T361426 [00:02:28] yeah, for bots it's best to create a new tool & bot account, as there's nothing of value in the existing tool [00:02:55] thankfully all the code's already published on https://en.wikipedia.org/wiki/User:Yapperbot [00:05:12] Yeah, I do have the code, gonna figure out what the onwiki paperwork is then [00:05:25] (and create a new account) [00:05:30] If we did full usurpation for bots and turned over their existing creds to the new tool owners we could keep well-known bots running indefinitely, but getting consensus on a process to do that which is both fair and secure felt really hard when I drafted the Abandoned tool policy [00:06:18] For most wikis forking is no big deal at all. For enwiki I guess it depends on how BAG feels about the new owner [00:09:29] I don't think we should be doing full bot usurpation, but one way could be to delete the PII data (botpassword) and then hand the toolforge tool to folks (re @wmtelegram_bot: For most wikis forking is no big deal at all. For enwiki I guess it depends on how BAG feels about the new owner) [00:10:14] In this case, code changes need to be made, but there might be cases where the bot just works if given a jolt [00:11:32] enwiki is generally happy to speedy approve forks with no code changes at the time of the approval [00:11:36] Deleting the existing creds is part of https://wikitech.wikimedia.org/wiki/Help:Toolforge/Abandoned_tool_policy. It just turns out that for most bots once you delete the creds there really isn't anything of value left (assuming the code is public) [00:12:24] but it's not written into the bot policy, it's all BAGger discretion [00:40:58] why not get the BRFA and new creds sorted first and then once they're ready to do then transfer existing tool? it should be a trivial time period to install new creds. (re @AntiComposite: yeah, for bots it's best to create a new tool & bot account, as there's nothing of value in the existing tool) [00:50:54] what if we established a pattern where bot accounts could declare a succession policy? a policy could be stated or incorporated by reference both on bot's user page and also in a file like yapperbot's ~/botpassword [00:50:54] maybe could require using a toolforge address for wiki account email address. or else another way to not necessarily give away old account email to new owner. (re @sohom_datta: I don't think we should be doing full bot usurpation, but one way could be to delete the PII data (botpassword) and then hand th...) [00:51:31] if XYZ happens with the toolforge account then do W with the wiki bot account. [00:52:33] I mean, part of the problem here is that the tool never had co-maintainers in the first place [00:55:58] and planning for adoption rather than planned succession is even more complex [01:34:46] /botpassword [04:22:34] !log tools rebooting tools-prometheus-8; unreachable [04:22:37] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools/SAL [07:15:54] Can anyone approve this? https://commons.m.wikimedia.org/wiki/Special:OAuthListConsumers/view/1e3dd844b1788dac2895170f03bf2769 [10:29:23] i see it was approved now (re @nokibsarkar: Can anyone approve this? https://commons.m.wikimedia.org/wiki/Special:OAuthListConsumers/view/1e3dd844b1788dac2895170f03bf2769) [18:42:03] !log lucaswerkmeister@tools-bastion-13 tools.quickcategories deployed 8f93390eb6 (&actions= and &title= parameters in /batch/new/pagepile, T397320) [18:42:07] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.quickcategories/SAL