105 lines
7.0 KiB
Markdown
105 lines
7.0 KiB
Markdown
<!---
|
||
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
|
||
--->
|
||
|
||
# Liaisons
|
||
|
||
Steering Committee members are elected representatives of the Kubernetes
|
||
project contributor base. It’s important that we make sure ensure a good
|
||
flow of governance information and feedback loops to and from the
|
||
groups. With over 35 community groups and 100+ leads, it can be hard to
|
||
connect for communitywide consensus and to help with this, each group
|
||
is assigned a Steering Committee liaison.
|
||
|
||
Leads may call on liaisons to act as a point of contact from Steering,
|
||
be an advisor for governance or community health matters, and kick
|
||
things off and consult throughout the process for [annual reports](committee-steering/governance/annual-reports.md).
|
||
|
||
Liaisons do not make decisions for the community group or on behalf of
|
||
the Steering Committee.
|
||
|
||
Liaisons are assigned community groups at random (adjustments can be
|
||
made, if needed) with each member having an (almost) equal distribution
|
||
of SIGs and WGs. Each year after Steering Committee elections, new
|
||
members will assume one of the departing members groups.
|
||
|
||
| Community Group | Steering Committee Liaison |
|
||
| -------------------------- | -------------------------- |
|
||
| [SIG API Machinery](sig-api-machinery/README.md) | Sascha Grunert (**[@saschagrunert](https://github.com/saschagrunert)**) |
|
||
| [SIG Apps](sig-apps/README.md) | Antonio Ojea (**[@aojea](https://github.com/aojea)**) |
|
||
| [SIG Architecture](sig-architecture/README.md) | Benjamin Elder (**[@BenTheElder](https://github.com/BenTheElder)**) |
|
||
| [SIG Auth](sig-auth/README.md) | Patrick Ohly (**[@pohly](https://github.com/pohly)**) |
|
||
| [SIG Autoscaling](sig-autoscaling/README.md) | Maciej Szulik (**[@soltysh](https://github.com/soltysh)**) |
|
||
| [SIG CLI](sig-cli/README.md) | Paco Xu 徐俊杰 (**[@pacoxu](https://github.com/pacoxu)**) |
|
||
| [SIG Cloud Provider](sig-cloud-provider/README.md) | Maciej Szulik (**[@soltysh](https://github.com/soltysh)**) |
|
||
| [SIG Cluster Lifecycle](sig-cluster-lifecycle/README.md) | Sascha Grunert (**[@saschagrunert](https://github.com/saschagrunert)**) |
|
||
| [SIG Contributor Experience](sig-contributor-experience/README.md) | Antonio Ojea (**[@aojea](https://github.com/aojea)**) |
|
||
| [SIG Docs](sig-docs/README.md) | Stephen Augustus (**[@justaugustus](https://github.com/justaugustus)**) |
|
||
| [SIG etcd](sig-etcd/README.md) | Antonio Ojea (**[@aojea](https://github.com/aojea)**) |
|
||
| [SIG Instrumentation](sig-instrumentation/README.md) | Patrick Ohly (**[@pohly](https://github.com/pohly)**) |
|
||
| [SIG K8s Infra](sig-k8s-infra/README.md) | Stephen Augustus (**[@justaugustus](https://github.com/justaugustus)**) |
|
||
| [SIG Multicluster](sig-multicluster/README.md) | Antonio Ojea (**[@aojea](https://github.com/aojea)**) |
|
||
| [SIG Network](sig-network/README.md) | Maciej Szulik (**[@soltysh](https://github.com/soltysh)**) |
|
||
| [SIG Node](sig-node/README.md) | Paco Xu 徐俊杰 (**[@pacoxu](https://github.com/pacoxu)**) |
|
||
| [SIG Release](sig-release/README.md) | Sascha Grunert (**[@saschagrunert](https://github.com/saschagrunert)**) |
|
||
| [SIG Scalability](sig-scalability/README.md) | Antonio Ojea (**[@aojea](https://github.com/aojea)**) |
|
||
| [SIG Scheduling](sig-scheduling/README.md) | Benjamin Elder (**[@BenTheElder](https://github.com/BenTheElder)**) |
|
||
| [SIG Security](sig-security/README.md) | Stephen Augustus (**[@justaugustus](https://github.com/justaugustus)**) |
|
||
| [SIG Storage](sig-storage/README.md) | Paco Xu 徐俊杰 (**[@pacoxu](https://github.com/pacoxu)**) |
|
||
| [SIG Testing](sig-testing/README.md) | Paco Xu 徐俊杰 (**[@pacoxu](https://github.com/pacoxu)**) |
|
||
| [SIG UI](sig-ui/README.md) | Maciej Szulik (**[@soltysh](https://github.com/soltysh)**) |
|
||
| [SIG Windows](sig-windows/README.md) | Benjamin Elder (**[@BenTheElder](https://github.com/BenTheElder)**) |
|
||
| [WG Batch](wg-batch/README.md) | Antonio Ojea (**[@aojea](https://github.com/aojea)**) |
|
||
| [WG Data Protection](wg-data-protection/README.md) | Patrick Ohly (**[@pohly](https://github.com/pohly)**) |
|
||
| [WG Device Management](wg-device-management/README.md) | Benjamin Elder (**[@BenTheElder](https://github.com/BenTheElder)**) |
|
||
| [WG etcd Operator](wg-etcd-operator/README.md) | Maciej Szulik (**[@soltysh](https://github.com/soltysh)**) |
|
||
| [WG LTS](wg-lts/README.md) | Sascha Grunert (**[@saschagrunert](https://github.com/saschagrunert)**) |
|
||
| [WG Policy](wg-policy/README.md) | Patrick Ohly (**[@pohly](https://github.com/pohly)**) |
|
||
| [WG Serving](wg-serving/README.md) | Maciej Szulik (**[@soltysh](https://github.com/soltysh)**) |
|
||
| [WG Structured Logging](wg-structured-logging/README.md) | Sascha Grunert (**[@saschagrunert](https://github.com/saschagrunert)**) |
|
||
| [Committee Code of Conduct](committee-code-of-conduct/README.md) | Sascha Grunert (**[@saschagrunert](https://github.com/saschagrunert)**) |
|
||
| [Committee Security Response](committee-security-response/README.md) | Stephen Augustus (**[@justaugustus](https://github.com/justaugustus)**) |
|
||
<!-- BEGIN CUSTOM CONTENT -->
|
||
## Expectations
|
||
### Liaison will:
|
||
- Alert leads the Annual Report process is starting, expectations, and timeline
|
||
- Check-ins with their groups at least once a quarter. This could mean a group DM
|
||
with Chairs, a visit to a group meeting, or some other connection. Get a pulse
|
||
on health of the following:
|
||
- Contributor base
|
||
- Chairs and other leads: How are they?
|
||
- Contributors, reviewers, approvers: How are they?
|
||
- Newcomers: able to efficiently join and contribute?
|
||
- Operational Health
|
||
- Transparency of meetings and decision processes (eg: published meeting
|
||
agendas, minutes, and video recordings)
|
||
- Communication best practices for shared status and decision making across
|
||
a WG and its sponsor SIG(s) and a SIG and its subprojects
|
||
- Provide consultation on how to improve operational health
|
||
- Gap Analysis
|
||
- Where is the group now and where do they want/need to be?
|
||
- Act as conduit for incoming cross-cutting deliverables requirements, such as
|
||
ones relative to test, infra, org, docs, etc.
|
||
- Check that sustainability is a priority.
|
||
- What is the group doing to ensure contributions are sustainable?
|
||
- What does the group need in order to keep things going?
|
||
- Are there areas of concern?
|
||
- Update Steering Committee keep the Steering Committee in the loop and keep
|
||
track of trackable (ie: not sensitive) work in public issues.
|
||
- Advise on funding matters - how to request and other inquiries
|
||
- Connect leads to whatever they need, when they ask. (if possible!)
|
||
|
||
### Liaisons should:
|
||
- Communicate with their groups on important business that happens at Steering
|
||
level (via our meetings, etc) in order for Steering to achieve a pulse on the
|
||
work we are doing and acknowledge governance changes.
|
||
- Example: if Steering is crafting a new policy, check in with the chairs to
|
||
see how it would fare with their groups.
|
||
|
||
<!-- END CUSTOM CONTENT -->
|