In this blog post I sketched a proposal to update the pre-RFC process. I'd like to move this forward but I'm not really sure what the best next steps are. I'd appreciate feedback either on the ideas themselves or on what the best next step is.
One thing I think is that maybe it'd be good to more crisply articulate the goals of this change -- I think some of them are non-obvious and maybe could be strengthened
Link to the Internals thread w/ feedback: https://internals.rust-lang.org/t/aic-adventures-in-consensus/9843/20?u=batmanaod
Most notably I want to improve the process of writing RFCs. I think the bar to writing an RFC can be high-ish and I'd like to overall make the process more of a "friendly one". @Ryan Levick had some interesting comments about how, in writing the safe transmute RFC, it was great to be able to work with @Josh Triplett. I think that writing up an idea and opening an RFC that immediates get criticism and sometimes unfriendly feedback can be a bit rough. I also think the "limbo" state of "I don't know if this is even something we really want" isn't great.
In meeting Niko mentions comments starting from this link particularly relevant: https://internals.rust-lang.org/t/aic-adventures-in-consensus/9843/20?u=nikomatsakis