Open kenhys opened 1 year ago
Background: At the previous vote, there was an issue of slow progress in voting.
Thanks for creating this issue! I agree with these changes. We might also consider the following.
If we make the threshold a percentage, it will be difficult to progress voting as the number of maintainers increases.
So, it may also be worth considering the condition such that a certain number of approvals(3
?) and no objections are required.
ref: code modifications
and veto
of Apache Voting Process
the proposal requires three positive votes and no negative votes in order to pass
About threshold issue is splitted into another issue.
Thanks!
If there is no disagreement in this direction, then we would consider the conditions that make a member emeritus
, right?
Example:
This issue has been automatically marked as stale because it has been open 30 days with no activity. Remove stale label or comment or this issue will be closed in 7 days
This issue has been automatically marked as stale because it has been open 30 days with no activity. Remove stale label or comment or this issue will be closed in 7 days
Describe the bug
Currently, there is no term for Fluentd maintainers.
More contributor involved, it tend to hard to call for voting in a timely manner which is described in Voting because it requires 2/3 majority.
This situation is caused because inactive members and active members are treated as "same" individuals.
To Reproduce
N/A
Expected behavior
Introduce "emeritus" maintainer status
"emeritus" means:
https://github.com/fluent/fluentd/blob/master/GOVERNANCE.md#voting should be revised such as:
NOTE: above sentence is just an draft.
Your Environment
Your Configuration
Your Error Log
Additional context
Apache project introduces "emeritus" ref. https://www.apache.org/dev/pmc.html#emeritus