csullivan commented on code in PR #102: URL: https://github.com/apache/tvm-rfcs/pull/102#discussion_r1283439824
########## rfcs/0102-clarify-strategy-decision-process.md: ########## @@ -0,0 +1,38 @@ +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 more verbose processes in a less successful. Review Comment: ```suggestion We have made attempts in the past to bring a more verbose processes, but this has proven to be less successful. ``` ########## rfcs/0102-clarify-strategy-decision-process.md: ########## @@ -0,0 +1,38 @@ +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 more verbose processes in a 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 of binding decisions to make strategic decisions in the TVM community, including: Review Comment: I had to look up Lazy majority and found Apache Hive has a nice table describing various forms of reaching approval. I appreciate TVM's consideration of incorporating both Lazy majority and 2/3 majority. By Lazy majority are we defining it as, >Lazy Majority | A lazy majority vote requires 3 binding +1 votes and more binding +1 votes that -1 votes. Perhaps it would be good to include that definition. -- 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]
