Thanks folks for discussions. Just want to chime in here. I think we all agree that the development and upstreaming flow should closely follow the normal process, which is A2 as being listed by @denise-k .
For emerging components being contributed to the community, it is certainly helpful for the community to have a roadmap that tracks things to be upstreamed to the codebase (that relates to contents to be upstreamed, which co-relates, but not depend on relax repo dev itself). To put it in another way, that the roadmap is independent from what/how things are being developed in relax, but more about what TVM community to expect in general as the change get checked in. The development in tvm itself still follows the normal RFC process in general (as being listed in A2). Having a separate roadmap is also important as initial integration usually starts with experimental and have a minimum impact to the current flow. From the high-level, as a community we need a way to track and maintain a global picture of things that to come while being agile enough to help us continue reinvent ourselves. This being said, I observe that one topic is about sequencing. e.g. should roadmap RFC be opened or merged at: - T0: After the first upstreaming RFC is being proposed/merged. - T1: After the initial upstreaming code itself is being merged. - T2: After k-steps of PRs themselves. As a community that welcomes constructive improvements, it is totally fair for a roadmap RFC to be opened early before T0, and taken into action after T0. This would be a net positive for the community as there will be more informations being tracked, as long as we hold the clear standard that the items are about wants and things to come to `apache/tvm` repo (just like other roadmap items). This would also help us welcome the folks working on `relax`(many of whom are also part of our community) to bringing their effort to the tvm community. >From sequencing pov, we can wait until the first relax upstreaming RFC, i >would warmly thank @denise-k for opening the RFC early and getting the >community involved! Thank you! -- Reply to this email directly or view it on GitHub: https://github.com/apache/tvm-rfcs/pull/69#issuecomment-1122343054 You are receiving this because you are subscribed to this thread. Message ID: <apache/tvm-rfcs/pull/69/c1122343...@github.com>
