Skip to content

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

New issue
New issue
Open
Open
Support for the "same" team across different orgs#2559
Labels
area/github-managementIssues or PRs related to GitHub Management subprojectarea/github-permissionsPermissions requests and problemskind/featureCategorizes issue or PR as related to a new feature.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.priority/awaiting-more-evidenceLowest priority. Possibly useful, but not yet enough support to actually get it done.sig/contributor-experienceCategorizes an issue or PR as relevant to SIG Contributor Experience.

Description

@nnordrum
nnordrum
opened on Jun 20, 2019

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.

Activity

  1. stevekuznetsov commented on Jun 20, 2019

    @stevekuznetsov
    stevekuznetsov
    on Jun 20, 2019

    Is this with peribolos?

  2. nnordrum commented on Jun 21, 2019

    @nnordrum
    nnordrum
    on Jun 21, 2019
    Author

    yeah

  3. stevekuznetsov commented on Jun 21, 2019

    @stevekuznetsov
    stevekuznetsov
    on Jun 21, 2019

    /cc @fejta @cblecker @nikhita

  4. spiffxp commented on Jul 10, 2019

    @spiffxp
    spiffxp
    on Jul 10, 2019
    Contributor

    /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)

  5. nnordrum commented on Jul 10, 2019

    @nnordrum
    nnordrum
    on Jul 10, 2019
    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... 🤔

  6. spiffxp commented on Aug 6, 2019

    @spiffxp
    spiffxp
    on Aug 6, 2019
    Contributor

    /area github-management

  7. fejta-bot commented on Nov 4, 2019

    @fejta-bot
    fejta-bot
    on Nov 4, 2019

    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

  8. cblecker commented on Nov 4, 2019

    @cblecker
    cblecker
    on Nov 4, 2019
    Member

    /remove-lifecycle stale

  9. fejta-bot commented on Feb 2, 2020

    @fejta-bot
    fejta-bot
    on Feb 2, 2020

    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

  10. fejta-bot commented on Mar 3, 2020

    @fejta-bot
    fejta-bot
    on Mar 3, 2020

    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

  11. cblecker commented on Mar 7, 2020

    @cblecker
    cblecker
    on Mar 7, 2020
    Member

    /remove-lifecycle rotten

  12. fejta-bot commented on Jun 5, 2020

    @fejta-bot
    fejta-bot
    on Jun 5, 2020

    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

  13. fejta-bot commented on Jul 5, 2020

    @fejta-bot
    fejta-bot
    on Jul 5, 2020

    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

  14. fejta-bot commented on Aug 4, 2020

    @fejta-bot
    fejta-bot
    on Aug 4, 2020

    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

  15. k8s-ci-robot commented on Aug 4, 2020

    @k8s-ci-robot
    k8s-ci-robot
    on Aug 4, 2020
    Contributor

    @fejta-bot: Closing this issue.

    Details

    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.

  16. 4 remaining items

  17. spiffxp
    transferred this issue fromkubernetes/test-infraon Mar 10, 2021
  18. spiffxp
    added
    area/github-managementIssues or PRs related to GitHub Management subproject
    area/github-permissionsPermissions requests and problems
    kind/featureCategorizes issue or PR as related to a new feature.
    priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete.
    sig/contributor-experienceCategorizes an issue or PR as relevant to SIG Contributor Experience.
    on Mar 10, 2021

  19. fejta-bot commented on Jun 8, 2021

    @fejta-bot
    fejta-bot
    on Jun 8, 2021

    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

  20. k8s-ci-robot
    added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Jun 8, 2021

  21. nikhita commented on Jul 5, 2021

    @nikhita
    nikhita
    on Jul 5, 2021
    Member

    /lifecycle frozen

  22. k8s-ci-robot
    added
    lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.
    and removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Jul 5, 2021

  23. spiffxp commented on Aug 17, 2021

    @spiffxp
    spiffxp
    on Aug 17, 2021
    Contributor

    /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

  24. k8s-ci-robot
    added
    priority/awaiting-more-evidenceLowest priority. Possibly useful, but not yet enough support to actually get it done.
    on Aug 17, 2021

  25. spiffxp commented on Aug 17, 2021

    @spiffxp
    spiffxp
    on Aug 17, 2021
    Contributor

    /remove-priority important-longterm

  26. k8s-ci-robot
    removed
    priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete.
    on Aug 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/github-managementIssues or PRs related to GitHub Management subprojectarea/github-permissionsPermissions requests and problemskind/featureCategorizes issue or PR as related to a new feature.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.priority/awaiting-more-evidenceLowest priority. Possibly useful, but not yet enough support to actually get it done.sig/contributor-experienceCategorizes an issue or PR as relevant to SIG Contributor Experience.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions