@tqchen @jroesch I updated the process to more closely match the Rust process. A few comments on it:
* I still kept it more lightweight than the Rust process. As a smaller community, I want to strike a balance between formalism and ease of application. * One major difference is in postponement. The Rust community appears to postpone RFCs before they are merged, adding a tag. This is in contract to TVM postponement, which is meant to capture features that may have been accepted but aren't actively being developed. If this is a point of confusion, I would suggest we change the name to something else. I'm not convinced that the Rust model of postponement is necessary for a project of this size and scope. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/tvm-rfcs/pull/2#issuecomment-825909082
