Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

maintainers: Drop samueldr #321436

Merged

Conversation

samueldr
Copy link
Member

@samueldr samueldr commented Jun 21, 2024

I waited a long time, to wait and see how things would pan out.

It turns out obvious problems can't be dealt with, in an appropriate timing and manner.

Thanks to one individual, backed by a possee of previously banned individuals, and additional perma-banned individuals did it.

Thanks to all of you, I am quitting NixOS.

The continuous concern trolling, the continuous bigotted discussions, the continued hostile tone, the actions made despite the numerous times you were told to do better. The constant FUD. The constant waste of time. It's not a single event. It is a pattern.

I do not think that this situation can be salvaged anymore.

Systemic issue in the lack of governance enabled this. While some will put the fault entirely on the shoulders of the organization, I will say that they share the blame, but the bullying and pressure from the individuals who fully understand what they are doing is what did it.

Couple that with the structural inability for action by the moderation team being abused by those bad actors, and you have a recipe for alienating and burning-out the leftover important contributors.

Let it be written here that I have discussed with organization members and moderation team members about the continued behaviour of casting FUD on the community by this individual. This was done this individual's ban. It happened in what was (and still) tacitly agreed toe be a NixOS community place, the subreddit. Probably elsewhere too.

Nothing was done, no mention of re-considering the duration of the ban, and as far as I know, not even some discussion about how continuing the behaviour that was the reason for being banned is unwelcome.

What made me snap?

Not long after the ban being lifted, this individual continued with weird persecution plots and conspiracy theories casting doubts on the legitimacy of the moderation team's actions.

And in the least self-aware way possible, continued this discourse of persecution and conspiracies, again casting FUD and divisiveness when asking for what, with a reasonable person, would have a formality.
See the original comment contents.

This continued into the same behaviour that brought up the initial warnings and ban, on the unmoderated community-adjacent subreddit.

This continued onto the discourse into the same behaviour that brought up the initial warnings and ban.

The absolute insolence, consistently twisting the words I wrote to fit in his imagined narrative, took me over the edge. Then the moderator decision to increase the time-out delay to twelve hours, which at one hour was already causing the bad behaviour of mass-dumping information into single messages, meant there was no way for me to correct the facts and act in this manner without relitigating elsewhere gave me the time and energy to do it.

That's it.

The behaviour of this person. No political beliefs (I still don't know what they are). No employer (while I know and hate it, it is what it is). No plot form some shadow bagel trying to somehow do... Only jon knows what it would do... No take-over plot... Only the unacceptable behaviour, or character if you will, of that person.

Someone who from the start always had an equal opportunity to participate, regardless of his attributes. This person should have been accountable for his actions, but couldn't understand it.

This was not helped by their posse harrassing me personally, on top of all that.

In other words, the organization and community is not tooled to protect its valued members.

So I am quitting with prejudice.

Even though I helped build the NixOS project for over seven years, helped the community be the best it could in the IRC times, helped direct some of the community decisions.

I did not want to leave this community, because this is not only my home, but I built it with collaborators who cared. It seems like there is no one who cares left anymore. And I was pushed out against my best efforts.

Mostly thankless to the end.

— samueldr

Things done

  • Built on platform(s)
    • x86_64-linux
    • aarch64-linux
    • x86_64-darwin
    • aarch64-darwin
  • For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
    • sandbox = relaxed
    • sandbox = true
  • Tested, as applicable:
  • Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
  • Tested basic functionality of all binary files (usually in ./result/bin/)
  • 24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)
    • (Package updates) Added a release notes entry if the change is major or breaking
    • (Module updates) Added a release notes entry if the change is significant
    • (Module addition) Added a release notes entry if adding a new NixOS module
  • Fits CONTRIBUTING.md.

https://discourse.nixos.org/t/maintainers-drop-samueldr-321436/47354

I waited a long time, to wait and see how things would pan out.

It turns out obvious problems can't be dealt with, in an appropriate
timing and manner.

Thanks to one individual, backed by a possee of previously banned
individuals, and additional perma-banned individuals did it.

Thanks to all of you, I am quitting NixOS.

The continuous concern trolling, the continuous bigotted discussions,
the continued hostile tone, the actions made despite the numerous times
you were told to do better. The constant FUD. The constant waste of
time. It's not a single event. It is a pattern.

I do not think that this situation can be salvaged anymore.

Systemic issue in the lack of governance enabled this. While some will
put the fault entirely on the shoulders of the organization, I will say
that they share the blame, but the bullying and pressure from the
individuals ***who fully understand what they are doing*** is what did
it.

Couple that with the structural inability for action by the moderation
team being abused by those bad actors, and you have a recipe for
alienating and burning-out the leftover important contributors.

Let it be written here that I have discussed with organization members
and moderation team members about the continued behaviour of casting FUD
on the community by this individual. This was done this individual's ban.
It happened in what was (and still) tacitly agreed toe be a NixOS
community place, the subreddit. Probably elsewhere too.

Nothing was done, no mention of re-considering the duration of the ban,
and as far as I know, not even some discussion about how continuing the
behaviour that was the reason for being banned is unwelcome.

His name is jonringer (Jonathan Ringer).

What made me snap?

Not long after the ban being lifted, this individual continued with
weird persecution plots and conspiracy theories casting doubts on the
legitimacy of the moderation team's actions.
 - NixOS/rfcs#175
And in the least self-aware way possible, continued this discourse of
persecution and conspiracies, again casting FUD and divisiveness when
asking for what, with a reasonable person, would have a formality.
See the original comment contents.
 - NixOS#50105 (comment)
This continued into the same behaviour that brought up the initial
warnings and ban, on the unmoderated community-adjacent subreddit.
 - https://old.reddit.com/r/NixOS/comments/1djuxpx/drama_will_jonringers_commit_bit_be_restored/ https://archive.is/sCJJw
This continued onto the discourse into the same behaviour that
brought up the initial warnings and ban.
 - https://discourse.nixos.org/t/should-jonringer-get-his-commit-bit-back/47267/46

The absolute insolence, consistently twisting the words I wrote to fit
in his imagined narrative, took me over the edge. Then the moderator
decision to *increase the time-out delay* to twelve hours, which at
one hour was already causing the bad behaviour of mass-dumping
information into single messages, meant there was no way for me to
correct the facts and act in this manner without relitigating
elsewhere gave me the time and energy to do it.

That's it.

The behaviour of this person. No political beliefs (I still don't know
what they are). No employer (while I know and hate it, it is what it is).
No plot form some shadow bagel trying to somehow do... Only jon knows
what it would do... No take-over plot... Only the unacceptable
behaviour, or character if you will, of that person.

Someone who from the start always had an equal opportunity to participate,
regardless of his attributes. This person should have been accountable for
his actions, but couldn't understand it.

This was not helped by their posse harrassing me personally, on top of
all that.

In other words, the organization and community is not tooled to protect
its valued members.

***So I am quitting with prejudice.***

Even though I helped build the NixOS project for over seven years,
helped the community be the best it could in the IRC times, helped
direct some of the community decisions.

I did not want to leave this community, because this is not only my
home, but I built it with collaborators who cared. It seems like
there is no one who cares left anymore. And I was pushed out against
my best efforts.

Mostly thankless to the end.

— samueldr

Signed-off-by: Samuel Dionne-Riel <[email protected]>
@github-actions github-actions bot added 6.topic: qt/kde 6.topic: printing 8.has: maintainer-list (update) This PR changes `maintainers/maintainer-list.nix` labels Jun 21, 2024
@NixOS NixOS locked as too heated and limited conversation to collaborators Jun 21, 2024
@NixOS NixOS unlocked this conversation Jun 21, 2024
@vcunat
Copy link
Member

vcunat commented Jun 21, 2024

Why do we need to immediately drop those packages?

@ofborg ofborg bot added 8.has: clean-up 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 labels Jun 21, 2024
@samueldr
Copy link
Member Author

samueldr commented Jun 21, 2024

The maintainer did not do upkeep on them for a while. Most if not all were added early in Nixpkgs' lifetime for myself. At least one is even probably bad/buggy.

And some have unresponsive upstreams or have been removed/superseded.

@vcunat
Copy link
Member

vcunat commented Jun 21, 2024

So by "unmaintained" you meant upstream. In this context it really seemed to refer to yourself.

@RossComputerGuy
Copy link
Member

What will happen with Mobile NixOS?

@samueldr
Copy link
Member Author

What will happen with Mobile NixOS?

https://discourse.nixos.org/t/maintainers-drop-samueldr-321436/47354#what-about-your-projects-2

@vcunat
Copy link
Member

vcunat commented Jun 21, 2024

I think the discourse thread is better suited for such discussion (though Samuel doesn't seem to want any reactions).

Anyone has an idea what this GitHub warning is about? I couldn't find anything. (It's well hidden I guess?)

The head ref may contain hidden characters: "ce\u00A0n'est\u00A0qu'un\u00A0au\u00A0revoir,\u00A0\u00E0\u00A0la\u00A0prochaine!"

@samueldr
Copy link
Member Author

samueldr commented Jun 21, 2024

So by "unmaintained" you meant upstream. In this context it really seemed to refer to yourself.

Sometimes both. I am picking up trash to try and lessen the load of "why is this even here?" in the future. I would have removed more, but that would have been a bad idea, since those are more important packages.

If needed, they can be fished back-up. Though I suspect things like the driver for this one printer model that has worked without the driver for years with IPP won't be needed anymore

@samueldr
Copy link
Member Author

samueldr commented Jun 21, 2024

I think the discourse thread is better suited for such discussion (though Samuel doesn't seem to want any reactions).

Discourse thread for the stuff other than my maintainership yeah.

Anyone has an idea what this GitHub warning is about? I couldn't find anything. (It's well hidden I guess?)

The head ref may contain hidden characters: "ce\u00A0n'est\u00A0qu'un\u00A0au\u00A0revoir,\u00A0\u00E0\u00A0la\u00A0prochaine!"

Look at the origin branch name. I tried being fancy. GitHub tattled on me. Github is being proactive with non-breaking spaces, I guess to prevent someone using "human command injection" with generated instructions?

@samueldr
Copy link
Member Author

Not waiting on Darwin for a maintainers removal.

image

@samueldr samueldr merged commit 1c0bec2 into NixOS:master Jun 21, 2024
27 of 29 checks passed
@samueldr samueldr deleted the ce n'est qu'un au revoir, à la prochaine! branch June 21, 2024 07:24
@vcunat
Copy link
Member

vcunat commented Jun 21, 2024

uefi-firmware-parser had a release upstream less than a year ago, but I don't know the package.

@samueldr
Copy link
Member Author

samueldr commented Jun 21, 2024

If you (or anyone else) need it, feel free to package it!

jtojnar added a commit to jtojnar/nixfiles that referenced this pull request Jun 24, 2024
Flake lock file updates:

• Updated input 'home-manager':
    'github:nix-community/home-manager/d7830d05421d0ced83a0f007900898bdcaf2a2ca' (2024-06-19)
  → 'github:nix-community/home-manager/6b1f90a8ff92e81638ae6eb48cd62349c3e387bb' (2024-06-23)
• Updated input 'nixpkgs':
    'github:nixos/nixpkgs/b60ebf54c15553b393d144357375ea956f89e9a9' (2024-06-16)
  → 'github:nixos/nixpkgs/a71e967ef3694799d0c418c98332f7ff4cc5f6af' (2024-06-22)

  nix-top removed NixOS/nixpkgs#321436
@eclairevoyant eclairevoyant mentioned this pull request Jun 28, 2024
13 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
6.topic: printing 6.topic: qt/kde 8.has: clean-up 8.has: maintainer-list (update) This PR changes `maintainers/maintainer-list.nix` 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