@neil #BSSG looks like a really polished static blog generator. Interesting that the entirety of #nix / #nixOS #nixpkgs has no mention whatsoever of it.

https://bssg.dragas.net/

Did I break tree-sitter or did #nixpkgs break tree-sitter? HALP #Neovim

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.

#NixOS#Nixpkgs#Nix

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.

#NixOS#Nix#Nixpkgs

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

#NixOS#Nix#Nixpkgs

TBH why the hell is #microsoft edge in #nixpkgs anyways

> goes down the rabbit hole of the origin of "legacyPackages" naming

> finds no good reason (yada yada nested package attributes and nix flake show whatever) that would ever allow it to be properly addressed in #nixpkgs, the one package set most people will always have to interact with

> decides to refer to upstream #nix as legacyNix because it makes just as much sense

> goes down the rabbit hole of the origin of "legacyPackages" naming

> finds no good reason (yada yada nested package attributes and nix flake show whatever) that would ever allow it to be properly addressed in #nixpkgs, the one package set most people will always have to interact with

> decides to refer to upstream #nix as legacyNix because it makes just as much sense

Furthermore, Tenacity is now in #Nixpkgs unstable for macOS on both Intel and Apple Silicon! This complements the existing Linux ports on Nixpkgs 25.05 that run on both x86 (32- and 64-bit) and ARM (64-bit only).

The takeaway? Tenacity runs everywhere, and where we lack in official binaries, we are privileged to have an awesome community fill in the gaps! 😄

Furthermore, Tenacity is now in #Nixpkgs unstable for macOS on both Intel and Apple Silicon! This complements the existing Linux ports on Nixpkgs 25.05 that run on both x86 (32- and 64-bit) and ARM (64-bit only).

The takeaway? Tenacity runs everywhere, and where we lack in official binaries, we are privileged to have an awesome community fill in the gaps! 😄

@quillmatiq this looks fantastic! Can't believe there isn't a module, not even a package yet in #NixOS #nixpkgs
Looks like I got something to hack on once I get around to it ☺️

EDIT: looks like they ship a Flake, package and module upstream! 🤩

@bonfire

NixOS 25.05 "Warbler" released with GNOME 48, initial support for the COSMIC desktop, reworked Mesa graphics drivers packaging, new modules, Cinnamon 6.4

https://nixos.org/blog/announcements/2025/nixos-2505/

#nixos #linux #nixpkgs