Update 2023-05-03

[lheckemann]

General business

Present in the meeting: no synchronous meeting took place; update prepared by @lheckemann and approved by @kevincox and @edolstra

Agenda for today:

Draft RFCs

• RFC 17: Intensional Store
• RFC 75: Declarative wrappers
• RFC 83: Common interface package sets
• RFC 98: Community Team
• RFC 99: Change default shell from bash to oil
• RFC 100: Sign commits
• RFC 105: Nix flake labels
• RFC 107: Nixpkgs version attribute usage normalization
• RFC 118: Extra semicolon as a warning instead of an syntax error
• RFC 120: Discourage nested with expressions
• RFC 123: Flake names
• RFC 137: Set Nix language version
• RFC 139: Declarative filesystem layouts
• RFC 141: Private Derivations

Unlabelled and New RFCs

• RFC 143: Nix Store ACLs opened for nominations
• RFC 144: Versioned Flake References opened for nominations
• RFC 145: Doc-comments opened for nominations; currently one accepted, 2 rejected, one outstanding (infinisil)
• RFC 146: Meta.Categories, not Filesystem Directory Trees opened for nominations

RFCs Open for Nominations

• RFC 140: Simple Package Paths Lack of clarity on authorship-shepherding exclusivity. RFCSC's position:
  • sees this as not much of an issue, partly because shepherding often results in contributing to the text of an RFC anyway;
  • RFCSC shall avoid selecting a shepherd team that does not include any opposing voices when such voices are present in the discussion;
  • Formalising this is not necessary, but if people feel the need and are willing to write an RFC to codify this it will of course be considered like any other RFC.

RFCs in Discussion

• RFC 101: Nix formatting Meeting took place yesterday, no action required
• RFC 109: Nixpkgs Generated Code Policy shepherd leader considering switching to co-author role. RFCSC does not consider this necessary, but this would not make the shepherd team too small so the team is welcome to decide to make this change
• RFC 110: Add "inherit-as-list" syntax construct to the Nix language Nix team requested changes, these are still pending
• RFC 114: Code of Conduct for NixOS Community Eelco will ask for a shepherd meeting
• RFC 127: Nixpkgs issues and warnings Meeting took place, no action required
• RFC 132: Meson Builds Nix No updates
• RFC 133: Git hashing and Git-hashing-based remote stores Author "to catch up completely";
• RFC 136: A plan to stabilize Flakes and the new CLI incrementally discussion ongoing
• RFC 138: Developing RFCs in repositories moved to draft based on decision from partial shepherd team and author.

RFCs in FCP

None

Accepted/Rejected/Closed

None

Discussion points

Apologies for the many missed meetings. Absences due to illness and travel have repeatedly prevented enough of the team from coming together to run a meeting.

Leader of next meeting

@tomberek will lead the next meeting on 2023-05-17

https://pad.mayflower.de/nixos-rfc-steering-committee

[infinisil]

I PM'd @lheckemann about this as well, but I can also just mention it here:

RFC 140 has 4 shepherd nominations (see the description, I summarized them there), but no shepherds were decided here. This is currently blocking the RFC from proceeding.

[nixos-discourse]

This issue has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/improving-our-rfc-process/28552/1