[RFC] SIG-Auth initial charter #2000

tallclair · 2018-04-04T05:39:28Z

Co-authored by: @liggitt @ericchiang @tallclair

Adapted from sig-governance-template-short and sig-governance-template-long.

/sig auth

k8s-ci-robot · 2018-04-04T05:39:33Z

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: liggitt

Assign the PR to them by writing /assign @liggitt in a comment when ready.

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

sig-auth/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

liggitt · 2018-04-04T14:49:18Z

cc @kubernetes/steering-committee @kubernetes/sig-auth-proposals

liggitt · 2018-04-04T14:52:22Z

sig-auth/charter.md

@@ -0,0 +1,150 @@
+# SIG Auth Governance


this jumps into structure/governance, but doesn't actually include the charter (current original charter/goals/non-goals inlined at https://github.com/kubernetes/community/blob/master/sig-auth/README.md#goals)

do we want to move that into this document? separately, those could use some updating/clarification, but probably best to tackle that in another PR

I think the charter / mission statement / goals are more broadly useful (and interesting). What do you think of keeping that content in the README, and instead renaming this document to "governance.md"?

liggitt · 2018-04-10T14:12:22Z

sig-auth/governance.md

+  - Technical Leads *MAY* select additional tech leads through a [super-majority] vote amongst tech
+    leads and chairs.  This *SHOULD* be supported by a majority of SIG Members under
+    [lazy-consensus].
+  - Technical Leads *MUST* remain active in the role and are automatically removed from the position


might consider rewording this to allow for a short-term planned absence (paternity/maternity leave, sabbatical, etc) with coordination to cover responsibilities. same comment for chairs.

tallclair · 2018-05-17T00:17:14Z

/assign @liggitt @ericchiang

liggitt · 2018-05-23T15:49:42Z

LGTM
/hold
for @ericchiang and ack from @kubernetes/steering-committee

ericchiang · 2018-05-23T16:07:19Z

lgtm

mikedanese · 2018-06-19T18:30:03Z

sig-auth/governance.md

+    subproject
+  - *MUST* proactively maintain the subproject health and status or delegate this
+    responsibility. For actively developed projects, this *SHOULD* include setting milestone
+    priorities, tracking release bits, and ensure adequate test coverage. For maintenance mode


s/ensure/ensuring

mikedanese · 2018-06-19T18:32:48Z

Who is responsible for semi-regular sig/auth issue triage?
Who is first point of contact to direct flaky/failing tests to subproject owners?

tallclair · 2018-06-19T23:30:02Z

Other questions from OOB discussion w/ @liggitt

what are chair roles?
do chairs make technical decisions?
what do chairs do around release?
do chairs or TLs make call on what features get into milestones?
PRs vs spreadsheets

We need to revisit the list of responsibilities with specific examples.

pwittrock · 2018-06-27T20:57:24Z

sig-auth/governance.md

+# SIG Auth Governance
+
+## Roles
+


What is the mission / scope / subprojects?

+1 See the SIG charter template if you need some guidance

I'm happy to help brainstorm this with y'all.

michelleN

Hey @tallclair @liggitt @ericchiang !

Thanks for submitting your charter. Please add a Scope section like the one in this template: https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-charter-template.md
We'd like for SIG charters to give everyone an idea of what areas of interest your SIG covers and the part of the code base or any sub projects it is responsible for. Appreciate your time!

michelleN · 2018-07-13T15:46:33Z

sig-auth/governance.md

+# SIG Auth Governance
+
+## Roles
+


+1 See the SIG charter template if you need some guidance

tallclair · 2018-07-17T21:49:24Z

/unassign @ericchiang
/assign @mikedanese

jbeda · 2018-07-18T19:41:11Z

sig-auth/governance.md

+    especially over areas for which they are the owner
+  - *MAY* be removed if not proactively working with other Subproject Owners to fulfill
+    responsibilities.
+  - *MAY* decide to step down at any time and propose a replacement.  Use [lazy-consensus] amongst


If a subproject has no effective leadership would it fall to majority of the SIG or the TLs of the SIG to solve/address this?

jbeda · 2018-07-18T19:43:55Z

sig-auth/governance.md

+they have defined.
+
+- Proposing and making decisions
+  - Proposals *SHOULD* be sent as [KEP] PRs and published to [kubernetes-sig-auth] as an


It would be great to document here who needs to be set as an approver when doing a KEP. My guess is that for stuff that impacts most of the SIG it'd be a TL (with acceptance from that TL and lazy consensus around that choice). Similarly for something that is solely scoped to a subproject it'd be a subproject owner w/ lazy consensus.

philips · 2018-07-20T16:49:33Z

Thank you for your patience as we work to your SIG charter merged.

Through the process of reviewing the first 11 charters the Steering Committee (SC) found a lot of copy/paste language caused by our poorly designed initial charter template. To fix this there is a new SIG charter template which focuses on the main things we want to see in charters: scope and responsibilities.

Please consider updating to this charter template and putting focus into the scope and responsibilities. SC members will focus more on a deep review of scope more than anything else and using this template will help with that focus.

tallclair · 2018-07-28T02:37:10Z

In the interest of preserving the history in this PR, I opened a new PR with the updated charter #2431

RIP #2000

k8s-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. sig/auth Categorizes an issue or PR as relevant to SIG Auth. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Apr 4, 2018

k8s-ci-robot requested review from ericchiang and liggitt April 4, 2018 05:39

k8s-ci-robot added the kind/design Categorizes issue or PR as related to design. label Apr 4, 2018

liggitt reviewed Apr 4, 2018

View reviewed changes

tallclair added 2 commits April 4, 2018 10:39

Copy governance template to sig-auth

21a5343

SIG-Auth governance

f5b6e69

tallclair force-pushed the charter branch from e5cb8e1 to f5b6e69 Compare April 4, 2018 17:41

liggitt reviewed Apr 10, 2018

View reviewed changes

Allow for short-term leaves of absence of leadership roles

a401a9c

k8s-ci-robot assigned ericchiang and liggitt May 17, 2018

k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 23, 2018

mikedanese reviewed Jun 19, 2018

View reviewed changes

pwittrock added the committee/steering Denotes an issue or PR intended to be handled by the steering committee. label Jun 21, 2018

jdumars mentioned this pull request Jun 24, 2018

Charters Meta-issue kubernetes/steering#31

Closed

pwittrock reviewed Jun 27, 2018

View reviewed changes

michelleN suggested changes Jul 13, 2018

View reviewed changes

sig-auth/governance.md

# SIG Auth Governance

## Roles

Copy link

michelleN Jul 13, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 See the SIG charter template if you need some guidance

k8s-ci-robot assigned mikedanese and unassigned ericchiang Jul 17, 2018

jbeda reviewed Jul 18, 2018

View reviewed changes

tallclair mentioned this pull request Jul 28, 2018

sig-auth charter (v2) #2431

Merged

tallclair closed this Jul 28, 2018

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[RFC] SIG-Auth initial charter #2000

[RFC] SIG-Auth initial charter #2000

tallclair commented Apr 4, 2018

k8s-ci-robot commented Apr 4, 2018

liggitt commented Apr 4, 2018

liggitt Apr 4, 2018 •

edited

Loading

tallclair Apr 4, 2018

liggitt Apr 4, 2018

liggitt Apr 10, 2018

tallclair May 16, 2018

tallclair commented May 17, 2018

liggitt commented May 23, 2018

ericchiang commented May 23, 2018

mikedanese Jun 19, 2018

mikedanese commented Jun 19, 2018

tallclair commented Jun 19, 2018

pwittrock Jun 27, 2018

michelleN Jul 13, 2018

jbeda Jul 18, 2018

michelleN left a comment

michelleN Jul 13, 2018

tallclair commented Jul 17, 2018

jbeda Jul 18, 2018

jbeda Jul 18, 2018

philips commented Jul 20, 2018

tallclair commented Jul 28, 2018

[RFC] SIG-Auth initial charter #2000

[RFC] SIG-Auth initial charter #2000

Conversation

tallclair commented Apr 4, 2018

k8s-ci-robot commented Apr 4, 2018

liggitt commented Apr 4, 2018

liggitt Apr 4, 2018 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

tallclair commented May 17, 2018

liggitt commented May 23, 2018

ericchiang commented May 23, 2018

Choose a reason for hiding this comment

mikedanese commented Jun 19, 2018

tallclair commented Jun 19, 2018

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

michelleN left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

tallclair commented Jul 17, 2018

Choose a reason for hiding this comment

Choose a reason for hiding this comment

philips commented Jul 20, 2018

tallclair commented Jul 28, 2018

liggitt Apr 4, 2018 •

edited

Loading