From 2cec35b2f05a3a56ef784cfc041e5e97c3a82ff8 Mon Sep 17 00:00:00 2001 From: Bob Killen Date: Mon, 2 May 2022 11:35:45 -0500 Subject: Archive SIG Service Catalog --- OWNERS_ALIASES | 2 - archive/sig-service-catalog/OWNERS | 8 + archive/sig-service-catalog/README.md | 69 +++++++++ archive/sig-service-catalog/annual-report-2021.md | 143 ++++++++++++++++++ archive/sig-service-catalog/charter.md | 169 ++++++++++++++++++++++ liaisons.md | 1 - sig-list.md | 1 - sig-service-catalog/OWNERS | 8 - sig-service-catalog/README.md | 69 --------- sig-service-catalog/annual-report-2021.md | 143 ------------------ sig-service-catalog/charter.md | 169 ---------------------- sigs.yaml | 72 --------- 12 files changed, 389 insertions(+), 465 deletions(-) create mode 100644 archive/sig-service-catalog/OWNERS create mode 100644 archive/sig-service-catalog/README.md create mode 100644 archive/sig-service-catalog/annual-report-2021.md create mode 100644 archive/sig-service-catalog/charter.md delete mode 100644 sig-service-catalog/OWNERS delete mode 100644 sig-service-catalog/README.md delete mode 100644 sig-service-catalog/annual-report-2021.md delete mode 100644 sig-service-catalog/charter.md diff --git a/OWNERS_ALIASES b/OWNERS_ALIASES index f139a120..4622c4cc 100644 --- a/OWNERS_ALIASES +++ b/OWNERS_ALIASES @@ -85,8 +85,6 @@ aliases: sig-security-leads: - IanColdwater - tabbysable - sig-service-catalog-leads: - - jhvhs sig-storage-leads: - jsafrane - msau42 diff --git a/archive/sig-service-catalog/OWNERS b/archive/sig-service-catalog/OWNERS new file mode 100644 index 00000000..a4884d4d --- /dev/null +++ b/archive/sig-service-catalog/OWNERS @@ -0,0 +1,8 @@ +# See the OWNERS docs at https://go.k8s.io/owners + +reviewers: + - sig-service-catalog-leads +approvers: + - sig-service-catalog-leads +labels: + - sig/service-catalog diff --git a/archive/sig-service-catalog/README.md b/archive/sig-service-catalog/README.md new file mode 100644 index 00000000..d1460d0e --- /dev/null +++ b/archive/sig-service-catalog/README.md @@ -0,0 +1,69 @@ + +# Service Catalog Special Interest Group + +Service Catalog is a Kubernetes extension project that implements the [Open Service Broker API](https://www.openservicebrokerapi.org/) (OSBAPI). It allows application developers the ability to provision and consume cloud services natively from within Kubernetes. + +The [charter](charter.md) defines the scope and governance of the Service Catalog Special Interest Group. + +## Meetings +*Joining the [mailing list](https://groups.google.com/forum/#!forum/kubernetes-sig-service-catalog) for the group will typically add invites for the following meetings to your calendar.* +* Regular SIG Meeting: [Mondays at 10:00 PT (Pacific Time)](https://zoom.us/j/7201225346) (biweekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=10:00&tz=PT%20%28Pacific%20Time%29). + * [Meeting notes and Agenda](https://docs.google.com/document/d/17xlpkoEbPR5M6P5VDzNx17q6-IPFxKyebEekCGYiIKM/edit). + * [Meeting recordings](https://www.youtube.com/watch?v=ukPj1sFFkr0&list=PL69nYSiGNLP2k9ZXx9E1MvRSotFDoHUWs). + +## Leadership + +### Chairs +The Chairs of the SIG run operations and processes governing the SIG. + +* Konstantin Semenov (**[@jhvhs](https://github.com/jhvhs)**), VMware + +## Emeritus Leads + +* Aaron Schlesinger (**[@arschles](https://github.com/arschles)**) +* Carolyn Van Slyck (**[@carolynvs](https://github.com/carolynvs)**) +* Doug Davis (**[@duglin](https://github.com/duglin)**) +* Jonathan Berkhahn (**[@jberkhahn](https://github.com/jberkhahn)**) +* Jay Boyd (**[@jboyd01](https://github.com/jboyd01)**) +* Michael Kibbe (**[@kibbles-n-bytes](https://github.com/kibbles-n-bytes)**) +* Mateusz Szostok (**[@mszostok](https://github.com/mszostok)**) +* Paul Morie (**[@pmorie](https://github.com/pmorie)**) +* Ville Aikas (**[@vaikas-google](https://github.com/vaikas-google)**) + +## Contact +- Slack: [#sig-service-catalog](https://kubernetes.slack.com/messages/sig-service-catalog) +- [Mailing list](https://groups.google.com/forum/#!forum/kubernetes-sig-service-catalog) +- [Open Community Issues/PRs](https://github.com/kubernetes/community/labels/sig%2Fservice-catalog) +- GitHub Teams: + - [@kubernetes/sig-service-catalog-api-reviews](https://github.com/orgs/kubernetes/teams/sig-service-catalog-api-reviews) - API Changes and Reviews + - [@kubernetes/sig-service-catalog-bugs](https://github.com/orgs/kubernetes/teams/sig-service-catalog-bugs) - Bug Triage and Troubleshooting + - [@kubernetes/sig-service-catalog-feature-requests](https://github.com/orgs/kubernetes/teams/sig-service-catalog-feature-requests) - Feature Requests + - [@kubernetes/sig-service-catalog-misc](https://github.com/orgs/kubernetes/teams/sig-service-catalog-misc) - General Discussion + - [@kubernetes/sig-service-catalog-pr-reviews](https://github.com/orgs/kubernetes/teams/sig-service-catalog-pr-reviews) - PR Reviews + - [@kubernetes/sig-service-catalog-proposals](https://github.com/orgs/kubernetes/teams/sig-service-catalog-proposals) - Design Proposals + - [@kubernetes/sig-service-catalog-test-failures](https://github.com/orgs/kubernetes/teams/sig-service-catalog-test-failures) - Test Failures and Triage +- Steering Committee Liaison: Bob Killen (**[@mrbobbytables](https://github.com/mrbobbytables)**) + +## Subprojects + +The following [subprojects][subproject-definition] are owned by sig-service-catalog: +### minibroker +- **Owners:** + - [kubernetes-sigs/minibroker](https://github.com/kubernetes-sigs/minibroker/blob/master/OWNERS) +### service-catalog +- **Owners:** + - [kubernetes-sigs/go-open-service-broker-client](https://github.com/kubernetes-sigs/go-open-service-broker-client/blob/master/OWNERS) + - [kubernetes-sigs/service-catalog](https://github.com/kubernetes-sigs/service-catalog/blob/master/OWNERS) + +[subproject-definition]: https://github.com/kubernetes/community/blob/master/governance.md#subprojects +[working-group-definition]: https://github.com/kubernetes/community/blob/master/governance.md#working-groups + + + diff --git a/archive/sig-service-catalog/annual-report-2021.md b/archive/sig-service-catalog/annual-report-2021.md new file mode 100644 index 00000000..3ed71f98 --- /dev/null +++ b/archive/sig-service-catalog/annual-report-2021.md @@ -0,0 +1,143 @@ +# 2021 Annual Report: SIG Service Catalog + +## Current initiatives + +1. What work did the SIG do this year that should be highlighted? + + - + - + - + +2. What initiatives are you working on that aren't being tracked in KEPs? + + - + - + - + +3. KEP work in 2021 (1.x, 1.y, 1.z): + + + + - Stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - Beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - Alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - Pre-alpha + - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) + +## Project health + +1. What areas and/or subprojects does your group need the most help with? + Any areas with 2 or fewer OWNERs? (link to more details) + + - + - + - + +2. What metrics/community health stats does your group care about and/or measure? + + - + - + - + +3. Does your [CONTRIBUTING.md] help **new** contributors engage with your group specifically by pointing + to activities or programs that provide useful context or allow easy participation? + + - + +4. If your group has special training, requirements for reviewers/approvers, or processes beyond the general [contributor guide], + does your [CONTRIBUTING.md] document those to help **existing** contributors grow throughout the [contributor ladder]? + + - + +5. Does the group have contributors from multiple companies/affiliations? + + - + +6. Are there ways end users/companies can contribute that they currently are not? + If one of those ways is more full time support, what would they work on and why? + + - + - + +## Membership + +- Primary slack channel member count: +- Primary mailing list member count: +- Primary meeting attendee count (estimated, if needed): +- Primary meeting participant count (estimated, if needed): +- Unique reviewers for SIG-owned packages: +- Unique approvers for SIG-owned packages: + +Include any other ways you measure group membership + +## Subprojects + + + +New in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Retired in $YYYY: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +Continuing: +- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +- + +## Working groups + + + +New in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Retired in $YYYY: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +Continuing: +- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) +- + +## Operational + +Operational tasks in [sig-governance.md]: + +- [ ] [README.md] reviewed for accuracy and updated if needed +- [ ] [CONTRIBUTING.md] reviewed for accuracy and updated if needed + (or created if missing and your contributor steps and experience are different or more + in-depth than the documentation listed in the general [contributor guide] and [devel] folder.) +- [ ] Subprojects list and linked OWNERS files in [sigs.yaml] reviewed for accuracy and updated if needed +- [ ] SIG leaders (chairs, tech leads, and subproject owners) in [sigs.yaml] are accurate and active, and updated if needed +- [ ] Meeting notes and recordings for 2021 are linked from [README.md] and updated/uploaded if needed +- [ ] Did you have community-wide updates in 2021 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: + - + - + +[CONTRIBUTING.md]: https://git.k8s.io/community/sig-service-catalog/CONTRIBUTING.md +[contributor ladder]: https://git.k8s.io/community/community-membership.md +[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md +[README.md]: https://git.k8s.io/community/sig-service-catalog/README.md +[sigs.yaml]: https://git.k8s.io/community/sigs.yaml +[contributor guide]: https://git.k8s.io/community/contributors/guide/README.md +[devel]: https://git.k8s.io/community/contributors/devel/README.md + diff --git a/archive/sig-service-catalog/charter.md b/archive/sig-service-catalog/charter.md new file mode 100644 index 00000000..d9ed51cd --- /dev/null +++ b/archive/sig-service-catalog/charter.md @@ -0,0 +1,169 @@ +# SIG Service Catalog Charter + +This charter adheres to the conventions described in the [Kubernetes Charter +README](https://github.com/kubernetes/community/blob/master/committee-steering/governance/README.md). + +## Scope + +Service Catalog is a Kubernetes extension project that implements the [Open +Service Broker API](https://www.openservicebrokerapi.org/) (OSBAPI). It enables +application developers to provision cloud services from within Kubernetes and +integrates configuration and discovery of those services into Kubernetes +resources. + +### In scope + +See the [service-catalog SIG entry](https://github.com/kubernetes/community/tree/master/sig-service-catalog). + +This SIG’s main goals are: +- Support, and adhere to, the Platform requirements of the [OSBAPI + specification](https://github.com/openservicebrokerapi/servicebroker/blob/master/spec.md). +- Provide a UX for Kubernetes users that is consistent with both the OSB API + specification and traditional Kubernetes user interactions. +- Align with the OSBAPI specification as changes are made. +- Provide feedback (bugs or feature requests) to the [OSBAPI WG]](https://www.openservicebrokerapi.org/). + +### Code, Binaries and services + +- [Source Repository](https://github.com/kubernetes-sigs/service-catalog) + - See [OWNERS](https://raw.githubusercontent.com/kubernetes-sigs/service-catalog/master/OWNERS) for who has access. +- [Image Repository](https://quay.io/organization/kubernetes-service-catalog) + - Canary builds are published on pushes to master. + - Release builds (and latest) are published on tags. + - Chairs have access to manage this repository. +- [Helm Repository](https://kubernetes-sigs.github.io/service-catalog) + - Charts are automatically published as part of the release process. +- [svc-cat.io](https://svc-cat.io) + - Published on pushes to master. + - Site hosted with [Netlify](https://app.netlify.com/sites/svc-cat/overview). + - Chairs and interested maintainers have access to manage this site. +- [CLI Binary Hosting](https://svc-cat.io/docs/install/#manual) + - Canary builds are published on pushes to master. + - Release builds (and latest) are published on tags. + - Files hosted on Azure blob storage. + - Azure account managed by Carolyn Van Slyck (Microsoft) and Aaron Schlesinger + (Microsoft). +- [Travis](https://travis-ci.org/kubernetes-sigs/service-catalog) + - Runs the CI builds. + - Maintainers have access. +- [Jenkins](https://service-catalog-jenkins.appspot.com/) + - Runs end-to-end tests on a live cluster. + - Server managed by Michael Kibbe (Google). + +### Out of scope + +The following, non-exhaustive, items are out of scope: +- Operation of OSBAPI Service Brokers. + +## Roles +This SIG's charter deviates from the +[sig-governance](https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md) +roles. We do not have the Tech Lead role, and have a honorary Emeritus Chair role. + +- [Maintainers](https://github.com/orgs/kubernetes-sigs/teams/service-catalog-maintainers/members) + - Maintainer is equivalent to the standard [Kubernetes definition of + Approver](https://github.com/kubernetes/community/blob/master/community-membership.md#approver). + - Responsible for reviewing pull requests, and approving pull requests for merge. + - Responsible for technical planning and stewardship of the project. + - New maintainers may be nominated by another maintainer, and accepted via lazy + two-thirds resolution amongst the chairs. + - Maintainers may be nominated for removal from their position by a chair, + and accepted via lazy two-thirds resolution amongst the chairs. + - Maintainers may propose changes to this charter at any time, by submitting a + pull request and then notifying the SIG mailing list, to be accepted via + lazy two-thirds resolution amongst the chairs. + +- Chairs + - Chairs are expected to perform the role of maintainer, in addition to their chair responsibilities. + - Chairs are listed in our [SIG + definition](https://github.com/kubernetes/community/tree/master/sig-service-catalog#chairs). + - Responsible for project administration activities within the SIG and are + non-technical in nature, such as organizing the weekly meetings. + - A chair does not have more rights, or votes, than a maintainer. + - Responsible for reporting the SIG’s status to the appropriate Kubernetes + leadership teams. + - All decisions amongst chairs are made using lazy consensus with a fallback + to a 2/3 majority vote (lazy two-thirds resolution). + This process is used for all decisions, such as changing chairs/maintainers + or modifying this charter. + - Chairs may nominate a new chair at any time, to be accepted via lazy + two-thirds resolution amongst the chairs. + - Chairs may decide to step down at any time. + - Chairs must remain active in the role and may be removed from the position + via lazy two-thirds resolution amongst the chairs, if they are unresponsive + for > 3 months or are not proactively working with other chairs to fulfill + responsibilities. + - There is no set number of Chairs. + +- Emeritus Chairs ([Inspired by the Helm + Project](http://technosophos.com/2018/01/11/introducing-helm-emeritus-core-maintainers.html)) + - A chair who steps down may choose to take an Emeritus Chair title. This + confers honor on the recipient and allows them to remain associated with the + SIG in acknowledgement of their significant contributions. + - Those who attain this title are no longer expected to attend the weekly + meetings, share in the issue queue triage rotation, vote on policy or + architectural issues, or review pull requests. + - They are [listed in our documentation](https://svc-cat.io/community/#leadership) + as Emeritus Chairs, and we will continue to invite them to participate in + related events, such as KubeCon. + +- Security Contacts + - Are a contact point for the Product Security Committee to reach out to for + triaging and handling of incoming issues. + - Must be a maintainer. + - Must accept and adhere to the Kubernetes [Embargo + Policy](https://git.k8s.io/security/private-distributors-list.md#embargo-policy). + - Defined in + [SECURITY_CONTACTS](https://github.com/kubernetes-sigs/service-catalog/blob/master/SECURITY_CONTACTS) + file. + +## Organizational management + +- SIG meets every week on Zoom at 1 PM PST on Mondays + - Agenda + [here](https://docs.google.com/document/d/17xlpkoEbPR5M6P5VDzNx17q6-IPFxKyebEekCGYiIKM/edit#). + - Anyone is free to add new agenda items to the doc. + - Recordings of the calls are made available [here](https://goo.gl/ZmLNX9). +- SIG members explicitly representing the group at conferences (SIG progress + reports, deep dives, etc.) should make their slides available for perusal and + feedback at least 2 week in advance. +- [Working + groups](https://github.com/kubernetes-sigs/service-catalog/wiki/Working-Groups) + can be initiated by any member. To create a new one, add the topic to the + weekly call’s agenda for discussion. + - These are not the same as cross-SIG working groups. + - Working groups exist for an unspecified period of time, so that interested + members can meet to discuss and solve problems for our SIG. + +### Project management +- [Milestones](https://github.com/kubernetes-sigs/service-catalog/milestones) + are defined by SIG maintainers. +- Anyone is free to request a discussion of the milestones/plans during + a weekly call. +- Weekly releases are typically done on Thursdays, and any member who has + maintainer rights is free to initiate it. _Friday releases are strongly + discouraged._ +- Major releases are planned and discussed among the SIG members during regular + weekly calls. +- The release process is defined + [here](https://github.com/kubernetes-sigs/service-catalog/wiki/Release-Process). +- Anyone can request to work on an issue by commenting on it with `#dibs`. + + +### Technical processes +- All technical decisions are made either through issues, pull requests or + discussions during the weekly SIG meeting. Major decisions should be + documented in an issue or pull request. +- There is no requirement that all pull requests have an associated issue. + However, if the PR represents a significant design decision then it is + recommended that it be discussed among the group to avoid unnecessary coding + that might not be accepted. +- While everyone is encouraged to contribute to the discussion of any topic, + ultimately any changes made to the codebase must be approved by the + maintainers. +- Pull requests are required to have at least 2 maintainers approve them. +- Pull requests that are labeled with `do-not-merge/hold` or have an on-going + discussion must not be merged until all concerns are addressed. +- Disagreements are resolved via lazy consensus. In the event that a common + decision cannot be made, then a vote among the maintainers will be taken. + Simple majority of votes cast (>50%) wins. diff --git a/liaisons.md b/liaisons.md index 14889285..c50a88e8 100644 --- a/liaisons.md +++ b/liaisons.md @@ -49,7 +49,6 @@ members will assume one of the departing members groups. | [SIG Scalability](sig-scalability/README.md) | Bob Killen (**[@mrbobbytables](https://github.com/mrbobbytables)**) | | [SIG Scheduling](sig-scheduling/README.md) | Jordan Liggitt (**[@liggitt](https://github.com/liggitt)**) | | [SIG Security](sig-security/README.md) | Paris Pittman (**[@parispittman](https://github.com/parispittman)**) | -| [SIG Service Catalog](sig-service-catalog/README.md) | Bob Killen (**[@mrbobbytables](https://github.com/mrbobbytables)**) | | [SIG Storage](sig-storage/README.md) | Paris Pittman (**[@parispittman](https://github.com/parispittman)**) | | [SIG Testing](sig-testing/README.md) | Paris Pittman (**[@parispittman](https://github.com/parispittman)**) | | [SIG UI](sig-ui/README.md) | Stephen Augustus (**[@justaugustus](https://github.com/justaugustus)**) | diff --git a/sig-list.md b/sig-list.md index b2e6385a..d91bd86d 100644 --- a/sig-list.md +++ b/sig-list.md @@ -51,7 +51,6 @@ When the need arises, a [new SIG can be created](sig-wg-lifecycle.md) |[Scalability](sig-scalability/README.md)|[scalability](https://github.com/kubernetes/kubernetes/labels/sig%2Fscalability)|* [Marcel Zieba](https://github.com/marseel), Google
* [Shyam Jeedigunta](https://github.com/shyamjvs), AWS
|* [Slack](https://kubernetes.slack.com/messages/sig-scalability)
* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-scale)|* Regular SIG Meeting: [Thursdays at 10:30 PT (Pacific Time) (bi-weekly ([upcoming meeting dates](#upcoming-meeting-dates)))](https://zoom.us/j/94252896018?pwd=cTlMMlBoTHZqUEdjRm9VY2NWNUg5dz09)
|[Scheduling](sig-scheduling/README.md)|[scheduling](https://github.com/kubernetes/kubernetes/labels/sig%2Fscheduling)|* [Wei Huang](https://github.com/Huang-Wei), Apple
* [Abdullah Gharaibeh](https://github.com/ahg-g), Google
|* [Slack](https://kubernetes.slack.com/messages/sig-scheduling)
* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-scheduling)|* 10AM PT Meeting: [Thursdays at 17:00 UTC (biweekly starting Thursday June 7, 2018)](https://zoom.us/j/841218129)
|[Security](sig-security/README.md)|[security](https://github.com/kubernetes/kubernetes/labels/sig%2Fsecurity)|* [Ian Coldwater](https://github.com/IanColdwater), Twilio
* [Tabitha Sable](https://github.com/tabbysable), Datadog
|* [Slack](https://kubernetes.slack.com/messages/sig-security)
* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-security)|* Regular SIG Meeting: [Thursdays at 9:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/9934z1184192?pwd=L25Tc0ZOL3FqU09KNERlTU12dFhTQT09)
-|[Service Catalog](sig-service-catalog/README.md)|[service-catalog](https://github.com/kubernetes/kubernetes/labels/sig%2Fservice-catalog)|* [Konstantin Semenov](https://github.com/jhvhs), VMware
|* [Slack](https://kubernetes.slack.com/messages/sig-service-catalog)
* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-service-catalog)|* Regular SIG Meeting: [Mondays at 10:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/7201225346)
|[Storage](sig-storage/README.md)|[storage](https://github.com/kubernetes/kubernetes/labels/sig%2Fstorage)|* [Saad Ali](https://github.com/saad-ali), Google
* [Xing Yang](https://github.com/xing-yang), VMware
|* [Slack](https://kubernetes.slack.com/messages/sig-storage)
* [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)
|[Testing](sig-testing/README.md)|[testing](https://github.com/kubernetes/kubernetes/labels/sig%2Ftesting)|* [Benjamin Elder](https://github.com/BenTheElder), Google
* [Aaron Crickenberger](https://github.com/spiffxp), Google
* [Steve Kuznetsov](https://github.com/stevekuznetsov), Red Hat
|* [Slack](https://kubernetes.slack.com/messages/sig-testing)
* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-testing)|* SIG Testing Bi-Weekly Meeting: [Tuesdays at 10:00 PT (Pacific Time) (bi-weekly starting Tuesday August 13, 2019)](https://zoom.us/j/135450138?pwd=WGJyaVZzekJCWFBTMGJGTXVjUFJaUT09)
|[UI](sig-ui/README.md)|[ui](https://github.com/kubernetes/kubernetes/labels/sig%2Fui)|* [Sebastian Florek](https://github.com/floreks), Kubermatic
* [Marcin Maciaszczyk](https://github.com/maciaszczykm), Kubermatic
* [Shu Muto](https://github.com/shu-mutou), NEC
|* [Slack](https://kubernetes.slack.com/messages/sig-ui)
* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-ui)|* Regular SIG Meeting: [Thursdays at 09:00 PT (Pacific Time) (bi-weekly)](https://groups.google.com/forum/#!forum/kubernetes-sig-ui)
diff --git a/sig-service-catalog/OWNERS b/sig-service-catalog/OWNERS deleted file mode 100644 index a4884d4d..00000000 --- a/sig-service-catalog/OWNERS +++ /dev/null @@ -1,8 +0,0 @@ -# See the OWNERS docs at https://go.k8s.io/owners - -reviewers: - - sig-service-catalog-leads -approvers: - - sig-service-catalog-leads -labels: - - sig/service-catalog diff --git a/sig-service-catalog/README.md b/sig-service-catalog/README.md deleted file mode 100644 index d1460d0e..00000000 --- a/sig-service-catalog/README.md +++ /dev/null @@ -1,69 +0,0 @@ - -# Service Catalog Special Interest Group - -Service Catalog is a Kubernetes extension project that implements the [Open Service Broker API](https://www.openservicebrokerapi.org/) (OSBAPI). It allows application developers the ability to provision and consume cloud services natively from within Kubernetes. - -The [charter](charter.md) defines the scope and governance of the Service Catalog Special Interest Group. - -## Meetings -*Joining the [mailing list](https://groups.google.com/forum/#!forum/kubernetes-sig-service-catalog) for the group will typically add invites for the following meetings to your calendar.* -* Regular SIG Meeting: [Mondays at 10:00 PT (Pacific Time)](https://zoom.us/j/7201225346) (biweekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=10:00&tz=PT%20%28Pacific%20Time%29). - * [Meeting notes and Agenda](https://docs.google.com/document/d/17xlpkoEbPR5M6P5VDzNx17q6-IPFxKyebEekCGYiIKM/edit). - * [Meeting recordings](https://www.youtube.com/watch?v=ukPj1sFFkr0&list=PL69nYSiGNLP2k9ZXx9E1MvRSotFDoHUWs). - -## Leadership - -### Chairs -The Chairs of the SIG run operations and processes governing the SIG. - -* Konstantin Semenov (**[@jhvhs](https://github.com/jhvhs)**), VMware - -## Emeritus Leads - -* Aaron Schlesinger (**[@arschles](https://github.com/arschles)**) -* Carolyn Van Slyck (**[@carolynvs](https://github.com/carolynvs)**) -* Doug Davis (**[@duglin](https://github.com/duglin)**) -* Jonathan Berkhahn (**[@jberkhahn](https://github.com/jberkhahn)**) -* Jay Boyd (**[@jboyd01](https://github.com/jboyd01)**) -* Michael Kibbe (**[@kibbles-n-bytes](https://github.com/kibbles-n-bytes)**) -* Mateusz Szostok (**[@mszostok](https://github.com/mszostok)**) -* Paul Morie (**[@pmorie](https://github.com/pmorie)**) -* Ville Aikas (**[@vaikas-google](https://github.com/vaikas-google)**) - -## Contact -- Slack: [#sig-service-catalog](https://kubernetes.slack.com/messages/sig-service-catalog) -- [Mailing list](https://groups.google.com/forum/#!forum/kubernetes-sig-service-catalog) -- [Open Community Issues/PRs](https://github.com/kubernetes/community/labels/sig%2Fservice-catalog) -- GitHub Teams: - - [@kubernetes/sig-service-catalog-api-reviews](https://github.com/orgs/kubernetes/teams/sig-service-catalog-api-reviews) - API Changes and Reviews - - [@kubernetes/sig-service-catalog-bugs](https://github.com/orgs/kubernetes/teams/sig-service-catalog-bugs) - Bug Triage and Troubleshooting - - [@kubernetes/sig-service-catalog-feature-requests](https://github.com/orgs/kubernetes/teams/sig-service-catalog-feature-requests) - Feature Requests - - [@kubernetes/sig-service-catalog-misc](https://github.com/orgs/kubernetes/teams/sig-service-catalog-misc) - General Discussion - - [@kubernetes/sig-service-catalog-pr-reviews](https://github.com/orgs/kubernetes/teams/sig-service-catalog-pr-reviews) - PR Reviews - - [@kubernetes/sig-service-catalog-proposals](https://github.com/orgs/kubernetes/teams/sig-service-catalog-proposals) - Design Proposals - - [@kubernetes/sig-service-catalog-test-failures](https://github.com/orgs/kubernetes/teams/sig-service-catalog-test-failures) - Test Failures and Triage -- Steering Committee Liaison: Bob Killen (**[@mrbobbytables](https://github.com/mrbobbytables)**) - -## Subprojects - -The following [subprojects][subproject-definition] are owned by sig-service-catalog: -### minibroker -- **Owners:** - - [kubernetes-sigs/minibroker](https://github.com/kubernetes-sigs/minibroker/blob/master/OWNERS) -### service-catalog -- **Owners:** - - [kubernetes-sigs/go-open-service-broker-client](https://github.com/kubernetes-sigs/go-open-service-broker-client/blob/master/OWNERS) - - [kubernetes-sigs/service-catalog](https://github.com/kubernetes-sigs/service-catalog/blob/master/OWNERS) - -[subproject-definition]: https://github.com/kubernetes/community/blob/master/governance.md#subprojects -[working-group-definition]: https://github.com/kubernetes/community/blob/master/governance.md#working-groups - - - diff --git a/sig-service-catalog/annual-report-2021.md b/sig-service-catalog/annual-report-2021.md deleted file mode 100644 index 3ed71f98..00000000 --- a/sig-service-catalog/annual-report-2021.md +++ /dev/null @@ -1,143 +0,0 @@ -# 2021 Annual Report: SIG Service Catalog - -## Current initiatives - -1. What work did the SIG do this year that should be highlighted? - - - - - - - - -2. What initiatives are you working on that aren't being tracked in KEPs? - - - - - - - - -3. KEP work in 2021 (1.x, 1.y, 1.z): - - - - - Stable - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable - - Beta - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta - - Alpha - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha - - Pre-alpha - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - -## Project health - -1. What areas and/or subprojects does your group need the most help with? - Any areas with 2 or fewer OWNERs? (link to more details) - - - - - - - - -2. What metrics/community health stats does your group care about and/or measure? - - - - - - - - -3. Does your [CONTRIBUTING.md] help **new** contributors engage with your group specifically by pointing - to activities or programs that provide useful context or allow easy participation? - - - - -4. If your group has special training, requirements for reviewers/approvers, or processes beyond the general [contributor guide], - does your [CONTRIBUTING.md] document those to help **existing** contributors grow throughout the [contributor ladder]? - - - - -5. Does the group have contributors from multiple companies/affiliations? - - - - -6. Are there ways end users/companies can contribute that they currently are not? - If one of those ways is more full time support, what would they work on and why? - - - - - - -## Membership - -- Primary slack channel member count: -- Primary mailing list member count: -- Primary meeting attendee count (estimated, if needed): -- Primary meeting participant count (estimated, if needed): -- Unique reviewers for SIG-owned packages: -- Unique approvers for SIG-owned packages: - -Include any other ways you measure group membership - -## Subprojects - - - -New in $YYYY: -- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) -- - -Retired in $YYYY: -- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) -- - -Continuing: -- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) -- - -## Working groups - - - -New in $YYYY: -- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) -- - -Retired in $YYYY: -- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) -- - -Continuing: -- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) -- - -## Operational - -Operational tasks in [sig-governance.md]: - -- [ ] [README.md] reviewed for accuracy and updated if needed -- [ ] [CONTRIBUTING.md] reviewed for accuracy and updated if needed - (or created if missing and your contributor steps and experience are different or more - in-depth than the documentation listed in the general [contributor guide] and [devel] folder.) -- [ ] Subprojects list and linked OWNERS files in [sigs.yaml] reviewed for accuracy and updated if needed -- [ ] SIG leaders (chairs, tech leads, and subproject owners) in [sigs.yaml] are accurate and active, and updated if needed -- [ ] Meeting notes and recordings for 2021 are linked from [README.md] and updated/uploaded if needed -- [ ] Did you have community-wide updates in 2021 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: - - - - - -[CONTRIBUTING.md]: https://git.k8s.io/community/sig-service-catalog/CONTRIBUTING.md -[contributor ladder]: https://git.k8s.io/community/community-membership.md -[sig-governance.md]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md -[README.md]: https://git.k8s.io/community/sig-service-catalog/README.md -[sigs.yaml]: https://git.k8s.io/community/sigs.yaml -[contributor guide]: https://git.k8s.io/community/contributors/guide/README.md -[devel]: https://git.k8s.io/community/contributors/devel/README.md - diff --git a/sig-service-catalog/charter.md b/sig-service-catalog/charter.md deleted file mode 100644 index d9ed51cd..00000000 --- a/sig-service-catalog/charter.md +++ /dev/null @@ -1,169 +0,0 @@ -# SIG Service Catalog Charter - -This charter adheres to the conventions described in the [Kubernetes Charter -README](https://github.com/kubernetes/community/blob/master/committee-steering/governance/README.md). - -## Scope - -Service Catalog is a Kubernetes extension project that implements the [Open -Service Broker API](https://www.openservicebrokerapi.org/) (OSBAPI). It enables -application developers to provision cloud services from within Kubernetes and -integrates configuration and discovery of those services into Kubernetes -resources. - -### In scope - -See the [service-catalog SIG entry](https://github.com/kubernetes/community/tree/master/sig-service-catalog). - -This SIG’s main goals are: -- Support, and adhere to, the Platform requirements of the [OSBAPI - specification](https://github.com/openservicebrokerapi/servicebroker/blob/master/spec.md). -- Provide a UX for Kubernetes users that is consistent with both the OSB API - specification and traditional Kubernetes user interactions. -- Align with the OSBAPI specification as changes are made. -- Provide feedback (bugs or feature requests) to the [OSBAPI WG]](https://www.openservicebrokerapi.org/). - -### Code, Binaries and services - -- [Source Repository](https://github.com/kubernetes-sigs/service-catalog) - - See [OWNERS](https://raw.githubusercontent.com/kubernetes-sigs/service-catalog/master/OWNERS) for who has access. -- [Image Repository](https://quay.io/organization/kubernetes-service-catalog) - - Canary builds are published on pushes to master. - - Release builds (and latest) are published on tags. - - Chairs have access to manage this repository. -- [Helm Repository](https://kubernetes-sigs.github.io/service-catalog) - - Charts are automatically published as part of the release process. -- [svc-cat.io](https://svc-cat.io) - - Published on pushes to master. - - Site hosted with [Netlify](https://app.netlify.com/sites/svc-cat/overview). - - Chairs and interested maintainers have access to manage this site. -- [CLI Binary Hosting](https://svc-cat.io/docs/install/#manual) - - Canary builds are published on pushes to master. - - Release builds (and latest) are published on tags. - - Files hosted on Azure blob storage. - - Azure account managed by Carolyn Van Slyck (Microsoft) and Aaron Schlesinger - (Microsoft). -- [Travis](https://travis-ci.org/kubernetes-sigs/service-catalog) - - Runs the CI builds. - - Maintainers have access. -- [Jenkins](https://service-catalog-jenkins.appspot.com/) - - Runs end-to-end tests on a live cluster. - - Server managed by Michael Kibbe (Google). - -### Out of scope - -The following, non-exhaustive, items are out of scope: -- Operation of OSBAPI Service Brokers. - -## Roles -This SIG's charter deviates from the -[sig-governance](https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md) -roles. We do not have the Tech Lead role, and have a honorary Emeritus Chair role. - -- [Maintainers](https://github.com/orgs/kubernetes-sigs/teams/service-catalog-maintainers/members) - - Maintainer is equivalent to the standard [Kubernetes definition of - Approver](https://github.com/kubernetes/community/blob/master/community-membership.md#approver). - - Responsible for reviewing pull requests, and approving pull requests for merge. - - Responsible for technical planning and stewardship of the project. - - New maintainers may be nominated by another maintainer, and accepted via lazy - two-thirds resolution amongst the chairs. - - Maintainers may be nominated for removal from their position by a chair, - and accepted via lazy two-thirds resolution amongst the chairs. - - Maintainers may propose changes to this charter at any time, by submitting a - pull request and then notifying the SIG mailing list, to be accepted via - lazy two-thirds resolution amongst the chairs. - -- Chairs - - Chairs are expected to perform the role of maintainer, in addition to their chair responsibilities. - - Chairs are listed in our [SIG - definition](https://github.com/kubernetes/community/tree/master/sig-service-catalog#chairs). - - Responsible for project administration activities within the SIG and are - non-technical in nature, such as organizing the weekly meetings. - - A chair does not have more rights, or votes, than a maintainer. - - Responsible for reporting the SIG’s status to the appropriate Kubernetes - leadership teams. - - All decisions amongst chairs are made using lazy consensus with a fallback - to a 2/3 majority vote (lazy two-thirds resolution). - This process is used for all decisions, such as changing chairs/maintainers - or modifying this charter. - - Chairs may nominate a new chair at any time, to be accepted via lazy - two-thirds resolution amongst the chairs. - - Chairs may decide to step down at any time. - - Chairs must remain active in the role and may be removed from the position - via lazy two-thirds resolution amongst the chairs, if they are unresponsive - for > 3 months or are not proactively working with other chairs to fulfill - responsibilities. - - There is no set number of Chairs. - -- Emeritus Chairs ([Inspired by the Helm - Project](http://technosophos.com/2018/01/11/introducing-helm-emeritus-core-maintainers.html)) - - A chair who steps down may choose to take an Emeritus Chair title. This - confers honor on the recipient and allows them to remain associated with the - SIG in acknowledgement of their significant contributions. - - Those who attain this title are no longer expected to attend the weekly - meetings, share in the issue queue triage rotation, vote on policy or - architectural issues, or review pull requests. - - They are [listed in our documentation](https://svc-cat.io/community/#leadership) - as Emeritus Chairs, and we will continue to invite them to participate in - related events, such as KubeCon. - -- Security Contacts - - Are a contact point for the Product Security Committee to reach out to for - triaging and handling of incoming issues. - - Must be a maintainer. - - Must accept and adhere to the Kubernetes [Embargo - Policy](https://git.k8s.io/security/private-distributors-list.md#embargo-policy). - - Defined in - [SECURITY_CONTACTS](https://github.com/kubernetes-sigs/service-catalog/blob/master/SECURITY_CONTACTS) - file. - -## Organizational management - -- SIG meets every week on Zoom at 1 PM PST on Mondays - - Agenda - [here](https://docs.google.com/document/d/17xlpkoEbPR5M6P5VDzNx17q6-IPFxKyebEekCGYiIKM/edit#). - - Anyone is free to add new agenda items to the doc. - - Recordings of the calls are made available [here](https://goo.gl/ZmLNX9). -- SIG members explicitly representing the group at conferences (SIG progress - reports, deep dives, etc.) should make their slides available for perusal and - feedback at least 2 week in advance. -- [Working - groups](https://github.com/kubernetes-sigs/service-catalog/wiki/Working-Groups) - can be initiated by any member. To create a new one, add the topic to the - weekly call’s agenda for discussion. - - These are not the same as cross-SIG working groups. - - Working groups exist for an unspecified period of time, so that interested - members can meet to discuss and solve problems for our SIG. - -### Project management -- [Milestones](https://github.com/kubernetes-sigs/service-catalog/milestones) - are defined by SIG maintainers. -- Anyone is free to request a discussion of the milestones/plans during - a weekly call. -- Weekly releases are typically done on Thursdays, and any member who has - maintainer rights is free to initiate it. _Friday releases are strongly - discouraged._ -- Major releases are planned and discussed among the SIG members during regular - weekly calls. -- The release process is defined - [here](https://github.com/kubernetes-sigs/service-catalog/wiki/Release-Process). -- Anyone can request to work on an issue by commenting on it with `#dibs`. - - -### Technical processes -- All technical decisions are made either through issues, pull requests or - discussions during the weekly SIG meeting. Major decisions should be - documented in an issue or pull request. -- There is no requirement that all pull requests have an associated issue. - However, if the PR represents a significant design decision then it is - recommended that it be discussed among the group to avoid unnecessary coding - that might not be accepted. -- While everyone is encouraged to contribute to the discussion of any topic, - ultimately any changes made to the codebase must be approved by the - maintainers. -- Pull requests are required to have at least 2 maintainers approve them. -- Pull requests that are labeled with `do-not-merge/hold` or have an on-going - discussion must not be merged until all concerns are addressed. -- Disagreements are resolved via lazy consensus. In the event that a common - decision cannot be made, then a vote among the maintainers will be taken. - Simple majority of votes cast (>50%) wins. diff --git a/sigs.yaml b/sigs.yaml index 7ff39eea..87d921e2 100644 --- a/sigs.yaml +++ b/sigs.yaml @@ -2423,78 +2423,6 @@ sigs: slack: sig-security owners: - https://raw.githubusercontent.com/kubernetes/sig-security/master/OWNERS -- dir: sig-service-catalog - name: Service Catalog - mission_statement: > - Service Catalog is a Kubernetes extension project that implements the [Open Service - Broker API](https://www.openservicebrokerapi.org/) (OSBAPI). It allows application - developers the ability to provision and consume cloud services natively from within - Kubernetes. - - charter_link: charter.md - label: service-catalog - leadership: - chairs: - - github: jhvhs - name: Konstantin Semenov - company: VMware - emeritus_leads: - - github: arschles - name: Aaron Schlesinger - - github: carolynvs - name: Carolyn Van Slyck - - github: duglin - name: Doug Davis - - github: jberkhahn - name: Jonathan Berkhahn - - github: jboyd01 - name: Jay Boyd - - github: kibbles-n-bytes - name: Michael Kibbe - - github: mszostok - name: Mateusz Szostok - - github: pmorie - name: Paul Morie - - github: vaikas-google - name: Ville Aikas - meetings: - - description: Regular SIG Meeting - day: Monday - time: "10:00" - tz: PT (Pacific Time) - frequency: biweekly - url: https://zoom.us/j/7201225346 - archive_url: https://docs.google.com/document/d/17xlpkoEbPR5M6P5VDzNx17q6-IPFxKyebEekCGYiIKM/edit - recordings_url: https://www.youtube.com/watch?v=ukPj1sFFkr0&list=PL69nYSiGNLP2k9ZXx9E1MvRSotFDoHUWs - contact: - slack: sig-service-catalog - mailing_list: https://groups.google.com/forum/#!forum/kubernetes-sig-service-catalog - teams: - - name: sig-service-catalog-api-reviews - description: API Changes and Reviews - - name: sig-service-catalog-bugs - description: Bug Triage and Troubleshooting - - name: sig-service-catalog-feature-requests - description: Feature Requests - - name: sig-service-catalog-misc - description: General Discussion - - name: sig-service-catalog-pr-reviews - description: PR Reviews - - name: sig-service-catalog-proposals - description: Design Proposals - - name: sig-service-catalog-test-failures - description: Test Failures and Triage - liaison: - github: mrbobbytables - name: Bob Killen - subprojects: - - name: minibroker - owners: - - https://raw.githubusercontent.com/kubernetes-sigs/minibroker/master/OWNERS - - name: service-catalog - owners: - - https://raw.githubusercontent.com/kubernetes-sigs/go-open-service-broker-client/master/OWNERS - - https://raw.githubusercontent.com/kubernetes-sigs/service-catalog/master/OWNERS - dir: sig-storage name: Storage mission_statement: > -- cgit v1.2.3