Attendees: @fricklerhandwerk @Ericson2314 @roberth @edolstra (later @thufschmitt @tomberek)
Agenda
- discuss whether and, if, how to approach picking up the flakes proposal
- or at least write down what to do next and when (15 min)
- continue working on stabilisation of
nixcommands (60 min) - work off discussion column (45 min)
CLI Stabilisation
-
Make 'nix store gc' use the auto-GC policy by edolstra · Pull Request #7851 · NixOS/nix · GitHub
- did a collaborative review
- decision: needs more work, continue async
Flakes
- decision: do not commit to anything until the new CLI is stable
Discussion
-
Guidelines for extensible JSON · Issue #7823 · NixOS/nix · GitHub
- agreement on proposal
- @roberth will make a PR, @fricklerhandwerk will review
-
Ensure that `self.outPath == ./.` by roberth · Pull Request #7796 · NixOS/nix · GitHub
- agreement that we want this
- assigned to @thufschmitt
-
Source tree abstraction by edolstra · Pull Request #6530 · NixOS/nix · GitHub
- decision: continue on replacing shelling out
gitwithlibgitand break out PRs to reduce the diff of the feature itself
- decision: continue on replacing shelling out
-
Keep splitting libcmd headers & files by Ericson2314 · Pull Request #7748 · NixOS/nix · GitHub
- some final changes requested by @edolstra, otherwise good to merge
Team process
-
@fricklerhandwerk: repeating myself: can we please find a rule for what to prioritise given a long list of discussion items?
-
2022 community survey pointed out contributor experience
- this sounds like a clear mandate, we should assign this higher priority
- @thufschmitt: right, so far we have been sidetracked by many other issues
-
@Ericson2314: focus on RFC-related PRs
-
@fricklerhandwerk: would it help to add a label for topics touching on accepted RFCs?
-
@roberth: yes, will add a label
- could even have a label per RFC
-
@fricklerhandwerk: no, you cannot remove labels later without losing information
- and the full label overview should be self-explanatory, and with per-RFC labels it will accumulate cruft
- so far it has shown to be effective to itemise our work and have as little recurrent tasks as possible
- simply sorting items by priority based on label worked well and we should continue that
- (agreement)
-
@thufschmitt: also have a milestone per RFC, as it allows for better querying
-
@fricklerhandwerk: yes, but only as additional infromation, not as a primary tool
- otherwise we’d have to dedicate time to look at milestones regularly, which is likely not to actually happen
-
@fricklerhandwerk: yes, but only as additional infromation, not as a primary tool
-
@roberth: yes, will add a label
-
@roberth: problem is that contributors can’t mark their work accordingly
- @thufschmitt: no problem, we’re triaging everything anyway
-
@fricklerhandwerk: would it help to add a label for topics touching on accepted RFCs?
-
2022 community survey pointed out contributor experience
- general agreement
-
@fricklerhandwerk will make PRs against the team handbook to further encode our agreed-upon process, once time allows
- help welcome!