RFCs and other major decisions go through a Final Comment Period of 10 days, during which time they are tagged and advertised. This ensures that people have a sufficient heads up to weigh in on discussions that are nearing a decision.
However, we previously required all team members to actively approve going into FCP, in addition to the 10 day period. In practice, this often means that items are left in limbo with one or two members taking a long time to get around to reviewing.
OTOH, we very much value our consensus-based decision-making process, and don’t want to lose that.
To find a better balance, we’re tweaking rfcbot so that an item can enter FCP if:
- A majority of the team has actively signed off
- No team-member has registered a concern
- There are fewer than 3 approvals remaining
What this means is that any team member can actively withhold consent and block FCP on that basis, but RFCs will no longer be passively blocked as often.
The exact configuration here will probably need further tweaking, but I wanted to let everyone know that FCP will now be entered without requiring a full set of checkmarks.