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

Add SIG etcd leadership roles #666

Merged
merged 1 commit into from
Nov 8, 2023
Merged

Add SIG etcd leadership roles #666

merged 1 commit into from
Nov 8, 2023

Conversation

jmhbnz
Copy link
Contributor

@jmhbnz jmhbnz commented Nov 4, 2023

Recently SIG etcd was established, with two tech leads and chair roles.

As discussed and agreed through maintainer majority in etcd-io/etcd#16794 (comment) this pull request:

  1. Renames the etcd project maintainers source of truth to our newly added OWNERS file.
  2. Adds a separate section under etcd for SIG etcd leadership roles .

cc @serathius, @ahrtr, @wenjiaswe, @jberkus

@amye
Copy link
Contributor

amye commented Nov 4, 2023

So, you can rename Maintainers to Owners, that's fine - but duplicate entries are going to throw things off. Can we consolidate?

@jmhbnz
Copy link
Contributor Author

jmhbnz commented Nov 4, 2023

So, you can rename Maintainers to Owners, that's fine - but duplicate entries are going to throw things off. Can we consolidate?

Thanks @amye - I've consolidated the entries. For some context, I'm currently the only SIG etcd lead that isn't currently also a code approver specified in OWNERS (currently reviewer) so I've retained the second category with just myself under it. Over the lifecycle of the SIG and project moving forward it is possible future co-chairs could also be in the same category of not being code owners, but still needed elevated permissions within the project.

@amye amye merged commit 76650f3 into cncf:main Nov 8, 2023
1 check passed
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