In reply to @nbp:mozilla.org
Thus one would set builder = stdenv.mkDerivation; recipe = { /* mkDerivation argument */ }; and a final phase will go after the fix-point to apply the builder to it argument.

Where builder and recipe are attributes of the overridable fixpoint, I suppose?
With something like lib.encapsulate, that would be

lib.encapsulate (this: {
  builder = stdenv.mkDerivation;
  recipe = { name = "hello"; ..... };
  public = this.builder this.recipe;
})

In reply to @philiptaron:matrix.org
At work, we use a approve-commits model, instead of an approve-PR model, which makes the review process substantially lighter. I'm sad that GitHub doesn't let that happen, since I only get the chance to review the whole squashed PR.

In reply to @jade_:matrix.org
this kinda exists with the various pr stacking tools like pkgs.sapling and many others but erm. what if nixpkgs had gerrit, (do not use gerrithub btw it is very broken)

at some point somebody should just be empowered to make decisions.
♥️

at some point somebody should just be empowered to make decisions.
♥️ to this

I'm a little sad that this action is being taken:

Publicly archive the private Nixpkgs Architecture Matrix channel

... as having "direct line" to those interested in architecture and structure rather than the things being built with the structure is quite nice.

In reply to @qyliss:fairydust.space
the "private Nixpkgs Architecture Matrix channel" is not this room