Re: Cleaning up SIG Release GitHub teams

[Stephen Augustus]

Circling back on this...

We've been discussing cleaning up the kubernetes-milestone-maintainers GitHub for a little while[1][2] and Aaron had a wonderful idea; let's just purge the list for the new year!

Hearing no strong objections on those issues or the 1.14 RT call this week, I plan on removing all members, except SIG Release Chairs and the 1.14 Release Team, this Friday.

With peribolos around the corner[3], we'll be able to handle and track new additions to the team via k/org.

-- Stephen Augustus (@justaugustus) // SIG Release Chair

[1] https://github.com/kubernetes/sig-release/issues/241

[2] https://github.com/kubernetes/sig-release/issues/353

[3] https://groups.google.com/d/topic/kubernetes-sig-testing/rVq8RiZXKbY/discussion

On Thu, Nov 15, 2018 at 6:16 PM Stephen Augustus <Ste...@agst.us> wrote:

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-maintainers
• release-admins
• sig-release-members
• Rename sig-release-members to sig-release
• Demote non-sig-release-admins to member status
• Add all 1.5+ Release Team role leads to group, per SIG Release Member policy (https://github.com/kubernetes/community/blob/master/sig-release/charter.md#sig-membership) (pre-1.5 were not listed in k/sig-release)
• Update SIG Release contact info: https://github.com/kubernetes/community/pull/2941
• Cleanup up repo admins for k/sig-release and k/release

There are still a few things to do:

• Prune kubernetes-milestone-maintainers - #241
  
• Prune kubernetes-release-managers
• Add subproject OWNERS to sig-release
• Close out the cleanup issue
  

Feel free to call out anything that I might be missing! :)

-- Stephen Augustus // SIG Release Chair

On Thu, Nov 15, 2018 at 7:14 AM Stephen Augustus <Ste...@agst.us> wrote:

Hey y'all,

I just realized a bunch of GitHub team notifications are going out that could be cause for alarm, so I'm shooting out a quick note.

I'm in the process of cleaning up SIG Release GitHub teams, as part of this issue: https://github.com/kubernetes/sig-release/issues/353

I'll send an update when I've finished.

-- Stephen Augustus // SIG Release Chair

[lig...@google.com]

That's not what was proposed in the issue, what was proposed was "Add the release team. Add current SIG chairs or TLs.", not just SIG Release chairs/release team. 

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-re...@googlegroups.com.
To post to this group, send email to kubernetes-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-release/CAFQm5ySp%2B7pfgo5fe7NNEPJBFY9MG1mOSFuW5Z_4W0hJdg7LBg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Stephen Augustus]

Thanks for the catch, Jordan. All Chairs / TLs was the intent; not just SIG Release.

[Josh Berkus]

On 01/08/2019 08:14 PM, Stephen Augustus wrote:
> Hearing no strong objections on those issues or the 1.14 RT call this
> week, I plan on removing all members, except SIG Release Chairs and the
> 1.14 Release Team, this Friday.

What about SIG Technical Leads? They should have MM as well. No?

--
--
Josh Berkus
Kubernetes Community
Red Hat OSAS

[Stephen Augustus]

Yep, all SIG Chairs and TLs will be included. 

[Stephen Augustus]

I'll be proceeding with this work shortly.

[Stephen Augustus]

Just to close the loop. This work has been completed.

We also went ahead and updated the other SIG Release teams, so our cleanup issue[1] is now closed. PRs are here[2][3].

h/t to Christoph for running the peribolos syncs! :)

-- Stephen

[1] https://github.com/kubernetes/sig-release/issues/353

[2] https://github.com/kubernetes/org/pull/346

[3] https://github.com/kubernetes/org/pull/351