@dikaiosune After chatting more with @nikomatsakis, here’s an updated proposal:
rfcbot
Commands
-
@rfcbot: fcp [merge|close|postpone]
- “Motion to fcp”
- Puts the RFC on the dashboard of everyone in any tagged T-team, until they’ve “reviewed” the motion
- Should be accompanied by detailed summary of discussion and rationale for disposition
-
@rfcbot: fcp cancel
- Cancel the motion to FCP, clearing it off dashboards
-
@rfcbot: concern foo
- Where “foo” is an arbitrary name for a blocking concern that needs to be addressed before moving to FCP
- The name spans from after “concern” to the end of the line
-
@rfcbox: resolved foo
- Marks concern “foo” as being addressed
-
@rfcbot: reviewed
- Marks the RFC as having been reviewed by the subteam member
- Everyone on the tagged subteams should leave such a comment; can come before or after any concerns
-
@rfcbot: f? @user
- Requests feedback from
@user
- Cleared when
@user
leaves a comment on thread
- Requests feedback from
Bot actions
Optional functionality, but would be very nice:
-
Once everyone has reviewed and there are no outstanding objections, post a comment saying that “Consensus reached to enter FCP for [merge|close|postpone]” with link back to the motion to FCP.
-
Once a week has passed since entering FCP, if no new
concern
s have been registered, post a comment saying “Consensus reached to [merge|close|postpone]”- If concerns were raised, as soon as they are resolved (and it’s more than a week since FCP), post the comment
-
Comment @user when it has been a week since a motion to FCP and @user has not yet reviewed
Dashboards
Ideally, there’s just one dashboard you go to, which is personalized for you.
At the top:
- Shows each RFC that still needs a
reviewed
comment from you (subteam members only) - Shows any outstanding
f?
requests
Below:
- Shows all RFCs in motion to FCP, or actually in FCP, together with the status of all subteam members (reviewed, concerns w/) w/ links to originating comments
- Organized by subteam