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

Support for the "same" team across different orgs #2559

Open
nnordrum opened this issue Jun 20, 2019 · 21 comments
Open

Support for the "same" team across different orgs #2559

nnordrum opened this issue Jun 20, 2019 · 21 comments
Labels
area/github-management Issues or PRs related to GitHub Management subproject area/github-permissions Permissions requests and problems kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience.

Comments

@nnordrum
Copy link

What would you like to be added:
In GitHub (at least GitHub Enterprise), Teams cannot be cross-org. I would like to support cross-org "Teams".

Why is this needed:
To "get around" the problem, we just replicate the same teams across different orgs. It would be nice to reference a Team, with like teamRef or something, that is specified at the Orgs level so they can be reused.

@stevekuznetsov
Copy link

Is this with peribolos?

@nnordrum
Copy link
Author

yeah

@stevekuznetsov
Copy link

/cc @fejta @cblecker @nikhita

@spiffxp
Copy link
Member

spiffxp commented Jul 10, 2019

/sig contributor-experience
A pattern we have used in the past is to make the configs used directly by the tool verbose and low level, and then use something else to generate those configs. Baking directly into the tool may make it too clever.

Somewhat implied by this would be the idea that org membership should be cross-org as well. Unclear whether it would be better to have a "global" overlay, or treating one org as a source of truth to be mirrored (ref: #966)

@nnordrum
Copy link
Author

the Xzibit strategy? 😄 (I put a tool around your tool to make a new tool)

I agree with the "make the tool too clever" thing--the though part is where to draw the line... We already assume GitHub, so it seems like we should have the same limitations/constraints as GitHub, acknowledging that they will change (we have already been "bitten" by their change to protected branches that match a given regex stepping on our branches protected via regex pattern).

I do like your idea of generating the config though... 🤔

@spiffxp
Copy link
Member

spiffxp commented Aug 6, 2019

/area github-management

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@cblecker
Copy link
Member

cblecker commented Nov 4, 2019

/remove-lifecycle stale

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@cblecker
Copy link
Member

cblecker commented Mar 7, 2020

/remove-lifecycle rotten

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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.

@spiffxp
Copy link
Member

spiffxp commented Mar 10, 2021

/reopen
/remove-lifecycle rotten
ref: #966 (comment)

I'm going to move this to kubernetes/org, if there are technical implementation details that need to find their way into this repo, we can discuss on followup issues or PRs

@k8s-ci-robot
Copy link
Contributor

@spiffxp: Reopened this issue.

In response to this:

/reopen
/remove-lifecycle rotten
ref: #966 (comment)

I'm going to move this to kubernetes/org, if there are technical implementation details that need to find their way into this repo, we can discuss on followup issues or PRs

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.

@k8s-ci-robot k8s-ci-robot reopened this Mar 10, 2021
@spiffxp spiffxp transferred this issue from kubernetes/test-infra Mar 10, 2021
@spiffxp spiffxp added area/github-management Issues or PRs related to GitHub Management subproject area/github-permissions Permissions requests and problems kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience. labels Mar 10, 2021
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 8, 2021
@nikhita
Copy link
Member

nikhita commented Jul 5, 2021

/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jul 5, 2021
@spiffxp
Copy link
Member

spiffxp commented Aug 17, 2021

/priority awaiting-more-evidence
I'm bumping this down to lowest priority because it's not clear to me this a problem actively plaguing the kubernetes community today. I would love to hear about use cases this is preventing

@k8s-ci-robot k8s-ci-robot added the priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. label Aug 17, 2021
@spiffxp
Copy link
Member

spiffxp commented Aug 17, 2021

/remove-priority important-longterm

@k8s-ci-robot k8s-ci-robot removed the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Aug 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/github-management Issues or PRs related to GitHub Management subproject area/github-permissions Permissions requests and problems kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience.
Projects
None yet
Development

No branches or pull requests

7 participants