+1, but don't transfer issues to the new repo(!). The reason for a separate repo is to increase the barrier to entry for RFCs, we are overwhelmed by the number of RFCs and a lot of them are just random ideas that people come up with and not think through (sorry, but it's the harsh truth). The RFC repo should specify a formal template of how an RFC should be described and everyone should stick to it. This will ensure that:
* **There is less room for ambiguity in the proposals.** This will make it easier to implement RFCs without having to go through yet even more discussions about what an RFC is really about. * **RFCs are only written for proposals which are important enough to warrant time spent writing the RFC**. This should increase their quality and make it more likely that they will be implemented. So please, just close the RFC issues and ask people to write a formal RFC if they are really passionate about their proposal.
