-
Notifications
You must be signed in to change notification settings - Fork 114
Tweak owners #162
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
Tweak owners #162
Conversation
OWNERS
Outdated
- kbarnard10 | ||
- steveperry-53 | ||
# - kbhawkey | ||
# - onlydole |
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.
@tengqm , Do you want to remove the pound signs?
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.
'kbhawkey', 'onlydole' and 'sftim' are not members of 'kubernetes-sigs', so I was getting "do-not-merge/invalid-owners-file" label for this PR.
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.
OK. Do you know how we become "members"?
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.
I've just dug into the issue. It looks like https://github.com/kubernetes/org/blob/master/config/kubernetes-sigs/org.yaml#L632-L644
is the place to edit it. Will sync with @zacharysarah on the next step.
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.
@tengqm Thanks for raising visibility--you are correct, the file in k/org sets admin/write permissions for this repo.
@kbhawkey @onlydole @sftim If I understand correctly, you need to:
-
Open an issue in k/org to apply for membership in the kubernetes-sigs org. Feel free to assign me and @tengqm for a +1.
-
Once you're approved as members of kubernetes-sigs, you should be add-able to
OWNERS
andorg.yaml
.
Do you need write permissions to generate reference docs?
@tengqm Thanks for tracking down the issue. 🙇
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.
No, not to generate the docs.
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.
GitHub issue filed at: kubernetes/org#2006
This PR tweaks the OWNERS files by - removing names that are no longer active in this or the website community. - adding SIG leads to the approvers list
@nikhita 👋 Can you shed light on the membership situation? I thought https://github.com/kubernetes/org/pull/2002/files#diff-fec2bf18d37c4aa0eba66d7ebe28f3c6R411 added @sftim as a member of kubernetes-sigs. Did I miss something? |
@zacharysarah -- @sftim would need to accept the invite to join k-sigs first. Once they accept the invite and become a member, running |
Invitation received and accepted. /verify-owners |
/lgtm |
@tengqm: you cannot LGTM your own PR. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: tengqm The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Ha, forgot that the PR was authored by me. :( |
Based on previous PRs and discussion: /lgtm |
Dummy comment to check if it triggers tide 🤔 |
This PR tweaks the OWNERS files by
(edited)