Thanks, everyone, for putting effort into making unity development happen.
Today, we come to the one-year mark of the unity connection proposal. It is amazing to see how the landscape of AI/ML has changed and how some of the emerging needs fit into the strategy we bought one year ago. Because of the time delays. The strategy as it is no longer timely sense as it was one year ago. So we decided to withdraw the proposal Standing at last year's point, it is obvious that if we took the default option of not pursuing or delaying the strategy, we would miss the opportunity to empower the community in the age of genAI. Luckily, we did not let that slip away and pushed the development of [unity branch](https://discuss.tvm.apache.org/t/establish-tvm-unity-branch/14244). Many of you may have seen the news lately on how they bear fruits in enabling real applications like bringing LLMs and other foundational models to various devices. The good news is that we have clarified [strategy decision process](https://github.com/apache/tvm-rfcs/blob/main/rfcs/0102-clarify-strategy-decision-process.md) to empower strategic proposals. There are also new emerging opportunities in the age of genAI and foundational models, which [majority community support](https://discuss.tvm.apache.org/t/discuss-tvm-community-strategy-for-foundational-models/15401). Please follow the unity branch, continue participating in community discussions, and let us bring TVM to enable everyone. Thank you to many community members who supported the proposal and believed in what it can bring. Let us do our best pushing unity development. We will also collect inputs and come up with new versions of strategies that reflects the current inputs. -- Reply to this email directly or view it on GitHub: https://github.com/apache/tvm-rfcs/pull/91#issuecomment-1693532638 You are receiving this because you are subscribed to this thread. Message ID: <apache/tvm-rfcs/pull/91/c1693532...@github.com>
