-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Project governance: introduce "emeritus" member status #4150
Comments
Background: At the previous vote, there was an issue of slow progress in voting. |
Thanks for creating this issue! If we make the threshold a percentage, it will be difficult to progress voting as the number of maintainers increases. ref:
|
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 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
The text was updated successfully, but these errors were encountered: