We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Present in the meeting:
Agenda for today:
version
None
@kloenk (if available) or @edolstra will lead the next meeting on 2021-12-15
pad.mayflower.de/nixos-rfc-steering-committee
The text was updated successfully, but these errors were encountered:
[x] RFC 62: Content-addressed paths — apparently nearly ready for FCP 🎉
Where is this from? I am not sure we had an RFC meeting yet. I left some comments on things I would like to see happen.
Sorry, something went wrong.
[x] RFC 62: Content-addressed paths — apparently nearly ready for FCP tada Where is this from? I am not sure we had an RFC meeting yet. I left some comments on things I would like to see happen.
[x] RFC 62: Content-addressed paths — apparently nearly ready for FCP tada
This was based on what @edolstra said, but your concerns seems valid.
No branches or pull requests
General business
Present in the meeting:
Agenda for today:
Draft RFCs
Unlabelled and New RFCs
RFCs Open for Nominations
version
attribute usage normalization Accepted nominations: @7c6f434c, @jeff-hykin; need some more. Nominate @sternenseemann?RFCs in Discussion
RFCs in FCP
None
Accepted/Rejected/Closed
None
Discussion points
Leader of next meeting
@kloenk (if available) or @edolstra will lead the next meeting on 2021-12-15
pad.mayflower.de/nixos-rfc-steering-committee
The text was updated successfully, but these errors were encountered: