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 owners files and notes on review/approver role to CONTRIBUTING.md #1601

Merged
merged 3 commits into from
Jul 27, 2022

Conversation

pweil-
Copy link
Member

@pweil- pweil- commented Jul 22, 2022

Fixes #1557

Figured this might be easier with something to actually apply red pen to. Note, this is not a judgement of any contributor's capabilities. I simply looked at history and picked what I thought looked like names that were frequently contributing to areas. Comment and change suggestions encouraged.

@openshift-ci openshift-ci bot requested review from ncdc and sttts July 22, 2022 12:02
@pweil-
Copy link
Member Author

pweil- commented Jul 22, 2022

please 👍 here to indicate you're good with what is shown in this PR with regards to the code areas and responsibilities. Thank you!

@sttts
Copy link
Member

sttts commented Jul 22, 2022

I mostly agree with the proposal. One change I think that is important:

  • we need an independent approver group for everything that can influence APIs
  • this includes pkg/admission, which is basically a golang-codified extension for API definitions
  • this includes *.yaml-patch in config/crds.

@sttts
Copy link
Member

sttts commented Jul 22, 2022

See how an API approver group can be implemented:

@pweil-
Copy link
Member Author

pweil- commented Jul 22, 2022

ack, thanks for the feedback.

Follow up question: do you think the additional people listed in admission packages should be added as reviewers or removed?

Since I didn't state it earlier I think this commit should get both +1 from @sttts and @ncdc as repo owners as well as a +1 by anyone listed in the file that they're comfortable with the role.

@sttts
Copy link
Member

sttts commented Jul 22, 2022

Follow up question: do you think the additional people listed in admission packages should be added as reviewers or removed?

Definitely as reviewers. We should encourage reviewers everywhere, especially those who have written the majority of code in a package should be reviewer there.

@pweil- pweil- force-pushed the owners branch 2 times, most recently from dbc7dde to e00dbce Compare July 22, 2022 15:58
@openshift-ci openshift-ci bot added the do-not-merge/invalid-owners-file Indicates that a PR should not merge because it has an invalid OWNERS file in it. label Jul 22, 2022
Copy link
Contributor

@openshift-ci openshift-ci bot left a comment

Choose a reason for hiding this comment

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

@pweil-: 1 invalid OWNERS file

In response to this:

Fixes #1557

Figured this might be easier with something to actually apply red pen to. Note, this is not a judgement of any contributor's capabilities. I simply looked at history and picked what I thought looked like names that were frequently contributing to areas. Comment and change suggestions encouraged.

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.

@openshift-ci openshift-ci bot removed the do-not-merge/invalid-owners-file Indicates that a PR should not merge because it has an invalid OWNERS file in it. label Jul 22, 2022
Co-authored-by: Dr. Stefan Schimanski <stefan.schimanski@gmail.com>
@sttts
Copy link
Member

sttts commented Jul 22, 2022

lgtm
/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 22, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sttts

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 22, 2022
@ncdc
Copy link
Member

ncdc commented Jul 26, 2022

LGTM. What's left before merging?

@pweil-
Copy link
Member Author

pweil- commented Jul 26, 2022

Folks were pinged on Slack today to give final thumbs up on where there names are. We can merge EOD tomorrow to give that time. Otherwise, no big deal, we can change it later.

@sttts
Copy link
Member

sttts commented Jul 27, 2022

/lgtm
/hold

@pweil- feel free to remove the hold at your EoD.

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 27, 2022
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jul 27, 2022
@pweil- pweil- removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 27, 2022
@pweil-
Copy link
Member Author

pweil- commented Jul 27, 2022

unholding. For any further feedback please submit it in the form of a PR. 👍

@openshift-merge-robot openshift-merge-robot merged commit 0f4ef86 into kcp-dev:main Jul 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

kcp OWNERS files
5 participants