Hi all, After some discussion, we'd like to propose that RFCs are numbered according to the GitHub PR number. This follows the idea of documenting those RFCs which are rejected. While it adds an extra step to the initial RFC posting, it simplifies all future references by not allocating two different IDs (PR number and RFC number). It also makes it very easy to find the discussion associated with a given PR when viewing it outside of a PR (e.g. through browsing the `tvm-rfcs` repo) and makes for one less link to update.
This also has [precedent](https://github.com/rust-lang/rfcs#what-the-process-is) in the rust community. Sending this PR as a proposal and would like for everyone to discuss/approve/reject this idea here. @hogepodge @apache/tvm-committers @tqchen -Andrew You can view, comment on, or merge this pull request online at: https://github.com/apache/tvm-rfcs/pull/17 -- Commit Summary -- * Update RFC numbering guidance to use PR number -- File Changes -- M README.md (11) -- Patch Links -- https://github.com/apache/tvm-rfcs/pull/17.patch https://github.com/apache/tvm-rfcs/pull/17.diff -- 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/17
