Call for full re-election of the Steering Committee

In light of recent events, we have lost confidence in the Steering Committee and call for a full re-election with staggered terms.

Signed by

  1. 0x4A6F, Nix formatting team, ex-moderation team, Nixpkgs committer
  2. adamcstephens, LXC and BEAM teams, Nixpkgs committer
  3. alois31, Nixpkgs maintainer
  4. amadaluzia, Nixpkgs maintainer
  5. antonmosich, Nixpkgs maintainer
  6. atalii, Nixpkgs maintainer
  7. awwpotato, Nixpkgs maintainer
  8. cafkafk, Nixpkgs committer
  9. CobaltCause, Nixpkgs maintainer
  10. con-f-use, Nixpkgs maintainer
  11. cyclic-pentane, Robotnix maintainer
  12. drakon64, Nixpkgs maintainer
  13. ElvishJerricco, systemd team, Nixpkgs committer
  14. emilazy, Darwin, stdenv, LLVM, and Nixpkgs core teams, Nixpkgs committer, nix-darwin committer
  15. emilylange, Nixpkgs committer, Chromium maintainer
  16. Enzime, Nixpkgs committer, nix-darwin committer, nixos-anywhere maintainer, disko maintainer
  17. FedericoSchonborn, ex-Nixpkgs maintainer
  18. Frontear, Nixpkgs maintainer
  19. getchoo, Budgie and GNOME Circle teams, Nixpkgs committer
  20. jopejoe1, Release Manager 25.11, Nixpkgs committer
  21. ipetkov, Crane maintainer
  22. isabelroses, Nixpkgs committer
  23. i-am-logger, Nixpkgs maintainer
  24. jackr, Nixpkgs maintainer
  25. jaen, Nixpkgs contributor
  26. JulienMalka, Nixpkgs committer
  27. K900, KDE, Steam, Linux kernel, and Nixpkgs core teams, ex-moderation team, Nixpkgs committer
  28. keysmashes, Nixpkgs maintainer
  29. KFearsoff, Nixpkgs contributor
  30. KiaraGrouwstra, Nixpkgs maintainer, co-maintainer of nixos-search
  31. lassulus, moderation team, NixOS Foundation treasurer, NixOS wiki administrator, ex-Nix Constitutional Assembly, Nixpkgs committer
  32. leona-ya, Release Manager for 25.05 and 25.11, Nixpkgs committer
  33. LeSuisse, security team, Nixpkgs committer
  34. lewo, Nixpkgs committer, SNM and nix2container maintainer
  35. lf-, Nixpkgs committer, Lix core team
  36. lheckemann, Release Manager for 19.03 and 19.09, ex-Nixpkgs committer
  37. lilyball, ex-Nixpkgs maintainer
  38. llakala, Nixpkgs maintainer
  39. LunNova, ROCm team
  40. LordGrimmauld, SDL and systemd teams, Nixpkgs committer
  41. Ma27, Linux kernel, Matrix, Nextcloud, Postgres, and PHP teams, Nixpkgs committer
  42. MagicRB, Nixpkgs contributor, NixNG maintainer
  43. maralorn, Haskell team, Nixpkgs committer
  44. marcin-serwin, SDL team, Nixpkgs maintainer
  45. michaelBelsanti, COSMIC team, Nixpkgs committer
  46. mmkaram, Nixpkgs maintainer
  47. mweinelt, infrastructure team lead, security team, Nixpkgs committer
  48. nadir-ishiguro, Nixpkgs maintainer
  49. networkException, Chromium maintainer
  50. niklaskorz, Nixpkgs committer, Darwin maintainer
  51. nim65s, ex-moderation team, Nixpkgs maintainer
  52. normalcea, Nixpkgs contributor
  53. Notarin, Nixpkgs maintainer
  54. nrdsp, Nixpkgs contributor
  55. nyabinary, COSMIC maintainer
  56. NyCodeGHG, Nixpkgs maintainer
  57. olafklingt, ex-documentation team
  58. OPNA2608, Lomiri and NGI teams, Nixpkgs committer
  59. Pamplemousse, Nixpkgs contributor
  60. patka-123, Nixpkgs maintainer
  61. paumr, Nixpkgs maintainer
  62. pbsds, Nixpkgs committer
  63. phaer, Nixpkgs committer
  64. philiptaron, CI and stdenv teams, Nixpkgs committer
  65. Picnoir, ex-moderation team, Nixpkgs committer
  66. piegames, Nix formatting team, Nixpkgs committer
  67. pluiedev, Nixpkgs maintainer
  68. pyrox0, Release Editor for 25.11, Nixpkgs committer
  69. reckenrode, Darwin team, Nixpkgs committer
  70. rhendric, ex-moderation team, Nixpkgs committer
  71. Samasaur1, Nixpkgs maintainer, nix-darwin committer, Swift maintainer
  72. samueldr, Release Manager for 18.09 and 19.03, ex-Nixpkgs committer
  73. Scrumplex, Nixpkgs committer
  74. SigmaSquadron, Xen Project team, Nixpkgs committer
  75. SomeoneSerge, CUDA team, Nixpkgs committer
  76. thefossguy, Nixpkgs maintainer
  77. tomodachi94, Java team, Nixpkgs committer, NixOS Discord moderator
  78. uninsane, Nixpkgs committer
  79. WeetHet, Nixpkgs maintainer
  80. wolfgangwalther, CI, Haskell, Postgres, and Nixpkgs core teams, Nixpkgs committer
  81. yuyuyureka, Nixpkgs committer
  82. Zimmi48, Nixpkgs committer
40 Likes

If you want to add your signature, DM me here on Discourse or at @wolfgangwalther:matrix.org on Matrix.

3 Likes

While I generally don’t get much involved in the “politics” (for the lack of a better word), I will support this because I want us to have a start with a clean state. Please add me too, as thefossguy, some random nixpkgs maintainer.

2 Likes
5 Likes

In light of this petition for a full re-election I called for a second formal vote of no confidence, which went down the same way as the original formal vote:

19 Likes

Thank you for the transparency. As it is clear the Steering Committee remains deadlocked and unable to establish confidence in itself, I continue to reiterate the call for a full re-election for the health of the community and the project governance.

Between this post going up four hours ago and the SC votes being shared, the following signatures were added:

  1. amadaluzia, Nixpkgs maintainer
  2. antonmosich, Nixpkgs maintainer
  3. Enzime, Nixpkgs committer, nix-darwin committer, nixos-anywhere maintainer, disko maintainer
  4. Frontear, Nixpkgs maintainer
  5. jopejoe1, Release Manager 25.11, Nixpkgs committer
  6. keysmashes, Nixpkgs maintainer
  7. lewo, Nixpkgs committer, SNM and nix2container maintainer
  8. lilyball, ex-Nixpkgs maintainer
  9. llakala, Nixpkgs maintainer
  10. marcin-serwin, SDL team, Nixpkgs maintainer
  11. mmkaram, Nixpkgs maintainer
  12. normalcea, Nixpkgs contributor
  13. NyCodeGHG, Nixpkgs maintainer
  14. patka-123, Nixpkgs maintainer
  15. Picnoir, ex-moderation team, Nixpkgs committer
  16. rhendric, ex-moderation team, Nixpkgs committer
  17. thefossguy, Nixpkgs maintainer
  18. WeetHet, Nixpkgs maintainer

I will continue to add more signatures as they come in.

I have asked a question to SC candidates about this procedural deadlock issue at Should the SC vote for confidence instead of for no-confidence? ¡ Issue #472 ¡ NixOS/SC-election-2025 ¡ GitHub.

14 Likes

isabelroses, Thank you so much for pointing me to the context which exactly answered my question.
When I first read that post yesterday, I read it too fast and skip too much. English is not my native language, I was only looking for paragraphs first sentence and sentences with bold words and large words and links. I wanted to speed up because there were a lot of replies and I thought it may have more informations in the replies.
I did not know that the evidence was treated as confidential and that was unable for public review.
I saw a lot of people said in their replies about they already read it, so that I was curious and asked Where can I read the evidence about SC prepared to lie to people? above.
I wanted to read it before making any decision like everybody did.
I am so sorry about asking that stupid question because of my misreading of the post. I am not trying to pressure anyone to review any confidential materials by any means.
I just login and find the post was flagged and hidden, and I received an automated message said it flag as inappropriate because the community feels it is offensive, abusive, to be hateful conduct or a violation.
I know it is all my fault in this sensitive moment saying those unsensible things.
I am not meant to offend anybody. It was unintentional and it was totally my mistake. I deeply apologize.

7 Likes

Per Steering Committee | Nix & NixOS , as far as I can tell, 5 of the 7 positions will be decided by the current election. Thus the current election is a larger election than we’d typically have. Am I misunderstanding this?

There are costs to bypassing the existing processes: losing continuty; increase overheads, especially for contributors unable to keep up with exceptions to the current process.

Given the costs, and that 5 of 7 SC members will be voted in soon, what is the motivation for a full re-election?

Is the call for a full-election about symbolism, urgency, or to remove the two members whose term ends in 2026?

A handy litmus test to answer that: would there still be a call for re-election if it were two other people whose term ended in 2026?

4 Likes

Asking this clarifying question arguably still underestimates how activist pressure, seemingly a good thing and more familiar territory to many of us, empowers the reactionary forces that arguably governed us before we gave having elected representatives a try instead.

From a narrative point of view those who try to see things through by serving out their term on the SC are just more likely to end up holding the bag (meaning getting blamed) than those who leave or vote no-confidence. Representatives get to go back to to joining the reactionary forces, reactionaries get to score some points, regardless of intention. Meanwhile the pressure stresses all of us out as well.

So a admittedly more radical question to ask ourselves is:

Do we want to be called into action again ahead of the next election?

In the aggregate, that may be what we get from falling back to activism too early, when we wanted to give elected representatives a try. The part of that statement that really demands a lot of patience from us and is admittedly very subjective is the ‘too early’ part.

4 Likes

I second @tomf.

Continuity and upholding processes is of more importance in a young organisation like ours.

I think a lot of opinions are out there about what happened and why that is bad (or not bad), but that does not mean we should change a vital election process.

Sure, the community can signal to the steering council that it is against a decision, and i believe that signal has already landed.

While it is of vital importance to keep people accountable, we should also empower the SC to steer us.

5 Likes

Just to clarify: Where exactly do you see someone “bypassing the existing processes” here?
I see a petition for full reelections here, which I interpret as an appeal to the SC and its members themselves, as that’s afaik the only group with the power to actually implement the desired change. If the SC would decide to do so, that’s a normal process outlined in the constitution.

So I fail to see how this is, in principle, any different to e.g. public petitions or demonstrations in any other democratic process? Or compared to just contacting SC members individually with your wishes & concerns. I don’t really see “exceptions to the current process” in the call for full-elections above. If you see one, please elaborate!

Regarding continuity & reelections, I just link @rhendrics comment in another thread to avoid repeating the same argument.

(Please note that I did not sign the call for full re-election so far; I am not even particularly fond of public petitions like these, I just think they are a legitimate instrument in democratic campaigns)

EDIT to add: More about the existing process this is about from my POV can be read here: org/doc/constitution.md at main ¡ NixOS/org ¡ GitHub

10 Likes

I have so far not stepped down

  • makes no material difference to the election EDIT: run-up
  • makes me unable to represent those who voted for me in other matters
  • makes us unable to fix what we broke (although chances to achieve something meaningful here are below the water line at this point)

I want the next SC to succeed, and I have been considering this.

32 Likes

This is a very important point. You have received a mandate from those who voted for you. They value and trust you, your judgement and character. We are many who believe you have done a great job, and we hope you stay on.

15 Likes

There seems to be a sort of implicit assumption that none of those that “voted for” roberth are among the people asking for a full re-election.

First, everyone voted on (rather than for/against) roberth, one way or another, since we had to rank the candidates. So there is no clear line between those who voted “for” him or “against” him. For instance, for my part, roberth was the top candidate that I voted for out of those serving on the Nix team, he was the 3rd candidate in my ranking out of those that were elected, and about the 8th candidate on my general ranking (according to my notes and my recollection). Given that there were 23 candidates (if I counted correctly), this means that I voted “for” rather than “against” roberth. That doesn’t prevent me from having signed this resignation petition.

15 Likes

Robert was my top vote overall and I wrote the open “letter”.

(And to make clear: the one-sentence-letter is about a loss of confidence in the SC as a body - this is not about any individual person. I have always highly valued each individual member of the SC and will continue to do so. They’re just… not good as SC. We didn’t know before, we tried, now we know. That’s all.)

18 Likes

You are being given a chance to do this, by accepting the losses the SC has incurred and stepping down.

You have to understand that sometimes, those who have failed don’t get a chance to make up for it. It is very disrespectful of those affected by the failure to force-feed them attempts at “fixing”, and constitutes an abuse cycle. Sometimes, the best you can do is accept responsibility and separate.

8 Likes

Please do not end your term early based on external pressure, stay on for the sake of the SC as an institution.

If we want the SC to have power, we need to give it power and also let it keep that power for the agreed upon time period. Otherwise the SC cannot do its job properly. It cannot make the decisions it would need to make, out of a fear of backlash, not via elections, but via activism and drama.

22 Likes

I recognize that full well, and I take that into account.

13 Likes