From b8cf4186d6f785e3fe051c070a96c6c8edde0c00 Mon Sep 17 00:00:00 2001 From: "Carol (Nichols || Goulding)" Date: Tue, 25 Apr 2017 10:18:05 -0400 Subject: [PATCH] Clarify what rfcbot thinks a week is I expected a week to mean 7 calendar days, but rfcbot thinks it's 10 calendar days :) https://github.com/dikaiosune/rust-dashboard/blob/dae280e5baf2174daa2bcb8197d00201d4071bd5/src/github/nag.rs#L299-L300 --- README.md | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index 5680d0b0e2b..58ea23e3f72 100644 --- a/README.md +++ b/README.md @@ -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