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

Enable team management for peribolos #337

Merged
merged 3 commits into from
Jan 11, 2019

Conversation

cblecker
Copy link
Member

@cblecker cblecker commented Jan 8, 2019

🙊!

This might actually work.
fixes #336

/assign @fejta @spiffxp
/hold

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 8, 2019
@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Jan 8, 2019
@cblecker cblecker force-pushed the teams-yay branch 2 times, most recently from ab0f0ae to 5de35f8 Compare January 9, 2019 00:22
@nikhita
Copy link
Member

nikhita commented Jan 9, 2019

@cblecker 🎉 🎈

Two questions:

  • Can we move the teams to a teams.yaml and merge the configs to avoid bloating org.yaml, like we do for contribex? Or do we intend to move to a teams.yaml for each SIG later?

  • Out of curiosity, how do --dump, --fix-teams and --fix-team-members come to know that sig-contribex teams should be dumped in its teams.yaml file and not append those in org.yaml? 🤔

@cblecker
Copy link
Member Author

cblecker commented Jan 9, 2019

@nikhita Thanks for feedback!

Can we move the teams to a teams.yaml and merge the configs to avoid bloating org.yaml, like we do for contribex?

Yes, we can.. it just requires manually trimming out the groups into a new folder, like contribex and apimachinery. I haven't done that yet, because it's a manual process, and I'm currently trying to keep the dump sync'd with what's in GitHub.

Out of curiosity, how do --dump, --fix-teams and --fix-team-members come to know that sig-contribex teams should be dumped in its teams.yaml file and not append those in org.yaml?

Manually :) I dumped out the list of teams, and then extracted out contribex and apimachinery as examples. I want to get peribolos as the source of truth first, and then we can do it for all the sigs to delegate approve rights.

@fejta
Copy link
Contributor

fejta commented Jan 9, 2019

Manually :) I dumped out the list of teams, and then extracted out contribex and apimachinery as examples.

However we organize the files https://github.com/kubernetes/org/tree/master/cmd/merge will then stitch them back together into one config.

@nikhita
Copy link
Member

nikhita commented Jan 9, 2019

Manual sounds like a lot of work though 😛 ....if teams have consistent naming, maybe we could automate it? But I think we should discuss this later on an issue somewhere and not on this PR. Thanks for getting this ready, again! 💯 :shipit:

Copy link
Contributor

@fejta fejta left a comment

Choose a reason for hiding this comment

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

/lgtm
Any chance we want to leave out the third commit that enables --fix-teams and put that in a separate PR?

maintainers:
- fejta
- k8s-ci-robot
privacy: secret
Copy link
Contributor

Choose a reason for hiding this comment

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

LOL

Bots:
description: Hmm, not working like I hoped...
maintainers:
- fejta
Copy link
Contributor

Choose a reason for hiding this comment

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

why am I a bot?! 😁

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jan 9, 2019
@cblecker
Copy link
Member Author

cblecker commented Jan 9, 2019

@fejta The reason I'm just turning it all on now is we would need a last "sync" from GitHub before we turn it on anyways. I figure I'll do that Friday morning right before merge.

@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jan 11, 2019
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cblecker

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

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 11, 2019
@fejta
Copy link
Contributor

fejta commented Jan 11, 2019

/lgtm
/hold
exciting! I guess Friday afternoon is the natural time to make this switch?

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jan 11, 2019
@cblecker
Copy link
Member Author

/hold cancel
Let's do this! 🚀

@k8s-ci-robot k8s-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 11, 2019
@k8s-ci-robot k8s-ci-robot merged commit 8f5d5d9 into kubernetes:master Jan 11, 2019
@cblecker cblecker deleted the teams-yay branch January 11, 2019 21:37
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. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Automate the management of github team membership
5 participants