tqchen commented on code in PR #102: URL: https://github.com/apache/tvm-rfcs/pull/102#discussion_r1285827223
########## rfcs/0102-clarify-strategy-decision-process.md: ########## @@ -0,0 +1,39 @@ +Authors: @tqchen + +- Feature Name: [Process RFC] Clarify Community Strategy Decision Process +- Start Date: 2023-08-03 +- RFC PR: [apache/tvm-rfcs#0102](https://github.com/apache/tvm-rfcs/pull/0102) +- GitHub Issue: [apache/tvm#0000](https://github.com/apache/tvm/issues/0000) + +## Summary + +Machine Learning Compilation (MLC) is an emerging field in fast development. +With the tremendous help from the whole community, it’s exciting to see that TVM delivers significant needs from and to +developers and thus has become widely popular in both academia and industry. + +As the community pushes for different goals that help each other, naturally, there +are strategy decision points about overall directions and new modules adoptions. +These decisions are not fine-grained code-level changes but are important for a +community to be viable in the long term. +The process of bringing those changes is less clarified to the community, and hurdles can be high. +We have made attempts in the past to bring a more verbose processes, but this has proven to be less successful. +One observation is that it is hard for broader volunteer developers and community members to follow complicated processes. +Additionally, different members can have different interpretations of how to do things, +leading to stagnation and lack of participation from volunteer members. + +We are in a different world now in the case of ML/AI ecosystem, and it is critical for +the community to be able to make collective decisions together and empower the community. +Following the practices of existing ASF projects (e.g. hadoop), we propose to use a simple process for strategic decisions. + +## Proposal: Strategy Decision Process + +We propose the following clarification of the strategy decision process: +It takes lazy 2/3 majority (at least 3 votes and twice as many +1 votes as -1 votes) +of binding decisions to make strategic decisions in the TVM community, including: + +- Adoption of a guidance-level community strategy to enable new directions or overall project evolution. +- Establishment of a new module in the project. Review Comment: I think it is up to @Hzfengsy to decide what to do with the other RFC. (addressing your question on what to do with existing RFC). I would remark that this reply is not taking the either the options that you listed, which contains specific operational ways of how. Instead it addresses the two action items (that covers the questions you ask): - The other RFC: leave it up to @Hzfengsy , however i don't think any action needs to be taken until we conclude either one of the two. - This RFC, I do not intend to expand on the particular item, as being stated, the goal is to is to come up with simple, less verbose process that everyone understand, as verbatim it is quite clear I think to many community members. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
