Skip to content

maintainers: drop tuynia#431156

Merged
philiptaron merged 1 commit intoNixOS:masterfrom
wolfgangwalther:maintainers-tuynia
Aug 10, 2025
Merged

maintainers: drop tuynia#431156
philiptaron merged 1 commit intoNixOS:masterfrom
wolfgangwalther:maintainers-tuynia

Conversation

@wolfgangwalther
Copy link
Contributor

They recently deleted their account, https://github.com/mivorasu doesn't seem to exist anymore.

They also deleted their PRs with them, for example https://github.com/NixOS/nixpkgs/pull/429345 was a treewide meta.lib refactor, in which @emilazy and @philiptaron were involved as well. Just returns a 404 for me right now.

No need to wait for 7 days, if the account doesn't exist anymore.

They recently deleted their account.
@nixpkgs-ci nixpkgs-ci bot added 10.rebuild-darwin: 0 This PR does not cause any packages to rebuild on Darwin. 10.rebuild-linux: 0 This PR does not cause any packages to rebuild on Linux. 6.topic: vscode A free and versatile code editor that supports almost every major programming language. 8.has: maintainer-list (update) This PR changes `maintainers/maintainer-list.nix` 9.needs: reviewer This PR currently has no reviewers requested and needs attention. labels Aug 5, 2025
@Artturin
Copy link
Member

Artturin commented Aug 5, 2025

They also deleted their PRs with them, for example #429345 was a treewide meta.lib refactor, in which emilazy and philiptaron were involved as well. Just returns a 404 for me right now.

That happens when github bans an account

@wolfgangwalther
Copy link
Contributor Author

wolfgangwalther commented Aug 5, 2025

That happens when github bans an account

I see. Quite counterproductive, because this user had plenty of legit PRs (~100), roughly half of which were already merged. If all of these are gone now, too, a lot of history is gone... (Edit: Yes, also merged PRs are returning 404 now)

@emilazy
Copy link
Member

emilazy commented Aug 5, 2025

It’s happened before, for a user with far more contributions. It also doesn’t happen for every kind of ban, I think. It’s a little mysterious. Not sure if you can request it yourself (e.g. for GDPR reasons).

@emilazy
Copy link
Member

emilazy commented Aug 5, 2025

(I don’t quite know what to make of the whole situation here. It feels very strange, beyond just the ban. No objection to removing the maintainers entry, though, but maybe waiting out the week would be a good idea under the odd circumstances.)

@wolfgangwalther
Copy link
Contributor Author

I don’t quite know what to make of the whole situation here. It feels very strange, beyond just the ban.

I have been in contact with the moderation team about this. Imho, this is not an isolated instance, but a user who left earlier creating a new account under a different name. I assume the hostility towards me came from earlier interactions between us (starting here, continuing in a different PR, which I can't find right now).

Of course, there is no proof for that, but the timelines just match up too well: The user dropped here created their account three weeks ago and suddenly started contributing massively two weeks ago.

I have no idea how a ban fits into all of this, though. A request for deletion of all their data, seems more likely to me in this case.

@emilazy
Copy link
Member

emilazy commented Aug 5, 2025

I have been in contact with the moderation team about this. Imho, this is not an isolated instance, but a user who left earlier creating a new account under a different name. I assume the hostility towards me came from earlier interactions between us (starting here, continuing in a different PR, which I can't find right now).

Yes, I was including that in “the whole situation” (I assume the new account was not meant to be a secret, as the avatar was almost identical, so I believe I am not overstepping by referencing it publicly).

Even aside from you, they raised accusations of personal insults levelled towards them from other contributors in that PR and on Matrix that AFAICT were never publicly substantiated and that I personally never witnessed any evidence for. I am not saying those insults did not happen, only that the claims appeared to come out of the blue in response to interactions directed at them that I did not perceive as serious insults, and that they happened again after I said that any such incidents should certainly be raised with the moderation team. Such insults, like saying someone has always been terrible and incapable, are of course unacceptable and I hope the moderation team would deal with them swiftly – but e.g. I found #425953 (comment) to come somewhat out of nowhere as an accusation, too. (I can understand feeling insulted by your comments there, but not the characterization given.)

I get the impression there was a language barrier element, but it has still felt odd to me. Anyway, perhaps it is not appropriate to go in depth publicly about someone who is (presumably?) not here to respond. But I think that in the LLM era there are going to be a lot more strange‐feeling interactions like this and I am not sure how we should handle them. I am certainly feeling much more nervous about treewides without thorough independent automated verification, at least if they do not come from long‐term contributors.

Anyway, it is unfortunate. I would like Nixpkgs to have good standards and to be careful about sweeping changes, and I would also like it to be welcoming to new and enthusiastic contributors even if there are communication issues, and I would also like it to be robust against potential bad actors. I am not sure how we can achieve all of these simultaneously.

@philiptaron
Copy link
Contributor

Couldn't have said it better myself, @emilazy.

The PR they prepared appeared to be the highest-quality one yet in removing with lib; from various sections, so I was well on my way to merging it once I had that spare moment to read through the code that produced it in depth and convince myself it was going to do things right... and pushing a change to put the 55,000 line change in the ignore-for-blame list.

The communication difficulties and intense assertion of "quiet!" made me believe that they weren't used to be in a bazaar such as Nixpkgs. Sad!

@philiptaron
Copy link
Contributor

In a twist of fate, there's a reaction from @mivorasu on this PR 😵

GitHub, how do you work!?

@wolfgangwalther
Copy link
Contributor Author

Oh, wow, that is really odd.

I will put this on draft, so that nobody accidentally merges this.

@wolfgangwalther wolfgangwalther marked this pull request as draft August 6, 2025 18:53
@nixpkgs-ci nixpkgs-ci bot removed the 9.needs: reviewer This PR currently has no reviewers requested and needs attention. label Aug 6, 2025
@wolfgangwalther
Copy link
Contributor Author

wolfgangwalther commented Aug 6, 2025

I added a "reaction" to this PR myself. And interestingly, when I do gh api -X GET /repos/NixOS/nixpkgs/issues/431156/reactions, I can only see my reaction, not the other one.

But the UI displays both...


Edit: By now, that other reaction is gone in the UI, too.

@wolfgangwalther
Copy link
Contributor Author

It seems like the account is now actually deleted, not just blocked anymore. I take that from:

In a twist of fate, there's a reaction from @mivorasu on this PR 😵

A few days ago, the @mivorasu was still a link to the 404-ed profile. Now it doesn't even show as a link anymore.

@wolfgangwalther wolfgangwalther marked this pull request as ready for review August 10, 2025 15:32
@nixpkgs-ci nixpkgs-ci bot added the 9.needs: reviewer This PR currently has no reviewers requested and needs attention. label Aug 10, 2025
@philiptaron philiptaron merged commit febe951 into NixOS:master Aug 10, 2025
31 checks passed
@wolfgangwalther wolfgangwalther deleted the maintainers-tuynia branch August 10, 2025 16:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

6.topic: vscode A free and versatile code editor that supports almost every major programming language. 8.has: maintainer-list (update) This PR changes `maintainers/maintainer-list.nix` 9.needs: reviewer This PR currently has no reviewers requested and needs attention. 10.rebuild-darwin: 0 This PR does not cause any packages to rebuild on Darwin. 10.rebuild-linux: 0 This PR does not cause any packages to rebuild on Linux.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants