[Nix-dev] Limiting access to only maintained packages and ensuring core packages are maintained

Peter Simons simons at nospf.cryp.to
Mon Sep 5 13:36:30 CEST 2016


laverne writes:

 > A "maintainer" that does not have commit access cannot maintain and
 > is thus not actually a maintainer.

Due to the wonders of Github, it's entirely feasible to maintain
packages without having commit access. A "maintainer" is not necessarily
the person who commits patches but rather the person who writes them
and/or helps other people write them. Once patches exist that improve
the package in some way, they are submitted for review in a Pull Request
via Github and -- assuming the patch is uncontroversial -- subsequently
merged to the distribution.


 > I don't really understand how NixOS's model works and am not
 > confident that anyone does.

If you have any specific question about the process used to develop Nix,
NixOS, and Nixpkgs then please don't hesitate to ask on this mailing
list or -- if you prefer -- on the #NixOS IRC channel. There are quite a
few people who understand how these processes work who will usually be
quite happy to help and share information.

Best regards,
Peter



More information about the nix-dev mailing list