[GitHub] [tvm-rfcs] denise-k commented on pull request #69: [RFC] Relay Next Roadmap

[GitBox <gi...@apache.org>]

denise-k commented on PR #69:
URL: https://github.com/apache/tvm-rfcs/pull/69#issuecomment-1121455411

   Thanks @Mousius for the great and insightful feedback.
   
   Let's split your feedback into two concerns which we can address separately:
   * **C1: Using TVM roadmaps to track work outside of TVM mainline**
      The [guidelines](https://github.com/apache/tvm-rfcs/blob/main/rfcs/0050-roadmaps.md) for Roadmap RFCs outline that valid roadmap items are TVM pre-RFCs, TVM RFCs, TVM Github Task-Tracking Issues, and TVM Bugfixes. 
   
      If I'm interpreting your message correctly, your concern is that Relax's current approach towards development does not *yet* utilize any of these task tracking mechanisms.
   * **C2: Relax upstreaming efforts and timeline**
      Currently, the Relax Roadmap RFC is vague about Relax's development practices, saying:
      > This proposed roadmap is intended to track the Relax project as it evolves
   
      The vague wording here makes it sound like the desire is to track Relax development in `tlcpack/relax` in a TVM roadmap, which is specifically why you mention *C1*.
   
   Here are some actions which I believe address these concerns:
   - [ ] **A1: In the Relax Roadmap RFC, clarify the scope of the roadmap (actionable in this PR)** 
      This roadmap will track (in approximate chronological order):
      - RFCs that the Relax community has made for Relax
      - The eventual (but yet-to-be-defined) upstreaming process of Relax functionalities to TVM mainline
      - The ongoing efforts to improve Relax capabilities in TVM mainline, after initial upstreaming.
   - [ ] **A2: Propose a set of RFCs for upstreaming Relax functionalities to TVM mainline (actionable by the Relax community)** 
      Yuchen and team are working on a set of RFCs to move Relax components to mainline TVM. These RFCs should eventually be tracked in the Relax Roadmap.
   - [ ] **A3: Propose to move Relax development to TVM mainline (actionable by the Relax community)** 
      As the Relax project matures, and the capabilities of Relax are moved into TVM mainline, it will eventually make sense to move all of Relax's development to TVM mainline. Still, we expect that there will be a long road ahead of improvements to Relax even post-upstreaming. This work should eventually also be tracked in the Relax Roadmap.
   
   Let me know if this sounds right.


-- 
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: commits-unsubscribe@tvm.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org