maintainer-list: drop gm6k

[Mic92]

Description of changes

This user has requested their personal information to be removed and wants to proceed further legal actions to enforce it. To comply we are proactivly removing all their personal information from this repository. See #273146 (comment)

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:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• 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.05 Release Notes (or backporting 23.05 and 23.11 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.

---

Add a 👍 reaction to pull requests you find important.

[github-actions]

Successfully created backport PR for release-23.11:

• [Backport release-23.11] maintainer-list: drop gm6k #275370

[zeuner]

Under what conditions to lose maintainer status is described here: https://github.com/NixOS/nixpkgs/blob/master/maintainers/README.md?plain=1#L45 ff. The author did not provide any evidence for the maintainer being unresponsive, and also did not wait for one week, so this PR is invalid as per our community guidelines.

Furthermore, the claims (which aren't relevant for revoking maintainer status) seem to be wrong. I could not find evidence anywhere for the maintainer asking to remove "all their personal information" from the repository. Furthermore, legal action cannot be confirmed since the author did not provide any court or file number to verify.

Taking also into account that the author was involved in several attempts to boycott contributions from the maintainer for no obvious reason, this seems to be a case where the author abused his commit privilege for bullying a developer he has personal issues with.

Should this not be the case, the author can revert this commit, refrain from his attempt to push it to further branches, and publish a loud and unambiguous apology on Discourse and GitHub.

[Mic92]

I did not revoke your maintenance status but you asked us to remove personal identifiable while threatening with legal consequences. Since this is a serious allegations it's better to be act fast and be better on the safe side. Feel free to open a pull request to restore this status if you have changed your mind. Currently it's too much of a legal minefield to me to readd your name without your explicit consent, so it's better if you do it yourself.

[piegamesde]

@zeuner following the contributions guidelines by the letter and not by the spirit is rules lawyering to me. Because obviously nobody will have written down something about how to handle the current situation. Mic made a call of judgement, and we can discuss it calmly without being threatened by knee-jerk counter reactions.