Closed Ericson2314 closed 7 months ago
OK added descriptions
Should I still wait with merging until roberth gave it a look?
I'll try to get another Nix team person to weigh in
another Nix team person
I kinda already started typing. Did you mean someone other me? That would be good. Nonetheless here are my thoughts:
Might CLI stabilization be a better choice? It'd be good to finish ongoing projects first, but then we might underestimate the effect on consistency from having done CLI review together. We have guidelines, but those are probably not sufficient. I wonder how much can be done without requiring an equal amount of input from team members.
We should organize those issues into an epic or tracking issue, along with
and (just for context) perhaps even
Our ecosystem-wide data model is slightly off in many places. I think this strategy is generally applicable
I'm conflicted about the size and scope of such feature flags. We have multiple fixes, and by balling them together we may avoid some unnecessary compatibility logic, which we'd have to support indefinitely. But also it risks creating a dragged out change process as with Flakes.
@roberth I meant you, or baring that, someone else. I.e. not me alone. Not excluding you :).
Yeah re @roberth the ideal thing would be some epics, and the GSOC person can simple start on what bite-sized pieces are not done by the time summer rolls around, but sadly I think grant processes punish agility like that.
Is there anything missing here or can I go ahead and merge this?
@Janik-Haag Yeah it can be merged. @roberth and I agree the stuff he wrote is not for changing it, but for following this up with more ideas if we like.
CC @roberth