New issue
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
[RFC 0044] Disband the Nix Core Team #44
Conversation
* Keep the core team around in its current form and responsibilities. | ||
Would require a fresh attempt to follow through on the relevant | ||
committments to be practical. | ||
* Reform the core team based on what we've learned, including possibly |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would love to hear what was learned anyway!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I learned I was too optimistic (about my time/energy) and thus ended up contributing through this team even less than I feared when it was being formed. That didn't result into me really "blocking" anything, I hope.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@grahamc Any recommendations for where to put that?
0236a91
to
8c53396
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The RFC process has proved to be much more successful than the Nix core team, and I'm grateful for both the efforts on this team, and the continued efforts on the RFC process. I look forward to continuing to improve our collective process and organization, even if this particular experiment did not end up as robust as we had hoped. Thank you for trying with me!
I would like to propose the members of the core team as shepherds: @edolstra @shlevy @peti @vcunat @copumpkin |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems reasonable to me. I'm sad that I haven't had the time or resources to commit to Nix recently, but the community seems to be thriving regardless, so that's good.
Shepherd team is @edolstra @peti @vcunat @copumpkin, with @edolstra as leader. I'd propose we're ready for FCP. |
This RFC is now in Final Comment Period. |
This RFC has been accepted! |
Rendered