denise-k commented on a change in pull request #50: URL: https://github.com/apache/tvm-rfcs/pull/50#discussion_r783520272
########## File path: rfcs/0050-roadmaps.md ########## @@ -0,0 +1,320 @@ +- Feature Name: roadmaps +- Start Date: 2022-01-07 +- RFC PR: [apache/tvm-rfcs#0050](https://github.com/apache/tvm-rfcs/pull/0050) +- GitHub Issue: [apache/tvm#0000](https://github.com/apache/tvm/issues/0000) +- pre-RFC: https://discuss.tvm.apache.org/t/pre-rfc-tvm-roadmap/11171 +- pre-RFC: https://discuss.tvm.apache.org/t/pre-rfc-roadmap-rfcs/11711 +- Co-Authors: Denise Kutnick (@denise-k), Andrew Reusch (@areusch) + +NOTE(areusch): This RFC is a combination of the two above pre-RFCs, and limited copy-editing has +been done to preserve the flow of the document. + +## Summary + +This RFC proposes to add product roadmaps to TVM. + +Roadmaps should be seen as a way of unifying the planning process of TVM, all the way from ideas to +PR merges. The roadmaps discussed in this pre-RFC are intentionally designed to integrate with TVM’s +existing planning tools (e.g. Github tracking issues, RFCs), while adding an additional space for +sharing and collaboration earlier in the R&D process. + +This proposal includes two categories of roadmaps: + +- **TVM Global Roadmap**: This roadmap aims to provide a holistic view of all components within TVM, + focusing on features which broadly affect the entire project or add significant functionality. +- **TVM Component Roadmaps**: These roadmaps aim to provide a more detailed view of a subsection of + TVM: including vertical efforts involving TVM's intermediate representations (such as Relay or + TIR) and the horizontal efforts which span across TVM's full stack (such as Automation or + Documentation). Details about each of the components in TVM will be discussed later in this + pre-RFC. Review comment: done -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
