#Tag
Probably a problem for most projects, fwiw.
｢ Consensus-building wouldn’t be as much of a problem if the Steering Committee were willing to force through certain policies with a vote but many of the current Steering Committee members do not have the temperament to “disagree and commit”, which means that if any committee member raises an objection and/or filibusters then the issue typically dies in committee ｣
https://www.haskellforall.com/2025/09/steering-committee-retrospective.html
❄️ Beyond package management: How Nix refactored my digital life / jimmyff
https://www.jimmyff.co.uk/blog/beyond-package-management-how-nix-refactored-my-digital-life/
⚡ Unix Co-Creator Brian Kernighan on Rust, Distros and NixOS | The New Stack
‘”I have written only one Rust program, so you should take all of this with a giant grain of salt,” he said. “And I found it a — pain… I just couldn’t grok the mechanisms that were required to do memory safety, in a program where memory wasn’t even an issue!”
https://thenewstack.io/unix-co-creator-brian-kernighan-on-rust-distros-and-nixos/
To tell the truth, I am disappointed.
The Anduril incident last year was really bad. People were rightfully opposed to Anduril occupying more of the community space. It was important enough for SC candidates to be asked their opinions, and many of them rejected the idea outright, and some of them were wishy-washy on it.
And yet, somehow, it all came to a point where the SC doesn't see a serious problem in Anduril receiving a seat in the main governance body.
The Zulip discussion last year was focused around establishing SC, to get ultimate authority for governance, and to restore community trust. I think those goals were not achieved. SC has been very reactive on many issues in the past, and now it also makes mistakes and instead of acknowledging it, publishes dismissive responses.
I don't think this is working out. It also actively reduces my trust, because I've seen many people I trust vouch for many SC members, who didn't really deliver. Another election cycle will not fix this.
To tell the truth, I am disappointed.
The Anduril incident last year was really bad. People were rightfully opposed to Anduril occupying more of the community space. It was important enough for SC candidates to be asked their opinions, and many of them rejected the idea outright, and some of them were wishy-washy on it.
And yet, somehow, it all came to a point where the SC doesn't see a serious problem in Anduril receiving a seat in the main governance body.
The Zulip discussion last year was focused around establishing SC, to get ultimate authority for governance, and to restore community trust. I think those goals were not achieved. SC has been very reactive on many issues in the past, and now it also makes mistakes and instead of acknowledging it, publishes dismissive responses.
I don't think this is working out. It also actively reduces my trust, because I've seen many people I trust vouch for many SC members, who didn't really deliver. Another election cycle will not fix this.
Sigh, so we've got an official SC response, here: https://discourse.nixos.org/t/statement-on-a-steering-committee-member-joining-anduril/69007
As the response correctly points out, there are two problems here: the failure to update on CoI and the Anduril employment.
CoI is a serious issue. Tom has informed the SC in advance - that's good! But SC has failed to inform the community. I'm not sure how a "living document" is relevant to that - SC provided many updates to the community via Discourse. A Discourse post would be perfectly fine here, too. The response doesn't address why the post was never made, though?
For Anduril employment, though... Anduril sponsoring NixCon last year has contributed to community split. An open letter was written, and many prolific contributors (including present SC members) commented against Anduril: https://discourse.nixos.org/t/should-organizations-relating-to-the-defense-sector-being-able-to-sponsor-nixos/41252?u=kfearsoff
Furthermore, when running for SC, there was a question about MIC sponsorships. Many rejected them. So I don't think it's unreasonable to expect SC members to have a problem with Anduril.
Sigh, so apparently Tom Berek of Steering Committee is now working for Anduril. You know, that same Anduril that caused an open letter denouncing MIC sponsoring community events. I don't see how it's acceptable for SC members to work for Anduril, especially in the wake of the whole, you know...
The failure to provide an update to his conflict of interest (and two SC members stating their personal opinions that they don't see much of an issue) is a breach of trust. This means, once again, that the community has to organize by themselves, and demand accountability from people in power. To this end, please spread this information far and wide, and give @nyanbinary a hug. And go support your local #Lix and #Aux representatives.
Original post: https://discourse.nixos.org/t/sc-member-tomberek-works-for-anduril/68971
Archive: https://web.archive.org/web/20250906212959/https://discourse.nixos.org/t/sc-member-tomberek-works-for-anduril/68971
Day 2 of #nixcon and I'm waiting for the train.
I'll be presenting at 15:00 CET a high level overview of the systems that build #nixos, so if you're interested in that drop by the Aula room or view it live at https://2025.nixcon.org/live/!
Day 2 of #nixcon and I'm waiting for the train.
I'll be presenting at 15:00 CET a high level overview of the systems that build #nixos, so if you're interested in that drop by the Aula room or view it live at https://2025.nixcon.org/live/!
Yes! I have finally shut down my last Flatcar Linux system 🥳
It’s pretty cool that the Flatcar setup ran largely unchanged since 2016, but nowadays I prefer #NixOS, and I finally got around to moving the last two VMs.
Est‑ce qu’une personne fan de #nixos serait d’accord de m’assister dans la mise en place du #flake Spicetify-Nix svp ?
Ça fait des heures que je suis dessus, j’arrive à changer les couleurs de spotify mais pas le thème… 🤯
Merci
#nix
Est‑ce qu’une personne fan de #nixos serait d’accord de m’assister dans la mise en place du #flake Spicetify-Nix svp ?
Ça fait des heures que je suis dessus, j’arrive à changer les couleurs de spotify mais pas le thème… 🤯
Merci
#nix
Also #proxmox “yeah btw q35 pci passthrough is broken atm. lol sorry”
v9 has really made me think about looking elsewhere for something like it. theres a lot it gets right but v9 is proving hard to love as the project (probably unsurprisingly given the vmware stuff) is lurching towards enterprises.
i have literally run proxmox almost non stop since 8 years everywhere. perhaps i should give it a break and chill and also not upgrade to .0 on “pseudo prod” homelab machines.
One of my favourite features is that because it's a Go binary it can be run as a client on multiple OS'. So i can run it on my primary #MacOS system to admin my nodes running on #Linux.
I wrote a blog post at the beginning of the year about how I set it up on a cheap 1L mini PC (along with relevant configuration.nix file):
https://blog.hetherington.uk/2025/01/setting-up-incus-with-zfs-on-nixos/
Another call out for help in the #Linux and #nixos community!
We REALLY want to get the #nixbook installer to be able to install #flatpak during (or right after) the calamares installation.
Currently its installing on first boot of nixbook, but it's janky, and causing some downstream issues.
I FEEL LIKE this should be fixable.
Again, the issue is that we want to install a handful of flatpaks after the nixos build, but it gets cranky with no DBUS.
Another call out for help in the #Linux and #nixos community!
We REALLY want to get the #nixbook installer to be able to install #flatpak during (or right after) the calamares installation.
Currently its installing on first boot of nixbook, but it's janky, and causing some downstream issues.
I FEEL LIKE this should be fixable.
Again, the issue is that we want to install a handful of flatpaks after the nixos build, but it gets cranky with no DBUS.
Last week I participated in the quadrennial large Dutch hacker camp, #WHY2025. It was a blast.
It's interesting how many ways there are to experience it: I helped organize in the Info team, hung out at the #NixOS Village, gave a talk about the IT infrastructure at Museum @EICAS , went into a rabbithole debugging the Linux kernel (more on that in a separate toot), joined jamsessions, caught some talks, met many interesting folks, and much more. Serious topics (like voting systems, global politics and security) mix with more lighthearted fun (Flamethrowers, Faxe Kondi and heaps of colorful LEDs). From the 40th anniversary of @phrack to teenagers finding their own way.
I think what unites us all is the sense of curiosity and creativity.
Last week I participated in the quadrennial large Dutch hacker camp, #WHY2025. It was a blast.
It's interesting how many ways there are to experience it: I helped organize in the Info team, hung out at the #NixOS Village, gave a talk about the IT infrastructure at Museum @EICAS , went into a rabbithole debugging the Linux kernel (more on that in a separate toot), joined jamsessions, caught some talks, met many interesting folks, and much more. Serious topics (like voting systems, global politics and security) mix with more lighthearted fun (Flamethrowers, Faxe Kondi and heaps of colorful LEDs). From the 40th anniversary of @phrack to teenagers finding their own way.
I think what unites us all is the sense of curiosity and creativity.
Considering recent events I'd like to believe that projects will start moving away from github (NixOS and Flatpak come to mind) but I have a hard time believing anything is gonna come of this realistically. Oh well, I should move the last few repos I have on github over to Codeberg or Disroot.
#nixos #flatpak #flathub #codeberg #github
A space for Bonfire maintainers and contributors to communicate
