Skip to content

Conversation

@spiffxp
Copy link
Contributor

@spiffxp spiffxp commented Jan 24, 2018

Initial implementation of #1673

A subproject is a one-to-many mapping of a name to a list of
OWNERS urls. This allows for a subproject to be a single repo (eg:
helm), or a subproject to be a list of multiple subdirectories across
one or more repos (eg: workloads api)

Strawman assignment of single repo subprojects per an initial mapping
from @bgrant0607

@k8s-ci-robot k8s-ci-robot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Jan 24, 2018
@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 24, 2018
@k8s-github-robot k8s-github-robot added sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/apps Categorizes an issue or PR as relevant to SIG Apps. sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. sig/autoscaling Categorizes an issue or PR as relevant to SIG Autoscaling. ug/big-data Categorizes an issue or PR as relevant to ug-big-data. sig/cli Categorizes an issue or PR as relevant to SIG CLI. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience. sig/docs Categorizes an issue or PR as relevant to SIG Docs. sig/instrumentation Categorizes an issue or PR as relevant to SIG Instrumentation. sig/multicluster Categorizes an issue or PR as relevant to SIG Multicluster. labels Jan 24, 2018
@k8s-ci-robot k8s-ci-robot added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. and removed size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Jan 31, 2018
@spiffxp spiffxp force-pushed the sig-ownership-strawman branch 2 times, most recently from a014965 to cfe4fc9 Compare January 31, 2018 23:57
@spiffxp
Copy link
Contributor Author

spiffxp commented Feb 1, 2018

kubernetes-dev thread

I will merge Tuesday Feb 6th if there are no objections or comments that can't be properly addressed

@spiffxp spiffxp force-pushed the sig-ownership-strawman branch from 97aac1f to 9058070 Compare February 1, 2018 20:51
|[Scheduling](sig-scheduling/README.md)|scheduling|* [Bobby (Babak) Salamat](https://github.com/bsalamat), Google<br>* [Timothy St. Clair](https://github.com/timothysc), Heptio<br>|* [Slack](https://kubernetes.slack.com/messages/sig-scheduling)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-scheduling)|* Regular SIG Meeting: [Thursdays at 20:00 UTC (biweekly)](https://zoom.us/j/7767391691)<br>
|[Service Catalog](sig-service-catalog/README.md)|service-catalog|* [Paul Morie](https://github.com/pmorie), Red Hat<br>* [Aaron Schlesinger](https://github.com/arschles), Microsoft<br>* [Ville Aikas](https://github.com/vaikas-google), Google<br>* [Doug Davis](https://github.com/duglin), IBM<br>|* [Slack](https://kubernetes.slack.com/messages/sig-service-catalog)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-service-catalog)|* Regular SIG Meeting: [Mondays at 20:00 UTC (weekly)](https://zoom.us/j/7201225346)<br>
|[Storage](sig-storage/README.md)|storage|* [Saad Ali](https://github.com/saad-ali), Google<br>* [Bradley Childs](https://github.com/childsb), Red Hat<br>|* [Slack](https://kubernetes.slack.com/messages/sig-storage)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-storage)|* Regular SIG Meeting: [Thursdays at 9:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/614261834)<br>
|[Testing](sig-testing/README.md)|testing|* [Aaron Crickenberger](https://github.com/spiffxp), Samsung SDS<br>* [Erick Feja](https://github.com/fejta), Google<br>* [Steve Kuznetsov](https://github.com/stevekuznetsov), Red Hat<br>* [Timothy St. Clair](https://github.com/timothysc), Heptio<br>|* [Slack](https://kubernetes.slack.com/messages/sig-testing)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-testing)|* Regular SIG Meeting: [Tuesdays at 13:00 PT (Pacific Time) (weekly)](https://zoom.us/my/k8s.sig.testing)<br>* Testing Commons: [Wednesdays at 07:30 PT (Pacific Time) (bi-weekly)](https://zoom.us/my/k8s.sig.testing)<br>
Copy link
Member

Choose a reason for hiding this comment

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

Should subproject meetings be listed in sig-list.md?

Copy link
Member

@bgrant0607 bgrant0607 left a comment

Choose a reason for hiding this comment

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

Good start, thanks!

I see subprojects in the kubernetes repo are mostly missing. I commented on some, but there are more we'll need to add, such as more code in pkg/registry and tests in kubernetes/tests.

SIG Auth includes RBAC and other auth plugins.

- **api**
- Owners:
- https://raw.githubusercontent.com/kubernetes/api/master/OWNERS
- **apiextensions-apiserver**
Copy link
Member

Choose a reason for hiding this comment

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

Subproject CRD

- **apiextensions-apiserver**
- Owners:
- https://raw.githubusercontent.com/kubernetes/apiextensions-apiserver/master/OWNERS
- **apimachinery**
Copy link
Member

Choose a reason for hiding this comment

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

I'd group these 3 under the apiserver subproject. Conversion should really only run in the apiserver. But I could see an argument for grouping apimachinery with gengo.

It's worth getting input from @kubernetes/sig-api-machinery-api-reviews how they'd group them.

- **apiserver-builder**
- Owners:
- https://raw.githubusercontent.com/kubernetes-incubator/apiserver-builder/master/OWNERS
- **client-go**
Copy link
Member

Choose a reason for hiding this comment

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

I'd group all the clients under a client library (or client SDK) subproject.

- **gen**
- Owners:
- https://raw.githubusercontent.com/kubernetes-client/gen/master/OWNERS
- **gengo**
Copy link
Member

Choose a reason for hiding this comment

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

I'd include gengo in an "IDL" subproject.

- **javascript**
- Owners:
- https://raw.githubusercontent.com/kubernetes-client/javascript/master/OWNERS
- **kube-aggregator**
Copy link
Member

Choose a reason for hiding this comment

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

API Aggregation subproject

## Subprojects

The following subprojects are owned by this SIG:
- **perf-tests**
Copy link
Member

Choose a reason for hiding this comment

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


## Subprojects

The following subprojects are owned by this SIG:
Copy link
Member

Choose a reason for hiding this comment

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


## Subprojects

The following subprojects are owned by this SIG:
Copy link
Member

Choose a reason for hiding this comment

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

## Subprojects

The following subprojects are owned by this SIG:
- **test-infra**
Copy link
Member

Choose a reason for hiding this comment

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

What about test infra in the kubernetes repo, such as parts of https://github.com/kubernetes/kubernetes/tree/master/test/e2e?

## Subprojects

The following subprojects are owned by this SIG:
- **dashboard**
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 sig-ui rather than sig-windows

@k8s-ci-robot k8s-ci-robot added the kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API label Feb 6, 2018
@k8s-github-robot k8s-github-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 6, 2018
- name: rudder-federation
owners:
- https://raw.githubusercontent.com/kubernetes-helm/rudder-federation/master/OWNERS
- name: workloads-api
Copy link
Contributor

Choose a reason for hiding this comment

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

jobs and cronjobs should also be here.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done, I updated the description and added the OWNERS files for the controllers and the batch api

@spiffxp spiffxp force-pushed the sig-ownership-strawman branch from 9058070 to f39a792 Compare February 7, 2018 14:58
@k8s-github-robot k8s-github-robot added sig/ui Categorizes an issue or PR as relevant to SIG UI. and removed needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels Feb 7, 2018
@spiffxp spiffxp force-pushed the sig-ownership-strawman branch from f39a792 to 4764a89 Compare February 7, 2018 16:27
@spiffxp
Copy link
Contributor Author

spiffxp commented Feb 7, 2018

I will take a crack at adding the subproject meetings to sig-list.md later today but honestly I think the formatting on that page needs to be re-thought and I don't want to play with it too much in this PR.

A subproject is a one-to-many mapping of a name to a list of
OWNERS urls.  This allows for a subproject to be a single repo (eg:
helm), or a subproject to be a list of multiple subdirectories across
one or more repos (eg: workloads api)

SIG meetings dedicated to a single subproject moved down to subproject
meetings
@spiffxp spiffxp force-pushed the sig-ownership-strawman branch from 4764a89 to ecd88cf Compare February 7, 2018 23:25
@spiffxp
Copy link
Contributor Author

spiffxp commented Feb 7, 2018

/hold cancel
ready for /lgtm

@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 Feb 7, 2018
@bgrant0607
Copy link
Member

Awesome. Merge and iterate. In the next attempt, I can try to enumerate more of the subprojects in the kubernetes repo.

/lgtm

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

[APPROVALNOTIFIER] This PR is APPROVED

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

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 OWNERS 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 6a4220c into kubernetes:master Feb 7, 2018
- **crd**
- Owners:
- https://raw.githubusercontent.com/kubernetes/apiextensions-apiserver/master/OWNERS
- **gen**
Copy link
Member

Choose a reason for hiding this comment

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

Is this gengo?

Copy link
Member

Choose a reason for hiding this comment

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

No, that's IDL, below

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. 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. kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API lgtm "Looks good to me", indicates that a PR is ready to be merged. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/apps Categorizes an issue or PR as relevant to SIG Apps. sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. sig/autoscaling Categorizes an issue or PR as relevant to SIG Autoscaling. sig/cli Categorizes an issue or PR as relevant to SIG CLI. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience. sig/docs Categorizes an issue or PR as relevant to SIG Docs. sig/instrumentation Categorizes an issue or PR as relevant to SIG Instrumentation. sig/multicluster Categorizes an issue or PR as relevant to SIG Multicluster. sig/network Categorizes an issue or PR as relevant to SIG Network. sig/node Categorizes an issue or PR as relevant to SIG Node. sig/release Categorizes an issue or PR as relevant to SIG Release. sig/scalability Categorizes an issue or PR as relevant to SIG Scalability. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. sig/service-catalog Categorizes an issue or PR as relevant to SIG Service Catalog. sig/storage Categorizes an issue or PR as relevant to SIG Storage. sig/testing Categorizes an issue or PR as relevant to SIG Testing. sig/ui Categorizes an issue or PR as relevant to SIG UI. sig/windows Categorizes an issue or PR as relevant to SIG Windows. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. ug/big-data Categorizes an issue or PR as relevant to ug-big-data.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

10 participants