I’m currently working to found the Nixpkgs Architecture Team, with the goal of solving bigger architectural issues in nixpkgs, such as:
- The inconsistency and variety of override mechanisms
- The file structure of
/pkgs
and how they relate toall-packages.nix
- The problem of nixpkgs becoming too big for a single repository
- And many more
You can read more about the motivation and goals on the team page, I really think this is what nixpkgs needs right now!
The team will hold public discussions, mainly on #nixpkgs-architecture:nixos.org and the weekly meetings. Feel free to join if you’re interested in listening in or bringing your opinion/experience!
While anybody can join the discussion, being a team member means that you’ll have to reach consensus on issues with other team members to make final decisions. If you’re interested in joining the team, please take a look at the team section.
Note that this team is still being formed. The first meeting will be held next week, but the workings of the team and its organization is still to be fully figured out. While I wrote the initial draft, I’d love to get feedback here or in #nixpkgs-architecture:nixos.org. Also feel free to give ideas as to what the team should work on