Archive SIG Service Catalog

4 files changed, 389 insertions, 0 deletions

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 @@
+<!---
+This is an autogenerated file!
+
+Please do not edit this file directly, but instead make changes to the
+sigs.yaml file in the project root.
+
+To understand how this file is generated, see https://git.k8s.io/community/generator/README.md
+--->
+# 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
+<!-- BEGIN CUSTOM CONTENT -->
+
+<!-- END CUSTOM CONTENT -->
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):
+
+<!--
+In future, this will be generated from kubernetes/enhancements kep.yaml files
+1. with SIG as owning-sig or in participating-sigs
+2. listing 1.x, 1.y, or 1.z in milestones or in latest-milestone
+-->
+
+   - 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: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files -->
+- Unique approvers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files -->
+
+Include any other ways you measure group membership
+
+## Subprojects
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+Manually visible via `git diff HEAD@{$YYYY-01-01} HEAD@{$YYYY-12-31} -- $sig-id/README.md`
+-->
+
+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
+
+<!--
+In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $YYYY-12-31
+Manually visible via `git diff HEAD@{$YYYY-01-01} HEAD@{$YYYY-12-31} -- $sig-id/README.md`
+-->
+
+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.