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

consider RFC signoff requirements #75

Open
Licenser opened this issue Sep 23, 2021 · 0 comments
Open

consider RFC signoff requirements #75

Licenser opened this issue Sep 23, 2021 · 0 comments
Labels
documentation Improvements or additions to documentation governance Documentation relating to project/community governance and policies process Process documentation

Comments

@Licenser
Copy link
Member

Currently, RFCs state the following requirement

Before actually entering FCP, *all* members of the subteam must sign off; 
this is often the point at which many subteam members first review the RFC

This can become problematic if a subteam member becomes unavailable, due to vacation, health, or personal reasons. It is worth considering how to phrase this requirement in a way that is accommodating for team members' lives and other unforeseen circumstances.

@darach darach added documentation Improvements or additions to documentation governance Documentation relating to project/community governance and policies process Process documentation labels Sep 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation governance Documentation relating to project/community governance and policies process Process documentation
Projects
None yet
Development

No branches or pull requests

2 participants