-
Notifications
You must be signed in to change notification settings - Fork 1
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
Intial Governance #4
Conversation
Signed-off-by: David Martin <davmarti@redhat.com>
975a359
to
7a96b6f
Compare
Here are some examples of how decisions have been made in the past: | ||
|
||
- discussing openly on the community slack channel | ||
- a call with a specific group of people (like component specific maintainers or a 'de facto project lead') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- a call with a specific group of people (like component specific maintainers or a 'de facto project lead') | |
- a call with a specific group of people (like component specific maintainers) |
### De facto project leads | ||
|
||
Although the project doesn't have a lead person, there are a few people that have become de facto leads. | ||
They would tend to be the most active on disucssions around roadmap items, releasing and generally on the community call. | ||
They would also be the main people that others would look to for approval on changes. | ||
The are: | ||
|
||
- Alex Snaps [alexsnaps] | ||
- Craig Brookes [maleck13] | ||
- Eguzki Astiz Lezaun [eguzki] | ||
- Guilherme Cassolato [guicassolato] | ||
|
||
There are no set rules for how a person can move to a 'de facto project lead' role. | ||
The existing list of people is subjective, based on who has been involved from the early stages of the project, and continues to be involved in the ways mentioned above. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
### De facto project leads | |
Although the project doesn't have a lead person, there are a few people that have become de facto leads. | |
They would tend to be the most active on disucssions around roadmap items, releasing and generally on the community call. | |
They would also be the main people that others would look to for approval on changes. | |
The are: | |
- Alex Snaps [alexsnaps] | |
- Craig Brookes [maleck13] | |
- Eguzki Astiz Lezaun [eguzki] | |
- Guilherme Cassolato [guicassolato] | |
There are no set rules for how a person can move to a 'de facto project lead' role. | |
The existing list of people is subjective, based on who has been involved from the early stages of the project, and continues to be involved in the ways mentioned above. | |
### Project Lead | |
At this time there is no concept of a project lead or leads. | |
This may change in the future. |
After discussion on https://kubernetes.slack.com/archives/C05J0D0V525/p1721813274877239, I'm thinking we remove this section and have a discussion on what this means and how someone can be assigned this role.
I'm going to close this PR in favour of #5. |
This is an attempt to capture some aspects of governance as they stand now.
I've based the sections on what's recommended in https://contribute.cncf.io/maintainers/governance/overview/