I know I don't get an official say in the matter, but if I can just offer this comment that this is a long-time coming, to be honest. Miraheze should be controlling all bot relays on its official platform channels, not outsourcing that to other parties / groups. It just makes good common sense to control our own data and access, to be honest. Other groups / parties can still operate their own bots, of course, which will remain welcome in the channels.

In T6852#135061, @Zppix wrote:

BotsProjectProposal (1).pdf84 KBDownload

keep in mind the standing agreement between MH and bots project

Thanks for sharing that, Zppix. I would just note that your arbitrarily shutting down the MH-Discord IRC bot and the IRC Relay Discord bot finds you in breach of:
"I would also like to continue offering the IRC<->Discord relay, SigmaBot and Void-bot via this
service.
This will help protect our users and ensure we can maintain the full functionality on a service for
the future without technically breaching anyone’s Terms of Service." (emphasis added)

Additionally, while, "[t]he current owners of the bots retain full control of the the codebase as much access as
practically possible[,]" is technically true, that applies only to the MirahezeBots servers and to the MirahezeBots repositories. As the code is open source, it is entirely within Miraheze Site Reliability Engineers' purview to fork the code, providing appropriate attribution to the code contributors.

Cheers,
Doug

I'm not totally aware of how bot servers work but will the bot be officially accessible by dev.miraheze.org?

In T6852#135075, @Naleksuh wrote:

I'm not totally aware of how bot servers work but will the bot be officially accessible by dev.miraheze.org?

Not sure how you mean, this would just be for the purposes of relaying the #miraheze, #miraheze-cvt, #miraheze-cvt-feed, and #miraheze-sre IRC channels to Discord basically. #wiki-feed on Discord is handled by a different bot, run by Miraheze (I think, not entirely sure who runs that one). If you mean the wiki-specific RC feeds on IRC, that's StreamBotMH, and we should probably consider migrating StreamBotMH to bots1, but may not be as essential as that bot is still operational and hosted by MirahezeBots.

@Dmehus incorrect , it was agreed and written, albeit poorly, upon, that the owners of the bot would not have any change of access as a whole, “as much access as possible” in that statement as well.

Ah. I'm not really aware of how bot system works. I just wanted to know if it would be run by specific user or on shared resources and/or if the bot is controlled by multiple people.

I have revoked Zppix's access per https://phab.MirahezeBots.org/T193 and will restore the relay

In T6852#135079, @RhinosF1 wrote:

I have revoked Zppix's access per https://phab.MirahezeBots.org/T193 and will restore the relay

So is the old relay up again? No need for any new bots or some change to bot server?

The relay is restored. Further discussions will occur today

In T6852#135081, @RhinosF1 wrote:

The relay is restored. Further discussions will occur today

Discussions about what?

The situation and Zppix's future

Thanks. Tagging @MacFan4000 and @Void to respond to me on IRC so we can discuss long term action as soon as possible.

In T6852#135095, @RhinosF1 wrote:

Per our discussion, Zppix's access will remain revoked and in this case any new access request needs approval anyway of Miraheze SRE.

The bots team are granting automatic approval to all current members as of this comment in the Miraheze Infra team to full root access to our cluster.

Per policy, any member of Infra can approve access for the rest.

I hope this reassured you. The relay token got deleted by @Zppix but I've made a new one and myself @Void will deploy that later so full access will be restored by end of day.

I think this is a sensible proposal and prevents unnecessary spending by Miraheze Limited for another server.