* steering: Liaison updates following 2023 election cycle
Signed-off-by: Stephen Augustus <foo@auggie.dev>
* liaisons: Add Bob for SIG etcd
Signed-off-by: Stephen Augustus <foo@auggie.dev>
* liaisons: Affinity-based swaps pt. 1
- Stephen:
- SIG Security: OpenSSF maintainer/GB member, SRC liaison
- SIG Docs: SIG Release Chair/Release Team subproject owner
- Nabarun:
- CoCC: Previous CoCC member
Signed-off-by: Stephen Augustus <foo@auggie.dev>
* liaisons: Rebalance Steering load
Signed-off-by: Stephen Augustus <foo@auggie.dev>
---------
Signed-off-by: Stephen Augustus <foo@auggie.dev>
The OWNERS at the root of these repos are sig-network people, and
the recent activity I've seen around these repos is coming from
sig-network people. My understanding is sig-autoscaling doesn't
want these projects anymore.
This is the first step, the next step is to suggest that these be
moved to kubernetes-sigs or kubernetes-retired depending on your
willingness to support or own them.
This commit add guidelines on what we expect from presentation and demos
at SIG Autoscaling meetings. This should help set expectations for
future demos, and avoid any misunderstandings about what kinds of
content are acceptable.
This updates the mission statement for SIG Autoscaling to correspond to
the scope of SIG Autoscaling in the charter.
It also ensures that SIG Autoscaling has the right subprojects listed (cluster
autoscaler, vertical pod autoscaler, horizontal-pod-autoscaler, and
scale-client, cluster proportional autoscalers, addon-resizer), moving the
metrics project to SIG instrumentation where it belongs.
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