# Refining RFCs part 3: Async decisions

**URL:** <https://internals.rust-lang.org/t/refining-rfcs-part-3-async-decisions/3658>\
**Category:** Uncategorized\
**Created:** [July 6, 2016, 12:50am UTC](https://internals.rust-lang.org/t/refining-rfcs-part-3-async-decisions/3658 "2016-07-06T00:50:11Z")\
**Posts on this page:** 1\
**Showing post:** 33

<div class="post-metadata">

**Author:** ![aturon](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/aturon/32/3272_2.png) [@aturon](https://internals.rust-lang.org/u/aturon)\
**Post date:** [July 26, 2016, 2:45pm UTC](https://internals.rust-lang.org/t/refining-rfcs-part-3-async-decisions/3658/33 "2016-07-26T14:45:57Z")

</div>

@dikaiosune After chatting more with @nikomatsakis, here’s an updated proposal:

# rfcbot

## Commands

- `@rfcbot: fcp [merge|close|postpone]`

- `@rfcbot: fcp cancel`

- `@rfcbot: concern foo`

- `@rfcbox: resolved foo`

- `@rfcbot: reviewed`

- `@rfcbot: f? @user`

## 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]”

- 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

---

_[View the full topic](https://internals.rust-lang.org/t/refining-rfcs-part-3-async-decisions/3658)._