> 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 . > 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.
👍 I think we're agreed on the boundary here, Relax development activities, principles and practices aren't relevant to the `apache/tvm` project, whereas the integration of Relax into TVM is. > 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 to come and provide everyone with visibility (which are > aside from technical contents which are handled by the technical RFCs opened > through out the upstreaming process when needed). One note here, as a growing community with many closely related projects, we have to be careful of tracking a project closely until it becomes relevant to TVM itself and follows the TVM processes. To be clear, on the specific issue of Relax, there's a clear intent to contribute this back into the mainline in a near future, which indicates it is mature enough to have a roadmap and we should definitely be moving in this direction. > 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. > From sequencing pov, we can wait until the first relax upstreaming RFC(T0) to > merge this, but i would warmly thank @denise-k for opening the RFC and > getting the community involved early. Given we've established the boundaries of the roadmap, do we need to wait for the first technical RFC? My concerns were only as outlined above, I don't want to hold up creating a roadmap and publicising the integration plan here as I believe that'd greatly aid the TVM community who haven't been a part of activities outside the Apache project. @denise-k I would propose we scope this roadmap to the relevant RFCs, Tracking Issues and PRs relevant to the integration of Relax into TVM, which we can immediately create and fill with placeholders to track that activity? -- Reply to this email directly or view it on GitHub: https://github.com/apache/tvm-rfcs/pull/69#issuecomment-1129970926 You are receiving this because you are subscribed to this thread. Message ID: <apache/tvm-rfcs/pull/69/c1129970...@github.com>
