People who develop tools in the #Nix and #NixOS ecosystem and hate Anduril:
Are you willing to adopt a license for your tools which would prevent the Andurils of the world from using them?
Yes, this means a license not approved by OSI or FSF
👋 Hello! GNU Guix is on @hachyderm - yay!
If you haven't heard of #gnu #guix we're a free software project that's created a hosted package manager (think homebrew or flatpak) and a GNU/Linux distribution.
GNU Guix uses the functional packaging approach pioneered by #nix and adds a user-experience and system configuration system. It uses a DSL that's based on Guile Scheme. You can use it configure your home environment, dev environments or the entire system using a declarative and transactional definition.
We hope to tell people about the project and our latest news. We'd love to engage with people around #freesoftware #guile #scheme and more general #linux topics!
As talk, we'll be hearing from @notthebee who recently tinkered on using #NixOS to power his couch gaming PC.
For our anniversary, we're reserving more time for hacking, troubleshooting and networking than before, so feel free to bring your laptops, projects and #Nix problems with you! And even for complete beginners, this may be a great opportunity to learn from more experienced Nix users.
Celebrating our first anniversary, our next #NixOS meetup is scheduled for Wednesday, December 18 at the Mathematikon in #Heidelberg. For the first time, we are separating our Nix and Rust meetup, so be prepared for another announcement of our Rust anniversary meetup.
No matter if you use #Nix 
or #Lix 
on #Linux or #macOS, everyone is welcome to join us.
Pizza and drinks will be provided. If you plan to join us, please register for the event here:
rheinneckar.events/events/2f36…
One year after our first Nix & Rust meetup, we are meeting again in Heidelberg for our first anniversary! 🎊 Note that for the first time, this meetup is only about Nix and NixOS, the declarative package manager and Linux distribution.rheinneckar.events
#deltachat_desktop 1.46 rollout is basically done except for #homebrew and #nix (the Nix package is already in the works, home-brew could use some help)
There are also some users reporting crashes with the flatpak: github.com/deltachat/deltachat…
And with the MacOS version from the appstore github.com/deltachat/deltachat…
So if you have problems tell us, additional information will help us to solve these issues. (frankly we rely on user feedback because we have #noTelemetry)
Delta Chat desktop flatpak 1.46.0, Ubuntu 22.04, Gnome shell 42.9, Wayland Today I suddenly have the problem that deltachat-desktop refuses to start. Here are the errors in the terminal when I atte...GitHub
I like #Nix, I do not like what has happened to it. #NixOS is an incredible technology and it deserves better. Nobody else has started the process so I guess I have to be the one to do it. We are forking. I would rather try and fail alongside all the people who love Nix but were pushed away from the project than give up.
I wrote a matrix bot for nixpkgs pull request notifications.
It‘s like the cool https//nixpk.gs/tracker.html by @qyliss, which shows you which release channels a pull request has reached.
With the bot you can subscribe and get notifications, whenever it reaches a channel instead of hammering F5 in your browser tab.
Just open a query to matrix.to/#/@nixpkgs-bot:maral… and send "help".
Looking forward to you all stress testing it!
You're invited to talk on Matrix. If you don't already have a client this link will help you pick one, and join the conversation. If you already have one, this link will help you join the conversationmatrix.to
If you use #NixOS or #nix and want to contribute with the new release (22.05), please check one of the failing builds from zh.fail/ and throw a PR at github.com/nixos/nixpkgs by following the instructions from this issue github.com/NixOS/nixpkgs/issue….
Thank you!
Mission Every time we branch off a release we stabilize the release branch. Our goal here is to get as little as possible jobs failing on the trunk/master jobsets. We call this effort "Zero Hy...GitHub
