Previously in Tweag
Next in Tweag
Making Nix solve people’s problems
Documentation
- @fricklerhandwerk published a report about working on Nix documentation
- @fricklerhandwerk added GitHub issue templates in Nixpkgs and in Nix to help reporting about missing documentation
- @solene crawled into the NixOS wiki to find obsolete pages and get them removed (thanks to @Mic92 who has permissions to delete pages)
jupyterWith
improvements
@djacu continued his work on jupyterWith:
Making Nix work reliably everywhere
-
@thufschmitt investigated a number of Nix performance/correctness issues:
- A very promising low-hanging fruit performance-wise turned out to just be a matter of wrong debug message: Nix was already doing the right thing (multipexing the HTTP requests and reusing sessions), although the logs seemed to indicate otherwise
-
nix-collect-garbage
seemed to be overly conservative when ran throughsudo
. This turned out to be a bad interaction between the waynix
searches for GC roots and a feature ofsudo
. Hopefully we can provide a good-enough workaround on the Nix side. - Fetching an invalid reference from GitHub can lead to a very strange error. This turned out to be due to the cache used by Nix not being precise enough.
- @Yoriksar and @infinisil are still working at getting systemd-boot to boot from ZFS, a systemd bug has surfaced and has been addressed in upstream
- @thufschmitt published the NixOS foundation board meeting notes of August and September
Making Nix ubiquitous
-
@solene added a ccache development environment for Nix, this can dramatically reduce Nix rebuild time. You can use it with
nix develop .#ccacheStdenv
- @jlesquembre added a tmate module for home-manager accompanied by a NixOS module which looks good to be merged
- @radvendii is compiling adoption metrics into graphs on a website.
Blog posts and medias
-
@fricklerhandwerk wrote a report about his four months of work on Nix documentation
-
@torhovland shared in a blog post about reusing Rust software using Nix flakes
-
@fuzzypixelz published about optimizing nickel array contracts, the result of his internship.
-
@bjth hosted the Summer of Nix 2022 lecture Real world DevOps with Nix by @lucperkins
Nickel
- @jlesquembre added Nickel related packages into Nixpkgs tree-sitter nickel grammer and a vim nickel plugin
What’s coming next?
Following our engagement from this summer, here are our plans for the coming weeks:
Making Nix solve people’s problems
Nix language tutorial
@fricklerhandwerk will continue (and ship!) its Nix language tutorial
Nix contributors onboarding
@balsoft will work on the onboarding experience for new contributors to the nix
repository, improving the hacking guide and trying to provide a better off-the-shelf development environment
A new jupyterWith
The rewrite of jupyterWith
that we have been working on for quite some time already is close to reaching feature parity with the current version (Yay ). @djacu will wrap-up the remaining issues, and make that the official version
Making Nix work reliably everywhere
Nix maintainers team
@thufschmitt and @frickelerhandwek started some effort towards gathering a proper team to bake the maintenance of Nix. Things are very fuzzy at that point, but hopefully we’ll be able get something started in the coming weeks.
Installer
@mkaito, @solene and @thufschmitt will keep the started work towards helping with a better official installer for Nix.
Nixpkgs work
As part of the work on the nixpkgs architecture
team, @infinisil opened an RFC to replace parts of the dready all-packages.nix
by a convention-based directory structure
Tests, tests, tests
@solene will try to untangle the Nix test suite to hopefully make it faster and more reliable. Lots of open questions there, so your input is welcome
Making Nix ubiquitous
Metrics
@Ravendii started gathering some metrics on the binary cache usage. This is still in an early stage, so he’ll work on improving it in the coming weeks.
Learning videos
@bjth is working on a series of short learning videos for Nix. Still in infancy, but hopefully that will complete the existing arsenal of learning material and complement @fricklerhandwerk’s work
Marketing team
@bjth recently joined the marketing team which has been quite dormant in the last months, and will with @garbas and others reboot its activity
build fast and reproducible