The RFC Steering Committee (RFCSC), originally defined by RFC 36, is responsible for managing the RFC process. It usually consists of five members with a rotation every year. Since another year has passed since the last rotation, it’s time to look for new members! To read more about this rotation process, see RFC 43.
In particular, @kevincox and @infinisil intend on stepping down.
@kevincox has been in the RFCSC for 3 years, and @infinisil for a bit over a year. Thanks for all the contributions!
If you are interested in joining the RFCSC, leave a comment in this thread with your nomination. You can also nominate other people if they agree to it.
Responsibilities of the RFCSC
The team holds a regular ~30min online meeting every two weeks. At least three of the five members are needed to hold the meeting. As such, members are expected to join most of the time.
During these meetings, the team takes care of supervising the RFC process:
- Encourage Shepherd Team nominations for new RFCs
- Decide the Shepherd Team and Shepherd Leader with enough nominations for an RFC
- Supervising that the Shepherd team are making progress on the RFC
- Merge or close RFCs depending on the Shepherd team’s decision
Notably the RFCSC has no special responsibility or authority over RFC contents. Whether RFCs get accepted or rejected is entirely up to the Shepherd Team.
FAQ
What does one need for an application?
There’s no formal requirements for an application other than having a GitHub and Matrix account. Showing interest is enough. However experience in the Nix community and the RFC process is preferred.
What time do you meet?
We will find a new meeting time based on the availibitiy of the new comittee.
Is a microphone/camera needed?
A microphone is needed for the meetings. Camera is optional.