RFC 136 (“A plan to stabilize Flakes and the new CLI incrementally”) has been going through a number of iterations. In particular, it saw its scope expanded a lot, from a simple roadmap towards stabilizing the new CLI to a large set of general principles around the development of Nix.
The reasoning behind that is that it was sometime unclear where exactly the “CLI, then flakes” plan was coming from. That lead to us writing a bunch more background material on layering/modularity, and stabilizing things in general. The idea was that the broader material could both provide an “origin story” for the plan, and (hopefully) ensure we don’t get into this situation again. The counterargument is that it makes this RFC too big and unfocused and that we should rather focus on solving the problem at hand rather than trying to prematurely abstract over it.
This now requires some more feedback, and in particular answering the question: Is the expanded scope of this RFC good, or should the new material be left for the future?
Please sound off in the comments, letting us know whether you think we should keep or cut this new material! That will inform what we do next, and then we can hopefully wrap this thing up.
I personally have my own very strong opinion about that, but I’ll refrain from mentioning it in this post