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

SIG Release Github team hygiene #353

Closed
7 tasks done
justaugustus opened this issue Oct 26, 2018 · 16 comments
Closed
7 tasks done

SIG Release Github team hygiene #353

justaugustus opened this issue Oct 26, 2018 · 16 comments
Assignees
Labels
priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/release Categorizes an issue or PR as relevant to SIG Release.
Milestone

Comments

@justaugustus
Copy link
Member

justaugustus commented Oct 26, 2018

Some action items for @tpepper and I once kubernetes/community#2778 merges.

  • (@calebamiles / @jdumars) Grant Tim and Stephen maintainer status for the following teams:
    • kubernetes-milestone-maintainers
    • kubernetes-release-managers
    • release-admins
    • release-maintainers
    • sig-release-admins
    • sig-release-api-reviews
    • sig-release-bugs
    • sig-release-feature-requests
    • sig-release-members
    • sig-release-misc
    • sig-release-pr-reviews
    • sig-release-proposals
    • sig-release-test-failures
  • Prune kubernetes-milestone-maintainers - Prune / update kubernetes-milestone-maintainers GitHub team #241
  • Prune kubernetes-release-managers
  • Remove unused teams
    • release-admins
    • release-maintainers
    • sig-release-api-reviews
    • sig-release-bugs
    • sig-release-feature-requests
    • sig-release-misc
    • sig-release-pr-reviews
    • sig-release-proposals
    • sig-release-test-failures
  • Update all SIG Release Github teams
  • Update contact details in k/community - Update SIG Release contact information community#2941
@justaugustus
Copy link
Member Author

/sig release
/assign @justaugustus @tpepper @calebamiles @jdumars

@k8s-ci-robot k8s-ci-robot added the sig/release Categorizes an issue or PR as relevant to SIG Release. label Oct 26, 2018
@justaugustus
Copy link
Member Author

justaugustus commented Nov 8, 2018

@calebamiles / @jdumars -- Can you grant Tim and I Maintainer access to these groups when you have a chance?

@calebamiles
Copy link
Contributor

done
/close

@k8s-ci-robot
Copy link
Contributor

@calebamiles: Closing this issue.

In response to this:

done
/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.

@justaugustus
Copy link
Member Author

Still some cleanup to do on this one, now that Tim and I have access.
/reopen
/unassign @calebamiles @jdumars

@k8s-ci-robot
Copy link
Contributor

@justaugustus: Reopened this issue.

In response to this:

Still some cleanup to do on this one, now that Tim and I have access.
/reopen
/unassign @calebamiles @jdumars

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.

@justaugustus
Copy link
Member Author

ML update:
So here's what we did...

  • Add Tim Pepper and myself as maintainers for all SIG Release groups
  • Delete:
    • sig-release-api-reviews
    • sig-release-bugs
    • sig-release-feature-requests
    • sig-release-misc
    • sig-release-pr-reviews
    • sig-release-proposals
    • sig-release-test-failures
    • release-maintainer
    • release-admins
  • sig-release-member
  • Cleanup up repo admins for k/sig-release and k/release

There are still a few things to do:

@idvoretskyi
Copy link
Member

/reopen

@kubernetes/sig-release mailing lists still exist. I can delete them after the explicit approval from at least one SIG chair.

REF: kubernetes/community#2324 (comment)

@idvoretskyi idvoretskyi reopened this Feb 12, 2019
@justaugustus
Copy link
Member Author

/priority important-soon
/milestone v1.15

@k8s-ci-robot k8s-ci-robot added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label May 1, 2019
@k8s-ci-robot k8s-ci-robot added this to the v1.15 milestone May 1, 2019
@justaugustus
Copy link
Member Author

@idvoretskyi -- which of the SIG Release lists still exist?

@idvoretskyi
Copy link
Member

@justaugustus it's fine now, we can close.

/close

@k8s-ci-robot
Copy link
Contributor

@idvoretskyi: Closing this issue.

In response to this:

@justaugustus it's fine now, we can close.

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

@justaugustus
Copy link
Member Author

There's still a little investigation I need to do around our Google Group moderation settings, so I'm reopening. :)
/reopen

@k8s-ci-robot k8s-ci-robot reopened this May 1, 2019
@k8s-ci-robot
Copy link
Contributor

@justaugustus: Reopened this issue.

In response to this:

There's still a little investigation I need to do around our Google Group moderation settings, so I'm reopening. :)
/reopen

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.

@justaugustus
Copy link
Member Author

nvm, I just realized this is only for GitHub teams. 😝
/close

@k8s-ci-robot
Copy link
Contributor

@justaugustus: Closing this issue.

In response to this:

nvm, I just realized this is only for GitHub teams. 😝
/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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/release Categorizes an issue or PR as relevant to SIG Release.
Projects
None yet
Development

No branches or pull requests

6 participants