Skip to content
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

Add sig-ibmcloud Charter #2555

Merged
merged 2 commits into from
Sep 21, 2018
Merged

Conversation

spzala
Copy link
Member

@spzala spzala commented Aug 18, 2018

Add charter for IBMCloud SIG. This PR is reviewed and discussed in the SIG meeting.

@k8s-ci-robot k8s-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Aug 18, 2018
@k8s-ci-robot k8s-ci-robot added the area/provider/ibmcloud Issues or PRs related to ibmcloud provider label Aug 18, 2018
@spzala
Copy link
Member Author

spzala commented Aug 18, 2018

/hold
Need to hold because specific reviewers are not assigned for the SIG yet.
/cc @spiffxp @duglin @bradtopol

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

This SIG adheres to the Roles and Organization Management outlined in [sig-governance]
and opts-in to updates and modifications to [sig-governance], with exception that the SIG only
have Chair role at present.
Copy link

@duglin duglin Aug 18, 2018

Choose a reason for hiding this comment

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

s/have/has the /

Copy link
Member

@idvoretskyi idvoretskyi left a comment

Choose a reason for hiding this comment

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

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Aug 18, 2018
Add charter for IBMCloud SIG.
@spzala spzala force-pushed the sigibmcloudcharter branch from 4eca286 to e38904b Compare August 19, 2018 21:14
@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Aug 19, 2018
@duglin
Copy link

duglin commented Aug 20, 2018

/approve

@duglin
Copy link

duglin commented Aug 20, 2018

/assign @idvoretskyi

Copy link
Member

@idvoretskyi idvoretskyi left a comment

Choose a reason for hiding this comment

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

/approve

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 20, 2018
@spiffxp
Copy link
Member

spiffxp commented Aug 20, 2018

/committee steering

@k8s-ci-robot k8s-ci-robot added the committee/steering Denotes an issue or PR intended to be handled by the steering committee. label Aug 20, 2018
Copy link
Member

@spiffxp spiffxp left a comment

Choose a reason for hiding this comment

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

This needs to be fleshed out more. We don't yet have an individual cloud provider sig charter merged, but SIG VMWare's PR is quite close. I would also want to see specifically how you compare and contrast with SIG Cloud Provider

The IBMCloud SIG enables activities and discussion around building, deploying, maintaining, supporting,
and using Kubernetes, and related CNCF projects, on IBM Public and Private Clouds.

The authoritative source for SIG information is the [SIG README] file.
Copy link
Member

Choose a reason for hiding this comment

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

Nope, please list it here. Your README is barren as far as scope. Specifically, please list:

  • Code, Binaries, Services
  • Cross-cutting and Externally Facing Processes

Copy link
Member Author

Choose a reason for hiding this comment

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

We don't have code repos etc yet as I mentioned in another comment as well, but creating provider repo is a work in progress right now and we will be updating charter once it happens. I think we can safely remove the line mentioning README, and will do it. Thanks!

Copy link
Member

@spiffxp spiffxp Sep 4, 2018

Choose a reason for hiding this comment

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

I would look to SIG VMWare's in-flight charter for some prior art here, with the caveat that I currently have some unaddressed nits there. I think they do a good job of taking ownership of community management and best practices in a way that articulates some artifacts and processes.

Copy link
Member Author

Choose a reason for hiding this comment

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

Yup, agree that it's nicely written. I will try elaborate on scope. Thanks!!

and opts-in to updates and modifications to [sig-governance], with exception that the SIG only
has the Chair role at present.

- SIG meets every other week on Zoom at 2 PM ET on Wednesday.
Copy link
Member

Choose a reason for hiding this comment

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

Out of scope for the charter doc

Copy link
Member Author

Choose a reason for hiding this comment

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

I am fine removing it but I used some of the already merged charter as reference and charters like sig-azure, cloud-provider, service-catalog (https://github.com/kubernetes/community/blob/master/sig-service-catalog/charter.md) have a similar addition. Also, as most SIGs charter (and charter template) has reference to the sig-governance (https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md) where it has a similar mention on meeting schedule, so my understanding was in the charter we provide a concise meeting detail etc. Again, I am fine to remove it if we decide so. Thanks!

Copy link
Member

Choose a reason for hiding this comment

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

You managed to pick as prior art three charters that merged either without much SC review, or before we got stricter about sticking to a common template. We plan on ensuring those change to match the template.

You can check kubernetes/steering#31 to see more info

That you meet regularly is an expectation that doesn't need to be spelled out here. When and how should be spelled out in sigs.yaml

Copy link
Member Author

Choose a reason for hiding this comment

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

Ah, LOL, OK sounds good to me 👍


This SIG adheres to the Roles and Organization Management outlined in [sig-governance]
and opts-in to updates and modifications to [sig-governance], with exception that the SIG only
has the Chair role at present.
Copy link
Member

Choose a reason for hiding this comment

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

Does this mean there are no duties for a Tech Lead to perform? Or that the Chair satisfies the duties of Tech Lead?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes, the chair role satisfies the duties as of today. We don't have code repo etc yet but once we have we will rethink on adding Tech lead role. Hope makes sense.

Copy link
Member

Choose a reason for hiding this comment

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

Can add a sentence stating this explicitly? eg: "Chairs must also fulfill all of the responsibilities of the Tech Lead role as outlined in [sig-governance]" (with a link)

Copy link
Member Author

Choose a reason for hiding this comment

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

Yup, absolutely, will do!

[here](https://goo.gl/PSkwBj).
- SIG mailing list link
[here](https://goo.gl/hUF9eF).

Copy link
Member

Choose a reason for hiding this comment

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

You're missing the section on Subproject Creation.

Copy link
Member Author

Choose a reason for hiding this comment

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

We don't have any subproject yet so it's not mentioned. I am fine if it's good to add a section with none for now? Thanks!

Copy link
Member

Choose a reason for hiding this comment

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

This is about documenting the process you will follow when you make a subproject. You need to choose an option from the template:

  • Option 1: by SIG Technical Leads
  • Option 2: by Federation of Subprojects

Also, I'm not entirely sure how on board I am with the notion of a SIG that owns no artifacts within this project. I guess I can find no prior art for this expectation other than "areas the SIG is responsible for directing and maintaining"

Is there code you own? Are there docs?

Copy link
Member Author

Choose a reason for hiding this comment

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

I see, I thought it's something related to existing sub projects. We don't have one yet but we have discussed this in SIG. We have provider code but not yet public and it's WIP to have a pubic repo. Thanks!

Copy link
Member Author

@spzala spzala left a comment

Choose a reason for hiding this comment

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

@spiffxp Aaron, hi, thanks so much for the review and comments. I have answered your comments inline.

@spiffxp
Copy link
Member

spiffxp commented Sep 11, 2018

Ping, any updates on this?

@spzala
Copy link
Member Author

spzala commented Sep 12, 2018

@spiffxp hello, sorry I was OOO, just created second commit. Thanks!

Add charter for IBMCloud SIG.

The work to have a cloud provider specific public code repository is in progress. This section will be updated once the work is complete. Kubernetes upstream code that
is directly related to IKS or ICP issues or features can be discussed.

Copy link
Member

Choose a reason for hiding this comment

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

You're missing the "Cross-cutting and Externally Facing Processes" section. I assume this means you have none.

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes, you got it right :) Thanks!

@spiffxp
Copy link
Member

spiffxp commented Sep 17, 2018

/lgtm
That said, this looks really light. There are currently 5 other SIGs that have no subprojects listed, so you're not alone on this, but I anticipate we'll want to resolve this down the line.

/assign @derekwaynecarr
you're the other steering committee member for this

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Sep 17, 2018
@spzala
Copy link
Member Author

spzala commented Sep 17, 2018

@spiffxp, thanks Aaron!! Yes, agree, we should have one or more in future as we work on open sourcing the provider code.

has the Chair role at present. Chairs must also fulfill all of the responsibilities of the Tech Lead role as outlined in [sig-governance].

### Subproject Creation
Associated subprojects are created following the `by SIG Technical Leads` option procedure described in [sig-governance].
Copy link
Member

Choose a reason for hiding this comment

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

nit: you can just say "SIG Technical Leads" in this section.

as an example: https://github.com/kubernetes/community/pull/2462/files#diff-ddf39acdb13e6743dcb3d690a0a68f96R60

Copy link
Member

Choose a reason for hiding this comment

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

i assume creation of subprojects will also be impacted by changes in "code, binaries, services" discussion.

@derekwaynecarr
Copy link
Member

I do not have a great sense on the scope of subprojects that could potentially be sponsored by this sig since there really are none yet. i would like to revisit this in the future once the code, binaries, and services section is better fleshed out. i agree w/ aaron that we can resolve this down the line.

/hold cancel
/lgtm
/approve

@k8s-ci-robot k8s-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 21, 2018
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: derekwaynecarr, duglin, idvoretskyi

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 merged commit 9b9420e into kubernetes:master Sep 21, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/provider/ibmcloud Issues or PRs related to ibmcloud provider 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/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants