Quarterly SIG Release teams update #1205
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -8,6 +8,7 @@ teams: | |
| - calebamiles | ||
| - justaugustus | ||
| - listx | ||
| - ps882 | ||
| - sumitranr | ||
| - tpepper | ||
| privacy: closed | ||
|
|
@@ -27,103 +28,98 @@ teams: | |
| maintainers: | ||
| - cblecker # ContribEx | ||
| - fejta # Testing | ||
| - mrbobbytables # 1.17 Enhancements Lead | ||
| - nikhita # ContribEx | ||
| - spiffxp # Testing | ||
| members: | ||
| - abgworrall # GCP | ||
| - adisky # OpenStack | ||
|
There was a problem hiding this comment. Is there any particular reason we are still providing access to old There was a problem hiding this comment. @nikhita -- there's still provider code in k/k, so those contributors will likely still need milestone maintainers privs. |
||
| - ahg-g # Scheduling | ||
| - alejandrox1 # 1.17 RT Lead Shadow | ||
| - aleksandra-malinowska # Patch Release Team | ||
| - andrewsykim # Cloud Provider | ||
| - benmoss # Windows | ||
| - bgrant0607 # Architecture | ||
| - bradamant3 # Docs | ||
| - brancz # Instrumentation | ||
| - bubblemelon # Branch Manager | ||
| - calebamiles # Release / PM | ||
| - cantbewong # VMware | ||
| - caseydavenport # Network | ||
| - cheftako # Cloud Provider | ||
| - childsb # Storage | ||
| - chrigl # OpenStack | ||
| - cpanato # Branch Manager | ||
| - craiglpeters # Azure | ||
| - d-nishi # AWS | ||
| - danielromlein # UI | ||
| - dcbw # Network | ||
| - dchen1107 # Node | ||
| - ddebroy # Windows | ||
| - deads2k # API Machinery / Auth | ||
| - derekwaynecarr # Architecture / Node | ||
| - dims # Architecture / Release | ||
| - dougm # Patch Release Team | ||
| - enj # Auth | ||
| - fabriziopandini # Cluster Lifecycle | ||
| - feiskyer # Azure | ||
| - floreks # UI | ||
| - foxish # Big Data | ||
| - frapposelli # VMware | ||
| - hoegaarden # Patch Release Team | ||
| - hogepodge # Cloud Provider / OpenStack | ||
| - hpandeycodeit # Usability | ||
| - idealhack # Patch Release Team | ||
| - janetkuo # Apps | ||
| - jberkhahn # Service Catalog | ||
| - jberkus # Release | ||
| - jdumars # Architecture / PM | ||
| - jeefy # UI | ||
| - jimangel # Docs | ||
| - justaugustus # Azure / PM / Release | ||
| - justinsb # AWS / Cluster Lifecycle | ||
| - k82cn # Scheduling | ||
| - k8s-release-robot # Release | ||
| - khenidak # Azure | ||
| - kow3ns # Apps | ||
| - kris-nova # AWS | ||
| - lachie83 # PM | ||
| - lavalamp # API Machinery | ||
| - liggitt # Auth / Release | ||
| - liyinan926 # Big Data | ||
| - luxas # Cluster Lifecycle | ||
| - maciaszczykm # UI | ||
| - mariantalla # 1.17 RT Lead Shadow | ||
| - mattfarina # Apps / Architecture | ||
| - mborsz # Scalability | ||
| - michmike # Windows | ||
| - mikedanese # Auth | ||
| - mm4tt # Scalability | ||
| - mszostok # Service Catalog | ||
| - mwielgus # Autoscaling | ||
| - neolit123 # Cluster Lifecycle | ||
| - parispittman # ContribEx | ||
| - patricklang # Windows | ||
| - phillels # ContribEx | ||
| - piosz # Instrumentation | ||
| - pmorie # Multicluster | ||
| - prydonius # Apps | ||
| - pwittrock # CLI | ||
| - quinton-hoole # Multicluster | ||
| - rajakavitha1 # Usability | ||
| - saad-ali # Storage | ||
| - seans3 # CLI | ||
| - shyamjvs # Scalability | ||
| - soltysh # CLI | ||
| - spzala # IBM Cloud | ||
| - stevekuznetsov # Testing | ||
| - tallclair # Auth | ||
| - tashimi # Usability | ||
| - thockin # Network | ||
| - timothysc # Cluster Lifecycle / Testing | ||
| - tpepper # Release | ||
| - vllry # Usability | ||
| - wojtek-t # Scalability | ||
| - zacharysarah # Docs | ||
| privacy: closed | ||
| previously: | ||
|
|
@@ -160,20 +156,17 @@ teams: | |
| - alexeldeib # Release Manager Associate | ||
| - bubblemelon # Branch Manager | ||
| - calebamiles # subproject owner / Build Admin | ||
| - cpanato # Branch Manager | ||
| - dougm # Patch Release Team | ||
| - feiskyer # Patch Release Team | ||
| - girikuncoro # Release Manager Associate | ||
| - hoegaarden # subproject owner / Patch Release Team | ||
| - idealhack # Patch Release Team | ||
| - imkin # Release Manager Associate | ||
| - javier-b-perez # Release Manager Associate | ||
| - justaugustus # subproject owner / Branch Manager / Build Admin | ||
| - listx # Build Admin | ||
| - ps882 # Build Admin | ||
| - pswica # Release Manager Associate | ||
| - slicknik # Release Manager Associate | ||
| - sumitranr # Build Admin | ||
|
|
@@ -187,10 +180,11 @@ teams: | |
| members: | ||
| - aleksandra-malinowska # Patch Release Team | ||
| - bubblemelon # Branch Manager | ||
| - cpanato # Branch Manager | ||
| - dougm # Patch Release Team | ||
| - feiskyer # Patch Release Team | ||
| - hoegaarden # Patch Release Team | ||
| - idealhack # Patch Release Team | ||
| - justaugustus # Branch Manager | ||
| - k8s-release-robot | ||
| - tpepper # Patch Release Team | ||
|
|
@@ -200,42 +194,35 @@ teams: | |
| release-team: | ||
| description: Members of the current Release Team and subproject owners. | ||
| maintainers: | ||
| - mrbobbytables # 1.17 Enhancements Lead | ||
| - spiffxp # subproject owner | ||
| members: | ||
| - aishsundar # subproject owner | ||
| - alejandrox1 # 1.17 RT Lead Shadow | ||
| - alenkacz # 1.17 CI Signal Lead | ||
| - bubblemelon # Branch Manager | ||
| - cartyc # 1.17 Release Notes Lead | ||
| - claurence # subproject owner | ||
| - cpanato # Branch Manager | ||
| - daminisatya # 1.17 Docs Lead | ||
| - evillgenius75 # 1.16 Enhancements Shadow | ||
| - guineveresaenger # 1.17 RT Lead | ||
| - idealhack # Branch Manager | ||
| - jberkus # subproject owner | ||
| - jeefy # 1.17 RT Lead Shadow | ||
| - josiahbjorgaard # 1.17 Bug Triage Lead | ||
| - justaugustus # subproject owner | ||
| - kacole2 # 1.16 Enhancements Lead | ||
| - lachie83 # subproject owner | ||
| - mariantalla # 1.17 RT Lead Shadow | ||
| - nikopen # 1.16 RT Lead Shadow | ||
| - onlydole # 1.16 Communications Lead | ||
| - onyiny-ang # 1.16 Release Notes Shadow | ||
| - rawkode # 1.17 Communications Lead | ||
| - rbitia # 1.16 Enhancements Shadow | ||
| - saschagrunert # 1.16 Release Notes Lead | ||
| - simplytunde # 1.16 Docs Lead | ||
| - soggiest # 1.16 CI Signal Shadow | ||
| - tpepper # subproject owner | ||
| - xmudrii # 1.16 Bug Triage Lead | ||
| privacy: closed | ||
|
|
@@ -246,32 +233,39 @@ teams: | |
| and can be used as a notification group. | ||
| Remove org members who are not current Release Team Leads. | ||
| members: | ||
| - alejandrox1 # 1.17 RT Lead Shadow | ||
| - guineveresaenger # 1.17 RT Lead | ||
| - jeefy # 1.17 RT Lead Shadow | ||
| - mariantalla # 1.17 RT Lead Shadow | ||
| privacy: closed | ||
| sig-release: | ||
| description: SIG Release Members | ||
| maintainers: | ||
| - mrbobbytables | ||
| - nikhita | ||
|
There was a problem hiding this comment. Out of curiosity, how do we decide who gets added to this team? Is it members who have previously participated in some form in the release team? Is this team also pruned periodically/after a release? There was a problem hiding this comment. @nikhita -- SIG Release has the concept of membership --> https://github.com/kubernetes/community/blob/master/sig-release/charter.md#sig-membership tl;dr Chairs, subproject owners, former RT role leads We don't currently prune anyone; only add, but members can definitely ask to be removed. |
||
| - spiffxp | ||
| members: | ||
| - abgworrall | ||
| - AishSundar | ||
| - alejandrox1 | ||
| - aleksandra-malinowska | ||
| - alenkacz | ||
| - alexeldeib | ||
| - amwat | ||
| - BenTheElder | ||
| - Bradamant3 | ||
| - bubblemelon | ||
| - caesarxuchao | ||
| - calebamiles | ||
| - cartyc | ||
| - castrojo | ||
| - chenopis | ||
| - chrisz100 | ||
| - cjwagner | ||
| - claurence | ||
| - cpanato | ||
| - craiglpeters | ||
| - daminisatya | ||
| - dashpole | ||
| - dchen1107 | ||
| - dims | ||
|
|
@@ -282,29 +276,35 @@ teams: | |
| - evillgenius75 | ||
| - feiskyer | ||
| - foxish | ||
| - girikuncoro | ||
| - guineveresaenger | ||
| - hoegaarden | ||
| - idealhack | ||
| - imkin | ||
| - ixdy | ||
| - javier-b-perez | ||
| - jberkus | ||
| - jdumars | ||
| - jeefy | ||
| - jimangel | ||
| - josiahbjorgaard | ||
| - jpbetz | ||
| - justaugustus | ||
| - k82cn | ||
| - kacole2 | ||
| - Katharine | ||
| - kbarnard10 | ||
| - krzyzacy | ||
| - lachie83 | ||
| - liggitt | ||
| - listx | ||
| - MaciekPytel | ||
| - MAKOSCAFEE | ||
| - mariantalla | ||
| - marpaia | ||
| - marun | ||
| - mbohlool | ||
| - mcrute | ||
| - mistyhacks | ||
| - mohammedzee1000 | ||
| - monopole | ||
|
|
@@ -313,15 +313,20 @@ teams: | |
| - nwoods3 | ||
| - onlydole | ||
| - onyiny-ang | ||
| - ps882 | ||
| - pswica | ||
| - pwittrock | ||
| - radhikapc | ||
| - rawkode | ||
| - rbitia | ||
| - saad-ali | ||
| - saschagrunert | ||
| - shyamjvs | ||
| - simplytunde | ||
| - slicknik | ||
| - soggiest | ||
| - steveperry-53 | ||
| - sumitranr | ||
| - tfogo | ||
| - tpepper | ||
| - wojtek-t | ||
|
|
||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One comment: While it is up to sig-release to administer their repos as they see fit, I think it's an anti-pattern to tie sig chairpersonship to a repos permission set.
Chairs are a process role, as defined in the dig governance docs. There are certain places where it makes sense for the chairs/leads to automatically be in owners files (mainly k/community meta docs, and k/org github meta data -- specifically where being in the owners file is directly tied to administering the sig), but I think in most cases actual access to things should be delegated to subproject owners.
This is similar to how the steering committee no longer gets automatic github owner to everything, rather they delegate that to the subproject that administers it.
To be clear though, this is just my opinion, and is not blocking (strictly speaking)
cc: @kubernetes/sig-release
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cblecker -- That's fair.
To be more explicit, SIG Release Chairs are subproject owners of the Release Engineering project and should have ownership of all tools/processes which have the potential to affect a Kubernetes release.
I was going to cite some things from our charter, specifically, deviations from SIG governance e.g., SIG Release does not have Technical Leads, as the Chairs are required to be technical, but it seems the charter is due for some updates (which I'll action on this cycle).
p.s. agreed on the Steering point; I did open the issue, after all. 😝
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ahh okay. I think we then just need to be explicit that Stephen and Caleb are added to this group because they are subproject owners, not because they are chairs. They're two distinct jobs, even though the same person can hold both. Is that right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cblecker -- yep, yep. Updated the PR description and commit comment to reflect.