@willbush Thanks! I’d appreciate help, here’s some pointers:
-
Join the Nixpkgs Architecture Matrix channel or my new weekly office hour to synchronise with me and others for all of the below
-
If you know Rust and are interested in helping out with the
pkgs/by-name
effort specifically, check out the RFC 140 milestone for things to do. While I’m planning to work on most of them myself, if I could offload some of that, it would help a lot! Otherwise, reviews are very appreciated too.Furthermore you can also just look at the nixpkgs-check-by-name codebase and make suggestions for improvements.
This all will be easier to help out with once nixpkgs-check-by-name is in its own repository.
-
As mentioned above, there’s the new architecture label in Nixpkgs. These are open architectural problems left to fix, each of which requiring lots of resources.
- If you see an appropriate issue not labeled yet (hard to keep track of them!), or if you create a new issue for something that’s not tracked yet, let me or another Nixpkgs committer know, so it can be labeled
- If something interests you or you have ideas, engage with comments
- The most impactful, but also most difficult way to help, is to pick up one of these issues and work on a design document/proposal to address it. This might be classified more as research rather than work, and you need to understand the topic very well to make good progress with it.