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

Update steering committee membership requirements #11942

Merged
merged 2 commits into from
Feb 28, 2024
Merged

Conversation

kflynn
Copy link
Member

@kflynn kflynn commented Jan 16, 2024

We'd like to change the requirement for Steering Committee members such that it's OK for committee members to have been responsible for a nontrivial Linkerd deployment in production within the last two years, rather than requiring responsibility currently. This change is meant to better reflect the reality of job moves in the tech industry: a member who, for example, changes jobs to an organization in the process of adopting Linkerd shouldn't be instantly disqualified because they don't yet have a production deployment to be responsible for!

@kflynn kflynn requested a review from a team as a code owner January 16, 2024 18:13
@kflynn
Copy link
Member Author

kflynn commented Jan 16, 2024

This change requires a majority of the maintainers to approve it. Please vote yes by putting a 👍 response on this comment, or no with a 👎. Thanks!!

STEERING.md Outdated
@@ -24,7 +24,8 @@ The Steering Committee’s responsibilities are to:
The Steering Committee comprises at most 7 people. To be eligible for
membership in the Steering Committee, you must:

1. Be responsible for a production Linkerd deployment of non-trivial size
1. Have been responsible for a production Linkerd deployment of non-trivial
Copy link
Member

Choose a reason for hiding this comment

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

If we're going to go in this direction, for clarity we might want to make this "Be currently responsible for a production Linkerd deployment of non-trivial size, or have been responsible for one within the past two years."

Copy link
Member Author

Choose a reason for hiding this comment

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

👍 Updated!

Copy link
Member

@wmorgan wmorgan left a comment

Choose a reason for hiding this comment

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

LGTM. Looks like we technically have a majority of maintainers already, but it would be nice to get a vote from @olix0r and @zaharidichev

@wmorgan wmorgan merged commit 71cb84e into main Feb 28, 2024
2 checks passed
@wmorgan wmorgan deleted the flynn/steering branch February 28, 2024 20:34
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.

4 participants