Skip to content
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

Closed
wants to merge 1 commit into from
Closed

Intial Governance #4

wants to merge 1 commit into from

Conversation

david-martin
Copy link

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/

GOVERNANCE.md Outdated Show resolved Hide resolved
Signed-off-by: David Martin <davmarti@redhat.com>
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')
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- 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)

Comment on lines +26 to +39
### 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.
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
### 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.

@david-martin
Copy link
Author

I'm going to close this PR in favour of #5.
I think having an elected committee ultimately decide on future governance is the right thing to do here, so let's see if we can agree on a steering committee approach first.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants