OceanBase Community ByLaws #891
Replies: 5 comments 2 replies
-
Membership can also be managed without mailing lists, like k8s community: Here new member is not invited by the community, the contributor should raise an apply himself for it. |
Beta Was this translation helpful? Give feedback.
-
This proposal has been proposed for 24 hours. Let's vote for this proposal. If this proposal has been past, it will be display in the official website. |
Beta Was this translation helpful? Give feedback.
-
It seems this discussion can't be changed from category of classroom to polls. +1(binding) |
Beta Was this translation helpful? Give feedback.
-
+1(binding) |
Beta Was this translation helpful? Give feedback.
-
Thanks to all. This proposal has been passed by all TOC members. The OceanBase Community will be displayed in the official website . |
Beta Was this translation helpful? Give feedback.
-
Roles and Responsibilities
OceanBase Community define a set of roles with associated rights and responsibilities. These roles govern what tasks an individual may perform within the project. Please refer to https://open.oceanbase.com/community/organization for the roles.
Voting
Decisions regarding the projects under https://github.com/OceanBase are made by votes on the primary project development (https://github.com/oceanbase/oceanbase/discussions). Where necessary, PMC voting may take place on the private SIG mailing list. Votes are clearly indicated by subject line starting with [VOTE]. Votes may contain multiple items for approval and these should be clearly separated. Voting is carried out by replying to the vote mail or discussion. Voting may take four flavors:
All participants in the OceanBase project are encouraged to show their agreement with or against a particular action by voting. For technical decisions, only the votes of PMCs or TOCs are binding. Non-binding votes are still useful for those with binding votes to understand the perception of an action in the wider OceanBase community. For PMC decisions, only the votes of PMC or TOC members are binding.
Voting can also be applied to changes already made to the OceanBase codebase. These typically take the form of a veto (-1) in reply to the commit message sent when the commit is made. Note that this should be a rare occurrence. All efforts should be made to discuss issues when they are still patches before the code is committed.
Only PMC or TOC members have binding votes.
Approvals
These are the types of approvals that can be sought. Different actions require different types of approvals
Vetoes
A valid, binding veto cannot be overruled. If a veto is cast, it must be accompanied by a valid reason explaining the reasons for the veto. The validity of a veto, if challenged, can be confirmed by anyone who has a binding vote. This does not necessarily signify agreement with the veto - merely that the veto is valid.
If you disagree with a valid veto, you must lobby the person casting the veto to withdraw their veto. If a veto is not withdrawn, any action that has been vetoed must be reversed in a timely manner.
Actions
This section describes the various actions which are undertaken within the project, the corresponding approval required for that action and those who have binding votes over the action.
Beta Was this translation helpful? Give feedback.
All reactions