-
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
Update steering committee membership requirements #11942
Conversation
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 |
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.
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."
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.
👍 Updated!
Signed-off-by: Flynn <[email protected]>
Signed-off-by: Flynn <[email protected]>
555caba
to
7e73d05
Compare
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.
LGTM. Looks like we technically have a majority of maintainers already, but it would be nice to get a vote from @olix0r and @zaharidichev
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!