Skip to content
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 Meeting 2019-12-12 #24

Closed
Mic92 opened this issue Dec 12, 2019 · 7 comments
Closed

RFC Meeting 2019-12-12 #24

Mic92 opened this issue Dec 12, 2019 · 7 comments

Comments

@Mic92
Copy link
Member

Mic92 commented Dec 12, 2019

General business

Election will take place

Unlabeled RFCs and New RFCs

RFCs Open for Nominations

RFCs in Discussion

RFCs in FCP

None

Accepted/Rejected

None

Robin will lead the next meeting.

@Mic92
Copy link
Member Author

Mic92 commented Dec 12, 2019

Meeting minutes

Election for RFC steering committee rotation

Starting with next year we will have 3 new members in our RFC committee, while 3
members will leave the team.
The new members are @worldofpeace, @lheckemann, @spacekookie.
The members leaving the team are @shlevy, @globin, @domenkozar.
@edolstra and @Mic92 remain.

Agenda

  • RFC 62: opened for nomination
  • RFC 55: asked @alyssais to become shepherd.
  • RFC 56: opened for discussion
  • RFC 57: asked @jD91mZM2 and @matklad to shepherd
  • RFC 58: asked @Lassulus to become shepherd
  • RFC 40: ask @fpletz to schedule a meeting
  • RFC 42: @globin should re-schedule a new meeting (the old one did not take place)
  • RFC 46: still wait for @grahamc's feedback
  • RFC 50: still @globin needs to schedule a meeting

@7c6f434c
Copy link
Member

7c6f434c commented Dec 12, 2019

Maybe list the shepherds of in-discussion RFCs here? For RFCs lacking enough nominations knowing who is definitely too overloaded with other RFCs would help with choosing whom to nominate. (In today's case you have resolved this, but maybe next time we can save a week on some RFCs this way)

@Mic92
Copy link
Member Author

Mic92 commented Dec 12, 2019

Ideally this would be done in an automated way. Every pr in discussion should have the metadata necessary: https://github.com/NixOS/rfcs/pull/17/files#diff-eef3bb3329dd189b0bf6ffcf143c0b5cR6

There is also an issue related to this: #1

@lheckemann
Copy link
Member

I think it's @spacekookie not @SpaceCookie?

@Mic92
Copy link
Member Author

Mic92 commented Dec 12, 2019

I think it's @spacekookie not @SpaceCookie?

Right!

@worldofpeace
Copy link
Contributor

@shlevy
Copy link
Member

shlevy commented Dec 19, 2019

I'm not feeling well so I will miss the last meeting. It's been great to be part of the team! Maybe I'll join again next year :)

@Mic92 Mic92 closed this as completed Dec 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants