# Refining RFCs part 2: RFC staging

**URL:** <https://internals.rust-lang.org/t/refining-rfcs-part-2-rfc-staging/3657>\
**Category:** Uncategorized\
**Created:** [July 6, 2016, 12:49am UTC](https://internals.rust-lang.org/t/refining-rfcs-part-2-rfc-staging/3657 "2016-07-06T00:49:41Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![djc](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/djc/32/1592_2.png) [@djc](https://internals.rust-lang.org/u/djc)\
**Post date:** [July 6, 2016, 6:44pm UTC](https://internals.rust-lang.org/t/refining-rfcs-part-2-rfc-staging/3657/7 "2016-07-06T18:44:11Z")

</div>

I think the regular posting of summaries is a really important part of this. I’m informed in this mostly by my experience with Python’s PEP process. The mailing list threads can get pretty unwieldy, but as long as there is a roll-up after a few days of intense discussion of consensus points and open issues, that makes the process much more accessible to contributors with less time on their hands.

The focus on motivation early in the process seems exactly right.

---

_[View the full topic](https://internals.rust-lang.org/t/refining-rfcs-part-2-rfc-staging/3657)._
