I want to take ownership of this part of the documentation, especially
with the cleanup in https://github.com/NixOS/nixpkgs/pull/245243. Doing so
before that PR is merged also allows me to get notified about any potential
future merge conflicts before they happen.
It is hard to get people to test changes to our kernel expression on
anything other than x86_64 and aarch64 before merging changes.
Therefore, I would like to be notified of PRs opened agains this
file, so that I can hopefully catch breakage before it is merged,
rather than afterwards.
I don't claim ownership of anything, but I would like to be notified
of PRs opened against the following paths where I've put a lot of
work into cleanup and deduplication:
lib/systems
pkgs/stdenv
pkgs/build-support/cc-wrapper
pkgs/development/compilers/gcc
Apparently CODEOWNERS is how you tell github you want to be notified
of such things.
I do a lot of work on QEMU VM and make-disk-image and I was bitten by an
unnotified change recently, so I want to chime in the future changes of
this file.
We currently have 5800 python modules in that path, and we're seeing
roughly 1000 pull requests for these modules per month.
Having @FRidh and @jonringer requested on every PR that touches a
python package isn't helping anyone, nor is it sustainable for any one
person to have that number of incoming notifications.
I think it's time to get rid of that code ownership.
Adds initial work towards a `lib.path` library
Originally proposed in https://github.com/NixOS/nixpkgs/pull/200718, but has
since gone through some revisions
Co-Authored-By: Valentin Gagarin <valentin.gagarin@tweag.io>
Co-Authored-By: Robert Hensing <robert@roberthensing.nl>
glib expression is messy enough as is.
Also rename the `glib-schema-to-var` argument to `schemaIdToVariableMapping` to better match Nixpkgs coding style.
the number of pull requests against documentation is too high to handle
on the side, and getting assigned as reviewer for all of them sends the
wrong message to authors.
