2022-12-02 Nix team meeting minutes #13

[fricklerhandwerk]

Attendees: @fricklerhandwerk @thufschmitt @Ericson2314 @roberth @infinisil @edolstra @tomberek

Agenda

• triage items in No Status (25 min)
• discuss items in To Discuss (30 min)

Triaging

• Release 2.12 · Issue #7371 · NixOS/nix · GitHub

  • to discuss

• Deduplicate code between Hydra and Nix · Issue #1164 · NixOS/hydra · GitHub

  • to discuss

• Establish a process for dealing with breaking changes · Issue #7255 · NixOS/nix · GitHub

  • delegate to @Ericson2314 if the previous RFC author doesn’t want to pick it back up
  • postponed

• how should paths be used in the context of lazy trees · Issue #7335 · NixOS/nix · GitHub

  • this is by nature a discussion item, and we agree this is relevant right now
  • to discuss

• Use PCRE for `builtins.match` and `builtins.split` by yorickvP · Pull Request #7336 · NixOS/nix · GitHub

  • @fricklerhandwerk: have to make sure it doesn’t break the interface
  • no agreement on implementation strategy
  • to discuss

• More useful error when command not found on remote by balsoft · Pull Request #6628 · NixOS/nix · GitHub

  • to discuss

• Document the PR policy · Issue #7393 · NixOS/nix · GitHub

  • delegate to @fricklerhandwerk to make a proposal we can discuss
  • postponed

• clarify definition of "installable" by fricklerhandwerk · Pull Request #7376 · NixOS/nix · GitHub

  • to review

• doc: listToAttrs: document repeated keys by aakropotkin · Pull Request #7381 · NixOS/nix · GitHub

  • merge

Discussion

• Release 2.12 · Issue #7371 · NixOS/nix · GitHub

  • decision: @roberth will join @edolstra to cut the release

• @fricklerhandwerk: shall we look at the different categories we discussed to fill the To Status column?

  • @thufschmitt: too much process, so far maintainers can just add things they care about, feel may be controversial, or don’t know how to deal with
  • @fricklerhandwerk: would prefer a predictable process,

• @tomberek: there should be a way to to veto a discussion, otherwise everything will end up in To Discuss

  • @fricklerhandwerk: yes, should be able to postpone by removing the item from the list entirely. it will bubble up eventually if it’s important enough.
  • agreement: added a Postponed column to the project board

• @fricklerhandwerk:

  • proposal:
    • prioritise pull requests over issues
      • @tomberek: agreed, it will increase momentum
      • @thufschmitt: there are more important issues than just PRs
    • interleave issues and PRs
    • prioritise releases when they are due
    • prioritise fixing bugs over adding features
  • agrement, @fricklerhandwerk will make a PR to the maintainer’s handbook