Tighten Permissions on k/features

[Stephen Augustus]

Hey everyone,

Feature Maintainers often use GitHub settings like `Milestone` to determine which Features require triage.

It's important that these settings are only touched by Feature Maintainers to ensure better signal during the release process.

As such, I'd like to do the following:

- remove the `kubernetes-maintainers` and `kubernetes-release-managers` from having direct write access to k/features

- update the membership of `features-maintainers` to only include the following:

  - SIG PM leadership

  - Product Management subproject leadership

  - Program Management subproject leadership

  - current Release Team Feature Lead & Shadows

- ensure the following are Maintainers of the `features-maintainers` GitHub group:

  - SIG PM leadership

  - Product Management subproject leadership

  - Program Management subproject leadership

Here's the current list to simplify the updates:

- Maintainers: @apsinha @idvoretskyi @calebamiles @justaugustus @dustinkirkland @jdumars

- Members: @kacole2 @robertsandoval @rajendar38

We'll go with lazy consensus for this on Wednesday, 7/25.

Here's the corresponding GitHub issue: https://github.com/kubernetes/features/issues/590

Best,

Stephen

--

Stephen Augustus

Kubernetes Product Management Chair

[Ihor Dvoretskyi]

+1.

--
You received this message because you are subscribed to the Google Groups "kubernetes-PM" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-p...@googlegroups.com.
To post to this group, send email to kubern...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-pm/CAN4RaVTZ-jV%2BqeJp-Pb359GaZc0RWgT0%2BfmiZd%2BasZycJwLU6Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Stephen Augustus]

Circling back on tightening up the repo permissions on k/enhancements with a slightly different plan...

How about we do the following?

• Remove write access for:
• `kubernetes-maintainers`
• `kubernetes-release-managers`
• Give write access on k/enhancements to `kubernetes-milestone-maintainers`
• Expand on the definition of [milestone maintainers](https://github.com/kubernetes/sig-release/tree/master/release-team#milestone-maintainers)
• Prune `enhancements-maintainers` to only include the SIG PM maintainers (@calebamiles, @idvoretskyi, @jdumars, @justaugustus) - [kubernetes/org#498](https://github.com/kubernetes/org/pull/498)

I suggest `kubernetes-milestone-maintainers` for write access because that team:

• is exactly the list of contributors that would need milestone privileges
• likely also the list of people that would need to edit enhancement issue content
• is actively pruned across release cycles

If there are no strong objections here, I'd like to assume lazy consensus Thursday, 2/21 EOD PT and proceed with the change this Friday.

-- Stephen

To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-pm/CA%2BhxP0vjgkEdFOPAvtKyUTe5-J4pBp5cv%3D4g9cjiPTPYiFvcJQ%40mail.gmail.com.

[Stephen Augustus]

(Adding k-dev as well)

tl;dr - 

We're planning up updating repo permissions on k/enhancements. Details below. 

Anyone affected by this change has already been pinged on https://github.com/kubernetes/enhancements/issues/590.

Lazy consensus, assuming no major objections: Thursday, 2/21 EOD PT

Change to happen on Friday.

Let me know if you have any questions!

-- Stephen

[Stephen Augustus]

Hearing no objections, we're going to move forward with this change tomorrow.

-- Stephen

[Stephen Augustus]

Thanks for helping close the loop on this, Aaron! :)

I've also updated the description for the team[1] and the process for requesting access to kubernetes-milestone-maintainers[2].

-- Stephen

[1] https://github.com/kubernetes/org/pull/523

[2] https://github.com/kubernetes/sig-release/pull/517

On Fri, Feb 22, 2019 at 4:55 PM Aaron Crickenberger <spi...@gmail.com> wrote:

Changes in effect: https://github.com/kubernetes/enhancements/issues/590#issuecomment-466560650

- aaron

--
You received this message because you are subscribed to the Google Groups "Kubernetes developer/contributor discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-de...@googlegroups.com.
To post to this group, send email to kuberne...@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-dev.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/60fdc376-aac9-487e-ab9b-52d03af1d1ee%40googlegroups.com.