Page MenuHomePhabricator

Zppix's access has been revoked
Closed, ResolvedPublic

Description

This is a review task of my action this morning.

While I was asleep, @Zppix unilaterally in a decision that fell, in my opinion below the standards of our team, revoked the relay.

After talking with Universal Omega and @Reception123, I revoked access.

I would like to hear reasons for access being restored or revoked on this task if others have them.

It is reasonably believed that John would support this and Paladox has confirmed their support.

Details

Security
None

Event Timeline

RhinosF1 updated the task description. (Show Details)
RhinosF1 added a subscriber: Zppix.

My own thoughts in detail.

I think in the current state, given the resignation of Zppix from SRE and events in last ~10 hours, allowing Zppix access to the project beyond today would pose a serious risk to the relationship we have with Miraheze SRE and the ability for us to provide certain services.

Per https://phabricator.miraheze.org/T6852, our ability to operate the relay is already at risk.

Though not an official member of the MirahezeBots development team, I was encouraged by @RhinosF1 to comment on this request. It saddens me greatly to see Zppix' access removed, but ultimately, MirahezeBots is a team-based project. It may have been founded by Zppix, but there's nothing in MirahezeBots' policies that give him carte blanche authority to unilaterally make major decisions affecting the entire project. I can say that I strongly encouraged him not to shutdown the Discord/IRC relay bots just because of a dispute over the Discord server moderation hierarchy. It was quite silly, really. It's the equivalent of taking one's sandbox of toys away when you disagreed with something either unrelated or barely related. When the other team members joined the MirahezeBots project, it was de facto agreed, at minimum, that the team would make major decisions collectively.

Zppix claimed in this request that there's a standing agreement between MirahezeBots and Miraheze Limited, which is true, and I thanked him for sharing that, but as I also pointed out, he was technically in material breach of that agreement by withdrawing the major Discord/IRC relays to which the community of more than 900+ Discord users rely on so heavily. Even Lakelimbo has had to join IRC because the Discord/IRC bot relays were revoked.

This revocation isn't forever; rather, it's merely a warning to Zppix from his peers that he needs to adhere to consensus-based team decision-making.

Thanks,
Doug

RhinosF1 added a subscriber: Void.

I've spoke to MacFan and he's fine with the access being revoked. Assigning to @Void as he's the only person I haven't spoke to.

I was very much hoping to be able to resolve this issue without anyone needing to walk away from the project, both in reference to this, and Miraheze as a whole. While I am not happy with Zppix's choice to remove the relay, I am even more disappointed that the issue was escalated. It seems to me that no attempt was made to sit down and discuss what the problem was so that it could be resolved. And now we're sitting here, bridges burned, and no closer to the root of the problem. I'm not even sure I know what it is at this point.

In T193#3331, @Void wrote:

I was very much hoping to be able to resolve this issue without anyone needing to walk away from the project, both in reference to this, and Miraheze as a whole. While I am not happy with Zppix's choice to remove the relay, I am even more disappointed that the issue was escalated. It seems to me that no attempt was made to sit down and discuss what the problem was so that it could be resolved. And now we're sitting here, bridges burned, and no closer to the root of the problem. I'm not even sure I know what it is at this point.

For what it's worth, I'm not sure I know what the solution is here. I agree that access doesn't need to be revoked, and it's also unfortunate this was escalated. Personally, I don't see why Zppix can't remain a part of the MirahezeBots project. To me, he just needs to acknowledge the events that to this unfortunate escalation and, equally critically, that MirahezeBots operates based on decisions made by the team. No one person controls the MirahezeBots project. You're all bot developers and operators, and that was agreed, implicitly or explicitly, when you made the decision as a team to coordinate your efforts and share in the development. Perhaps the solution here is to assign this task to @Zppix to see if he wants to continue?

We haven't heard from Reception123 here, so @Reception123, do you have any thoughts?

Closing this per our discussions and with this comment the removal is ratified.

We will discuss future policy changes and who will take over project lead elsewhere. There is a seperate off boarding task.