Attendees: @unwhgw-2SOWNaBf6c6k6jg @layus @bKTAyiAjR4COcXhZNHJF_g @regnat @infinisil Round on the current issues to discuss builtins.debug https://github.com/NixOS/nix/pull/4914 Everything good on the design part. Just need the author (or someone else) to fix the CI failure. Flake inputs propagation Mostly https://github.com/NixOS/nix/issues/6549 and https://github.com/NixOS/nix/pull/6550

Nix UX meeting 2022-05-05 Nix UX meeting 2022-05-12 Nix UX meeting 2022-05-19 Nix UX meeting 2022-06-02 Nix UX meeting 2022-06-09 Nix UX meeting 2022-06-30

Round on the current blockers Agenda for the day

Attendees: Eelco, Ben, Guillaume, Yannik, Théophane, Tom + John later Round on the current blockers Flake owner check (Théophane) -> Needs to be merged ! syntax for the installables (John) Should we keep it in the “UX” board Is this an extension to the ^installable syntax? (Addendum after John joined)

Flakes and Git integration The point of this document is to question the UX choice of flakes to only consider files that are tracked by the git repository, ignoring files that are visible in the filesystem. I have obseved many complaints about this design, and I wanted to collect opinions, use cases and stumbling stones at one place, in order to provide the community with a unified design document. All the questions should be adressed, which should make the choice more acceptable to users, as they can get some conviction that their issues have been taken into account for the final decision. This is not about the integration and proeminence of github as the default remote git provider, nor the github:// input shceme for flakes. It is also not about the the fact that flakes make a copy of the content of the current git repository into the store for evaluation. This is adressed by the Source tree abstraction #6530 draft PR. Current design (with nix (Nix) 2.8.0pre20220411_f7276bc) An example: creating a new flake This is the ideal workflow for creating a new flake. The git repo may already exist, but let's assume we start a completely new project for the sake of the demo.

:::info Attendees: @layus @regnat … Agenda: Round on the current blockers Flakes and Git integration (@layus) ::: Issue Review

Round on the current blockers (15 minutes) project board review Debugger flag Approved, but still one open conversation. @bburdette doesn’t really know how to apply the requested change so didn’t do it eelco will have a look at it

Design notes Linked issues (Mostly the result of searching for subflake in the github issues) flakes: allow composing from multiple files Allow folder ignored by git to be used as a subflake Development only flake inputs or different category of inputs More intelligent subflake locking Allow getFlake of in-store paths in pure mode Allow flakes to refer to other flakes by relative path

Round on the current blockers Debugger PR Mergeable o/ Some issues with printing potentially large values, but not a blocker Extra debug info PR Conflicts with the debugger. Might need to choose one to merge first 21:11:07 @edolstra: Maybe the debugger first