As an individual Relax contributor from UCSD, I don’t feel our community has 
created an environment that welcomes new contributors and new contributions.

I am happy to see different opinions in the discussion, but it's really 
shocking and disappointing that we are afraid of moving forward even with large 
amount of community support, and for such a technically strong optional module.😞

Based on several community members, Relax can solve the needs that they care 
about. It’s also made clear by @YuchenJin in the RFC that Relax is an optional 
module which does not disrupt the current TVM flow, and it does not have the 
intention to replace Relay. He explained in the section 6 that the three 
components are tightly coupled together, and explained the difficulties in 
simply updating Relay to bring all the benefits of Relax, but still got the 
same questions again and again. I am very surprised that such a module that can 
solve the current pain points of tvm has received so many questions about 
future migration plans—these are S1 and S2 stage questions, which shouldn’t be 
in the scope of this RFC.

It's hard to imagine that everyone who wants to contribute to tvm, especially 
those who do foundational work like relax, needs to answer all of these 
questions and do future predictions about existing flow deprecation and 
timelines, which in my opinion discourages people from contributing.



-- 
Reply to this email directly or view it on GitHub:
https://github.com/apache/tvm-rfcs/pull/89#issuecomment-1267632697
You are receiving this because you are subscribed to this thread.

Message ID: <apache/tvm-rfcs/pull/89/c1267632...@github.com>

Reply via email to