Fwd: Approvers and Reviewers for Windows Node KEP

[Craig Peters]

Had the wrong email for sig-pm

---------- Forwarded message ---------
From: Craig Peters <craig.l...@gmail.com>
Date: Thu, Jan 24, 2019 at 12:11 PM
Subject: Approvers and Reviewers for Windows Node KEP
To: <kubernetes-si...@googlegroups.com>, <kubernetes-...@googlegroups.com>, <kubernetes-...@googlegroups.com>, <kubernete...@googlegroups.com>, <kubernetes-sig-c...@googlegroups.com>, <kubernetes-...@googlegroups.com>, <kubernete...@googlegroups.com>, <kubernet...@googlegroups.com>

All,

To remain on track for the 1.14 milestone, this Windows Node KEP and issue (https://github.com/kubernetes/enhancements/pull/676 and https://github.com/kubernetes/enhancements/issues/116) need approval to be marked as implementable in time for enhancements freeze on January 29, 2019. Towards that end I am proposing that the list of approvers and reviews be:

Approvers:

sig-release: @spiffxp (Aaron Crickenberger)

sig-architecture: @briangrant (Brian Grant)

sig-windows: @m2 (Michael Michael)

sig-windows: @patricklang (Patrick Lang)

Reviewers:

sig-architecture: @mattfarina (Matt Farina)

sig-node: @daschott (David Schott)

sig-testing: @timothysc (Timothy St. Clair)

If you're on the proposed list and willing to be a reviewer or approver, thanks! If you're on the list and cannot, please suggest an alternate. If you're not on the list and think you should be please let me know.

Thanks,

Craig

P.S.

Apologies for the broad distribution, but it is necessary to assure that we get the right set of reviewers and approvers for adding Windows Node support to Kubernetes clusters. 

Windows container users desire Kubernetes to include GA support. We are currently tracking the KEP for the 1.14 milestone. In discussions with a number of SIGs it was agreed that Windows support requires broad review prior to release because adding a new operating system type to Kubernetes clusters has many wide-ranging implications. Towards this end I am sending this email to assess the level of agreement among us about who should review, and who should approve this KEP. 

As we adopt and adapt KEP process (https://github.com/kubernetes/enhancements/), the reviewer and approver roles are still under refinement, but the working model is that reviewers are responsible for raising issues on a KEP, and approvers are responsible for assuring that the reviews have been thorough and addressed appropriately.