On 21-02-2016 15:28:08, Bjørn Forsman wrote: > On 21 February 2016 at 15:17, zimbatm <[email protected]> wrote: > > tl,td; I think that we should split nixpkgs/pkgs in two > > Another way to do it is the Linux kernel way. Instead of splitting the > (git) repository in two (or more) pieces, split _maintenance > responsibility_ into a hierarchy. This is opposite to the flat > responsibility model NixOS development use today.
I completely second this. The problem is IMHO _not_ that the repo gets big (there are other repos which are way, way bigger than nixpkgs) but the development model. AFAIK I said that before on this list. The problem is that everyone who wants to be a contributer gets push access to master. It just screams at you "I won't scale"! > > In such a model, PRs are initially made against a topic tree and then > each topic tree periodically submit aggregate PRs back to the main > tree. > > Some possible topic trees: > > * nixos (modules etc.) > * desktops environments (KDE, GNOME) > * package updates > * new packages > > Just my thoughts... > Exactly what I'd propose. -- Mit freundlichen Grüßen, Kind regards, Matthias Beyer Proudly sent with mutt. Happily signed with gnupg.
signature.asc
Description: PGP signature
_______________________________________________ nix-dev mailing list [email protected] http://lists.science.uu.nl/mailman/listinfo/nix-dev
