hogepodge commented on a change in pull request #2:
URL: https://github.com/apache/tvm-rfcs/pull/2#discussion_r610910470
##########
File path: README.md
##########
@@ -1,6 +1,64 @@
# TVM RFCs
-This repoisitory is an evolving repo containing the new RFC process for TVM,
more changes to come in next few days.
+## What is an RFC?
+[what-is-an-rfc]: #what-is-an-rfc
+An RFC is a “Request for Change” to the TVM project. It is a design document
Review comment:
I'm flexible on numbering. The standard across many open source projects
(including Rust and Kubernetes, for example), is to just increase by 1 and
resolve conflicts as they arise. One problem that might come out of linking to
the discussion post or pull request number is it ties the repository to
technology that the project might not be using in the future.
The workflow seems to be:
* Initial discussion on Discuss, with a decision to formalize as a pull
request.
* Pull request, which has more of a final review before merging.
* Upon merging, merged RFC becomes source of truth.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
