seeding sig-auth tech leads

[Jordan Liggitt]

In the process of opening the PR to change chairs, I realized that even though our charter indicates we will make use of the tech lead role, we haven't seeded that list. Because many people wear a bunch of hats, it wasn't obvious that was lacking as the distinction between the chair and tech lead role developed over the last year.

As a method of seeding this list, I propose we do the following:

1. Update (and merge) the subprojects PR to ensure we have up-to-date OWNERS file references for our subprojects
2. Gather the list of sig-auth subproject owners (which I think is supposed to map to approvers in those files)
3. Determine the people with the broadest ownership for sig-auth subprojects
4. Seed the top 3 who are willing to serve in a tech lead capacity

What are people's thoughts on that approach?

Jordan

[Mo Khan]

Sounds like a good plan to me as long as the OWNERS files are correct.

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

[Jordan Liggitt]

As a first step, opened https://github.com/kubernetes/kubernetes/pull/70600 to make sure we have approver/reviewer aliases for each of the sig-auth subprojects, populated with existing approvers/reviewers for those packages where possible.

On Thu, Oct 4, 2018 at 2:22 PM Mo Khan <mo...@redhat.com> wrote:

Sounds like a good plan to me as long as the OWNERS files are correct.

On Thu, Oct 4, 2018 at 11:21 AM, 'Jordan Liggitt' via kubernetes-sig-auth <kubernete...@googlegroups.com> wrote:

In the process of opening the PR to change chairs, I realized that even though our charter indicates we will make use of the tech lead role, we haven't seeded that list. Because many people wear a bunch of hats, it wasn't obvious that was lacking as the distinction between the chair and tech lead role developed over the last year.

As a method of seeding this list, I propose we do the following:

1. Update (and merge) the subprojects PR to ensure we have up-to-date OWNERS file references for our subprojects
2. Gather the list of sig-auth subproject owners (which I think is supposed to map to approvers in those files)
3. Determine the people with the broadest ownership for sig-auth subprojects
4. Seed the top 3 who are willing to serve in a tech lead capacity

What are people's thoughts on that approach?

Jordan

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-auth" group.

To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-...@googlegroups.com.
To post to this group, send email to kubernete...@googlegroups.com.

[Jordan Liggitt]

Circling back to this, opened https://github.com/kubernetes/community/pull/3080 as described. Will bring up in the sig-auth meeting today and leave the PR open for comment.