Skip to content

Clarify what rfcbot thinks a week is #1981

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

Merged
merged 1 commit into from
Apr 25, 2017
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 7 additions & 6 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -138,12 +138,13 @@ the conversation has settled, the RFC will enter its *final comment period*
(FCP). This is a final opportunity for the community to comment on the pull
request and is a reminder for all members of the sub-team to be aware of the
RFC.
* The FCP lasts one week. It may be extended if consensus between sub-team
members cannot be reached. At the end of the FCP, the [sub-team] will either
accept the RFC by merging the pull request, assigning the RFC a number
(corresponding to the pull request number), at which point the RFC is 'active',
or reject it by closing the pull request. How exactly the sub-team decide on an
RFC is up to the sub-team.
* The FCP lasts ten calendar days, so that it is open for at least 5 business
days. It may be extended if consensus between sub-team members cannot be
reached. At the end of the FCP, the [sub-team] will either accept the RFC by
merging the pull request, assigning the RFC a number (corresponding to the pull
request number), at which point the RFC is 'active', or reject it by closing
the pull request. How exactly the sub-team decide on an RFC is up to the
sub-team.


## The role of the shepherd
Expand Down