Closed
Description
General business
Present in the meeting: @infinisil @GetPsyched @MMesch @kevincox @tomberek
Onboarding new team
- @GetPsyched: Anything else to push RFCs forward?
- @infinisil: Delegated to the shepherds
- More automated reach-outs would be great, when RFCs are opened or need shepherds
- @MMesch: Discourse or GitHub preferred?
- @infinisil: GitHub for content discussions, Discourse for more reach
NixOS/rfcs#138
- Finding more shepherds in the steering committee
- @MMesch interested in shepherding
- @infinisil will ping the other members as well
Unlabelled and New RFCs
None
RFCs Open for Nominations
- RFC 138: Developing RFCs in repositories
- Still only 1 shepherd
- Posted notice for not enough shepherds
- RFC 167: nixpkgs maintainer requirements
- Still no activity since opening
- Posted notice for not enough shepherds
- RFC 169: Feature parameter names
- No nominations yet, but activity
- Leave as is
RFCs in Discussion
- RFC 132: Meson Builds Nix
- No updates still, posted another ping
- RFC 143: Nix Store ACLs
- No updates
- Leave as is for now
- RFC 146: Meta.Categories, not Filesystem Directory Trees
- Minimal activity
- Leave as is
- RFC 152:
local-overlay
store- No updates since the last ping
- Sent another ping, suggesting drafting
- RFC 163: Portable Service Layer
- Minimal activity
- Matrix channel created but no messages yet
- Leave as is
- RFC 165: Bootspec v2
- Leave as is
- RFC 166: Nix formatting, take two
- Being worked on
RFCs in FCP
None
Leader of next meeting
@kevincox will lead the next meeting on 2024-02-20
Metadata
Metadata
Assignees
Labels
No labels