Closed
Description
General business
Present in the meeting: @edolstra @kevincox @lheckemann
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 101: Nix formatting moved from "in discussion", but discussion is active
- 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 138: Developing RFCs in repositories
- RFC 139: Declarative filesystem layouts
- RFC 140: Simple Package Paths FCP cancelled, back in discussion
- RFC 141: Private Derivations
- RFC 149: Cache key rotation WIP, ongoing
Unlabelled and New RFCs
- RFC 151: NixOS port allocator opened for nominations
RFCs Open for Nominations
- RFC 143: Nix Store ACLs open-for-nominations stage announced last time, no nominations yet
- RFC 144: Versioned Flake References still pending more nominations, will be closed in the next round if none are made
- RFC 145: Doc-comments sterni, davhau and asymmetric as shepherd team
- RFC 146: Meta.Categories, not Filesystem Directory Trees no nominations, post standard message
- RFC 148: Pipe operator maralorn accepted, roberth nominated but no response yet
RFCs in Discussion
- RFC 109: Nixpkgs Generated Code Policy Author wants to pass the mantle on; asked kfears, recently active in the discussion, in #dev
- RFC 110: Add "inherit-as-list" syntax construct to the Nix language text updated, Nix team will take another look
- RFC 114: Code of Conduct for NixOS Community Eelco (co-shepherd) will ping
- RFC 127: Nixpkgs issues and warnings meeting being organised
- RFC 132: Meson Builds Nix external blocker is moving
- RFC 133: Git hashing and Git-hashing-based remote stores Kevin will try to get a meeting organised
- RFC 136: A plan to stabilize Flakes and the new CLI incrementally pinged Tom to suggest a meeting for potentially calling FCP
RFCs in FCP
None
Accepted/Rejected/Closed
None
Discussion points
An RFC discussion matrix room will be created, as suggested by @piegamesde -- thanks!
Leader of next meeting
@kevincox will lead the next meeting on 2023-06-28
Metadata
Metadata
Assignees
Labels
No labels