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.

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

SIG-scalability charter. #1607

Closed
wants to merge 1 commit into
base: master
from

Conversation

Projects
None yet
9 participants
@porridge
Member

porridge commented Jan 15, 2018

SIG-scalability leads:
/cc @wojtek-t @countspongebob
Steering committee representatives:
/cc @thockin @smarterclayton @spiffxp

Marcin Owsiany
@k8s-ci-robot

This comment has been minimized.

Contributor

k8s-ci-robot commented Jan 15, 2018

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: porridge
We suggest the following additional approver: wojtek-t

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

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

Needs approval from an approver in each of these OWNERS Files:

You can indicate your approval by writing /approve in a comment
You can cancel your approval by writing /approve cancel in a comment

@countspongebob

This looks like a good update, and LGTM. However, we should have some discussion about how to interact with people with small amounts of time to contribute.

@thockin

This comment has been minimized.

Member

thockin commented Jan 19, 2018

lgtm

@wojtek-t

This comment has been minimized.

Member

wojtek-t commented Jan 19, 2018

LGTM

@countspongebob - I agree that we may be able to tweak it in the future, but I think it's great starting point.

@porridge

This comment has been minimized.

Member

porridge commented Jan 23, 2018

@wojtek-t

This comment has been minimized.

Member

wojtek-t commented Jan 23, 2018

@bgrant0607 @jdumars - FYI if you have any suggestions

@porridge

This comment has been minimized.

Member

porridge commented Feb 13, 2018

@smarterclayton @spiffxp please comment
This is my last week working on kubernetes, so I'd like to get this submitted.

@spiffxp

This comment has been minimized.

Member

spiffxp commented Feb 13, 2018

Things that are missing from the charter:

  • what are the responsibilities of your SIG leads?
  • what process do you use to change SIG leadership?
  • what code do you own?

I'm not a fan of blocking the entire queue, but I guess I'm fighting a losing battle here.

@porridge

This comment has been minimized.

Member

porridge commented Feb 14, 2018

These are very good questions, none of which I know answers to.
@shyamjvs @wojtek-t @countspongebob can you comment on the above?
@wasylkowski-a FYI we'll probably need a new owner for this PR since it's unlikely we will be able to find an agreed upon answer to this question, get the final approvals and get it merged in the remaining 3 days.

@wasylkowski-a

This comment has been minimized.

wasylkowski-a commented Feb 14, 2018

Re. the PR I will take it over if needed, but let's discuss the course of action offline.

@bgrant0607

This comment has been minimized.

Member

bgrant0607 commented Feb 15, 2018

FYI, we're working on a SIG charter template here:
#1650

It's still missing things like scope of the SIG.

Please also make sure your subprojects are correctly identified in https://github.com/kubernetes/community/blob/master/sigs.yaml

@wasylkowski-a

This comment has been minimized.

wasylkowski-a commented Feb 21, 2018

I have created a copy (#1829) where we should continue given that this PR will not be updated anymore (see @porridge's comment).

@bgrant0607

This comment has been minimized.

Member

bgrant0607 commented Feb 28, 2018

@porridge porridge closed this Mar 10, 2018

@porridge porridge deleted the porridge:charter branch Mar 10, 2018

@wojtek-t

This comment has been minimized.

Member

wojtek-t commented May 14, 2018

I've openede #2149 as a replacement.

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