This is an automated email from the ASF dual-hosted git repository.
syfeng pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/tvm-rfcs.git
The following commit(s) were added to refs/heads/main by this push:
new 4de475c [Process RFC] Clarify Community Strategy Decision Process
(#102)
4de475c is described below
commit 4de475c808a707919dda560d76b7b535e29de6a1
Author: Tianqi Chen <[email protected]>
AuthorDate: Fri Aug 25 10:58:31 2023 -0400
[Process RFC] Clarify Community Strategy Decision Process (#102)
* [Process RFC] Clarify Community Strategy Decision Process
* Update 0102-clarify-strategy-decision-process.md
* Update rfcs/0102-clarify-strategy-decision-process.md
Co-authored-by: Chris Sullivan <[email protected]>
* Include description of lazy 2/3 majority
* Update 0102-clarify-strategy-decision-process.md
* Update 0102-clarify-strategy-decision-process.md
* Finish
---------
Co-authored-by: Chris Sullivan <[email protected]>
---
rfcs/0102-clarify-strategy-decision-process.md | 39 ++++++++++++++++++++++++++
1 file changed, 39 insertions(+)
diff --git a/rfcs/0102-clarify-strategy-decision-process.md
b/rfcs/0102-clarify-strategy-decision-process.md
new file mode 100644
index 0000000..87f5df5
--- /dev/null
+++ b/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 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 the following strategic decisions in the TVM
community:
+
+- Adoption of a guidance-level community strategy to enable new directions or
overall project evolution.
+- Establishment of a new module in the project.
+- Adoption of a new codebase: When the codebase for an existing, released
product is to be replaced with an alternative codebase.
+ If such a vote fails to gain approval, the existing code base will continue.
This also covers the creation of new sub-projects within the project.
+
+All these decisions are made after community conversations that get captured
as part of the summary.
