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

Feature: eliminate "pre-FCP" procedures for merge/close/postpone #288

Open
nikomatsakis opened this issue Jul 27, 2020 · 0 comments
Open

Comments

@nikomatsakis
Copy link
Contributor

As discussed in rust-lang/wg-governance#38, I would like to streamline our rfcbot procedures as follows:

First, eliminate the "pre-FCP" period for fcp merge. What this means is that when someone proposed "rfcbot fcp merge", we go immediately into the "final-comment-period". The final comment period lasts until all of the following have occurred:

  • 10 days have elapsed.
  • Sufficient team members have checked their boxes.
  • There are no unresolved concerns.

Second, make close/postpone easier. In the case of close/postpone, we would also go immediately to final comment period, but with the following ending conditions:

  • 10 days have elapsed.
  • there are no unresolved concerns

In particular, we would not have "checkboxes" for close/postpone, and would instead just ping the team to give them a chance to raise concerns.

This is based on the following observations:

  • Once an rfcbot fcp merge occurs, people treat it as though FCP has occurred and there is immediate discussion. It usually takes way longer to get all the team members to check their boxes, and the final 10 days is almost always empty space.
  • Similarly, closing/postponing is awfully hard and it's a lot of busy work to get folks to check their boxes just to keep the status quo.
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

1 participant