Skip to content

Sig Governance Short Template #1830

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Mar 6, 2018
Merged

Sig Governance Short Template #1830

merged 1 commit into from
Mar 6, 2018

Conversation

pwittrock
Copy link
Member

@pwittrock pwittrock commented Feb 21, 2018 •
edited
Loading

Short template for sig governance

Also see:

@k8s-ci-robot k8s-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Feb 21, 2018
@k8s-github-robot k8s-github-robot added the committee/steering Denotes an issue or PR intended to be handled by the steering committee. label Feb 21, 2018
@pwittrock pwittrock mentioned this pull request Feb 22, 2018
Closed
pwittrock added a commit to pwittrock/community that referenced this pull request Feb 22, 2018
@pwittrock
delete faq and short template (short template is in PR) kubernetes#1830
ce38873
@pwittrock pwittrock force-pushed the sig-governance-short branch from c4e3523 to e97d841 Compare February 23, 2018 16:08
@k8s-ci-robot k8s-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Feb 23, 2018
@pwittrock pwittrock changed the title Sig governance short. Rebase on 1650 Sig governance short template Feb 23, 2018
@pwittrock pwittrock force-pushed the sig-governance-short branch 3 times, most recently from 71baeae to 6d58a38 Compare February 23, 2018 16:35
@pwittrock pwittrock changed the title Sig governance short template Sig Governance Short Template Feb 23, 2018
@k8s-ci-robot k8s-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Feb 27, 2018
@pwittrock pwittrock force-pushed the sig-governance-short branch 4 times, most recently from e5afb18 to db9b7b5 Compare February 27, 2018 19:50
@philips
Copy link
Contributor

philips commented Feb 27, 2018

LGTM, but I see you are still incorporating stuff.

timothysc
timothysc approved these changes Feb 28, 2018
View reviewed changes
Copy link
Member

@timothysc timothysc left a comment

Choose a reason for hiding this comment

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

lgtm but will wait on others on before labeling.

@pwittrock
Copy link
Member Author

@philips @timothysc Thanks!

I updated the PR to include the new SIG Lead name (long live Coordinator!). I also refined / clarified some points that were implied but could be made more clear.

  • Change SIG Lead -> Coordinator
  • Generally tighten up wording
  • Clarify that votes to select coordinators and project leads are done amongst existing coordinators / project leads
  • Re-order options for SIG Technical Lead vs Federation of Project Leads to put SIG TL first since it is expected to be the more common case
  • Clarify that subproject leads as escalation point a MUST (this wasn't clearly called out)
  • Clarify that subproject leads can delegate decision making authority
  • Clarify that coordinators can delegate responsibilities to members
  • Clarify SIG membership as having some documented role in either the SIG or a subproject (reviewer / approver count)

@pwittrock pwittrock force-pushed the sig-governance-short branch 3 times, most recently from 23ad236 to c92af5d Compare March 1, 2018 01:34
bgrant0607
bgrant0607 reviewed Mar 1, 2018
View reviewed changes
committee-steering/governance/sig-governance-template-short.md Outdated
- Resolve X-Subproject technical issues and decisions


- Subproject Leads
Copy link
Member

Choose a reason for hiding this comment

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

This should be subproject owners, to be consistent with the contributor ladder.

Copy link
Member Author

Choose a reason for hiding this comment

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

+1 Done

tpepper
tpepper reviewed Mar 2, 2018
View reviewed changes
committee-steering/governance/sig-governance-template-short.md Outdated

[lazy-consensus]: http://communitymgt.wikia.com/wiki/Lazy_consensus
[super-majority]: https://en.wikipedia.org/wiki/Supermajority#Two-thirds_vote
[warnocks-dilemma]: http://communitymgt.wikia.com/wiki/Warnock%27s_Dilemma
Copy link
Member

Choose a reason for hiding this comment

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

These links look copied from the long template, with some not used and probably should be (eg: lazy consensus) and some not used and probably need removed (eg: warnocks dilemma and slo).

Copy link
Member Author

Choose a reason for hiding this comment

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

Done

@pwittrock pwittrock force-pushed the sig-governance-short branch from c92af5d to 40e1634 Compare March 6, 2018 01:43
@pwittrock
Copy link
Member Author

Addressed outstanding comments. Updated the SIG role names.

@pwittrock pwittrock force-pushed the sig-governance-short branch from 40e1634 to 1a4a1bf Compare March 6, 2018 21:49
@pwittrock pwittrock force-pushed the sig-governance-short branch from 98a14ae to 68658bf Compare March 6, 2018 22:10
@bgrant0607
Copy link
Member

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Mar 6, 2018
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bgrant0607, pwittrock

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:

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

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 6, 2018
@k8s-ci-robot k8s-ci-robot merged commit e208e4d into kubernetes:master Mar 6, 2018
wking added a commit to wking/kubernetes-community that referenced this pull request May 22, 2018
@wking
*: Assorted internal-reference cleanups
cad3440 
This is mostly replacing
https://github.com/kubernetes/community/blob/master/... links with
relative links, because relative links are easier to maintain.  For
example, if you rename a.md to b.md in a feature branch, updating an
../a.md to ../b.md target will work immediately (e.g. during
pull-request review), while updating
https://github.com/kubernetes/community/blob/master/a.md to
https://github.com/kubernetes/community/blob/master/b.md will only
work after your branch lands the rename in master.

I'm not sure why the #L1454 fragment was part of the old
sig-governance template sigs.yaml link, but it's been there since the
template landed in 68658bf (Provide short template for SIG
governance, 2018-02-23, kubernetes#1830).  I've removed it in this commit.

The Kubernetes Charter README link in the sig-governance template
could just be:

  [Kubernetes Charter README]: README.md

but I've sent it down to the project root and back to make life easier
on new SIGs which copy/paste the file to a new location in this
repository.  With this commit they'll just need to drop one level of
../ to get the references working from places like
sig-contributor-experience/charter.md.

I've also chased a few files and anchors as they've moved around
(e.g. the OBSOLETE_templates.md rename from 18958f8 (addressing
Brians comments, 2017-09-06, kubernetes#1010) and the "and maintenance" header
addition from f471f6b (Add new contact info for Paris and me,
2017-10-17, kubernetes#1215).

This commit isn't complete, but it's a step in the right direction and
all I had time for tonight ;).
@wking wking mentioned this pull request May 22, 2018
Closed
wking added a commit to wking/kubernetes-community that referenced this pull request May 22, 2018
@wking
*: Assorted internal-reference cleanups
8d5390e 
This is mostly replacing
https://github.com/kubernetes/community/blob/master/... links with
relative links, because relative links are easier to maintain.  For
example, if you rename a.md to b.md in a feature branch, updating an
../a.md to ../b.md target will work immediately (e.g. during
pull-request review), while updating
https://github.com/kubernetes/community/blob/master/a.md to
https://github.com/kubernetes/community/blob/master/b.md will only
work after your branch lands the rename in master.

I'm not sure why the #L1454 fragment was part of the old
sig-governance template sigs.yaml link, but it's been there since the
template landed in 68658bf (Provide short template for SIG
governance, 2018-02-23, kubernetes#1830).  I've removed it in this commit.

The Kubernetes Charter README link in the sig-governance template
could just be:

  [Kubernetes Charter README]: README.md

but I've sent it down to the project root and back to make life easier
on new SIGs which copy/paste the file to a new location in this
repository.  With this commit they'll just need to drop one level of
../ to get the references working from places like
sig-contributor-experience/charter.md.

I've also chased a few files and anchors as they've moved around,
e.g. the OBSOLETE_templates.md rename from 18958f8 (addressing Brians
comments, 2017-09-06, kubernetes#1010) and the "and maintenance" header addition
from f471f6b (Add new contact info for Paris and me, 2017-10-17,

This commit isn't complete, but it's a step in the right direction and
all I had time for tonight ;).
wking added a commit to wking/kubernetes-community that referenced this pull request May 22, 2018
@wking
*: Assorted internal-reference cleanups
7d86321 
This is mostly replacing
https://github.com/kubernetes/community/blob/master/... links with
relative links, because relative links are easier to maintain.  For
example, if you rename a.md to b.md in a feature branch, updating an
../a.md to ../b.md target will work immediately (e.g. during
pull-request review), while updating
https://github.com/kubernetes/community/blob/master/a.md to
https://github.com/kubernetes/community/blob/master/b.md will only
work after your branch lands the rename in master.

I'm not sure why the #L1454 fragment was part of the old
sig-governance template sigs.yaml link, but it's been there since the
template landed in 68658bf (Provide short template for SIG
governance, 2018-02-23, kubernetes#1830).  I've removed it in this commit.

The Kubernetes Charter README link in the sig-governance template
could just be:

  [Kubernetes Charter README]: README.md

but I've sent it down to the project root and back to make life easier
on new SIGs which copy/paste the file to a new location in this
repository.  With this commit they'll just need to drop one level of
../ to get the references working from places like
sig-contributor-experience/charter.md.

I've also chased a few files and anchors as they've moved around,
e.g. the OBSOLETE_templates.md rename from 18958f8 (addressing Brians
comments, 2017-09-06, kubernetes#1010) and the "and maintenance" header addition
from f471f6b (Add new contact info for Paris and me, 2017-10-17,

This commit isn't complete, but it's a step in the right direction and
all I had time for tonight ;).
wking added a commit to wking/kubernetes-community that referenced this pull request May 22, 2018
@wking
*: Assorted internal-reference cleanups
e008e0d 
This is mostly replacing
https://github.com/kubernetes/community/blob/master/... links with
relative links, because relative links are easier to maintain.  For
example, if you rename a.md to b.md in a feature branch, updating an
/a.md to /b.md target will work immediately (e.g. during pull-request
review), while updating
https://github.com/kubernetes/community/blob/master/a.md to
https://github.com/kubernetes/community/blob/master/b.md will only
work after your branch lands the rename in master.

I'm not sure why the #L1454 fragment was part of the old
sig-governance template sigs.yaml link, but it's been there since the
template landed in 68658bf (Provide short template for SIG
governance, 2018-02-23, kubernetes#1830).  I've removed it in this commit.

The Kubernetes Charter README link in the sig-governance template
could just be:

  [Kubernetes Charter README]: README.md

but I've based it on the project root and back to make life easier
on new SIGs which copy/paste the file to a new location in this
repository.

I personally prefer targets that use ../ for referencing other
directories within a project, because those also work with generic
Markdown tools (e.g. Emacs' Markdown mode).  I've gone with /-rooted
targets in this commit as requested in
/sig-contributor-experience/markdown-link-style-guide.md.

I've also chased a few files and anchors as they've moved around,
e.g. the OBSOLETE_templates.md rename from 18958f8 (addressing Brians
comments, 2017-09-06, kubernetes#1010) and the "and maintenance" header addition
from f471f6b (Add new contact info for Paris and me, 2017-10-17,

This commit isn't complete, but it's a step in the right direction and
all I had time for tonight ;).
wking added a commit to wking/kubernetes-community that referenced this pull request Jun 20, 2018
@wking
*: Assorted internal-reference cleanups
13aae20 
This is mostly replacing
https://github.com/kubernetes/community/blob/master/... links with
relative links, because relative links are easier to maintain.  For
example, if you rename a.md to b.md in a feature branch, updating an
/a.md to /b.md target will work immediately (e.g. during pull-request
review), while updating
https://github.com/kubernetes/community/blob/master/a.md to
https://github.com/kubernetes/community/blob/master/b.md will only
work after your branch lands the rename in master.

I'm not sure why the #L1454 fragment was part of the old
sig-governance template sigs.yaml link, but it's been there since the
template landed in 68658bf (Provide short template for SIG
governance, 2018-02-23, kubernetes#1830).  I've removed it in this commit.

The Kubernetes Charter README link in the sig-governance template
could just be:

  [Kubernetes Charter README]: README.md

but I've based it on the project root and back to make life easier
on new SIGs which copy/paste the file to a new location in this
repository.

I personally prefer targets that use ../ for referencing other
directories within a project, because those also work with generic
Markdown tools (e.g. Emacs' Markdown mode).  I've gone with /-rooted
targets in this commit as requested in
/sig-contributor-experience/markdown-link-style-guide.md.

I've also chased a few files and anchors as they've moved around,
e.g. the OBSOLETE_templates.md rename from 18958f8 (addressing Brians
comments, 2017-09-06, kubernetes#1010) and the "and maintenance" header addition
from f471f6b (Add new contact info for Paris and me, 2017-10-17,

This commit isn't complete, but it's a step in the right direction and
all I had time for tonight ;).
wking added a commit to wking/kubernetes-community that referenced this pull request Jun 20, 2018
@wking
*: Assorted internal-reference cleanups
ca74dc3 
This is mostly replacing
https://github.com/kubernetes/community/blob/master/... links with
relative links, because relative links are easier to maintain.  For
example, if you rename a.md to b.md in a feature branch, updating an
/a.md to /b.md target will work immediately (e.g. during pull-request
review), while updating
https://github.com/kubernetes/community/blob/master/a.md to
https://github.com/kubernetes/community/blob/master/b.md will only
work after your branch lands the rename in master.

I'm not sure why the #L1454 fragment was part of the old
sig-governance template sigs.yaml link, but it's been there since the
template landed in 68658bf (Provide short template for SIG
governance, 2018-02-23, kubernetes#1830).  I've removed it in this commit.

The Kubernetes Charter README link in the sig-governance template
could just be:

  [Kubernetes Charter README]: README.md

but I've based it on the project root and back to make life easier
on new SIGs which copy/paste the file to a new location in this
repository.

I personally prefer targets that use ../ for referencing other
directories within a project, because those also work with generic
Markdown tools (e.g. Emacs' Markdown mode).  I've gone with /-rooted
targets in this commit as requested in
/sig-contributor-experience/markdown-link-style-guide.md.

I've also chased a few files and anchors as they've moved around,
e.g. the OBSOLETE_templates.md rename from 18958f8 (addressing Brians
comments, 2017-09-06, kubernetes#1010) and the "and maintenance" header addition
from f471f6b (Add new contact info for Paris and me, 2017-10-17,

This commit isn't complete, but it's a step in the right direction and
all I had time for tonight ;).

The sig-list.md changes were generated automatically from the
generator/list.tmpl changes with:

  $ make generate
wking added a commit to wking/kubernetes-community that referenced this pull request Jun 20, 2018
@wking
*: Assorted internal-reference cleanups
4833c3c 
This is mostly replacing
https://github.com/kubernetes/community/blob/master/... links with
relative links, because relative links are easier to maintain.  For
example, if you rename a.md to b.md in a feature branch, updating an
/a.md to /b.md target will work immediately (e.g. during pull-request
review), while updating
https://github.com/kubernetes/community/blob/master/a.md to
https://github.com/kubernetes/community/blob/master/b.md will only
work after your branch lands the rename in master.

I'm not sure why the #L1454 fragment was part of the old
sig-governance template sigs.yaml link, but it's been there since the
template landed in 68658bf (Provide short template for SIG
governance, 2018-02-23, kubernetes#1830).  I've removed it in this commit.

The Kubernetes Charter README link in the sig-governance template
could just be:

  [Kubernetes Charter README]: README.md

but I've based it on the project root and back to make life easier
on new SIGs which copy/paste the file to a new location in this
repository.

I personally prefer targets that use ../ for referencing other
directories within a project, because those also work with generic
Markdown tools (e.g. Emacs' Markdown mode).  I've gone with /-rooted
targets in this commit as requested in
/sig-contributor-experience/markdown-link-style-guide.md.

I've also chased a few files and anchors as they've moved around,
e.g. the OBSOLETE_templates.md rename from 18958f8 (addressing Brians
comments, 2017-09-06, kubernetes#1010) and the "and maintenance" header addition
from f471f6b (Add new contact info for Paris and me, 2017-10-17,

This commit isn't complete, but it's a step in the right direction and
all I had time for tonight ;).

The sig-list.md changes were generated automatically from the
generator/list.tmpl changes with:

  $ make generate
wking added a commit to wking/kubernetes-community that referenced this pull request Jul 1, 2018
@wking
*: Assorted internal-reference cleanups
8e15a8d 
This is mostly replacing
https://github.com/kubernetes/community/blob/master/... links with
relative links, because relative links are easier to maintain.  For
example, if you rename a.md to b.md in a feature branch, updating an
/a.md to /b.md target will work immediately (e.g. during pull-request
review), while updating
https://github.com/kubernetes/community/blob/master/a.md to
https://github.com/kubernetes/community/blob/master/b.md will only
work after your branch lands the rename in master.

I'm not sure why the #L1454 fragment was part of the old
sig-governance template sigs.yaml link, but it's been there since the
template landed in 68658bf (Provide short template for SIG
governance, 2018-02-23, kubernetes#1830).  I've removed it in this commit.

The Kubernetes Charter README link in the sig-governance template
could just be:

  [Kubernetes Charter README]: README.md

but I've based it on the project root and back to make life easier
on new SIGs which copy/paste the file to a new location in this
repository.

I personally prefer targets that use ../ for referencing other
directories within a project, because those also work with generic
Markdown tools (e.g. Emacs' Markdown mode).  I've gone with /-rooted
targets in this commit as requested in
/sig-contributor-experience/markdown-link-style-guide.md.

I've also chased a few files and anchors as they've moved around,
e.g. the OBSOLETE_templates.md rename from 18958f8 (addressing Brians
comments, 2017-09-06, kubernetes#1010) and the "and maintenance" header addition
from f471f6b (Add new contact info for Paris and me, 2017-10-17,

This commit isn't complete, but it's a step in the right direction and
all I had time for tonight ;).

The sig-list.md changes were generated automatically from the
generator/list.tmpl changes with:

  $ make generate
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@tpepper tpepper tpepper left review comments

@bgrant0607 bgrant0607 bgrant0607 left review comments

@timothysc timothysc timothysc approved these changes

@jbeda jbeda Awaiting requested review from jbeda

@philips philips Awaiting requested review from philips

Assignees

@bgrant0607 bgrant0607

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. committee/steering Denotes an issue or PR intended to be handled by the steering committee. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
7 participants
@pwittrock @philips @bgrant0607 @k8s-ci-robot @timothysc @tpepper @k8s-github-robot