diff options
128 files changed, 7049 insertions, 907 deletions
@@ -13,17 +13,20 @@ It is important to read and understand this legal agreement. ## How do I sign? -After creating your first Pull Request the linux-foundation-easycla bot will respond with information regarding your CLA status along with a link to sign the CLA. +After creating your first Pull Request, the linux-foundation-easycla bot will respond with information regarding your CLA status along with a link to sign the CLA. <img width="1065" alt="EasyCLA bot" src="https://user-images.githubusercontent.com/69111235/152226443-f6fe61ee-0e92-46c5-b6ea-c0deb718a585.png"> -#### 1. If you are signing up as a corporate contributor, ensure that you have linked your corporate email address to your GitHub profile (it doesn't have to be your primary email address for GitHub) or else it can lead to issues with the CLA system. For more information, see [Adding an email address to your GitHub account](https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account). +#### 1. If you are signing up as a corporate contributor, ensure that you have linked your corporate email address to your GitHub profile (it doesn't have to be your primary email address for GitHub) or else it can lead to issues with the CLA system. + +For more information, please see [Adding an email address to your GitHub account](https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account). #### 2. Authorize EasyCLA to read some of your GitHub information <img width="554" alt="GitHub EasyCLA Authorization" src="https://user-images.githubusercontent.com/69111235/152228712-7d22f9d0-9f3c-4226-9ee0-bacba4b47725.png"> -Click on the "Please click here to be authorized" link to navigate to the GitHub Authorize Linux Foundation: EasyCLA page. Then click Authorize LF-Engineering to give the Linux Foundation read-only access to list the email addresses associated with your GitHub account. +- Click on the **Please click here to be authorized** link to navigate to the GitHub Authorize Linux Foundation: EasyCLA page. +- Then click **Authorize LF-Engineering** to give the Linux Foundation read-only access to list the email addresses associated with your GitHub account. #### 3. Select from the two types of contributor @@ -80,12 +83,11 @@ Canonical until 2017-03-31 If you encounter any problems signing the CLA and need further assistance, log a ticket by clicking on the link [please submit a support request ticket](https://jira.linuxfoundation.org/plugins/servlet/theme/portal/4) from the EasyCLA bot's response. Someone from the CNCF will respond to your ticket to help. Should you have any issues using the LF Support Site, send a message to the -backup e-mail support address <login-issues@jira.linuxfoundation.org> +backup email support address <login-issues@jira.linuxfoundation.org> ## Setting up the CNCF CLA check -If you are a Kubernetes GitHub organization or repo owner and would like to setup -the Linux Foundation CNCF CLA check for your repositories, [read the docs on setting up the CNCF CLA check](/github-management/setting-up-cla-check.md) +If you are a Kubernetes GitHub organization or repo owner and would like to setup the Linux Foundation CNCF CLA check for your repositories, [read the docs on setting up the CNCF CLA check](/github-management/setting-up-cla-check.md) [Linux Foundation Support Site]: https://support.linuxfoundation.org/ @@ -1,17 +1,27 @@ # See the OWNERS docs at https://go.k8s.io/owners -approvers: - - cblecker - - idvoretskyi - - jdumars - - mrbobbytables - - nikhita - - parispittman - - sig-contributor-experience-leads - - committee-steering -emeritus_approvers: - - alisondy - - castrojo - - calebamiles - - grodrigues3 - - spiffxp +filters: + ".*": + approvers: + - cblecker + - idvoretskyi + - jdumars + - mrbobbytables + - nikhita + - parispittman + - sig-contributor-experience-leads + - committee-steering + emeritus_approvers: + - alisondy + - castrojo + - calebamiles + - grodrigues3 + - spiffxp + # ensure PRs for annual reports are generated + "annual-report-.*\\.md$": + labels: + - area/annual-reports + # label charter changes for review by steering + "charter.md": + labels: + - committee/steering diff --git a/OWNERS_ALIASES b/OWNERS_ALIASES index 01d35dfe..47493ff4 100644 --- a/OWNERS_ALIASES +++ b/OWNERS_ALIASES @@ -69,6 +69,7 @@ aliases: - dchen1107 - derekwaynecarr sig-release-leads: + - Verolop - cpanato - jeremyrickard - justaugustus @@ -93,7 +94,10 @@ aliases: sig-testing-leads: - BenTheElder - alvaroaleman + - aojea - cjwagner + - michelle192837 + - pohly - spiffxp - stevekuznetsov sig-ui-leads: @@ -138,20 +142,16 @@ aliases: wg-structured-logging-leads: - pohly - serathius - ug-big-data-leads: - - erikerlandson - - foxish - - liyinan926 ug-vmware-users-leads: - brysonshepherd - cantbewong - mylesagray - phenixblue committee-code-of-conduct: + - detiber - endocrimes - hlipsig - jeremyrickard - - palnabarun - salaxander committee-security-response: - cjcullen @@ -162,12 +162,12 @@ aliases: - tabbysable - tallclair committee-steering: + - BenTheElder - cblecker - - dims + - cpanato - justaugustus - - liggitt - mrbobbytables - - parispittman + - palnabarun - tpepper ## BEGIN CUSTOM CONTENT provider-aws: diff --git a/ug-big-data/OWNERS b/archive/ug-big-data/OWNERS index cef3c5d3..cef3c5d3 100644 --- a/ug-big-data/OWNERS +++ b/archive/ug-big-data/OWNERS diff --git a/ug-big-data/README.md b/archive/ug-big-data/README.md index 9fd546e8..9fd546e8 100644 --- a/ug-big-data/README.md +++ b/archive/ug-big-data/README.md diff --git a/ug-big-data/resources.md b/archive/ug-big-data/resources.md index c7b3b2d0..c7b3b2d0 100644 --- a/ug-big-data/resources.md +++ b/archive/ug-big-data/resources.md diff --git a/archive/wg-component-standard/component-config/README.md b/archive/wg-component-standard/component-config/README.md new file mode 100644 index 00000000..66e7185b --- /dev/null +++ b/archive/wg-component-standard/component-config/README.md @@ -0,0 +1,980 @@ +This copy of [Versioned Component Configuration Files](vccf-proposal) +was automatically converted from Google Docs to Markdown +so that it could be included in the community archive. +Several interesting comment threads remain unexported but +available in the Google Doc. You can gain access to the +doc by joining the `dev@kubernetes.io` mailing list +(previously `kubernetes-dev@googlegroups.com`). Please +do not request access via the Google Docs UI, as this +spams the owners with access requests. Thank you :). + +[vccf-proposal]: https://docs.google.com/document/d/1FdaEJUEh091qf5B98HM6_8MS764iXrxxigNIdwHYW9c/ + + +# Versioned Component Configuration Files + + +## How Kubelet learned to stop using flags and love versioned config. How your component can, too. + +**Shared publicly!** + +**Author:** mtaufen@google.com + +**Last Updated:** March 28, 2018 + +**Self Link:** https://goo.gl/GM8KyH + +# Background + +A long time ago (but still in this galaxy), someone had the bright idea that we could avoid a lot of the pain of deploying and managing command-line flags for each core cluster component (kubelet, kube-proxy, scheduler, etc.) by switching to Kubernetes-style versioned configuration files. This effort became known to the community as _component configuration_, or simply _componentconfig_. At its origin, a consistent philosophy for _what_ componentconfig should look like did not exist. + +Last year, mikedanese@ did a great job of compiling the ideas behind componentconfig (ideas Mike, other folks, and I were discussing in several GitHub threads) into a single [document](https://docs.google.com/document/d/1arP4T9Qkp2SovlJZ_y790sBeiWXDO6SG10pZ_UUU-Lc), in the hope that we could provide standard guidelines and improve consistency across the project. Mike's document catalyzed our push to try componentconfig in a few components, and here we are almost a year later. + +As of Kubernetes v1.10, the Kubelet is firmly on its way to migrating from flags to versioned configuration files. It can consume a beta-versioned config file and many flags are now deprecated and pending removal in favor of this file. Many remaining flags will be replaced by the file over time. Additionally, the kube-proxy component is very close to having a beta-versioned config file of its own. + +This document restates the motivation and records lessons from OSS work over the past year: + + + +* a brief review of why we want versioned config files for all core cluster components +* the _ideal_ state of a component's configuration API +* how to migrate an existing component to versioned configuration files (Kubelet example) +* remaining work + + +# Why versioned config files? + +The short answer is that flags are nonstandard interfaces with weak stability guarantees. They are confusing and hard to deploy, and this is the opposite of what Kubernetes should be. + +Command-line flags present a number of problems: + + + +* Flags are a public API, but are not versioned and cannot be versioned separately from the binary: + * For _core_ components the binary version is coupled to the Kubernetes release version. We use semantic versioning for our binaries, but can't bump a major version unless Kubernetes does: + * We _shouldn't_ ever **fix bad defaults** for existing flag names without bumping the major version of a binary. In reality, we get around this by giving advance warning and technically breaking semantic versioning of the binary. + * We _shouldn't_ ever **remove a flag** without bumping the major version of a binary. In reality we use a [flag deprecation policy](https://kubernetes.io/docs/reference/deprecation-policy/#deprecating-a-flag-or-cli) that allows us to technically break semantic versioning of the binary as long as we give advance warning. + * We incrementally deprecate individual parameters over time, instead of guaranteeing a consistent set of parameters for the life of an API version. This confuses users and results in a less stable API. + * We can't typically deploy flag-based configuration independently from a binary version upgrade, because the compatibility of the interface is so tightly coupled. +* Values are often re-configured, which precipitates additional tools to parameterize and write configuration for system-specific process management agents (e.g. systemd). We can eliminate the dependency on parameterization tools if process manager config is static; e.g. the configured command line just needs to reference a file in a fixed location. +* Developers inevitably embed structured data in strings and invent one-off parsers to process their flags. This invites bugs. +* mikedanese@ outlined more issues in his [document](https://docs.google.com/document/d/1arP4T9Qkp2SovlJZ_y790sBeiWXDO6SG10pZ_UUU-Lc). + +Core goals of componentconfig include: + + + +* Standardize the configuration approach for all core cluster components. +* Enable dynamic configuration deployment mechanisms. + +Conveniently, Kubernetes has similar goals: + + + +* Standardize the configuration approach for cluster infrastructure. +* Enable dynamic deployment mechanisms. + +Kubernetes had already paved the way: It has what we need to version our configuration interfaces, decouple configuration changes from binary changes, represent configuration in a structured format, and deploy configuration in a dynamic environment. + + + +* Versioning was accomplished via the API machinery's group/version mechanism. +* Adhering to the same API guarantees as the core Kubernetes APIs provides a stable configuration surface, and allows us to decouple the configuration interface from releases that support the same API version. +* Kubernetes API objects are defined as Go structs, which means we don't have to parse strings to deal with structured config. +* Kubernetes has deployment mechanisms (ConfigMap volume source) that work well for pushing new versions of configuration files into production. +* There is no requirement to restart a process when you change a file, unlike flags. + +**All core Kubernetes components should eventually consume their configuration via versioned configuration files, instead of command-line flags.** + + +# tl;dr: What should a component do? + +**This is the _ideal_ command-line API for every core cluster component:** + +```console +$ component --config=path +``` + +The component exposes _only one_ flag on its command line. This flag provides the file path to a config file with a versioned format. All other relevant configuration information is referenced via this file. + +_One, stable flag where everything else is versioned config_ is the ideal API recommended by componentconfig. If you are creating a new component from scratch, begin and end with this API. + +For several reasons discussed in the next section, the migration from flags to versioned config is a serious journey for most existing components, and these may want or even need a couple more flags at the end of the day. + +In general, every core cluster component should: + + + +* Maintain a distinct Kubernetes API group called {component}.config.k8s.io, which contains versioned sets of config objects - primarily a {Component}Configuration struct in each version. This struct, serialized to disk by the API machinery, is the file format for configuration. +* Ensure {component}.config.k8s.io adheres to the standard Kubernetes [API deprecation policy](https://kubernetes.io/docs/reference/deprecation-policy/#deprecating-parts-of-the-api), [API conventions](https://github.com/kubernetes/community/blob/master/contributors/devel/api-conventions.md), and [API changes policy](https://github.com/kubernetes/community/blob/master/contributors/devel/api_changes.md). +* Expose a flag named --config, which accepts a path to a file that contains a serialized {Component}Configuration struct. +* Use the Kubernetes API machinery to deserialize the config file data, apply defaults, and convert to an internal version for runtime use. +* Validate the internal version prior to using it. If validation fails, refuse to run with the specified configuration. +* Ensure third-party libraries aren't leaking flags. + +We discuss how to migrate a component from flags to versioned config files in the next section. + + +# In-depth: How to migrate a component from flags to a versioned config file + + +## Take back control of the command-line API + +Our goal is to _decrease_ flag usage in favor of versioned config files. It will help to decrease the growth rate of the component's flag API. There are at least two sources of this growth: + + + +* PRs that directly extend the flag API. +* Adding or updating third-party libraries. + +Whoever owns the componentconfig effort for a given component should be in-the-loop on PRs that add new flags. This person has a strong interest in saying "no" to new flags, because it increases the number of things they have to carefully migrate to the new versioned config file API. When new flags really prove necessary, this person still has a strong interest in ensuring they will be compatible when migrated. + +The second case is an artifact of many libraries registering flags globally (global flag sets are provided by both the _flag_ and _pflag_ libraries). Since most components just parse the global flag sets by default, they tend to accumulate the flags from these libraries. The libraries are impolite, and the components are typically too trusting. Each component should be more cautious by: + + + +* constructing its own, isolated flag set +* explicitly registering necessary flags from third-party libraries into this flag set +* parsing _only_ the flags in this flag set + +You can find the example of how the Kubelet took back control of its flag set in [Explicit kubelet flags](https://github.com/kubernetes/kubernetes/pull/57613) (see also the follow-up PR, [#58095](https://github.com/kubernetes/kubernetes/pull/58095)). + +Many components indiscriminately add the global flag set to their primary flag set via `pflag.CommandLine.AddGoFlagSet(flag.CommandLine)`. Further, most components delegate their flag parsing, help text generation, etc. to [Cobra](https://github.com/spf13/cobra). Cobra implicitly adds flag.CommandLine in several cases, which unfortunately gets in the way of explicit control over the flag API. + +In order for Cobra to parse flags for you, it has to be made aware of your flagset. This is achieved by registering flags to the command's flag set. Cobra will implicitly merge the global command lines with this flag set when it parses flags. Consider the following Go program, which creates a local, isolated flag set (as recommended above). The program also registers a global flag, which we _hope_ won't be parsed, because it is not explicitly registered with our local flag set. + + +```go +package main + +import ( + "fmt" + "os" + + "github.com/spf13/cobra" + "github.com/spf13/pflag" +) + +const use = "testcmd" + +var ( + globalFlagTarget string + localFlagTarget string +) + +func init() { + pflag.StringVar(&globalFlagTarget, "global-flag", globalFlagTarget, "globally-registered flag") +} + +func NewLocalFlagSet() *pflag.FlagSet { + fs := pflag.NewFlagSet(use, pflag.ContinueOnError) + fs.StringVar(&localFlagTarget, "local-flag", localFlagTarget, "locally-registered flag") + return fs +} + +func NewTestCmd() *cobra.Command { + cmd := &cobra.Command{ + Use: use, + Run: func(cmd *cobra.Command, args []string) { + fmt.Printf("globalFlagTarget: %q\n", globalFlagTarget) + fmt.Printf("localFlagTarget: %q\n", localFlagTarget) + }, + } + cmd.Flags().AddFlagSet(NewLocalFlagSet()) + return cmd +} + +func main() { + cmd := NewTestCmd() + if err := cmd.Execute(); err != nil { + fmt.Fprintf(os.Stderr, "error: %v\n", err) + os.Exit(1) + } +} +``` + + +If we run the program, we see that this is not the case. The global flag is parsed by Cobra: + + +```console +$ testcmd --global-flag hello + +globalFlagTarget: "hello" +localFlagTarget: "" +``` + + +You can circumvent this by disabling Cobra's flag parsing. This, unfortunately, requires that you both parse flags and implement --help short-circuiting on your own. The next example attempts to extend the above to do so. + + +```go +package main + +import ( + "fmt" + "os" + + "github.com/spf13/cobra" + "github.com/spf13/pflag" +) + +const use = "testcmd" + +var ( + globalFlagTarget string + localFlagTarget string +) + +func init() { + pflag.StringVar(&globalFlagTarget, "global-flag", globalFlagTarget, "globally-registered flag") +} + +func NewLocalFlagSet() *pflag.FlagSet { + fs := pflag.NewFlagSet(use, pflag.ContinueOnError) + fs.StringVar(&localFlagTarget, "local-flag", localFlagTarget, "locally-registered flag") + return fs +} + +func NewTestCmd() *cobra.Command { + localFlagSet := NewLocalFlagSet() + cmd := &cobra.Command{ + Use: use, + DisableFlagParsing: true, + Run: func(cmd *cobra.Command, args []string) { + // parse our local flag set + if err := localFlagSet.Parse(args); err != nil { + cmd.Usage() + fatal(err) + } + // --help + help, err := localFlagSet.GetBool("help") + if err != nil { + fatal(fmt.Errorf(`"help" flag is non-bool, programmer error, please correct`)) + } + if help { + cmd.Help() + return + } + // print the flag values + fmt.Printf("globalFlagTarget: %q\n", globalFlagTarget) + fmt.Printf("localFlagTarget: %q\n", localFlagTarget) + }, + } + localFlagSet.BoolP("help", "h", false, fmt.Sprintf("help for %s", cmd.Name())) + // Cobra still needs to be aware of our flag set to generate usage and help text + cmd.Flags().AddFlagSet(localFlagSet) + return cmd +} + +func fatal(err error) { + fmt.Fprintf(os.Stderr, "error: %v\n", err) + os.Exit(1) +} + +func main() { + cmd := NewTestCmd() + if err := cmd.Execute(); err != nil { + fatal(err) + } +} +``` + + +When we run the program and attempt to set the global flag, we see that the global flag is now rejected, but we also see that it is still included in the usage text! + + +```console +$ testcmd --global-flag hello +Usage: + testcmd [flags] + +Flags: + --global-flag string globally-registered flag + -h, --help help for testcmd + --local-flag string locally-registered flag +error: unknown flag: --global-flag +``` + + +The same thing happens when we pass --help: + + +```console +$ testcmd --help +Usage: + testcmd [flags] + +Flags: + --global-flag string globally-registered flag + -h, --help help for testcmd + --local-flag string locally-registered flag +``` + + +This is because Cobra also uses the global flags when generating usage and help text. This can be circumvented by doing-it-yourself, again. + + +```go +package main + +import ( + "fmt" + "os" + + "github.com/spf13/cobra" + "github.com/spf13/pflag" +) + +const use = "testcmd" + +var ( + globalFlagTarget string + localFlagTarget string +) + +func init() { + pflag.StringVar(&globalFlagTarget, "global-flag", globalFlagTarget, "globally-registered flag") +} + +func NewLocalFlagSet() *pflag.FlagSet { + fs := pflag.NewFlagSet(use, pflag.ContinueOnError) + fs.StringVar(&localFlagTarget, "local-flag", localFlagTarget, "locally-registered flag") + return fs +} + +func NewTestCmd() *cobra.Command { + localFlagSet := NewLocalFlagSet() + cmd := &cobra.Command{ + Use: use, + DisableFlagParsing: true, + Run: func(cmd *cobra.Command, args []string) { + // parse our local flag set + if err := localFlagSet.Parse(args); err != nil { + cmd.Usage() + fatal(err) + } + // --help + help, err := localFlagSet.GetBool("help") + if err != nil { + fatal(fmt.Errorf(`"help" flag is non-bool, programmer error, please correct`)) + } + if help { + cmd.Help() + return + } + // print the flag values + fmt.Printf("globalFlagTarget: %q\n", globalFlagTarget) + fmt.Printf("localFlagTarget: %q\n", localFlagTarget) + }, + } + localFlagSet.BoolP("help", "h", false, fmt.Sprintf("help for %s", cmd.Name())) + + // ugly, but necessary, because Cobra's default UsageFunc and HelpFunc pollute the flagset with global flags + const usageFmt = "Usage:\n %s\n\nFlags:\n%s" + cmd.SetUsageFunc(func(cmd *cobra.Command) error { + fmt.Fprintf(cmd.OutOrStderr(), usageFmt, cmd.UseLine(), localFlagSet.FlagUsagesWrapped(2)) + return nil + }) + cmd.SetHelpFunc(func(cmd *cobra.Command, args []string) { + fmt.Fprintf(cmd.OutOrStdout(), usageFmt, cmd.UseLine(), localFlagSet.FlagUsagesWrapped(2)) + }) + + return cmd +} + +func fatal(err error) { + fmt.Fprintf(os.Stderr, "error: %v\n", err) + os.Exit(1) +} + +func main() { + cmd := NewTestCmd() + if err := cmd.Execute(); err != nil { + fatal(err) + } +} +``` + + +And now things are more as we expect. + + +```console +$ testcmd --global-flag hello +Usage: + testcmd [flags] + +Flags: + -h, --help help for testcmd + --local-flag string locally-registered flag +error: unknown flag: --global-flag + +$ testcmd --help +Usage: + testcmd [flags] + +Flags: + -h, --help help for testcmd + --local-flag string locally-registered flag +``` + + +**Alternative solutions to piecewise-DIY-overrides are highly welcomed** (if someone wants to write a Cobra replacement that meets our needs while managing state more cleanly, I won't stop you). As all core components will need to solve this one way or another, a centralized utility library for working with Cobra would be useful, at the very least. + + +### Use a flags struct + +The migration from flags to versioned config files will be much easier if you first centralize where your target flag values, registrations, and deprecations happen. If you have a single structure definition that contains all of the component's flag-targeted values, you can focus on moving fields from this structure into your versioned configuration API. + +The Kubelet uses a structure called KubeletFlags, with an associated `func (f *KubeletFlags) AddFlags(fs *pflag.FlagSet)` to handle flag registrations and deprecations. Note that AddFlags does not register global flags from third-party libraries; it is only concerned with flags in the KubeletFlags structure. + +We also recommend that defaulting behavior for flags be clearly separated from the flag registrations. Kubelet initializes flag defaults when constructing a new KubeletFlags, and re-uses these values when registering flags. This makes it easy to see which defaults are applied, which makes it easy to migrate those defaults to versioned config. This also prevents AddFlags from overriding values in the flags struct, in the event that you need to modify values before registering flags. + +Finally, the Kubelet offers a function for validating the flags structure. You may choose to centralize validation here, which will make it easier to migrate that validation to your versioned config, and will also elevate configuration errors to sooner in the component's lifecycle. **It is important to point out that burying flag validation in application logic is an anti-pattern that should be avoided whenever possible. Given the opportunity, components should be refactored to centralize validation.** The Kubelet unfortunately falls into the "validation all over the place" trap, and will eventually need to be refactored to centralize validation. + +KubeletFlags currently contains some flags that are only registered on specific operating systems (e.g. Windows). These fields are prefixed with the name of the OS (e.g. `Windows*`) and registrations are handled by OS-specific implementations of the addOSFlags method (managed via Go build tags). + +This excerpt from the Kubelet's flag code gives the general structure: + + +<table> + <tr> + <td>cmd/kubelet/app/options/options.go + </td> + </tr> + <tr> + <td>type KubeletFlags struct { +<p> + KubeletConfigFile string +<p> + … +<p> +} +<p> +func NewKubeletFlags() *KubeletFlags { +<p> + return &KubeletFlags{ +<p> + // apply defaults here +<p> + } +<p> +} +<p> +func (f *KubeletFlags) AddFlags(fs *pflag.FlagSet) { +<p> + f.addOSFlags(fs) +<p> + fs.StringVar(&f.KubeletConfigFile, "config", f.KubeletConfigFile, "…") +<p> + … +<p> +} +<p> +func ValidateKubeletFlags(f *KubeletFlags) error { +<p> + // validate here, return error if validation fails, nil otherwise +<p> + … +<p> +} + </td> + </tr> + <tr> + <td>cmd/kubelet/app/options/osflags_windows.go + </td> + </tr> + <tr> + <td>// +build windows +<p> +… +<p> +func (f *KubeletFlags) addOSFlags(fs *pflag.FlagSet) { +<p> + // add windows flags here +<p> +} + </td> + </tr> + <tr> + <td>cmd/kubelet/app/options/osflags_other.go + </td> + </tr> + <tr> + <td>// +build !windows +<p> +… +<p> +func (f *KubeletFlags) addOSFlags(fs *pflag.FlagSet) { +<p> + // noop +<p> +} + </td> + </tr> +</table> + + + +## Create component's config API group + +Components should expose versioned Kubernetes-style configuration APIs. This section explains how to do so. + +As explained in the [API Conventions](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md) doc, Kubernetes API objects consist of a canonical internal version, and multiple external versions. In a given release, it is possible to convert between any of the external versions by first converting to the internal version, then converting from the internal version to the target version. + +All versions live together in the same API group. Typically, an API group's source tree consists of a top-level directory that implements the package for the internal version, and subdirectories corresponding to the packages that implement each external version. There are usually a few additional files that implement various utilities. Finally, there will be generated files (omitted from the below file tree) for conversions, deep-copies, and defaulter registration. + +For example, the file hierarchy of the Kubelet's _kubelet.config.k8s.io_ API group looks like this: + + +``` +- pkg/kubelet/apis/kubeletconfig +| - fuzzer // utility for fuzzing kubelet.config.k8s.io objects +| | - fuzzer.go +| +| - scheme // utility for scheme and codecs (serializations and conversions) +| | - scheme.go +| | - scheme_test.go // round trip tests that use the fuzzer +| +| - v1beta1 // implementation of v1beta1 external type +| | - defaults.go // v1beta1 defaults +| | - doc.go // various build tags that trigger code generation +| | - register.go // functions for registering API with a scheme +| | - types.go // v1beta1 versions of kubelet.config.k8s.io objects +| +| - validation // utility for validating kubelet.config.k8s.io objects +| | - validation.go +| +| - doc.go // various build tags that trigger code generation +| - helpers.go // utility functions +| - helpers_test.go // tests for utility functions +| - register.go // +| - types.go +``` + + +**When creating your component's API group, please refer to upstream Kubernetes for the most up-to-date example of how it should look, and assign [@mtaufen](https://github.com/mtaufen) or [@liggitt](https://github.com/liggitt) to review your PR.** A few important points to remember are: + + + +* The API group should be named _{component}.config.k8s.io_, where _{component}_ is the name of your component. It is conventional to also name the directory containing the API group _{component}config_, e.g. _kubeletconfig_. +* You should start by creating only a _v1alpha1_ external config version, and migrating fields from your flags structure to the objects in this version. Loading config from a file should be considered an alpha feature until you are confident enough in your _v1alpha1_ version to move it to beta. +* If your configuration can contain relative file paths, these paths should be resolved relative to the location to the config file when loaded. The Kubelet has a utility function (KubeletConfigurationPathRefs in file _helpers.go_) that enumerates these fields. +* Once you have created your API group (and whenever you update your config structs), you can run make clean\_generated; make generated\_files to produce the generated conversions, deep-copies, and defaulter registrations. +* At the beginning, most componentconfig APIs will only load a single object, though this object may be a composition of subobjects. E.g. the Kubelet just loads a KubeletConfiguration, which is a composition of subobjects defined in the _types.go_ files. +* Isomorphic objects must exist in both the internal and external versions for conversions to be generated. +* Only the internal, canonical type needs to be validated. External-versioned config files must be converted to this representation and then validated before your component uses the configuration. +* You should not treat nil and empty container types (maps and slices) as semantically different in your API, as this has caused issues with serializers in the past. In practice, this means all map and slice fields should be +optional and omitempty (see [Optional vs. Required](https://github.com/kubernetes/community/blob/master/contributors/devel/api-conventions.md#optional-vs-required)). In general, it is rare to have any required config fields, as config versions should ship with functional defaults. +* You don't have to worry about supporting loading config from Proto yet, but you should not rule this out as an eventual possibility. +* Try to keep the order of the fields the same between the internal and external types, the defaulter, and the flag registrations. This makes the code much easier to read and maintain. +* Make component configs modular and composable. Share structs for the same functionality in different components (think of PodSpec shared in many of the core resources). +* **TODO:** please add more if necessary + + +## Make it possible to parse flags into the internal config object + +In order to maintain command-line compatibility, it must still be possible to parse flags for a period of time after they become available in your config API. When a field moves from your flags structure to your config structure, you should update the corresponding flag registration to target the internal config structure. It helps to keep all flag registrations close to each other. + +For example, Kubelet provides some additional utilities in its options package for targeting KubeletConfiguration values via flags: a constructor (similar to NewKubeletFlags) that returns a default KubeletConfiguration and a function for registering flags that target this config. + + +<table> + <tr> + <td>cmd/kubelet/app/options/options.go + </td> + </tr> + <tr> + <td>func NewKubeletConfiguration() (*kubeletconfig.KubeletConfiguration, error) { +<p> + scheme, _, err := kubeletscheme.NewSchemeAndCodecs() +<p> + if err != nil { +<p> + return nil, err +<p> + } +<p> + versioned := &v1beta1.KubeletConfiguration{} +<p> + scheme.Default(versioned) +<p> + config := &kubeletconfig.KubeletConfiguration{} +<p> + if err := scheme.Convert(versioned, config, nil); err != nil { +<p> + return nil, err +<p> + } +<p> + applyLegacyDefaults(config) +<p> + return config, nil +<p> +} +<p> +func AddKubeletConfigFlags(fs *pflag.FlagSet, c *kubeletconfig.KubeletConfiguration) { +<p> + // register flags here, in the same style as in KubeletFlags.AddFlags +<p> + … +<p> +} + </td> + </tr> +</table> + + + +## Improve/fix defaults between flags and versioned config + +Note in the previous example from the Kubelet, there is a call to a function called applyLegacyDefaults. With the move to versioned config files, each API version can have its own set of default values. Flags implicitly constitute their own "version," so it is possible to have different defaults when you load config from a file versus when you load config from flags. NewKubeletConfiguration is specifically constructing a config object to be targeted by flags, so it modifies the values to contain the defaults associated with flags. + +The ability to separate defaults across versions allowed us to use better defaults in _v1beta1_ (see [Secure Kubelet's componentconfig defaults while maintaining CLI compatibility](https://github.com/kubernetes/kubernetes/pull/59666)) than the Kubelet's flag API, without breaking compatibility. If you have defaults in your component's flag API that you would like to change, this is the opportunity to do so. + + +## Incrementally migrate flags to your config API + +For many flags, you will simply be able to: + + + +1. Cut the field from your flags struct. +2. Paste the field into both the internal and versioned config structs. +3. Ensure the field tags are correct on the versioned config struct (json, omitempty, etc.). +4. Move the default into the versioned defaulter, if the old default should be kept. \ +If the versioned default should be different than the old default value, add the new default to the versioned defaulter and the old default into applyLegacyDefaults. +5. Move the flag registration to the AddFlags function for your internal config struct. + +Some, however, will need more work: + + + +* If a flag embeds structure in a string format (e.g. a list or map), you should use the appropriate language structures (e.g. Go slice or map) to represent that structure in your config API, which will facilitate writing JSON and YAML files. For backwards compatibility, you can write a shim to parse the flag into the structured field. See these PRs for examples: + * [Make feature gates loadable from a map[string]bool](https://github.com/kubernetes/kubernetes/pull/53025) + * [Lift embedded structure out of ManifestURLHeader field](https://github.com/kubernetes/kubernetes/pull/54643) + * [Lift embedded structure out of eviction-related KubeletConfiguration fields](https://github.com/kubernetes/kubernetes/pull/54823) + * [ColonSeparatedMultimapStringString: allow multiple Set invocations with default override](https://github.com/kubernetes/kubernetes/pull/55254) +* If a flag enables or configures alpha or experimental features which do not have an associated [feature gate](https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/apiserver/pkg/util/feature/feature_gate.go) (see _[kube\_features.go](https://github.com/kubernetes/kubernetes/blob/master/pkg/features/kube_features.go)_ for a list of gates), you must add a gate or graduate the feature to beta before moving the flag to versioned config. The [API changes policy](https://github.com/kubernetes/community/blob/master/contributors/devel/api_changes.md) allows for alpha fields in beta or GA-versioned config, but only if the behavior configured via the fields is guarded by a feature gate and disabled by default (see [Adding Unstable Features to Stable Versions](https://github.com/kubernetes/community/blob/master/contributors/devel/api_changes.md#adding-unstable-features-to-stable-versions)). Note that if you add an alpha field to beta or GA-versioned config, you permanently exhaust the name you choose for the field; if you change the name before the field graduates from alpha, you must tombstone the old name and never reuse it. +* If a field requires a [non-zero](https://golang.org/ref/spec#The_zero_value) default value, but the zero-value is _still_ a valid option, it should carry a pointer type in the versioned config struct. This allows the defaulter to differentiate between omitted fields and fields explicitly configured to the zero value. For many fields, especially paths, it is sufficient to simply use the zero value as the default. + * Try to avoid pointer fields on the internal type, so that you need fewer nil checks in your code. Let the defaulter handle nils on the external type. You may need to add a [conversion function](https://github.com/kubernetes/kubernetes/blob/e8388e035b1f08d00dd2bf811d9587c6b7589ace/staging/src/k8s.io/apimachinery/pkg/apis/meta/v1/conversion.go) to facilitate pointer to non-pointer conversion generation. +* If a field is a nilable container type (slice or map) and requires a non-empty default, users must always explicitly set the field to achieve non-default values. If specifying an empty container type was previously valid (e.g. to disable), you will need to provide an explicit substitute for doing so. Since [some serializers (e.g. proto)](https://github.com/kubernetes/kubernetes/issues/43203) do not differentiate between nil and empty container types, neither can we. + * See [Add 'none' option to EnforceNodeAllocatable](https://github.com/kubernetes/kubernetes/pull/59515) as an example. + +Finally, some flags should not yet be migrated to versioned config. These are unsolved problems, and you should wait to migrate until they can be solved with a consistent pattern across all core components (for more detail, see _Remaining work_). + + + +* Some flags are only registered in builds for specific operating systems (e.g. the Kubelet's --windows-service flag). We have not settled on how these sorts of fields should be represented in versioned config files, so please refrain from migrating these flags for now. +* Some flags specify instance-specific values (e.g. the Kubelet's --hostname-override flag). It is impossible to share the same instance-specific value between multiple instances of a component (e.g. you wouldn't want two nodes with the same hostname). If there is (or you suspect) a use case where you want to share the same config source between multiple instances of a component (e.g. if you want to deliver config files via a ConfigMap), you should refrain from migrating these flags for now. + +**Note: Do not use unversioned types in your versioned config; stick to language primitives and types from versioned APIs. That said, even using types from other versioned APIs carries risk: you'll have to respond if that API version is deprecated.** + + +## Component Bootstrap + +This section describes the general steps for bootstrapping a component to the point that it knows it has a valid internal-versioned configuration to run with. This should be sufficient for most components. This section begins with the Run method on the Cobra command, and ends with validation of a fully-resolved internal config object. + + +### Initial Flags Parse + +The first thing your component should do is parse its command line into an instance of the flags struct and the internal-verisoned config struct, with defaults applied prior to parsing flags. This is shown in the example in the _Take back control of the command-line API_ section. If you have validation for the flags struct, this is an appropriate place to perform it. + + +### Load config file, convert to internal version, resolve relative paths + +Once the initial flags parse is complete, check whether the user provided a path to --config. If so, load the file at that path (if relative, --config should be resolved relative to the Kubelet's working directory) and unmarshal it via the API machinery's UniversalDecoder, which should perform defaulting and conversion to the internal type. For example: + + +<table> + <tr> + <td>pkg/kubelet/kubeletconfig/util/codec/codec.go + </td> + </tr> + <tr> + <td>// DecodeKubeletConfiguration decodes a serialized KubeletConfiguration to the internal type +<p> +func DecodeKubeletConfiguration(kubeletCodecs *serializer.CodecFactory, data []byte) (*kubeletconfig.KubeletConfiguration, error) { +<p> + // the UniversalDecoder runs defaulting and returns the internal type by default +<p> + obj, gvk, err := kubeletCodecs.UniversalDecoder().Decode(data, nil, nil) +<p> + if err != nil { +<p> + return nil, fmt.Errorf("failed to decode, error: %v", err) +<p> + } +<p> + internalKC, ok := obj.(*kubeletconfig.KubeletConfiguration) +<p> + if !ok { +<p> + return nil, fmt.Errorf("failed to cast object to KubeletConfiguration, unexpected type: %v", gvk) +<p> + } +<p> + return internalKC, nil +<p> +} + </td> + </tr> +</table> + + +Next, any fields in the config that specify file paths should be resolved relative to the location of the config file. The Kubelet has a helper that returns pointers to the path fields for a given config (and also a test to detect when new fields are added). + + +<table> + <tr> + <td>pkg/kubelet/apis/kubeletconfig/helpers.go + </td> + </tr> + <tr> + <td>// KubeletConfigurationPathRefs returns pointers to all of the KubeletConfiguration fields that contain filepaths. +<p> +// You might use this, for example, to resolve all relative paths against some common root before +<p> +// passing the configuration to the application. This method must be kept up to date as new fields are added. +<p> +func KubeletConfigurationPathRefs(kc *KubeletConfiguration) []*string { +<p> + paths := []*string{} +<p> + paths = append(paths, &kc.StaticPodPath) +<p> + paths = append(paths, &kc.Authentication.X509.ClientCAFile) +<p> + paths = append(paths, &kc.TLSCertFile) +<p> + paths = append(paths, &kc.TLSPrivateKeyFile) +<p> + paths = append(paths, &kc.ResolverConfig) +<p> + return paths +<p> +} + </td> + </tr> +</table> + + +These pointers can be used to resolve relative paths when loading the config file: + + +<table> + <tr> + <td>pkg/kubelet/kubeletconfig/configfiles/configfiles.go + </td> + </tr> + <tr> + <td>// resolveRelativePaths makes relative paths absolute by resolving them against `root` +<p> +func resolveRelativePaths(paths []*string, root string) { +<p> + for _, path := range paths { +<p> + // leave empty paths alone, "no path" is a valid input +<p> + // do not attempt to resolve paths that are already absolute +<p> + if len(*path) > 0 && !filepath.IsAbs(*path) { +<p> + *path = filepath.Join(root, *path) +<p> + } +<p> + } +<p> +} + </td> + </tr> +</table> + + + +### Enforce flag precedence + +If you were able to move all of your command-line flags to versioned config (e.g. you had no flags in the OS-specific, instance-specific, or alpha-not-feature-gated categories), you may not need this step. If you have flags remaining, however, you will need to incrementally migrate them into your API without breaking backwards compatibility. + +Since moving a field to the config structs implicitly adds a default value for that field, you must override this value with the corresponding flag value as long as the flag is set on the command line. Otherwise, simply upgrading a component to a version that migrates a flag to versioned config could break the command-line API. See [#56171](https://github.com/kubernetes/kubernetes/issues/56171) or [Graduating KubeletFlags subfields to KubeletConfiguration](https://docs.google.com/document/d/18-MsChpTkrMGCSqAQN9QGgWuuFoK90SznBbwVkfZryo) for more detail. + +The Kubelet achieves this by constructing a flag set that can parse the entire command line, but only populates the config struct as a result of parsing. All non-config flags registrations target mock values, while config flags target real values. + +The mock values for global flags are generated by the below helper in the Kubelet, which substitutes values with noop Set operations. NoOp is implemented by [k8s.io/apiserver/pkg/util/flag/noop.go](https://github.com/kubernetes/apiserver/blob/master/pkg/util/flag/noop.go). + + +<table> + <tr> + <td>cmd/kubelet/app/server.go + </td> + </tr> + <tr> + <td>// newFakeFlagSet constructs a pflag.FlagSet with the same flags as fs, but where +<p> +// all values have noop Set implementations +<p> +func newFakeFlagSet(fs *pflag.FlagSet) *pflag.FlagSet { +<p> + ret := pflag.NewFlagSet("", pflag.ExitOnError) +<p> + ret.SetNormalizeFunc(fs.GetNormalizeFunc()) +<p> + fs.VisitAll(func(f *pflag.Flag) { +<p> + ret.VarP(flag.NoOp{}, f.Name, f.Shorthand, f.Usage) +<p> + }) +<p> + return ret +<p> +} + </td> + </tr> +</table> + + +We mock component flags by simply targeting a throwaway flags struct. The config flags are simply registered via the AddKubeletConfigFlags function. + +Though it is usually sufficient to enforce precedence at flag granularity, for some map fields you may instead wish to enforce precedence at key-value pair granularity. It is generally simpler to avoid doing so, but the FeatureGates field is one example where the Kubelet chooses a piecewise precedence semantic: the key-value pairs from the command line and config file are merged, with the command-line pairs taking precedence. This was done specifically to enable feature rollout via the alpha Dynamic Kubelet Config feature, even when some feature gates are set on the command-line. + + +<table> + <tr> + <td>cmd/kubelet/app/server.go + </td> + </tr> + <tr> + <td>// Remember original feature gates, so we can merge with flag gates later +<p> +original := kc.FeatureGates +<p> +// re-parse flags +<p> +if err := fs.Parse(args); err != nil { +<p> + return err +<p> +} +<p> +// Add back feature gates that were set in the original kc, but not in flags +<p> +for k, v := range original { +<p> + if _, ok := kc.FeatureGates[k]; !ok { +<p> + kc.FeatureGates[k] = v +<p> + } +<p> +} + </td> + </tr> +</table> + + + +### Validate the config + +At this point, you should have a configuration that is ready for validation: + + + +* A config file was loaded, if specified. +* Relative paths in the config file were resolved relative to the location of the config file. + * Note that relative paths from flags are implicitly relative to the Kubelet's working directory, as this is the default behavior of Go's file system utilities. +* Flag precedence has been enforced, including feature gate merging. + +The next step is to validate this configuration with the validation functions that accompany your API group. If your validation incorporates feature gates, remember to set the feature gates from the config before validating. You can use the [FeatureGate.SetFromMap](https://github.com/kubernetes/kubernetes/blob/52ed0368f8d076236ada19b09828f2f9e2ebb6ef/staging/src/k8s.io/apiserver/pkg/util/feature/feature_gate.go#L84) function to set the gates directly from the field in your config object. + +**🎉🎉Congrats, your component now has a versioned config file API! 🎉🎉** + + +# Remaining work + +This section enumerates known issues and shares my opinion on the way forward. The below is all open to discussion. + + +## Versioned config for third-party flag values + +One item we have not discussed in detail is how to migrate flags from third-party libraries to your versioned config file API. + +It is, of course, best if you don't expose these flags at all, but in some cases (e.g. _glog_), doing so is infeasible. In these cases, you can provide a field in your config API for each third-party value and manually plumb the field's value through a flag set with the corresponding flag registered to it. + +**Be careful! If a third-party library removes a flag in an update (say, their deprecation policy doesn't align with ours), you'll still be on the hook for maintaining the behavior of fields in your config API.** + + +## Unsolved problems + + +### Per-instance configuration + +We left instance-specific parameters as flags, because a single config source may need to be shared across multiple instances. We should not, however, abandon these parameters to the command-line. + +The most obvious solution, to me, seems to be the introduction of an --instance-config flag, which accepts a file that contains the instance-specific parameters in a format defined by the component's config API group. This way, instance-specific parameters can be covered by the versioned config file API. + + +### OS-specific configuration + +We left operating-system-specific parameters as flags, because we haven't really had a discussion on how best to represent these in our config APIs. Similar to per-instance configuration, we should not abandon these parameters to the command-line. + +I think that a simple and flexible solution is to prefix OS-specific fields with the name of the OS: + + + +* This helps avoid the complexity of having a top-level substructure for each supported OS, or OS specific substructures of general substructures. +* These fields should always be optional and omitempty, so that they can be omitted in environments where they are not necessary. +* If we see common fields, it should be relatively easy to add a non-prefixed field that works across multiple supported operating systems. +* We'll likely need to ensure that defaulting and validation only process OS-specific fields for the OS we are currently running on. +* It would be really nice if we could have API machinery that could mark which fields are supported on which OSes. + + +# TODOs + +**TODO: Dig through the following and identify things I missed in this doc:** + +Original dynamic config proposal discussion, esp. points about API policies: https://github.com/kubernetes/kubernetes/pull/29459#issuecomment-271990251 + +Major related PRs: + + + +* [Graduate kubeletconfig API group to beta](https://github.com/kubernetes/kubernetes/pull/53833) +* [Deprecate KubeletConfiguration flags](https://github.com/kubernetes/kubernetes/pull/60148) + +Other Related PRs (massaging KubeletConfiguration object to beta quality, fixing flag precedence, testing, correct loading behavior, etc): + + + +* [Make feature gates loadable from a map[string]bool](https://github.com/kubernetes/kubernetes/pull/53025) +* [Mulligan: Remove deprecated and experimental fields from KubeletConfiguration](https://github.com/kubernetes/kubernetes/pull/53088) +* [Move --enable-cusom-metrics to KubeletFlags and mark it deprecated](https://github.com/kubernetes/kubernetes/pull/54154) +* [Move runtime-related flags from KubeletConfiguration to KubeletFlags](https://github.com/kubernetes/kubernetes/pull/54160) +* [Lift embedded structure out of ManifestURLHeader field](https://github.com/kubernetes/kubernetes/pull/54643) +* [Lift embedded structure out of eviction-related KubeletConfiguration fields](https://github.com/kubernetes/kubernetes/pull/54823) +* [ColonSeparatedMultimapStringString: allow multiple Set invocations with default override](https://github.com/kubernetes/kubernetes/pull/55254) +* [Move 'alpha' KubeletConfiguration fields that aren't feature-gated and self-registration fields to KubeletFlags](https://github.com/kubernetes/kubernetes/pull/55562) +* [Kubelet: Relative paths in local config file](https://github.com/kubernetes/kubernetes/pull/55648) +* [Add kubeletconfig round trip test](https://github.com/kubernetes/kubernetes/pull/55961) +* [seccomp is an alpha feature and not feature gated](https://github.com/kubernetes/kubernetes/pull/55983) +* [Kubelet flags take precedence over config from files/ConfigMaps](https://github.com/kubernetes/kubernetes/pull/56097) +* [flag precedence redo](https://github.com/kubernetes/kubernetes/pull/56995) +* [Refactor kubelet config controller bootstrap process](https://github.com/kubernetes/kubernetes/pull/57488) +* [Explicit kubelet flags](https://github.com/kubernetes/kubernetes/pull/57613) +* [Fix PodCIDR flag: defaults come from the object, not as literal args to the flag function](https://github.com/kubernetes/kubernetes/pull/57621) +* [Replace --init-config-dir with --config](https://github.com/kubernetes/kubernetes/pull/57624) +* [e2e node framework can generate a base kubelet config file](https://github.com/kubernetes/kubernetes/pull/57638) +* [More default fixups for Kubelet flags](https://github.com/kubernetes/kubernetes/pull/57770) +* [Move some old security controls to KubeletFlags and mark them deprecated](https://github.com/kubernetes/kubernetes/pull/57851) +* [Turn KubeletConfigFile on in e2enode tests](https://github.com/kubernetes/test-infra/pull/5637) +* [Removal of KubeletConfigFile feature gate: Step 1](https://github.com/kubernetes/kubernetes/pull/58760) +* [Removal of KubeletConfigFile feature gate: Step 2 (stop setting KubeletConfigFile)](https://github.com/kubernetes/test-infra/pull/6490) +* [Removal of KubeletConfigFile feature gate: Step 3 (final)](https://github.com/kubernetes/kubernetes/pull/58978) +* [--generate-kubelet-config-file=true is now default](https://github.com/kubernetes/test-infra/pull/6654) +* [Fix PodPidsLimit and ConfigTrialDuration on internal KubeletConfig type](https://github.com/kubernetes/kubernetes/pull/59062) +* [Add 'none' option to EnforceNodeAllocatable](https://github.com/kubernetes/kubernetes/pull/59515) +* [remove CAdvisorPort from KubeletConfiguration struct](https://github.com/kubernetes/kubernetes/pull/59580) +* [Bury KubeletConfiguration.ConfigTrialDuration for now](https://github.com/kubernetes/kubernetes/pull/59628) +* [Secure Kubelet's componentconfig defaults while maintaining CLI compatibility](https://github.com/kubernetes/kubernetes/pull/59666) +* [Ignore 0% and 100% eviction thresholds](https://github.com/kubernetes/kubernetes/pull/59681) +* [expunge the word 'manifest' from Kubelet's config API](https://github.com/kubernetes/kubernetes/pull/60314) diff --git a/committee-code-of-conduct/README.md b/committee-code-of-conduct/README.md index af13794a..37ae5129 100644 --- a/committee-code-of-conduct/README.md +++ b/committee-code-of-conduct/README.md @@ -14,10 +14,10 @@ The [charter](charter.md) defines the scope and governance of the Code of Conduc ## Members -* Danielle Lancashire (**[@endocrimes](https://github.com/endocrimes)**), VMware +* Jason DeTiberus (**[@detiber](https://github.com/detiber)**), Cisco +* Danielle Lancashire (**[@endocrimes](https://github.com/endocrimes)**), Independent * Hilliary Lipsig (**[@hlipsig](https://github.com/hlipsig)**), RedHat * Jeremy Rickard (**[@jeremyrickard](https://github.com/jeremyrickard)**), Microsoft -* Nabarun Pal (**[@palnabarun](https://github.com/palnabarun)**), VMware * Xander Grzywinski (**[@salaxander](https://github.com/salaxander)**), Microsoft ## Contact @@ -61,6 +61,7 @@ The Code of Conduct Committee sincerely thanks our emeritus committee members fo - Jaice Singer Dumars (Google) - Jennifer Rondeau (Stripe) - Carolyn Van Slyck (Microsoft) +- Eric Paris (Red Hat) - Paris Pittman (Apple) - Aeva Black (Microsoft) - Tasha Drew (VMware) diff --git a/committee-steering/README.md b/committee-steering/README.md index 75961a15..0d2d4552 100644 --- a/committee-steering/README.md +++ b/committee-steering/README.md @@ -21,12 +21,12 @@ The [charter](https://git.k8s.io/steering/charter.md) defines the scope and gove ## Members +* Benjamin Elder (**[@BenTheElder](https://github.com/BenTheElder)**), Google * Christoph Blecker (**[@cblecker](https://github.com/cblecker)**), Red Hat -* Davanum Srinivas (**[@dims](https://github.com/dims)**), VMware +* Carlos Tadeu Panato Jr. (**[@cpanato](https://github.com/cpanato)**), Chainguard, Inc * Stephen Augustus (**[@justaugustus](https://github.com/justaugustus)**), Cisco -* Jordan Liggitt (**[@liggitt](https://github.com/liggitt)**), Google * Bob Killen (**[@mrbobbytables](https://github.com/mrbobbytables)**), Google -* Paris Pittman (**[@parispittman](https://github.com/parispittman)**), Apple +* Nabarun Pal (**[@palnabarun](https://github.com/palnabarun)**), VMware * Tim Pepper (**[@tpepper](https://github.com/tpepper)**), VMware ## Contact diff --git a/committee-steering/governance/README.md b/committee-steering/governance/README.md index 8fda6940..e75c2e5a 100644 --- a/committee-steering/governance/README.md +++ b/committee-steering/governance/README.md @@ -43,7 +43,7 @@ As part of this we will define roles for the [OARP] process (Owners, Approvers, If more substantial changes are desired it is advisable to socialize those before drafting a PR. - The steering committee will be looking to ensure the scope of the SIG as represented in the charter is reasonable (and within the scope of Kubernetes) and that processes are fair. - For large changes alert the rest of the Kubernetes community (Participants) as the scope of the changes becomes clear. - Sending mail to [dev@kubernetes.io] and/or announcing at the community meeting are a good ways to do this. + Sending mail to [dev@kubernetes.io] and (optionally) announcing it in the #kubernetes-contributors slack channel. If there are questions about this process please reach out to the steering committee at [steering@kubernetes.io]. diff --git a/committee-steering/governance/annual-reports.md b/committee-steering/governance/annual-reports.md index 84e13121..a4209cbc 100644 --- a/committee-steering/governance/annual-reports.md +++ b/committee-steering/governance/annual-reports.md @@ -201,7 +201,7 @@ Operational tasks in [sig-governance.md]: [ ] 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 $YYYY are linked from [README.md] and updated/uploaded if needed -[ ] Did you have community-wide updates in $YYYY (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: +[ ] Did you have community-wide updates in $YYYY (e.g. kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: - - diff --git a/committee-steering/governance/sig-governance.md b/committee-steering/governance/sig-governance.md index fc1e6108..81d9c514 100644 --- a/committee-steering/governance/sig-governance.md +++ b/committee-steering/governance/sig-governance.md @@ -16,9 +16,6 @@ repo [Kubernetes Community YouTube playlist] - Report activity with the community via the dev@kubernetes.io mailing list at least once a year. - - Each SIG is assigned an update during the [monthly community meeting] - throughout the year from sig-contributor-experience. The meeting host will publish the notes to the - kubernetes-dev mailing list with the update. - This is separate from the [annual report]. - Participate in release planning meetings and retrospectives, and burndown meetings, as needed @@ -115,7 +112,6 @@ Subproject contributors (as applicable). groups like SIGs and the Steering Committee but *MAY* delegate the actual communication and creation of content to other contributors where appropriate -- *MUST* provide updates through the [monthly community meeting] - *MUST* present yearly [annual report] for the group but *SHOULD* get help with curation from other SIG participants @@ -276,6 +272,5 @@ Issues impacting multiple subprojects in the SIG should be resolved by either: [Marketing Council]: /communication/marketing-team/role-handbooks/council.md [Events Lead]: /events/events-team/events-lead.md [PR Wrangler]: https://kubernetes.io/docs/contribute/participate/pr-wranglers/ -[monthly community meeting]: /events/community-meeting.md [Inclusive Open Source Community Orientation course]: https://training.linuxfoundation.org/training/inclusive-open-source-community-orientation-lfc102/ [technical-lead.md]: /contributors/chairs-and-techleads/technical-lead.md diff --git a/communication/OWNERS b/communication/OWNERS index 01c24fe2..78e2cbc6 100644 --- a/communication/OWNERS +++ b/communication/OWNERS @@ -1,7 +1,6 @@ # See the OWNERS docs at https://go.k8s.io/owners reviewers: - - parispittman - jdumars - idvoretskyi - jeefy @@ -9,10 +8,10 @@ reviewers: - markyjackson-taulia approvers: - mrbobbytables - - parispittman - sig-contributor-experience-leads emeritus_approvers: - castrojo + - parispittman labels: - sig/contributor-experience - area/community-management diff --git a/communication/README.md b/communication/README.md index 54033338..feb96d0e 100644 --- a/communication/README.md +++ b/communication/README.md @@ -125,7 +125,7 @@ Documentation is published at https://kubernetes.io - [website guidelines] Owned and operated by sig-contribex [community management] subproject. [Kubernetes Community channel] - recordings of community group meetings, Thursday -community call, meet our contributors, office hours, and more [YouTube Guidelines]. +community call, and more [YouTube Guidelines]. #### Kubernetes Blog @@ -140,10 +140,6 @@ For questions about installing, running, or troubleshooting Kubernetes, please start with the [troubleshooting guide]. If that doesn't answer your question(s), try to post on discuss.kubernetes.io or if you think you found a bug, please [file an issue]. -### Office Hours - -Office hours are held once a month. Please refer to [the docs][office-hours] -to learn more. Join the conversation on slack under [#office-hours]. ### Other - [r/kubernetes] - reddit channel owned and operated by community members and @@ -201,7 +197,6 @@ place! [these instructions]: /communication/slack-guidelines.md#requesting-a-channel [community management]: /sig-contributor-experience#community-management [kubeweekly]: https://kubeweekly.io/ -[the docs]: /events/office-hours.md [r/kubernetes]: https://www.reddit.com/r/kubernetes/ [awesome kubernetes list]: https://github.com/ramitsurana/awesome-kubernetes [Last Week in Kubernetes Development]: http://lwkd.info/ @@ -218,11 +213,8 @@ place! [blog team]: /sig-docs/blog-subproject [submit a blog post]: https://kubernetes.io/docs/contribute/start/#write-a-blog-post [zoom guidelines]: ./zoom-guidelines.md -[the doc]: /events/office-hours.md [moderators]: ./moderators.md [slack moderators]: ./moderators.md#slack [#kubernetes-contributors]: https://app.slack.com/client/T09NY5SBT/C09R23FHP [#sig-contribex]: https://app.slack.com/client/T09NY5SBT/C1TU9EB9S -[#office-hours]: https://app.slack.com/client/T09NY5SBT/C6RFQ3T5H -[office-hours]: /events/office-hours.md [LWKD]: https://lwkd.info diff --git a/communication/best-practices.md b/communication/best-practices.md index 188ee00a..39cdf13c 100644 --- a/communication/best-practices.md +++ b/communication/best-practices.md @@ -94,7 +94,7 @@ procedure, see the Gmail help page on [Creating rules to filter your email]. These suggestions come largely from an old [kubernetes-dev] mailing list [thread] on Gmail filters for Kubernetes. -[kubernetes-dev]: https://groups.google.com/g/kubernetes-dev +[kubernetes-dev]: https://groups.google.com/a/kubernetes.io/g/dev [thread]: https://groups.google.com/forum/#!topic/kubernetes-dev/5qU8irU7_tE/discussion <!-- shared links --> diff --git a/communication/contributor-comms/CHARTER.md b/communication/contributor-comms/CHARTER.md new file mode 100644 index 00000000..cde7d25c --- /dev/null +++ b/communication/contributor-comms/CHARTER.md @@ -0,0 +1,51 @@ +# Kubernetes Contributor Communications Team Charter + +## Summary + +The mission of the Kubernetes Contributor Communications team (Contributor Comms for short) is to elevate the hard work being done throughout the Kubernetes community by its contributors. Promoting the work of contributors both internally within the contributor community, and externally is at the core of the Contributor Comms team’s work. The goal of this work is to improve the overall sustainability of the project by giving or elevating information to contributors so they stay well informed. + +## Ethos/Vision + +This group's work is in support of the upstream Kubernetes community only (the open source project). As such it will adhere to the [Kubernetes Community Values](/values.md#kubernetes-community-values). The core value we feel strongest about is [Community over product or company](/values.md#community-over-product-or-company). The makeup of this team will be from all walks of life including vendors. The work of the Kubernetes community should always be prioritized over vendor created works. Contributor Comms team members are expected to act in the interest of the community and not their employers while performing community duties. + +## Goals + +The goal of the Contributor Comms team is to be of service to the community by being leaders in contributor storytelling. It will act to facilitate conversations across the Kubernetes community and share compelling stories about contributors. It will also act as a voice of the community to broaden the reach and effectiveness of community communications. Facilitating those communications is a critical function of this team. + +## Out of Scope + +This team operates independently from Cloud Native Computing Foundation (CNCF) operations. The Team works with CNCF as needed but it exists within the Kubernetes governance model and is not a part or extension of CNCF Marketing. As such, this is not the team to reach out to about official CNCF Events and/or KubeCon. #kubecon on slack can be a helpful resource there. This team can assist in some ways with other CNCF projects but, the first priority of the team is Kubernetes. + +## Governance + +The Contributor Comms subproject welcomes and encourages its members to take on leadership roles in their contributions. The group defines the areas of its work such as social media, blogging, etc. and creates associated leadership roles accordingly. Members are encouraged to pursue any interest in specific areas as contributing team members, leads, or shadows. Leadership roles are defined in the subproject’s [role handbooks](../role-handbooks/). + +## Roles and Subproject Management + +General subproject leadership is handled by the Contributor Comms Subproject Lead(s). Specific subproject responsibilities are also broken down into areas with their own lead roles, as defined here: + +* Contributor Comms Subproject Lead +* [Social Media Coordinator](../role-handbooks/Social-Media.md) +* [Comms Tech Lead](../role-handbooks/Comms-Tech-Lead.md) +* [Comms Event Lead](../role-handbooks/Comms-Event-Lead.md) +* [Comms Blog Coordinator](../role-handbooks/blog-coordinator.md) +* [Storytellers](../role-handbooks/storytellers.md) & other members +* Emeritus (previous team members that we had the privilege of working with) + +All roles can have multiple shadows and should have at least one shadow. All leads should actively recruit members and shadows for the entire team. + +Roles are flexible and subject to change. + +Roles are occupied or available as indicated on our [README.md](https://github.com/kubernetes/community#readme). + +### Decision Making + +Decisions affecting all of Contributor Comms are made primarily led by the Contributor Comms Subproject Lead[s]. Decisions are generally made by lazy consensus with the goal of everyone getting a say, but leads are ultimately responsible for making the decision. If team members do not agree with one or more decisions made on behalf of the team, this should be raised to the subproject lead[s] as well as the SIG Contributor Experience leads to facilitate a resolution. + +Leads have the responsibility and autonomy to decide what is right for their portion of the group's division of work. The same escalation path can be used in case of disagreement that cannot be resolved by internal discussion. + +### Off-Ramp + +Things change, priorities get optimized, life happens. Having an easy on and off ramp is important to this team. If a lead needs to take an extended absence or leave the team, a shadow would be offered the lead position prior to seeking a lead elsewhere. Therefore moving from shadow to lead and vice versa should be made as simply as possible by continued communications from this team about its members, roles, successes, and failures. + +In the case where no shadow is available, other team members have the responsibility to cover the role. Concerns for time or ability to cover work can be escalated to advisors and SIG Contributor Experience leads as necessary. diff --git a/communication/marketing-team/OWNERS b/communication/contributor-comms/OWNERS index e20309c7..a18dd739 100644 --- a/communication/marketing-team/OWNERS +++ b/communication/contributor-comms/OWNERS @@ -1,16 +1,24 @@ # See the OWNERS docs at https://go.k8s.io/owners reviewers: + - Atharva-Shinde + - AvineshTripathi - chris-short - - onlydole - - parispittman + - fsmunoz + - imnmo + - kaslin approvers: - - parispittman - - Pensu - - rajula96reddy + - Atharva-Shinde + - AvineshTripathi + - chris-short + - fsmunoz + - imnmo - kaslin emeritus_approvers: + - Pensu - mbbroberg + - parispittman + - rajula96reddy labels: - sig/contributor-experience - area/contributor-comms diff --git a/communication/marketing-team/README.md b/communication/contributor-comms/README.md index c7a2b0a0..04c3adf6 100644 --- a/communication/marketing-team/README.md +++ b/communication/contributor-comms/README.md @@ -1,7 +1,6 @@ -# Upstream Marketing +# Contributor Communications -The Upstream Marketing Contributor Communications team (Contributor Comms for short) is part of the `community-management` subproject in -[Contributor Experience]. View our [charter] to learn more about us. +The Contributor Communications team (Contributor Comms for short) is part of the `community-management` subproject in [Contributor Experience]. View our [charter] to learn more about us. ## Purpose @@ -9,11 +8,13 @@ To better inform the Kubernetes contributor community and highlight their work t | Area & Handbook Link | Team | Notes | | --- | --- | --- | -| [Marketing Council] Program Lead | @mbbroberg, shadow: @JasonMorgan,| advisors: @parispittman, @chris-short | -| [Marketing Council] Promotion Lead |@kaslin, shadow: @Debanitrkl | advisors: @parispittman, @chris-short | -| [Marketing Council] Liaison Lead | @rajula96reddy, shadow: `OPEN` | Shadow role is available. | -| Liaisons | release: @rajula96reddy, docs: `OPEN` | Are you a SIG that wants support from Contributor Comms? Ping the liaison lead! | -| [Storytellers] & other members | @kunal-kushwaha, @gkarthiks, @dewan-ahmed, @joelbyronbarker, Sladyn Nunes, @hpopal11 | New to Contributor Comms? Add your name here! +| Subproject Lead | @kaslin, @chris-short | Shadow role is available. | +| [Social Media Coordinator](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/role-handbooks/Social-Media.md) |@kaslin | Shadow role is available. | +| [Comms Tech Lead](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/role-handbooks/Comms-Tech-Lead.md) | @Atharva-Shinde, @imnmo | @markarranz (shadow) | +| [Comms Event Lead] | @AvineshTripathi | Shadow role is available. | +| [Comms Blog Coordinator](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/role-handbooks/blog-coordinator.md) | @fsmunoz | Shadow role is available. | +| [Storytellers] & other members | @hpopal11, @Atharva-Shinde | New to Contributor Comms? Add your name here! | +| Emeritus | @parispittman, @mbbroberg | ## Contact Us! @@ -38,9 +39,11 @@ Let us know you are interested and if you have any questions. [charter]: ./CHARTER.md [Could be you!]: #could-be-you [Contributor Experience]: /sig-contributor-experience -[Marketing Council]: ./role-handbooks/editor.md [Internal Communications]: ./role-handbooks/internal-marketing.md [Social Media]: ./role-handbooks/social-media.md +[Comms Tech Lead]: ./role-handbooks/Comms-Tech-Lead.md +[Comms Event Lead]: ./role-handbooks/Comms-Event-Lead.md +[Comms Blog Coordinator]: ./role-handbooks/blog-coordinator.md [Storytellers]: ./role-handbooks/storytellers.md [Designer]: ./role-handbooks/wip-roles.md [kubernetes/community]: https://github.com/kubernetes/community/issues diff --git a/communication/contributor-comms/role-handbooks/Comms-Events.md b/communication/contributor-comms/role-handbooks/Comms-Events.md new file mode 100644 index 00000000..28375fea --- /dev/null +++ b/communication/contributor-comms/role-handbooks/Comms-Events.md @@ -0,0 +1,42 @@ +# Comms Events Lead Role Handbook + +## Overview + +As Event Co-ordinator Lead, you are responsible for +- connecting with organizers of contributor events such as the monthly community meeting or contributor summits +- working with the Contributor Comms team to ensure communications about events are being created and promoted through various means including email (k-dev), slack (slack bot, etc), twitter (K8sContributors), etc. + +Time Commitment: + +1-3 hours a week from 0-1.5 months in +2-5 hours a week from 1.5 months-to event + +## Minimum skills and Requirements + +- Kubernetes github org [membership](https://github.com/kubernetes/community/blob/master/community-membership.md) +- familiarity with the workflow of [#sig-contributor-comms](https://github.com/kubernetes/community/tree/master/communication/contributor-comms) +- has understanding of the [social guidelines](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/storytelling-resources/social-guidelines.md) +- Good grasp on general marketing activities surrounding events +- Understanding of common forms of marketing communications +- Event planning experience is a plus +- Willing and able to directly coordinate across timezones and contributor groups +- commitement for the role is relative and would vary depending upon events + +## Expectations and tasjs + +The core task for the role would be to stay current on [upcoming](https://www.kubernetes.dev/events/) events. Planning should be done with the team about the event, target audience, mode of communication, timeline, etc. This could be coordinated via a call or async conversatios. Sometimes, some big events might require you to join a weekly or bi-weekly call. The following are the possible tasks to perform (may vary depending upon the event). + +- Creating a communication schedule - what, when, how, who +- Promoting on different platforms like + - emailing on [kdev](https://github.com/kubernetes/community/blob/master/communication/mailing-list-guidelines.md) + - twitting from main or k8scontributor accounts + - coordinating with CNCF(if required) + - sending slack notification to various channels(depending on the target audience) +- Assisting in the entire blog process +- Coordinating with Contributor Comms team members to ensure above tasks are completed + +Timeline for the communication can be crucial parameters so ideally timelines should at least begin to be decided weeks before the event. + +## Shadowing the Event Coordinator Role + +This role can include one or more shadows. The Event Coordinator Lead can delegate/assign tasks to the shadows. The expectation from a shadow is to work with the lead to develop a plan to adopt ownership of the role over time, including all tasks listed in the "Expectations and Tasks" section. The shadows to the Event Coordinator Lead are responsible for handling all Event Coordinator lead related activities in the absence of the Lead. diff --git a/communication/contributor-comms/role-handbooks/Comms-Tech-Lead.md b/communication/contributor-comms/role-handbooks/Comms-Tech-Lead.md new file mode 100644 index 00000000..3a5605de --- /dev/null +++ b/communication/contributor-comms/role-handbooks/Comms-Tech-Lead.md @@ -0,0 +1,55 @@ +# Comms Tech Lead Role Handbook + +## Overview + +This handbook outlines expectations and responsibilities for Tech Leads as well as Contributor Comms team members who wish to contribute to technical efforts. + +Tech leads' contributions further the Contributor Comms team's efforts to communicate contributors' stories by resolving technical issues and decisions around [contributor-site](https://www.kubernetes.dev/), social media automation tools [kubernetes-sigs/contributor-tweets](https://github.com/kubernetes-sigs/contributor-tweets), and [slack-bot](https://github.com/kubernetes-sigs/slack-infra/tree/main/slack-post-message). + +[contributor-site](https://www.kubernetes.dev/) is a one-stop for Kubernetes contributor content and news. It brings important documentation scattered throughout the project into one central location. + +Along with contributor-site there exist two automation tools that help: +1. To create tweets (k8scontributors) via GitHub actions (see: [workflow](https://github.com/kubernetes-sigs/contributor-tweets/blob/main/.github/workflows/main.yml)) +2. To broadcasts messages across multiple slack channels (see: [slack-bot](https://github.com/kubernetes-sigs/slack-infra/tree/main/slack-post-message)) + +The [contributor-tweets repo](https://github.com/kubernetes-sigs/contributor-tweets) utilizes open source Github action [twitter-together](https://github.com/gr2m/twitter-together) project to automate tweet approval from an issue. + +## Minimum Skills and Requirements + +- Are a member of the [Kubernetes GitHub Org] +- Good knowledge of Node.js, Hugo(docsy theme and frontmatter) +- Have a basic experience in Go (for Slack bot) +- Have a good understanding of Github actions +- Available to either attend regular Contributor Comms meetings or collaborate asynchronously via the #sig-contribex-comms channel in the Kubernetes Slack + +### Expected Time Investment + +Team leads: 4-5 hours per week. +Team members: 2-3 hours per week. + +## General Expectations + +- Be welcoming, be yourself +- Take ownership of an issue and submit a PR for repositories like (especially if it's quick or relates to work you're already doing) Contributor-site, tweets, and, slack bot +- Have an understanding of what an issue is about and able to triage them, or know who to contact to determine the required information +- Coordinate work to fix any issues in automation tools to ensure valid tweet requests are fulfilled +- Train new leads + +Team members will be expected to keep an eye out for news or issues related to slack bot or Github automation. Common sources of such announcements are the k-dev mailing list and the #contributor-comms channel on Slack. + +## Associates Overview (Shadow) + +Team members who wish to become technical leads shadow should express this desire to the current lead. + +Leads should work with shadows to understand their capacity to take on the needs of the lead role and work with the shadow on a plan for them to take on responsibility including: + +* General familiarity with our repositories and automation tools +* Willingness and ability to follow up with contributors about issues, on Github, Slack, and email, as appropriate +* Ability to file well-crafted Kubernetes issues, including labeling and prow commands +* General knowledge of our SIG system and SIGs' areas of responsibility or knowing who to contact to determine the required information + +Additionally, the following qualifications make a candidate more suitable for the technical team, but are not requirements: + +* Prior involvement with the Contributor Comms team and the contributor experience team +* Experience with Github actions and Github workflow +* A basic understanding of Golang diff --git a/communication/marketing-team/role-handbooks/Social-Media.md b/communication/contributor-comms/role-handbooks/Social-Media.md index 305082dc..f1a1b36b 100644 --- a/communication/marketing-team/role-handbooks/Social-Media.md +++ b/communication/contributor-comms/role-handbooks/Social-Media.md @@ -24,9 +24,9 @@ Team members: 1-3 hour per week. ## General Expectations -- Rules for social posts and more can be found in [social guidelines](https://github.com/kubernetes/community/blob/master/communication/marketing-team/storytelling-resources/social-guidelines.md) +- Rules for social posts and more can be found in [social guidelines](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/storytelling-resources/social-guidelines.md) - Be welcoming, be yourself -- Understanding, communicating, and setting/adjusting [social guidelines](https://github.com/kubernetes/community/blob/master/communication/marketing-team/storytelling-resources/social-guidelines.md) +- Understanding, communicating, and setting/adjusting [social guidelines](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/storytelling-resources/social-guidelines.md) - Coordinating work to create tweets, ensuring tweet requests are fulfilled - Working with other Contributor Comms leads, such as the Event Coordinator Lead, on social media tasks - Approving tweet PRs on [kubernetes-sigs/contributor-tweets](https://github.com/kubernetes-sigs/contributor-tweets) diff --git a/communication/contributor-comms/role-handbooks/Subproject-Lead.md b/communication/contributor-comms/role-handbooks/Subproject-Lead.md new file mode 100644 index 00000000..1287c6b9 --- /dev/null +++ b/communication/contributor-comms/role-handbooks/Subproject-Lead.md @@ -0,0 +1,68 @@ + +# Contributor Comms Subproject Lead Role Handbook + +## Overview + +This handbook outlines expectations and responsibilities for Kubernetes Contributor Communications Subproject Leads and shadows. + +Contributor Comms Subproject Leads are general, top level leads of any and all matters relating to the subproject. Individual area concerns should generally be handled by the area leads, but Subproject Leads may act as advisors or interim leads in cases where subproject leads are not available and a decision is needed. + +General responsibilities which do not fall under an area lead may be assumed to be the responsibility of the Subproject Lead[s]. + + +## **Minimum Skills and Requirements** + +A subproject lead should be: + + + +* A member of the [Kubernetes GitHub Org](https://github.com/kubernetes/org) +* Available to attend/lead regular Contributor Comms meetings and collaborate asynchronously via the #sig-contribex-comms channel in the Kubernetes Slack +* Able and willing to actively recruit members and shadows for the benefit of the entire team and the contributor +* [Preferred] Familiar with managing a social media presence by either having personal accounts or managing another account (brand, OSS project, employer, local nonprofit, etc) + +### **Expected Time Investment** + + +Team leads: 3-5 hours per week. Shadows: 1-3 hours per week. + + +## **General Expectations** + +Contributor Communications Subproject Leads are responsible for a number of tasks that are delegated to the team from SIG Contributor Experience, this includes: + +Subproject Lead-specific responsibilities include: + + + +* Running Subproject Meetings +* Uphold the Kubernetes Code of Conduct especially in terms of personal behavior and responsibility +* Actively promote diversity and inclusion in the subproject +* Report the subproject status at events and community meetings wherever possible + * SIG meetings +* Managing ownership of subproject repos (such as [kubernetes-sigs/contributor-tweets](https://github.com/kubernetes-sigs/contributor-tweets)) +* Ensuring that role handbooks are created, updated, used, and deprecated as needed +* Managing the Contributor Comms team’s Slack presence + * Alias + * Channel + * Team +* Managing how work is requested of the Contributor Communications Subproject + * Managing issue/request workflows +* Handling emergency communications alongside the social media lead (e.g. passing of a community member, highly sensitive topics like dockershim, etc.) +* Understanding, communicating, and setting/adjusting the [subproject charter](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/CHARTER.md) +* Coordinating work as needed among area leads and general team members +* Requesting funds from Kubernetes Steering Committee as needed +* Be welcoming, be yourself +* Finding and training new subproject and area leads as needed + +## **Subproject Lead Shadowing** + + +Team members who wish to become subproject leads should express this desire to the current lead(s). Leads should work with shadows to understand their capacity to take on the needs of the lead role and work with the shadow on a plan for them to take on responsibility including: + + + +* Regular meeting leadership +* Gaining familiarity with key connections, such as the SIG-ContribEx Chairs +* Becoming an owner (approver privileges) on relevant repos +* Understanding and ownership of key subproject docs such as the [README](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/README.md) and [Charter](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/CHARTER.md) diff --git a/communication/contributor-comms/role-handbooks/blog-coordinator.md b/communication/contributor-comms/role-handbooks/blog-coordinator.md new file mode 100644 index 00000000..9eef7b37 --- /dev/null +++ b/communication/contributor-comms/role-handbooks/blog-coordinator.md @@ -0,0 +1,48 @@ +# Blog Coordinator Handbook + +This handbook outlines expectations and responsibilities for Blog coordinator as well as Contributor Comms team members who wish to contribute to blogging activities. + +Writing and sharing articles is one of the ways through which Kubernetes contributors add to the community, and the Blog Coordinator role exists to + +1. Serve as an initial point of contact for content suggestions +2. Help contributors to navigate the existing publishing processes +3. Assist in determining the final publishing targets of the content. +4. Coordinate with SIG-Docs in the publishing process, namely by following and improving the Blogging Guidelines. +5. Coordinate with the rest of the Contributor Comms team, and specifically the Social Media Coordinator, in the best ways to broaden external awareness of published content. + +The [Kubernetes Contributor Blog](https://www.kubernetes.dev/blog/) is one of the most direct points of entry for those that want to share with a wider audience. The role of the Blog Coordinator is to guide those that want to contribute in the best way to do so, while coordinating with the rest of the team (including other Contributor Comms team members) to assign editors, reviewers and other roles to new submissions. + +The Blog Coordinator has an active involvement in defining, with others, the [Blogging Guidelines](https://hackmd.io/@fsm/blog-guidelines), and should constantly seek to improve them, with an eye on the improvement of the contributor experience. + + +### Minimum Skills and Requirements + +Those in this role should ideally: + +* Be a member of the [Kubernetes GitHub Org](https://github.com/kubernetes/) +* Have some familiarity with blogging platforms and editing tools; specific knowledge of Markdown, GitHub and Hugo is a plus. +* Be available to either attend regular Contributor Comms meetings or collaborate asynchronously via the #sig-contribex-comms channel in the Kubernetes Slack + +#### Expected time commitment + +* Team leads: 3-5h per week. +* Team members: 1-3h per week. + +### General Expectations + +1. Be ready to help those wanting to contribute to the blogs. +2. Understand the Blogging Guidelines and assist contributors in following them. +3. Help in determining applicability of the proposed content, with the rest of the team: this includes discussion in the Slack channel or regular meeting. +4. Identify team members that can review blog submissions. +5. Discuss with SIG-Docs, when needed, for possible publication in the main Kubernetes site. +6. Review blog submissions. +7. Open the blog submission PR (with the author as Co-author), or find someone that can assist in this tasks within the Contributor Comms team. +8. Follow up submitted PRs and help with the approval process. + +### Associates Overview (Shadow) + +Team members who which to become Blogging Leads should express their desire to the current lead; leads should work with shadows to understand their capacity to take on the needs of the lead role and work with the shadow on a plan to take on responsibility, including: + +* Become a reviewer of new submitted content. +* Open the PRs and follow them through. +* Provide assistance to new contributors that are asking how to submit content. diff --git a/communication/marketing-team/role-handbooks/storytellers.md b/communication/contributor-comms/role-handbooks/storytellers.md index bd8ce435..a90f72de 100644 --- a/communication/marketing-team/role-handbooks/storytellers.md +++ b/communication/contributor-comms/role-handbooks/storytellers.md @@ -2,7 +2,7 @@ ## Overview -Upstream Marketing depends on great storytelling to get the message out about our amazing community. +Contributor Comms depends on great storytelling to get the message out about our amazing community. It's no secret that governance and technical documentation can be kind of on the boring side. And that's ok–it's not always there for entertainment purposes. It is about providing valuable information and getting you where you need to go. But that said, an important message can be lost without an entertaining messenger. @@ -10,11 +10,11 @@ In this role, Storytellers are here to help Kubernetes contributors hear the lat ## Workflow ⚡️ -Storytelling is welcome in any medium that can be supported by the Upstream Marketing team. This includes but is not limited to written word–as outlined in [blogging guidelines]–or through video following our [YouTube guidelines]. +Storytelling is welcome in any medium that can be supported by the Contributor Comms team. This includes but is not limited to written word–as outlined in [blogging guidelines]–or through video following our [YouTube guidelines]. Storytellers are constantly building new ways to share, and these resources are gathered in the [storytelling resources folder]. -### Upstream Marketing Process +### Contributor Comms Process #### Idea Paths @@ -22,7 +22,7 @@ There are multiple ways to successfully contribute a Kubernetes blog post. Here **To start:** -* Open a [Contributor Comms Requests issue](https://github.com/kubernetes/community/issues) to share your blog idea, or attend an [Upstream Marketing team](https://github.com/kubernetes/community/tree/master/communication/marketing-team) meeting to discuss it ahead of time +* Open a [Contributor Comms Requests issue](https://github.com/kubernetes/community/issues) to share your blog idea, or attend an [Contributor Comms team](https://github.com/kubernetes/community/tree/master/communication/contributor-comms) meeting to discuss it ahead of time **To write:** @@ -30,17 +30,17 @@ There are multiple ways to successfully contribute a Kubernetes blog post. Here * A draft can be written in: * Google Docs or * Markdown (and shared via [Gist](https://gist.github.com/) or [HackMD](https://hackmd.io/)) -* Connect with a storyteller -- if you reach out to Upstream Marketing, you will be paired with someone to help you through writing, editing, and getting your article published +* Connect with a storyteller -- if you reach out to Contributor Comms, you will be paired with someone to help you through writing, editing, and getting your article published * Discussion happens via GitHub issue or through working group meetings -* This includes working with Upstream Marketing team to polish, and format your blog post - * There is not a single canonical format for documents, but we do have [guidelines for effective articles](https://github.com/kubernetes/community/blob/master/communication/marketing-team/blog-guidelines.md#how-to-write-an-effective-blog) +* This includes working with Contributor Comms team to polish, and format your blog post + * There is not a single canonical format for documents, but we do have [guidelines for effective articles](https://github.com/kubernetes/community/tree/master/sig-docs/blog-subproject#blog-guidelines) * There are further technical considerations by the [Blog team](https://github.com/kubernetes/community/blob/4026287dc3a2d16762353b62ca2fe4b80682960a/sig-docs/blog-subproject/README.md#submit-a-post) When it's ready, submit the blog post: * Go to the `kubernetes/website` repository * Open a PR with your added blog post - * If you need help with this process, Upstream Marketing will look to pair you with someone for PR and shepherd it through the review cycle + * If you need help with this process, Contributor Comms will look to pair you with someone for PR and shepherd it through the review cycle Or if you already have everything you think you need you can: @@ -72,7 +72,7 @@ Anyone is welcome to contribute when they have time. The core expectation of sto If you would like to be listed as a member of the team, here are the expectations: 1. Be prepared to write one blog a quarter and participate in edits to other articles. The time commitment is typically 5-10 hours per quarter depending on the number of blog posts in the review queue. -2. Storytellers are expected to attend at least one upstream marketing team meeting a month or check-in to remain active. +2. Storytellers are expected to attend at least one Contributor Comms meeting a month or check-in to remain active. 3. Remain non-partial: if you receive a request to write about a project, an individual, or a group of people from your employer, you should ask an impartial blogger to write it. 4. As with all contribution to Kubernetes, adhere to the [code of conduct](/code-of-conduct.md), values, and principles of the project. diff --git a/communication/marketing-team/storytelling-resources/blog-guidelines.md b/communication/contributor-comms/storytelling-resources/blog-guidelines.md index d370e187..cadf0cdd 100644 --- a/communication/marketing-team/storytelling-resources/blog-guidelines.md +++ b/communication/contributor-comms/storytelling-resources/blog-guidelines.md @@ -1,6 +1,6 @@ -# Upstream Marketing Blog Guidelines +# Contributor Comms Blog Guidelines -This initiative falls under the [Upstream Marketing Charter](./CHARTER.md). +This initiative falls under the [Contributor Comms Charter](./CHARTER.md). We are looking for Kubernetes-curious community members who are **interested in writing** and **care about getting the word out** to our huge community of users, developers, and contributors of all types. Here's how to get involved. @@ -55,7 +55,7 @@ Anyone is welcome to contribute when they have time. If you would like to be listed as a member of the team, here are the expectations: 1. Be prepared to write one blog a quarter and participate in edits to other articles. The time commitment is typically 5-10 hours per quarter depending on the number of blog posts in the review queue. -2. Bloggers are expected to attend at least one upstream marketing team meeting a month or check-in to remain active. +2. Bloggers are expected to attend at least one Contributor Comms team meeting a month or check-in to remain active. 3. Remain non-partial: if you receive a request to write about a project, an individual, or a group of people from your employer, you should ask an impartial blogger to write it. 4. As with all contribution to Kubernetes, adhere to the [code of conduct](/code-of-conduct.md), values, and principles of the project. diff --git a/communication/marketing-team/storytelling-resources/event-checklist.md b/communication/contributor-comms/storytelling-resources/event-checklist.md index 48549da4..48549da4 100644 --- a/communication/marketing-team/storytelling-resources/event-checklist.md +++ b/communication/contributor-comms/storytelling-resources/event-checklist.md diff --git a/communication/marketing-team/storytelling-resources/example-interview-qs-sig-windows.md b/communication/contributor-comms/storytelling-resources/example-interview-qs-sig-windows.md index 51fe382c..51fe382c 100644 --- a/communication/marketing-team/storytelling-resources/example-interview-qs-sig-windows.md +++ b/communication/contributor-comms/storytelling-resources/example-interview-qs-sig-windows.md diff --git a/communication/marketing-team/storytelling-resources/example-topics.md b/communication/contributor-comms/storytelling-resources/example-topics.md index e71c29d3..e71c29d3 100644 --- a/communication/marketing-team/storytelling-resources/example-topics.md +++ b/communication/contributor-comms/storytelling-resources/example-topics.md diff --git a/communication/marketing-team/storytelling-resources/multichannel-communications.md b/communication/contributor-comms/storytelling-resources/multichannel-communications.md index dd0b786f..dd0b786f 100644 --- a/communication/marketing-team/storytelling-resources/multichannel-communications.md +++ b/communication/contributor-comms/storytelling-resources/multichannel-communications.md diff --git a/communication/marketing-team/storytelling-resources/sig-spotlight-blog-process.md b/communication/contributor-comms/storytelling-resources/sig-spotlight-blog-process.md index 056047d5..29245ef9 100644 --- a/communication/marketing-team/storytelling-resources/sig-spotlight-blog-process.md +++ b/communication/contributor-comms/storytelling-resources/sig-spotlight-blog-process.md @@ -7,8 +7,4 @@ The steps to create a SIG Spotlight blog post are as follows: 3) Interview those people - usually the SIG chairs. We generally recommend doing the interview asynchronously via a Google Doc because written responses are easier to work with. The SIG-Multicluster one was done with a recorded zoom interview but it took a long time to complete. 4) Write a blog post. The post should be in markdown format and we like to do a round of review on a rough draft before creating a PR. We recommend either hackmd.io or Google Docs for this. Google Docs can be converted to markdown fairly easily. -Example past spotlights: - -February 7, 2022 [SIG-Multicluster](https://kubernetes.io/blog/2022/02/07/sig-multicluster-spotlight-2022/) - -June 30, 2020 [SIG-Windows](https://kubernetes.io/blog/2020/06/30/sig-windows-spotlight-2020/) +[Past Spotlights](./sig-spotlights.md) diff --git a/communication/contributor-comms/storytelling-resources/sig-spotlights.md b/communication/contributor-comms/storytelling-resources/sig-spotlights.md new file mode 100644 index 00000000..29ddcb2e --- /dev/null +++ b/communication/contributor-comms/storytelling-resources/sig-spotlights.md @@ -0,0 +1,12 @@ +# SIG Spotlights + +These are all the spot lights that are published to date: + +| SIG | Label | Link | Author | Publish Date | +|-----|-------|------|--------|--------------| +| [Windows](https://github.com/kubernetes/community/blob/master/sig-windows/README.md) | [windows](https://github.com/kubernetes/kubernetes/labels/sig%2Fwindows) | [SIG-Windows Spotlight](https://kubernetes.io/blog/2020/06/30/sig-windows-spotlight-2020/) | Kaslin Fields | 2020-06-30 | +| [Usability](https://github.com/kubernetes/community/blob/master/sig-usability/README.md) | [usability](https://github.com/kubernetes/kubernetes/labels/sig%2Fusability) | [Spotlight on SIG Usability](https://kubernetes.io/blog/2021/07/15/sig-usability-spotlight-2021/) | Kunal Kushwaha | 2021-07-15 | +| [Node](https://github.com/kubernetes/community/blob/master/sig-node/README.md) | [node](https://github.com/kubernetes/kubernetes/labels/sig%2Fnode) | [Spotlight no SIG Node](https://kubernetes.io/blog/2021/09/27/sig-node-spotlight-2021/) | Dewan Ahmed | 2021-09-27 | +| [Multicluster](https://github.com/kubernetes/community/blob/master/sig-multicluster/README.md) | [multicluster](https://github.com/kubernetes/kubernetes/labels/sig%2Fmulticluster) | [Spotlight on SIG Multicluster](https://kubernetes.io/blog/2022/02/07/sig-multicluster-spotlight-2022/) | Dewan Ahmed <br> Chris Short | 2022-02-07 | +| [Docs](https://github.com/kubernetes/community/blob/master/sig-docs/README.md) | [docs](https://github.com/kubernetes/kubernetes/labels/sig%2Fdocs) | [Spotlight on SIG Docs](https://kubernetes.io/blog/2022/08/02/sig-docs-spotlight-2022/) | Purneswar Prasad | 2022-08-02 | +| [Storage](https://github.com/kubernetes/community/blob/master/sig-storage/README.md) | [storage](https://github.com/kubernetes/kubernetes/labels/sig%2Fstorage) | [Spotlight on SIG Storage](https://kubernetes.io/blog/2022/08/22/sig-storage-spotlight/) | Frederico Muñoz | 2022-08-22 | diff --git a/communication/marketing-team/storytelling-resources/social-guidelines.md b/communication/contributor-comms/storytelling-resources/social-guidelines.md index 04a72b72..ecb5b221 100644 --- a/communication/marketing-team/storytelling-resources/social-guidelines.md +++ b/communication/contributor-comms/storytelling-resources/social-guidelines.md @@ -4,7 +4,7 @@ ## General guidelines -All messaging must be consistent with the values and principles of the project and the [ethos/vision of the team](/communication/marketing-team/CHARTER.md#ethosvision). Messaging should be positive and uplifting. Be aware that sarcasm and/or jokes are generally hard to read over a medium such as social media. +All messaging must be consistent with the values and principles of the project and the [ethos/vision of the team](/communication/contributor-comms/CHARTER.md#ethosvision). Messaging should be positive and uplifting. Be aware that sarcasm and/or jokes are generally hard to read over a medium such as social media. Original messages should come out of this teams' accounts at least twice a week (if not more). However, there should be no more than three tweets per hour (including retweets). Retweets, likes, and responses are unlimited, but they should be used thoughtfully to encourage inclusive and kind participation. Use scheduling software as needed to space out messages. All messages should serve a purpose: have an action and/or thumbnail image ("click link for details," "register today," etc. are example actions). Never include photos, user handles, or other personally identifiable information without explicit permission. diff --git a/communication/marketing-team/team-resources.md b/communication/contributor-comms/team-resources.md index 96e27997..96e27997 100644 --- a/communication/marketing-team/team-resources.md +++ b/communication/contributor-comms/team-resources.md diff --git a/communication/marketing-team/CHARTER.md b/communication/marketing-team/CHARTER.md deleted file mode 100644 index 68f3ba13..00000000 --- a/communication/marketing-team/CHARTER.md +++ /dev/null @@ -1,39 +0,0 @@ -# Kubernetes Upstream Marketing Contributor Communications Team Charter - -## Summary - -The mission of the Kubernetes Upstream Marketing Contributor Communications team (Contributor Comms for short) is to elevate the hard work being done throughout the Kubernetes community by its contributors. Promoting the work and helping fill the needs of the Kubernetes community is the driving force behind the Contributor Comms team. The goal of this work is to improve the overall sustainability of the project by giving or elevating information to contributors so they stay well informed. - -## Ethos/Vision - -This group's work is in support of the upstream Kubernetes community only (the open source project). As such it will adhere to the [Kubernetes Community Values](/values.md#kubernetes-community-values). The core value we feel strongest about is [Community over product or company](/values.md#community-over-product-or-company). The makeup of this team will be from all walks of life including vendors. The work of the Kubernetes community should always be prioritized over vendor created works. Contributor Comms team members are expected to act in the interest of the community and not their employers. - -## Goals - -The goal of the Contributor Comms team is to be of service to the community by being leaders in contributor storytelling. It will act to facilitate conversations across the Kubernetes community and share compelling stories about contributors. It will also act as a voice of the community to broaden the reach and effectiveness of community communications. Facilitating those communications is a critical function of this team. - -## Out of Scope - -This team operates independently from Cloud Native Computing Foundation (CNCF) operations. The Team works with CNCF as needed but it exists within the Kubernetes governance model and is not a part or extension of CNCF Marketing. As such, this is not the team to reach out to about official CNCF Events and/or KubeCon. #kubecon on slack can be a helpful resource there. This team can assist in some ways with other CNCF projects but, the first priority of the team is Kubernetes. - -## Governance - -Leadership is divided up between [Marketing Council] team members. This group of leaders divide up the core responsibilities of the team and look to further optimize the experience of both code and non-code contributors. - -### Roles - -Roles are divided up between Marketing Council members and other members, notably Storytellers. Marketing Council members are scoped to have at least one shadow. All leads should actively recruit shadows for the entire team. - -### Decision Making - -Decisions affecting all of Contributor Comms are made primarily led by the program lead as defined in the [Marketing Council]. They come to decision by lazy consensus with the goal of everyone getting a say, but they are responsible for making the decision. If other council members do not agree with one or more decisions made on behalf of the team, this should be raised to the advisors as well as the SIG Contributor Experience leads to facilitate a resolution. - -Other council leads have the responsibility and autonomy to decide what is right for their portion of the council's division of work. The same escalation path can be used in case of disagreement that cannot be resolved by internal discussion. - -### Off-Ramp - -Things change, priorities get optimized, life happens. Having an easy on and off ramp is important to this team. If a lead needs to take an extended absence or leave the team, a shadow would be offered the lead position prior to seeking a lead elsewhere. Therefore moving from shadow to lead and vice versa should be made as simply as possible by continued communications from this team about its members, roles, successes, and failures. - -In the case where no shadow is available, other Marketing Council team members have the responsibility to cover the role. Concerns for time or ability to cover work can be escalated to advisors and SIG Contributor Experience leads as necessary. - -[Marketing Council](/communication/marketing-team/role-handbooks/council.md) diff --git a/communication/marketing-team/role-handbooks/council.md b/communication/marketing-team/role-handbooks/council.md deleted file mode 100644 index ea0e7b8e..00000000 --- a/communication/marketing-team/role-handbooks/council.md +++ /dev/null @@ -1,91 +0,0 @@ -# Marketing Council Handbook - -## Overview - -The Marketing Council is made up of multiple individuals working to bring multiple functions together to ensure Kubernetes contributors have a wealth of robust content and communications. The Marketing Council act as joint leaders to the Upstream Marketing team and its key responsibilities to the entire Kubernetes contributor base. - -#### How It Works - -The ideal Marketing Council is made up of one of each of the leadship roles with one shadow for each. In practice, Council members can cover multiple roles but with the intention of finding someone else to fill the position. Coverage is outlined in the [project README]. - -## Responsibilities - -Responsibilities are categorized by the division of contribution among Marketing Council members. What brings us all together is a commitment to: - -- Be welcoming of everyone by being your unique self -- Be inclusive on contributors, especially non-code contribution -- Be a leader of this sub-project with a commitment to its charter - -#### Program Lead - -- Develop high level marketing strategies and themes to address problem areas, challenges, and innovation/moving the project forward; expected to collaborate with Leads on their strategies for functional areas -- Ensure the team has a unified voice, focus, and work within the charter scope -- Research and identify new and innovative ways of delivering content that appeals to our mission -- Facilitates meetings or can delegate to another Marketing Council member -- Manage the [editorial calendar] and [marketing project] boards -- Coordinate [storytellers] and other member involvement - -#### Promotion Lead - -- Lead and encourage use of owned communication channels, including the team's Twitter account and other social channels -- Helping to recruit other members of the team, ensuring onboarding but delegating to proper lead -- Promoting contributor events - - In the events folder or one off contributor events like SIG onboarding sessions -- KEPs - - To follow the same process as [social guidelines] - - No promotion unless there is an explicit documented request -- Proofreading and editing articles with our [blogging] and [ethos] in mind -- If time allows, market the team; blog about the team and it's progress, encourage team to blog about their work - -#### Liaison Lead - -- Act as or facilitate conversations and workflows between all types of internal stakeholders. This includes attending meetings and coordinating efforts with teams such as: - - SIG Contributor Experience - - Community Group Chairs and Tech Leads - - CNCF - - Steering Committee - - Contributors -- Working with the liaison team members to manage communications and workflows between the groups -- Create new liaison positions as needed to coordinate key initiatives across the Kubernetes community -- Audit the experience of engaging with the Upstream Marketing team and propose opportunities for improvement - -### Minimum Skills and Requirements - -Skills: - -- Be comfortable with general GitHub workflows. To date, this team still requires some expertise in this department to be effective. Current members can teach specifics but a foundation for this role is necessary. You'll be working inside of multiple repositories with different workflows and helping others on the team with troubleshooting. -- Be willing and capable of saying "no" as necessary, but try to get to a "yes, and" to help the community achieve its goals. In short, be empathetic. -- Strong written and verbal communication skills. A willingness to meet (a lot) of new people is important for this work. - -Requirements: - -- Member of the [Kubernetes GitHub Org] -- [Reviewer] in the marketing team folder -- Shadowed under a lead in any role on the team for 6 months total (could be a combination of roles during that time period) - -#### Expected Time Investment - -- Four hours a week as a minimal target. - -#### Duration - -Ideally, no lead should be in the same position indefinitely. With that in mind, every member of the Marketing Council is asked to raise awareness of the position and seek a shadow in preparation of them becoming a lead in the future. The team would like to see new leadership every 12 months to keep a fresh perspective. - -### Becoming a Shadow - -Any Upstream Marketing regular contributor can raise their hand to become a shadow of one or more of the positions in the council. If accepted, the objective of the council members is to nurture that shadow into a leadership position in the next 6 months. - -#### Expectations of a Shadow - -Consistently communicate and collaborate closely with the Marketing Council member of your choice. The objective is to get you, as the shadown, to be a confident leader of the above responsibilities. Be ready to backfill for them when they are unable to attend a meeting or represent the working group. - -[editorial calendar]: https://github.com/orgs/kubernetes/projects/41 -[marketing project]: https://github.com/orgs/kubernetes/projects/39 -[team-resources]: ../team-resources.md -[Kubernetes GitHub Org]: https://git.k8s.io/community/community-membership.md -[Reviewer]: ../OWNERS -[OWNERS]: /communication/OWNERS -[blogging]: ../storytelling-resources/blog-guidelines.md -[ethos]: ../CHARTER.md#ethosvision -[project README]: ../README.md -[storytellers]: ./storytellers.md
\ No newline at end of file diff --git a/communication/moderators.md b/communication/moderators.md index 99cd13bd..8bb4874a 100644 --- a/communication/moderators.md +++ b/communication/moderators.md @@ -44,7 +44,6 @@ Administrator seats: 3 | ------------------- | ------------------- | -------- | ------------------------------------------------------- | | Aaron Crickenberger | @spiffxp | Americas | [PT - Pacific Time (US West Coast)](https://time.is/PT) | | Davanum Srinivas | @dims | Americas | [ET - Eastern Time (US East Coast)](https://time.is/ET) | -| Paris Pittman | @paris | Americas | [PT - Pacific Time (US West Coast)](https://time.is/PT) | #### Primary Moderators @@ -175,11 +174,13 @@ Moderators pro tempore seats: 3 ### Owner -Owners seats (non-admin role): 1 +Owners seats (non-admin role): 3 -| Name | Kubernetes Slack ID | Region | Timezone | -| --------------- | ------------------- | -------- | ---------------------------------------------------- | -| Chris Aniszczyk | @caniszczyk | Americas | [CT - Central Time (US Central)](https://time.is/CT) | +| Name | Kubernetes Slack ID | Region | Timezone | +| --------------- | ------------------- | -------- | ---------------------------------------------------- | +| Chris Aniszczyk | @caniszczyk | Americas | [CT - Central Time (US Central)](https://time.is/CT) | +| Bob Killen | @mrbobbytables | Americas | [ET - Eastern Time (US East Coast)](https://time.is/ET) | +| Ihor Dvoretskyi | @ihor.dvoretskyi | Europe | [EET - Eastern European Time](https://time.is/EET) | ### Moderators @@ -193,7 +194,6 @@ Moderators seats: 10 | Jorge Alarcon | @alejandrox1 | Americas | [ET - Eastern Time (US East Coast)](https://time.is/ET) | | Katharine Berry | @Katharine | Americas | [PT - Pacific Time (US West Coast)](https://time.is/PT) | | Jaice Singer DuMars | @jdumars | Americas | [PT - Pacific Time (US West Coast)](https://time.is/PT) | -| Paris Pittman | @paris | Americas | [PT - Pacific Time (US West Coast)](https://time.is/PT) | | Noah Kantrowitz | @coderanger | Americas | [PT - Pacific Time (US West Coast)](https://time.is/PT) | | Ihor Dvoretskyi | @ihor.dvoretskyi | EMEA | [EET - Eastern European Time](https://time.is/EET) | | Yang Li | @idealhack | APAC | [JST - Japan Standard Time](https://time.is/Japan) | @@ -225,7 +225,6 @@ Administrators seats: 6 | Jorge Castro | @castrojo | Americas | [ET - Eastern Time (US East Coast)](https://time.is/ET) | | Bob Killen | @mrbobbytables | Americas | [ET - Eastern Time (US East Coast)](https://time.is/ET) | | Jorge Alarcon | @alejandrox1 | Americas | [ET - Eastern Time (US East Coast)](https://time.is/ET) | -| Paris Pittman | @paris | Americas | [PT - Pacific Time (US West Coast)](https://time.is/PT) | | Naeil Ezzoueidi | @nzoueidi | EMEA | [CET - Central European Time](https://time.is/CET) | | Yang Li | @idealhack | APAC | [JST - Japan Standard Time](https://time.is/Japan) | | Taylor Dolezal | @onlydole | Americas | [PT - Pacific Time (US West Coast)](https://time.is/PT) | diff --git a/communication/slack-config/OWNERS b/communication/slack-config/OWNERS index 13a52162..6ae6b23e 100644 --- a/communication/slack-config/OWNERS +++ b/communication/slack-config/OWNERS @@ -2,17 +2,19 @@ # These are the primary slack moderators. approvers: - - katharine - - castrojo - jeefy - mrbobbytables - alejandrox1 - - jdumars - - parispitmann - coderanger - - idvoretskyi - - idealhack - munnerz - DylanGraham + - jberkus +emeritus_approvers: + - parispitmann + - idvoretskyi + - katharine + - castrojo + - jdumars + - idealhack labels: - area/slack-management diff --git a/communication/slack-config/channels.yaml b/communication/slack-config/channels.yaml index bd1bf5c5..27f9454c 100644 --- a/communication/slack-config/channels.yaml +++ b/communication/slack-config/channels.yaml @@ -24,6 +24,8 @@ channels: - name: awesome-kubernetes - name: aws-authenticator - name: aws-controllers-k8s + - name: aws-vpc-cni + - name: azure-service-operator - name: bazel - name: bindings-discuss - name: bootkube @@ -52,6 +54,7 @@ channels: - name: cluster-api-aws-alerts - name: cluster-api-azure - name: cluster-api-baremetal + - name: cluster-api-cloud-director - name: cluster-api-cloudstack - name: cluster-api-digitalocean - name: cluster-api-docker @@ -61,6 +64,7 @@ channels: - name: cluster-api-kubemark - name: cluster-api-kubevirt - name: cluster-api-nested + - name: cluster-api-nutanix - name: cluster-api-oci - name: cluster-api-openstack - name: cluster-api-operator @@ -84,6 +88,7 @@ channels: - name: csi-secrets-store #this channel is for secrets-store-csi-driver which is a subproject of sig-auth - name: de-events - name: de-users + - name: deppy-dev - name: devfile - name: devspace - name: devstats @@ -94,6 +99,7 @@ channels: - name: dra - name: draft-dev - name: draft-users + - name: druid-operator - name: eks - name: elastickube - name: elk-charts @@ -108,8 +114,10 @@ channels: - name: events - name: external-dns - name: external-secrets + - name: external-secrets-dev - name: falco - name: fiaas + - name: finops - name: fi-users - name: flatcar - name: flink-operator @@ -172,8 +180,10 @@ channels: - name: kalm - name: kaniko - name: karpenter + - name: karpenter-dev - name: k8s-dual-stack archived: true + - name: k8s-image-swapper - name: k8s-infra-alerts - name: k8s-release archived: true @@ -193,10 +203,12 @@ channels: - name: kcna-exam-prep - name: klog - name: knative - - name: ko-project + - name: ko-build + id: C01T7DTP65S - name: kompose - name: kong - name: konveyor + - name: koordinator - name: kops-dev - name: kops-users - name: kots @@ -213,10 +225,12 @@ channels: - name: krex - name: krustlet - name: kube-aws + - name: kube-bind - name: kube-deploy archived: true - name: kube-monkey - name: kube-oidc-proxy + - name: kube-operating-systems-dev - name: kube-router - name: kube-score - name: kube-spawn @@ -274,6 +288,7 @@ channels: - name: malaysia-users - name: malta-users - name: meet-our-contributors + archived: true - name: meetup-athens - name: meetup-atlanta - name: meetup-austin @@ -326,6 +341,7 @@ channels: - name: octant - name: odo - name: office-hours + archived: true - name: okteto - name: olm-dev - name: open-cluster-mgmt @@ -346,9 +362,11 @@ channels: - name: osbkit - name: outreachy-apps id: CDH610735 + - name: paralus - name: pharmer - name: pinniped - name: pl-users + - name: podman-desktop - name: pr-reviews - name: prometheus - name: prometheus-operator @@ -382,6 +400,7 @@ channels: - name: sig-apps - name: sig-auth - name: sig-auth-kms-dev + - name: sig-auth-triage - name: sig-autoscaling - name: sig-autoscaling-api - name: sig-cli @@ -431,6 +450,7 @@ channels: - name: suse-caasp - name: talk-proposals - name: tanzu-community-edition + archived: true - name: tanzu-streaming-runtimes - name: terraform-providers - name: terranetes @@ -446,9 +466,11 @@ channels: - name: tw-users - name: ug-big-data id: C0ELB338T + archived: true - name: ug-vmware - name: undistro - name: vcluster + - name: velero-data-mover - name: velero-dev - name: velero-users id: C6VCGP4MT diff --git a/communication/slack-config/sig-release/usergroups.yaml b/communication/slack-config/sig-release/usergroups.yaml index 2b3b88d8..5526902a 100644 --- a/communication/slack-config/sig-release/usergroups.yaml +++ b/communication/slack-config/sig-release/usergroups.yaml @@ -16,17 +16,13 @@ usergroups: members: - ameukam # Release Manager Associate - cpanato # Release Manager + - jeremyrickard # Release Manager - jimangel # Release Manager Associate - justaugustus # subproject owner / Release Manager - - mkorbi # Release Manager Associate - - onlydole # Release Manager Associate - palnabarun # Release Manager - puerco # Release Manager - saschagrunert # subproject owner / Release Manager - - sethmccombs # Release Manager Associate - - thejoycekung # Release Manager Associate - Verolop # Release Manager - - wilsonehusin # Release Manager Associate - xmudrii # Release Manager # Should match the membership of the following groups at all times: @@ -52,15 +48,17 @@ usergroups: - sig-release members: - cpanato # SIG Release Technical Lead - - gracenng # 1.26 RT Lead Shadow - - jeremyrickard # SIG Release Technical Lead + - Heba # 1.27 RT Lead Shadow + - hosseinsalahi # 1.27 RT Lead Shadow + - JamesLaverack # 1.27 Emeritus Advisor + - jeremyrickard # SIG Release Chair - justaugustus # SIG Release Chair - - katcosgrove # 1.26 RT Lead Shadow - - leonardpahlke # 1.26 RT Lead - - nate-double-u # 1.26 RT Lead Shadow + - katcosgrove # 1.27 RT Lead Shadow - puerco # SIG Release Technical Lead - - psaggu # 1.26 RT Lead Shadow + - psaggu # 1.27 RT Lead Shadow - saschagrunert # SIG Release Chair + - Verolop # SIG Release Technical Lead + - Xander # 1.27 RT Lead # Should match SIG Release Leads at all times: # https://git.k8s.io/community/sig-release/README.md#leadership @@ -74,10 +72,11 @@ usergroups: - sig-release members: - cpanato # SIG Release Technical Lead - - jeremyrickard # SIG Release Technical Lead + - jeremyrickard # SIG Release Chair - justaugustus # SIG Release Chair - puerco # SIG Release Technical Lead - saschagrunert # SIG Release Chair + - Verolop # SIG Release Technical Lead # Should match the membership of the following teams at all times: # - https://git.k8s.io/security/#product-security-committee-psc @@ -92,16 +91,17 @@ usergroups: - sig-release members: - cjcullen # Product Security Committee - - cpanato # Release Manager + - cpanato # subproject owner / Release Manager + - jeremyrickard # subproject owner / Release Manager - joelsmith # Product Security Committee - justaugustus # subproject owner / Release Manager - lukehinds # Product Security Committee - micahhausler # Product Security Committee - palnabarun # Release Manager - - puerco # Release Manager + - puerco # subproject owner / Release Manager - saschagrunert # subproject owner / Release Manager - swamymsft # Product Security Committee - tabbysable # Product Security Committee - tallclair # Product Security Committee - xmudrii # Release Manager - - Verolop # Release Manager + - Verolop # subproject owner / Release Manager diff --git a/communication/slack-config/sig-security/config.yaml b/communication/slack-config/sig-security/config.yaml index 1d32525d..7227b7b4 100644 --- a/communication/slack-config/sig-security/config.yaml +++ b/communication/slack-config/sig-security/config.yaml @@ -4,3 +4,4 @@ channels: - name: sig-security-docs - name: sig-security-tooling - name: sig-security-assessments + - name: sig-security-assess-vsphere-csi-driver diff --git a/communication/slack-config/usergroups.yaml b/communication/slack-config/usergroups.yaml index 10c5ef93..13617746 100644 --- a/communication/slack-config/usergroups.yaml +++ b/communication/slack-config/usergroups.yaml @@ -21,8 +21,8 @@ usergroups: - TaoBeier - name: contributor-comms - long_name: Upstream Marketing - description: Upstream Marketing group. + long_name: Contributor Communications + description: Contributor Communications group. channels: - sig-contribex members: @@ -35,6 +35,7 @@ usergroups: - paris - PurneswarPrasad - rajula96reddy + - imran # Should match the membership of the following teams at all times: # - https://git.k8s.io/security/#product-security-committee-psc @@ -180,18 +181,28 @@ usergroups: - jonasrosland - pnbrown + - name: podman-desktop-devs + long_name: Podman Desktop Dev Team + description: Active developers of Podman Desktop on #podman-desktop + channels: + - podman-desktop + members: + - cdrage + - benoitf + - vzhukovs + - name: steering-members long_name: Kubernetes Steering Committee description: Members of the Kubernetes Steering Committee channels: - steering-committee members: + - bentheelder - cblecker - - dims + - cpanato - justaugustus - - liggitt - mrbobbytables - - paris + - palnabarun - tpepper - name: grafana-operator-maintainers @@ -209,6 +220,14 @@ usergroups: - vladimirmukhin - wurbanski + - name: druid-operator-maintainers + long_name: Druid Operator Maintainers + description: Dev and Support group for Druid Operator. + channels: + - druid-operator + members: + - adheipsingh + - name: devfile-devs long_name: Devfile Development Team description: Active developers of Devfile on #devfile @@ -224,3 +243,22 @@ usergroups: - rtaniwa - schultzp2020 - yangcao77 + + - name: cluster-api-release-team + long_name: Cluster API Release Team + description: Members of the Cluster API Release Team + members: + - alexander-demicev + - aniruddha2000 + - CecileRobertMichon + - cpanato + - dntosas + - furkatgofurov7 + - hackeramitkumar + - joekr + - nawazkh + - oscr + - sayantani11 + - sbueringer + - VibhorChinda + - ykakarap diff --git a/communication/slack-config/users.yaml b/communication/slack-config/users.yaml index 09eb3e3f..3e87bd2a 100644 --- a/communication/slack-config/users.yaml +++ b/communication/slack-config/users.yaml @@ -2,12 +2,15 @@ # usernames to Kubernetes Slack user IDs. users: adisky: U9YRVLTEH + adheipsingh: T09NY5SBT alejandrox1: U6AS37R50 aleksandra-malinowska: U357LUPHS + alexander-demicev: UR7UCR7RV AlexB138: U3JA3MDGV alisondy: U9CBCBLCV ameukam: U68KPQ448 anandrkskd: U01DRS3V0R2 + aniruddha2000: U02BU1RP41H anjaltelang: U028B09KZ5X ankeesler: UBAA1KQ4A annajung: U8SLB1P2Q @@ -19,6 +22,8 @@ users: Bart Farrell: U01DZM7PJDT bart0sh: U8VJC20R3 benjaminapetersen: U0217E7EXV4 + bentheelder: U1P7T516X + benoitf: UCQC3DNUA bhumijgupta: U022JUBM3B4 briandealwis: UAZKM38JV bubblemelon: U7K9C643G @@ -28,6 +33,7 @@ users: castrojo: U1W1Q6PRQ cblecker: U3EDWR9FV cdrage: U2TU9NPH9 + CecileRobertMichon: U98JPHB2M cfryanr: U0188B6J42H chrisshort: U2YGXSD9B cici37: UTY5J12L9 @@ -42,6 +48,7 @@ users: dharmit: U0APPPEKE dims: U0Y7A2MME divya-mohan0209: UV4J7K97Z + dntosas: UKT4D74F3 dougm: U8GG20UE9 elezar: ULV21K3CH elsony: UCW8323KL @@ -51,20 +58,25 @@ users: fabianvf: UAJ3UH29F feiskyer: U0ASA4398 feloy: UFG7CN85U + furkatgofurov7: UV31DL3CG gianarb: U0FSCELCR girishramnani: U9M4K75EU gracenng: U01GX18N6H3 grdryn: U017628HJL8 gsquared94: U0131C0PJBU guineveresaenger: U4H2QU3DW + hackeramitkumar: U045992D532 hasheddan: ULLQEF30C + Heba: UHE5TSU4W hoegaarden: U7VA4RZS9 + hosseinsalahi: U7SR0QJP8 hubertstefanski: U01941KQ2UT iancoldwater: U9VL5SZPX idealhack: U5NJ3DQM9 idvoretskyi: U0CBHE6GM ilya-zuyev: U018UF2G42F IsaacPD: U01B0C1R9NZ + imran: U03K4862X7U JamesLaverack: U9MK7274Y Jason: UB272379N jberkhahn: U7Q21LH2S @@ -76,6 +88,7 @@ users: jlbutler: U0122V3T932 jmccormick2001: UMPLV0G0H jmrodri: U4KATPQ48 + joekr: U02MUT273GA Joel Barker: U014AHSTBPA joelanford: U1R6NQD8W joelsmith: U5SLG8T8F @@ -117,10 +130,12 @@ users: mrbobbytables: U511ZSKHD munnerz: U0EC03FTN nate-double-u: U01AWL6BD62 + nawazkh: U03HJN1C81W nikhita: U2PQHGMLN nkubala: UA90QL2BE nzoueidi: UBU72MWP2 onlydole: U1DD4AZND + oscr: U0183J37JUQ pabloschuhmacher: U01AAGZ06KU palnabarun: UBH9NTMBM paris: U5SB22BBQ @@ -142,11 +157,12 @@ users: rnapoles-rh: U01KDAMSWJD robshelly: U01LL4P09SR rtaniwa: U03K27HLHKN - salaxander: UDHV1RXB2 sammy: U8NJFL023 sandipanpanda: U02A47HJ517 saschagrunert: U53SUDBD4 savitharaghunathan: UC8U2V3BM + sayantani11: U028S6XNVSN + sbueringer: U48TE1L75 schultzp2020: U030K8UQA2G scott-seago: UHGD79E78 sethmccombs: U92LLUZ8A @@ -169,11 +185,15 @@ users: valaparthvi: U016TMJVDAA varshaprasad96: UK59YP2DA Verolop: U7NNE57PU + VibhorChinda: U031EALE91D vladimirmukhin: UHVSCSD4G + vzhukovs: U030TR1FG85 wilsonehusin: U0100068GF2 wurbanski: URX7CMK97 + Xander: UDHV1RXB2 xmudrii: U4Q2TNGVD xun-jiang: U02J0QC1VKJ yangcao77: U01D1VCNJQ3 yinw: UMVD1GDCY + ykakarap: U0145EMCA03 zubron: U7G0KNS86 diff --git a/communication/slack-guidelines.md b/communication/slack-guidelines.md index 45f0e75f..b9033940 100644 --- a/communication/slack-guidelines.md +++ b/communication/slack-guidelines.md @@ -386,19 +386,19 @@ past "X" minutes/hours. Report any actions taken to the other slack admins, and if needed the [Code of Conduct Committee][cocc]. - [coc]: /code-of-conduct.md - [admins]: ./moderators.md#Slack - [Slack Archive Download]: https://drive.google.com/drive/folders/1Xnkwsxis3tu0pT7rwp-crRq4IciZ5b1o?usp=sharing - [cocc]: /committee-code-of-conduct/README.md - [CNCF Slack]: https://slack.cncf.io/ - [Tempelis]: http://sigs.k8s.io/slack-infra/tempelis - [slack-config]: ./slack-config/ - [Channel Documentation]: ./slack-config/README.md - [sig-list]: https://www.kubernetes.dev/community/community-groups - [Slack Config Documentation]: ./slack-config/README.md - [OWNERS]: /contributors/guide/owners - [usergroups.yaml]: ./slack-config/usergroups.yaml - [User Group Documentation]: ./slack-config/README.md#usergroups - [GitHub Issue]: https://github.com/kubernetes/community/issues/new/choose - [moderation guidelines]: ./moderation.md - [Slack's policy on inactivated accounts]: https://get.slack.help/hc/en-us/articles/204475027-Deactivate-a-member-s-account +[coc]: /code-of-conduct.md +[admins]: ./moderators.md#Slack +[Slack Archive Download]: https://drive.google.com/drive/folders/1Xnkwsxis3tu0pT7rwp-crRq4IciZ5b1o?usp=sharing +[cocc]: /committee-code-of-conduct/README.md +[CNCF Slack]: https://slack.cncf.io/ +[Tempelis]: http://sigs.k8s.io/slack-infra/tempelis +[slack-config]: ./slack-config/ +[Channel Documentation]: ./slack-config/README.md +[sig-list]: https://www.kubernetes.dev/community/community-groups +[Slack Config Documentation]: ./slack-config/README.md +[OWNERS]: /contributors/guide/OWNERS +[usergroups.yaml]: ./slack-config/usergroups.yaml +[User Group Documentation]: ./slack-config/README.md#usergroups +[GitHub Issue]: https://github.com/kubernetes/community/issues/new/choose +[moderation guidelines]: ./moderation.md +[Slack's policy on inactivated accounts]: https://get.slack.help/hc/en-us/articles/204475027-Deactivate-a-member-s-account diff --git a/communication/youtube/OWNERS b/communication/youtube/OWNERS index bb84ded5..3f77586f 100644 --- a/communication/youtube/OWNERS +++ b/communication/youtube/OWNERS @@ -1,7 +1,6 @@ # See the OWNERS docs at https://go.k8s.io/owners reviewers: - - parispittman - jeefy - mrbobbytables - chris-short diff --git a/communication/youtube/youtube-guidelines.md b/communication/youtube/youtube-guidelines.md index 0bd56d03..85a10e3a 100644 --- a/communication/youtube/youtube-guidelines.md +++ b/communication/youtube/youtube-guidelines.md @@ -23,8 +23,7 @@ and includes all communications such as YouTube. The [Kubernetes YouTube Channel] has separate playlists for each SIG, WG, UG meeting recordings, as well as recordings of other recurring events such as the -Kubernetes [community meeting], [Office Hours], [Meet our Contributors] -and others. +Kubernetes [community meeting], and others. [Subprojects], in addition to SIGs, WGs, UGs may request their own playlists to better target their contributors and increase general discoverability. @@ -35,8 +34,8 @@ playlist can upload videos *to that particular playlist* (links & playlists are one-to-one). Each group's playlist link will be shared with the group's leadership via Slack -and the group leadership Google Group. Other playlists links, for example Office -Hours, will be shared with the appropriate point(s) of contact. +and the group leadership Google Group. Other playlists links, will be shared +with the appropriate point(s) of contact. ### Uploading Guidelines for Collaborators @@ -173,9 +172,8 @@ The following SIGs and groups are currently running splain.io: - [SIG Release] - [Steering Committee] - [WG Data Protection] -- The main Zoom admin account which holds Meet Our Contributors and others (if - you log in to splain using this account, all of the other accounts will be - logged here) +- The main Zoom admin account (if you log in to splain using this account, + all of the other accounts will be logged here) ### Descriptions and Playlists @@ -214,9 +212,9 @@ to hear from you. ### Streaming Events YouTube admins with a system capable of streaming may be asked to stream public -Kubernetes Community events such as the weekly [Community Meeting], -[Office Hours], [Meet our Contributors], or other publicly streamed -events. For detailed information about streaming, see our [Streaming Config]. +Kubernetes Community events such as the weekly [Community Meeting], or other +publicly streamed events. For detailed information about streaming, see our +[Streaming Config]. ### Migrating Content @@ -236,26 +234,24 @@ downloaded and then reuploaded to the Kubernetes channel. generate thumbnails and process the videos. 7. Once videos are finalized, set the playlist to Public to publish them. - [coc]: /code-of-conduct.md - [admins]: /communication/moderators.md - [Kubernetes YouTube Channel]: https://www.youtube.com/channel/UCZ2bu0qutTOM0tHYa_jkIwg - [community meeting]: /events/community-meeting.md - [Office Hours]: /events/office-hours.md - [Meet our Contributors]: /events/meet-our-contributors.md - [Subprojects]: /governance.md#subprojects - [collaboration]: https://support.google.com/youtube/answer/6109639 - [update the permissions in your YouTube settings]: https://support.google.com/a/answer/6212415 - [YouTube admins]: /communication/moderators.md#YouTube-Channel - [SIG Contributor Experience]: /sig-contributor-experience/README.md - [moderation guidelines]: /communication/moderation.md - [trim]: https://support.google.com/youtube/answer/9057455?hl=en - [edit]: https://support.google.com/youtube/topic/9257530?hl=en&ref_topic=9257610 - [Zoom guidelines]: /communication/zoom-guidelines.md - [SIG Auth]: /sig-auth/README.md - [SIG Docs]: /sig-docs/README.md - [SIG Network]: /sig-network/README.md - [SIG Release]: /sig-release/README.md - [Steering Committee]: /committee-steering/governance/README.md - [WG Data Protection]: /wg-data-protection/README.md - [Streaming Config]: /communication/youtube/streaming-config.md - [youtube-dl]: https://ytdl-org.github.io/youtube-dl/index.html +[coc]: /code-of-conduct.md +[admins]: /communication/moderators.md +[Kubernetes YouTube Channel]: https://www.youtube.com/channel/UCZ2bu0qutTOM0tHYa_jkIwg +[community meeting]: /events/community-meeting.md +[Subprojects]: /governance.md#subprojects +[collaboration]: https://support.google.com/youtube/answer/6109639 +[update the permissions in your YouTube settings]: https://support.google.com/a/answer/6212415 +[YouTube admins]: /communication/moderators.md#YouTube-Channel +[SIG Contributor Experience]: /sig-contributor-experience/README.md +[moderation guidelines]: /communication/moderation.md +[trim]: https://support.google.com/youtube/answer/9057455?hl=en +[edit]: https://support.google.com/youtube/topic/9257530?hl=en&ref_topic=9257610 +[Zoom guidelines]: /communication/zoom-guidelines.md +[SIG Auth]: /sig-auth/README.md +[SIG Docs]: /sig-docs/README.md +[SIG Network]: /sig-network/README.md +[SIG Release]: /sig-release/README.md +[Steering Committee]: /committee-steering/governance/README.md +[WG Data Protection]: /wg-data-protection/README.md +[Streaming Config]: /communication/youtube/streaming-config.md +[youtube-dl]: https://ytdl-org.github.io/youtube-dl/index.html diff --git a/communication/zoom-guidelines.md b/communication/zoom-guidelines.md index 00df1f0a..e83125d4 100644 --- a/communication/zoom-guidelines.md +++ b/communication/zoom-guidelines.md @@ -5,8 +5,8 @@ description: | --- Zoom is the main video communication platform for Kubernetes. It is used for -running the [community meeting], [SIG/WG meetings], [Office Hours], -[Meet Our Contributors] and many other Kubernetes online events. Since the Zoom +running the [community meeting], [SIG/WG meetings], +and many other Kubernetes online events. Since the Zoom meetings are open to the general public, a Zoom host or co-host has to moderate a meeting in all senses of the word, from starting and stopping the meeting to acting on [Kubernetes code of conduct] issues. @@ -190,27 +190,25 @@ for which models work best. Thanks for making Kubernetes meetings work great! - [community meeting]: /events/community-meeting - [SIG/WG meetings]: /sig-list.md - [Office Hours]: /events/office-hours - [Meet Our Contributors]: /mentoring/programs/meet-our-contributors.md - [Kubernetes code of conduct]: /code-of-conduct.md - [moderation]: ./moderation.md - [CNCF Service Desk]: https://github.com/cncf/servicedesk - [Zoom Admins]: ./moderators.md#zoom - [centralized list of administrators]: ./moderators.md - [sig creation procedure]: /sig-wg-lifecycle.md#communicate - [latest version]: https://zoom.us/download - [host key]: https://support.zoom.us/hc/en-us/articles/205172555-Host-Key - [waiting room]: https://support.zoom.us/hc/en-us/articles/115000332726-Waiting-Room - [documentation on how to use their moderation tools]: https://support.zoom.us/hc/en-us/articles/201362603-Host-Controls-in-a-Meeting - [best practices doc]: https://docs.google.com/document/d/1fudC_diqhN2TdclGKnQ4Omu4mwom83kYbZ5uzVRI07w/edit?usp=sharing - [Code of Conduct Committee]: /committee-code-of-conduct/README.md - [Please follow this guideline for more details]: ./youtube/youtube-guidelines.md - [Kubernetes channel]: https://www.youtube.com/c/kubernetescommunity - [SIG Contributor Experience]: /sig-contributor-experience - [documentation on how to use their screen sharing feature]: https://support.zoom.us/hc/en-us/articles/201362153-How-Do-I-Share-My-Screen - [lots of things that can go wrong]: https://www.youtube.com/watch?v=JMOOG7rWTPg - [Blue Yeti]: https://www.bluedesigns.com/products/yeti/ - [pop filter]: https://en.wikipedia.org/wiki/Pop_filter - [Join on muted audio and video]: https://support.zoom.us/hc/en-us/articles/203024649-Video-Or-Microphone-Off-By-Attendee +[community meeting]: /events/community-meeting +[SIG/WG meetings]: /sig-list.md +[Kubernetes code of conduct]: /code-of-conduct.md +[moderation]: ./moderation.md +[CNCF Service Desk]: https://github.com/cncf/servicedesk +[Zoom Admins]: ./moderators.md#zoom +[centralized list of administrators]: ./moderators.md +[sig creation procedure]: /sig-wg-lifecycle.md#communicate +[latest version]: https://zoom.us/download +[host key]: https://support.zoom.us/hc/en-us/articles/205172555-Host-Key +[waiting room]: https://support.zoom.us/hc/en-us/articles/115000332726-Waiting-Room +[documentation on how to use their moderation tools]: https://support.zoom.us/hc/en-us/articles/201362603-Host-Controls-in-a-Meeting +[best practices doc]: https://docs.google.com/document/d/1fudC_diqhN2TdclGKnQ4Omu4mwom83kYbZ5uzVRI07w/edit?usp=sharing +[Code of Conduct Committee]: /committee-code-of-conduct/README.md +[Please follow this guideline for more details]: ./youtube/youtube-guidelines.md +[Kubernetes channel]: https://www.youtube.com/c/kubernetescommunity +[SIG Contributor Experience]: /sig-contributor-experience +[documentation on how to use their screen sharing feature]: https://support.zoom.us/hc/en-us/articles/201362153-How-Do-I-Share-My-Screen +[lots of things that can go wrong]: https://www.youtube.com/watch?v=JMOOG7rWTPg +[Blue Yeti]: https://www.bluedesigns.com/products/yeti/ +[pop filter]: https://en.wikipedia.org/wiki/Pop_filter +[Join on muted audio and video]: https://support.zoom.us/hc/en-us/articles/203024649-Video-Or-Microphone-Off-By-Attendee diff --git a/contributors/chairs-and-techleads/leadership-changes.md b/contributors/chairs-and-techleads/leadership-changes.md index bc0dbb78..03e1af35 100644 --- a/contributors/chairs-and-techleads/leadership-changes.md +++ b/contributors/chairs-and-techleads/leadership-changes.md @@ -35,7 +35,7 @@ lazy consensus cannot be achieved, an election should be held. SIG Contributor Experience should be contacted to assist with the administration of the election. -[kubernetes-dev]: https://groups.google.com/g/kubernetes-dev +[kubernetes-dev]: https://groups.google.com/a/kubernetes.io/g/dev [steering-private]: steering-private@kubernetes.io [member]: /community-membership.md#member [`sigs.yaml`]: /sigs.yaml diff --git a/contributors/devel/development.md b/contributors/devel/development.md index 00ebe0a3..ab5d4cce 100644 --- a/contributors/devel/development.md +++ b/contributors/devel/development.md @@ -3,7 +3,7 @@ This document is the canonical source of truth for things like supported toolchain versions for building Kubernetes. -Please submit an [issue] on Github if you +Please submit an [issue] on GitHub if you * Notice a requirement that this doc does not capture. * Find a different doc that specifies requirements (the doc should instead link here). @@ -285,7 +285,8 @@ different versions of Kubernetes. | 1.19 - 1.20 | 1.15.5 | | 1.21 - 1.22 | 1.16.7 | | 1.23 | 1.17 | -| 1.24+ | 1.18 | +| 1.24 | 1.18 | +| 1.25+ | 1.19 | ##### A Note on Changing Go Versions @@ -322,6 +323,10 @@ this permanent, add this to your `.bashrc` or login script: export PATH="$GOPATH/src/k8s.io/kubernetes/third_party/etcd:${PATH}" ``` +##### BASH version requirement + +To successfully run unit tests in Kubernetes, you will need bash version installed to be >4.3. + Once you have installed all required software, you can proceed to the [Building Kubernetes](#building-kubernetes) section to test if it all works properly. diff --git a/contributors/devel/running-locally.md b/contributors/devel/running-locally.md index 89b5d960..490f1c20 100644 --- a/contributors/devel/running-locally.md +++ b/contributors/devel/running-locally.md @@ -33,7 +33,7 @@ You will need a [Container Runtime](https://kubernetes.io/docs/setup/production- ### etcd -You need [etcd](https://github.com/coreos/etcd/releases) installed and in your `$PATH`. [Check here](https://github.com/kubernetes/community/blob/master/contributors/devel/development.md#install-etcd) for instructions on installing a local copy. +You need [etcd](https://github.com/coreos/etcd/releases) installed and in your `$PATH`. [Check here](https://github.com/kubernetes/community/blob/master/contributors/devel/development.md#etcd) for instructions on installing a local copy. ### go diff --git a/contributors/devel/sig-architecture/api-conventions.md b/contributors/devel/sig-architecture/api-conventions.md index 1acdbdc8..98cfc27d 100644 --- a/contributors/devel/sig-architecture/api-conventions.md +++ b/contributors/devel/sig-architecture/api-conventions.md @@ -980,7 +980,7 @@ read/modify/write cycle, by verifying that the current value of resourceVersion matches the specified value. The resourceVersion is currently backed by [etcd's -modifiedIndex](https://coreos.com/etcd/docs/latest/v2/api.html). +mod_revision](https://etcd.io/docs/latest/learning/api/#key-value-pair). However, it's important to note that the application should *not* rely on the implementation details of the versioning system maintained by Kubernetes. We may change the implementation of resourceVersion in the future, such as to change it diff --git a/contributors/devel/sig-architecture/conformance-tests.md b/contributors/devel/sig-architecture/conformance-tests.md index 91026639..d04fb506 100644 --- a/contributors/devel/sig-architecture/conformance-tests.md +++ b/contributors/devel/sig-architecture/conformance-tests.md @@ -370,3 +370,28 @@ for your provider, please see the [testgrid conformance README] [testgrid conformance README]: https://github.com/kubernetes/test-infra/blob/master/testgrid/conformance/README.md [v1.9 conformance doc]: https://github.com/cncf/k8s-conformance/blob/master/docs/KubeConformance-1.9.md [conformance.yaml]: https://github.com/kubernetes/kubernetes/blob/master/test/conformance/testdata/conformance.yaml + +## Demoting Conformance Tests + +Occasionally it may be necessary to remove a test that was added to conformance. Reasons may include but are not limited to: + +* The test does not actually [meet the criteria](#conformance-test-requirements) to be a conformance test +* The test is discovered to be unreliable and/or includes functionality not intended to be part of conformance +* The project deprecates or removes a feature + +These criteria apply to conformance added in a current release and should follow the same process involved in promoting a test. + +We may occasionally discover that a conformance test must be demoted in an already released version. This is generally a safe operation for the consumers of conformance - no existing distribution will become less conformant as a result of demoting a test. We should apply the same heightened bar for backporting conformance demotions as we would for backporting any code change: + +* Ensuring agreement among the responsible SIG(s) that the criteria for demotion are met +* Agreement from conformance approvers that backporting the demotion is consistent with backwards compatibility for the project +* Verifying the demotion does not result in a loss of function in a previous release + +The process for demoting a conformance test in a previous release is: + +* Demote the test in the current release following the current release process +* Open the appropriate backport PR following the backport process +* Approval of the backport by the conformance approvers and the release lead +* Update of necessary conformance test tooling is the responsibility of their owners, such as for CNCF automation that approves test results + +A backported demotion does not imply previously conformant distributions must recertify - those distributions are no less conformant than they were previously. As Kubernetes is a continuously evolving project new patches to previously released versions may tweak behavior in keeping with our commitment to API stability, so we expect true conformance changes in previously released versions to be rare.
\ No newline at end of file diff --git a/contributors/devel/sig-node/OWNERS b/contributors/devel/sig-node/OWNERS index dcf3663c..2ea840ee 100644 --- a/contributors/devel/sig-node/OWNERS +++ b/contributors/devel/sig-node/OWNERS @@ -2,11 +2,11 @@ reviewers: - sig-node-leads - - ehashman - SergeyKanzhelev approvers: - sig-node-leads - - ehashman - SergeyKanzhelev +emeritus_approvers: + - ehashman labels: - sig/node diff --git a/contributors/devel/sig-node/e2e-node-tests.md b/contributors/devel/sig-node/e2e-node-tests.md index bbfbdee7..c44262c4 100644 --- a/contributors/devel/sig-node/e2e-node-tests.md +++ b/contributors/devel/sig-node/e2e-node-tests.md @@ -16,8 +16,9 @@ Prerequisites: - [Install etcd](https://github.com/coreos/etcd/releases) and include the path to the installation in your PATH - Verify etcd is installed correctly by running `which etcd` - Or make etcd binary available and executable at `/tmp/etcd` -- [Install ginkgo](https://github.com/onsi/ginkgo) and include the path to the installation in your PATH - - Verify ginkgo is installed correctly by running `which ginkgo` +- [containerd](https://github.com/containerd/containerd) configured with the cgroupfs driver +- Working CNI + - Ensure that you have a valid CNI configuration in /etc/cni/net.d/. For testing purposes, a [bridge](https://www.cni.dev/plugins/current/main/bridge/) configuration should work. From the Kubernetes base directory, run: diff --git a/contributors/devel/sig-release/kubernetes-versions.md b/contributors/devel/sig-release/kubernetes-versions.md index a5f06099..754d7539 100644 --- a/contributors/devel/sig-release/kubernetes-versions.md +++ b/contributors/devel/sig-release/kubernetes-versions.md @@ -328,6 +328,7 @@ The following generic markers are available: - `k8s-stable1` - `k8s-stable2` - `k8s-stable3` +- `k8s-stable4` Generic markers reference cross builds generated via the `ci-kubernetes-build` jobs, which run approximately every hour. @@ -400,6 +401,7 @@ We publish a set of additional generic version markers: - `k8s-stable1` - `k8s-stable2` - `k8s-stable3` +- `k8s-stable4` Depending on the point in the release cycle, the meaning of these markers can change. diff --git a/contributors/guide/OWNERS b/contributors/guide/OWNERS index 2ae0a6da..6e7ebd56 100644 --- a/contributors/guide/OWNERS +++ b/contributors/guide/OWNERS @@ -2,10 +2,10 @@ approvers: - mrbobbytables - - parispittman emeritus_approvers: - castrojo - guineveresaenger + - parispittman labels: - sig/contributor-experience - area/contributor-guide diff --git a/contributors/guide/README.md b/contributors/guide/README.md index 538c442a..d53d754d 100644 --- a/contributors/guide/README.md +++ b/contributors/guide/README.md @@ -38,7 +38,7 @@ be able to pick up issues, write code to fix them, and get your work reviewed and merged. This document is the single source of truth for how to contribute to the code -base. Feel free to browse the [open issues] and file new ones, all feedback +base. Feel free to browse the [open issues] and file new ones, all feedback is welcome! ## Contributor Guide @@ -63,7 +63,7 @@ easier: ### Create a GitHub account -Before you get started, you will need to [signup](http://github.com/signup) for a GitHub user account. +Before you get started, you will need to [sign up](http://github.com/signup) for a GitHub user account. ### Sign the CLA @@ -86,7 +86,7 @@ for how to set up your environment. ### Community Expectations and Roles Kubernetes is a community project. Consequently, it is wholly dependent on its -community to provide a productive, friendly and collaborative environment. +community to provide a productive, friendly, and collaborative environment. - Read and review the [Community Expectations] for an understanding of code and review expectations. @@ -120,7 +120,7 @@ up the contributor ladder! ### Events Kubernetes participates in KubeCon + CloudNativeCon, held three times per year -in China, Europe and in North America. Information about these and other +in China, Europe, and North America. Information about these and other community events is available on the CNCF [Events] pages. ### Meetups @@ -131,9 +131,7 @@ as Meetups) program by email (meetups@cncf.io) ### Mentorship -Learn more about the Kubernetes [mentoring initiatives]. Join past and present -Kubernetes Contributors for a live question-and-answer session during -[Meet Our Contributors]. +Learn more about the Kubernetes [mentoring initiatives]. ## Advanced Topics @@ -156,7 +154,6 @@ do not need to interact with regularly. [here]: /events/2019/11-contributor-summit [General Information]: /communication [mentoring initiatives]: /mentoring/README.md -[Meet Our Contributors]: /mentoring/programs/meet-our-contributors.md [OWNERS files]: ./owners.md [Cloud Native Computing Foundation Guidelines]: https://github.com/cncf/communitygroups [Events]: https://www.cncf.io/events/ diff --git a/contributors/guide/contributing.md b/contributors/guide/contributing.md index 5ea85606..dfc004ba 100644 --- a/contributors/guide/contributing.md +++ b/contributors/guide/contributing.md @@ -60,9 +60,9 @@ Refer to its [command reference documentation](https://go.k8s.io/bot-commands). Common new contributor PR issues are: -* not having correctly signed the CLA ahead of your first PR. See the [CLA page](/CLA.md) for troubleshooting help, in some cases you might need to file a ticket with the CNCF to resolve a CLA problem. -* finding the right SIG or reviewer(s) for the PR (see [Code Review](#code-review) section) and following any SIG or repository specific contributing guidelines (see [Learn about SIGs](first-contribution.md#learn-about-sigs) section) -* dealing with test cases which fail on your PR, unrelated to the changes you introduce (see [Test Flakes](/contributors/devel/sig-testing/flaky-tests.md)) +* Not having correctly signed the CLA ahead of your first PR. See the [CLA page](/CLA.md) for troubleshooting help, in some cases you might need to file a ticket with the CNCF to resolve a CLA problem. +* Finding the right SIG or reviewer(s) for the PR (see [Code Review](#code-review) section) and following any SIG or repository specific contributing guidelines (see [Learn about SIGs](first-contribution.md#learn-about-sigs) section) +* Dealing with test cases which fail on your PR, unrelated to the changes you introduce (see [Test Flakes](/contributors/devel/sig-testing/flaky-tests.md)) * Not following [scalability good practices](scalability-good-practices.md) * Include mentions (like @person) and [keywords](https://help.github.com/en/articles/closing-issues-using-keywords) which could close the issue (like fixes #xxxx) in commit messages. @@ -73,10 +73,10 @@ There are two aspects of code review: giving and receiving. To make it easier for your PR to receive reviews, consider the reviewers will need you to: -* follow the project [coding conventions](coding-conventions.md) -* write [good commit messages](https://chris.beams.io/posts/git-commit/) -* break large changes into a logical series of smaller patches which individually make easily understandable changes, and in aggregate solve a broader issue -* label PRs with appropriate SIGs and reviewers: to do this read the messages the bot sends you to guide you through the PR process +* Follow the project [coding conventions](coding-conventions.md) +* Write [good commit messages](https://chris.beams.io/posts/git-commit/) +* Break large changes into a logical series of smaller patches which individually make easily understandable changes, and in aggregate solve a broader issue +* Label PRs with appropriate SIGs and reviewers: to do this read the messages the bot sends you to guide you through the PR process Reviewers, the people giving the review, are highly encouraged to revisit the [Code of Conduct](/code-of-conduct.md) as well as [community expectations](./expectations.md#expectations-of-reviewers-review-latency) and must go above and beyond to promote a collaborative, respectful community. When reviewing PRs from others [The Gentle Art of Patch Review](http://sage.thesharps.us/2014/09/01/the-gentle-art-of-patch-review/) suggests an iterative series of focuses which is designed to lead new contributors to positive collaboration without inundating them initially with nuances: diff --git a/contributors/guide/contributor-cheatsheet/README.md b/contributors/guide/contributor-cheatsheet/README.md index f4fd8956..0ed76794 100644 --- a/contributors/guide/contributor-cheatsheet/README.md +++ b/contributors/guide/contributor-cheatsheet/README.md @@ -387,7 +387,7 @@ git push --force [Kubernetes Code Search]: https://cs.k8s.io/ [@dims]: https://github.com/dims [calendar]: https://calendar.google.com/calendar/embed?src=calendar%40kubernetes.io -[kubernetes-dev]: https://groups.google.com/forum/#!forum/kubernetes-dev +[kubernetes-dev]: https://groups.google.com/a/kubernetes.io/g/dev [slack channels]: http://slack.k8s.io/ [Stack Overflow]: https://stackoverflow.com/questions/tagged/kubernetes [youtube channel]: https://www.youtube.com/c/KubernetesCommunity/ diff --git a/contributors/guide/github-workflow.md b/contributors/guide/github-workflow.md index 178c5854..a50b3a66 100644 --- a/contributors/guide/github-workflow.md +++ b/contributors/guide/github-workflow.md @@ -237,6 +237,11 @@ For mass automated fixups such as automated doc formatting, use one or more commits for the changes to tooling and a final commit to apply the fixup en masse. This makes reviews easier. +An alternative to this manual squashing process is to use the Prow and Tide based automation that is configured in GitHub: adding a comment to your PR with `/label tide/merge-method-squash` will trigger the automation so that GitHub squash your commits onto the target branch once the PR is approved. Using this approach simplifies things for those less familiar with Git, but there are situations in where it's better to squash locally; reviewers will have this in mind and can ask for manual squashing to be done. + +By squashing locally, you control the commit message(s) for your work, and can separate a large PR into logically separate changes. +For example: you have a pull request that is code complete and has 24 commits. You rebase this against the same merge base, simplifying the change to two commits. Each of those two commits represents a single logical change and each commit message summarizes what changes. Reviewers see that the set of changes are now understandable, and approve your PR. + ## Merging a commit Once you've received review and approval, your commits are squashed, your PR is ready for merging. diff --git a/contributors/guide/non-code-contributions.md b/contributors/guide/non-code-contributions.md index 11813bac..7678a722 100644 --- a/contributors/guide/non-code-contributions.md +++ b/contributors/guide/non-code-contributions.md @@ -27,11 +27,6 @@ These are roles that either span the project as a whole, or span several areas o - Community education - Answering questions on [Discuss](https://discuss.kubernetes.io/), [Slack](http://slack.k8s.io/), [StackOverflow](https://stackoverflow.com/questions/tagged/kubernetes), etc - - [K8s Office Hours](https://github.com/kubernetes/community/blob/master/events/office-hours.md) - - [Slack](https://kubernetes.slack.com/messages/C6RFQ3T5H/) - - [Discuss](https://discuss.kubernetes.io/tags/office-hours) - - [YouTube](https://www.youtube.com/playlist?list=PL69nYSiGNLP3azFUvYJjGn45YbF6C-uIg) - - [Meet Our Contributors](https://github.com/kubernetes/community/blob/master/mentoring/programs/meet-our-contributors.md) - [Slack](https://kubernetes.slack.com/messages/C8WRR2BB9/) - [YouTube](https://www.youtube.com/playlist?list=PL69nYSiGNLP3QpQrhZq_sLYo77BVKv09F) - Onboarding new contributors diff --git a/elections/steering/2022/ballots.csv b/elections/steering/2022/ballots.csv new file mode 100644 index 00000000..65e34f11 --- /dev/null +++ b/elections/steering/2022/ballots.csv @@ -0,0 +1,220 @@ +qedrakmar,lavalamp,bentheelder,mrbobbytables,cpanato,palnabarun,deads2k,cici37 +6,8,4,2,3,5,7,1 +8,1,6,3,5,7,2,4 +8,8,1,2,8,8,8,3 +8,1,1,8,8,8,1,8 +8,8,3,4,1,2,8,8 +6,7,2,1,4,3,8,5 +6,7,1,2,3,5,8,4 +8,2,3,4,6,8,1,5 +6,8,4,2,7,3,5,1 +8,1,2,3,8,8,4,5 +8,5,1,3,4,2,6,7 +7,5,2,1,3,4,6,8 +8,8,8,8,8,8,8,8 +3,8,1,2,3,3,8,4 +No opinion,No opinion,3,1,No opinion,No opinion,2,No opinion +8,7,5,1,4,3,2,6 +No opinion,5,1,2,6,3,4,No opinion +No opinion,2,1,3,No opinion,No opinion,No opinion,No opinion +No opinion,No opinion,7,No opinion,No opinion,8,No opinion,No opinion +8,1,2,8,8,8,4,3 +1,7,4,2,5,6,8,3 +8,1,3,5,8,6,4,2 +3,2,3,1,8,8,8,2 +8,4,2,8,8,8,3,1 +No opinion,2,No opinion,No opinion,No opinion,No opinion,1,No opinion +8,5,3,7,2,6,1,4 +8,1,4,2,5,8,3,8 +6,8,1,2,3,4,8,5 +5,8,2,1,6,4,7,3 +4,4,2,1,8,8,3,8 +4,4,2,1,8,8,3,8 +4,8,7,3,6,5,1,2 +8,8,8,1,4,5,2,3 +6,1,3,4,6,6,5,2 +No opinion,No opinion,2,3,4,1,No opinion,No opinion +8,5,1,1,4,6,7,5 +No opinion,1,2,5,No opinion,No opinion,4,3 +8,7,4,1,6,2,3,5 +4,4,1,1,4,4,4,4 +7,8,8,8,7,7,8,7 +8,1,2,3,8,8,8,4 +8,8,1,1,3,2,8,2 +4,7,3,1,2,5,8,6 +4,2,2,1,3,2,1,3 +7,8,1,2,5,3,8,4 +8,1,3,4,8,8,2,8 +8,2,3,4,5,8,1,8 +8,7,5,1,2,3,4,6 +7,1,3,4,6,8,2,5 +5,7,2,3,1,6,8,4 +5,7,3,2,6,4,8,1 +5,7,1,2,8,3,4,6 +4,7,3,1,6,5,8,2 +No opinion,3,1,4,No opinion,No opinion,5,2 +3,2,2,1,2,3,3,1 +8,2,1,3,8,8,4,8 +8,8,8,8,8,8,8,8 +8,1,4,5,8,8,3,2 +No opinion,No opinion,No opinion,3,1,No opinion,No opinion,2 +7,4,2,1,6,5,8,3 +3,No opinion,2,1,4,6,No opinion,5 +8,8,2,2,3,1,8,3 +No opinion,No opinion,3,2,1,4,No opinion,No opinion +3,8,1,1,4,5,6,4 +7,4,5,3,2,1,8,6 +6,3,1,5,8,4,2,8 +5,8,4,2,3,1,7,6 +8,8,8,2,3,1,8,4 +No opinion,3,3,2,4,1,8,4 +7,8,1,1,8,4,2,8 +6,2,3,5,8,7,1,4 +7,8,6,4,1,2,3,5 +8,7,3,2,5,1,4,6 +8,2,8,8,8,3,1,8 +8,7,3,4,8,6,1,4 +2,2,2,2,2,1,2,2 +No opinion,No opinion,8,No opinion,8,No opinion,No opinion,No opinion +8,8,2,1,8,8,8,8 +No opinion,8,8,8,No opinion,No opinion,No opinion,No opinion +8,8,8,1,2,3,8,8 +3,3,2,2,2,1,3,2 +8,6,4,1,5,3,2,7 +8,8,2,1,4,8,3,8 +8,8,2,3,8,1,8,8 +2,2,1,1,1,2,2,2 +8,8,1,5,2,3,8,4 +No opinion,No opinion,No opinion,2,No opinion,1,No opinion,No opinion +8,3,2,4,8,8,1,8 +8,8,8,3,2,1,8,8 +6,3,2,1,6,6,3,6 +No opinion,2,1,3,No opinion,No opinion,No opinion,No opinion +6,2,3,1,8,5,7,4 +No opinion,No opinion,2,No opinion,No opinion,No opinion,1,No opinion +3,4,1,1,1,1,2,2 +8,8,8,1,8,4,3,2 +8,2,3,1,5,4,6,7 +8,1,1,1,8,1,4,4 +8,8,2,4,1,8,8,3 +8,8,4,3,2,1,8,8 +4,6,2,3,1,7,8,5 +8,4,1,3,8,8,8,2 +No opinion,No opinion,8,6,6,8,No opinion,No opinion +6,4,3,2,5,7,1,8 +6,1,3,No opinion,No opinion,5,2,4 +4,8,1,2,5,6,8,3 +8,7,1,3,8,2,2,7 +2,No opinion,No opinion,3,No opinion,4,No opinion,1 +8,5,1,2,8,6,3,7 +6,3,1,2,4,7,8,5 +8,2,4,3,8,8,5,1 +8,2,4,5,6,7,3,1 +No opinion,1,2,4,No opinion,No opinion,3,No opinion +8,1,8,8,3,8,2,8 +7,5,2,3,8,6,1,4 +8,1,2,3,4,5,6,7 +No opinion,No opinion,No opinion,No opinion,8,8,No opinion,No opinion +8,8,3,2,4,1,8,8 +8,4,2,5,3,1,8,8 +No opinion,No opinion,No opinion,No opinion,No opinion,1,No opinion,No opinion +No opinion,No opinion,5,No opinion,No opinion,1,No opinion,No opinion +5,6,2,4,3,1,8,7 +No opinion,No opinion,2,3,4,1,No opinion,No opinion +8,2,4,1,8,5,3,8 +8,2,3,1,5,6,7,4 +8,5,3,1,4,7,2,6 +5,4,2,1,3,1,4,4 +8,No opinion,4,1,2,3,7,No opinion +No opinion,No opinion,No opinion,No opinion,No opinion,1,No opinion,No opinion +5,6,1,2,4,8,7,3 +8,6,4,2,7,3,1,5 +No opinion,No opinion,No opinion,No opinion,No opinion,8,No opinion,No opinion +8,4,1,2,8,8,5,3 +5,6,3,8,4,1,7,2 +8,8,4,2,8,1,3,8 +8,8,1,1,8,8,8,1 +8,6,1,3,4,2,5,7 +No opinion,No opinion,8,No opinion,5,No opinion,8,No opinion +6,5,4,1,2,3,8,7 +No opinion,2,1,3,4,No opinion,No opinion,5 +8,2,3,1,4,7,6,5 +2,7,6,1,4,5,8,3 +3,8,1,1,1,2,8,3 +8,1,8,8,8,8,1,1 +No opinion,No opinion,2,No opinion,No opinion,1,No opinion,No opinion +2,4,No opinion,1,No opinion,No opinion,8,3 +7,4,2,1,6,5,8,3 +No opinion,No opinion,2,2,No opinion,1,No opinion,2 +7,6,4,3,5,1,2,8 +8,8,3,8,1,4,8,2 +No opinion,4,2,1,No opinion,No opinion,3,No opinion +No opinion,No opinion,3,2,No opinion,1,No opinion,No opinion +8,4,3,1,7,6,5,2 +6,8,2,7,4,5,3,1 +No opinion,4,5,4,2,1,No opinion,No opinion +7,6,5,4,3,1,8,2 +8,8,8,8,8,2,1,3 +6,7,2,1,4,5,3,8 +8,2,8,1,8,8,3,8 +8,8,8,8,8,8,8,8 +8,8,2,1,8,6,5,3 +8,8,8,8,8,8,8,8 +4,1,2,2,8,5,6,8 +2,No opinion,4,1,No opinion,No opinion,3,No opinion +8,3,2,5,7,6,4,1 +8,1,4,2,7,6,3,5 +No opinion,3,1,2,No opinion,No opinion,5,4 +8,1,2,4,7,6,5,3 +7,6,2,1,5,3,8,4 +No opinion,7,8,No opinion,5,5,8,6 +6,1,2,3,4,5,8,7 +3,No opinion,2,4,No opinion,No opinion,1,No opinion +4,7,6,1,5,2,8,3 +3,8,7,8,5,2,6,5 +5,No opinion,No opinion,2,3,1,No opinion,4 +8,1,1,8,8,8,1,8 +8,4,2,3,8,8,1,8 +6,7,1,2,3,4,8,5 +5,8,1,2,4,3,8,6 +8,8,3,2,8,8,8,1 +No opinion,2,No opinion,No opinion,No opinion,No opinion,1,3 +8,3,2,6,7,4,1,5 +8,4,2,3,7,5,1,6 +No opinion,No opinion,3,2,4,No opinion,1,No opinion +8,8,8,8,8,8,8,8 +5,6,2,1,4,3,7,8 +8,8,3,1,8,2,8,8 +7,3,4,2,5,8,6,1 +8,8,8,8,8,8,8,8 +No opinion,4,2,3,No opinion,No opinion,1,5 +No opinion,No opinion,1,1,3,1,2,3 +No opinion,No opinion,1,1,3,1,2,3 +2,8,1,4,3,5,7,6 +3,1,7,2,6,4,8,5 +7,5,3,1,4,2,8,6 +8,8,1,8,8,8,8,8 +No opinion,No opinion,8,No opinion,No opinion,8,8,No opinion +5,3,1,1,2,2,8,4 +7,6,3,1,4,2,5,8 +8,3,2,1,8,8,4,8 +8,8,8,8,8,1,8,8 +2,8,3,4,1,8,8,8 +6,5,2,1,8,7,3,4 +No opinion,No opinion,No opinion,No opinion,8,8,No opinion,8 +5,5,1,2,3,5,4,5 +8,2,8,8,8,8,1,3 +8,2,1,3,8,8,6,7 +8,8,1,8,8,8,8,8 +5,1,2,8,5,3,5,4 +No opinion,2,3,No opinion,No opinion,No opinion,1,No opinion +6,7,1,3,4,5,8,2 +8,6,1,2,4,3,7,5 +3,4,2,1,7,6,8,5 +2,2,2,1,2,2,2,2 +7,8,3,1,2,4,5,6 +1,1,1,1,2,2,8,2 +8,8,1,1,8,8,1,8 +6,2,3,4,8,5,1,7 +3,No opinion,2,1,4,5,No opinion,6 +8,4,1,8,8,2,3,8 diff --git a/elections/steering/2022/results.md b/elections/steering/2022/results.md new file mode 100644 index 00000000..37637496 --- /dev/null +++ b/elections/steering/2022/results.md @@ -0,0 +1,23 @@ +# Results of the 2022 Steering Committee Election + +- Number of seats open: 3 (2 year term) +- Number of eligible voters: 698 +- Number of votes cast: 219 +- Turnout: 31.37% + +## Winners + +The winners of the open seats are as follows for their two year term: + +1. [Bob Killen](https://github.com/mrbobbytables) +2. [Benjamin Elder](https://github.com/bentheelder) +3. [Nabarun Pal](https://github.com/palnabarun) + +The rest of the candidates were placed as follows: +4. [Cici Huang](https://github.com/cici37) +5. [Carlos Tadeu Panato Junior](https://github.com/cpanato) +6. [Daniel Smith](https://github.com/lavalamp) +7. [David Eads](https://github.com/deads2k) +8. [Noah Abrahams](https://github.com/qedrakmar) + +Proportional representation limits were not invoked for this election. diff --git a/elections/steering/2023-GB/OWNERS b/elections/steering/2023-GB/OWNERS new file mode 100644 index 00000000..66b007e9 --- /dev/null +++ b/elections/steering/2023-GB/OWNERS @@ -0,0 +1,4 @@ +approvers: + - jberkus + - mrbobbytables + diff --git a/elections/steering/2023-GB/ballots.csv b/elections/steering/2023-GB/ballots.csv new file mode 100644 index 00000000..1b1e77b5 --- /dev/null +++ b/elections/steering/2023-GB/ballots.csv @@ -0,0 +1,7 @@ +cblecker,justaugustus +1,2 +1,2 +2,1 +1,2 +1,2 +2,1 diff --git a/elections/steering/2023-GB/candidate-cblecker.md b/elections/steering/2023-GB/candidate-cblecker.md new file mode 100644 index 00000000..9ab44282 --- /dev/null +++ b/elections/steering/2023-GB/candidate-cblecker.md @@ -0,0 +1,6 @@ +------------------------------------------------------------- +name: Christoph Blecker +ID: cblecker +------------------------------------------------------------- + +# Christoph Blecker diff --git a/elections/steering/2023-GB/candidate-justaugustus.md b/elections/steering/2023-GB/candidate-justaugustus.md new file mode 100644 index 00000000..3e70e44c --- /dev/null +++ b/elections/steering/2023-GB/candidate-justaugustus.md @@ -0,0 +1,6 @@ +------------------------------------------------------------- +name: Stephen Augustus +ID: justaugustus +------------------------------------------------------------- + +# Stephen Augustus diff --git a/elections/steering/2023-GB/election.yaml b/elections/steering/2023-GB/election.yaml new file mode 100644 index 00000000..0db85456 --- /dev/null +++ b/elections/steering/2023-GB/election.yaml @@ -0,0 +1,13 @@ +name: 2023 Kubernetes CNCF Governing Board Election +organization: Kubernetes +start_datetime: 2023-01-19 00:00:01 +end_datetime: 2023-01-22 11:59:59 +no_winners: 1 +allow_no_opinion: False +delete_after: True +election_officers: + - mrbobbytables + - jberkus +eligibility: Eligibility is limited to the [current Steering Committee Members](https://github.com/kubernetes/steering/tree/c0e6eafa131bb5918bd24653233568a44439497f#members) +exception_description: No exception requests accepted for the GB election. +exception_due: 2023-01-19 00:00:01 diff --git a/elections/steering/2023-GB/election_desc.md b/elections/steering/2023-GB/election_desc.md new file mode 100644 index 00000000..618757dd --- /dev/null +++ b/elections/steering/2023-GB/election_desc.md @@ -0,0 +1,3 @@ +# Vote for the Kubernetes CNCF GB Seat + +Please complete your voting by the end of 1/22/2023. diff --git a/elections/steering/2023-GB/results.md b/elections/steering/2023-GB/results.md new file mode 100644 index 00000000..af809839 --- /dev/null +++ b/elections/steering/2023-GB/results.md @@ -0,0 +1,11 @@ +# Results of the 2023 Kubernetes CNCF Governing Board representative + +- Number of seats open: 1 (2 year term) +- Number of eligible voters: 7 +- Number of votes cast: 6 +- Turnout: 86% + +## Winner + +- Christoph Blecker + diff --git a/elections/steering/2023-GB/voters.yaml b/elections/steering/2023-GB/voters.yaml new file mode 100644 index 00000000..b1723224 --- /dev/null +++ b/elections/steering/2023-GB/voters.yaml @@ -0,0 +1,8 @@ +eligible_voters: +- BenTheElder +- cblecker +- cpanato +- justaugustus +- mrbobbytables +- palnabarun +- tpepper diff --git a/elections/steering/OWNERS b/elections/steering/OWNERS index de4ba9fd..a08ed834 100644 --- a/elections/steering/OWNERS +++ b/elections/steering/OWNERS @@ -2,11 +2,12 @@ approvers: - jberkus - - parispittman - jdumars - committee-steering - sig-contributor-experience-leads - coderanger - dims +emeritus_approvers: + - parispittman labels: - committee/steering diff --git a/events/2016/developer-summit-2016/KubDevSummitVoting.md b/events/2016/developer-summit-2016/KubDevSummitVoting.md index 46909c02..265a27e5 100644 --- a/events/2016/developer-summit-2016/KubDevSummitVoting.md +++ b/events/2016/developer-summit-2016/KubDevSummitVoting.md @@ -1,33 +1,31 @@ -###Kubernetes Developer's Summit Discussion Topics Voting
-###
-A voting poll for discussion topic proposals has been created, and the link to the poll can be found [here][poll].
-
-The poll will close on 10/07/16 at 23:59:59 PDT.
-
-#### How Does it Work?
-####
-The voting uses the Condorcet method, which relies on relative rankings to pick winners. You can read more about the Condorcet method and the voting service we're using on the [CIVS website][civs].
-
-There are 27 topics to choose from, and you will rank them from 1 (favorite) to 27 (least favorite). You can also mark "no opinion" on topics that you don't wish to include in the ranking.
-
-The poll on CIVS has just the topic titles for ease of viewing. For topic descriptions, please see this [spreadsheet][topics]. The topic order on the voting service should mirror the order on the spreadsheet.
-
-You will note the message saying "*Only the 15 favorite choices will win the poll*". CIVS requires a number be selected for winners, and we have arbitrarily chosen 15. The final schedule may include more or less than 15 of the submitted topics.
-
-##### A Small Request
-#####
-
-In order to make the poll accessible via URL, it has to be made "public". This means than any unique IP address can vote, which can be easily exploited for multiple votes.
-
-We fully expect the community to behave with sportsmanship and only vote once, and as such we almost didn't bring this concern up to begin with. However, we have chosen to explicitly address it, in order to reiterate the importance of everyone's voice receiving equal weight in a community-driven event.
-
-#### After the Poll
-####
-A schedule will be made from the winning topics with
-some editorial license, and the schedule will be announced to the group
-at least a week before the event.
-
-[//]: # (Reference Links)
- [civs]: <http://civs.cs.cornell.edu/>
- [poll]: <http://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_9ef4ac5e58c4cab1&akey=7cc2652f9715b525>
- [topics]: <https://docs.google.com/spreadsheets/d/1bmp6uLG8H32MVz02-zsieeKKZDZITw-8B6UjOaNTXOA/edit?usp=sharing>
\ No newline at end of file +### Kubernetes Developer's Summit Discussion Topics Voting + +A voting poll for discussion topic proposals has been created, and the link to the poll can be found [here][poll]. + +The poll will close on 10/07/16 at 23:59:59 PDT. + +#### How Does it Work? + +The voting uses the Condorcet method, which relies on relative rankings to pick winners. You can read more about the Condorcet method and the voting service we're using on the [CIVS website][civs]. + +There are 27 topics to choose from, and you will rank them from 1 (favorite) to 27 (least favorite). You can also mark "no opinion" on topics that you don't wish to include in the ranking. + +The poll on CIVS has just the topic titles for ease of viewing. For topic descriptions, please see this [spreadsheet][topics]. The topic order on the voting service should mirror the order on the spreadsheet. + +You will note the message saying "*Only the 15 favorite choices will win the poll*". CIVS requires a number be selected for winners, and we have arbitrarily chosen 15. The final schedule may include more or less than 15 of the submitted topics. + +##### A Small Request + +In order to make the poll accessible via URL, it has to be made "public". This means than any unique IP address can vote, which can be easily exploited for multiple votes. + +We fully expect the community to behave with sportsmanship and only vote once, and as such we almost didn't bring this concern up to begin with. However, we have chosen to explicitly address it, in order to reiterate the importance of everyone's voice receiving equal weight in a community-driven event. + +#### After the Poll + +A schedule will be made from the winning topics with +some editorial license, and the schedule will be announced to the group +at least a week before the event. + +[civs]: <http://civs.cs.cornell.edu/> +[poll]: <http://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_9ef4ac5e58c4cab1&akey=7cc2652f9715b525> +[topics]: <https://docs.google.com/spreadsheets/d/1bmp6uLG8H32MVz02-zsieeKKZDZITw-8B6UjOaNTXOA/edit?usp=sharing> diff --git a/events/2016/developer-summit-2016/Kubernetes_Dev_Summit.md b/events/2016/developer-summit-2016/Kubernetes_Dev_Summit.md index f66df508..e0448e41 100644 --- a/events/2016/developer-summit-2016/Kubernetes_Dev_Summit.md +++ b/events/2016/developer-summit-2016/Kubernetes_Dev_Summit.md @@ -1,12 +1,11 @@ # Kubernetes Dev Summit -# ## Edit - Event Location -## + The event is on the 4th Floor of the *Union Street Tower* of the Sheraton Seattle Hotel. # About the Event -# + The Kubernetes Developers' Summit provides an avenue for Kubernetes developers to connect face to face and mindshare about future community development and community governance endeavors. @@ -15,7 +14,7 @@ In some sense, the summit is a real-life extension of the community meetings and SIG meetings. ## Event Format -## + The Dev Summit is a "loosely-structured [unconference][uncf]". Rather than speakers and presentations, we will have moderators/facilitators and discussion topics, alongside all-day completely unstructured @@ -35,7 +34,7 @@ Then, there will be 2 smaller rooms for hacking / unstructured discussion all day. #### Who Should Go? -#### + The target audience is the Kubernetes developer community. The group will be relatively small (~120-150 attendees), to improve communication and facilitate easier decision-making. The majority of the attendees @@ -52,7 +51,7 @@ Please note that this Summit is not the right environment for people to involved initially. #### Call for Proposals -#### + Proposals for discussion topics can be submitted through [this form][propfrm] by September 30, 23:59 PT. If you propose a session topic, please be prepared to attend and facilitate the session if it gets @@ -71,7 +70,7 @@ some editorial license, and the schedule will be announced to the group at least a week before the event. ## When & Where? -## + The Dev Summit will follow [Kubecon][kbc] on November 10th, 2016. Fortunately for those who attend Kubecon, the Dev Summit will be at the same venue, [the Sheraton Seattle Hotel][sher]. As of now, the day's @@ -79,18 +78,17 @@ activities should run from breakfast being served at 8 AM to closing remarks ending around 3:30 PM, with an external happy hour to follow. ## Desired outcomes -## + * Generate notes from the sessions to feed the project's documentation and knowledge base, and also to keep non-attendees plugged in * Make (and document) recommendations and decisions for the near-term and mid-term future of the project * Come up with upcoming action items, as well as leaders for those action items, for the various topics that we discuss -[//]: # (Reference Links) - [uncf]: <https://en.wikipedia.org/wiki/Unconference> - [mtp]: <http://www.meetup.com/topics/kubernetes/all/> - [lotfrm]: <https://docs.google.com/forms/d/e/1FAIpQLSe8t6pvRjh1OeF6xrXKbXmzHGMhQ4c-MbZ6QUr9APJNjpgAzA/viewform> - [propfrm]: <https://docs.google.com/forms/d/e/1FAIpQLSf30x18OGCv_Und7qah4y5Zs3Z-0YoBCo964ZsmhtbxBjMzxA/viewform> - [civs]: <http://civs.cs.cornell.edu/> - [kbc]: <http://events.linuxfoundation.org/events/kubecon> - [sher]: <http://www.sheratonseattle.com/> +[uncf]: <https://en.wikipedia.org/wiki/Unconference> +[mtp]: <http://www.meetup.com/topics/kubernetes/all/> +[lotfrm]: <https://docs.google.com/forms/d/e/1FAIpQLSe8t6pvRjh1OeF6xrXKbXmzHGMhQ4c-MbZ6QUr9APJNjpgAzA/viewform> +[propfrm]: <https://docs.google.com/forms/d/e/1FAIpQLSf30x18OGCv_Und7qah4y5Zs3Z-0YoBCo964ZsmhtbxBjMzxA/viewform> +[civs]: <http://civs.cs.cornell.edu/> +[kbc]: <http://events.linuxfoundation.org/events/kubecon> +[sher]: <http://www.sheratonseattle.com/> diff --git a/events/OWNERS b/events/OWNERS index 11bddf19..71503abe 100644 --- a/events/OWNERS +++ b/events/OWNERS @@ -1,9 +1,10 @@ # See the OWNERS docs at https://go.k8s.io/owners approvers: - - parispittman - mrbobbytables - jberkus - sig-contributor-experience-leads +emeritus_approvers: + - parispittman labels: - sig/contributor-experience diff --git a/events/office-hours.md b/events/office-hours.md deleted file mode 100644 index 2ebb24c6..00000000 --- a/events/office-hours.md +++ /dev/null @@ -1,184 +0,0 @@ ---- -title: Office Hours -weight: 3 -description: | - Office Hours is a live stream where we answer live questions about Kubernetes - from users on the YouTube channel. Office hours are a regularly scheduled - meeting where people can bring topics to discuss with the greater community. - They are great for answering questions, getting feedback on how you’re using - Kubernetes, or to just passively learn by following along. ---- - -# Kubernetes Community Office Hours - -Office Hours is a live stream where we answer live questions about Kubernetes -from **users** on the [YouTube channel]. Office hours are a regularly scheduled -meeting where people can bring topics to discuss with the greater community. -They are great for answering questions, getting feedback on how you’re using -Kubernetes, or to just passively learn by following along. - -### When and Where - -Third Wednesday of every month, there are two sessions: - -- European Edition: [9am ET] -- Western Edition: [5pm PT] - -Tune into the [Kubernetes YouTube Channel] to follow along. - -You can post questions on the [#office-hours channel] on Slack, or if you like -you can submit your question to Stack Overflow and have us take a look. - -### How it Works - -#### Bringing your own question - -If you submit a question on [discuss.kubernetes.io] that is prewritten that -always makes it easier for the panelists to read all your information ahead of -time. You can also submit a question from [StackOverflow]. - -As a thanks to the community the person asking the question can then ensure that -a well written answer makes it way to the question afterwards so that we can -build a knowledge base and help maintain the incoming questions. We can also use -the video archive of each meeting to bring context to each question we answer. - -Questions that aren’t addressed or need work can be punted to the next week or -we can encourage other people to give them a look, at a bare minimum we can at -least help socialize the difficult questions. - -#### What’s on topic? - -Specific questions about Kubernetes as pertaining to the topic. Since this is a -Q&A format, we’d like questions that can be answered generally. So for example: - -- Bad: My ingress configuration is broken please fix it. (Dependent on local - configuration) -- Good: My ingress configuration is broken can you discuss what problems you - usually see and common mistakes that people make so I can avoid them? - (Generalized and can communicate things that can help multiple people) -- Bad: How do I deploy my application in Kubernetes? (Easy to look up, tons of - content on this) -- Good: What best practice techniques are there for deploying applications in - Kubernetes? (Nuanced version lets us cover RBAC, application lifecycle) -- Bad: My pods aren’t coming up on a node. (Vague) -- Good: My pods aren’t coming up or misbehaving, what are the debugging steps to - find out the root cause? (Helps us communicate the thought process for - debugging to a general audience) - -#### What’s off topic? - -Developer/Contributor questions: This event is for end users and operators, -there is a separate livestream called [Meet our Contributors] where you can ask -questions about getting started contributing, participating in peer reviews, -and other development topics. - -Local installation and debugging: The participants don’t have access to your -network or your hardware. The host can/should help the user transform a vague -question into something answerable and reusable. - -### Archives - -Archives of all the sessions are kept here: - -- [Office Hours playlist] - -### Volunteering - -We're always looking for volunteers to host and answer questions. Volunteers -looking to host hours in more time zones are also welcome to join in and help us -expand. - -- [Volunteer working sheet] - -If you have any questions ping [@castrojo]. - -## Host Information - -This information is for the host/panel to prep the show. - -### Host Checklist - -- [ ] 1st of the month: Create the livestream events in YouTube. -- [ ] 1st of the month: Update topic in [#kubernetes-users], [#office-hours], - and [#kubernetes-novice] with the correct YouTube URLs. -- [ ] 2nd wednesday of the month: Remind panelists of dates, get confirmation - for each event. -- [ ] Monday before: Post "Office hours is this Wednesday" with the links to - everything in [#kubernetes-users], [#office-hours], and [#kubernetes-novice]. -- [ ] Monday before: Post to the general section of discuss.k8s.io with a link - to the show and a link to this github page. Tag the post with [#office-hours] -- [ ] Monday before: Tweet "Office hours is this Wednesday" with the links to - everything, send a mail to social@cncf.io to RT your tweet. -- [ ] -1h before show: Tweet again, repost "Office hours is going live in ~1h" - with the links to everything in [#kubernetes-users], [#office-hours], and - [#kubernetes-novice]. -- [ ] -30m before show: Ensure panelists have link to Zoom meeting. -- [ ] -30m before show: Prep a hack.md document with notes and questions from - the channel over the course of the last month, ensure panelists have the URL. -- [ ] 0: Go live, do the show. -- [ ] After show: Collate links from the show as markdown and post it in the - show thread that you posted in the forums. -- [ ] After show: Check and publish the video on YouTube, ensure it's in the - Office Hours playlist. - -### Intro Script - -Welcome everyone to today’s Kubernetes Office Hours, where we answer your user -questions live on the air with our esteemed panel of experts. You can find us in -[#office-hours] on slack, and check the topic for the URL for the information. - -- Before we begin let’s start by introducing ourselves: (Give each panelist about - a minute) -- Before we start here are the ground rules: - - This is a Kubernetes event so the Code of Conduct is in effect, please be - excellent to each other. - - This is a judgement-free zone, everyone had to start from somewhere so please - help out your buddy by having a supportive environment in the channel. - - While we will do our best to answer your questions the panel doesn’t have - access to your cluster, so live debugging is off topic, but we will do our - best to get you moving down the next step. - - Panelists, you’re encouraged to expand on answers with your experiences and - pro-tips. - - Audience, you can help by pasting in URLs to official docs, blogs, or - anything that might be relevant to the topic at hand. - - Post your questions on [discuss.kubernetes.io]. - - You can also help us out by tweeting, spreading the word, and paying it - forward. - - This panel is made entirely of volunteers, if you want to rotate in please - let us know, we love to have new people rotate in and help out. - -### Contest - -The hack.md notes document will have a list of who has asked questions, roll a -dice to see who won the shirts. On occasion if someone from the audience has -been helpful feel free to give them a shirt as well, we want to reward people -for helping others. Note: Multi-sided dice not included. - -### Outro - -(Note, the companies will change over time depending on the hosts) - -- Thanks to the following companies for supporting the community with developer - volunteers: Giant Swarm, StockX, Pivotal, Pusher.com, Weaveworks, VMware, - University of Michigan, Red Hat, and Utility Warehouse. Special thanks to CNCF - for sponsoring the t-shirt giveaway. - -And lastly, feel free to hang out in [#office-hours] afterwards, if the other -channels are too busy for you and you’re looking for a friendly home, you’re -more than welcome to pull up a chair and hang out. - - -[YouTube channel]: https://www.youtube.com/c/KubernetesCommunity/ -[9am ET]: http://www.thetimezoneconverter.com/?t=09:00&tz=ET%20%28Eastern%20Time%29 -[5pm PT]: http://www.thetimezoneconverter.com/?t=17:00&&tz=PT%20(Pacific%20Time) -[Kubernetes YouTube Channel]: https://www.youtube.com/c/KubernetesCommunity/live -[#office-hours channel]: https://kubernetes.slack.com/messages/office-hours -[discuss.kubernetes.io]: https://discuss.kubernetes.io -[StackOverflow]: https://stackoverflow.com/questions/tagged/kubernetes -[Meet our Contributors]: /mentoring/programs/meet-our-contributors.md -[Office Hours playlist]: https://www.youtube.com/watch?v=D0Q7wwljN30&list=PL69nYSiGNLP3azFUvYJjGn45YbF6C-uIg -[Volunteer working sheet]: http://bit.ly/k8s-office-hours-volunteers -[@castrojo]: https://github.com/castrojo -[#kubernetes-users]: https://kubernetes.slack.com/messages/kubernetes-users -[#office-hours]: https://kubernetes.slack.com/messages/office-hours -[#kubernetes-novice]: https://kubernetes.slack.com/messages/kubernetes-novice diff --git a/generator/annual-report/github_issue.tmpl b/generator/annual-report/github_issue.tmpl index 0c5b44df..b286e3df 100644 --- a/generator/annual-report/github_issue.tmpl +++ b/generator/annual-report/github_issue.tmpl @@ -29,3 +29,4 @@ If you have any questions or concerns about this process, you may reach the Stee /{{.Prefix}} {{.Label}} /committee steering +/area annual-reports diff --git a/generator/annual-report/sig_report.tmpl b/generator/annual-report/sig_report.tmpl index d018622a..2b9206e9 100644 --- a/generator/annual-report/sig_report.tmpl +++ b/generator/annual-report/sig_report.tmpl @@ -14,25 +14,16 @@ - - -3. KEP work in {{lastYear}} (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) +{{$releases := getReleases}} +{{$owingsig := .Dir}} +3. KEP work in {{lastYear}} (v{{$releases.Latest}}, v{{$releases.LatestMinusOne}}, v{{$releases.LatestMinusTwo}}): +{{- range $stage, $keps := filterKEPs $owingsig $releases}} + {{ $stage }}: + {{- range $keps}} + - [{{.Number}} - {{.Title}}](https://github.com/kubernetes/enhancements/tree/master/keps/{{.OwningSIG}}/{{.Name}}) - {{.LatestMilestone -}} + {{ end}} +{{- end}} + ## Project health @@ -80,43 +71,62 @@ In future, this will be generated from kubernetes/enhancements kep.yaml files Include any other ways you measure group membership -## Subprojects +## [Subprojects](https://git.k8s.io/community/{{.Dir}}#subprojects) +{{- define "subprojects" -}} +{{- $owingsig := .Dir -}} +{{- if .New}} + +**New in {{lastYear}}:** +{{range .New}} + - {{.}} +{{- end}} +{{- end}} + +{{- if .Retired}} + +**Retired in {{lastYear}}:** +{{range .Retired}} + - {{.}} +{{- end}} +{{- end}} + +{{- if .Continuing}} -<!-- -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` ---> +**Continuing:** +{{range .Continuing}} + - {{.}} +{{- end}} +{{- end}} +{{- end}} -New in $YYYY: -- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) -- +{{ template "subprojects" (getCategorizedSubprojects .Dir) }} -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](https://git.k8s.io/community/{{.Dir}}#working-groups) +{{ $categorizedWorkingGroups := getCategorizedWorkingGroups .Dir }} +{{- if $categorizedWorkingGroups.New}} -## Working groups +**New in {{lastYear}}:** +{{range $categorizedWorkingGroups.New }} + - {{.}} +{{- end}} +{{- end}} -<!-- -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` ---> +{{- if $categorizedWorkingGroups.Retired}} -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 {{lastYear}}:** +{{range $categorizedWorkingGroups.Retired }} + - {{.}} +{{- end}} +{{- end}} -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)) -- +{{- if $categorizedWorkingGroups.Continuing}} -Continuing: -- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) -- +**Continuing:** +{{range $categorizedWorkingGroups.Continuing }} + - {{ . }} +{{- end}} +{{- end}} ## Operational diff --git a/generator/app.go b/generator/app.go index 0e67ec1d..09986697 100644 --- a/generator/app.go +++ b/generator/app.go @@ -17,18 +17,31 @@ limitations under the License. package main import ( + "context" + "encoding/json" "fmt" + "io" "io/ioutil" "log" + "net/http" "net/url" "os" "path/filepath" "regexp" "sort" + "strconv" "strings" "text/template" "time" + "k8s.io/enhancements/api" + + "github.com/google/go-github/v32/github" + + "github.com/go-git/go-git/v5" + "github.com/go-git/go-git/v5/plumbing" + "github.com/go-git/go-git/v5/storage/memory" + yaml "gopkg.in/yaml.v3" ) @@ -55,13 +68,99 @@ const ( regexRawGitHubURL = "https://raw.githubusercontent.com/(?P<org>[^/]+)/(?P<repo>[^/]+)/(?P<branch>[^/]+)/(?P<path>.*)" regexGitHubURL = "https://github.com/(?P<org>[^/]+)/(?P<repo>[^/]+)/(blob|tree)/(?P<branch>[^/]+)/(?P<path>.*)" + + // For KEPs automation + kepURL = "https://storage.googleapis.com/k8s-keps/keps.json" + // For Subprojects automation + communityRepoURL = "https://github.com/kubernetes/community.git" + localRepoPath = "." ) var ( - baseGeneratorDir = "" - templateDir = "generator" + baseGeneratorDir = "" + templateDir = "generator" + releases = Releases{} + cachedKEPs = []api.Proposal{} + repo = &git.Repository{} + annualReportYear = time.Time{} + currentYear = time.Time{} + commitFromAnnualReportYear = &plumbing.Hash{} + commitFromCurrentYear = &plumbing.Hash{} ) +type Releases struct { + Latest string + LatestMinusOne string + LatestMinusTwo string +} + +// TODO: improve as suggested in https://github.com/kubernetes/community/pull/7038#discussion_r1069456087 +func getLastThreeK8sReleases() (Releases, error) { + ctx := context.Background() + client := github.NewClient(nil) + + releases, _, err := client.Repositories.ListReleases(ctx, "kubernetes", "kubernetes", nil) + if err != nil { + return Releases{}, err + } + var result Releases + result.Latest = strings.Split(strings.TrimPrefix(*releases[0].TagName, "v"), ".")[0] + "." + strings.Split(strings.TrimPrefix(*releases[0].TagName, "v"), ".")[1] + result.LatestMinusOne = strings.Split(strings.TrimPrefix(*releases[1].TagName, "v"), ".")[0] + "." + strings.Split(strings.TrimPrefix(*releases[1].TagName, "v"), ".")[1] + result.LatestMinusTwo = strings.Split(strings.TrimPrefix(*releases[2].TagName, "v"), ".")[0] + "." + strings.Split(strings.TrimPrefix(*releases[2].TagName, "v"), ".")[1] + return result, nil +} + +func getReleases() Releases { + return releases +} + +func fetchKEPs() error { + url, err := url.Parse(kepURL) + if err != nil { + return fmt.Errorf("Error parsing url: %v", err) + } + + req, err := http.NewRequest("GET", url.String(), nil) + if err != nil { + return fmt.Errorf("Error creating request: %v", err) + } + + client := &http.Client{} + resp, err := client.Do(req) + if err != nil { + return fmt.Errorf("Error fetching KEPs: %v", err) + } + defer resp.Body.Close() + + body, err := ioutil.ReadAll(resp.Body) + if err != nil { + return fmt.Errorf("Error reading KEPs body: %v", err) + } + + err = json.Unmarshal(body, &cachedKEPs) + if err != nil { + return fmt.Errorf("Error unmarshalling KEPs: %v", err) + } + return nil +} + +func filterKEPs(owningSig string, releases Releases) (map[api.Stage][]api.Proposal, error) { + kepsByStage := make(map[api.Stage][]api.Proposal) + for _, kep := range cachedKEPs { + if kep.OwningSIG == owningSig { + for _, stage := range api.ValidStages { + if kep.Stage == stage && (strings.HasSuffix(kep.LatestMilestone, releases.Latest) || + strings.HasSuffix(kep.LatestMilestone, releases.LatestMinusOne) || + strings.HasSuffix(kep.LatestMilestone, releases.LatestMinusTwo)) { + kepsByStage[stage] = append(kepsByStage[stage], kep) + } + } + } + } + + return kepsByStage, nil +} + // FoldedString is a string that will be serialized in FoldedStyle by go-yaml type FoldedString string @@ -169,7 +268,8 @@ type Group struct { Leadership LeadershipGroup `yaml:"leadership"` Meetings []Meeting Contact Contact - Subprojects []Subproject `yaml:",omitempty"` + Subprojects []Subproject `yaml:",omitempty"` + KEPs map[string][]api.Proposal `yaml:",omitempty"` } type WGName string @@ -428,14 +528,18 @@ func getExistingContent(path string, fileFormat string) (string, error) { } var funcMap = template.FuncMap{ - "tzUrlEncode": tzURLEncode, - "trimSpace": strings.TrimSpace, - "trimSuffix": strings.TrimSuffix, - "githubURL": githubURL, - "orgRepoPath": orgRepoPath, - "now": time.Now, - "lastYear": lastYear, - "toUpper": strings.ToUpper, + "tzUrlEncode": tzURLEncode, + "trimSpace": strings.TrimSpace, + "trimSuffix": strings.TrimSuffix, + "githubURL": githubURL, + "orgRepoPath": orgRepoPath, + "now": time.Now, + "lastYear": lastYear, + "toUpper": strings.ToUpper, + "filterKEPs": filterKEPs, + "getReleases": getReleases, + "getCategorizedSubprojects": getCategorizedSubprojects, + "getCategorizedWorkingGroups": getCategorizedWorkingGroups, } // lastYear returns the last year as a string @@ -456,8 +560,9 @@ func githubURL(url string) string { } // orgRepoPath converts either -// - a regular GitHub url of form https://github.com/org/repo/blob/branch/path/to/file -// - a raw GitHub url of form https://raw.githubusercontent.com/org/repo/branch/path/to/file +// - a regular GitHub url of form https://github.com/org/repo/blob/branch/path/to/file +// - a raw GitHub url of form https://raw.githubusercontent.com/org/repo/branch/path/to/file +// // to a string of form 'org/repo/path/to/file' func orgRepoPath(url string) string { for _, regex := range []string{regexRawGitHubURL, regexGitHubURL} { @@ -685,11 +790,243 @@ func writeYaml(data interface{}, path string) error { return enc.Encode(data) } +// get the first commit on a given date +func getCommitByDate(repo *git.Repository, date time.Time) (*plumbing.Hash, error) { + // Get the commit iterator + iterator, err := repo.Log(&git.LogOptions{Order: git.LogOrderCommitterTime}) + if err != nil { + return nil, err + } + + // Iterate through the commits + var commit *plumbing.Hash + for { + // Get the next commit + c, err := iterator.Next() + if err != nil { + if err == io.EOF { + break + } + return nil, err + } + + // Check if the commit date is less than or equal to the specified date + if c.Committer.When.Before(date) || c.Committer.When.Equal(date) { + commit = &c.Hash + break + } + } + + return commit, nil +} + +// get the "sigs.yaml" file from a given commit +func getFileFromCommit(repo *git.Repository, commit *plumbing.Hash, filename string) ([]byte, error) { + // Get the commit object + obj, err := repo.CommitObject(*commit) + if err != nil { + return nil, err + } + + // Get the commit tree + tree, err := obj.Tree() + if err != nil { + return nil, err + } + + // Get the file from the tree + entry, err := tree.FindEntry(filename) + if err != nil { + return nil, err + } + + // Get the file content + file, err := repo.BlobObject(entry.Hash) + if err != nil { + return nil, err + } + + reader, err := file.Reader() + if err != nil { + return nil, err + } + defer reader.Close() + + content, err := ioutil.ReadAll(reader) + if err != nil { + return nil, err + } + + return content, nil +} + +func getSigsYamlFromCommit(repo *git.Repository, commitFromAnnualReportYear, commitFromCurrentYear plumbing.Hash) (Context, Context, error) { + var annualReportYearSigs, currentYearSigs Context + + annualReportYearSigFile, err := getFileFromCommit(repo, &commitFromAnnualReportYear, sigsYamlFile) + if err != nil { + return Context{}, Context{}, err + } + err = yaml.Unmarshal([]byte(annualReportYearSigFile), &annualReportYearSigs) + if err != nil { + return Context{}, Context{}, err + } + + currentYearSigFile, err := getFileFromCommit(repo, &commitFromCurrentYear, sigsYamlFile) + if err != nil { + return Context{}, Context{}, err + } + err = yaml.Unmarshal([]byte(currentYearSigFile), ¤tYearSigs) + if err != nil { + return Context{}, Context{}, err + } + + return annualReportYearSigs, currentYearSigs, nil +} + +func contains(strlist []string, val string) bool { + for _, str := range strlist { + if str == val { + return true + } + } + return false +} + +func getCategorizedSubprojects(dir string) (map[string][]string, error) { + subprojectsMap := make(map[string][]string) + // set for the subprojects in the annual year + annualSubprojects := make(map[string]bool) + + annualReportYearSigs, currentYearSigs, err := getSigsYamlFromCommit(repo, *commitFromAnnualReportYear, *commitFromCurrentYear) + if err != nil { + return nil, err + } + + // iterate over sigs from the annual report year (say 2022) + for _, sig1 := range annualReportYearSigs.Sigs { + if sig1.Dir != dir { + continue + } + for _, sub1 := range sig1.Subprojects { + annualSubprojects[sub1.Name] = true + } + } + + // iterate over sigs from the current year (say 2023) + for _, sig2 := range currentYearSigs.Sigs { + if sig2.Dir != dir { + continue + } + for _, sub2 := range sig2.Subprojects { + if annualSubprojects[sub2.Name] { + subprojectsMap["Continuing"] = append(subprojectsMap["Continuing"], sub2.Name) + delete(annualSubprojects, sub2.Name) + } else { + subprojectsMap["New"] = append(subprojectsMap["New"], sub2.Name) + } + } + } + + for sub := range annualSubprojects { + subprojectsMap["Retired"] = append(subprojectsMap["Retired"], sub) + } + + return subprojectsMap, nil +} + +func getCategorizedWorkingGroups(dir string) (map[string][]string, error) { + workingGroupsMap := make(map[string][]string) + + // set for the working groups in the annual year + annualWGs := make(map[string]bool) + annualReportYearSigs, currentYearSigs, err := getSigsYamlFromCommit(repo, *commitFromAnnualReportYear, *commitFromCurrentYear) + if err != nil { + return nil, err + } + + annualReportYearSigs.Complete() + annualReportYearSigs.Sort() + currentYearSigs.Complete() + currentYearSigs.Sort() + + // iterate over the ReportingWGs from the annual report year (say 2022) + for _, sig := range annualReportYearSigs.Sigs { + if sig.Dir != dir { + continue + } + for _, wg := range sig.ReportingWGs { + annualWGs[string(wg)] = true + } + } + + // iterate over the ReportingWGs from the current year (say 2023) + for _, sig := range currentYearSigs.Sigs { + if sig.Dir != dir { + continue + } + for _, newWG := range sig.ReportingWGs { + if _, ok := annualWGs[string(newWG)]; !ok { + workingGroupsMap["New"] = append(workingGroupsMap["New"], string(newWG)) + } else { + workingGroupsMap["Continuing"] = append(workingGroupsMap["Continuing"], string(newWG)) + delete(annualWGs, string(newWG)) + } + } + } + + for wg := range annualWGs { + workingGroupsMap["Retired"] = append(workingGroupsMap["Retired"], string(wg)) + } + + return workingGroupsMap, nil +} + func main() { + // prep for automated listing of subprojects in the annual report + intLastYear, err := strconv.Atoi(lastYear()) + if err != nil { + log.Fatal(err) + } + annualReportYear = time.Date(intLastYear, time.January, 1, 0, 0, 0, 0, time.UTC) + currentYear = time.Date(intLastYear+1, time.January, 1, 0, 0, 0, 0, time.UTC) + + repo, err = git.PlainOpen(localRepoPath) + if err != nil { + if err == git.ErrRepositoryNotExists { + repo, err = git.Clone(memory.NewStorage(), nil, &git.CloneOptions{ + URL: communityRepoURL, + }) + } else { + log.Fatal(err) + } + } + + commitFromAnnualReportYear, err = getCommitByDate(repo, annualReportYear) + if err != nil { + log.Fatal(err) + } + + commitFromCurrentYear, err = getCommitByDate(repo, currentYear) + if err != nil { + log.Fatal(err) + } + + // fetch KEPs and cache them in the keps variable + err = fetchKEPs() + if err != nil { + log.Fatal(err) + } + + releases, err = getLastThreeK8sReleases() + if err != nil { + log.Fatal(err) + } + yamlPath := filepath.Join(baseGeneratorDir, sigsYamlFile) var ctx Context - err := readYaml(yamlPath, &ctx) + err = readYaml(yamlPath, &ctx) if err != nil { log.Fatal(err) } @@ -4,5 +4,30 @@ go 1.18 require ( github.com/client9/misspell v0.3.4 - gopkg.in/yaml.v3 v3.0.0-20190409140830-cdc409dda467 + github.com/go-git/go-git/v5 v5.2.0 + github.com/google/go-github/v32 v32.1.0 + gopkg.in/yaml.v3 v3.0.0-20200313102051-9f266ea9e77c + k8s.io/enhancements v0.0.0-20230113204613-7f681415a001 +) + +require ( + github.com/emirpasic/gods v1.12.0 // indirect + github.com/go-git/gcfg v1.5.0 // indirect + github.com/go-git/go-billy/v5 v5.0.0 // indirect + github.com/go-playground/locales v0.13.0 // indirect + github.com/go-playground/universal-translator v0.17.0 // indirect + github.com/go-playground/validator/v10 v10.4.1 // indirect + github.com/google/go-querystring v1.0.0 // indirect + github.com/imdario/mergo v0.3.11 // indirect + github.com/jbenet/go-context v0.0.0-20150711004518-d14ea06fba99 // indirect + github.com/kevinburke/ssh_config v0.0.0-20190725054713-01f96b0aa0cd // indirect + github.com/leodido/go-urn v1.2.1 // indirect + github.com/mitchellh/go-homedir v1.1.0 // indirect + github.com/pkg/errors v0.9.1 // indirect + github.com/sergi/go-diff v1.1.0 // indirect + github.com/xanzy/ssh-agent v0.2.1 // indirect + golang.org/x/crypto v0.0.0-20201002170205-7f63de1d35b0 // indirect + golang.org/x/net v0.0.0-20201224014010-6772e930b67b // indirect + golang.org/x/sys v0.0.0-20210112080510-489259a85091 // indirect + gopkg.in/warnings.v0 v0.1.2 // indirect ) @@ -1,6 +1,113 @@ +github.com/alcortesm/tgz v0.0.0-20161220082320-9c5fe88206d7 h1:uSoVVbwJiQipAclBbw+8quDsfcvFjOpI5iCf4p/cqCs= +github.com/alcortesm/tgz v0.0.0-20161220082320-9c5fe88206d7/go.mod h1:6zEj6s6u/ghQa61ZWa/C2Aw3RkjiTBOix7dkqa1VLIs= +github.com/anmitsu/go-shlex v0.0.0-20161002113705-648efa622239 h1:kFOfPq6dUM1hTo4JG6LR5AXSUEsOjtdm0kw0FtQtMJA= +github.com/anmitsu/go-shlex v0.0.0-20161002113705-648efa622239/go.mod h1:2FmKhYUyUczH0OGQWaF5ceTx0UBShxjsH6f8oGKYe2c= +github.com/armon/go-socks5 v0.0.0-20160902184237-e75332964ef5 h1:0CwZNZbxp69SHPdPJAN/hZIm0C4OItdklCFmMRWYpio= +github.com/armon/go-socks5 v0.0.0-20160902184237-e75332964ef5/go.mod h1:wHh0iHkYZB8zMSxRWpUBQtwG5a7fFgvEO+odwuTv2gs= github.com/client9/misspell v0.3.4 h1:ta993UF76GwbvJcIo3Y68y/M3WxlpEHPWIGDkJYwzJI= github.com/client9/misspell v0.3.4/go.mod h1:qj6jICC3Q7zFZvVWo7KLAzC3yx5G7kyvSDkc90ppPyw= -gopkg.in/check.v1 v0.0.0-20161208181325-20d25e280405 h1:yhCVgyC4o1eVCa2tZl7eS0r+SDo693bJlVdllGtEeKM= +github.com/creack/pty v1.1.9/go.mod h1:oKZEueFk5CKHvIhNR5MUki03XCEU+Q6VDXinZuGJ33E= +github.com/davecgh/go-spew v1.1.0/go.mod h1:J7Y8YcW2NihsgmVo/mv3lAwl/skON4iLHjSsI+c5H38= +github.com/davecgh/go-spew v1.1.1 h1:vj9j/u1bqnvCEfJOwUhtlOARqs3+rkHYY13jYWTU97c= +github.com/davecgh/go-spew v1.1.1/go.mod h1:J7Y8YcW2NihsgmVo/mv3lAwl/skON4iLHjSsI+c5H38= +github.com/emirpasic/gods v1.12.0 h1:QAUIPSaCu4G+POclxeqb3F+WPpdKqFGlw36+yOzGlrg= +github.com/emirpasic/gods v1.12.0/go.mod h1:YfzfFFoVP/catgzJb4IKIqXjX78Ha8FMSDh3ymbK86o= +github.com/flynn/go-shlex v0.0.0-20150515145356-3f9db97f8568/go.mod h1:xEzjJPgXI435gkrCt3MPfRiAkVrwSbHsst4LCFVfpJc= +github.com/gliderlabs/ssh v0.2.2 h1:6zsha5zo/TWhRhwqCD3+EarCAgZ2yN28ipRnGPnwkI0= +github.com/gliderlabs/ssh v0.2.2/go.mod h1:U7qILu1NlMHj9FlMhZLlkCdDnU1DBEAqr0aevW3Awn0= +github.com/go-git/gcfg v1.5.0 h1:Q5ViNfGF8zFgyJWPqYwA7qGFoMTEiBmdlkcfRmpIMa4= +github.com/go-git/gcfg v1.5.0/go.mod h1:5m20vg6GwYabIxaOonVkTdrILxQMpEShl1xiMF4ua+E= +github.com/go-git/go-billy/v5 v5.0.0 h1:7NQHvd9FVid8VL4qVUMm8XifBK+2xCoZ2lSk0agRrHM= +github.com/go-git/go-billy/v5 v5.0.0/go.mod h1:pmpqyWchKfYfrkb/UVH4otLvyi/5gJlGI4Hb3ZqZ3W0= +github.com/go-git/go-git-fixtures/v4 v4.0.2-0.20200613231340-f56387b50c12 h1:PbKy9zOy4aAKrJ5pibIRpVO2BXnK1Tlcg+caKI7Ox5M= +github.com/go-git/go-git-fixtures/v4 v4.0.2-0.20200613231340-f56387b50c12/go.mod h1:m+ICp2rF3jDhFgEZ/8yziagdT1C+ZpZcrJjappBCDSw= +github.com/go-git/go-git/v5 v5.2.0 h1:YPBLG/3UK1we1ohRkncLjaXWLW+HKp5QNM/jTli2JgI= +github.com/go-git/go-git/v5 v5.2.0/go.mod h1:kh02eMX+wdqqxgNMEyq8YgwlIOsDOa9homkUq1PoTMs= +github.com/go-playground/assert/v2 v2.0.1 h1:MsBgLAaY856+nPRTKrp3/OZK38U/wa0CcBYNjji3q3A= +github.com/go-playground/assert/v2 v2.0.1/go.mod h1:VDjEfimB/XKnb+ZQfWdccd7VUvScMdVu0Titje2rxJ4= +github.com/go-playground/locales v0.13.0 h1:HyWk6mgj5qFqCT5fjGBuRArbVDfE4hi8+e8ceBS/t7Q= +github.com/go-playground/locales v0.13.0/go.mod h1:taPMhCMXrRLJO55olJkUXHZBHCxTMfnGwq/HNwmWNS8= +github.com/go-playground/universal-translator v0.17.0 h1:icxd5fm+REJzpZx7ZfpaD876Lmtgy7VtROAbHHXk8no= +github.com/go-playground/universal-translator v0.17.0/go.mod h1:UkSxE5sNxxRwHyU+Scu5vgOQjsIJAF8j9muTVoKLVtA= +github.com/go-playground/validator/v10 v10.4.1 h1:pH2c5ADXtd66mxoE0Zm9SUhxE20r7aM3F26W0hOn+GE= +github.com/go-playground/validator/v10 v10.4.1/go.mod h1:nlOn6nFhuKACm19sB/8EGNn9GlaMV7XkbRSipzJ0Ii4= +github.com/golang/protobuf v1.3.2/go.mod h1:6lQm79b+lXiMfvg/cZm0SGofjICqVBUtrP5yJMmIC1U= +github.com/google/go-cmp v0.3.0 h1:crn/baboCvb5fXaQ0IJ1SGTsTVrWpDsCWC8EGETZijY= +github.com/google/go-cmp v0.3.0/go.mod h1:8QqcDgzrUqlUb/G2PQTWiueGozuR1884gddMywk6iLU= +github.com/google/go-github/v32 v32.1.0 h1:GWkQOdXqviCPx7Q7Fj+KyPoGm4SwHRh8rheoPhd27II= +github.com/google/go-github/v32 v32.1.0/go.mod h1:rIEpZD9CTDQwDK9GDrtMTycQNA4JU3qBsCizh3q2WCI= +github.com/google/go-querystring v1.0.0 h1:Xkwi/a1rcvNg1PPYe5vI8GbeBY/jrVuDX5ASuANWTrk= +github.com/google/go-querystring v1.0.0/go.mod h1:odCYkC5MyYFN7vkCjXpyrEuKhc/BUO6wN/zVPAxq5ck= +github.com/imdario/mergo v0.3.9/go.mod h1:2EnlNZ0deacrJVfApfmtdGgDfMuh/nq6Ok1EcJh5FfA= +github.com/imdario/mergo v0.3.11 h1:3tnifQM4i+fbajXKBHXWEH+KvNHqojZ778UH75j3bGA= +github.com/imdario/mergo v0.3.11/go.mod h1:jmQim1M+e3UYxmgPu/WyfjB3N3VflVyUjjjwH0dnCYA= +github.com/jbenet/go-context v0.0.0-20150711004518-d14ea06fba99 h1:BQSFePA1RWJOlocH6Fxy8MmwDt+yVQYULKfN0RoTN8A= +github.com/jbenet/go-context v0.0.0-20150711004518-d14ea06fba99/go.mod h1:1lJo3i6rXxKeerYnT8Nvf0QmHCRC1n8sfWVwXF2Frvo= +github.com/jessevdk/go-flags v1.4.0/go.mod h1:4FA24M0QyGHXBuZZK/XkWh8h0e1EYbRYJSGM75WSRxI= +github.com/kevinburke/ssh_config v0.0.0-20190725054713-01f96b0aa0cd h1:Coekwdh0v2wtGp9Gmz1Ze3eVRAWJMLokvN3QjdzCHLY= +github.com/kevinburke/ssh_config v0.0.0-20190725054713-01f96b0aa0cd/go.mod h1:CT57kijsi8u/K/BOFA39wgDQJ9CxiF4nAY/ojJ6r6mM= +github.com/kr/pretty v0.1.0/go.mod h1:dAy3ld7l9f0ibDNOQOHHMYYIIbhfbHSm3C4ZsoJORNo= +github.com/kr/pty v1.1.1/go.mod h1:pFQYn66WHrOpPYNljwOMqo10TkYh1fy3cYio2l3bCsQ= +github.com/kr/text v0.1.0/go.mod h1:4Jbv+DJW3UT/LiOwJeYQe1efqtUx/iVham/4vfdArNI= +github.com/kr/text v0.2.0 h1:5Nx0Ya0ZqY2ygV366QzturHI13Jq95ApcVaJBhpS+AY= +github.com/kr/text v0.2.0/go.mod h1:eLer722TekiGuMkidMxC/pM04lWEeraHUUmBw8l2grE= +github.com/leodido/go-urn v1.2.0/go.mod h1:+8+nEpDfqqsY+g338gtMEUOtuK+4dEMhiQEgxpxOKII= +github.com/leodido/go-urn v1.2.1 h1:BqpAaACuzVSgi/VLzGZIobT2z4v53pjosyNd9Yv6n/w= +github.com/leodido/go-urn v1.2.1/go.mod h1:zt4jvISO2HfUBqxjfIshjdMTYS56ZS/qv49ictyFfxY= +github.com/mitchellh/go-homedir v1.1.0 h1:lukF9ziXFxDFPkA1vsr5zpc1XuPDn/wFntq5mG+4E0Y= +github.com/mitchellh/go-homedir v1.1.0/go.mod h1:SfyaCUpYCn1Vlf4IUYiD9fPX4A5wJrkLzIz1N1q0pr0= +github.com/niemeyer/pretty v0.0.0-20200227124842-a10e7caefd8e h1:fD57ERR4JtEqsWbfPhv4DMiApHyliiK5xCTNVSPiaAs= +github.com/niemeyer/pretty v0.0.0-20200227124842-a10e7caefd8e/go.mod h1:zD1mROLANZcx1PVRCS0qkT7pwLkGfwJo4zjcN/Tysno= +github.com/pkg/errors v0.8.1/go.mod h1:bwawxfHBFNV+L2hUp1rHADufV3IMtnDRdf1r5NINEl0= +github.com/pkg/errors v0.9.1 h1:FEBLx1zS214owpjy7qsBeixbURkuhQAwrK5UwLGTwt4= +github.com/pkg/errors v0.9.1/go.mod h1:bwawxfHBFNV+L2hUp1rHADufV3IMtnDRdf1r5NINEl0= +github.com/pmezard/go-difflib v1.0.0 h1:4DBwDE0NGyQoBHbLQYPwSUPoCMWR5BEzIk/f1lZbAQM= +github.com/pmezard/go-difflib v1.0.0/go.mod h1:iKH77koFhYxTK1pcRnkKkqfTogsbg7gZNVY4sRDYZ/4= +github.com/sergi/go-diff v1.1.0 h1:we8PVUC3FE2uYfodKH/nBHMSetSfHDR6scGdBi+erh0= +github.com/sergi/go-diff v1.1.0/go.mod h1:STckp+ISIX8hZLjrqAeVduY0gWCT9IjLuqbuNXdaHfM= +github.com/stretchr/objx v0.1.0/go.mod h1:HFkY916IF+rwdDfMAkV7OtwuqBVzrE8GR6GFx+wExME= +github.com/stretchr/testify v1.4.0/go.mod h1:j7eGeouHqKxXV5pUuKE4zz7dFj8WfuZ+81PSLYec5m4= +github.com/stretchr/testify v1.6.1/go.mod h1:6Fq8oRcR53rry900zMqJjRRixrwX3KX962/h/Wwjteg= +github.com/stretchr/testify v1.7.0 h1:nwc3DEeHmmLAfoZucVR881uASk0Mfjw8xYJ99tb5CcY= +github.com/xanzy/ssh-agent v0.2.1 h1:TCbipTQL2JiiCprBWx9frJ2eJlCYT00NmctrHxVAr70= +github.com/xanzy/ssh-agent v0.2.1/go.mod h1:mLlQY/MoOhWBj+gOGMQkOeiEvkx+8pJSI+0Bx9h2kr4= +golang.org/x/crypto v0.0.0-20190219172222-a4c6cb3142f2/go.mod h1:6SG95UA2DQfeDnfUPMdvaQW0Q7yPrPDi9nlGo2tz2b4= +golang.org/x/crypto v0.0.0-20190308221718-c2843e01d9a2/go.mod h1:djNgcEr1/C05ACkg1iLfiJU5Ep61QUkGW8qpdssI0+w= +golang.org/x/crypto v0.0.0-20200302210943-78000ba7a073/go.mod h1:LzIPMQfyMNhhGPhUkYOs5KpL4U8rLKemX1yGLhDgUto= +golang.org/x/crypto v0.0.0-20200622213623-75b288015ac9/go.mod h1:LzIPMQfyMNhhGPhUkYOs5KpL4U8rLKemX1yGLhDgUto= +golang.org/x/crypto v0.0.0-20201002170205-7f63de1d35b0 h1:hb9wdF1z5waM+dSIICn1l0DkLVDT3hqhhQsDNUmHPRE= +golang.org/x/crypto v0.0.0-20201002170205-7f63de1d35b0/go.mod h1:LzIPMQfyMNhhGPhUkYOs5KpL4U8rLKemX1yGLhDgUto= +golang.org/x/net v0.0.0-20190311183353-d8887717615a/go.mod h1:t9HGtf8HONx5eT2rtn7q6eTqICYqUVnKs3thJo3Qplg= +golang.org/x/net v0.0.0-20190404232315-eb5bcb51f2a3/go.mod h1:t9HGtf8HONx5eT2rtn7q6eTqICYqUVnKs3thJo3Qplg= +golang.org/x/net v0.0.0-20200301022130-244492dfa37a/go.mod h1:z5CRVTTTmAJ677TzLLGU+0bjPO0LkuOLi4/5GtJWs/s= +golang.org/x/net v0.0.0-20201224014010-6772e930b67b h1:iFwSg7t5GZmB/Q5TjiEAsdoLDrdJRC1RiF2WhuV29Qw= +golang.org/x/net v0.0.0-20201224014010-6772e930b67b/go.mod h1:m0MpNAwzfU5UDzcl9v0D8zg8gWTRqZa9RBIspLL5mdg= +golang.org/x/oauth2 v0.0.0-20180821212333-d2e6202438be/go.mod h1:N/0e6XlmueqKjAGxoOufVs8QHGRruUQn6yWY3a++T0U= +golang.org/x/sys v0.0.0-20190215142949-d0b11bdaac8a/go.mod h1:STP8DvDyc/dI5b8T5hshtkjS+E42TnysNCUPdjciGhY= +golang.org/x/sys v0.0.0-20190221075227-b4e8571b14e0/go.mod h1:STP8DvDyc/dI5b8T5hshtkjS+E42TnysNCUPdjciGhY= +golang.org/x/sys v0.0.0-20190412213103-97732733099d/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs= +golang.org/x/sys v0.0.0-20200302150141-5c8b2ff67527/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs= +golang.org/x/sys v0.0.0-20201119102817-f84b799fce68/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs= +golang.org/x/sys v0.0.0-20210112080510-489259a85091 h1:DMyOG0U+gKfu8JZzg2UQe9MeaC1X+xQWlAKcRnjxjCw= +golang.org/x/sys v0.0.0-20210112080510-489259a85091/go.mod h1:h1NjWce9XRLGQEsW7wpKNCjG9DtNlClVuFLEZdDNbEs= +golang.org/x/term v0.0.0-20201126162022-7de9c90e9dd1/go.mod h1:bj7SfCRtBDWHUb9snDiAeCFNEtKQo2Wmx5Cou7ajbmo= +golang.org/x/text v0.3.0/go.mod h1:NqM8EUOU14njkJ3fqMW+pc6Ldnwhi/IjpwHt7yyuwOQ= +golang.org/x/text v0.3.2/go.mod h1:bEr9sfX3Q8Zfm5fL9x+3itogRgK3+ptLWKqgva+5dAk= +golang.org/x/text v0.3.3 h1:cokOdA+Jmi5PJGXLlLllQSgYigAEfHXJAERHVMaCc2k= +golang.org/x/text v0.3.3/go.mod h1:5Zoc/QRtKVWzQhOtBMvqHzDpF6irO9z98xDceosuGiQ= +golang.org/x/tools v0.0.0-20180917221912-90fa682c2a6e/go.mod h1:n7NCudcB/nEzxVGmLbDWY5pfWTLqBcC2KZ6jyYvM4mQ= +google.golang.org/appengine v1.1.0/go.mod h1:EbEs0AVv82hx2wNQdGPgUI5lhzA/G0D9YwlJXL52JkM= gopkg.in/check.v1 v0.0.0-20161208181325-20d25e280405/go.mod h1:Co6ibVJAznAaIkqp8huTwlJQCZ016jof/cbN4VW5Yz0= -gopkg.in/yaml.v3 v3.0.0-20190409140830-cdc409dda467 h1:w3VhdSYz2sIVz54Ta/eDCCfCQ4fQkDgRxMACggArIUw= -gopkg.in/yaml.v3 v3.0.0-20190409140830-cdc409dda467/go.mod h1:K4uyk7z7BCEPqu6E+C64Yfv1cQ7kz7rIZviUmN+EgEM= +gopkg.in/check.v1 v1.0.0-20190902080502-41f04d3bba15/go.mod h1:Co6ibVJAznAaIkqp8huTwlJQCZ016jof/cbN4VW5Yz0= +gopkg.in/check.v1 v1.0.0-20200227125254-8fa46927fb4f h1:BLraFXnmrev5lT+xlilqcH8XK9/i0At2xKjWk4p6zsU= +gopkg.in/check.v1 v1.0.0-20200227125254-8fa46927fb4f/go.mod h1:Co6ibVJAznAaIkqp8huTwlJQCZ016jof/cbN4VW5Yz0= +gopkg.in/warnings.v0 v0.1.2 h1:wFXVbFY8DY5/xOe1ECiWdKCzZlxgshcYVNkBHstARME= +gopkg.in/warnings.v0 v0.1.2/go.mod h1:jksf8JmL6Qr/oQM2OXTHunEvvTAsrWBLb6OOjuVWRNI= +gopkg.in/yaml.v2 v2.2.2/go.mod h1:hI93XBmqTisBFMUTm0b8Fm+jr3Dg1NNxqwp+5A1VGuI= +gopkg.in/yaml.v2 v2.2.4/go.mod h1:hI93XBmqTisBFMUTm0b8Fm+jr3Dg1NNxqwp+5A1VGuI= +gopkg.in/yaml.v2 v2.3.0/go.mod h1:hI93XBmqTisBFMUTm0b8Fm+jr3Dg1NNxqwp+5A1VGuI= +gopkg.in/yaml.v2 v2.4.0 h1:D8xgwECY7CYvx+Y2n4sBz93Jn9JRvxdiyyo8CTfuKaY= +gopkg.in/yaml.v3 v3.0.0-20200313102051-9f266ea9e77c h1:dUUwHk2QECo/6vqA44rthZ8ie2QXMNeKRTHCNY2nXvo= +gopkg.in/yaml.v3 v3.0.0-20200313102051-9f266ea9e77c/go.mod h1:K4uyk7z7BCEPqu6E+C64Yfv1cQ7kz7rIZviUmN+EgEM= +k8s.io/enhancements v0.0.0-20230113204613-7f681415a001 h1:WIc9tKwNWdlFwmEMzK8rX5DVpxmKQPo8LA0yyKroxxs= +k8s.io/enhancements v0.0.0-20230113204613-7f681415a001/go.mod h1:VTK7nLkF9+GUWaHX08TT7CYf8tZSY8rChiH8GFwPYy8= diff --git a/governance.md b/governance.md index 2d889c1d..903abafc 100644 --- a/governance.md +++ b/governance.md @@ -160,16 +160,15 @@ See [user group governance] for more details about forming and disbanding User Groups. To facilitate discoverability and engagement, -user groups are documented in [sigs.yaml] +user groups are documented in [sigs.yaml]. ## Community Group Annual Reports As you can see in the descriptions above, the project is robust with diverse groups of contributors and their varying degrees of expected communications. -The annual community group health check will establish an opportunity for deeper +The [annual community group health check] will establish an opportunity for deeper dialogue and broader communication across the chairs of each group and the - Steering Committee. By including this reporting with the existing community - meeting structure, we can focus on the goals outlined in the [Annual Report] doc. + Steering Committee. ## Cross-project Communication and Coordination @@ -223,6 +222,5 @@ All contributors must sign the CNCF CLA, as described [here](CLA.md). [working group governance]: /committee-steering/governance/wg-governance.md [user group governance]: /committee-steering/governance/ug-governance.md [SIG Governance Requirements]: /committee-steering/governance/sig-governance-requirements.md -[Annual Report]: /committee-steering/governance/annual-reports.md -[monthly community meeting]: /events/community-meeting.md +[annual community group health check]: /committee-steering/governance/annual-reports.md [KEP process]: https://github.com/kubernetes/enhancements/tree/master/keps#kubernetes-enhancement-proposals-keps diff --git a/hack/generate-devstats-repo-sql.py b/hack/generate-devstats-repo-sql.py index 71d77497..c86c26f0 100755 --- a/hack/generate-devstats-repo-sql.py +++ b/hack/generate-devstats-repo-sql.py @@ -15,7 +15,7 @@ # limitations under the License. """ -Output devstats repo_groups.sql based on subproject defintions in sigs.yaml +Output devstats repo_groups.sql based on subproject definitions in sigs.yaml This is likely missing a few repos because: - some repos lack an owner (eg: kubernetes/kubernetes) diff --git a/liaisons.md b/liaisons.md index c50a88e8..f621a9b2 100644 --- a/liaisons.md +++ b/liaisons.md @@ -30,38 +30,37 @@ members will assume one of the departing members groups. | Community Group | Steering Committee Liaison | | -------------------------- | -------------------------- | -| [SIG API Machinery](sig-api-machinery/README.md) | Davanum Srinivas (**[@dims](https://github.com/dims)**) | +| [SIG API Machinery](sig-api-machinery/README.md) | Nabarun Pal (**[@palnabarun](https://github.com/palnabarun)**) | | [SIG Apps](sig-apps/README.md) | Bob Killen (**[@mrbobbytables](https://github.com/mrbobbytables)**) | -| [SIG Architecture](sig-architecture/README.md) | Jordan Liggitt (**[@liggitt](https://github.com/liggitt)**) | +| [SIG Architecture](sig-architecture/README.md) | Benjamin Elder (**[@BenTheElder](https://github.com/BenTheElder)**) | | [SIG Auth](sig-auth/README.md) | Christoph Blecker (**[@cblecker](https://github.com/cblecker)**) | | [SIG Autoscaling](sig-autoscaling/README.md) | Tim Pepper (**[@tpepper](https://github.com/tpepper)**) | | [SIG CLI](sig-cli/README.md) | Stephen Augustus (**[@justaugustus](https://github.com/justaugustus)**) | | [SIG Cloud Provider](sig-cloud-provider/README.md) | Stephen Augustus (**[@justaugustus](https://github.com/justaugustus)**) | -| [SIG Cluster Lifecycle](sig-cluster-lifecycle/README.md) | Davanum Srinivas (**[@dims](https://github.com/dims)**) | +| [SIG Cluster Lifecycle](sig-cluster-lifecycle/README.md) | Nabarun Pal (**[@palnabarun](https://github.com/palnabarun)**) | | [SIG Contributor Experience](sig-contributor-experience/README.md) | Bob Killen (**[@mrbobbytables](https://github.com/mrbobbytables)**) | -| [SIG Docs](sig-docs/README.md) | Paris Pittman (**[@parispittman](https://github.com/parispittman)**) | +| [SIG Docs](sig-docs/README.md) | Carlos Tadeu Panato Jr. (**[@cpanato](https://github.com/cpanato)**) | | [SIG Instrumentation](sig-instrumentation/README.md) | Christoph Blecker (**[@cblecker](https://github.com/cblecker)**) | | [SIG K8s Infra](sig-k8s-infra/README.md) | Stephen Augustus (**[@justaugustus](https://github.com/justaugustus)**) | | [SIG Multicluster](sig-multicluster/README.md) | Bob Killen (**[@mrbobbytables](https://github.com/mrbobbytables)**) | | [SIG Network](sig-network/README.md) | Tim Pepper (**[@tpepper](https://github.com/tpepper)**) | | [SIG Node](sig-node/README.md) | Tim Pepper (**[@tpepper](https://github.com/tpepper)**) | -| [SIG Release](sig-release/README.md) | Davanum Srinivas (**[@dims](https://github.com/dims)**) | +| [SIG Release](sig-release/README.md) | Nabarun Pal (**[@palnabarun](https://github.com/palnabarun)**) | | [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 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 Scheduling](sig-scheduling/README.md) | Benjamin Elder (**[@BenTheElder](https://github.com/BenTheElder)**) | +| [SIG Security](sig-security/README.md) | Carlos Tadeu Panato Jr. (**[@cpanato](https://github.com/cpanato)**) | +| [SIG Storage](sig-storage/README.md) | Carlos Tadeu Panato Jr. (**[@cpanato](https://github.com/cpanato)**) | +| [SIG Testing](sig-testing/README.md) | Carlos Tadeu Panato Jr. (**[@cpanato](https://github.com/cpanato)**) | | [SIG UI](sig-ui/README.md) | Stephen Augustus (**[@justaugustus](https://github.com/justaugustus)**) | -| [SIG Usability](sig-usability/README.md) | Davanum Srinivas (**[@dims](https://github.com/dims)**) | -| [SIG Windows](sig-windows/README.md) | Jordan Liggitt (**[@liggitt](https://github.com/liggitt)**) | -| [WG API Expression](wg-api-expression/README.md) | Jordan Liggitt (**[@liggitt](https://github.com/liggitt)**) | +| [SIG Usability](sig-usability/README.md) | Nabarun Pal (**[@palnabarun](https://github.com/palnabarun)**) | +| [SIG Windows](sig-windows/README.md) | Benjamin Elder (**[@BenTheElder](https://github.com/BenTheElder)**) | +| [WG API Expression](wg-api-expression/README.md) | Benjamin Elder (**[@BenTheElder](https://github.com/BenTheElder)**) | | [WG Batch](wg-batch/README.md) | Bob Killen (**[@mrbobbytables](https://github.com/mrbobbytables)**) | | [WG Data Protection](wg-data-protection/README.md) | Christoph Blecker (**[@cblecker](https://github.com/cblecker)**) | | [WG IoT Edge](wg-iot-edge/README.md) | Christoph Blecker (**[@cblecker](https://github.com/cblecker)**) | -| [WG Multitenancy](wg-multitenancy/README.md) | Jordan Liggitt (**[@liggitt](https://github.com/liggitt)**) | +| [WG Multitenancy](wg-multitenancy/README.md) | Benjamin Elder (**[@BenTheElder](https://github.com/BenTheElder)**) | | [WG Policy](wg-policy/README.md) | Christoph Blecker (**[@cblecker](https://github.com/cblecker)**) | -| [WG Structured Logging](wg-structured-logging/README.md) | Davanum Srinivas (**[@dims](https://github.com/dims)**) | -| [UG Big Data](ug-big-data/README.md) | Tim Pepper (**[@tpepper](https://github.com/tpepper)**) | +| [WG Structured Logging](wg-structured-logging/README.md) | Nabarun Pal (**[@palnabarun](https://github.com/palnabarun)**) | | [UG VMware Users](ug-vmware-users/README.md) | Tim Pepper (**[@tpepper](https://github.com/tpepper)**) | | [Committee Code of Conduct](committee-code-of-conduct/README.md) | Tim Pepper (**[@tpepper](https://github.com/tpepper)**) | | [Committee Security Response](committee-security-response/README.md) | Stephen Augustus (**[@justaugustus](https://github.com/justaugustus)**) | diff --git a/mentoring/OWNERS b/mentoring/OWNERS index bb13fa55..570487ed 100644 --- a/mentoring/OWNERS +++ b/mentoring/OWNERS @@ -1,11 +1,11 @@ # See the OWNERS docs at https://go.k8s.io/owners approvers: - - parispittman - nikhita - sig-contributor-experience-leads emeritus_approvers: - markyjackson-taulia # for community-bridge and meeting bosun + - parispittman # processes and programs and logos labels: - sig/contributor-experience - area/mentorship-planning diff --git a/mentoring/README.md b/mentoring/README.md index 7d186f59..6e4a5a34 100644 --- a/mentoring/README.md +++ b/mentoring/README.md @@ -24,10 +24,6 @@ SIG's office hours / mentoring - [Office hours / mentoring](/mentoring/programs/office-hours.md) -Mentors On Demand - -- [Meet Our Contributors](/mentoring/programs/meet-our-contributors.md) - Long Term Contributor Ladder Growth - Through [Group Mentoring Cohorts](/mentoring/programs/group-mentoring.md) diff --git a/mentoring/processes/group-mentoring.md b/mentoring/processes/group-mentoring.md index a3fc7fe7..ef34836d 100644 --- a/mentoring/processes/group-mentoring.md +++ b/mentoring/processes/group-mentoring.md @@ -22,10 +22,11 @@ suggestions: *Reviewer* - Enhancements -- Overview of Release Cycle +- Overview of Release Cycle +- Overview of SIGs subprojects - Development - Triage - - Reviews + - Reviews - detailed walk thrus - API Changes - Testing - Code Freeze @@ -54,24 +55,32 @@ Examples: 0. Need is established and SIG provides a mentor* 1. ContribEx kicks off two issues, sets a target start and end date, and selects a coordinator - - issue #1: outreach issue to collect folks who are interested, issue will - close when there are the max participants needed - - issue #2 setting up infra - template here: [TODO link to example] -2. ContribEx or SIG member posts the issue to the following places: - - SIG and k-dev mailing lists + - issue #1: outreach issue to collect folks who are interested and set up + infra, issue will close when there are the max participants needed + example: https://github.com/kubernetes/community/issues/5962 + key bits of info: target, start/end date, sign up and requirements, slack info, + mentors, coordinators + - issue #2: structure of sessions and assign guest speakers + start with a hackmd to coordinate with mentors and then set issue +1. ContribEx Coordinator(s) posts issue #1 to the following places: + - SIG list first and then k-dev mailing lists with timeboxes for responses - #diversity, #kubernetes-contributors, #sig-[name], and other slack channels -3. Coordinator arranges a doodle for the kick off meeting and days/times that -would be best for the mentor and group for slack standups and touch points. Once conscensus is reached, coordinator schedules it. -4. Mentor creates template that serves as a reference guide for the group. See +3. Slack stand ups happen on the day of the SIG meetings but the 30-min +bi-weekly meetings will need to be arranged. Coorindator should send out a +doodle to the selected group with a few times that work for the mentors. +4. Coorindator and mentors work together on the three-month plan template. +Coordinator will schedule the speakers and create a calendar for the group. +example here: https://hackmd.io/1aAIaMChR8Gfi31aOKBHlA +5. Mentor creates template that serves as a reference guide for the group. See a sig-node example here: https://hackmd.io/8i8prErgSOamUmEZDDZPWA -5. Program begins at the kick off meeting +6. Program begins at the kick off meeting - [TODO add kick off template] -6. Feedback is continuous as you stand up weekly; however, the ContribEx +7. Feedback is continuous as you stand up weekly; however, the ContribEx Coorindator will set a mid program check-in. In this check-in, members of the group will start their application process for their roles and any group members who have not had the time. - [TODO add community membership template] -7. By this point, folks should know where they stand. At the end of the program, +8. By this point, folks should know where they stand. At the end of the program, mentors and/or individuals will start the PR process in OWNERS files or sigs.yaml for leadership roles for those who are ready diff --git a/mentoring/processes/mentor-guide.md b/mentoring/processes/mentor-guide.md index 32b595c3..3a0d61bc 100644 --- a/mentoring/processes/mentor-guide.md +++ b/mentoring/processes/mentor-guide.md @@ -89,11 +89,6 @@ CNCF will financially support one Outreachy intern for Kubernetes per semester; A former GSoC intern for Kubernetes is now leading this for us - mentoring works! Thanks @nikhita! -*[Meet Our Contributors - Mentors On Demand](meet-our-contributors.md)* -* One hour a month on a streaming YouTube show answering questions about the contribution process, your experience in open source, and other questions that people would normally ask to a mentor. -* Typically a one hour a quarter time commitment is expected; this is an opt-in sign up. -* You will need to be on the call 5 minutes early to test audio quality and make sure we are good to go for streaming. - *[Pod Mentoring](mentoring-events.md)* * Short group sessions with other mentors during KubeCon/CloudNativeCon events answering mentee questions * Designed to eliminate the awkwardness of 1:1s and ensure a wider breadth of knowledge to reduce pressure of having to provide an answer diff --git a/mentoring/programs/group-mentee-guide.md b/mentoring/programs/group-mentee-guide.md index 36320904..01d49074 100644 --- a/mentoring/programs/group-mentee-guide.md +++ b/mentoring/programs/group-mentee-guide.md @@ -67,9 +67,6 @@ TODO: add more here - mailing lists - dev@kubernetes.io - your respective sig (ie - kubernetes-sig-cli@googlegroups.com) -- contributor office hours - - Kubernetes Community Office Hours - - #office-hours on slack - the docs - kubernetes/community is your friend for upstream workflows, processes, and information around contributing diff --git a/mentoring/programs/meet-our-contributors.md b/mentoring/programs/meet-our-contributors.md index fca04632..d5006706 100644 --- a/mentoring/programs/meet-our-contributors.md +++ b/mentoring/programs/meet-our-contributors.md @@ -7,6 +7,8 @@ description: | participate in peer code reviews. --- +# Program is on hiatus and may be brought back at a future date + # Meet Our Contributors - Ask Us Anything! When Slack seems like it’s going too fast, and you just need a quick answer from diff --git a/sig-api-machinery/README.md b/sig-api-machinery/README.md index e8daa788..32869331 100644 --- a/sig-api-machinery/README.md +++ b/sig-api-machinery/README.md @@ -14,7 +14,7 @@ The [charter](charter.md) defines the scope and governance of the API Machinery ## Meetings *Joining the [mailing list](https://groups.google.com/forum/#!forum/kubernetes-sig-api-machinery) for the group will typically add invites for the following meetings to your calendar.* -* Kubebuilder and Controller Runtime Meeting: [Thursdays at 09:00 PT (Pacific Time)]() (biweekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=09:00&tz=PT%20%28Pacific%20Time%29). +* Kubebuilder and Controller Runtime Meeting: [Thursdays at 11:00 PT (Pacific Time)]() (biweekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=11:00&tz=PT%20%28Pacific%20Time%29). * [Meeting notes and Agenda](https://docs.google.com/document/d/1Ih-2cgg1bUrLwLVTB9tADlPcVdgnuMNBGbUl4D-0TIk/edit?usp=sharing). * Regular SIG Meeting: [Wednesdays at 11:00 PT (Pacific Time)](https://zoom.us/my/apimachinery) (biweekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=11:00&tz=PT%20%28Pacific%20Time%29). * [Meeting notes and Agenda](https://goo.gl/0lbiM9). @@ -47,7 +47,7 @@ subprojects, and resolve cross-subproject technical issues and decisions. - [@kubernetes/sig-api-machinery-pr-reviews](https://github.com/orgs/kubernetes/teams/sig-api-machinery-pr-reviews) - PR Reviews - [@kubernetes/sig-api-machinery-proposals](https://github.com/orgs/kubernetes/teams/sig-api-machinery-proposals) - Design Proposals - [@kubernetes/sig-api-machinery-test-failures](https://github.com/orgs/kubernetes/teams/sig-api-machinery-test-failures) - Test Failures and Triage -- Steering Committee Liaison: Davanum Srinivas (**[@dims](https://github.com/dims)**) +- Steering Committee Liaison: Nabarun Pal (**[@palnabarun](https://github.com/palnabarun)**) ## Working Groups diff --git a/sig-architecture/Kubernetes_PRR_Survey_2020Q1.pdf b/sig-architecture/Kubernetes_PRR_Survey_2020Q1.pdf Binary files differnew file mode 100644 index 00000000..2fb9e4ea --- /dev/null +++ b/sig-architecture/Kubernetes_PRR_Survey_2020Q1.pdf diff --git a/sig-architecture/Kubernetes_PRR_Survey_2021Q2.pdf b/sig-architecture/Kubernetes_PRR_Survey_2021Q2.pdf Binary files differnew file mode 100644 index 00000000..087bfd94 --- /dev/null +++ b/sig-architecture/Kubernetes_PRR_Survey_2021Q2.pdf diff --git a/sig-architecture/Kubernetes_PRR_Survey_2022Q2.pdf b/sig-architecture/Kubernetes_PRR_Survey_2022Q2.pdf Binary files differnew file mode 100644 index 00000000..b106c037 --- /dev/null +++ b/sig-architecture/Kubernetes_PRR_Survey_2022Q2.pdf diff --git a/sig-architecture/README.md b/sig-architecture/README.md index bd0ae7ab..4d2a76fa 100644 --- a/sig-architecture/README.md +++ b/sig-architecture/README.md @@ -36,7 +36,7 @@ The [charter](charter.md) defines the scope and governance of the Architecture S The Chairs of the SIG run operations and processes governing the SIG. * Derek Carr (**[@derekwaynecarr](https://github.com/derekwaynecarr)**), Red Hat -* Davanum Srinivas (**[@dims](https://github.com/dims)**), VMware +* Davanum Srinivas (**[@dims](https://github.com/dims)**), Amazon Web Services * John Belamaric (**[@johnbelamaric](https://github.com/johnbelamaric)**), Google ## Contact @@ -51,7 +51,7 @@ The Chairs of the SIG run operations and processes governing the SIG. - [@kubernetes/sig-architecture-pr-reviews](https://github.com/orgs/kubernetes/teams/sig-architecture-pr-reviews) - PR Reviews - [@kubernetes/sig-architecture-proposals](https://github.com/orgs/kubernetes/teams/sig-architecture-proposals) - Design Proposals - [@kubernetes/sig-architecture-test-failures](https://github.com/orgs/kubernetes/teams/sig-architecture-test-failures) - Test Failures and Triage -- Steering Committee Liaison: Jordan Liggitt (**[@liggitt](https://github.com/liggitt)**) +- Steering Committee Liaison: Benjamin Elder (**[@BenTheElder](https://github.com/BenTheElder)**) ## Working Groups diff --git a/sig-architecture/generics.md b/sig-architecture/generics.md index 059a65f2..f468bab2 100644 --- a/sig-architecture/generics.md +++ b/sig-architecture/generics.md @@ -1,9 +1,9 @@ # Background -In general, Kubernetes has not restricted using new Go features, we've quickly +In general, Kubernetes has not restricted using new Go features. We've quickly adopted new standard library types and methods and will continue to do so. -Generally the latest stable go release is in use on the main development branch. +Generally the latest stable Go release is in use on the main development branch. This includes all of the staging libraries (client-go etc.) that originate in the main [kubernetes/kubernetes](https://github.com/kubernetes/kubernetes) repository. @@ -14,19 +14,21 @@ Now that v1.24.0 is out, use of generics should be allowed. # Generics Policy -Generics may be used in Kubernetes starting in v1.25, with the following restrictions -applying only until v1.24 is [out of support][version-support]: +Generics may be used in Kubernetes starting in v1.24, with the following restrictions +applying only until v1.23 is [out of support][version-support]: - Generics should **not** be used in Kubernetes libraries used across multiple Kubernetes -versions, that is the non "staged" libraries like: + versions, that is the non "staged" libraries like: - [k8s.io/utils](https://github.com/kubernetes/utils) - [sigs.k8s.io/yaml](https://github.com/kubernetes-sigs/yaml) - [k8s.io/klog](https://github.com/kubernetes/klog) - etc. -- Generics should be **avoided** when writing Kubernetes bug fixes that are likely to be backported, to streamline cherry-picking to older release branches. +- Generics should be **avoided** when writing Kubernetes bug fixes that are + likely to be backported to v1.23 or older, to streamline cherry-picking to + those release branches which predate Go 1.18. -These restrictions should be considered lifted when v1.24 is out of support. +These restrictions should be considered lifted when v1.23 is out of support. ## Recommendations for Reviewers diff --git a/sig-auth/README.md b/sig-auth/README.md index 4082719d..6946e1ab 100644 --- a/sig-auth/README.md +++ b/sig-auth/README.md @@ -168,6 +168,10 @@ Infrastructure implementing Kubernetes service account based workload identity. - [kubernetes/kubernetes/pkg/kubelet/token](https://github.com/kubernetes/kubernetes/blob/master/pkg/kubelet/token/OWNERS) - [kubernetes/kubernetes/pkg/serviceaccount](https://github.com/kubernetes/kubernetes/blob/master/pkg/serviceaccount/OWNERS) - [kubernetes/kubernetes/plugin/pkg/admission/serviceaccount](https://github.com/kubernetes/kubernetes/blob/master/plugin/pkg/admission/serviceaccount/OWNERS) +### sig-auth-tools +Tooling to automate the SIG Auth project boards +- **Owners:** + - [kubernetes-sigs/sig-auth-tools](https://github.com/kubernetes-sigs/sig-auth-tools/blob/main/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-cli/README.md b/sig-cli/README.md index 57ba5b85..82ece69f 100644 --- a/sig-cli/README.md +++ b/sig-cli/README.md @@ -14,13 +14,13 @@ The [charter](charter.md) defines the scope and governance of the CLI Special In ## Meetings *Joining the [mailing list](https://groups.google.com/forum/#!forum/kubernetes-sig-cli) for the group will typically add invites for the following meetings to your calendar.* -* Bug Scrub: [Wednesdays at 09:00 PT (Pacific Time)](https://zoom.us/j/288426795?pwd=UDdoYnFyNjBiS1RHcXRxS1BCNy9wUT09) (monthly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=09:00&tz=PT%20%28Pacific%20Time%29). +* Bug Scrub: [Wednesdays at 09:00 PT (Pacific Time)](https://zoom.us/j/288426795?pwd=UDdoYnFyNjBiS1RHcXRxS1BCNy9wUT09) (every four weeks). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=09:00&tz=PT%20%28Pacific%20Time%29). * [Meeting notes and Agenda](https://docs.google.com/document/d/1r0YElcXt6G5mOWxwZiXgGu_X6he3F--wKwg-9UBc29I/edit?usp=sharing). * [Meeting recordings](https://www.youtube.com/playlist?list=PL69nYSiGNLP28HaTzSlFe6RJVxpFmbUvF). * KRM Functions Subproject Meeting: [Wednesdays at 10:30 PT (Pacific Time)](https://zoom.us/j/288426795?pwd=UDdoYnFyNjBiS1RHcXRxS1BCNy9wUT09) (biweekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=10:30&tz=PT%20%28Pacific%20Time%29). * [Meeting notes and Agenda](https://docs.google.com/document/d/1x80l4i88F27zSCxSjlhvwFdH6jQAHou1k1ibuXrDTaw/edit). * [Meeting recordings](https://www.youtube.com/playlist?list=PL69nYSiGNLP28HaTzSlFe6RJVxpFmbUvF). -* Kustomize Bug Scrub: [Wednesdays at 09:00 PT (Pacific Time)](https://zoom.us/j/288426795?pwd=UDdoYnFyNjBiS1RHcXRxS1BCNy9wUT09) (monthly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=09:00&tz=PT%20%28Pacific%20Time%29). +* Kustomize Bug Scrub: [Wednesdays at 09:00 PT (Pacific Time)](https://zoom.us/j/288426795?pwd=UDdoYnFyNjBiS1RHcXRxS1BCNy9wUT09) (every four weeks). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=09:00&tz=PT%20%28Pacific%20Time%29). * [Meeting notes and Agenda](https://docs.google.com/document/d/1r0YElcXt6G5mOWxwZiXgGu_X6he3F--wKwg-9UBc29I/edit?usp=sharing). * [Meeting recordings](https://www.youtube.com/playlist?list=PL69nYSiGNLP28HaTzSlFe6RJVxpFmbUvF). * Regular SIG Meeting: [Wednesdays at 09:00 PT (Pacific Time)](https://zoom.us/j/288426795?pwd=UDdoYnFyNjBiS1RHcXRxS1BCNy9wUT09) (biweekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=09:00&tz=PT%20%28Pacific%20Time%29). diff --git a/sig-cloud-provider/README.md b/sig-cloud-provider/README.md index 528c58e4..a7faeca1 100644 --- a/sig-cloud-provider/README.md +++ b/sig-cloud-provider/README.md @@ -88,12 +88,13 @@ The following [subprojects][subproject-definition] are owned by sig-cloud-provid - [Meeting recordings](https://www.youtube.com/playlist?list=PLWpmsLfcyyD7HAhlLTuwmI9KWuoiaN9nO). ### provider-aws - **Owners:** - - [kubernetes-sigs/aws-alb-ingress-controller](https://github.com/kubernetes-sigs/aws-alb-ingress-controller/blob/master/OWNERS) - [kubernetes-sigs/aws-ebs-csi-driver](https://github.com/kubernetes-sigs/aws-ebs-csi-driver/blob/master/OWNERS) - [kubernetes-sigs/aws-efs-csi-driver](https://github.com/kubernetes-sigs/aws-efs-csi-driver/blob/master/OWNERS) - [kubernetes-sigs/aws-encryption-provider](https://github.com/kubernetes-sigs/aws-encryption-provider/blob/master/OWNERS) + - [kubernetes-sigs/aws-file-cache-csi-driver](https://github.com/kubernetes-sigs/aws-file-cache-csi-driver/blob/main/OWNERS) - [kubernetes-sigs/aws-fsx-csi-driver](https://github.com/kubernetes-sigs/aws-fsx-csi-driver/blob/master/OWNERS) - [kubernetes-sigs/aws-iam-authenticator](https://github.com/kubernetes-sigs/aws-iam-authenticator/blob/master/OWNERS) + - [kubernetes-sigs/aws-load-balancer-controller](https://github.com/kubernetes-sigs/aws-load-balancer-controller/blob/main/OWNERS) - [kubernetes-sigs/provider-aws-test-infra](https://github.com/kubernetes-sigs/provider-aws-test-infra/blob/master/OWNERS) - [kubernetes/cloud-provider-aws](https://github.com/kubernetes/cloud-provider-aws/blob/master/OWNERS) - **Meetings:** @@ -108,7 +109,7 @@ The following [subprojects][subproject-definition] are owned by sig-cloud-provid - [kubernetes-sigs/blobfuse-csi-driver](https://github.com/kubernetes-sigs/blobfuse-csi-driver/blob/master/OWNERS) - [kubernetes-sigs/cloud-provider-azure](https://github.com/kubernetes-sigs/cloud-provider-azure/blob/master/OWNERS) - **Meetings:** - - Azure Subproject Meeting: [Mondays at 18:00 PT (Pacific Time)](https://zoom.us/j/586836662) (monthly - third Monday). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=18:00&tz=PT%20%28Pacific%20Time%29). + - Azure Subproject Meeting: [Tuesdays at 16:00 PT (Pacific Time)](https://zoom.us/j/586836662) (monthly - third Tuesday). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=16:00&tz=PT%20%28Pacific%20Time%29). - [Meeting notes and Agenda](https://docs.google.com/document/d/1SpxvmOgHDhnA72Z0lbhBffrfe9inQxZkU9xqlafOW9k/edit). - [Meeting recordings](https://www.youtube.com/playlist?list=PL69nYSiGNLP2JNdHwB8GxRs2mikK7zyc4). ### provider-baiducloud diff --git a/sig-cluster-lifecycle/README.md b/sig-cluster-lifecycle/README.md index 0b16a30c..649ce370 100644 --- a/sig-cluster-lifecycle/README.md +++ b/sig-cluster-lifecycle/README.md @@ -25,7 +25,7 @@ The Chairs of the SIG run operations and processes governing the SIG. * Justin Santa Barbara (**[@justinsb](https://github.com/justinsb)**), Google * Lubomir Ivanov (**[@neolit123](https://github.com/neolit123)**), VMware -* Vince Prignano (**[@vincepri](https://github.com/vincepri)**), VMware +* Vince Prignano (**[@vincepri](https://github.com/vincepri)**), Red Hat ### Technical Leads The Technical Leads of the SIG establish new subprojects, decommission existing @@ -45,7 +45,7 @@ subprojects, and resolve cross-subproject technical issues and decisions. - [Open Community Issues/PRs](https://github.com/kubernetes/community/labels/sig%2Fcluster-lifecycle) - GitHub Teams: - [@kubernetes/sig-cluster-lifecycle](https://github.com/orgs/kubernetes/teams/sig-cluster-lifecycle) - SIG Cluster Lifecycle mailing list -- Steering Committee Liaison: Davanum Srinivas (**[@dims](https://github.com/dims)**) +- Steering Committee Liaison: Nabarun Pal (**[@palnabarun](https://github.com/palnabarun)**) ## Working Groups @@ -77,6 +77,10 @@ A project focused on providing declarative APIs and tooling to simplify provisio - Cluster API office hours: [Wednesdays at 10:00 PT (Pacific Time)](https://zoom.us/j/861487554?pwd=dTVGVVFCblFJc0VBbkFqQlU0dHpiUT09) (weekly). [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/1ushaVqAKYnZ2VN_aa3GyKlS4kEd6bSug13xaXOakAQI/edit). - [Meeting recordings](https://www.youtube.com/playlist?list=PL69nYSiGNLP29D0nYgAGWt1ZFqS9Z7lw4). +### cluster-api-addon-provider-helm +Implementation of Cluster Add-on Provider for Helm, an add-on orchestration solution for Cluster API using Helm. +- **Owners:** + - [kubernetes-sigs/cluster-api-addon-provider-helm](https://github.com/kubernetes-sigs/cluster-api-addon-provider-helm/blob/main/OWNERS) ### cluster-api-operator Leverages a declarative API and an operator to empower admins to handle the lifecycle of Cluster API providers within the management cluster - **Owners:** @@ -249,9 +253,14 @@ A project that uses Ansible / Vagrant for deploying production ready clusters on - **Contact:** - Slack: [#kubespray](https://kubernetes.slack.com/messages/kubespray) - [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-cluster-lifecycle) +### logical-cluster +A set of APIs to improve the Kubernetes user experience for cluster administration by offering utilities to interact with fleet of clusters which can be managed by Cluster API, or other entities (like cloud providers). +- **Owners:** + - [kubernetes-sigs/logical-cluster](https://github.com/kubernetes-sigs/logical-cluster/blob/main/OWNERS) ### minikube Implements a local Kubernetes cluster for application development on macOS, Linux, and Windows - **Owners:** + - [kubernetes-sigs/minikube-gui](https://github.com/kubernetes-sigs/minikube-gui/blob/main/OWNERS) - [kubernetes/minikube](https://github.com/kubernetes/minikube/blob/master/OWNERS) - **Contact:** - Slack: [#minikube](https://kubernetes.slack.com/messages/minikube) diff --git a/sig-contributor-experience/README.md b/sig-contributor-experience/README.md index 4954f44b..fc023cb1 100644 --- a/sig-contributor-experience/README.md +++ b/sig-contributor-experience/README.md @@ -96,11 +96,6 @@ Creates and runs contributor-focused events, such as the Contributor Summit. Ev - [kubernetes/community/events](https://github.com/kubernetes/community/blob/master/events/OWNERS) - **Contact:** - Slack: [#sig-contribex](https://kubernetes.slack.com/messages/sig-contribex) -- **Meetings:** - - Office Hours European Edition (Open Q&A for end-user kubernetes related questions): [Wednesdays at 09:00 ET (Eastern Time)](https://hackmd.io/@k8s/office-hours) (monthly on 3rd Wednesday). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=09:00&tz=ET%20%28Eastern%20Time%29). - - Office Hours Western Edition (Open Q&A for end-user kubernetes related questions): [Wednesdays at 12:00 ET (Eastern Time)]() (monthly on 3rd Wednesday). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=12:00&tz=ET%20%28Eastern%20Time%29). - - [Meeting notes and Agenda](https://hackmd.io/@k8s/office-hours). - - [Meeting recordings](https://www.youtube.com/playlist?list=PL69nYSiGNLP3azFUvYJjGn45YbF6C-uIg). ### github-management Manages and controls Github permissions, repos, and groups, including Org Membership. - **Owners:** @@ -119,7 +114,7 @@ Manages and controls Github permissions, repos, and groups, including Org Member - [Meeting notes and Agenda](https://docs.google.com/document/d/1IiVrr1hcFWmbboExk971FsMUGfr2Wp68mdMribCuzLs/edit). - [Meeting recordings](https://www.youtube.com/playlist?list=PL69nYSiGNLP2x_48wbOPO0vXQgNTm_xxr). ### mentoring -Oversees and develops programs for helping contributors ascend the contributor ladder, including the New Contributor Workshops, Meet Our Contributors, and other programs. +Oversees and develops programs for helping contributors ascend the contributor ladder, including the New Contributor Workshops, and other programs. - **Owners:** - [kubernetes-sigs/contributor-katacoda](https://github.com/kubernetes-sigs/contributor-katacoda/blob/main/OWNERS) - [kubernetes-sigs/contributor-playground](https://github.com/kubernetes-sigs/contributor-playground/blob/master/OWNERS) diff --git a/sig-contributor-experience/meeting-notes-archive/2022-meeting-notes.md b/sig-contributor-experience/meeting-notes-archive/2022-meeting-notes.md new file mode 100644 index 00000000..a33794ca --- /dev/null +++ b/sig-contributor-experience/meeting-notes-archive/2022-meeting-notes.md @@ -0,0 +1,3863 @@ + +**December 7** + +* Host: Bob Killen +* Notetaker: +* Attendees: + * Noah Abrahams + * David Tesar + * Craig Peters + * Laura Santamaria + * Mars Toktonaliev + * Josh Berkus + * Bob Killen + * Kaslin Fields + * Nigel + * Riian Kleinhans + * Arpit Agrawal + * Roger K + * Vamshi Reddy + * Jason DeTiberus + * +* Welcome and recurring business [Host] + * CoC [Host] + * New Contributor Intro here \o/ [Everyone] +* Events: + * Office hours (Transitioning to CNCF?) + * [Community Meeting](https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k/edit#gid=932627810) [Laura] + * Behind due to job changes; still discussing what we should talk about in general? + * Holiday celebration next week + * Contributor Summit(s) + * [Bob] Call for leads - anyone potentially interested in running KCSEU? + * Noah is interested + * Check for Europeans on prior teams + * Other/Discussion: +* Mentoring: + * Group Mentoring + * External Mentoring Programs +* Contributor Comms [Kaslin] + * Had a number of new folks last meeting, which was lovely! + * Repo is updated with new roles: [https://github.com/kubernetes/community/tree/master/communication/contributor-comms](https://github.com/kubernetes/community/tree/master/communication/contributor-comms) + * Chris coming back on as a co-subproject lead (not that he ever really left) + * Still need to write up a role definition for this. + * [Blog post](https://github.com/kubernetes/contributor-site/pull/338) by Frederico, our blogging lead, on the verge of posting. +* Contributor-documentation: + * Contributor Guide [Bob] + * Developer Guide [Erik/Joel] + * Contributor Site [Bob] +* Moderation [Marky]: + * YouTube Automation updates [nigel] + * need to get project zapier account + * Nigel has it basically working, issues with specific vs. top-level account for rolling out + * Some videos go live immediately, need to have descriptions and attributes edited by YouTube mods + * Need to do an audit of who has admin +* GitHub-management [Bob/Nikhita/Christoph]: + * Discussion/Update: +* Open Mic/Discussion + * [your name and topic here - should this be an issue against kubernetes/community?] + * David Tesar - [(1) Improve PR reviewer efficiency through improved label automation · Issue #6999 · kubernetes/community (github.com)](https://github.com/kubernetes/community/issues/6999) + * New Help Wanted site from CNCF (alpha): https://clotributor.dev/ + * Kubernetes has very few Help Wanted issues + * Would require some changes to labels + * CNCF wants feedback + + +## **November 9th** + + + +* Host: Madhav Jivrajani +* Notetaker: Josh Berkus +* Attendees: + * Laura Santamaria + * Noah Abrahams + * Madhav Jivrajani + * Riaan Kleinhans + * Shivanshu Raj Shrivastava + * +* Welcome and recurring business [Host] + * CoC [Host] + * New Contributor Intro here \o/ [Everyone] +* Events: + * [Community Meeting](https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k/edit#gid=932627810) [Laura] + * Contributor summit open spaces + * notes – are they being moved? Ask summit team on Monday + * Meeting next Thursday + * Potential other items + * How to deal with big PRs (Aldo) + * registry.k8s.io, maybe stop serving artifacts + * discussion item, plans are being formed - k8s-infra (Ben, Arnaud) + * Chair terms? Not yet + * Contributor Summit(s): retro on Monday + * Other/Discussion: +* Mentoring: + * Meet Our Contributors + * This is archived unless the office hours folks stop bringing on contributors + * Group Mentoring + * Madhav reached out to the current cohorts, not responses yet. + * Speed Mentoring at Kubecon + * The session at Kubecon was well-attended + * Had 8-9 kubernetes people as mentors + * Was it people looking where to get started? Some, but there were also people looking to advance. + * Definitely should participate in again + * TAG-CS is talking about doing a prep session for mentees before the speed mentoring. + * Madhav was on the community table, there was a lot of experience sharing, people talked about their own contributor experience. Madhav shared contact info, shared where to contribute. This worked out well. + * Better than usual follow-through from mentees. + * CNCF Mentoring + * Overhauling CNCF mentoring repo to make it accessible to mentees + * Ideally will have a lot of "where do I start" info + * There is help needed around this, there is an issue open as well. + * Kubernetes will use the new repo to list internship projects – or should we have a link. Probably a link. +* Community-management: + * Nothing from slack-admin. + * Youtube automation POC is made. +* Marketing [Kaslin] + * Skipping +* Contributor-documentation: + * Contributor Guide [Bob] + * Developer Guide [Erik/Joel] + * Contributor Site [Bob] + * Session at Kubecon mentioned non-code but didn't include the meeting. + * Sending an email to k-dev about the non code contribution meeting. [Noah] + * More focused on planning the initiative than recruiting new nc contributors yet. +* GitHub-management [Bob/Nikhita/Christoph]: + * No update +* Open Mic/Discussion + * [your name and topic here - should this be an issue against kubernetes/community?] + + +## October 12 + + + +* Host: Bob +* Notetaker: Josh Berkus +* Attendees: + * Craig Peters + * Laura Santamaria (leaving early) + * Rey Lejano + * Noah Abrahams + * Bob Killen + * Nigel Brown + * Josh Berkus +* Welcome and recurring business [Host] + * CoC [Host] + * New Contributor Intro here \o/ [Everyone] +* Events: + * Office hours (Transitioning to CNCF?) + * [Community Meeting](https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k/edit#gid=932627810) [Laura] + * No updates + * [Laura] No community meeting this month (KubeCon), November community meeting is week before US Thanksgiving + * [Josh] We have the label, do a campaign to use the label. (Laura still has to do a blog post) For the November community meeting, suggest to find a volunteer(s) to do a summary of decisions at Contributor Summit (Summit recap) + * [Bob] If hosts are needed, we have ContribEx lead shadows that can volunteer — after KubeCon + * Contributor Summit(s) + * Will see everyone at the summit + * Other/Discussion: +* Mentoring: + * Meet Our Contributors [Paris] + * This is archived unless the office hours folks stop bringing on contributors + * [Josh] Move to more or less the same as APAC is doing, doing Meet Our Contributors as blog posts. This will be easier to maintain. The last few Meet Our Contributors sessions were not well attended. Video is a huge effort versus a stream of blog posts + * Future priorities: 1:1 hour, group mentoring +* Community-management: + * YouTube Automation Updates [nigel] + * Trying to get zapier to behave: first send to drive, then send to youtube + * Should videos automatically go live or not? + * Josh: eventually they should but let's see the results before we do that + * Nigel: concerns about video hijacking + * Initial version will not go live automatically + * Limitations: we can make 5 zaps and have 100 actions run + * We'll get a paid account if we need it + * Pre-authorize a paid account? CNCF already authorizes it, we just need to file a servicedesk ticket + * If we get this working, do a CNCF blog so that other projects can copy it +* Marketing [Kaslin] + * Comms is all about Kubecon + * Contributor survey next year? +* Contributor-documentation: + * Contributor Guide [Bob] + * [Noah] Want to evangelize non-code meetings that will come together post kubecon + * Course is not going to publish before Kubecon – will pub after + * Craig working on live demo using minikube & codespaces, would like to have configurations in k/k github dir + * will switch from minikube to kind + * will create issue and tag Bob etc. + * Developer Guide [Erik/Joel] + * Contributor Site [Bob] +* GitHub-management [Bob/Nikhita/Christoph]: + * Discussion/Update: +* Open Mic/Discussion + * [Noah] Group Mentoring at Kubecon + * Signup here: [https://www.surveymonkey.com/r/kcna22mentor](https://www.surveymonkey.com/r/kcna22mentor) + * Noah will ask about sharing with K-dev + * Has already been shared publicly in Sched + * [https://kccncna2022.sched.com/event/1AGu4/peer-group-mentoring-career-networking-in-person](https://kccncna2022.sched.com/event/1AGu4/peer-group-mentoring-career-networking-in-person) + * [your name and topic here - should this be an issue against kubernetes/community?] + + +## September 28 + + + +* Host: Josh Berkus +* Notetaker: + * Craig Peters +* Attendees: + * Craig Peters + * Rey Lejano + * Josh Berkus + * Chris Short + * Noah Abrahams + * Kaslin Fields + * Laura Santamaria + * Omer Bensaadon + * Debabrata Panigrahi + * Atharva Shinde + * Joseph Sandoval +* Welcome and recurring business [Host] + * CoC [Host] + * New Contributor Intro here \o/ [Everyone] +* Events: + * Office hours (Transitioning to CNCF?) + * [Community Meeting](https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k/edit#gid=932627810) [Laura] + * None for October because KubeCon NA + * New tags are ready (thank you, Madhav! [https://github.com/kubernetes/community/issues/6704](https://github.com/kubernetes/community/issues/6704)) + * Need to sync with Marketing about comms on this. Would a blog post be helpful, too? What would be the best way to socialize this? + * SIG Release Enhancements may have input ([#release-enhancements](https://kubernetes.slack.com/archives/C02BY55KV7E) in Slack) + * Yes to a blog post; chat about what kinds of things should be tagged, why we have it, etc. + * Contributor Summit(s) + * CFP closes Friday! Submit today! + * [https://www.kubernetes.dev/events/2022/kcsna/cfp](https://www.kubernetes.dev/events/2022/kcsna/cfp)/ + * Active comms campaign - hoping for more submissions + * Other/Discussion: +* Mentoring: + * CNCF mentoring working group underway – coordinate? + * CNCF has the same concerns and challenges: same set of internship programs (e.g. outreachy and GSoC, GSoD, LFX) + * Want to recruit coordinators for each program + * Already have one for outreachy + * A coordinator: act as an admin for the program (larger time commitment during the operation of the program), keep track of deadlines, get listed with each program + * Current issue is when contribex does it there are too many conflicting independent deadlines + * Debabrata and Paris had documented this role, [https://github.com/kubernetes/community/blob/master/mentoring/programs/mentoring-lead.md](https://github.com/kubernetes/community/blob/master/mentoring/programs/mentoring-lead.md) but it didn’t work as desired. If we get commitment and early. Will draft comms and get it sent out next week + * Leverage excitement around KubeCon to get the message out + * Group mentoring at KubeCon - is it happening? Who from CNCF is running it? Is there a signup sheet? Wendy West @ CNCF usually handles it + * Participate in some way - Noah is going to reach out +* Community-management: + * Steering Election + * Vote today (open through eod Thursday) + * Please share in social media +* Communications [Kaslin] + * New Roles in Comms + * Social Media Lead + * [https://github.com/kubernetes/community/blob/master/communication/marketing-team/role-handbooks/Social-Media.md](https://github.com/kubernetes/community/blob/master/communication/marketing-team/role-handbooks/Social-Media.md) + * handles all the tweets + * Blogging Lead + * [https://github.com/kubernetes/community/pull/6893](https://github.com/kubernetes/community/pull/6893) + * Requires coordination with docs blogging + * Events Lead + * [https://github.com/kubernetes/community/pull/6817](https://github.com/kubernetes/community/pull/6817) + * usually have comms lead for each event, but we don't always + * what if the comms lead for an event is not on the team? + * this person works with them + * Tech Lead + * [https://github.com/kubernetes/community/pull/6891](https://github.com/kubernetes/community/pull/6891) + * Automation on the [https://github.com/kubernetes-sigs/contributor-tweets](https://github.com/kubernetes-sigs/contributor-tweets) with a GitHub Action - needs ownership + * A larger contribution the k8s.dev contributor site + * Slackbot ownership + * Find us in #sig-contribex-comms! + * Josh + * Succession plans included in the role definitions - roles are time intensive and give shadowing a meaningful + * Renames: Comms Tech Lead, Event Comms Lead to distinguish from other roles + * Need similar definitions for contibex roles - linked from the charter (not on the charter so sigs.yaml doesn’t require rebuild) + * Definition for the subproject lead role +* Contributor-documentation: + * Contributor Guide [Bob] + * Developer Guide [Erik/Joel] + * there has been some progress on self-paced training + * Contributor Site [Bob] + * Non-code contributor guide after kubecon + * Comms team brings it up in meetings +* GitHub-management [Bob/Nikhita/Christoph]: + * [Omer] Looking to enable [Issue Hierarchy](https://gist.github.com/omerbensaadon/a9e7c790e3c6f06c549acc2e0a795eba) in Kubernetes, would like feedback from folks + * Demo + * Omer can provide access to those in the k8s org - anyone who can edit the md in the issues can create task lists + * Note: K8x merges are not managed by the GitHub permissions + * Omer is looking for a point of contact - for feedback and a shared slack channel - #github-management is the right slack channel + * Madhav suggests sharing the info and the gist in #github-management channel + * Doesn’t yet work for PRs (e.g. a list of issues a PR closes) but will in the future + * Discussion/Update: + * [madhav][update] Prow now has support for closing issues as “Not Supported” and the bot auto-closes issues as “Not Planned” now. Ex: [https://github.com/kubernetes/kubernetes/issues/109661](https://github.com/kubernetes/kubernetes/issues/109661) +* Open Mic/Discussion + * Cody statement? + + +## September 14 + + + +* Host: Madhav Jivrajani +* Notetaker: Josh Berkus/Bob Killen +* Attendees: + * Craig Peters + * Madhav Jivrajani + * Bob Killen + * Josh Berkus + * Noah Abrahams + * Chris Short + * Laura Santamaria (late) +* Welcome and recurring business [Host] + * CoC [Host] + * New Contributor Intro here \o/ [Everyone] +* Events: + * [Community Meeting](https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k/edit#gid=932627810) [Laura] + * Enhancements submissions process (Expert: Rey and Grace; Mark Rossetti) + * Talk about changes, go end to end through process + * Election update (Dims/Kaslin/Other Noah) + * PLEASE VOTE + * Voting walk-through + * Reminders about summit and CFP + * New approve stuff not ready yet + * Feedback on applying triage labels that removes the needs-triage status [Expert: Christoph and Madhav] + * Contributor Summit(s) + * On track, need people to reg ASAP and submit stuff to CFP + * Current reg: 140 + * [https://www.kubernetes.dev/events/2022/kcsna/cfp/](https://www.kubernetes.dev/events/2022/kcsna/cfp/) + * Other/Discussion: +* Mentoring: + * Meet Our Contributors [Paris] + * This is archived unless the office hours folks stop bringing on contributors + * Group Mentoring [Paris] + * [bob] contribex is the only one running the mentoring cohorts as of now. +* Community-management: + * [bob] Marky is reaching out to all youtube mods to create a schedule and rotation of people + * https://github.com/kubernetes/community/issues/6754 + * if you are a youtube admin, you need to sign up for the rotation + * we'll need more admins + * If you can help out here, please contact Marky! +* Marketing [Kaslin] + * [chris] working on individual guides/rolebooks + * Twitter automation is working great! +* Contributor-documentation: + * Contributor Guide [Bob] + * [Noah] There should be a meeting time coming very soon for non code contribution + * Developer Guide [Erik/Joel] + * Contributor Site [Bob] + * Update on the contributor workshop: + * [craig] there’s been some progress in putting together in some of the sessions and objectives of the training course + * Review in progress here. + * [Course Material for New Contributor Course](https://docs.google.com/document/d/1IbOFPVPRDzeX0GOpnn0je7S8OaTOWKHx8sd-zUSQduo/edit#heading=h.voa35abkeqdi) + * Last update here was this was on course for KCNA 2022 + * Taken from old contributor workshop/course to be published on k8s.dev + * [josh] any updates on codespaces to use for new contirbutor build envs? + * [Craig] Team is positive to codespaces + * [Craig] Availability of Codespaces to all will happen after Kubecon + * Demo is definitely possible, just not GA by KubeCon + * Converting [Katacoda scenarios](https://github.com/kubernetes-sigs/contributor-katacoda) to Codespaces? + * Need to look at it. Craig will take the lead, and recruit Chris to help +* GitHub-management [Bob/Nikhita/Christoph]: + * Discussion/Update: + * [madhav] FYI: Enable use of triage labels other than triage/accepted - [https://github.com/kubernetes/test-infra/pull/27424](https://github.com/kubernetes/test-infra/pull/27424) + * [Bob] Definitely will need to communicate the change to the broader community and also ask for feedback since this essentially changes the triage process for dev on k/k. + * People used needs-information as an indicator of “we are not accepting this work until more information is posted” + * Before rolling this out, we would need to have community consensus on this. + * Good item for community meeting + * Completes triage automation + * Need to message out the change + * When we originally did this the other triage labels worked differently + * People were leaving needs-triage on until it was accepted + * Our triage labels are: triage-accepted, triage-needsinfo, triage-unresolved … +* Open Mic/Discussion + * New member coordinator? A form went to the contribex list, there was no follow-up. + * Is there existing research on new contributor friction? [Craig] + * [Josh] We have annual developer K8s contributor surveys + * We haven't had one in a while, need new questions to justify one + * We are also going to be putting out CNCF wide contributor survey + * Wil have specific questions around friction + * Part of TAG contributor strat + CNCF marketing + + +## August 31 + + + +* Host: Josh Berkus +* Notetaker: Chris Short +* Attendees: + * Craig Peters (he/him) + * Xander Grzywinski (he/him) + * Laura Santamaria (she/her) + * Chris Short (he/him) +* Welcome and recurring business [Host] + * CoC [Host] + * New Contributor Intro here \o/ [Everyone] +* Events: + * Office hours (Transitioning to CNCF?) + * [Community Meeting](https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k/edit#gid=932627810) [Laura] + * No major updates + * Requesting a new label - `area/community-meeting` + * [https://github.com/kubernetes/community/issues/6704](https://github.com/kubernetes/community/issues/6704) + * Important for all repos + * TODO(Laura): Update issue to explain why we decided it was important for all repos + * Contributor Summit(s) + * DeluxeFlux (venue) + * Other/Discussion: +* Mentoring: (SKIP: No one here from these groups) + * Meet Our Contributors [Paris] + * This is archived unless the office hours folks stop bringing on contributors + * Group Mentoring [Paris] +* Community-management: (SKIP: No one here from these groups) +* Marketing [Kaslin] + * Auto-feed to new Buffer account and shared out automatically. Note that if there’s a publish then unpublish situation, be careful because automation. + * Note currently using Nigel’s Zapier account, but will get a new financial owner once more automation created +* Contributor-documentation: + * Contributor Guide [Bob] + * Developer Guide [Erik/Joel] + * Craig here to chat about the hands-on stuff. GitHub Codespaces as the platform for that. General interest? Questions/concerns? + * Is Codespaces a paid add-on? + * Currently, only available if two types of subscriptions, but currently trying to make Codespaces available to everyone with a free tier + * What if it disappears (e.g., Katacoda)? + * There’s options like GitPod, but that would require running servers. + * How do we describe the difference between Katacoda and Codespaces? + * A lot of people might not be familiar with the differences. + * Would love to spend some time to write that out. + * Contributor Site [Bob] +* GitHub-management [Bob/Nikhita/Christoph]: (SKIP: No one here from these groups) + * Discussion/Update: +* Open Mic/Discussion + * [your name and topic here - should this be an issue against kubernetes/community?] + + +## August 17 + + + +* Host: +* Notetaker: +* Attendees: + * Xander Grzywinski (he/him) + * Jason DeTiberus (he/him) + * Laura Santamaria (she/her) +* Welcome and recurring business [Host] + * CoC [Host] + * New Contributor Intro here \o/ [Everyone] +* Events: + * Office hours (Transitioning to CNCF?) + * [Community Meeting](https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k/edit#gid=932627810) [Laura] + * Cancelling this month as there’s not much to talk about. Focus on email/twitter announcements of steering election and release stuff + * Contributor Summit(s) + * Other/Discussion: +* Mentoring: + * Group Mentoring [Paris] +* Community-management: +* Marketing [Kaslin] + * +* Contributor-documentation: + * Contributor Guide [Bob] + * Developer Guide [Erik/Joel] + * Contributor Site [Bob] +* GitHub-management [Bob/Nikhita/Christoph]: + * Discussion/Update: +* Open Mic/Discussion + * [your name and topic here - should this be an issue against kubernetes/community?] + + +## August 3 + + + +* Host: Bob Killen +* Notetaker: Josh Berkus +* Attendees: + * Jason DeTiberus + * Marky Jackson + * Chris Short + * Bob Killen + * Noah Abrahams + * Josh Berkus + * Rishit Dagli + * Craig Peters + * Debabrata Panigrahi + * Frederico Muñoz + * Rey Lejano +* Welcome and recurring business [Host] + * CoC [Host] + * New Contributor Intro here \o/ [Everyone] +* Events: + * Contributor Summit(s) + * No updates this week + * Other/Discussion: +* Mentoring: + * Meet Our Contributors [Paris] + * This is archived unless the office hours folks stop bringing on contributors + * Group Mentoring [Paris] +* Community-management: + * Elections [jberkusn] + * EOs have draft schedule + * Started Role docs + * Will be working on other tasks + * Code of Conduct committee + * Nominations end tomorrow + * Should be familiar with Kubernetes, do not need to be org members, do need to be familiar with CoCCs +* Marketing [Kaslin] + * [Notes](https://docs.google.com/document/d/1KDoqbw2A6W7rLSbIRuOlqH8gkoOnp2IHHuV9KyJDD2c/edit#) + * SIG-Docs blog coming out + * Overhauling blog submissions to use docs instead of PRs +* Contributor-documentation: + * Contributor Guide [Bob] + * Non-Code Contributors Guide [Noah A] + * Developer Guide [Erik/Joel] + * Contributor Site [Bob] +* GitHub-management [Bob/Nikhita/Christoph]: + * Discussion/Update: +* Open Mic/Discussion + * [your name and topic here - should this be an issue against kubernetes/community?] + * Craig - ideas about using GitHub Codespaces to smooth the onramp for new contributors, and for maintainers to review PRs. Other ideas around mentoring? + * Hasn't heard back from anyone yet + * Craig joined github codespaces in April, trying to help OSS projects get the most out of it + * Not everyone has access yet + * Codespaces is a custom dev container which runs vscode (backed by a whole vm with tools, debugger, testing etc) + * Would like to offer new contributor experience for builds + * Can do live PR builds/reviews in the codespace + * Not available to all users yet, could make it available to all kubernetes org members though + * Better to be accessible to folks who are not yet org members – maybe create kubernetes-learners and turn on for that group + * Some brainstorming about ideas on how to use this + * Craig (pairing with Marky) will identify the personas and use cases, and look for volunteers via [https://groups.google.com/a/kubernetes.io/g/dev](https://groups.google.com/a/kubernetes.io/g/dev) + * Marky - Add a new section for public moderation status? + * Yeah, let's overhaul the template + + +## July 20 + + + +* Host: Josh Berkus +* Notetaker: Madhav +* Attendees: + * Josh Berkus + * Bob Killen + * Jason DeTiberus + * Madhav + * Nabarun Pal + * Atharva + * Arnaud Meukam + * Avinesh + * Debabrata + * Frederico + * Joseph +* Welcome and recurring business [Host] + * CoC [Host] + * New Contributor Intro here \o/ [Everyone] +* ContribEx News + * Lead Shadows selected \o/ + * Chair shadows: + * Marky + * Kaslin + * Nabarun + * TL shadows: + * Madhav + * Priyanka + * Jason +* Events: + * Office hours (Transitioning to CNCF?) + * [Community Meeting](https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k/edit#gid=932627810) [Laura] -can't make it due to DevOpsDays Seattle, but here's notes! + * Cancelled this month's meeting as the planned topic for the steering charter PR (ref last Contribex meeting) is out of public review by that point. No need to poke at it more, and getting topics together this quickly won't happen. + * At this point steering has the input it needs to merge the change. + * [Bob] We also wanted to keep all the discussion in one place, instead of keeping it scattered across multiple avenues. + * Need to cancel the meeting invite if someone who has perms can do that (please and thank you!!!) + * [Bob] Done + * [Help Wanted] As usual, please notify Laura or someone from contribex for items to be discussed in the community meeting. + * Contributor Summit(s) + * NA kicked off, lead roles are filled -[ looking for shadows](https://github.com/kubernetes/community/issues/6734) + * [Bob] we had our first meeting this week and we have leads in all potential areas. + * [Bob] we are now looking for shadows for those roles - to be leads in future summits. + * [Bob] Doesn’t cover everything but covers quite a few things related to events: [https://github.com/kubernetes/community/tree/master/events/events-team](https://github.com/kubernetes/community/tree/master/events/events-team) + * Need to review registration form by this Friday + * Also follow up on fixing contributor-site + * Other/Discussion: +* Mentoring: + * Meet Our Contributors [Paris] + * Archived until office hours folks + * MoC APAC blog posts - the problem we have with publishing blogs via contrib-site is that editing them is a prohibitive process. + * [Josh] Going to propose a few changes to the process of publishing blogs. + * [Josh] Probably going to move over to a process where blog submissions for contrib-site is done through a hackmd or a google doc. + * + * Group Mentoring [Paris] + * Need more coordinators +* Marketing [Kaslin] + * update later + * [Deba] 3-4 blog posts in the pipeline for SIG spotlights + * Need to coordinate editorial with blog generation +* GitHub-management [Bob/Nikhita/Christoph]: + * Discussion/Update: + * [madhav] Auto-close issues as “Not Planned”: [https://github.com/kubernetes/test-infra/issues/26380](https://github.com/kubernetes/test-infra/issues/26380) + * Wanted to put it on the agenda to generate some discussion around this on the issue. + * Context: GH API recently added a new state for issues to be closed with reason “Not Planned” + * Helpful to close duplicate, support, stale issues as not planned. + * Currently the default reason/state for auto-closed issues is “Completed”. + * [Bob] I dont think “Not Planned” will need to go through community wide consensus, the messaging if changed, will need to. + * +1 to this either way. + * [Josh] This will need an announcement rather than feedback. + * [Josh] Will need to announce on #kubernetes-contributors and dev mailing list. + * [Bob] New Member Coordinator selection + * Should be notified soon, waiting to hear back from all github admins +* Elections + * Elections Subproject is now a thing + * Join #sig-contribex-elections if interested + * Should we have a meeting? Not sure + * Elekto [updated to 0.6.0](https://github.com/elekto-io/elekto/releases/tag/0.6.0) + * 2022 SC Election + * [Election Officer recommendations](https://github.com/kubernetes/community/issues/6737) + * Select officers? + * [Josh] We need to have the final set of election officers approved by steering and the officers need to come up with a timeline for the elections. All of this needs to happen by mid-August. +* Open Mic/Discussion + * [your name and topic here - should this be an issue against kubernetes/community?] + * [arnaud] slack & GCP integration : [https://github.com/kubernetes/community/issues/6717](https://github.com/kubernetes/community/issues/6717) + + +## July 6 + + + +* Host: Bob Killen +* Notetaker: Josh Berkus, others? +* Attendees: + * Noah Abrahams + * Chris Short + * Laura Santamaria (only can be here for 30 min) + * Jason DeTiberus + * Josh Berkus + * Purneswar Prasad + * Madhav Jivrajani + * Joseph Sandoval + * Atharva Shinde + * Abhishek Kumar + * Frederico Muñoz +* Welcome and recurring business [Host] + * CoC [Host] + * New Contributor Intro here \o/ [Everyone] +* Events: + * Office hours (Transitioning to CNCF?) + * [Community Meeting](https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k/edit#gid=932627810) [Laura] + * Initial interest from some folks to host in the contributors channel :tada: + * Considering the steering charter discussions, thoughts on having an experienced host + * Probably a very good idea, along with additional co-hosts and moderators + * Meeting is on the 21st + * Who? + * Laura *should* be available, assuming travel is not in the way + * Jason DeTiberus also willing to help as co-host/mod + * Chris Short will be there + * Clock for feedback on the steering charter changes will end on 27th + * Will be public steering meeting tomorrow, so expect to get bulk of feedback there + * Need to figure out moderators + * Chris is going to make it + * Recommending topics + * No comments on issue in a while ([https://github.com/kubernetes/community/issues/6544](https://github.com/kubernetes/community/issues/6544)) + * Label is stuck on technical issue, need to review + * Madhav is following up + * [https://github.com/kubernetes/community/issues/6704](https://github.com/kubernetes/community/issues/6704) + * Contributor Summit(s) + * Bob hopes to get meetings running by Monday + * Other/Discussion: +* Mentoring: + * Group Mentoring [Paris] + * SIG-App & SIG-CLI Contributor Ladder Cohort + * [https://github.com/kubernetes/community/issues/6665](https://github.com/kubernetes/community/issues/6665) + * Requisite number of folks have signed up, timeline details on the issue. + * Finishing ContribEx Lead shadow selection, will reach out to folks by end of week (ideally). +* Community-management: +* Marketing [Kaslin] + * Comms has been sent regarding the ingress-nginx survey + * Ref: [link to the email](https://groups.google.com/a/kubernetes.io/g/dev/c/A2mbA1Xyzfg/m/yOSJ09t7AgAJ?utm_medium=email&utm_source=footer) + * Buffer account? CNCF has approved, but need to set up billing manager + * waiting on CNCF staff +* Contributor-documentation: + * Contributor Guide [Bob] + * Non-code guide will be picking back up in the next couple weeks [Noah A] + * Intend to focus on discoverability of tasks and roles + * Developer Guide [Erik/Joel] + * Contributor Site [Bob] + * A lot of content on the CS is not hosted in the CS repo, it's elsewhere in the project. + * Need to replace BASH script that imports content + * [Help Wanted] Tracking issue: [https://github.com/kubernetes/contributor-site/issues/93](https://github.com/kubernetes/contributor-site/issues/93) + * Don't forget that we can just move content to the CS repo + * Pritish: question about how site publishing works to fix publish future +* GitHub-management [Bob/Nikhita/Christoph]: + * Discussion/Update: call out for new member coordinators, several people applied +* Open Mic/Discussion + * Elections Subproject, can I get +1s to push that forward this week? + * Also – other insterested members? + * Abhishek: question about pending PR. + * [your name and topic here - should this be an issue against kubernetes/community?] + + +## June 22 + + + +* Host: Josh Berkus +* Notetaker: Kaslin +* Attendees: + * Bob Killen + * Mahamed Ali + * Debabrata + * Rishit Dagli + * Nigel + * Kendall Nelson + * Frederico Munoz +* Welcome and recurring business [Host] + * CoC [Host] + * New Contributor Intro here \o/ [Everyone] +* Events: + * Office hours (Transitioning to CNCF?) + * [Community Meeting](https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k/edit#gid=932627810) [Laura] + * Contributor Summit(s) + * Detroit – will be ramping things up 2nd week of July + * Will call for volunteers then + * [Retro from EU](https://docs.google.com/document/d/1AGw5ocC-21hnGgq_nhoiJLfwwLERTPJLwlf1LrXkUuE/edit#) + * Steering Election: (see below) + * Other/Discussion: + * KCDs? + * Do we want to reach out to organizers of Kubernetes Community Days Events to see if they need any support for contributor stuff? + * Would need volunteer – issue call on SIG channels +* Mentoring: + * Meet Our Contributors + * Blogs on contributors ongoing (Especially the APAC series) + * There was a bit of confusion with the publish date of the most recent blog. The PR is currently in need of revision. + * Editing blog posts via Github comments is horribly painful and slow. Could use an updated process. Discussing officially switching the process to using a more editable format like hackmd or Google Docs rather than just making a PR. + * Volunteer to help with the the original author getting credit: Rishit Dagli (on slack or rishit.dagli@gmail.com) + * Video editions of this haven’t been happening lately + * Blockers: Volunteers, avoiding repetitive questions + * Unlikely to happen in the near future. + * Try training followed by Q&A? + * Group Mentoring [Paris] +* Community-management: + * [nigel] YouTube Automation moving toward demo + * Reliably getting Zoom to Google Drive before naming and stress testing + * Surveys: what resources should academic surveys be allowed to access? + * options: #kubernetes-users, mailing lists, boosting with tweets, #announce + * Survey requirements: public results, full survey info in header, review of survey for sanity + * ContribEx can determine what outlets are appropriate + * There is a survey slack channel for folks to throw their surveys into a void. There is no regulation of that. + * Maybe even kubernetes blog? + * Blog folks need to know the difference between official and 3rd party content + * Bob to work with blog subproject as they’re reviewing their processes +* Elections [Jberkus]: + * Preparing to launch elections subproject … members? + * Noah, Jaice, Paris, others? + * Responsibilities include updating documentation, supporting the election software alongside k8s-infra + * Intention for adopting the current election software was to allow other parts of the k8s project to hold their own elections with help from the subproject. + * Will need to shut down elections site while the repo moves/gets re-organized + * A few issues have been addressed + * Steering Election Officers + * Dims + * Noah + * *Need a 3rd* + * Responsibilities: Reminding people they need to vote. Fixing up candidate profiles (yaml) +* Marketing [Kaslin] + * Rename of marketing to Contributor-Comms + * Timing? + * Sweep of references + * Chris started it + * We have a new Slack channel! #sig-contribex-comms + * Announcement? Comms to discuss + * Josh suggests opening it to SIGs to send requests to Comms + * Compose announcement? + * We would want to let the release team know + * Working on issue template to notify Comms + * Several members working on SIG Spotlights + * Share the blog post with josh &/or sftim before creating a PR + * Author as co-commiter? + * Interviewee also needs to approve. + * Chris Short is stepping down from Comms + * always need more contribs + * Working on new role definitions, for Comms vols to fill + * Shadows too +* Contributor-documentation: + * Contributor Guide [Bob] + * Developer Guide [Erik/Joel] + * Contributor Site [Bob] +* GitHub-management [Bob/Nikhita/Christoph]: + * Expanding new members coordinator role + * Will be kicking off a new audit to remove inactive people. Since it’s been a while, will probably be big, like 150 people or something. +* Open Mic/Discussion + * [mahamed] Hi, I’m working on this PR for sig-release [https://github.com/kubernetes/org/pull/3451](https://github.com/kubernetes/org/pull/3451) . Details [here](https://github.com/kubernetes/org/pull/3451/files#diff-77d2ef584aad105b3c74e744d7b7a497e54e6d7c026acc629e075acde8f98984) and [here](https://github.com/kubernetes/release/issues/2175). Would be nice to get this feature approved so I can move forward with this. + * [Bob] Don’t believe this belongs in the k-org repo. This should be moved to the release repo. If it’s in the k-org repo, it would become the responsibility of the admins, and it’s a workflow that is specific to release. + * Finalize Josh as Chair? Done + * [Kaslin] Forgot to mention - Buffer! + * [Need get a budget request approved](https://github.com/kubernetes/funding/issues/32) + * Kaslin to monitor this: https://github.com/kubernetes/funding/issues/32 + +**June 8** + + + +* Host: Bob Killen +* Notetaker: Chris/Josh/Kaslin +* Attendees: + * Bob Killen + * Josh Berkus + * Kaslin Fields + * Jason DeTiberus + * Nigel Brown + * Chris Short + * Avinesh Tripathi + * Noah Abrahams + * Debabrata + * Frederico Muñoz +* Welcome and recurring business [Host] + * CoC [Host] + * New Contributor Intro here \o/ [Everyone] +* Events: + * Office hours (Transitioning to CNCF?) + * [Community Meeting](https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k/edit#gid=932627810) [Laura] + * No May community meeting (KCEU) + * No topics volunteered for June + * No June host but, Laura has a lead + * Josh and Bob volunteered as emergency backups (Laura at OSSummit NA) + * Topics + * Registry work (hosting locations folks pointing) + * Annual report summary + * "We could also introduce the new release lead for 1.25" —Joseph + * KubeCon Meetings Discussion (sustainability and others) + * Order for June will be Release Lead intro, registry, annual report summary, KubeCon EU meetings discussions + * KubeCon NA + * hotels already getting booked up - book soon! + * Largest number of CFP submissions yet. + * Contributor Summit(s) [Bob] + * [Retro scheduled for Monday](https://docs.google.com/document/d/1AGw5ocC-21hnGgq_nhoiJLfwwLERTPJLwlf1LrXkUuE/edit?usp=sharing) + * Kick off for starting to plan NA to ramp up soon + * No NCW + * Basics of contributing session, though, is good + * There has been some interest expressed in a longer Contrib Summit, but this is not under consideration for NA. + * Steering Election: + * At least one person who has been on Steering Election committee before needs to be on it this time, and it can’t be Josh. Sounds like it needs to be Noah. + * Other/Discussion: +* Mentoring: + * Meet Our Contributors [Paris] + * On hold, though the APAC series just completed a blog post focused on China + * PR expected like tomorrow + * [New Contributor Workshop](https://docs.google.com/document/d/1XiXjDWCc087VKqX2b6LMGRnlaRyLYGh2-eWQQr6dAmc/edit#heading=h.vs8waxtx792q) [Alison] + * Group Mentoring [Paris] + * [Deba] Was reached out by a few LFX Mentees regarding project swags, is there any way we could get them a few swags. + * Swag requests should go to ContribEx leads. +* Community-management: + * Zoom access for [nigel] + * More groups are now running into the issue where they cannot send calendar invites to their mailing lists. + * Will need to accelerate migrating groups to Kubernetes-owned domains. + * This was forced through for K-dev, but needs to be cleaned up and turned into a clear process for other groups. + * There should be an issue for this somewhere. +* Marketing [Chris/Kaslin] + * Lots of activity going on. Members new and existing engaged in a variety of activities including: + * Catching up on 1.24 feature blog tweets + * Annual report tweets + * New SIG Spotlight blogs + * Buffer for Twitter management? + * Fell off due to KubeCon. Put a link to the issue in the steering committee channel + * Working on role definitions & other repo updates + * Repo/team name change + * Slack channel creation? + * Open a PR. Naming convention: SIGname-subproject + * Need to assign Bob + * [https://github.com/kubernetes/community/blob/master/communication/slack-guidelines.md#requesting-a-channel](https://github.com/kubernetes/community/blob/master/communication/slack-guidelines.md#requesting-a-channel) +* Contributor-documentation: + * Contributor Guide [Bob] + * Developer Guide [Erik/Joel] + * Contributor Site [Bob] +* GitHub-management [Bob/Nikhita/Christoph]: + * Discussion/Update: +* Open Mic/Discussion + * [your name and topic here - should this be an issue against kubernetes/community?] + * [Deba] [https://github.com/kubernetes/website/issues/34140](https://github.com/kubernetes/website/issues/34140) + * A new server has been created to persist Kubernetes katacoda content beyond the platform’s deprecation. + * Working on figuring out what needs to be done to persist the Kubernetes content. + * ContribEx Chairs + * Chairs are overtaxed, bringing on Josh Berkus as a 3rd chair for the time being. + * Working on shadowing program to bring on new chairs. + * Likely expanding to more than 2 chairs for the future. + * Interest in shadowing chairs: + * Jason DeTiberus (Detiber) + * Noah Abrahams + * Nigel + * Kaslin + +**May 11** + + + +* Host: Bob Killin +* Notetaker: Kaslin Fields +* Attendees: + * Chris Short + * Josh Berkus + * Frederico Munoz + * Rajesh Gunasekran + * Pushkar Joglekar +* Welcome and recurring business [Host] + * CoC [Host] + * New Contributor Intro here \o/ [Everyone] +* Events: + * [Community Meeting](https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k/edit#gid=932627810) [Laura] + * Canceled this month due to KubeCon + * Should most likely cancel the October community meeting because a contributor summit will be happening very close to it. + * Should check in closer to the date + * Contributor Summit(s) [] + * ~110 registrations + * About double what we had in LA. + * 12 sigs signed up for meet and greet + * 4 sig meetings at summit + * Things should be busy! + * Planning for Detroit has begun + * Room layout already selected. 1 more room than we have for EU. 1 big, 4 small rooms. + * No new contributor workshop, but workshops targeting active org members (intermediate level) should occur in Detroit. + * We should designate someone to be in charge of contributor awards sooner rather than later. + * Steering Election: + * Josh not planning to be on the committee this year. + * Need to launch the subproject after KubeCon + * Stuff needs to be moved from the community repo, which is likely to break electo (our automated tool) + * CNCF wants to use this process for some of their own elections, so it needs to be packaged up nicely. + * Got a lot of election documentation to update/backfill. May need help. + * Other/Discussion: +* Community-management: + * SIG-Cluster-Lifecycle’s mailing list has reached the point where they are too big to be able to work properly. Will need to convert it as we did k-dev. + * We want to get everything over to k8s.io managed groups over time. + * Expect this to be rolled out over the next year. + * We can now do shared drives with custom domains, which is nice. + * The transparency report makes it look like there’s a lot more CoC sanctioning stuff going on than there is. Nowhere do we explain that the slack admin team mainly just kicks spammers off the slack. + * This gave one person the impression that the CoC committee was having a sanctioning meeting once a week, which is far from the truth of what that group does. + * This could use some clarification. + * Also people get warnings before they get kicked out. + * Marky was gonna write up a lot of this +* Marketing [Chris/Debabrata/Kaslin] + * + * + * PR out to change our repo name in github + * Marketing Team -> Contributor Comms + * Buffer request was on the Steering committee meeting agenda + * **ASAP **Need to open a PR to the steering funding directory. Once there’s a thing to +1, it’ll happen. + * Chris is on it. +* GitHub-management [Bob/Nikhita/Christoph]: + * Discussion/Update: + * Nikhita forwarded a schedule which needs to be set up. To look into again post-KubeCon. + * [Josh] Quality of life improvement suggestion: would be great to have a tool to communicate to other leads, when a lead will be out. + * GitHub admins will be giving ops-genie (atlassian on-call tool) a spin for this. +* Open Mic/Discussion + * [PJ] Two SRC + SIG Security proposals: + * SECURITY_CONTACTS merges with OWNERS. Any suggestions on how we could achieve consensus on this? Also, thinking of using this tool: [https://github.com/kubernetes-sigs/maintainers](https://github.com/kubernetes-sigs/maintainers) to keep the new field fresh. With whom and where should we start this collaboration? + * Bob made a similar suggestion a while ago. Will need signoff from: + * github admins + * prow/sig-test + * general consensus from community via k-dev. + * We have a huge issue with keeping reviewers and approvers accurately recorded in OWNERS files. Some automation could be useful here. + * If you need to do it, talk to sig lead or look at approvers and look for most active ones. + * There is some action going on here for automation to at least remove inactive approvers. + * There are thousands of owners files. You might want to limit it to named subprojects. + * Possible to keep the security_contacts field empty. + * New mailing list per SIG for private triage that includes SIG Chairs (SIG-foo-leads maybe can be reused?). Extra responsibility for the chair. How can we do a pulse check? + * Export control considerations here. Generally in favor of looping in sig leads to find the right people for these types of needs. + * If we’re going to do this, is there some way we can warn the SIG leads? + * [Josh] Suggestion: Propose an unconference session at the contributor summit. Many of the folks who need to be involved in this discussion will be there. + * Also a good item for next month’s leads meeting. Only chairs and TL’s are normally invited, but we can get it on the agenda and add Pushkar as needed. + * [your name and topic here - should this be an issue against kubernetes/community?] + +**April 27** + + + +* Host: + * Josh Berkus +* Notetaker: + * Kaslin Fields + * Laura Santamaria +* Attendees: + * Josh Berkus + * Puja Abbassi + * Arnaud Meukam + * Debabrata + * Rey Lejano + * Atharva Shinde + * Kaslin Fields + * Chris Short + * Laura Santamaria + * Rajesh Gunasekaran +* Welcome and recurring business [Host] + * CoC [Host] + * New Contributor Intro here \o/ [Everyone] +* Events: + * Office hours (Transitioning to CNCF?) + * Laura needs to chat with David, otherwise no updates + * [Community Meeting](https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k/edit#gid=932627810) [Laura] + * Great work on the community meeting last week! + * Still have an open issue/PR in progress ([https://github.com/kubernetes/community/issues/6544](https://github.com/kubernetes/community/issues/6544) and [https://github.com/kubernetes/community/pull/6597](https://github.com/kubernetes/community/pull/6597)) + * Contributor Summit(s) [Alison] + * Planning ongoing + * Currently looking at ~80 registered attendees, not sure what actual will be. + * Working on sorting out space for SIG Meetings + * SIG Meet & Greet also in the works. + * A lot of messaging needed right now, Chris and Kaslin on that. + * Could really use a coordinator for the SIG Meet and Greet + * Event will occur on the Friday of KubeCon, during lunch. + * Most of the work is needed now. You could do this role even without attending. + * Steering Election: + * Josh hasn’t had the time to officially launch the subproject. + * Other/Discussion: +* Mentoring: + * Meet Our Contributors + * [New Contributor Workshop](https://docs.google.com/document/d/1XiXjDWCc087VKqX2b6LMGRnlaRyLYGh2-eWQQr6dAmc/edit#heading=h.vs8waxtx792q) + * Group Mentoring + * Atharva, Purneswar, Carlos, and Aishwarya are ramping up on leading this, being guided by Paris. +* Community-management: + * No updates +* Marketing [Chris/Debabrata/Kaslin] + * A lot of comms needed right now for the contrib summit + * Also need some comms for SIG Meet & Greet + * KubeCon EU tweet spreadsheet is all together, and coming along. Tweets getting spec’d out in the sheet. + * Working on creating a new GitHub group to get tagged in issues + * Keeping an eye on release comms because reasons + * [Question] Calendar? + * Short version: Kinda; it’s not in place yet but we want it. Working on a lot of things to get back to fixing up some things like the Twitter bot. + * We do need to have an events calendar. This may be a role for the contrib comms sub-project. + * Improved twitter bot might be a great mentoring/internship project + * Ask CNCF to pay for [Buffer](https://buffer.com/pricing)? About $150 a year. + * Social media scheduling tool. Could function as a central hub for social media comms (not email). Can also produce a calendar, which could be useful. + * Even has approval tooling. + * [$5/mo for individual account, $10/mo for a team account.](https://buffer.com/pricing) + * Josh: We should go ahead and request the $10/mo account. + * Funding request needs to go through Steering Committee; Josh will ask Bob + * [https://github.com/kubernetes/funding](https://github.com/kubernetes/funding) + * Laura: There’s other ones like Sendible and Hootsuite, but I agree Buffer is probably better for this group + * Josh: Hootsuite is around $1000/year + * We’ve had folks interested in this work, but have lacked mentors for this project. Don’t have folks familiar enough with the twitter bot and/or with time to mentor. Which is why this might be better as an internship. Someone more experienced could just get paid to do it for a bit. +* Contributor-documentation: + * Contributor Guide [Bob] + * Developer Guide [Erik/Joel] + * Contributor Site [Bob] +* GitHub-management [Bob/Nikhita/Christoph]: + * It would be good to have more people involved in the approval process + * Chris is ready and willing. Just waiting for an opportunity to jump in. (Next meeting isn’t scheduled until after KubeCon.) +* Open Mic/Discussion + * + +**April 13** + + + +* Host: Josh Berkus / Bob Killen +* Notetaker: Rey Lejano +* Attendees: + * Rey Lejano (he/him) + * Laura Santamaria (she/her) + * Erik Arneson + * Avinesh Tripathi + * Noah Abrahams + * Debabrata + * Atharva + * Josh + * Bob + * Kaslin + * Madhav + * Paris +* Welcome and recurring business [Host] + * CoC [Host] + * New Contributor Intro here \o/ [Everyone] +* Events: + * Office hours (Transitioning to CNCF?) + * [Community Meeting](https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k/edit#gid=932627810) [Laura] + * [https://github.com/kubernetes/community/pull/6597](https://github.com/kubernetes/community/pull/6597) almost done, just need to move a file to a different directory + * [Laura] Role handbook for community meeting page + * Have all the topics for the next meeting, double-checking on the experts to come in to add to the discussion + * [Laura] Topics are chosen: + * Team lead separation proposal - [https://github.com/kubernetes/community/issues/5890](https://github.com/kubernetes/community/issues/5890) + * Terms for chair - [https://github.com/kubernetes/community/issues/5886](https://github.com/kubernetes/community/issues/5886) + * Annual reports + * Still need for April: + * [Laura] Need volunteers for the following: + * A host + * Ushers + * Notetakers + * A Zoom owner (I can’t make it as I’m out of town) + * Will post need for volunteers on Slack + * [Josh] Ideas for continuously getting topics + * [https://github.com/kubernetes/community/issues/6544](https://github.com/kubernetes/community/issues/6544) + * [Madhav] Will post an update on the above issue + * Contributor Summit(s) [Alison] + * [Josh] Social events scheduled, unconference format, + * Nigel Brown is content lead + * Relatively low-key + * Registration is higher than LA currently at 60. + * Starting next week, soliciting attendees for other things like thinking about topics, scheduling SIG meetings. + * Please share that registration is open + * SIG Docs is planning for a docs sprint + * Happy to have volunteers to help + * [Bob] Hotels are being booked for Detroit + * [Madhav] Would it be helpful for chairs and TL to review/update the help wanted section in their annual report for the meet and greet + * [Josh] SIG Meet and Greet will be during one of the lunch periods + * [Bob] Second leads meeting is tomorrow and we can mention it and add it to email to leads list + * Other/Discussion: +* Mentoring: + * Meet Our Contributors [Paris] + * [Paris] Still looking for 1 person to help out with group mentoring. Group mentoring for roles like owner/approver. Focus this year on growing more owners. Will link an issue on the chat. + * [Paris] Meet Our Contributors still on hold and will be bundled with Office Hours which will be handed over to CNCF + * [Josh] Will try next week to try async meetings for mentoring group. We did a poll on meeting times and the results were not helpful. + * [Bob] Is the meeting officially gone from the calendar? Bob will check +* Community-management: + * [Paris] YouTube needs automation, it’s a higher priority thing. Some SIG leads like to update their own videos but most others don’t. Affects the transparency of the project. Get the word out, get help. + * [Laura] Building automation for PulumiTV. Will talk to David and take care of both at the same time. Using CUELang and Pulumi (maybe - we’ll see) + * [Bob] Let’s create a service desk ticket and get this done +* Marketing [Chris/Debabrata/Kaslin] + * Discussion/Update + * [Kaslin] Kaslin is taking over marketing and comms for Contributor Summit Valencia. + * [Bob] Tweet that v1.24 is delayed - PR is merging + * [Josh] A few surveys ongoing: Release cadence survey is still going. Taylor is helping to reach the right people for the survey about renaming k/k master branch to main. Reached out to the usual channels, CNCF conformance, vendors. + * [Kaslin] We can do another tweet on k/k branch renaming + * [Bob] Get the distribution list from Security Response Committee + * [Paris] From Zoom chat, [Security-discuss@kubernetes.io](mailto:Security-discuss@kubernetes.io) + * Discussion/Update + * 1.24 release delay + * 1.25 release team applications + * Release cadence survey still going + * Contributor Summit + * Master->Main branch rename + * Target audience; Groups that do a build from git, to update their ci/cd to be ready + * Poking the security response committee to see who actually builds +* Contributor-documentation: + * Contributor Guide [Bob] + * Developer Guide [Erik/Joel] + * [Erik] PR is on the way, and working on to the next phase on the e-learning module + * [Bob] Only thing left on the PR is fixing markdown links + * [Erik] Errors came from using Google Docs + * [Bob] Google Docs has markdown support + * Contributor Site [Bob] + * [Bob] No other updates besides info on the contributor summit. Another potential contractor thing is to rewrite the converter (bash script) and moving contributor guide to contributor site +* GitHub-management [Bob/Nikhita/Christoph]: + * Discussion/Update: + * [Bob] Nabarun and Arnaud are new GH admins. Still will look for back-filling on new member coordinator role to process the applications. Nabarun is working on automation on removing or adding people. + * [Madhav] On the status of automation, we found that it can be fully automated. Is it time to introduce a new label that communicates help-wanted. Everything has an interpretation of it + * [Bob] Gut-take is that it would not be used, we get complaints of too many labels + * [Madhav] We have good-first-issue and help-wanted, are these 2 labels enough. We have a guide on the labels + * [Bob] It’s the SIG’s interpretation, there’s an expectation that whoever takes that help can do it with little guidance. Maybe update the messaging to be more explicit with what most SIGs believe what “help-wanted” will be used for. Another idea is another survey on what folks think “help-wanted” means + * [Josh] We have too many surveys going on, put this new survey after 1.24. What if we get incoherent signal. + * [Bob] A lot of the SIGs use help-wanted if the regulars don’t have capacity but issues need to be worked on. + * [Josh] Could also mean lack of expertise like if an issue needs a cryptography expert. + * [Madhav] Maybe updating the wording to be clearer + * [Paris] From Zoom chat: Add this as another question for the larger contribex survey that should come out in summer + * [Paris] From Zoom chat: IMO/E - good-first-issue (its easy as heck and/or you have a mentor), help-wanted (we need help and what we can help you with is in the issue) +* Open Mic/Discussion + * Release Team Shadow Application - Diversity [Joseph] + * [Joseph] There are areas where we can improve + * Gender ratios: + * Shadow applications 105 - 21 + * Shadows 13-12 + * Team leads 5-1 + * Lead shadows 3-1 + * Also have challenge with representation maybe work on async meetings better + * How do we amplify and get more diverse applicants. We don’t ask much besides pronouns. Are there areas where we can train leads e.g. inclusive speaker training. For 1.25, 4 (maybe 5) of the leads identify as women. + * [Paris] Please comment here [https://github.com/kubernetes/community/issues/5913](https://github.com/kubernetes/community/issues/5913) + * [Josh] Is an advocate from bringing back video interviews + * [Laura] It’s hard for women in tech space to attend meetings. Reach out to companies like get past leads to encourage companies to push for this. There needs to be education on the employer side + * [Rey] Release Team shadow reports from this [Slack thread](https://kubernetes.slack.com/archives/C1TU9EB9S/p1649839127329499) \ +[https://github.com/kubernetes-sigs/release-team-shadow-stats/issues/7](https://github.com/kubernetes-sigs/release-team-shadow-stats/issues/7) + * [Josh] Would like to get approval on Deb’s for 3rd party mentoring handbook \ +[https://github.com/kubernetes/community/pull/6570](https://github.com/kubernetes/community/pull/6570) + * [your name and topic here - should this be an issue against kubernetes/community?] + +**March 30** + + + +* Host: Bob Killen +* Notetaker: Multiplayer +* Attendees: + * Bob Killen + * Nigel Brown + * Erik Arneson + * Laura Santamaria + * Chris Short + * Atharva Shinde +* Welcome and recurring business [Host] + * CoC [Host] + * New Contributor Intro here \o/ [Everyone] +* Events: + * Office hours [rawkode] + * Carlos will be taking over soon, his first solo office hours was last month and he’ll continue to iterate and bringing a second host in due course. + * [Community Meeting](https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k/edit#gid=932627810) [Laura] + * I owe a PR to lay out each role + * Zoom to YT is fixed :tada: + * Need a way to collect topics as a group activity so it's not on the host. Ideas? + * Covered in prior meetings and Slack chats. Issue opened: [https://github.com/kubernetes/community/issues/6544](https://github.com/kubernetes/community/issues/6544), and note from last async meeting: [https://kubernetes.slack.com/archives/C01M6BTU9D3/p1647967278853499?thread_ts=1647964834.428929&cid=C01M6BTU9D3](https://kubernetes.slack.com/archives/C01M6BTU9D3/p1647967278853499?thread_ts=1647964834.428929&cid=C01M6BTU9D3) + * Where to post chat/transcript? + * SIG leads to create a gdocs folder, link from notes + * Also we're going to turn on transcription by default in the future + * Contributor Summit(s) [Alison] + * Have started regular meetings + * Still need Content Lead (unconference) + * Potentially Nigel if travel is approved + * Bob to stub out website + * on contributor-site + * North America: + * Will need to request the rooms in mid-April + * Likely will be back to the “old” version of the summit by then (we hope, knock on wood) + * Home turf, so lots of people have ideas and plans + * Bob/Jeefy/Jorge to run that CS + * Other/Discussion: +* Mentoring: + * Meet Our Contributors [Paris] + * [New Contributor Workshop](https://docs.google.com/document/d/1XiXjDWCc087VKqX2b6LMGRnlaRyLYGh2-eWQQr6dAmc/edit#heading=h.vs8waxtx792q) [Alison] + * talking about a 1.5-2 hour thing the day after CS in Detroit + * [PR](https://github.com/kubernetes/community/pull/6570) for 3rd party mentorship lead role handbook + * Discussion regarding the same [https://github.com/kubernetes/community/issues/6471](https://github.com/kubernetes/community/issues/6471) +* Community-management: + * Nigel to sync with Marky Jackson on YouTube Automation + * Will enforcing naming on Splain be sufficient? + * No, splain is unreliable – fails constantly, splain does not provide support + * Nigel is exploring other tools + * zapier, but need to go via gdrive and it's multiple steps + * will need to pay for zapier + * Calendar items should be shared to the SIG lists, which will then go to the community calendar. + * Calendar can be viewed at: https://www.kubernetes.dev/resources/calendar/ + * Calendar invites need to be tied to a sig or wg +* Marketing [Chris/Debabrata/Kaslin] + * Tweets regarding code freeze is up + * More tweets on release cycle coming up + * Surveys + * Can we re-boost the Release Cadence survey? (josh) + * Vendor survey coming up +* Contributor-documentation: + * Contributor Guide [Bob] + * Developer Guide [Erik/Joel] + * Contributor Site [Bob] +* GitHub-management [Bob/Nikhita/Christoph]: + * [Lazy Consensus out for promoting Nabarun and Arnaud to GitHub admins](https://groups.google.com/g/kubernetes-sig-contribex/c/O26DCoCdMYQ/m/GwkkzX-2AQAJ) + * Will be looking to backfill new member coordinators +* Open Mic/Discussion + * Elekto/elections + * Currently working on elekto improvements, will address creating the subproject once that's done + * [your name and topic here - should this be an issue against kubernetes/community?] + + +## + + + +* Host: Alison +* Notetaker: +* Attendees: + * Alison Dowdney + * Avinesh Tripathi + * Chris Short + * Debabrata + * Eddie + * Erik + * Harshita + * Madhav + * Nigel + * Puja + * Laura Santamaria + * Sreekaran + * Kaslin + * Atharva Shinde +* Welcome and recurring business [Host] + * CoC [Host] + * New Contributor Intro here \o/ [Everyone] +* Events: + * Office hours + * Had a presentation from sig docs today + * and 3 questions answered + * [Community Meeting](https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k/edit#gid=932627810) [Laura] + * Community Meeting is Tomorrow + * Josh is our host this month. Only one or two topics because I got delayed in putting the call out for topics. + * Exploring using labels on issues to flag topics for the meeting + * We really need a better way to find topics for the meeting, needs to be continuous, not up to the meeting host – ideas? + * That’s the point of the labels ^^^ + * [Alison] Could we define another role for agenda curation? + * [Nigel] Creating a space in slack + * Better reminders for SIG Leads + * [Laura] Better messaging about what’s expected + * [Nigel] More community meetings, and more representation of folks who aren’t in leadership + * [Madhav] Slack Automation, around reactions potentially? + * Issue created: [https://github.com/kubernetes/community/issues/6544](https://github.com/kubernetes/community/issues/6544) + * Contributor Summit(s) [Alison] + * stepping up as co-lead + * Can puja lead NA too? [paris] + * For NA I still need to check if I’ll really be there [puja] + * Scheduled meeting for next monday + * Meeting Notes and Details + * Invite is in the document + * [Notes - [Sig ContribEx] KCSEU 2022 Planning - Google Docs](https://docs.google.com/document/d/1YGPnM3UF4i9Jx4VTdIg-zfjn-_2kyps24XhPoMB67gA/edit#heading=h.y2c30jj7ec8n) + * + * Elections: + * Josh to submit the PR for the Elections subproject charter + * Move elections at the same time we update elekto + * [Chris] whats the time commitment for election committee + * Documentation needs to be updated and completed + * Other/Discussion: +* Mentoring: + * Meet Our Contributors [Paris] + * MightRolling into office hours; might sunset the documentation + * Playground, gsoc, outreachy, LFX Mentorship Program [Ihor] + * Looking for group mentoring mentoring coordinator [paris] - need to link to issue + * [https://github.com/kubernetes/community/issues/6517](https://github.com/kubernetes/community/issues/6517) + * [New Contributor Workshop](https://docs.google.com/document/d/1XiXjDWCc087VKqX2b6LMGRnlaRyLYGh2-eWQQr6dAmc/edit#heading=h.vs8waxtx792q) [Alison] + * [Chris] We should have a meeting about this + * AI +* Community-management: + * Need to get lead moderator going again [paris] +* Marketing [Chris/Debabrata/Kaslin] + * Comms regarding Kubernetes release cycle survey, sent out through slack bot/ mailing list and twitter + + [https://www.surveymonkey.com/r/k8s-cadence-2022](https://www.surveymonkey.com/r/k8s-cadence-2022) + + * Tweets/mailing list updates sent regarding office hours & monthly community meetings. + * New Meet our Contributors blog post is out, [https://kubernetes.io/blog/2022/03/16/meet-our-contributors-au-nz-ep-02/](https://kubernetes.io/blog/2022/03/16/meet-our-contributors-au-nz-ep-02/) + + [https://www.kubernetes.dev/blog/2022/03/14/meet-our-contributors-au-nz-ep-02/](https://www.kubernetes.dev/blog/2022/03/14/meet-our-contributors-au-nz-ep-02/) + +* [Nigel] Community Meeting Blog Post + * +* Contributor-documentation: + * Contributor Guide [Erik] + * Pr’s to review + * [Update the YouTube guidelines by pymander · Pull Request #6520 · kubernetes/community (github.com)](https://github.com/kubernetes/community/pull/6520) + * [Add a helper script for reformatting Markdown files by pymander · Pull Request #6356 · kubernetes/community (github.com)](https://github.com/kubernetes/community/pull/6356) + * [Update release-notes.md with community feedback by pymander · Pull Request #6498 · kubernetes/community (github.com)](https://github.com/kubernetes/community/pull/6498) + * [Update communication guide to match style guidelines by pymander · Pull Request #6491 · kubernetes/community (github.com)](https://github.com/kubernetes/community/pull/6491) + * Developer Guide [Erik/Joel] + * Contributor Site [Alison] + * [https://github.com/kubernetes/community/issues/6511](https://github.com/kubernetes/community/issues/6511) +* GitHub-management [Bob/Nikhita/Christoph]: + * Discussion/Update: +* Open Mic/Discussion + * [your name and topic here - should this be an issue against kubernetes/community?] + * [https://github.com/kubernetes/community/issues/6492](https://github.com/kubernetes/community/issues/6492) - swag ideas for OWNERs + * + + +## + + + +* Host: Alison +* Notetaker: +* Attendees: +* Avinesh Tripathi(thanks Chris) +* Chris Short +* Laura Santamaria +* Rey Lejano +* Erik Arneson +* David Flanagan +* Purneswar Prasad +* Umesh Roy +* Atharva Shinde +* Debabrata Panigrahi +* Kaslin Fields (only for about half) +* Welcome and recurring business [Host] + * CoC [Host] + * New Contributor Intro here \o/ [Everyone] +* Annual Report [Alison] + * [[WIP] SIG Contribex 2021 Annual Report by alisondy · Pull Request #6411 · kubernetes/community (github.com)](https://github.com/kubernetes/community/pull/6411) + * Go through this as a group + * Assign remaining items +* Events: + * Office hours [David] + * Making some changes to the format over the past few months + * Low engagement of questions and a lot of work to find forum questions + * Decided to split time to get updates from SIGs; will continue to do that to get some visibility and help + * New cohost: Carlos Santana. Keep rotation going over time. + * [Community Meeting](https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k/edit#gid=932627810) [Laura] + * Nigel did a great job + * Updates to do for the docs and website + * Going to put a call out for hosts unless someone wants to handraise now + * [Form for topics](https://forms.gle/EqKdy29Ts5kXi83r5) + * 17th of March + * Josh and Chris both offered if no one raises a hand + * Contributor Summit(s) [Alison] + * Contributor Summit EU + * Event Page + * [Add contributor summit EU under events by alisondy · Pull Request #6490 · kubernetes/community (github.com)](https://github.com/kubernetes/community/pull/6490) + * Going to start asynchronous meetings + * Every Tuesday from 1100 British Time + * Need to send out mailing list + * [Bob] Have one in person, biweekly f2f meeting to get some of the bigger things worked out + * Until the crew is recruited + * Need help with a call for interest to be sent out to k-dev the mailing list + * [Bob] Create a github issue + * Reference issue in mailing list + * contribex + * leads + * Ask folks + * If they are planning to be there in person + * we can get help from folks who aren’t on site for organizing + * Steering Election: + * [Elections will now be a contribex subproject](https://www.google.com/url?q=https://github.com/kubernetes/community/issues/6084&sa=D&source=docs&ust=1646245716148821&usg=AOvVaw1GTXMbEcr7bObX7UUPy0dl) + * Continuity between elections, and making election tools available to sigs + * Other/Discussion: +* Mentoring: + * Meet Our Contributors [Paris] + * Playground, gsoc, outreachy, LFX Mentorship Program [~~Ihor ~~OOO.] + * [New Contributor Workshop](https://docs.google.com/document/d/1XiXjDWCc087VKqX2b6LMGRnlaRyLYGh2-eWQQr6dAmc/edit#heading=h.vs8waxtx792q) [Erik] + * Will be starting soon, a couple weeks! + * New Mentoring meeting doodle, please fill out if you're in mentoring + * Dual meeting with two different cycles, 12 hours apart + * Can’t cover the globe with one timeslot + * Alot of folks picking current timeslot, but it’s not available. +* Community-management: + * [Nigel] Will have time to work on automation +* Marketing [Chris/Debabrata/Kaslin] + * [https://github.com/kubernetes/contributor-site/pull/292](https://github.com/kubernetes/contributor-site/pull/292) + * PR for Meet our Contributor blog post for APAC region(Aus-NZ) + * Updated marketing roles to include shadows, who is doing what + * Campagins, + * Trying to help out for mentorship co-ordinator + * Release time, tweet issue, see below. + * [Atharva] The current tweet automation is broken and it either needs to be replaced or needs someone familiar with the workflow to work on. + * [Bob] What new tools + * Microsoft Workflow + * [Atharva] Made a document [Kubernetes Tweet Automation - Google Docs](https://docs.google.com/document/d/1vX8x5y6jpKLNJ9_UyJYAMizfo0RlTWpc5AgLWXjXPo0/edit#heading=h.1pb2sfe4dwv9) + * Unable to find a free solution + * [Bob] Why are we looking at other tools? + * [`.tweet` Front Matter syntax for replies, retweets, schedule, media, and more · Issue #166 · gr2m/twitter-together (github.com)](https://github.com/gr2m/twitter-together/issues/166) + * Want better flexibility with tools + * [Bob] Potential solution is to contribute a fix upstream + * Would be good for many projects, not just Kubernetes. + * If we go to something that is another a tool, it may be harder for other folks outside of marketing and contribex to interface +* Contributor-documentation: + * Have done a bunch of PR’s + * [Erik] Created script in hack directory, auto format markdown + * Needs some more reviews + * Contributor Guide [Erik] + * Developer Guide [Erik/Joel] + * Contributing.md is different for some sigs + * Reach out to other sigs to update them + * Sigs that do have contributing.md have them because their process differs from main guide + * Get contributors, and get them familiar with the subgroups + * Contributor Site [Bob] + * What are thoughts on moving the contributor guide to the contributor site + * We had discussions about this, pre contributor site + * k.dev is starting to be used more that k/community + * Native support for localization + * Hugo Shortcodes + * [Paris] We need a plan + * [Alison] We need an issue +* GitHub-management [Bob/Nikhita/Christoph]: + * Discussion/Update: + * +* Open Mic/Discussion + * [your name and topic here - should this be an issue against kubernetes/community?] + + +## February 16 + + + +* Host: Alison / Chris Short +* Notetaker: Rey Lejano +* Attendees: + * Alison Dowdney + * Chris Short + * Debabrata + * Rey Lejano + * Laura Santamaria + * Erik Arneson + * Jayesh Srivastava + * Atharva Shinde + * Nigel + * Kaslin Fields +* Welcome and recurring business [Host] + * CoC [Host] + * New Contributor Intro here \o/ [Everyone] +* Events: + * Office hours [Rawkode] + * Paris was on today showing love for contribex! + * [Paris] David and Carlos, Carlos will host office hours as well, are looking to take the program to CNCF and not contribex for sustainability reasons. It’s not official yet until we migrate the documentation over. Once we can migrate documentation in regards to operations of office hours then it will be a CNCF thing. Trying to figure out where that lives in the CNCF. + * [Community Meeting](https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k/edit#gid=932627810) [Laura] + * [Laura] Starting this month, meeting invite is out. Nigel will be our host. Nigel has an email out to k-dev which is now via form. Three major topics: dockershim removal, reliability, updates on 1.24 and a brief we moved k-dev. There is a form where people can propose a topic and when they would like to present it. Trying to figure out how to get form to contribex Google drive. + * [Paris] Can we create a form in GitHub or maybe an issue template. We can do a drive and set Laura up as an editor. + * [AI - Laura] Laura to add [contributor@kubernetes.io](mailto:contributor@kubernetes.io) as editor on the form that is already created + * [Rey] Can we do announcements, asking for the March community meeting + * [Laura] Yes + * [Nigel] Agenda should be up-to-date, will do a dry run and watch a previous meeting + * [Laura] Will also be on for the recording, call for a note taker + * [Nigel] Open question is what goes in the blog - for post-call + * Contributor Summit(s) [Alison] + * Start meeting to discuss logistics + * Help Wanted - Create Doodle for KCS meeting + * [Alison] Call for help to create a doodle and post in contributor summit Slack + * Logistics to be discussed + * Content + * Same as NA? Chillout space + * [Alison] Subject to change after 1st meeting + * Website + * Help Wanted - Create save the date page + * Documents in community repo + * Alison - Will pr into community repo tonight with details, space, and dates + * TAG App-Delivery is interested in gathering in the same space/time + * Other/Discussion: +* Mentoring: + * Meet Our Contributors [Paris] \ + - LETS GOOOOOOO + * Lets make April our new launch + * Or should we bundle this into office hours and not do it? + * [Paris] Since calendar is unjammed now, we should kick off Meet Our Contributors. Want to talk about sustainability of the program, since its an intense gathering and preparation. It’s great for new contributors who want to help out. It takes about 5 hours to do one monthly episode. In the Office Hours, there’s a new format that includes a contributor on what they’re working on so there’s a meet a contributor vibe there. Should we continue to do Meet Our Contributors or wrap it with Office Hours so it’s something that we don’t have to maintain. + * [Deba] We started a meeting our contributors blog series with APAC region + * [Paris] Maybe keep meet our contributors as a blog + * [Paris] Will open an issue and make final decisions on the issue. If we don’t join meet our contributors with Office Hours then maybe do a Meet Our Contributors to once a quarter instead of once a month + * Playground, gsoc, outreachy, LFX Mentorship Program [Ihor] + * [https://github.com/kubernetes/community/issues/6471](https://github.com/kubernetes/community/issues/6471) + * [Paris] Do we need a third-party coordinator to manage full-lifecycle (not just outreach) LFX, GSOC, GSOD. Right now, we do it ad hoc. Should we make this more formal as a SIG for this role. + * [Deba] SIGs were not getting the dates, we have an umbrella issue to reach out to SIGs and use slack bots to inform of deadlines. + * [Paris] Thinking of more of full lifecycle management beyond outreach. Include managing interns as well + * [New Contributor Workshop](https://docs.google.com/document/d/1XiXjDWCc087VKqX2b6LMGRnlaRyLYGh2-eWQQr6dAmc/edit#heading=h.vs8waxtx792q) [Alison] + * KubeCon tickets for contributors [eddiezane] + * [Eddie] We as SIG Leads and chairs, we should have a way to get KubeCon tickets for active contributors. Who should we talk to? + * [Chris Short] Chris can help + * [Alison] This should be brought up with steering and reach out to CNCF and will reach out to other contribex leads + * [Paris] This is in progress + * [Eddie] Doesn’t need to be a full scholarship (transportation and housing) just a ticket + * [Paris] Need a process for this and work with the CNCF, there’s an open issue to follow [https://github.com/kubernetes/community/issues/3783](https://github.com/kubernetes/community/issues/3783) +* Community-management: + * [Nigel] On youtube, AI to create an umbrella issue and conducting testing +* Marketing [Kaslin/Chris/Debabrata] + * Discussion/Update + * [Chris] Tweet for tomorrow’s community meeting, release team support, SIG profiles + * [Deba] Working on talking with release team emeritus advisors on how can shadows contribute if they’re not selected +* Contributor-documentation: + * Contributor Guide [Bob] + * [Erik Arneson] Created a Google doc with changes they want to make, a Google doc was a poor choice to diff with markdown - almost done. Working on restructuring of help wanted guide to drive new and existing contributors to path that would be most helpful + * Developer Guide [Erik/Joel] + * [Erik] Looked at the developer guide and it hasn’t changed a whole lot since the last time Erik and Joel worked on it a year or 1.5 years ago. There’s a stale issue for SIG leads to work on their developers guide. + * Contributor Site [Bob] + * [Paris] need more contributors +* GitHub-management [Bob/Nikhita/Christoph]: + * Discussion/Update: + * [Paris] need more trusted contributors +* Open Mic/Discussion + * [your name and topic here - should this be an issue against kubernetes/community?] + * Annual reports are going on + * If you are a subproject owner ,check in with your chair to update them on whats up + * Summary will hopefully be published at the end of March and will need the outreach horns - marketing team already knows + * [Carlos] Went to kubernetes.dev, where to start? + * [Paris] https://github.com/kubernetes/contributor-site + * [Erik] The path on the site doesn’t match the path in the repo + * [Carlos] Want to update the office hours links + * [Paris] It’s canonical to the source, PR to the source then it will update kubernetes.dev + * [Carlos] Can help to get the preview link working for kubernetes.dev + * [Carlos] Carlos runs a Kubernetes book club, uses personal invite for calendar invite and is hitting the limit. Can this be part of contribex to have a Google group and run the invitation via the group + * [Chris] Out of scope if its vendor inclusive and books have to be accessible to everyone + * [Paris] From chat, scope of this sig is upstream + * [Carlos] not vendor specific, we pick free books like Production Kubernetes, 197 things SREs need to know + * [Paris] CNCF is the perfect home for this + * [Paris] See if the CNCF Ambassadors want to help out, at least you can get a mailing list with the CNCF + * [Kaslin] There’s a book club in the CNCF slack + * https://cloud-native.slack.com/archives/C01A77X84CR + + +## February 2 + + + +* Host: Alison Dowdney +* Notetaker: +* Attendees: + * Bob Killen + * Ihor Dvoretskyi + * Chris Short + * nigel brown + * Stephen Novak + * Erik Arneson + * Atharva Shinde + * Debabrata + * Umesh Roy + * Avinesh Tripathi + * Kendall Nelson + * Pritish + * Anosh Bhakare +* +* Welcome and recurring business [Host] + * CoC [Host] + * New Contributor Intro here \o/ [Everyone] +* Events: + * Office hours [PoP/Rawkode] + * Going to revist that in a bit, + * Unsure of whats going on with cloudnative tv + * Bringing in new folks to help with current + * [Community Meeting](https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k/edit#gid=932627810) [Laura] + * Need to respond to marketing (sorry!) for updates on reach-outs + * Form for topics: [https://forms.gle/Q9Jtd6Ky5ENwfEAH8](https://forms.gle/Q9Jtd6Ky5ENwfEAH8) (not sure how to share this with the new google group) + * If anyone new would love to host, I’m happy to support you and get you up there! + * [Chris] If you are new, it’s great opportunity to get involved + * Contributor Summit(s) [Alison] + * Have fallen behind on this work + * Kubecon Valencia is May 16 – 20 + * We are planning to have a reception + * We put the room reservation in already, for the same type of space as NA - 1 room with rounds and 1 smaller meeting room and SIG Docs will have a room. Assumption is that it will be a repeat, we haven’t submitted any A/V requests yet. - note from last meeting + * [Chris] Are other CNCF groups invited? + * AI: GitHub Issue to track other groups + * [https://github.com/kubernetes/community/issues/6421](https://github.com/kubernetes/community/issues/6421) + * Other/Discussion: +* Mentoring: + * Meet Our Contributors [Paris] + * Is on permahold + * Is taking place in a blog post + * Monday morning mentoring is filled with new contributors + * Opportunity to reboot + * Playground, gsoc, outreachy, LFX Mentorship Program [Ihor] + * GSoC is open for the project ideas: + * [https://github.com/cncf/mentoring/discussions/469](https://github.com/cncf/mentoring/discussions/469) + * LFX project ideas are already submitted (nearly 40 proposals total, yay!) + * [https://github.com/cncf/mentoring/discussions/445](https://github.com/cncf/mentoring/discussions/445) + * Accepted projects will be available on the LFX website shortly, and mentees will be able to apply + * [Ihor]: We’re moving forward with opening GitHub discussions for CNCF Mentoring. + * Doodle to go out for new mentoring meeting + * [New Contributor Workshop](https://docs.google.com/document/d/1XiXjDWCc087VKqX2b6LMGRnlaRyLYGh2-eWQQr6dAmc/edit#heading=h.vs8waxtx792q) [Alison] + * Next on the list +* Community-management: + * [nigel] New issue coming with updates to the YouTube Automation + * Potential solution to dump to google drive instead of YT + * Use zapier to potentially go from gdrive to YT? + * Build our own solution? + * AI – create an umbrella issue, to discuss what path to go forward. +* Marketing [Kaslin/Chris] + * Discussion/Update + * [Chris] Talked about the mentoring sub + * Katacoda scenarios needs to be documented + * Evergreen tweets + * Annual report marketing planning is underway +* Contributor-documentation: + * Contributor Guide [Erik] + * Revisiting + * Contributor Site [Bob] +* GitHub-management [Bob/Nikhita/Christoph]: + * EasyCLA Migration this weekend + * [HELP WANTED: Updating CLA.md with EasyCLA info](https://github.com/kubernetes/community/issues/6401) +* Open Mic/Discussion + * [your name and topic here - should this be an issue against kubernetes/community?] + * [Alison] + * Annual report + * Stub things + * [2021 Annual Report: SIG Contributor Experience · Issue #6370 · kubernetes/community (github.com)](https://github.com/kubernetes/community/issues/6370) + + +## January 19 + + + +* Host: Bob +* Notetaker: + * If no one else, Laura will (but please feel free to take it on if you haven’t done it before!) +* Attendees: + * Laura Santamaria + * Debabrata Panigrahi + * Purneswar Prasad + * Bob Killen + * Chris Short + * Nigel Brown + * Kendall Nelson + * Paris Pittman + * Sahdev Zala + * Atharva Shinde + * Ayushman + * Madhav Jivrajani +* Welcome and recurring business [Host] + * CoC [Host] + * New Contributor Intro here \o/ [Everyone] + * No one new :) +* Events: + * Office hours [PoP/Rawkode] + * Paris is opening an issue to donate it to Cloud Native TV. Jorge is also +1 for that. + * Chris can also help. + * [Community Meeting](https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k/edit#gid=932627810) [Laura] + * February + * K-dev migration “retro” + * KEPs + * Reliability Bar proposal + * Dockershim docs + * Open to any hosts! + * Contributor Summit(s) [] + * No updates right now + * Will be a copy-paste of KubeCon NA right now (small rooms with rounds, etc.) + * Other/Discussion: + * No new questions +* Mentoring: + * Meet Our Contributors [Paris] + * Should this stay on here? Yes. + * Paris is doing roadmap planning for mentoring with help from mentees. + * New MOC once we’ve had 1-2 community meetings (so dependent on that as community meetings are higher priority right now) + * So plan is for Q2 relaunch + * Question: + * How to help with roadmap planning? Paris doesn’t have anything specific right now. Going through issues and PRs that have an “area/mentoring” tag, on spreadsheet with impact and timetable, then deciding what goes into what quarter. Looking to get that approved by subproject owners after organizing the issues. + * Playground, gsoc, outreachy, LFX Mentorship Program [Ihor] + * Outreachy: Paris would like to start an outreachy request for Rob Scott (Gateway API). Start up a lot of support in that area. + * Group mentoring: Paris wants to prioritize this in 2022. Issues will be incoming to reboot group mentoring. + * Need to set up a programmatic setup so “you don’t need a Paris to set it up” + * [Chris] Docs? [Paris] in the repo + * It’s impactful and visible. We grew 10 chairs from this initiative last year. We need to do this. + * [Paris] No one has really figured out the 1:1 program, so either should sunset or get someone back onboard. + * [Bob, Chris] in favor of sunsetting. Hard to get investment. + * [Paris] Will make the issue to sunset it. + * [New Contributor Workshop](https://docs.google.com/document/d/1XiXjDWCc087VKqX2b6LMGRnlaRyLYGh2-eWQQr6dAmc/edit#heading=h.vs8waxtx792q) [Alison] + * Joel, Eric, and folks from Lion’s Way will be tackling this. + * Probably starting up in later Q1/early Q2. + * [Paris] Will be perfect timing for Meet Our Contributors, maybe try to collaborate with that +* Community-management: + * YouTube [Nigel] + * Making some progress. Working on the automation for YT. Need to figure out what’s captured in issues in the repo presently, so then can address programmatically vs addressing only pain points. Working on Zoom and such in terms of capabilities. So triage time! + * [Bob] The rest of CNCF and all will find this hugely helpful, so great job! [Chris] +1 + * No other questions +* Marketing [Kaslin/Chris] + * Discussion/Update: + * Twitter automation fixed :tada: + * Need more folks interested in writing/interviewing SIG leads for SIG Spotlights + * Stalled out after the new year. Send folks to the marketing meeting if you know anyone! + * Purneswar Prasad is willing to help. Will come to the meeting. + * APAC blog went live this month (last Thursday we think because time has no meaning right now). + * Other blogs in progress; should it go to the dev site first? We’re discussing it. + * [Bob] We’re currently dual-posting to both. Canonical URL would boost the SEO for k-dev, so that’s why it would be good to put it to the dev site first. Please do :) + * Question: + * How are we planning comms for Dockershim? + * So much work going on for this. There’s a whole Slack channel on this. Celeste is leading this effort, and it seems to be going well *knock on wood* + * Other than the work out of docs, don’t want to stir the hornet’s nest/bring up a ton. So blogs that come from that are good; more than that might not be the best. + * [Paris/Bob] Suggestion: Focus on the upstream contributor for marketing. Contributor site blog on that audience. Call to action on contributors. Stay scoped. Link to project board. A “meta” call. + * Docs are focused on the downstream user. + * Annual reports are starting to kick up; no specific thing for marketing right now, but what about what to do _after_ annual report is done? Tweets, blog posts, etc. Paris will come to the next meeting to start digging. End Q1/beginning Q2. + * [Debabrata] Need an efficient way to do this. Last time it was a doc; would really appreciate a better way. +* Contributor-documentation: + * Things in flight that need review: + * [Style updates to contributor guide](https://github.com/kubernetes/community/pull/6347) + * [Comms updates](https://drive.google.com/drive/folders/1v8U1jqSduLwm7lzNPILm2vmuGFy8hUPL) (large overhaul of at least 3 comms docs) + * Please try to make some time for these two reviews over the next couple days. +* GitHub-management [Bob/Nikhita/Christoph]: + * EasyCLA slated for flip over on 5 Feb 2022 (it’s a Saturday) + * Could use social boosting and Slack boost (dear Marketing…) + * [Josh] Currently, reporting path is via LF ticket. But it gives us no idea of how many problems exist. + * [Bob] Was the same problem as before, though. That’s why we let it soak for 2 months with the old one. We’ve searched for consistent issues right now, and it seems like it’s mostly new contributors that signed the old CLA and the database sync hasn’t happened. It’s a small number. So we should be mostly set at this point. (Bob’s been talking with LF about this a lot.) Things should be pretty good by now. + * Test Infra PR: [https://github.com/kubernetes/test-infra/pull/24844](https://github.com/kubernetes/test-infra/pull/24844) + * ^^ Open PR for flipping to EasyCLA. + * [Madhav] Key difference: We have removed our bot’s message on every CLA-no. Message from the LF bot now includes those details automatically. No need to duplicate notifications. + * [Madhav] k/k issues right now are mostly along the lines of support vs bugs or feature requests. Also there’s quite a few bugs/requests that are opened against versions no longer supported. + * There have been discussions (and an issue opened) around how to handle support issues. Different SIGs do different things (some ignore, some attempt to answer). The triage bot also close issues actively if it’s support with rotten and all, which is a negative experience. + * Instead of letting the triage bot auto-close, what if we had a “kind/support” label? The bot then responds with “hey, this is a support request, it will be closed in 30 days, but here’s where you can get support.” (to avoid the rotten message). ← Update the lifecycle plugin. + * Feedback: + * [Josh] Why leave them open for 30 days? + * [Madhav] To provide as much support as possible, but set expectation that there’s no guarantee of support. + * [Bob] SIGs don’t all triage the same, either. A lot of the time, there are things left open. Alternative messaging other than “rotten” would be helpful. + * [Madhav] Same logic but for out-of-support versions + * Triage label for “out of support” that has the same 30 day period and the bot tells them with a link to the version policy, etc. Will need to consider who can apply the label. + * Feedback: + * [Bob] Would this require bumping each time? + * [Josh] No, think the tag is stateless. + * [Madhav] Only org members or someone specific could apply that label. + * [Bob] Oh, so not automatically applied. + * [Josh] Would definitely need to have a human check if it appears in current/supported version. + * [Madhav] Based on current activity, it’s a really common question on whether it’s reproducible on a current version + * [Bob] What about updating the template with a link to the version docs. + * [Bob] Advanced tags and such don’t typically get used as much outside of a core group. So we’d need to socialize this a lot if we change/implement a solution. + * Answer to both: Yes, create an issue and ask for feedback! + * Note that we would have to apply this *just* to k/k. (And the support request in k/k takes you right to discuss.k). + * [Josh] New tag with “release notes action required” to alert people for changes before upgrading. Release team thought that would also have the release notes tag, but not always. They’ve fixed that, but are there any other tools that use it? + * [Bob] The rel notes website (https://relnotes.k8s.io/). But looks fixed. + * We haven’t announced that tag; probably should notify k-dev. +* Open Mic/Discussion + * [Nigel] Event coming up in Austin - Open Source Summit. Do we do stuff with that? + * [Paris] A great CFP is the Zoom to YouTube integration :D + * Really, fill out the CFPs for this kind of thing for the contributor stuff. + * In general, we don’t do anything at that event. + * [Josh] Maintainer submissions due on the 14th. Will we submit? + * [Bob] Yes… ? Any other subprojects that want to do one? Will ask in Slack. + + +## January 5 + + + +* Host: Alison Dowdney +* Notetaker: + * Rey Lejano +* Attendees: + * Alison Dowdney + * Bob Killen + * Chris Short + * Josh Berkus + * Rey Lejano + * Pritish Samal + * Purneswar Prasad + * Sandipan Panda + * James Laverack + * Xander G. + * Debabrata + * Atharva Shinde + * Anubhav Vardhan + * Ayushman Mishra + * Oshi Gupta + * Kaslin Fields (only in for 20min today though) +* Welcome and recurring business [Host] + * CoC [Host] + * New Contributor Intro here \o/ [Everyone] +* New Year Kickoff [Alison] + * We’re here! + * 2021, Briefly + * 2022, What’s in store this Q +* Events: + * Office hours [Rawkode] + * [Bob] There’s talk of making it part of Cloud Native TV instead of a Kubernetes event + * [Community Meeting](https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k/edit#gid=932627810) [Laura] + * Sorry, can’t make it in person. Update is now that the kdev migration is done, we can start the meeting back up again. Question: **Would it be better to let people get settled for January into the new mailing list before sending out a meeting invite?** (so plan for February to start back up)? Thoughts welcome! - Laura + * Bob & Chris : Yes + * Chris - What is the new mailing list + * Bob - We migrated from googlegroups to kubernetes.dev + * public mailing list was too large to send cal invites to everyone + * Contributor Summit(s) [Bob] + * Do we need to start planning for Valencia now [Alison] + * [Alison] AI - PR into the repo a new folder for Contributor Summit 2022 Valencia + * [Josh] Do we want to plan any formal Contributor Summit if this KubeCon will be up in the air like the recent KubeCons + * [Alison] We can plan out and have a potential redundancy plan for virtual. + * [Bob] We put the room reservation in already, for the same type of space as NA - 1 room with rounds and 1 smaller meeting room and SIG Docs will have a room. Assumption is that it will be a repeat, we haven’t submitted any A/V requests yet. + * [Alison] Should give a space for EU contributors to catch up + * Contributor Celebration tl;dr retro + * [Bob] Virtual, no longer worth the investment (less attendance) + * [Bob] Awards can still be virtual but prefer to be in-person + * [Alison] Still have value in events like the bake-off + * Had to cancel the bake-off this year to low participation + * [Alison] Having a roadmap kind of thing would be great & helpful + * Other/Discussion: +* Mentoring: + * Meet Our Contributors [Paris] + * [Paris] Now we have a dev list we can kick-off Meet Our Contributors but it’s lower priority than the Community Meeting. In the project state, we need maintainers and retaining the maintainers instead of new contributors. Would like to put a sem-hold for Meet our Contributors. + * [Chris] What does the Contributor Meeting need? + * [Paris] We need a program manager to drive it for structure, interesting topics, etc. + * [Bob] Laura’s structuring idea would work well but we didn’t have calendar invites. Things like bigger cross-cutting KEPs and inter-SIG things would be interesting for maintainers + * [Paris] Think about this with sustainability in mind instead of a monthly event + * [Alison] Possibly have Meet our Contributors in Cloud Native TV? + * Playground, gsoc, outreachy, LFX Mentorship Program [Ihor] + * [Josh] gsoc is not open for applications yet but it will be open soon, not sure what is going on with LFX cycle + * [Bob] Around LFX and outreach, instead of having to re-create proposals have SIGs massage/re-submit for the next scheduled thing + * [Josh] We have a directory under community to get the various SIG leads to fill things out + * [New Contributor Workshop](https://docs.google.com/document/d/1XiXjDWCc087VKqX2b6LMGRnlaRyLYGh2-eWQQr6dAmc/edit#heading=h.vs8waxtx792q) [Alison] + * [Bob] Tech Writers will be starting soon both on updating the contributor guide (re-doing it from scratch, give it 1 style / 1 voice) and that will feed into the workshop that will be developed +* Community-management: + * [Need to Know Chairs/TLs email](https://docs.google.com/document/d/1cC799hHZpo8JJfwvUa94uiPfUpo17oTTJDFobxNLL7c/edit) [Bob/Alison] + * [Alison] A little behind, for chairs/TLs, if you have things you would like to share. + * [Paris] Don’t think we do this anymore + * [Bob] We send to the leads list + * [Alison] We’ll remove this + * [Paris] Background, chairs and TL still need forms of communication and things need to bubble up to them. A lot of the chairs thought we were giving a lot of info a lot of the time. Since now we have the monthly meeting and we have a leads list, we don’t need this anymore. + * [Bob] +1 to that + * [Alison] Agree to this and will update on the agenda template +* Devstats [Bob] + * [Paris] We should remove this from the template also + * [Josh] Should come off the regular template + * [Bob] Dims wrote a tool to update devstats in shared repos better +* Marketing [Kaslin/Chris] + * Discussion/Update + * [Chris] Twitter automation is still broken, still need to look at it. A couple of Meet our Contributor posts in-flight below: + * [Deba]-Meet our Contributor series(Blog Post) + * [https://github.com/kubernetes/website/pull/31208](https://github.com/kubernetes/website/pull/31208) + * [https://github.com/kubernetes/contributor-site/pull/279](https://github.com/kubernetes/contributor-site/pull/279) + * [Atharva] Default for the automation is the master branch, when Atharva changed it to main on his local then it worked + * [Chris] Do we need a GitHub admin to help change the master branch to main + * [Bob] Don’t need a GitHub admin, there is a doc in k8s.dev/rename to help +* Contributor-documentation: + * Contributor Guide [Bob] + * [Bob] No further updates other than tech writers starting on contributor guide + * Developer Guide [Erik/Joel] + * [Bob] Lump this with the Contributor Guide. Erik, Joel, and one additional person are tech writers + * Contributor Site [Bob] + * [Chris] SEO, trying to improve k8s.dev in search results + * [Alison] Just tried searching Kubernetes Contributor on google and k8s.dev came up first +* GitHub-management [Bob/Nikhita/Christoph]: + * Discussion/Update: + * EasyCLA + * Hard Cutoff Mid february, Need to check that issues are resolved +* Slack-infra [Jeefy]: + * Discussion/Update + * [Bob] Suggest to scratch this from the agenda +* Open Mic/Discussion + * Hello from the K8s 1.24 release team [James/Xander] + * If you have been involved, continue to be transparent + * Improve the contributor experience for release team + * Blog - I didn’t make it on the Release Team, how can I still be involved? + * Find a team which is still looking for new contributors + * Roadmap + * [Alison] Would like to have a session on developing a roadmap + * [Bob] Need to look at priorities and milestones + * [Alison] Aspirational goal, by end of next week, it would be nice to get the tidying up done. + + +# 2021 + + +## December 8 + + + +* Host: Bob Killen +* Notetaker: +* Attendees: + * Laura Santamaria + * Atharva Shinde + * Rey Lejano + * Xander Grzywinski + * Avinesh Tripathi + * nigel brown + * Pritish + * Oshi Gupta + * Paris + * Debabrata + * Chris Short + * Sreekaran Srinath + * Shrikanta +* Welcome and recurring business [Host] + * CoC [Host] + * New Contributor Intro here \o/ [Everyone] +* Events: + * Office hours [PoP/Rawkode] + * Paris still needs to talk to them about taking this project and its docs (preserving) to cncf and out of contribex + * [Community Meeting](https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k/edit#gid=932627810) [Laura] + * Blocked on kdev migration (still) + * Contributor Summit(s) [Bob] + * Contributor Summit EU 2022 + * Need to reserve space by EoY + * Do we have a reasonable situation that Kubecon EU will be different from Kubecon NA? + * Let’s try to put the registration up by early Jan + * Speaker submissions are way down + * Should we have “maybe” as an option? + * Yes + * We should have multiple maybe(s) - travel restrictions, etc + * Go for 1 or 2 rooms (1 decent sized room, 1 small room) + * Looking for lead and need to think about assembling the team Jan 2022 + * Doc sprint by #sig-docs (a board room will suffice) + * Contributor Celebration + * On track for next week, please social boost [https://k8s.dev/celebration](https://k8s.dev/celebration) + * [Bob] Most of the part is tagging along at this point + * It’s structured for impromptu activities. If you want to organize something, hop-in the discord and drop it there. + * We should start documenting how Contributor Celebration is organized. + * [Paris] We should resume contributor summit and discontinue Contributor Celebration + * Steering Election: + * + * Other/Discussion: +* Mentoring: + * Meet Our Contributors [Paris] + * Blocked on kdev migration + * Playground, gsoc, outreachy, LFX Mentorship Program [Ihor] + * [New Contributor Workshop](https://docs.google.com/document/d/1XiXjDWCc087VKqX2b6LMGRnlaRyLYGh2-eWQQr6dAmc/edit#heading=h.vs8waxtx792q) [Alison] + * Erik/Joel will take on in the new year + * Contributor Katacoda setup complete + * [https://github.com/kubernetes-sigs/contributor-katacoda](https://github.com/kubernetes-sigs/contributor-katacoda) + * [https://katacoda.com/k8scontributors](https://katacoda.com/k8scontributors) + * [https://github.com/kubernetes-sigs/contributor-katacoda/pull/1](https://github.com/kubernetes-sigs/contributor-katacoda/pull/1) + * This PR needs to be merged for the scenario to work + * +* Community-management: + * Community management lead / lead moderator role + * [https://github.com/kubernetes/community/pull/6242#issuecomment-976880828](https://github.com/kubernetes/community/pull/6242#issuecomment-976880828) - need a lgtm here + * [group name for new k-dev mailing list](https://github.com/kubernetes/community/issues/6274) + * Need to approve the timeline of [Proposal: Migrating k-dev to a managed kubernetes.io account](https://github.com/kubernetes/community/issues/5877) + * [Post migration before go-live: kdev mailing list](https://github.com/kubernetes/community/issues/6275) + * Youtube stuff + * We need to figure out the zoom log in + * Kdev migration - paris + * Plan and timeline approved? + * Name +* Devstats [Bob] + * +* Marketing [Kaslin/Chris] + * +* Contributor-documentation: + * Contributor Guide [Bob] + * Erik/Joel will be starting work on revamping the contributor guide in Q1 2022 + * Developer Guide [Erik/Joel] + * Erik/Joel will be working on this after the Contributor Guide and Workshop are complete. Working backwards from the devel guide audit late last year + * Contributor Site [Bob] + * **HELP WANTED:** someone with go, regex, markdown and bash experience to rewrite bash script that handles the way content is ingested on the contributor site. + * Issue: [https://github.com/kubernetes/contributor-site/issues/93](https://github.com/kubernetes/contributor-site/issues/93) + * WIP PR: [https://github.com/kubernetes/contributor-site/pull/223](https://github.com/kubernetes/contributor-site/pull/223) +* GitHub-management [Bob/Nikhita/Christoph]: + * EasyCLA rollout delayed until 2022 + * Dec 23rd meeting cancelled; see you all in new year + * Kubernetes-nightly GitHub org used for publishing bot to be added under officially managed GitHub orgs +* Slack-infra [Jeefy]: + * +* Open Mic/Discussion + * [your name and topic here - should this be an issue against kubernetes/community?] + * + + +## November 10th + + + +* Host: Bob Killen +* Notetaker: Rey Lejano, Josh Berkus +* Attendees: + * Nigel Brown + * Josh Berkus + * Chris Short + * Rey Lejano + * Paris Pittman + * Debabrata + * Bhargav Krishna + * Kendall Nelson + * Paris Pittman + * Purneswar Prasad + * Bhargav Krishna + * Atharva Shinde + * Pranshu Srivastava + * Sandipan Panda + * Kaslin Fields +* Welcome and recurring business [Host] + * CoC [Host] + * New Contributor Intro here \o/ [Everyone] +* Events: + * [Community Meeting](https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k/edit#gid=932627810) [Laura] + * [Bob] Blocked until mailing list issues are sorted out, once mailing list issues are sorted then we’ll start up again + * Contributor Summit(s) [Bob] + * Bob will be stepping in to lead the summit + * [Bob] Plan is still to use Discord, use what we learned last year to make it smoother/easier this time around. We’ll get the site up relatively soon + * [Chris] Will the scope be tighter? + * [Bob] Will do the bakeoff and art (Josh to organize) + * [Rey] Rey, Cody, Mars, Purneswar are working on the awards + * [Josh] Starting an artist group for Kubernetes, new Slack channel called [‘Krafternetes’](https://kubernetes.slack.com/archives/C02LM67B3GA), this gives us a pool of people to sign up for things like designing an awards plaque + * [Bob] Last year, took till June to send out awards and Canada was the hardest. May use KubeCon Valencia to distribute awards + * [Paris] DevOps party games will contribute + * [Bob] Jack Box games allows you to do personal questions + * [Bob] Meeting invite for Celebration went out on Monday and we’ll use that as the main touchpoint + * Steering Election: + * [Josh] Steering election is over. Retro is still being scheduled. Probably next Thursday then will share it with Steering. One thing that came out is a technical to-do list that should be fixed in the platform + * [Bob] Dawn wrote a script that will scrape GitHubs and commits to get the emails of the voters + * [Josh] Link to the election retro \ +[https://docs.google.com/document/d/1edqfsSNk_p746PcXlbHTJa8ZHNlnw3QEqNPzlVDJmUc/edit?usp=sharing](https://docs.google.com/document/d/1edqfsSNk_p746PcXlbHTJa8ZHNlnw3QEqNPzlVDJmUc/edit?usp=sharing) + * [Josh] Need to define roles + * Other/Discussion: +* Mentoring: + * Meet Our Contributors [Paris] + * Blocked on kdev migration - same as community meeting + * https://github.com/kubernetes/community/issues/5877 + * [Bob] Need to have a k-dev admin to create this + * [Paris] Will start on this today + * [Josh] Biggest thing is to change permissions on the documents. Need to blast out to all the SIGs + * [Paris] Will get a timeline on an issue: first tell the leads for a heads up about the docs, then an email to k-dev, then continue on + * [Bob] Do this after the 1.23 release (Dec 7) + * Playground, gsoc, outreachy, LFX Mentorship Program [Ihor] + * [New Contributor Workshop](https://docs.google.com/document/d/1XiXjDWCc087VKqX2b6LMGRnlaRyLYGh2-eWQQr6dAmc/edit#heading=h.vs8waxtx792q) [Alison] + * [Bob] The contract is done for hiring the tech writers, PO is cut. Hopefully content will be produced soon and updating the Contributor Guide. We can engage more directly when the PO is done +* Community-management: + * [Bob] YouTube Admin responsibilities + * [Paris] Has 4 mentees ready to go , but have not heard from current admins about roadmap (Chris is a YT admin and can help). Need to share the load more and think of the automation. + * [Bob] Even if we solve importing of videos, need to publish with correct date and correct name for each of those and that takes the longest + * [Chris] Agrees that it is the longest process of updating and uploading to YT + * [Bob] All SIG leads need to make sure all meetings are named correctly + * [Josh] Can we quickly automate uploads (with wrong name and categorization) - yes from Paris. Then have folks rename and categorize videos after + * [Paris] Still have a pipeline issue (using Splain, third-party exporter) and a human issue + * [Paris] Need an ok from the admins to onboard mentees - yes from Chris and Bob + * [Paris] It’s a trusted role, have to be cautious with deletions since they’re permanent + * [Bob] Some sensitive things can be uploaded so we state that it’ll be at least 24 hours until a video is uploaded for videos to be sanitized + * [Chris] We need more folks for marketing + * [Kaslin] We have a good number of folks, but need clear shadowing roles/processes + * [Paris] Broadcast to k-dev + * [Josh] Bring it up to the mentoring session, there are a lot of mentees wanting an opportunity + * [Chris] Marketing meeting is on Fridays at 11am Eastern + * Need to get a meeting with all admins - only mentees responded to the doodle + * [https://doodle.com/poll/c88mdse773ruxi7z?utm_source=poll&utm_medium=link](https://doodle.com/poll/c88mdse773ruxi7z?utm_source=poll&utm_medium=link) + * [Nigel] Prior art for automation + * [https://github.com/Welltory/Zoom2Youtube](https://github.com/Welltory/Zoom2Youtube) + * [https://github.com/marketlytics/zoom-youtube-integration](https://github.com/marketlytics/zoom-youtube-integration) + * [https://marketplace.zoom.us/apps/WPKzwuoLQDuj_gPs68AQxw](https://marketplace.zoom.us/apps/WPKzwuoLQDuj_gPs68AQxw) +* Marketing [Kaslin/Chris] + * Discussion/Update + * [Kaslin] Matt is stepping out of his role, then revamping roles to have a leadership council. Chris, Kaslin, Jason, Kunal will be the council. PR is in to update and define the roles. Part of that is to create a shadowing program. + * [Chris] Doing a lot of work to increase discoverability of kubernetes.dev \ +Rey and Chris created a few PRs \ +Still trying to get access to search console +* Contributor-documentation: + * Contributor Guide [Bob] + * Developer Guide [Erik/Joel] + * Contributor Site [Bob] +* GitHub-management [Bob/Nikhita/Christoph]: + * Discussion/Update: + * Big issues with EasyCLA, which Bob is working on. + * Hoping to switch after 1.23 + * Technical issues have largely been resolved + * Can't do dual-system, will have to cut over entirely + * Still have limitations on the LF side for having multiple admins; currently only Bob and Aaron. + * Sandipan brought up the hyperlinks issue: [https://github.com/kubernetes/community/issues/5994](https://github.com/kubernetes/community/issues/5994) + * Atharva volunteered to help with GH automation. + * Contributor Marketing’s [tweets repo](https://github.com/kubernetes-sigs/contributor-tweets) needs help + * Setting up a scheduling system for tweets + * Creating auto-pr’s for k-dev emails + * Creating auto-pr’s for blog posts + * (missed 5 min of discussion because notes were frozen) +* Slack-infra [Jeefy]: + * Discussion/Update +* Open Mic/Discussion + * [your name and topic here - should this be an issue against kubernetes/community?] + * [deba] [https://github.com/kubernetes/community/issues/6003](https://github.com/kubernetes/community/issues/6003) + * Need to open a new repository + * Need a SIG to take ownership + * Try out this [https://www.katacoda.com/debanitrkl](https://www.katacoda.com/debanitrkl) it’s the scenario + * Ready for upstream developers + * [paris] [https://github.com/kubernetes/community/issues/6200](https://github.com/kubernetes/community/issues/6200) + * want to survey folks who have named roles + * will try to get ready for the celebration + * Paris to get started on that this week +* [Kaslin] Contributor Celebration + * End of year bug bash idea from past meeting? + * Also, maybe: master-->main switch? + * Blocker: must be an admin to actually do that. + * Goal is to have all repos on main by end of year + * May not be able to push this along side doc re-attribution effort + * just list it as a bug bash item? +* [Josh] Archiving the notes + +## + October 27th + +* Host: Alison +* Notetaker: +* Attendees: + * Bob Killen + * Debabrata Panigrahi + * Sandipan Panda + * Madhav Jivrajani + * Kaslin Fields + * Alison + * Pritish Samal + * Laura Santamaria (late!) + * Chris Short + * Purneswar Prasad + * Naren (First time Attendee 👋🎉) +* Welcome and recurring business [Host] + * CoC [Host] + * New Contributor Intro here \o/ [Everyone] +* Events: + * Office hours [PoP/Rawkode] + * Things are going well + * Potentially looking for other people to help + * [Community Meeting](https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k/edit#gid=932627810) [Laura] + * Discussion yet to be finished + * Still coming up with KubeCon NA + * We’ll punt to next year so we can focus on the mailing list migration. + * Do we have a discussion about the whole mailing list migration agenda? + + To be added below. + + * Contributor Summit(s) [Bob] + * We need to archive the contributor summit website + * Will be a pretty good GFI(good-first-issue) - Eg: MD links addition + * Ex. PR - [https://github.com/kubernetes/contributor-site/pull/196](https://github.com/kubernetes/contributor-site/pull/196) + * Contributor celebration: + * We’ve to plan the kickoff contributor celebration? + * Emails need to go out + * Alison is leading. + * Will kick off next week + * Shadows and more help welcome and encouraged + * Josh in for food and craft shenanigans + * Lots of hand raises for activities + * Need to get awards going ASAP + * Will be on Discord + * TODO: Alison to define shadowing + * Steering Election: + * Josh: We’re in the middle of the voting period which closes on Nov 4 + * Ability for voter exceptions closed friday + * Think of creative ways to get the word out to eligible contributors that they need to vote + * 160 ballots - exactly half of our target + * We haven’t used the slack bot to send the text in all channels + * Emailing all the sig mailing lists + * A sort of video or something to advertise steering elections + * Since there are a lot of companies that have employees as contributors to k8s, can we send out mail through them? - It’s already done (Eg: Redhat, Google, Vmware) + * The election email address can apparently send out emails; some work needs to be done to set that up to reach SIG mailing lists without getting a ton of notifications + * + * Other/Discussion: + * APAC coordinator meeting - that meeting has been canceled for a while; there was a coordinated sprint for a different APAC initiative (the blog, I think), but that sprint has finished +* Mentoring: + * Meet Our Contributors [Paris] + * Playground, gsoc, outreachy, LFX Mentorship Program [Ihor] + * Currently collecting the mid-term evaluations of the mentees + * Virtual mentees showcase - those who have successfully graduated from LFX this year or the year before. [IDEA] + * [New Contributor Workshop](https://docs.google.com/document/d/1XiXjDWCc087VKqX2b6LMGRnlaRyLYGh2-eWQQr6dAmc/edit#heading=h.vs8waxtx792q) [Alison] + * Tech writers are working on it +* Community-management: + * K8s dev migration + * Contributor documentation - rotated around lifecycle periods - SIG Docs is refusing to redirect contributor docs because of the need for localization (translation to other languages) + * The contributor site does support localization, just no one has done it yet. + * Need someone to start working on that localization + * [https://github.com/kubernetes/contributor-site/issues/167](https://github.com/kubernetes/contributor-site/issues/167) + * Needs links from other sites (SEO work, too) to get the website there + * Great first-time contributor work ;) Need familiarity with Hugo + * [https://github.com/kubernetes/contributor-site/issues/202](https://github.com/kubernetes/contributor-site/issues/202) + * Maybe falls under the Marketing Team’s purview? + * Bob: Localized contributor cheatsheet +* Marketing [Matt/Kaslin] + * Had to cancel last week meeting - Several senior contributors were out or occupied + * Next meeting will focus on role updates + * Shadowing process for helping new folks grow into those roles + * Steering Election + * Have released at least one tweet, another 2 coming this week. + * More important - Slack bot. We’ll work on getting a notice sent out to all SIGs via the Slack bot. + * Contrib Site SEO + * Should Marketing Team take this on? + * [https://github.com/kubernetes/contributor-site/issues/202](https://github.com/kubernetes/contributor-site/issues/202) +* Contributor-documentation: + * Contributor Guide [Bob] + * Developer Guide [Erik/Joel] + * Contributor Site [Bob] +* GitHub-management [Bob/Nikhita/Christoph]: + * There’s a meeting tomorrow - Easy CLA + * There’s an open PR by Nikhita - rotating of membership coordinators + * [https://github.com/kubernetes/community/pull/6185](https://github.com/kubernetes/community/pull/6185) +* Slack-infra [Jeefy]: + * No updates +* Open Mic/Discussion + * [your name and topic here - should this be an issue against kubernetes/community?] + * [Deba][https://github.com/kubernetes/community/issues/5576#issuecomment-949753480 ](https://github.com/kubernetes/community/issues/5576#issuecomment-949753480) + * [All] Mailing list migration + * Migrating k-dev to a managed kubernetes.io account : [Issue](https://github.com/kubernetes/community/issues/5877) + * The big thing is teasing out the comms schedule + * Aaron was working on GSuite automation; could migrate all docs to each SIGs Google Drive to make permissions easier + * Also should migrate all SIG mailing lists (Gdrive doesn’t require mailing list migration) + + +## September 29th + + + +* Host: Bob Killen +* Notetaker: +* Attendees: + * Pritish Samal + * Arnaud Meukam + * Josh Berkus + * Alison Downdey + * Chris Short + * Ihor Dvorestskyi + * Avinesh Tripathi + * Debabrata Panigrahi + * Anubhav Vardhan + * David Espejo + * Madhav Jivrajani + * Kaslin Fields + * Sandipan Panda +* Welcome and recurring business [Host] + * CoC [Host] + * New Contributor Intro here \o/ [Everyone] +* Events: + * Office hours [PoP/Rawkode] + * Still going well 👍 + * [Community Meeting](https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k/edit#gid=932627810) [Laura] + * Solve mailing list problem then we can revisit + * AI: find issue in k/community and push to discuss + * Contributor Summit(s) [Bob] + * AI: kick off the end of year celebration + * Steering Election: [Alison/Josh/Noah] + * Comms have been sent out + * Delay of 1 week due to technical issues + * Other/Discussion: +* Mentoring: + * Meet Our Contributors [Paris] + * Playground, gsoc, outreachy, LFX Mentorship Program [Ihor] + * No current updates + * Continue to be blocked on mentor time, can bring up in chair and TL meeting + * [New Contributor Workshop](https://docs.google.com/document/d/1XiXjDWCc087VKqX2b6LMGRnlaRyLYGh2-eWQQr6dAmc/edit#heading=h.vs8waxtx792q) [Alison] + * Going to docs sprint at kubecon to help with that + * Going to move mentoring meeting to a slack meeting +* Community-management: + * [Need to Know Chairs/TLs email](https://docs.google.com/document/d/1cC799hHZpo8JJfwvUa94uiPfUpo17oTTJDFobxNLL7c/edit) [Bob/Alison] +* Devstats [Bob] +* Marketing [Matt/Kaslin] + * Meet our Contributors blog series ongoing and doing well +* Contributor-documentation: + * Contributor Guide [Bob] + * Developer Guide [Erik/Joel] + * Contributor Site [Bob] +* GitHub-management [Bob/Nikhita/Christoph]: + * Discussion/Update: +* Slack-infra [Josh]: + * Nothing exciting this week. + * Contingency chat: Ansible project folks have picked Matrix as their new chat platform for community management reasons. Would be good to find out why they chose it over Discord. Josh will ask. +* Open Mic/Discussion + * [arnaud] Adoption of [https://cs.k8s.io](https://cs.k8s.io) : [https://github.com/kubernetes/k8s.io/issues/2182](https://github.com/kubernetes/k8s.io/issues/2182) + * Current status : running on a Equinix baremetal instance: [https://github.com/cncf/cluster/issues/67](https://github.com/cncf/cluster/issues/67) + * Working on migration to community-owned infrastructure: [https://github.com/kubernetes/k8s.io/pull/2513](https://github.com/kubernetes/k8s.io/pull/2513) + * If moving to community-owned infra, which SIG should own it? Contribex or Infra? + * Bob things Infra, but need to check with Nikita/Christoph + * If we give up this Equinix server, we should use it for something else. + * [David E] Where to start to help with [#222](https://github.com/kubernetes/contributor-site/pull/222)? + * [paris] should elections be its own subproject? + * Needs an area/label now + * Has its own tooling + * Has its own documentation + * Putting a pin in this until after the steering election + * [paris] should we have a moderator and admin + * [paris] should we have some kind of leads coordinator role in contribex? + * Bob and i currently do a lot of this right now + * Run monthly sig chair and tl meeting + + +## September 15th + + + +* Host: Alison +* Notetaker: Bob +* Attendees: + * Avinesh Tripathi + * Debabrata + * Laura Santamaria + * Kendall Nelson + * Alison + * Bob + * Paris + * Lakshya + * Neo for Adena Shao + * Sandipan Panda + * David Espejo + * Shivam Tyagi + * Kaslin Fields +* Welcome and recurring business [Host] + * CoC [Host] + * New Contributor Intro here \o/ [Everyone] +* Events: + * Office hours [PoP/Rawkode] + * Discuss with Pop/Rawkode about potentially moving Office Hours over to the CNCF + * Follow up with an item on our mailing list + * AI: Paris to reach out about it + * [Community Meeting](https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k/edit#gid=932627810) [Laura] + * There have been issues with conflicting zoom meeting IDs and people winding up in different locations. + * Shortlink routes to a different zoom link, old meeting ID has a different zoom ID + * Goal to sort out current zoom ID issues before bringing up restarting the community meeting again + * [https://zoom.us/j/91768411674?pwd=MVpqL0ZHbGFYMnpXVXpybTBvalFRQT09](https://zoom.us/j/91768411674?pwd=MVpqL0ZHbGFYMnpXVXpybTBvalFRQT09) - this is the original zoom link + * Rethink the community meeting, maybe a newsletter - repurpose lwkd and send it to kdev every week + * Use the time at kubecon to bust through a lot of the open items + * September will not be going on this round because of all of the Zoom stuff + * Contributor Summit(s) [Bob] + * Summit now more of a get together with a social in the evening + * There still will be room for people to come chill and hang out for a day (and work on stuff together) + * No formal content + * Need to start planning the end of year Virtual Contributor Celebration + * Master to main rename party + * Steering Election: + * [PR opened to add election info](https://github.com/kubernetes/community/pull/5986) + * Steering discussion going on about changing start date for SC members to accommodate KubeCon date changes + * Other/Discussion: +* Mentoring: + * Meet Our Contributors [Paris] + * Dependency - Need a calendar invite before can staff it, so no cal invites until kdev migration + * Ready to staff it + * Playground, gsoc, outreachy, LFX Mentorship Program [Ihor] + * No updates + * [New Contributor Workshop](https://docs.google.com/document/d/1XiXjDWCc087VKqX2b6LMGRnlaRyLYGh2-eWQQr6dAmc/edit#heading=h.vs8waxtx792q) [Alison] + * No updates +* Community-management: + * [Need to Know Chairs/TLs email](https://docs.google.com/document/d/1cC799hHZpo8JJfwvUa94uiPfUpo17oTTJDFobxNLL7c/edit) [Bob/Alison] +* Devstats [Lauri] + * No updates +* Marketing [Matt/Kaslin] + * Discussion/Update + * Quite a few new folks + * Group working on Meet Our Contributors APAC (as a blog series) + * Tweets going out around annual survey + * Would be great to get more automation built for marketing team (CTA to get put together) + * Also *really* need zoom to youtube automation (discussion down under open mic) +* Contributor-documentation: + * Contributor Guide [Bob] + * No updates + * Developer Guide [Erik/Joel] + * No updates + * Contributor Site [Bob] + * No updates +* GitHub-management [Bob/Nikhita/Christoph]: + * EasyCLA + * Doing a 2nd round of testing to see if enabling it is a blocker or not as a failed check. If yes, there will need to be more coordination around a cut over date. If no, can soft roll it out and then flip over to it later. +* Slack-infra [Jeefy]: + * Discussion/Update + * No update +* Open Mic/Discussion + * [your name and topic here - should this be an issue against kubernetes/community?] + * Week-long Tech Debt Community Hackathon idea + * Part of contributor celebration (lead up to it)? + * Big way for new folks to join + * End of year would be great, no pressure to get into release, etc. + * Frame as Tech Debt Burndown, SIG leads likely will be more interested in + * Good signal to big cloud providers/companies to encourage no-meeting weeks + * + + +## August 18th + + + +* Host: +* Notetaker: +* Attendees: + * Madhav Jivrajani + * Vedant Kakde + * Dawn Foster + * Kim Schlesinger + * Sahdev Zala + * Arnaud Meukam + * Josh Berkus + * Madhi Chaker + * Nigel + * Kaslin Fields + * Debabrata + * Rodolfo Martínez + * Ihor + * Pritish Samal +* Welcome and recurring business [Host] + * CoC [Host] + * New Contributor Intro here \o/ [Everyone] +* Events: + * Office hours [PoP/Rawkode] + * [Community Meeting](https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k/edit#gid=932627810) [Laura] + * Contributor Summit(s) [Bob] + * Steering Election[] + * Need to propose committee to steering + * Other/Discussion: +* Mentoring: + * Meet Our Contributors [Paris] + * Apac focused meet our contributors - blog post style + * Playground, gsoc, outreachy, LFX Mentorship Program [Ihor] + * [New Contributor Workshop](https://docs.google.com/document/d/1XiXjDWCc087VKqX2b6LMGRnlaRyLYGh2-eWQQr6dAmc/edit#heading=h.vs8waxtx792q) [Alison] +* Community-management: + * [Need to Know Chairs/TLs email](https://docs.google.com/document/d/1cC799hHZpo8JJfwvUa94uiPfUpo17oTTJDFobxNLL7c/edit) [Bob/Alison] +* Devstats [Lauri] +* Marketing [Matt/Kaslin] + * Discussion/Update + * Great collab in our last meeting around the Meet Our Contributors APAC effort + * 2 SIG-Profile blog posts in progress + * Comms efforts ongoing/in planning for KubeCon, Contrib Summit, and Steering Committee Elections + * Keeping an eye on EasyCLA migration +* Contributor-documentation: + * Contributor Guide [Bob] + * Developer Guide [Erik/Joel] + * Contributor Site [Bob] +* GitHub-management [Bob/Nikhita/Christoph]: + * Discussion/Update: +* Slack-infra [Jeefy]: + * Discussion/Update +* Open Mic/Discussion + * [your name and topic here - should this be an issue against kubernetes/community?] + * Josh Berkus - Steering Elections. We have a committee. Josh, Alison, and Noah, with Arnaud acting as liaison to Infra for use of Electa (for the first time). + * Need to set an election calendar and get things going. + * [https://github.com/kubernetes-sigs/contributor-tweets/issues/59](https://github.com/kubernetes-sigs/contributor-tweets/issues/59) [Debabrata] + * The K8sContributors tweet automation is not able to create tweet threads (as far as Kaslin is aware). Such a usecase would have to be addressed manually. But please reach out and tell us more @contributor-comms on Slack or in our meeting! + * Remove kind/design label: https://github.com/kubernetes/community/issues/5641 + + +## August 4th + + + +* Host: Bob +* Notetaker: Laura (if no one else wants it) +* Attendees: + * Laura Santamaria + * Kim Schlesinger + * Madhav Jivrajani + * Arnaud Meukam + * Josh Berkus + * Bob Killen + * Ihor Dvoretskyi + * Alison Dowdney + * Kim Schlesigner +* Welcome and recurring business [Host] + * CoC [Host] + * New Contributor Intro here \o/ [Everyone] +* Events: + * Office hours [POP/Rawkode] + * Seems to be going well? + * [Community Meeting](https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k/edit#gid=932627810) [Laura] + * August is going to be the release retro + * There was another discussion about whether the community meeting is worth persisting with the current model. Do we want to discuss that here? + * Biggest problem is updating people’s calendars + * We can export k-dev now! So should make a managed account easier to avoid the API limits :) We’re working on that. Comms is now the big thing. We need to define a plan for cutover. Laura will talk with comms to figure that plan out. + * Contributor Summit(s) [Bob] + * Going well! + * Reg form is live. Comms and Website updates are incoming + * Original plan/idea is still being followed. + * Next big decision: Where to host social + * Separate meeting on Mondays (you will get the invite if you’re on the contribex mailing list--join to get it added, or ask in the Slack channel) + * SIG meet and greet spaces are available on Wednesday at some point. + * Steering Election [Josh] + * SC Elections: need EC members (first step) + * Normally 3-person election committee, all from different employers + * Josh: tech implementation + * Using Electo + * ??: Voter management + * Maintaining list + * ??: Comms + * Sending out messages + * Will reach out to the marketing team and ask (note can’t be Broberg or Short because they work at the same company as Josh) + * If you’re interested in joining the committee, let Josh and Bob know + * Other/Discussion: + * N/A +* Mentoring: + * Meet Our Contributors [Paris] + * Now have Streamyard :tada: + * Still need calendars to get figured out, like with the community meeting + * Playground, gsoc, outreachy, LFX Mentorship Program [Ihor] + * Kicking off the fall cycle soon (LFX mentoring) + * [https://github.com/cncf/mentoring/tree/main/lfx-mentorship/2021/03-Fall](https://github.com/cncf/mentoring/tree/main/lfx-mentorship/2021/03-Fall) + * Dates are Sept 1 to end of Nov + * Call for Projects going out soon + * No updates for GSOC. End of program is end of August. 17 mentees this round. + * Last year was ~18-19 + * [New Contributor Workshop](https://docs.google.com/document/d/1XiXjDWCc087VKqX2b6LMGRnlaRyLYGh2-eWQQr6dAmc/edit#heading=h.vs8waxtx792q) Course [Alison] + * Good chat about everything on Monday + * Potentially getting tech writers from budget from Google (yay help!) + * Still need to set up page layout, then need to translate current stuff to guide format (currently in talks and slides format) + * There are a bunch of open issues in GitHub (prefix: NCW2). Jump on in! Mentoring meeting is on the SIG Contribex calendar. + * This upcoming Summit in North America isn’t running a New Contributor Workshop, as a side note (and likely won’t do one at KubeCon again due to low usefulness/amount of people actually sticking around. Seems to be better with local Meetups). + * As a replacement, see SIG Meet & Greet above in the contributor summit section. +* Community-management: + * [Need to Know Chairs/TLs email](https://docs.google.com/document/d/1cC799hHZpo8JJfwvUa94uiPfUpo17oTTJDFobxNLL7c/edit) [Bob/Alison] + * Several things on the docket: + * Contributor Summit stuff + * Steering election reminder + * General discussion around making tech leads mandatory along with terms and term limits + * K-dev migration! Send it to *everything* + * We need to set a timeframe. Set it to after the steering election? But calendar issues are acute right now. + * If we do it now, we would need to start comms right now and do the cutover in August + * We’d do a straight cutover. And we can remove bouncing emails, thankfully. + * Elections wouldn’t be too affected *other than* permissions on Google Docs. + * Moderation queues would be a big deal to get started. Every single new person posting would need to be approved, which would be everyone on a new Google Group. + * Need a minimum of 5-6 people + * We’d also need to block posting to that list at some point to help move over to the new list. + * Biggest thing is coordinating the comms. We’re migrating, and k-dev will be first. + * We can create the list now and start moving over docs and all while still in the initial comms phase. + * How about migrating sig-contribex first? Or having a starting list to move to catch things... + * Note that this migration is the Google Workspace Automation issue on GitHub + * We also can do it for any list; the person who exports the list has to have admin access to the list. + * Offer: k8s-infra as a guinea pig. Especially since the working group is becoming a SIG. + * TODO: Recruit Team + * TODO: Draft comms + * TODO: Test with k8s-infra/contribex + * TODO: Consolidate to one GitHub issue +* Devstats [Lauri] + * No updates +* Marketing [Matt/Kaslin] + * Discussion/Update + * Quite a bit of work coming up! + * Lots of asks moved over to the marketing agenda (thanks, Kaslin!) + * Couple of articles in progress (SIG-Node and Contributor Summit) + * Comms for registration and contributor summit stuff + * Bart Farrell is doing great work with a video series from contributors + * If you need help, ping the group at contributor-comms on Slack, join the meetings, or ping Kaslin! +* Contributor-documentation: + * Contributor Guide [Bob] + * No updates + * Developer Guide [Erik/Joel] + * No updates + * Contributor Site [Bob] + * No updates +* GitHub-management [Bob/Nikhita/Christoph]: + * EasyCLA Migration + * Biggest thing. We still want to try for next week, but the PR to add the support to the CI is still open. Has not been tested yet. A lot of back and forth going on. + * [https://github.com/kubernetes/test-infra/pull/22742](https://github.com/kubernetes/test-infra/pull/22742) (as soon as that merges, test so we can get it going :) ) + * Aaron is watching it + * Theoretically, seamless migration. + * Will loop in comms when we’re ready to launch + * Recently, there are a lot of good first issues, but a lot of people aren’t giving enough context to make them good first issues. So a lot of people who pick up an issue are stuck and need help. Madhav has been trying to help and pinging authors for context. Has there been any discussion to have better prompts or otherwise encourage better context on the good-first-issue labels (versus just tagging it and not having enough context)? + * Not really yet, but good question. + * Anyone can tag. Probably would be good to send a reminder out. + * Probably no better way to do it than the one at a time situation, unfortunately. The original author or someone with strong knowledge of the code needs to do it. + * If you do it, feel free to note that you’re doing it on behalf of SIG Contributor Experience. And feel free to add the context if you already know. Be sure to ping on GitHub and Slack both. + * What about a good-first-issue template? Checklists and everything. Might be hard to create across all of the repos, but yes + * Note that a lot of issues start out as regular issues and then get flagged later. + * A comment from a bot would probably help. + * Contributor comms would be helpful here, too :) Kaslin added to the marketing agenda +* Slack-infra [Jeefy]: + * Discussion/Update + * Huddles are awful. The end. + * Josh disabled a bunch and is working through them all. +* Open Mic/Discussion + * [arnaud] domain validation for Search Console. + * Last year, we were talking about this. Did we do this, or is it still needed? + * Project was to improve the SEO of the .io website. + * Arnaud has access to the console now (yay) + * ~Probably need to reach out to docs~ + * We actually mean the shortcut links, so ignore some of the above comments. We’re talking about k8s.io + * There is a problem here since we use so many short links + * We can add text records in the management stuff. + * Arnaud’s got this :) No big rush, though. + * [your name and topic here - should this be an issue against kubernetes/community?] + + +## July 21st + + + +* Host: Alison +* Notetaker: +* Attendees: + * Arnaud Meukam + * Kim Schlesinger + * Josh Berkus + * Christoph Blecker + * Sahdev Zala + * Paris Pittman +* Welcome and recurring business [Host] + * CoC [Host] + * New Contributor Intro here \o/ [Everyone] +* Events: + * Office hours [Jorge] + * [Community Meeting](https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k/edit#gid=932627810) [Laura] + * Do we have a template / structure to the agenda - + * Agenda template for moderator + * Contributor Summit(s) [Bob] + * + * Steering Election[] + * Other/Discussion: +* Mentoring: + * Meet Our Contributors [Paris] + * Streamyard is now available + * Just need calendar and streamyard + * Follow up on slack with Bob and Josh + * Playground, gsoc, outreachy, LFX Mentorship Program [Ihor] + * [New Contributor Workshop](https://docs.google.com/document/d/1XiXjDWCc087VKqX2b6LMGRnlaRyLYGh2-eWQQr6dAmc/edit#heading=h.vs8waxtx792q) [Alison] + * Got the pr into the community/.mentoring + * Need t o get pr into community website + * +* Community-management: + * [Need to Know Chairs/TLs email](https://docs.google.com/document/d/1cC799hHZpo8JJfwvUa94uiPfUpo17oTTJDFobxNLL7c/edit) [Bob/Alison] + * Couple things to send out next week when reg is announced for CS + * Can sponsor non org members to go to CS + * Half day mini summits like sig storage ones back in day, can do that just got to let us now +* Devstats [Lauri] +* Marketing [Matt/Kaslin] + * Discussion/Update +* Contributor-documentation: + * Contributor Guide [Bob] + * Developer Guide [Erik/Joel] + * Contributor Site [Bob] +* GitHub-management [Bob/Nikhita/Christoph]: + * Discussion/Update: + * Easy cla support for prow + * Once feedback is addredssed we can go to second round of testing + * Monthly github pmanagement meeting is tomorrow +* Slack-infra [Jeefy]: + * Discussion/Update +* Open Mic/Discussion + * [your name and topic here - should this be an issue against kubernetes/community?] + * 1password + * Community management group mentoring + * Bring up new members in the sig to help out + + +## July 7th Meeting + + + +* Host: +* Notetaker: +* Attendees: + * Arsh Sharma + * Bob Killen + * Chris Short + * Kendall Nelson + * Laura Santamaria + * Alison Dowdney + * Cody Crudgington (LATE) +* Welcome and recurring business [Host] + * CoC [Host] + * New Contributor Intro here \o/ [Everyone] +* Contributor-documentation: + * Contributor Guide [Bob] + * Developer Guide [Erik/Joel] + * Contributor Site [Bob] \ +- Content ingestion script [@arsh] - second regex detecting https links too now, how to generate the actual url? +* Mentoring: + * Meet Our Contributors [Paris] + * Still waiting on the Streamyard licensing to get completed for MOC + * Playground, gsoc, outreachy, LFX Mentorship Program [Ihor] + * [New Contributor Workshop](https://docs.google.com/document/d/1XiXjDWCc087VKqX2b6LMGRnlaRyLYGh2-eWQQr6dAmc/edit#heading=h.vs8waxtx792q) [Alison] + * [https://github.com/kubernetes/community/pull/5775](https://github.com/kubernetes/community/pull/5775) needs lgtm +* Community-management: + * [Need to Know Chairs/TLs email](https://docs.google.com/document/d/1cC799hHZpo8JJfwvUa94uiPfUpo17oTTJDFobxNLL7c/edit) [Bob/Alison] + * [Community Health Metrics](https://docs.google.com/spreadsheets/d/14GU565kurmyXpj3cr2klwyp2QfkS207ENrIecV9rwak/edit?usp=sharing) +* Devstats [Lauri] +* Marketing [Matt/Kaslin] + * Discussion/Update +* GitHub-management [Bob/Nikhita/Christoph]: + * Discussion/Update: +* Slack-infra [Jeefy]: + * Discussion/Update +* Events: + * [Community Meeting](https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k/edit#gid=932627810) [Laura] + * Open PR: [https://github.com/kubernetes/community/pull/5845](https://github.com/kubernetes/community/pull/5845) + * Issue regarding migrating k-dev + * Contributor Summit(s) [Bob] + * Steering Election[] + * Need to kick off process sooner rather than later + * Other/Discussion: + + +## June 30th Slack Meeting + + + +* Mentoring + * NCW at KCD Bangalore had over 75 attendees and 50+ people submitted their first PRs in contributor-playground! + * Still need to get streamyard licensed for MoC +* Events + * Community Meeting + * Still hunting for July's host; call is out on Slack in #sig-contribex and #kubernetes-contributors (looking for another engaged host for the first handful of events, which is why this isn't an email out to k-dev just yet). + * Paris volunteered as backup + * Calendars are still a sore point + * Some tentative topics are on the docket already for July + * Still evaluating the format as our attendance has been low in comparison; as a reminder/note, we're thinking a lot of the problem is Zoom fatigue more than the format not working + * Summit planning kicking off soon separately from main meeting +* Community Management + * Kick off meeting with 1password scheduled, will begin plan of rollout soon +* GitHub Management + * [Retain LGTM through squash](https://github.com/kubernetes/test-infra/pull/22663) + * [EasyCLA Migration](https://github.com/kubernetes/org/issues/2778) + * LF has been provided a dump of org members and anyone that has opened a PR within the past year to validate cla status + * [WIP PR adding support for the different CLA context to the prow plugin](https://github.com/kubernetes/test-infra/pull/22742) + * Assuming both the groups and plugin can be done and tested, current target time frame is the week of August 9th +* Slack Infra + * Slack Moderator Plugin went into CrashLoopBackOff + * K8s infra working on monitoring solution + + +## June 23rd Meeting + + + +* Host: Alison/Bob +* Notetaker: Laura +* Attendees: + * Kendall Nelson (diablo_rojo) + * Laura Santamaria + * Kaslin Fields + * Alison Dowdney + * Josh Berkus + * Ihor Dvoretskyi + * Bob AKA Kubernetes Zoom + * Arsh Sharma +* Welcome and recurring business [Host] + * CoC [Host] + * New Contributor Intro here \o/ [Everyone] +* Events: + * Office hours [Jorge] + * No updates? See notes on streaming + * [Community Meeting](https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k/edit#gid=932627810) [Laura] + * Updates to guide, website, etc (open PRs) + * Concern about a lot of work put on the hosts again. How can we get away from the requirement of the hosts needing to be majorly plugged in? + * Also, count? ~30 people on the call. Publicity blitz didn't really get the turnout we'd like to see. There were no good discussions or questions. + * Has the new format experiment failed? + * Hard to get people to come when it's optional right now, also hard with calendar invite not being able to go out. + * It probably will be a full year before the Zoom burnout ends. + * Let's start with the calendar invite problem? We've basically lost the constant communication channel and people live by their calendars. + * We really need to migrate k-dev to a managed kubernetes.io address… This is a lot of work to do. + * KEP? + * Might be a great first issue set for updating docs and such across the project. Hackday! The Google docs will possibly be the hardest part. + * TODO: Create an issue and start talking about all of the things that need to happen for this migration. + * Contributor Summit(s) [Bob/Deb] + * Graphics finalization + * Survey Monkey. Support request was sent in because the survey results were by number that didn't match the image… We're still waiting to hear back from SM Support (Ihor) + * Clear winner is #2, but we don't know what 2 is. Deb will vote and we can see which one incremented by one. + * Timeline for registration to launch? + * We should start scheduling a meeting and have a team together to plan. + * Recruit the full team :D + * Then Doodle for a date. Guess probably is end of July/early August. + * Then we can start programming + * Reception search + * Deb's working on venue search now + * Video of space at venue will be coming in a month or so. + * Result from online v in-person. 20% (24) in-person no matter restrictions; 26% (32) if company restrictions lifted, 18% (22) in person if international ok. 28% (34) virtually. 2% (3) don't plan to attend. + * Guess: ~200. Think ⅔ of folks we're used to. + * Google has explicitly allowed KubeCon + * RH individual exception requests + * Little startups mainly are as you feel comfortable + * If these numbers flip because of variants or something, we're already planning for hybrid, so *should* be an easy switch for content. The things that will change are food/beverage, giveaways, etc. + * Steering Election [Josh] + * Get Electo properly packaged for Kubernetes infrastructure. + * Could host on Equinix Metal cluster… + * Go to test infra team? WG-k8s-infra? + * There's a lot of options + * Managed Google MySQL instance + * This is ~$75/mo + * Election in September + * Announcements not quite yet. Later part of July. + * Will pull list of contributors from devstats + * Community repo is where election stuff will keep living + * Other/Discussion: + * Streaming platform (Streamyard) + * Update to double-check the login. Once it's paid for, we're good to go. + * Can someone log in without creating an account? Can we pass credentials off to fill out finance data as an example? + * They'll send an email with a passcode. You can pass that to someone else to login. + * Currently set up to the [stream-team@kubernetes.io](mailto:stream-team@kubernetes.io) address + * TODO: Ihor will get back to the group on this +* Mentoring: + * Meet Our Contributors [Paris] + * Semi-blocked on Streamyard and calendar issues (see community meeting) + * July clashes with US holiday + * Playground, gsoc, outreachy, LFX Mentorship Program [Ihor] + * No major updatesl next milestone in a couple weeks + * GSOC is in progress, as is LFX Mentoring + * [New Contributor Workshop](https://docs.google.com/document/d/1XiXjDWCc087VKqX2b6LMGRnlaRyLYGh2-eWQQr6dAmc/edit#heading=h.vs8waxtx792q) [Alison] + * Tidied up the PR and all. Next to update the website PR to remove contributing folder +* Community-management: + * [Need to Know Chairs/TLs email](https://docs.google.com/document/d/1cC799hHZpo8JJfwvUa94uiPfUpo17oTTJDFobxNLL7c/edit) [Bob/Alison] + * The potential k-dev migration and the planning involved! + * We want to test switching with contribex. Probably step 1. + * Coming up, lots of various small stuff for all of the SIGs (fallout from the annual reports) + * We will probably get pinged to help with solving the YouTube uploads, getting meetings scheduled, etc. etc. + * Not now, but soon. + * Community survey [Josh] + * Josh putting graphs together. + * Anyone really want to poke around in the data and look for things? Ping Josh. + * TODO: Export raw data into csv for the contribex raw results collection + * TODO: PII-scrubbed version to get merged to k/community +* Devstats [Lauri] + * There will be ability to filter by SIG and WG labels (issue link) +* Marketing [Matt/Kaslin] + * A few requests coming in through Slack; good to work with the community meeting. + * Talking about process, limitations, etc. + * How to enable more people is a big conversation, so keep an eye out for that getting shared + * Savita from the release team joined after hearing about marketing in the community meeting, and that communication channel is a big win! +* Contributor-documentation: + * Contributor Guide [Bob] + * No updates + * Developer Guide [Erik/Joel] + * No updates + * Contributor Site [Bob] + * No updates + * Two open working things + * WIP preview of listing the enhancements on the page ([https://github.com/kubernetes/contributor-site/pull/222](https://github.com/kubernetes/contributor-site/pull/222)) + * Arsh - Ingestion stuff + * Currently can specify in YAML the repo URL and files to copy over. Still stuck on links. + * Detecting the links in the files is part of the current line of work. + * Next steps for the content ingestion script [@arsh] + * Bash script uses regexes; no issues currently because we haven't imported content that has links in code blocks. + * Next step should be looking for libraries that can pass links in markdown. Laura will hunt. + * Goal: Search for links and then get them all corrected, then drop them in the correct location in the repo. +* GitHub-management [Bob/Nikhita/Christoph]: + * Upcoming: Issue in k/org - EasyCLA migration. Original timeframe was after code freeze, but right now, too little time to communicate and test. Now probably headed to the backup date. In short, in the works, but moving back. +* Slack-infra [Bob/Josh]: + * No updates +* Open Mic/Discussion + * [your name and topic here - should this be an issue against kubernetes/community?] + + +## June 9th Meeting + + + +* Host: Alison +* Notetaker: Laura +* Attendees: + * Alison Dowdney + * Laura Santamaria + * Arsh Sharma + * Eddie Zaneski + * Sahdev Zala + * Josh Berkus + * Sheetal Joshi + * Deb Giles + * Bob Killen + * Kendall Nelson + * Cody Crudgington +* Welcome and recurring business [Host] + * CoC [Host] + * New Contributor Intro here \o/ [Everyone] +* Open Mic/Discussion + * Script to ingest external content into the contributor site [#93](https://github.com/kubernetes/contributor-site/issues/93), [Slack thread](https://kubernetes.slack.com/archives/C1TU9EB9S/p1622097259050400) [@arsh] + * Context: Current contrib site uses a lot of regex to find and fix links from a bunch of extra repos and sources. We want to replace the regex. + * Current plan: First clone the repos and then rename to drop the directories and all to just have the .md info. +* Where are the rules for renaming the file coming from? Is there anything to keep in mind? + * Outside of renaming the files, once you get to updating the links, then you have to do the fuzzy replace of the directory location to where it will exist in Hugo (on the contributor site) + * The logs are the data to follow to help understand it. +* For now is it fine if we follow this structure -> clone, rename, replace links + * Yep! Sounds about right. Review happening in a 1:1 +* How would I know the URLs to be used for the links? + * This is where the regexes come in, to look for links in the markdown docs. We want to get away from that to use the markdown library to do that (since regex picks up links in codeblocks that we don't want to change - e.g., links to a repo) + * Bob will resync with Arsh after he has a moment to go back through the code. + * [your name and topic here - should this be an issue against kubernetes/community?] +* Events: + * Office hours [POP] + * It is still set to go, that's what we know :) + * [Community Meeting](https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k/edit#gid=932627810) [Laura] + * On the to-dos: Update the site page to mirror current process. Hope to get that PR in this week. + * Josh volunteered to host June; happily will take more people signing up for other months! + * Eddie's KEP! + * [https://github.com/kubernetes/enhancements/pull/2777](https://github.com/kubernetes/enhancements/pull/2777) + * TODO - Ping contributor comms to ping all the slack channels (and add that to the hosting guide) + * Contributor Summit(s) [Bob/Deb] + * Don't forget the poll! Update: 99 people responded so far. Everyone wants something in person; 21 attend no matter what, 28 people if company travel lifted, 19 people attend if international, 26 virtual, 3 not planning on doing so. Only 15 people responded to the late-add question. Generally, people want to attend in person, and some will attend virtual if needed. + * Registration released sometime in the next week or two. + * Helpful: save the date. Can we get that up? + * Yes, but put it on the contributor site to keep everything together. + * Graphic options are available (for branding). The contrib site doesn't exactly have a theme, but happy to put up a banner! Watch Slack for options. LA theme + * Put it to a vote at the community meeting! Deb will connect with Josh. + * Hotel: JW Marriott + * TODO: All details to get dropped in Slack so the site can get updated + * Next: When should we do this? Day -1, Day 0? + * Guess what, the colo events will happen both Monday and Tuesday :uh-oh: + * Monday is probably our best bet still (Day -1) + * Picking Monday, will disperse on Tuesday. + * Will want to look into social activities for Monday night. + * Maybe need rooms on Tuesday for a SIG to say they want a bit of time to meet + * Maintainer track CFP still TBD + * Planning for now will still be part of this meeting until we eventually need to meet separately. + * Other/Discussion: + * N/A +* Mentoring: + * Meet Our Contributors [Alison] + * Didn’t go ahead; event was missing on calendar and other issues like rescheduling the mentoring meeting so it doesn't conflict with MOC. + * Need to sort out streamer for this or streamyard (aka who can host July?) + * At this point, for streamyard, we're going to get there. Bob's looking up how to make this happen for a shared account. (Also working on 1Password - the OSS version) + * Issue for July: First Monday is July 5, which is problematic for US folks. + * Need to explore the right day/time for July being different. + * Playground, gsoc, outreachy, LFX Mentorship Program [Ihor] + * N/A + * [New Contributor Workshop](https://docs.google.com/document/d/1XiXjDWCc087VKqX2b6LMGRnlaRyLYGh2-eWQQr6dAmc/edit#heading=h.vs8waxtx792q) [Alison] + * Updated the PR that was in motion :tada: Should be all squared away soon. Please review the PR if you're able/supposed to. + * Aiming to get all the bootstrap stuff done by end of the week + * Goal: Get Done by KubeCon NA, so October +* Community-management: + * [Need to Know Chairs/TLs email](https://docs.google.com/document/d/1cC799hHZpo8JJfwvUa94uiPfUpo17oTTJDFobxNLL7c/edit) [Bob/Alison] + * Drop an item in there if you need to +* Devstats [Lauri] + * Updated to support individual repos/SIGs stats! + * Pick dashboards we want to offer in a curated fashion to SIG/Subproject leads to embed in the contrib site (with interpretation info) +* Marketing [Matt/Kaslin] + * Discussion/Update + * Soon, there will be the ability to request tweets by opening an issue (which will do all the automation for the PR for you) + * Note that it will not support image embeds as that's a limitation of the tool. Ping contrib-comms manually still for those +* Contributor-documentation: + * Contributor Guide [Bob] + * No updates + * Developer Guide [Erik/Joel] + * No updates + * Contributor Site [Bob] + * No updates +* GitHub-management [Bob/Nikhita/Christoph]: + * Discussion/Update: + * The big thing is the migration to EasyCLA (to replace current CLA bot). CNCF is vetting the bot with a random examination of the contrib base, and also ensure all org members exist in all systems. + * Target (soft target): Week after code freeze (when fewest PRs to k8s/k8s). May punt. +* Slack-infra [Jeefy]: + * Discussion/Update + * The switch on for the official Slack pronoun field (yay!). Not as much flak/negativity this time around, so that's good. +* Any other notes? + * N/A + + +## May 26th Meeting + + + +* Host: Bob Killen +* Notetaker: Josh Berkus +* Attendees: + * Arsh Sharma + * Deb Giles + * Kaslin Fields +* Welcome and recurring business [Host] + * CoC [Host] + * New Contributor Intro here \o/ [Everyone] +* Events: + * Office hours [Jorge] + * Request for funding for streamyard opened + * They're trying to get us on an org account, but pricing is unreasonable + * Setup for shared account is in progress + * Cloudnative.TV folks will carry Office Hours + * [Community Meeting](https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k/edit#gid=932627810) [Laura] + * Still having calendar issues, Ggroup won't let us send invites + * Need to migrate group to k.io owned group + * Should we do an opt-in migration? Would remove inactive accounts + * Should we audit kdev members? Josh says "no". + * Alison hosted (thank you!); Laura needs to finalize the notes and post to the community + * Archive of the older notes complete + * Looking for the June host if anyone's interested + * Josh can host + * Contributor Summit(s) [Bob] + * Leads would like to host something + * Have not notified/solicited anyone yet because most companies have not changed their policy yet + * Probably hangout space + unconference sessions + * Would really like Hybrid + * Streaming + Interaction + * or streaming + chat? with dedicated facilitators + * Space requirements? + * 1 big welcome room/hangout space + * smaller unconference rooms -- maybe 4 total + * May release depending on prospective attendance + * Docs wants space on monday + * Social event? Folks are more interested in the social than they are in the sessions, but don't know what possibilities are until COVID restrictions change June 15. + * Monday night + * Won't have numbers until August + * Will ALSO do a virtual contributor celebration in December. + * Will give contributor awards there + * Did star charts there last year, CNCF shipped + * Shipping was a serious problem +* Mentoring: + * Meet Our Contributors [Paris] + * Still waiting for streamyard + * Playground, gsoc, outreachy, LFX Mentorship Program [Ihor] + * + * [New Contributor Workshop](https://docs.google.com/document/d/1XiXjDWCc087VKqX2b6LMGRnlaRyLYGh2-eWQQr6dAmc/edit#heading=h.vs8waxtx792q) [Alison] + * [Readme](https://github.com/ykakarap/test-infra/blob/approve2/prow/plugins/approve2/approvers/README.md) + * [POC PR](https://github.com/kubernetes/test-infra/pull/21398) + * Stub documents for NCW + * Complete by Kubecon LA? +* Devstats [Lauri] + * Progress on setting up pages for devstats +* Marketing [Matt/Kaslin] + * Working with cloudnative.tv folks + * Annual report summary is in progress + * Developer story blogs +* GitHub-management [Bob/Nikhita/Christoph]: + * Some changes to github, expect minimal impact for most contributors + * Ability to xref PRs between orgs is coming + * +* Slack-infra [Jeefy]: + * Has real pronoun fields now. Should we enable? + * Josh is ready to do so + * Also need to let people know to migrate their custom one +* Open Mic/Discussion + * [your name and topic here - should this be an issue against kubernetes/community?] + * LWKD migration just waiting on Bob/Nikhita availability + * will open a funding ticket for post-mailchimp + * Arsh to work on [golang issue](https://github.com/kubernetes/contributor-site/issues/93 ) + + +## May 19th Slack Meeting + + + +* Events: + * Contributor Summit(s) [Bob] + * Event is shaping up to be unconference event, follow up is to send an item to k-dev for commentary +* Mentoring: + * NCW content has been re-organized in two separate PRs + * k/community - [Contributor workshop update mentoring information](https://github.com/kubernetes/community/pull/5775) + * k/contributor-site - [Stub Worksho](https://github.com/kubernetes/contributor-site/pull/220) +* GitHub-management [Bob/Nikhita/Christoph]: + * Branch rename updates: + * [k/website is moving forward with branch rename](https://github.com/kubernetes/website/issues/21749#issuecomment-841722918) + * Prow (as of 2 months ago) will not retrigger presubmits when a branch is renamed + * Approve Plugin rewrite + * Significant progress has been made + * [Readme](https://github.com/ykakarap/test-infra/blob/approve2/prow/plugins/approve2/approvers/README.md) + * [POC PR](https://github.com/kubernetes/test-infra/pull/21398) + * “Undocumented” orgs + * There are a few orgs that don’t follow our regular pattern of managing orgs (k, k-sigs etc), but are used for specific purposes and these should be documented + * [Kubernetes-purgatory](https://github.com/kubernetes-purgatory) - Used by GitHub admins to transfer repos into the project. + * [kubernetes-nightly](https://github.com/kubernetes-nightly) - Not owned by GitHub admins, but should be (sttts is the current owner), the org is used for producing nightly snapshots +* Slack-infra []: + * Open question regarding Private slack channels, should they be publicly documented? There are previous issues discussing creation of specific ones, but there is no current (public) index. + + +## May 12th Meeting + + + +* Host: Alison +* Notetaker: +* Attendees: + * Arsh Sharma + * Arnaud Meukam + * Joel Barker + * Sahdev Zala + * Christoph Blecker + * Bob Killen + * Nabarun Pal + * Laura Santamaria (late) +* Welcome and recurring business [Host] + * CoC [Host] + * New Contributor Intro here \o/ [Everyone] +* Events: + * Office hours + * Need to open a funding ticket for streamyard + * Establish the users for streamyard + * Community Meeting [Laura] + * Alison will host on May 20th (thanks!) + * Workaround for calendar invite problem is to send an ICS out as an attachment + * Laura will sync with Alison afterward + * Contributor Summit(s) [Bob] + * Following up with previous discussion with leads + * More or less in agreement with hosting in person but will be very loose unconference style + * There was support for hybrid, have to coordinate with deb + * Confirming those details in tomorrow's leads meeting + * Committing to virtual event as well +* Mentoring: + * Meet Our Contributors [Alison] + * Did not do it this month as it clashed with KubeCon + * Will pick up next month with the first Monday of the month + * Need to wrangle panelists + * Reach out to upstream marketing + * Reach out to sigs and advertise focused contributing for specific SIGs e.g. the SIG CLI MoC, SIG Network MoC etc. + * Playground, gsoc, outreachy, LFX Mentorship Program + * Need to follow up with CNCF on creating a central pool of proposals for any program + * [New Contributor Workshop](https://docs.google.com/document/d/1XiXjDWCc087VKqX2b6LMGRnlaRyLYGh2-eWQQr6dAmc/edit#heading=h.vs8waxtx792q) [Alison] + * Updated guides + * [Contributor Workshop Update PR](https://github.com/kubernetes/community/pull/5775) + * [Contributor Site Workshop PR](https://github.com/kubernetes/contributor-site/pull/220) + * CTA contribex mailing list for friday +* Community-management: + * [Need to Know Chairs/TLs email](https://docs.google.com/document/d/1cC799hHZpo8JJfwvUa94uiPfUpo17oTTJDFobxNLL7c/edit) [Bob/Alison] +* Marketing [Matt/Kaslin] + * Multiple stories in flight + * SIG Usability + * Intro to user stories + * Chris’s story +* Contributor-documentation: + * Developer Guide audit almost complete, only one remaining SIG + + +## April 28th Meeting + + + +* Host: Bob +* Notetaker: Chris Short +* Attendees: + * Chris Short + * Bob Killen + * Alison Dowdney + * Josh Berkus + * Carlos Panato + * Kunal Kushwaha + * Christoph Blecker + * Deb Giles + * Ihor Dvoretskyi + * Josh Berkus + * Jason DeTiberus + * Kaslin Fields + * Rodolfo Martínez + * Madhav Jivrajani + * Peeyush Gupta + * Matt Broberg +* Contributor Summit + * Space Monday October 11th/12th + * We should do something but probably scaled back and smaller than normal + * Room capacities are currently limited to 25% which is subject to change + * Christoph: Concerns about exclusivity especially if we breakout into sigs + * Suggests talking with Chairs/TLs + * Corporate policy will dictate people's travel plans + * Bob: Survey again for potential attendees + * Deb: Contributor celebration could be a mask off event so CNCF is still figuring out logistics + * Matt: The online experience last year was good; but we have to consider how those left out might feel + * Kaslin: Something that involves everyone but can be done remotely/virtually as well + * Alison: Cookie decorating + * Josh: Make space for teams to work together on-site + * Jason: If you're the only remote person in a meeting there's a disconnect + * Matt: Someone curating events on behalf of virtual attendees + * Deb: We have space to do what we like, but we need to know some requirements in the next few weeks + * A/V will be improved due to the hybrid experience + * Someone to MC/move about with mic + * Christoph: What are the timelines? + * Deb: Will provide timelines in the next week or so + * **Space decisions need to be made by end of May** + * Virtual celebration + * Similar to what we did last year with less Discord rooms + * Took about a month of prep + * TODO: + * Survey community + * Determine limitations + * Determine what they'd like to see + * Josh will help with survey + * Discuss at next SIG/TLs meeting +* Welcome and recurring business [Host] + * CoC [Host] + * New Contributor Intro here \o/ [Everyone] +* Events: + * Office hours [Jorge] + * [Community Meeting](https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k/edit#gid=932627810) [Laura] + * The Community Meeting went well, folks participated and we filled the 30min time slot. + * Calendar event will be an issue till we mgirate k-dev and others to use a gsuite managed mailing list. +* Mentoring: + * Meet Our Contributors [Paris] + * AI: Update Meet our Contributors page in k/community + * Playground, gsoc, outreachy, LFX Mentorship Program [Ihor] + * [GSoC] Mentors must select mentees by next Monday + * [LFX] Summer Cycle starting up + * Setup a list or location where mentor projects can be suggested agnostic of whichever mentor program would use them + * [New Contributor Workshop](https://docs.google.com/document/d/1XiXjDWCc087VKqX2b6LMGRnlaRyLYGh2-eWQQr6dAmc/edit#heading=h.vs8waxtx792q) [Alison] +* Marketing [Matt/Kaslin] + * Ready to publish to k8s.dev blog with personal narratives focused on contribution + * To confirm: Bob do you like that scope? Can I [Matt] document it in the repo? + * Go live on the .dev domain? Yes, sayeth the Bob. + * Please share your stories with us!!! + * [Kunal] Almost done with the blog on SIG-Usability. Got proofread by Jason. Should be out this week (before KubeCon as that’s what the blog consists of). + * Plans on doing a Contribex blog looking for folks to speak with +* GitHub-management [Bob/Nikhita/Christoph]: + * GitHub Forms overview (in beta) could be incredibly helpful + * If involved in a subproject that's interested let GitHub Admins know +* Slack-infra [Jeefy]: + * Slack Word Moderator has been deployed \o/ + + +## April 14th Meeting + + + +* Host: Alison Dowdney +* Notetaker: +* Attendees: + * Marky Jackson + * Alison Dowdney + * Laura Santamaria + * Bob + * Eddie Zaneski + * Joel Barker + * Josh Berkus + * Sandhya Dalavi + * Matthew Broberg + * Sladyn Nunes + * Madhav Jivrajani + * Sahdev Zala +* Welcome and recurring business [Host] + * CoC [Host] + * New Contributor Intro here \o/ [Everyone] +* Events: + * Office hours [Jorge] + * need to ping Jorge + * POP and Rawkode be taking over? + * Need to request a streamyard account + * [Community Meeting](https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k/edit#gid=932627810) [Laura] + * Updated our hosting guide for the community meeting: [https://docs.google.com/document/d/1g7fR5cvCGFq15SJ4iQMclbj0QIeREKu_QP8ftnSaJ4o/edit?usp=sharing](https://docs.google.com/document/d/1g7fR5cvCGFq15SJ4iQMclbj0QIeREKu_QP8ftnSaJ4o/edit?usp=sharing) + * Need to update the calendar + * Going to do the 4th Thursday this month (because we didn't realize the 3rd one is tomorrow…) + * Joel and Josh volunteered to help moderate Zoom next week while Laura hosts + * Laura tracking down other people to help keep conversations moving +* Mentoring: + * Meet Our Contributors [Paris] + * Need to update calendar event + * Alison to host + * Playground, gsoc, outreachy, LFX Mentorship Program [Ihor] + * outreachy - we only had one team come forward with a project + * project was for separate cncf project + * outreachy mentors collectively decided not to approve it + * We have one credit that we are returning to the outreachy fund + * We could use some new people in the outreachy mentoring team + * + * [New Contributor Workshop](https://docs.google.com/document/d/1XiXjDWCc087VKqX2b6LMGRnlaRyLYGh2-eWQQr6dAmc/edit#heading=h.vs8waxtx792q) [Alison] + * Was supposed to move meeting to this week, + * Meeting next week will clash with MOC + * Calendars +* Community-management: + * [Need to Know Chairs/TLs email](https://docs.google.com/document/d/1cC799hHZpo8JJfwvUa94uiPfUpo17oTTJDFobxNLL7c/edit) [Bob/Alison] + * Not enough updates to send one out + * APAC coordinator update [who dis?]: +* Devstats [Lauri] + * Adding a bunch of boards to be useful + * Delayed due to issues + * might pick back up next week +* Marketing [Matt/Kaslin] + * Adding new regulars to our Slack group + * We have 6 new people! + * Handful of contributor story articles in progress (ex: [https://github.com/kubernetes/contributor-site/pull/205](https://github.com/kubernetes/contributor-site/pull/205)) + * Building a different narrative form .io, .io user focused, .dev is contributor focused + * We’d love to help you write one too! DM or @contributor-comms in Slack + * Recorded a talk for Kubecon EU! +* Contributor-documentation: + * Contributor Guide [Bob/Jorge] + * Developer Guide [Erik/Joel] + * Contributor Site [Bob/Jorge] +* GitHub-management [Bob/Nikhita/Christoph]: + * nw +* Slack-infra [Jorge/Jeefy]: + * new bot released, +* Open Mic/Discussion + * [Need to assign follow up actions to to subproject prioritization](https://docs.google.com/spreadsheets/d/1glhdFcUdqYAByW16hujxK1X_0k9mt_nrkCO4POeDNbs/edit) + * Sent out priorities with staffing level + * If folks can follow up with people who are more familiar with subprojects + * Ask people to add their GitHub handles if they have one so we can follow up in a GitHub issue for tracking + * [https://github.com/kubernetes/community](https://github.com/kubernetes/community) - new contributors, find the sig you’re interested in, sign up for their mailing list, sig meetings are a good point of call for more questions about how to contribute to a particular sig + + +## March 31 Meeting + + + +* Host: Alison +* Notetaker: +* Attendees: + * Joel Barker + * Ihor Dvoretskyi + * Marky Jackson + * Kendall Nelson + * Bob Killen +* Welcome and recurring business [Host] + * CoC [Host] + * New Contributor Intro here \o/ [Everyone] +* Events: + * [Community Meeting](https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k/edit#gid=932627810) [Laura] + * (Laura: I can't make it today, so here are some notes) + * First-time reminder email going out tomorrow for the community meeting topic submissions + * Paris suggested some changes for the agenda to ensure folks see the change (embed the table, etc.). Need to do that before the reminder email goes out + * Still needed: Update the host instructions to match the new meeting layout. + * Potentially reach out to the marketing team to use slack bot to push announcements to channels. + * Potentially go through KEPs to raise items that require more general discussion about a week before the event + * Other/Discussion: +* Mentoring: + * Meet Our Contributors [Paris] + * Scheduled for next week Monday at 8am? + * AI: Alison and Bob to test stream setup + * Playground, gsoc, outreachy, LFX Mentorship Program [Ihor] + * [New Contributor Workshop](https://docs.google.com/document/d/1XiXjDWCc087VKqX2b6LMGRnlaRyLYGh2-eWQQr6dAmc/edit#heading=h.vs8waxtx792q) [Alison] + * Switching to more of a focus on written content, as it has a better chance of getting done as well as easier to assign work. + * AI: remove evening APAC Mentoring meeting + * Other: Looking for folks to help with CODE2040 and other partnerships that will help us with diversity, specifically that back up our BLM statements and our values [Paris] + * Ideally, training on Kubernetes (it’s important that folks are users or around the space) and ultimately a new contributor workshop) + * Conversion to slides is secondary to getting the content down. + * Who else is involved with Kubernetes Community Days in Africa? + * Targeted outreach groups - Contributor Training, Kubernetes hands on training +* Community-management: + * [Need to Know Chairs/TLs email](https://docs.google.com/document/d/1cC799hHZpo8JJfwvUa94uiPfUpo17oTTJDFobxNLL7c/edit) [Bob/Alison] +* Devstats [Bob] + * [Dashboards in the process of being updated to support per-repo and per-sig stats](https://github.com/cncf/devstats/issues/289). +* Marketing [Joel] + * Few blogs moving forward + * Survey + * Should we close the survey - ask Matt, or Bob + * Surveys now closed +* Contributor-documentation: + * Contributor Guide [Bob/Jorge] + * No Season of Docs this time around due to complications with the CNCF and allocations and projects + * Developer Guide [Erik/Joel] + * Annual report pushing sigs to do audit, more complete list of what needs to be updated in the developer guide + * Most sigs have been proactive and pring in changes where needed + * Issue tracking developer guide audit : [https://github.com/kubernetes/community/issues/5229](https://github.com/kubernetes/community/issues/5229) + * Contributor Site [Bob/Jorge] + * [New community section added](http://k8s.dev/community) + * Added values, mentoring +* GitHub-management [Bob/Nikhita/Christoph]: + * GitHub is rolling out [new Issue form templates](https://gh-community.github.io/issue-template-feedback/welcome/#how-do-i-get-started) (beta), looking to test with the k/org repo. +* Slack-infra [Jorge/Jeefy]: + * Discussion/Update + * New bot being rolled out that can privately message on keywords +* Open Mic/Discussion + * [Annual Report, please get reviews in by EoD](https://github.com/kubernetes/community/pull/5573) [Bob] + * [Should we add LF unconscious bias training as an Org member requirement?](https://training.linuxfoundation.org/training/inclusive-speaker-orientation/) [Bob] + * Could potentially restrict potential org members It could discourage URMs from applying. + * We do not want to create obstructions for other people + * There isn’t a good way of enforcing it at levels at reviewer/approver level. + * Add it in as optional for org member applications + * Add a survey question as a follow-up in the annual survey to ask followup and their thoughts on it. + * Optional for now, and highly encourage folks to take the training + * Look into getting aggregate information from those that have contributed to the project from the LF + + +## March 24th Slack Meeting + + + +* Events: + * [Community Meeting](https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k/edit#gid=932627810) [Laura] + * Email sent to k-dev announcing the new experimental community meeting format with a sheet to enter topics into. No topics added yet; planning on dropping a reminder at the top of the month +* Mentoring: + * Meet Our Contributors [Paris] + * Spinning back up, now scheduled for 8:30AM PT on the first Monday of each month. +* Community-management: + * [Several people have started to be onboarded for the areas highlighted in the program initiative and spreadsheet](https://docs.google.com/spreadsheets/d/1glhdFcUdqYAByW16hujxK1X_0k9mt_nrkCO4POeDNbs/edit#gid=0) +* Marketing [Matt/Kaslin] + * The Slack messages and additional marketing helped get an additional 100+ survey respondents + * Quite a few stories in flight +* GitHub-management [Bob/Nikhita/Christoph]: + * [Looking into setting up ArtifactHub orgs for kubernetes/kubernetes-sigs](https://github.com/kubernetes/org/issues/2587) + * [Discussing the removal of the label kind/design](https://github.com/kubernetes/community/issues/5641) + * Some repos do make use of the label despite the overlap with others + * Currently leaning towards removing in kubernetes/kubernetes repo only +* Slack-infra [Jeefy]: + * Working through some issues on getting the slack moderator word list in place. + + +## March 17th Weekly Meeting + + + +* Host: Bob Killen +* Notetaker: Laura Santamaria and whoever else wants to join in :) +* Attendees: + * Alex Lovell-Troy + * Alison Dowdney + * Bob Killen + * Chris Short + * Eddie Zaneski + * Josh Berkus + * Lau + * Laura Santamaria + * Matthew Broberg + * Paris + * Rajula + * Tim Pepper +* Welcome and recurring business [Host] + * CoC [Host] + * New Contributor Intro here \o/ [Everyone] + * We all did intros :D +* Events: + * Office hours [Jorge] + * It happened today! No details, but it happened! + * People were asking questions and it was engaging. We actually had *too* many volunteers for once + * [Community Meeting](https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k/edit#gid=932627810) [Laura] + * Email draft done and ready to go to review, along with a Google sheet + * WIll try to rekick in April. + * Will need to ensure there's a host and moderator each month. +* Mentoring: + * Meet Our Contributors [Paris] + * Hasn't really happened in a bit. Will talk more about the contributor sheet and this topic later. + * Doodle is going out later today. Several folks said they can host, so that will be kicking up again. + * Playground, gsoc, outreachy, LFX Mentorship Program [Ihor] + * There was a call for mentors and projects. Lots of applicants, but no specific projects or mentors. Very few mentors with well-scoped projects in general in the past, so same problem here. + * For the most part, we're reaching out to other groups and asking for bandwidth. The bandwidth problem has been a big one this past year. + * Next mentoring meeting is on Monday 5p UTC/11a ET/8a PT + * Mentoring PRs are coming in for group mentoring for reviewer pool + * [New Contributor Workshop](https://docs.google.com/document/d/1XiXjDWCc087VKqX2b6LMGRnlaRyLYGh2-eWQQr6dAmc/edit#heading=h.vs8waxtx792q) [Alison] + * Will be one of the big focuses for the upcoming mentoring meeting + * Lots of stuff spec'd out (slides and presentations), but need to decide what stuff needs to be recorded. Some of the smaller bite-sized stuff can be written tutorials right now. Just need to figure out the logistics. + * Lack of people able to record and produce content for workshops. + * See [https://github.com/kubernetes/community/labels/area%2Fnew-contributor-track](https://github.com/kubernetes/community/labels/area%2Fnew-contributor-track) + * Do we need a producer to track people down? Potentially. Do people need help editing? Potentially. Review at next mentoring meeting (see note above about timeframe for that meeting) +* Community-management: + * [Need to Know Chairs/TLs email](https://docs.google.com/document/d/1cC799hHZpo8JJfwvUa94uiPfUpo17oTTJDFobxNLL7c/edit) [Bob/Alison] + * No immediate things that need to go in there outside of the contributor survey and annual reports + * APAC coordinator update [who dis?]: + * No update. Lost bandwidth; going async for now +* Devstats [Lauri] + * https://k8s.devstats.cncf.io/ + * Very soon, devstats will be able to go down to per repo and per SIG. Update coming. See [https://github.com/cncf/devstats/issues/289](https://github.com/cncf/devstats/issues/289) (should land in next week or two) + * Want to add a section where we can add dashboards with our annotations on how to interpret data and make it useful. Brief WIP: [https://deploy-preview-194--kubernetes-contributor.netlify.app/resources/dashboards/](https://deploy-preview-194--kubernetes-contributor.netlify.app/resources/dashboards/) (embed in iframe) +* Marketing [Matt/Kaslin] + * (Goal is no-code message) Message of low/no code is helping with recruits! 2 new consistent members. 🎉 + * Helping push the Contributor Survey (Q: How many submissions do we have?) + * [https://groups.google.com/g/kubernetes-dev/c/S--Ia5Pjmmg?pli=1](https://groups.google.com/g/kubernetes-dev/c/S--Ia5Pjmmg?pli=1) + * [https://twitter.com/K8sContributors/status/1371535294227390464](https://twitter.com/K8sContributors/status/1371535294227390464) + * Results: as of yesterday: 55 respondees… One way to get more respondents is getting cofounders of the project/people with decent followings to post about it. But the hard thing is the non-contributors answering. + * Opportunity to increase reach / fills: + * Reinforce the impact + * Reinforce that “this looks familiar, but it’s incredibly important to us” + * 130 response min because 10% of org stat + * Definitely prefer quality over quantity. + * Going to push to various Slack channels tomorrow (draft message going up today-ish) + * Ideas welcome! + * Articles in progress updated here: [https://github.com/orgs/kubernetes/projects/41](https://github.com/orgs/kubernetes/projects/41) + * Series on contributor contribution in progress for k8s.dev (target KubeCon EU) + * PR inbound on Michelle (https://twitter.com/michellenoorali) + * Reach out with any more ideas :) + * Archiving 1y+ umbrella issues in favor of systems as part of the group + * Document programs that we have in GitHub +* Contributor-documentation: + * Contributor Guide [Bob/Jorge] + * No updates + * Developer Guide [Erik/Joel] + * Audit is still progressing + * If you happen to be involved in any other SIGs, please remind for reviewing outstanding issues to call out out-of-date or missing docs + * Contributor Site [Bob/Jorge] + * Got moved over to the Kubernetes org! + * There is interest in localizing that content, and that will start up soon-ish (probably) +* GitHub-management [Bob/Nikhita/Christoph]: + * Discussion/Update: + * Only big thing is we are really in progress with renaming repos. Comms about k8s.dev rename. Please refer people to k8s.dev/rename for more info +* Slack-infra [Jorge/Jeefy]: + * Discussion/Update + * No real update +* Open Mic/Discussion + * [your name and topic here - should this be an issue against kubernetes/community?] + * [eddiezane] Code freeze notifications on PR? + * There have been a bunch of new contributors asking about getting merged during code freeze. What about more notifications? + * Example: [https://github.com/kubernetes/kubernetes/pull/99892#issuecomment-800862933](https://github.com/kubernetes/kubernetes/pull/99892#issuecomment-800862933) + * Lots of people don't seem to read the bot notifications. + * We should look at our other bot messages, but something does seem to be needed. + * Release schedule is at k8s.dev/release. Maybe a banner would be helpful when a freeze is in effect? + * [Bob] Prioritization spreadsheet + * [https://docs.google.com/spreadsheets/d/1glhdFcUdqYAByW16hujxK1X_0k9mt_nrkCO4POeDNbs/edit#gid=0](https://docs.google.com/spreadsheets/d/1glhdFcUdqYAByW16hujxK1X_0k9mt_nrkCO4POeDNbs/edit#gid=0) + * There's been some holes that have come up over the past year for various reasons. + * Automation would be really helpful if possible over trying to find more/new people. + + +## March 3rd Weekly Meeting + + + +* Host: Alison Dowdney +* Notetaker: Bob Killen +* Attendees: + * Kendall Nelson + * Bob Killen + * Nikhita Raghunath + * Matt Broberg + * Alison Dowdney + * Christoph Blecker + * Ihor Dvoretskyi +* Welcome and recurring business [Host] + * CoC [Host] +* Events: + * [Community Meeting](https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k/edit#gid=932627810) [Laura] + * Going to try a discussion centric meeting +* Mentoring: + * Playground, gsoc, outreachy, LFX Mentorship Program [Ihor] + * Call for outreachy interns due the 7th of March + * There's interest, but no one has proposed a project yet that they want to push forward. + * [New Contributor Workshop](https://docs.google.com/document/d/1XiXjDWCc087VKqX2b6LMGRnlaRyLYGh2-eWQQr6dAmc/edit#heading=h.vs8waxtx792q) [Alison] + * Plan to add a calendar event for the meeting +* Community-management: + * [Need to Know Chairs/TLs email](https://docs.google.com/document/d/1cC799hHZpo8JJfwvUa94uiPfUpo17oTTJDFobxNLL7c/edit) [Bob/Alison] + * APAC coordinator update [nikhita]: + * No updates +* Devstats [Lauri] + * [bob] going to open an issue with asks + * Filter by repo vs repo_group + * Filter by labels + * Filter by Organization (OSPO Hat on) +* Marketing [Matt/Kaslin] + * Great discussion around PSP articles -- next steps Tabitha/Ian working on an article / [Blog on PSP deprecation by kaslin · Pull Request #26279 · kubernetes/website](https://github.com/kubernetes/website/pull/26279) + * Other articles in progress: [https://docs.google.com/document/d/1KDoqbw2A6W7rLSbIRuOlqH8gkoOnp2IHHuV9KyJDD2c/edit#](https://docs.google.com/document/d/1KDoqbw2A6W7rLSbIRuOlqH8gkoOnp2IHHuV9KyJDD2c/edit#) +* Contributor-documentation: + * Contributor Guide [Bob/Jorge] + * Developer Guide [Erik/Joel] + * AI: Follow up pinging people to complete their audit + * Contributor Site [Bob/Jorge] + * Plan to migrate it to the kubernetes org within the next 2 weeks +* GitHub-management [Bob/Nikhita/Christoph]: + * Lots of discussion on the master -> main branch rename + * Prow recently updated the trigger plugin which could be turned off on a per repo basis to help mitigate webhook storm +* Slack-infra [Jorge/Jeefy]: + * [nikhita] will follow up with jeff and bob to deploy the slack-moderator-words bot +* Open Mic/Discussion + * [Annual Report](https://hackmd.io/9jRC1zNfQDaN8wAv_nzb5Q) + * Lack of ContribEx bandwidth to keep all programs going + * Need to evaluate projects with must/should etc + * Need help by trusted contributors to drive the critical things (e.g. zoom -> YT automation) + * Asynchronous call to action, google doc with whats the scenario, whats we plan to do, and how to feedback + * AI: Send a spreadsheet with projects and initiatives to prioritize. + + +## February 24th Slack Weekly Meeting + + + +* Events: + * [Community Meeting](https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k/edit#gid=932627810) [Laura] + * Test discussion based community meeting with general call out for items. +* Mentoring: + * Playground, gsoc, outreachy, LFX Mentorship Program [Ihor] + * **Call for outreachy interns due Monday March 1st.** + * Reach out to Nikhita or Josh with ideas. +* Community-management: + * [Need to Know Chairs/TLs email](https://docs.google.com/document/d/1cC799hHZpo8JJfwvUa94uiPfUpo17oTTJDFobxNLL7c/edit) [Bob/Alison] +* Marketing [Matt/Kaslin] + * Contributor Comms engaged with notification for [Annual Contributor Survey](https://www.surveymonkey.com/r/k8scommsurvey2021). + * Initial announcement was to be sent from [community@kubenretes.io](mailto:community@kubenretes.io) however a group cannot cc another group +* GitHub-management [Bob/Nikhita/Christoph]: + * [Update k/k issue template for kind/feature](https://github.com/kubernetes/kubernetes/pull/98867) based on feedback that feature issues in k/k are rarely triaged or implemented. Please provide feedback on the issue itself. + * [Add functionality for prow to respond to issues by label](https://github.com/kubernetes/test-infra/pull/20868). This could enable auto-closing of issues that are tagged by members with kind/support. +* Slack-infra: + * Add functionality to auto-respond to users when certain words are said + * [https://github.com/kubernetes/k8s.io/pull/1696](https://github.com/kubernetes/k8s.io/pull/1696) + * [https://github.com/kubernetes-sigs/slack-infra/pull/41](https://github.com/kubernetes-sigs/slack-infra/pull/41) + * [https://github.com/kubernetes/k8s.io/pull/1719](https://github.com/kubernetes/k8s.io/pull/1719) +* Open Mic/Discussion + * [2021 Audit of ContribEx owners, subprojects, github groups etc.](https://github.com/kubernetes/community/issues/5444) + + +## February 17th Weekly Meeting + + + +* Host: Alison +* Notetaker: Bob Killen +* Attendees: + * Joel Barker + * Bob Killen + * Alison Dowdney + * Jason Morgan + * Sahdev Zala + * Ihor Dvoretskyi +* Welcome and recurring business [Host] + * CoC [Host] + * New Contributor Intro here \o/ [Everyone] +* Events: + * Office hours [Jorge] + * Jorge has been getting Pop and Rawkode involved to help host + * [Community Meeting](https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k/edit#gid=932627810) [Laura] + * Discussed at chair and TL meeting, still sorta TBD +* Mentoring: + * Playground, gsoc, outreachy, LFX Mentorship Program [Ihor] + * LFX Mentoring Programs are in the stage of selecting their mentees + * Make your selection before the 26th + * CNCF participating in GSoC, final confirmation from Google is expected after the 19th + * [New Contributor Workshop](https://docs.google.com/document/d/1XiXjDWCc087VKqX2b6LMGRnlaRyLYGh2-eWQQr6dAmc/edit#heading=h.vs8waxtx792q) [Alison] + * Update on scheduling meeting - [doodle](https://doodle.com/poll/zsmtkgit2capbq7v) + * AI: Reach out to former active mentoring contributors about time for the meeting. +* Community-management: + * [Need to Know Chairs/TLs email](https://docs.google.com/document/d/1cC799hHZpo8JJfwvUa94uiPfUpo17oTTJDFobxNLL7c/edit) [Bob/Alison] + * [Annual report](https://github.com/kubernetes/community/blob/master/committee-steering/governance/annual-reports.md) + * Need to open draft PR ideally by the end of the month and complete as a group before April. + * Annual survey status + * Currently locked out of survey account, Amye from CNCF will fix account +* Marketing [Chris] + * PSP blog post is in flight, now coordinating with SIG Auth + * Further automation in progress for twitter feeds + * Looking for content, people to interview. + * Reach out to @contributor-comms in slack or open an issue in k/community +* Contributor-documentation: + * Contributor Guide [Bob/Jorge] + * Developer Guide [Erik/Joel] + * Developer Guide Audit + * SIGs are actively working on their audit, aiming to complete by 1.21 release +* GitHub-management [Bob/Nikhita/Christoph]: + * [nikhita] Updates to enhancement issue template + automation. Needs review: + * Issue template - [https://github.com/kubernetes/kubernetes/pull/98867](https://github.com/kubernetes/kubernetes/pull/98867) + * Automation - [https://github.com/kubernetes/test-infra/pull/20868](https://github.com/kubernetes/test-infra/pull/20868) +* Slack-infra [Jorge/Jeefy]: + * [nikhita] Need review on slack bot that will display a message to the author if they use non-inclusive language + * PR - [https://github.com/kubernetes-sigs/slack-infra/pull/41](https://github.com/kubernetes-sigs/slack-infra/pull/41) + * Sent an [email](https://groups.google.com/g/kubernetes-wg-naming/c/d5JyKPUXA0g) to WG Naming for review too +* Open Mic/Discussion + * [your name and topic here - should this be an issue against kubernetes/community?] + * [sahdev] Issue with people claiming good first issue issues after they’ve already been claimed + * Example: [https://github.com/kubernetes/community/issues/5451](https://github.com/kubernetes/community/issues/5451) + * AI: Add item to triage guidelines, expect a draft PR open within 2 weeks before + + +## February 10th Slack Meeting + + + +* Events: + * [Community Meeting](https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k/edit#gid=932627810) [Laura] + * [Meeting comms sheet from polling chair/TL](https://docs.google.com/spreadsheets/d/1UP4zOZOFxiwE5J98y0f-LorrPztadPvg-wfYrS0DjRA/edit#gid=0) + * Remove SIG updates and move to discussions / demos etc +* Marketing + * Contributor Profiles + * Need to reach out to Michelle Noorali, and do a profile of her and her GB experiences +* Annual Contributor Survey + * Survey is largely done - should be ready to send out next week + + +## February 3rd Weekly Meeting + +**HELP WANTED:** Help with inactive OWNER PRs. See [parent inactive owner issue](https://github.com/kubernetes/org/issues/2456) for details and examples of what it looks like. + + + +* Host: Bob Killen +* Notetaker: Chris Short +* Attendees: + * Chris Short + * Matt Broberg + * Joel Barker + * Sahdev Zala +* Welcome and recurring business [Host] + * CoC [Host] + * New Contributor Intro here \o/ [Everyone] +* Events: + * Office hours [Jorge] + * [Community Meeting](https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k/edit#gid=932627810) [Laura - Can't make it in person today due to double-booked meetings] + * Opened [https://github.com/kubernetes/community/issues/5462](https://github.com/kubernetes/community/issues/5462) for more discussion. If I missed any context from last week's meeting, please feel free to correct me. + * Also reached out to Paris separately re: SIG reporting updates as there's a discussion around changing the SIG reporting structure. Summarized the notes in [https://github.com/kubernetes/community/issues/5462#issuecomment-772656560](https://github.com/kubernetes/community/issues/5462#issuecomment-772656560), but basically steering is looking to increase async comms and reduce meeting load. There's already a lot of duplicated reporting with the annual report, kubecon updates, and weekly/biweekly/triweekly SIG meetings. + * February community meeting: Should we move forward with the prior format? Current schedule is the working/user groups, and I was going to add in committees and SIG Arch from January's schedule if we're moving forward. + * Other/Discussion: +* Mentoring: + * Meet Our Contributors [Paris] + * Playground, gsoc, outreachy, LFX Mentorship Program [Ihor] + * [LFX Mentee program launched](https://www.cncf.io/blog/2021/02/03/cncf-lfx-projects-are-open-for-spring-term-2021-apply-now-for-a-mentorship-opportunity/) + * Season of Docs starting soon? ContribEx will want to participate + * [New Contributor Workshop](https://docs.google.com/document/d/1XiXjDWCc087VKqX2b6LMGRnlaRyLYGh2-eWQQr6dAmc/edit#heading=h.vs8waxtx792q) [Josh/Alison] + * New meeting [Doodle for EU/APAC friendly meeting](https://doodle.com/poll/zsmtkgit2capbq7v) +* Community-management: + * [Need to Know Chairs/TLs email](https://docs.google.com/document/d/1cC799hHZpo8JJfwvUa94uiPfUpo17oTTJDFobxNLL7c/edit) [Bob/Alison] + * Comms about change in annual reports due date, draft opened by March, completed by April + * APAC coordinator update [who dis?]: +* Devstats [Lauri] +* Marketing [Matt/Kaslin] + * PSP article waiting for review [https://github.com/kubernetes/website/pull/26279](https://github.com/kubernetes/website/pull/26279) + * Making progress on contributor stories! + * Chris Short on non-code contribution + * Matt Broberg on timeboxing contribution + * Peeyush Gupta on contributing across time zones + * Sladyn Nunes on learning new skills + * Kaslin TBD + * Need MAOR :) + * SIG Profiling? Can we bring that back? + * Right now: backburner idea -- we always offer it up to potential authors but it tends to fall behind and not get all the way to publication. + * Thoughts to improve? + * Not necessarily reach out to leads + * Cover more subgroups + * Consider focusing on the individual and their experience in the SIG to reduce the feedback churn (and sense that it has to be 100% representative of the experience) + * Some follow up ideas + * Disclaimer on articles -- personal experience and not representative of the entire community experience + * Long-living SIG Profiling Quotes document where we get a few quotes, then theme them into an article on Friday meetings (AI: Matt to bring this back to Marketing on Friday) +* Contributor-documentation: + * Contributor Guide [Bob/Alison] + * Developer Guide [Erik/Joel] + * Contributor Site [Bob/Alison] + * Going to move to kubernetes org from kubernetes-sigs +* GitHub-management [Bob/Nikhita/Christoph]: + * [GitHub default branch rename: master -> main](https://github.com/kubernetes/org/issues) + * Migrated k/org repo - migration did trigger rerunning of pre and postsubmits. +* Slack-infra [Jorge/Jeefy]: + * Discussion/Update +* Open Mic/Discussion + * [Bob] Alternate zoom/slack meetings + * [Bob] Annual Survey demographic data will not be asked. Should try and get the survey out ASAP. + * [your name and topic here - should this be an issue against kubernetes/community?] + + +## January 27th Weekly Meeting + +HELP WANTED: Help with inactive OWNER PRs. See [parent inactive owner issue](https://github.com/kubernetes/org/issues/2456) for details and examples of what it looks like. + + + +* Host: Bob Killen +* Notetaker: +* Attendees: + * Alison D + * Matt Broberg + * Kendall Nelson + * Rey Lejano + * Cody Crudgington +* Welcome and recurring business [Host] + * CoC [Host] + * New Contributor Intro here \o/ [Everyone] +* ContribEx Updates: + * Lazy consensus period over for Alison to become chair \o/ + * [Meeting looking to be moved 30min early](https://groups.google.com/g/kubernetes-sig-contribex/c/OYYklOzZemU/m/YC-MT5TmDgAJ)+1 +* Events: + * Office hours [Jorge] + * [Community Meeting](https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k/edit#gid=932627810) [Laura] + * SIGs schedule their own public sessions, getting updates from SIGs independently + * It was dropped as it’d be difficult for attendees + * Openstack approaches community meetings by letting folks record video updates, We could approach folks to record video updates every quarter and then compile them together + * + * Considering the “why” of the meeting + * A front door for new members (or campfire aspect of news) + * A ‘what’s new for current members’ + * Would we be able to keep the same vibe with a different medium + * Maybe podcast, maybe youtube + * Issue with the community meeting was there was no discussion + * Fixing calendar issue - port the mailing list to gsuite + * Is google groups adequate? A whole other can of worms + * TODO : Create a GitHub issue for further discussion + * + * Contributor Summit(s) [Bob] + * Potentially do something for Kubecon EU + * If we do something it will be separate from kubecon + * Other/Discussion: +* Mentoring: + * Meet Our Contributors [Paris] + * Still looking for folks to get involved with helping out, mailing list + * Playground, gsoc, outreachy, LFX Mentorship Program [Ihor] + * If you plan to be a mentor, the deadline is January 31 + * Info is in the cncf repo + * [New Contributor Workshop](https://docs.google.com/document/d/1XiXjDWCc087VKqX2b6LMGRnlaRyLYGh2-eWQQr6dAmc/edit#heading=h.vs8waxtx792q) [Josh] + * Progress has been made with making an interactive environment for build and test + * Progress is slow but steady + * Calendar Invite + * Josh to create doodle to find new eu friendly meeting time +* Community-management: + * [Need to Know Chairs/TLs email](https://docs.google.com/document/d/1cC799hHZpo8JJfwvUa94uiPfUpo17oTTJDFobxNLL7c/edit#heading=h.j2likm89by0n) [Bob/Jorge] + * Need to send this email out + * More folks need to see this and take a look + * APAC coordinator update [who dis?]: + * [Annual Contributor Survey](https://github.com/kubernetes/community/issues/5153) + * [Survey questions](https://docs.google.com/document/d/1IERzLwPBJkw5IYnolJ0UnS3ueWNEhePpoeRtTzIlrqs/edit) + * Demographic data is desired to help establish a baseline of contributor diversity. Questions have been sent to CoCC for comment. + * Questions have been locked in, except for the demographic ones + * Code of conduct committee are reviewing demographic questions +* Devstats [Lauri] +* Marketing [Matt/Kaslin] + * Content push right now --- asking anyone and everything to write up a few paragraphs on how they contribute to kubernetes + * Signed up: + * Chris Short on “non-code contribution” + * Matt Broberg on “lurker to contributor in 4 hours a week” + * Sladyn Nunes on joining marketing to learn a new skill + * Interested? + * Draft in progress on PSP deprecation - [https://github.com/kubernetes/website/issues/26202#issuecomment-766901866](https://github.com/kubernetes/website/issues/26202#issuecomment-766901866) + * Going to talk about the Community meeting next :) +* Contributor-documentation: + * Contributor Guide [Bob/Jorge] + * Developer Guide [Erik/Joel] + * Contributor Site [Bob/Jorge] +* GitHub-management [Bob/Nikhita/Christoph]: + * [Jan 2021 Inactive Member clean up](https://github.com/kubernetes/org/issues/2456) + * Removes 60~ people from the org + * HELP WANTED: Need assistance with follow up OWNER files clean up. + * Is there any Automation we would like around this? + * There is some automation we would like to do in the long term +* Slack-infra [Jorge/Jeefy]: + * Discussion/Update + * Finished renaming the kubernetes contributor channel + * Positive changes seen, most comments are on topic +* Open Mic/Discussion + * Slack “meeting” feedback [Bob] + * Positives, we were able to get responses from people in many different time zones + * Negatives: Slack threading made things hard to follow + * Needed to bound the conversation times more formally- conclude comments by X date/time + * Potentially create a separate channel for the meetings + * Alternating slack meetings with video meetings could be a good approach if we work out the technical issues + * Actual things that need to be decisions/discussions to be placed on a separate thread + * Decisions section of the notes + * Here are the decisions, send them out to the mailing list to get feedback + * Potential integration [https://fellow.app/blog/2020/effective-meetings-with-fellow-and-slack/](https://fellow.app/blog/2020/effective-meetings-with-fellow-and-slack/) + * Review 1.20 / 1.21 milestone [Bob] + * Managed to clear out a bunch of issues in 1.20 + * New Contributor Workshop to be the focus of the next release cycle + + +## January 20th Slack Weekly Meeting + +HELP WANTED: Paris is looking for someone to help host Meet Our Contributors in February. + + + +* Events: + * [Community Meeting](https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k/edit#gid=932627810) + * Cancelled January session. Calendar invites are broken for k-dev. + * AI: Laura to sync with steering on scheduling remainder of sessions for the year. +* Mentoring: + * Meet Our Contributors + * Paris is looking for someone to help host Meet Our Contributors in February. + * Playground, gsoc, outreachy, LFX Mentorship Program [Ihor] + * LFX mentoring starting for spring, due **Jan 31st.** + * [Open PR adding project idea in CNCF Mentoring Repo](https://github.com/cncf/mentoring/blob/master/lfx-mentorship/2021/01-Spring/project_ideas.md). +* Community-management: + * [Kubernetes-dev slack channel to be renamed kubernetes-contributors.](https://groups.google.com/g/kubernetes-dev/c/ShYNQY90k5c/m/JB1VPmbwDAAJ) + * APAC coordinator update: + * Have put a timebox on replies for APAC meet our contributors blog series. Plan to start adding them soon. +* Contributor-documentation: + * Contributor Site + * The contributor-site is going to be migrated from the kubernetes-sigs org to kubernetes. + * Should streamline localization and support other community groups looking to create documentation there directly. + * [Link to approved sign-off from SIG Arch](https://groups.google.com/g/kubernetes-sig-architecture/c/FYmPPdMNq8w/m/RIhCXA88DQAJ) +* Open Mic/Discussion + * Annual Contributor Survey + * Plan to add demographic questions to the annual contributor survey. + * should help us better establish a baseline of the current diversity and representation within our community. + * Demographic data will NOT be shared publicly and will be treated like PII. + * Aggregate or summary data will be made available assuming summary results cannot be linked back to an individual. + + +# January 14th APAC Biweekly Meeting + +[Peeyush] Cancelled as Holiday in India and lack of attendance + + +## January 13th Slack Weekly Meeting + +HELP WANTED: Paris is looking for someone to help host Meet Our Contributors in February. + + + +* Events: + * [Community Meeting](https://docs.google.com/spreadsheets/d/1adztrJ05mQ_cjatYSnvyiy85KjuI6-GuXsRsP-T2R3k/edit#gid=932627810) [Jorge] + * Laura going to start scheduling SIGs to meetings, but needs to sync with steering. +* Mentoring: + * Meet Our Contributors [Paris] + * Paris is looking for someone to help host MoC + * Josh and Bob are backups +* Marketing [Matt/Kaslin] + * Paris plans to open up some PRs with governance related tweets +* Contributor-documentation: + * Contributor Site [Bob/Jorge] + * Adding comms guidelines to docs portion of site: + * [k/contributor-site PR](https://github.com/kubernetes-sigs/contributor-site/pull/200) + * [k/community PR](https://github.com/kubernetes/community/pull/5397) + * Adding a top level [Community section](https://github.com/kubernetes-sigs/contributor-site/issues/201) to house community and governance related items such as the CoC and values. + * [Need to improve overall SEO and discoverability of the site](https://github.com/kubernetes-sigs/contributor-site/issues/202) +* GitHub-management [Bob/Nikhita/Christoph]: + * No action at this time, but need to monitor [GitHub’s migration path for existing ](https://github.com/github/renaming#creating-a-seamless-move-for-existing-repositories-)repositories master -> main +* Open Mic/Discussion + * Annual Survey + * [Tracking Issue](https://github.com/kubernetes/community/issues/5153) + * [Questions](https://docs.google.com/document/d/1IERzLwPBJkw5IYnolJ0UnS3ueWNEhePpoeRtTzIlrqs/edit) + * Questions are close to being finalized + * Marketing to help with messaging and broadcasting to all sig mailing lists. + * diff --git a/sig-docs/CONTRIBUTING.md b/sig-docs/CONTRIBUTING.md index e4f8b6bc..03ad059d 100644 --- a/sig-docs/CONTRIBUTING.md +++ b/sig-docs/CONTRIBUTING.md @@ -18,7 +18,7 @@ Before opening a pull request, contributors must sign the [CNCF Contributor Lice Contributors should be familiar with the following: - [kubernetes/website repo](https://github.com/kubernetes/website) -- [Reference docs repo](https://github.com/kubernetes-sigs/reference-docs)) +- [Reference docs repo](https://github.com/kubernetes-sigs/reference-docs) - [Hugo static site generator](https://gohugo.io/) - [Documentation content guide](https://kubernetes.io/docs/contribute/style/content-guide/) - [What's allowed](https://kubernetes.io/docs/contribute/style/content-guide/#what-s-allowed) @@ -40,4 +40,4 @@ Anyone can review pull requests and the review process is outlined in the ## Questions about contributing Feel free to ask any questions in the [#sig-docs](https://kubernetes.slack.com/messages/sig-docs) Slack channel or in a -[SIG Docs meeting](https://github.com/kubernetes/community/tree/master/sig-docs#meetings).
\ No newline at end of file +[SIG Docs meeting](https://github.com/kubernetes/community/tree/master/sig-docs#meetings). diff --git a/sig-docs/README.md b/sig-docs/README.md index 5b531788..1dc87aac 100644 --- a/sig-docs/README.md +++ b/sig-docs/README.md @@ -82,7 +82,7 @@ subprojects, and resolve cross-subproject technical issues and decisions. - [@kubernetes/sig-docs-pt-owners](https://github.com/orgs/kubernetes/teams/sig-docs-pt-owners) - Portuguese language content - [@kubernetes/sig-docs-uk-owners](https://github.com/orgs/kubernetes/teams/sig-docs-uk-owners) - Ukrainian language content - [@kubernetes/sig-docs-zh-owners](https://github.com/orgs/kubernetes/teams/sig-docs-zh-owners) - Chinese language content -- Steering Committee Liaison: Paris Pittman (**[@parispittman](https://github.com/parispittman)**) +- Steering Committee Liaison: Carlos Tadeu Panato Jr. (**[@cpanato](https://github.com/cpanato)**) ## Subprojects diff --git a/sig-instrumentation/README.md b/sig-instrumentation/README.md index 30ae9385..95f52ddb 100644 --- a/sig-instrumentation/README.md +++ b/sig-instrumentation/README.md @@ -24,7 +24,7 @@ The [charter](charter.md) defines the scope and governance of the Instrumentatio ### Chairs The Chairs of the SIG run operations and processes governing the SIG. -* Elana Hashman (**[@ehashman](https://github.com/ehashman)**), Red Hat +* Elana Hashman (**[@ehashman](https://github.com/ehashman)**), Apple * Han Kang (**[@logicalhan](https://github.com/logicalhan)**), Google ### Technical Leads @@ -98,6 +98,9 @@ Organization of SIG Instrumentation subprojects - **Owners:** - [kubernetes-sigs/logtools](https://github.com/kubernetes-sigs/logtools/blob/main/OWNERS) - [kubernetes/kubernetes/staging/src/k8s.io/component-base/logs](https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/component-base/logs/OWNERS) +### usage-metrics-collector +- **Owners:** + - [kubernetes-sigs/usage-metrics-collector](https://github.com/kubernetes-sigs/usage-metrics-collector/blob/main/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-instrumentation/archive/2022-kubelet-tracing.png b/sig-instrumentation/archive/2022-kubelet-tracing.png Binary files differnew file mode 100644 index 00000000..931c6d02 --- /dev/null +++ b/sig-instrumentation/archive/2022-kubelet-tracing.png diff --git a/sig-instrumentation/archive/meeting-notes-2022.md b/sig-instrumentation/archive/meeting-notes-2022.md new file mode 100644 index 00000000..9f9b8c13 --- /dev/null +++ b/sig-instrumentation/archive/meeting-notes-2022.md @@ -0,0 +1,304 @@ +## Triage (2022-12-29) + +Cancelled - winter holidays + + +## Agenda (2022-12-22) + +Cancelled - winter holidays + + +## [NEXT] Triage (2022-12-15) + + +## Agenda (2022-12-08): + +* Deep Dive Video is out on Youtube - +* [] - maintaining subprojects + status + * KSM: new contributors, improving; most active subproject w/3 active + approvers and 3 new active reviewers, lots of first-time contributors! + * Metrics-server: We have 2 active reviewers and 1 active approver, only one + approver. Doing the bare minimum + * Custom-metrics-apiserver: need to keep maintaining this. Damien only + approver, doesn’t have time, Olivier is working on it + * prometheus-metrics-adapter: should we consider archiving? There’s now a + good replacement, KEDA, with bigger scope + ([https://keda.sh/docs/1.4/scalers/prometheus/](https://keda.sh/docs/1.4/scalers/prometheus/)). + Hasn’t been well-maintained, project needs a rewrite because the codebase + is hard to understand, UX is suboptimal, debugging is very complex and + tedious. Maybe write a migration guide rather than cleaning up KSM. + * Can we consider adding people directly to subproject ownership in the new year? + * Don’t want to give a newbie maintainer status without mentorship + * Seems reasonable to add people as reviewers right away if requested; + approver is a higher bar + * Reviewer status gives you some feelings of ownership and + responsibility but doesn’t give any privileges above and beyond org + member. For people who are not yet org members, we can work with them. +* [yangjunmyfm192085] Ask the release plan of metrics-server + * I think We need to make a release plan for metrics-server v0.6.2 and v0.7.0 + * Marek didn’t have time for a while to cut releases. Damien should now have + permissions to cut the release, but going forward wants to find someone + else to do it. Was difficult to release because it had been 6+ months + between releases so bumping dependencies was tedious. We should be + releasing every month or 2, at minimum every go version. + * Han volunteers, Catherine will think about it. Olivier will look into + contributing as well. + * Not a lot of new code changes to make, project is pretty stable now, just + need to keep maintaining (bumping dependencies, bug fixes, CVE management, + releases, etc.) +* [ehashman] Repo created for [https://github.com/kubernetes-sigs/usage-metrics-collector](https://github.com/kubernetes-sigs/usage-metrics-collector) + * Got repo created in the last few weeks. + * Waiting for approval to push code externally, hopefully by end of year, at + latest January. + * Once public, we can do a walk-the-code update/demo on a meeting? +* [Paige] Does SIG instrumentation do tracing for system components? + * Yes! This is being led by David Ashpole (API server) + * API server tracing should go beta in the next release + * Kubelet tracing (Sally O’Malley) - currently in alpha, lots of changes + required before beta + +## Agenda (2022-11-10) + +* [Pranshu] KSM’s own mixin’s project? +* [Pranshu] Enabling discussions on the repository (can start with KSM). + * Already enabled +* [Pranshu] Shadow program follow-ups ()? + * More [members](https://github.com/kubernetes/community/blob/master/community-membership.md#requirements)? + * Forms rollout, assessing possible major tasks. +* [Benjamin Saint-Cyr] Demo of kernel tracing for kubelets. + + + +* https://github.com/BenjaminSaintCyr/k8s-instrumentation-demo + + +## Notes from Kubecon SIG F2F: + +* Better guidelines/documentations for metrics and logs and traces + 1. Answering basic questions like which logger should we use in k8s custom controllers +* Move documentation to website +* Does kubebuilder use component-base? + 2. Should look into migrating metrics stuff to component-base +* Should we promote metrics/resource to stable? +* Metrics server scalability + 3. We need to graduate metrics/resource metrics to stable status. +* Kubelet metrics should possibly sharded to different endpoints +* Better first-time issues + + +## Agenda (2022-10-13) + +* [pwittrock] [Proposal for new sig project for usage metrics](https://docs.google.com/document/d/12JEje-SpM78N5OhZzWg-_Ba91n6VWRm5c4l_c2U-ljw/edit#) + * AI: ehashman to open issue with kubernetes/org for repo creation. + + +## Agenda (2022-09-29) + +* Shadow Program: + + +## Agenda (2022-09-15) + +* [dashpole] Plans for KEPs in 1.26? + * [https://github.com/kubernetes/enhancements/issues?q=is%3Aopen+is%3Aissue+label%3Asig%2Finstrumentation](https://github.com/kubernetes/enhancements/issues?q=is%3Aopen+is%3Aissue+label%3Asig%2Finstrumentation) +* AI: Document [logtools](https://github.com/kubernetes-sigs/logtools) as a sub-project +* KSM v3.0 planning: [https://github.com/orgs/kubernetes/projects/90/views/1](https://github.com/orgs/kubernetes/projects/90/views/1) + + +## Agenda (2022-09-01) + +* [logicalhan] - [https://github.com/kubernetes/enhancements/pull/3469/](https://github.com/kubernetes/enhancements/pull/3469/) +* [logicalhan] - status of metrics framework KEP +* [dgrisonnet] taking ownership of events/v1 migration [https://github.com/kubernetes/enhancements/issues/383](https://github.com/kubernetes/enhancements/issues/383) + * New KEP to plan a safe migration path for all the kube components: + * Need new per EventSeries backoff mechanism + * Rate-limiting for unique Events + + +## Agenda (2022-08-18) + +* No agenda items to discuss + + +## Agenda (2022-08-04) + +* [raptorsun (just taking notes)] Metrics API/Server + * Metrics API stability + * Resource usage / performance of Metrics server implementation + * Notes: + * We can always do a v2 if needed + * We can always replace the metrics server with a better implementation +* [logicalhan] extending stability update +* [dashpole] Kubelet Tracing made it into 1.25! + * Follow-ups for etcd: + * Ask for increasing otel library version to 1.0+ in 3.5? + * Ask to change the default sampling rate to 0 from 100%. (bug fix) + + +## Agenda (2022-07-21) + +* [raptorsun] kubctl top + node column & memory unit [issue](https://github.com/kubernetes/kubernetes/issues/110722) +* To discuss in next meeting: + * Metrics API stability + * Resource usage / performance of Metrics server implementation + * [after a meeting note from serathius@ (owner of Metrics Server)]. Please reach out to me on Slack if you have any questions. + + +## Agenda (2022-07-07) + +* [serathius] Question about admin experience on reliability of K8s logs. + * Is anyone running high log generating applications? + * What’s your experience with log reliability? Have you noticed logs being lost? + * Do you measure the percentage of logs delivered? + * If you or someone you know had this problem, would love to talk. Feel free to reach out to @serathius on K8s Slack + + +## Agenda (2022-06-23) + +* [dgrisonnet] Standardizing metrics initialization and registration in k/k: + * [https://github.com/kubernetes/kubernetes/pull/110027/files#r872226087](https://github.com/kubernetes/kubernetes/pull/110027/files#r872226087) +* [serathius] Question about admin experience on reliability of K8s logs. + * Serathius - will not be able to attend. Feel free to skip. +* [dashpole,dgrisonnet] OpenTelemetry and Prometheus Exponential (Sparse) Histograms continuation + * Concern about migrating to sparse histogram: Cardinality when producing fixed buckets? + * AI: Write a strawman document for how we would do a migration. Share with the prometheus folks to see if any concerns/problems are addressable. +* [catherineF-dev] High cardinitiy metric apiserver_request_duration_seconds_bucket [https://github.com/kubernetes/kubernetes/issues/110742](https://github.com/kubernetes/kubernetes/issues/110742) + * Trace + one simplified metric (only capture high latency cases and drop some labels) + * AI: Look into adding exemplars to the metric and traceid to the audit logs + * [serathius] ^ Looks like more structured logging thing then audit log + + +## Agenda (2022-06-09) + +* [raptorsun, dgrisonnet] Improve kubectl top UX with PodMetrics + * [https://github.com/kubernetes/kubernetes/issues/102051](https://github.com/kubernetes/kubernetes/issues/102051) + * [https://github.com/kubernetes/kubectl/issues/830](https://github.com/kubernetes/kubectl/issues/830) +* [dashpole] OpenTelemetry and Prometheus Exponential (Sparse) Histograms + * + * TL;DR they differ on bucket start being inclusive vs exclusive. + * Do we consider it backwards-compatible to switch from fixed-bucket histograms to exponential histograms (since it changes bucket boundaries)? Would we switch histograms to exponential histograms if bucket boundaries are the only thing that changes? + + +## Agenda (2022-05-12) + +* KEP planning - Enhancement freeze June 16th + + +## Agenda (2022-04-28) + +* Canceled due to technical difficulties. + + +## Agenda (2022-04-14) + +* Announcements + * Release delayed until May 3rd: [https://github.com/kubernetes/sig-release/pull/1884](https://github.com/kubernetes/sig-release/pull/1884) +* Discussion from Chairs/Leads: + * Ensuring test flakes get fixed + * [https://github.com/kubernetes/kubernetes/issues?q=is%3Aopen+is%3Aissue+label%3Asig%2Finstrumentation+label%3Akind%2Fflake](https://github.com/kubernetes/kubernetes/issues?q=is%3Aopen+is%3Aissue+label%3Asig%2Finstrumentation+label%3Akind%2Fflake) + * Improving Kubernetes reliability + * Improving the enhancements process + * There is a huge amount of toil in writing KEPs/adding metadata, + particularly when much of the information is available in the git + history already + * Kepctl is useful but most people don’t know it exists and it often + breaks, needs frequent patches in order to work. If documentation was + improved, might be helpful + * KEP process is very painful, giant barrier for new contributors; can + we think bigger and reimagine the process rather than just adding + tooling (technical solutions to a process problem)? + * SIG is okay with changes to kep.yaml files so long as tools + autogenerate all changes, no additional manual work for contributors + + +## Triage (2022-04-07) + + +## Agenda (2022-03-31) + +Canceled - no agenda + + +## Agenda (2022-03-17) + +* Reminder: code freeze + * Milestone review: bumped API tracing beta to 1.25 +* [serathius,pohly] Needs reviewers for klog + * [https://github.com/kubernetes/klog/issues/222](https://github.com/kubernetes/klog/issues/222) + * **Action:** serathius will run the maintainers script to update OWNERS file + + +## Agenda (2022-03-03) + +* [Leads] Annual report + * [https://github.com/kubernetes/community/pull/6463](https://github.com/kubernetes/community/pull/6463) + * Should be merged by Mar. 1 +* [dgrisonnet,sanchezl] Adding a new bounded dimension to a stable metric. + Extending apiserver_admission_webhook_admission_duration with a bounded + resource label for finer grained SLO. + * [https://github.com/kubernetes/kubernetes/pull/69895](https://github.com/kubernetes/kubernetes/pull/69895) + * [https://github.com/kubernetes/kubernetes/pull/108468](https://github.com/kubernetes/kubernetes/pull/108468) + + +## Triage (2022-02-24) + + +## Agenda (2022-02-17) + +* [Leads] Annual report + * [https://github.com/kubernetes/community/pull/6463](https://github.com/kubernetes/community/pull/6463) +* [ehashman] Charter update FYI + * Adds tracing, removes heapster + * [https://github.com/kubernetes/community/pull/6464](https://github.com/kubernetes/community/pull/6464) +* + + +## Triage (2022-02-10) + +* [hase1128] Continue to discuss the idea for KEP2312 \ +[https://github.com/kubernetes/enhancements/pull/2312](https://github.com/kubernetes/enhancements/pull/2312) \ +Doc URL(I uploaded on slack): [https://kubernetes.slack.com/archives/C20HH14P7/p1643912029063699](https://kubernetes.slack.com/archives/C20HH14P7/p1643912029063699) + + +## Agenda (2022-02-03) + +* Announcements + * Final KEP review: deadline is today +* [dgrisonnet] Improve tooling to make sure that all PRs modifying a metrics.go file, are approved by sig-instrumentation. +* [hase1128] I would like to get feedback about my current idea for KEP2312 \ +[https://github.com/kubernetes/enhancements/pull/2312](https://github.com/kubernetes/enhancements/pull/2312) \ +Doc URL(I uploaded on slack): [https://kubernetes.slack.com/archives/C20HH14P7/p1643912029063699](https://kubernetes.slack.com/archives/C20HH14P7/p1643912029063699) + + +## Triage (2022-01-27) + + +## Agenda (2022-01-20) + +* Announcements + * Damien is our new TL! + * Reminder: upcoming release dates +* [fromani] (can be postponed, 1.24 or beyond) klog: towards per-flow verbosity + * Looking for previous history/attempts (if any) and design yay/nay + * Probably deserves a full KEP, will write depending on the above bullet point + * POC/usecase description [here](https://github.com/kubernetes-sigs/scheduler-plugins/pull/289) (caveat: security implications not addressed) +* [dashpole] Stable metric deprecation period discussion: Should stable metrics be permanent? + * [https://github.com/kubernetes/website/pull/31389#pullrequestreview-856542765](https://github.com/kubernetes/website/pull/31389#pullrequestreview-856542765) + + +## Triage (2022-01-13) + + +## Agenda (2022-01-06) + +* Announcements + * 1.24 dates not yet finalized + * Week 1: January 10 + * Week ???: Release planned for April 19 +* [Leads] New TL update + * Congrats Damien! + * Lazy consensus: need to submit PR/mailing list post + * Also need to clean up OWNERS files with leads once done +* [ehashman] 1.24 KEP planning, continued +* [logicalhan] +* [dgrisonnet] Possible new KEPs diff --git a/sig-k8s-infra/README.md b/sig-k8s-infra/README.md index 2fb0d298..9d480fb4 100644 --- a/sig-k8s-infra/README.md +++ b/sig-k8s-infra/README.md @@ -24,8 +24,8 @@ The [charter](charter.md) defines the scope and governance of the K8s Infra Spec ### Chairs The Chairs of the SIG run operations and processes governing the SIG. -* Arnaud Meukam (**[@ameukam](https://github.com/ameukam)**), Alter Way -* Davanum Srinivas (**[@dims](https://github.com/dims)**), VMware +* Arnaud Meukam (**[@ameukam](https://github.com/ameukam)**), VMware +* Davanum Srinivas (**[@dims](https://github.com/dims)**), Amazon Web Services ### Technical Leads The Technical Leads of the SIG establish new subprojects, decommission existing @@ -83,6 +83,17 @@ Code and configuration to manage Kubernetes project infrastructure, including va - Regular SIG Meeting: [Wednesdays at 20:00 UTC](https://zoom.us/j/93109963352?pwd=SHJTcFR2bVg1akYxSDREUWQzaldrQT09) (bi-weekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=20:00&tz=UTC). - [Meeting notes and Agenda](http://bit.ly/sig-k8s-infra-notes). - [Meeting recordings](http://bit.ly/sig-k8s-infra-playlist). +### porche +A custom HTTP redirector serving Kubernetes binaries from existing vendor supported and approved storage services. +- **Owners:** + - [kubernetes-sigs/porche](https://github.com/kubernetes-sigs/porche/blob/main/OWNERS) +- **Contact:** + - Slack: [#sig-k8s-infra](https://kubernetes.slack.com/messages/sig-k8s-infra) + - [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-k8s-infra) +- **Meetings:** + - Regular SIG Meeting: [Wednesdays at 20:00 UTC](https://zoom.us/j/93109963352?pwd=SHJTcFR2bVg1akYxSDREUWQzaldrQT09) (bi-weekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=20:00&tz=UTC). + - [Meeting notes and Agenda](http://bit.ly/sig-k8s-infra-notes). + - [Meeting recordings](http://bit.ly/sig-k8s-infra-playlist). ### registry.k8s.io A custom HTTP redirector serving Kubernetes container image blobs from existing vendor supported container registries. - **Owners:** diff --git a/sig-list.md b/sig-list.md index 05f20dd7..632823be 100644 --- a/sig-list.md +++ b/sig-list.md @@ -32,27 +32,27 @@ When the need arises, a [new SIG can be created](sig-wg-lifecycle.md) | Name | Label | Chairs | Contact | Meetings | |------|-------|--------|---------|----------| -|[API Machinery](sig-api-machinery/README.md)|[api-machinery](https://github.com/kubernetes/kubernetes/labels/sig%2Fapi-machinery)|* [David Eads](https://github.com/deads2k), Red Hat<br>* [Federico Bongiovanni](https://github.com/fedebongio), Google<br>|* [Slack](https://kubernetes.slack.com/messages/sig-api-machinery)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-api-machinery)|* Kubebuilder and Controller Runtime Meeting: [Thursdays at 09:00 PT (Pacific Time) (biweekly)]()<br>* Regular SIG Meeting: [Wednesdays at 11:00 PT (Pacific Time) (biweekly)](https://zoom.us/my/apimachinery)<br> +|[API Machinery](sig-api-machinery/README.md)|[api-machinery](https://github.com/kubernetes/kubernetes/labels/sig%2Fapi-machinery)|* [David Eads](https://github.com/deads2k), Red Hat<br>* [Federico Bongiovanni](https://github.com/fedebongio), Google<br>|* [Slack](https://kubernetes.slack.com/messages/sig-api-machinery)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-api-machinery)|* Kubebuilder and Controller Runtime Meeting: [Thursdays at 11:00 PT (Pacific Time) (biweekly)]()<br>* Regular SIG Meeting: [Wednesdays at 11:00 PT (Pacific Time) (biweekly)](https://zoom.us/my/apimachinery)<br> |[Apps](sig-apps/README.md)|[apps](https://github.com/kubernetes/kubernetes/labels/sig%2Fapps)|* [Janet Kuo](https://github.com/janetkuo), Google<br>* [Kenneth Owens](https://github.com/kow3ns), Brex<br>* [Maciej Szulik](https://github.com/soltysh), Red Hat<br>|* [Slack](https://kubernetes.slack.com/messages/sig-apps)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-apps)|* Regular SIG Meeting: [Mondays at 9:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/739385290?pwd=ekVmNGRjT214MGJkY1JUUUpPMVlJUT09)<br> -|[Architecture](sig-architecture/README.md)|[architecture](https://github.com/kubernetes/kubernetes/labels/sig%2Farchitecture)|* [Derek Carr](https://github.com/derekwaynecarr), Red Hat<br>* [Davanum Srinivas](https://github.com/dims), VMware<br>* [John Belamaric](https://github.com/johnbelamaric), Google<br>|* [Slack](https://kubernetes.slack.com/messages/sig-architecture)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-architecture)|* Enhancements Subproject Meeting: [Thursdays at 10:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/95357819945)<br>* Production Readiness Office Hours: [Wednesdays at 12:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/482444151)<br>* Regular SIG Meeting: [Thursdays at 11:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/845605479)<br>* code organization Office Hours: [Thursdays at 14:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/159990793)<br>* conformance office Hours: [Wednesdays at 18:00 UTC (First Wednesday of the month)](https://zoom.us/j/427337923)<br> +|[Architecture](sig-architecture/README.md)|[architecture](https://github.com/kubernetes/kubernetes/labels/sig%2Farchitecture)|* [Derek Carr](https://github.com/derekwaynecarr), Red Hat<br>* [Davanum Srinivas](https://github.com/dims), Amazon Web Services<br>* [John Belamaric](https://github.com/johnbelamaric), Google<br>|* [Slack](https://kubernetes.slack.com/messages/sig-architecture)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-architecture)|* Enhancements Subproject Meeting: [Thursdays at 10:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/95357819945)<br>* Production Readiness Office Hours: [Wednesdays at 12:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/482444151)<br>* Regular SIG Meeting: [Thursdays at 11:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/845605479)<br>* code organization Office Hours: [Thursdays at 14:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/159990793)<br>* conformance office Hours: [Wednesdays at 18:00 UTC (First Wednesday of the month)](https://zoom.us/j/427337923)<br> |[Auth](sig-auth/README.md)|[auth](https://github.com/kubernetes/kubernetes/labels/sig%2Fauth)|* [Mo Khan](https://github.com/enj), Microsoft<br>* [Mike Danese](https://github.com/mikedanese), Google<br>* [Rita Zhang](https://github.com/ritazh), Microsoft<br>|* [Slack](https://kubernetes.slack.com/messages/sig-auth)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-auth)|* Regular SIG Meeting: [Wednesdays at 11:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/264572674)<br>* Secrets Store CSI Meeting: [Thursdays at 8:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/91272289538)<br>* Weekly Issues/PR Triage Meeting: [Mondays at 9:00 PT (Pacific Time) (weekly)](https://zoom.us/j/264572674)<br> |[Autoscaling](sig-autoscaling/README.md)|[autoscaling](https://github.com/kubernetes/kubernetes/labels/sig%2Fautoscaling)|* [Guy Templeton](https://github.com/gjtempleton), Skyscanner<br>* [Marcin Wielgus](https://github.com/mwielgus), Google<br>|* [Slack](https://kubernetes.slack.com/messages/sig-autoscaling)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-autoscaling)|* Regular SIG Meeting: [Mondays at 16:00 Poland (weekly)](https://zoom.us/j/944410904)<br> -|[CLI](sig-cli/README.md)|[cli](https://github.com/kubernetes/kubernetes/labels/sig%2Fcli)|* [Katrina Verey](https://github.com/KnVerey), Shopify<br>* [Eddie Zaneski](https://github.com/eddiezane), Chainguard, Inc<br>* [Sean Sullivan](https://github.com/seans3), Google<br>|* [Slack](https://kubernetes.slack.com/messages/sig-cli)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-cli)|* Bug Scrub: [Wednesdays at 09:00 PT (Pacific Time) (monthly)](https://zoom.us/j/288426795?pwd=UDdoYnFyNjBiS1RHcXRxS1BCNy9wUT09)<br>* KRM Functions Subproject Meeting: [Wednesdays at 10:30 PT (Pacific Time) (biweekly)](https://zoom.us/j/288426795?pwd=UDdoYnFyNjBiS1RHcXRxS1BCNy9wUT09)<br>* Kustomize Bug Scrub: [Wednesdays at 09:00 PT (Pacific Time) (monthly)](https://zoom.us/j/288426795?pwd=UDdoYnFyNjBiS1RHcXRxS1BCNy9wUT09)<br>* Regular SIG Meeting: [Wednesdays at 09:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/288426795?pwd=UDdoYnFyNjBiS1RHcXRxS1BCNy9wUT09)<br> -|[Cloud Provider](sig-cloud-provider/README.md)|[cloud-provider](https://github.com/kubernetes/kubernetes/labels/sig%2Fcloud-provider)|* [Andrew Sy Kim](https://github.com/andrewsykim), Google<br>* [Nick Turner](https://github.com/nckturner), Amazon<br>|* [Slack](https://kubernetes.slack.com/messages/sig-cloud-provider)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-cloud-provider)|* Regular SIG Meeting: [Wednesdays at 9:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/508079177?pwd=ZmEvMksxdTFTc0N1eXFLRm91QUlyUT09)<br>* (cloud-provider-extraction-migration) Weekly Sync removing the in-tree cloud providers led by @cheftako and @mcrute: [Thursdays at 13:30 PT (Pacific Time) (weekly)](https://docs.google.com/document/d/1KLsGGzNXQbsPeELCeF_q-f0h0CEGSe20xiwvcR2NlYM/edit)<br>* (provider-alibaba-cloud) Regular Alibaba Cloud Subproject Meeting: [Tuesdays at 12:00 UTC (monthly 2020 start date: Jan. 7th)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>* (provider-aws) Regular AWS Subproject Meeting: [Fridays at 9:00 PT (Pacific Time) (biweekly 2019 start date: Jan. 11th)](https://zoom.us/my/k8ssigaws)<br>* (provider-azure) Azure Subproject Meeting: [Mondays at 18:00 PT (Pacific Time) (monthly - third Monday)](https://zoom.us/j/586836662)<br>* (provider-gcp) Regular GCP Subproject Meeting: [Thursdays at 16:00 UTC (biweekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>* (provider-ibmcloud) Regular IBM Subproject Meeting: [Wednesdays at 14:00 ET (Eastern Time) (monthly - last Wednesday every month)](https://zoom.us/j/9392903494)<br>* (provider-oci) Regular Oracle Cloud Subproject Meeting: [Tuesdays at 06:00 PT (Pacific Time) (First Tuesday of each month)](https://oracle.zoom.us/j/99910180651?pwd=MjhhVC9jZjU3eGIxdjNTYm1UU3V6dz09)<br>* (provider-openstack) Regular OpenStack Subproject Meeting: [Wednesdays at 08:00 PT (Pacific Time) (biweekly starting Wednesday March 20, 2019)](https://docs.google.com/document/d/1bW3j4hFN4D8rv2LFv-DybB3gcE5ISAaOO_OpvDCgrGg/edit)<br>* (provider-vsphere) Cloud Provider vSphere monthly syncup: [Wednesdays at 09:00 PT (Pacific Time) (monthly - first Wednesday every month)](https://zoom.us/j/584244729)<br> -|[Cluster Lifecycle](sig-cluster-lifecycle/README.md)|[cluster-lifecycle](https://github.com/kubernetes/kubernetes/labels/sig%2Fcluster-lifecycle)|* [Justin Santa Barbara](https://github.com/justinsb), Google<br>* [Lubomir Ivanov](https://github.com/neolit123), VMware<br>* [Vince Prignano](https://github.com/vincepri), VMware<br>|* [Slack](https://kubernetes.slack.com/messages/sig-cluster-lifecycle)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-cluster-lifecycle)|* Regular SIG Meeting: [Tuesdays at 09:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/916523531?pwd=eVhPNU5IQWtBYWhmT1N4T0V6bHZFZz09)<br>* (cluster-addons) Cluster Addons meeting: [Tuesdays at 09:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/130096731?pwd=U3pzWloxZ0lpbEtadTZGSERRdENrZz09)<br>* (cluster-api) Cluster API office hours: [Wednesdays at 10:00 PT (Pacific Time) (weekly)](https://zoom.us/j/861487554?pwd=dTVGVVFCblFJc0VBbkFqQlU0dHpiUT09)<br>* (cluster-api-provider-aws) Cluster API Provider AWS office hours: [Mondays at 09:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/423312508?pwd=Tk9OWnZ4WHg2T2xRek9xZXA1eFQ4dz09)<br>* (cluster-api-provider-azure) Cluster API Provider Azure office hours: [Thursdays at 09:00 PT (Pacific Time) (weekly)](https://zoom.us/j/566930821?pwd=N2JuRWljc3hGS3ZnVlBLTk42TFlzQT09)<br>* (cluster-api-provider-digitalocean) Cluster API Provider DigitalOcean office hours: [Thursdays at 09:00 PT (Pacific Time) (monthly, second Thursday of the month)](https://zoom.us/j/91312171751?pwd=bndnMDdJMkhySDVncjZoR1VhdFBTZz09)<br>* (cluster-api-provider-ibmcloud) Cluster API Provider IBM Cloud office hours: [Fridays at 09:00 IST (weekly)](https://zoom.us/j/9392903494)<br>* (cluster-api-provider-kubevirt) Cluster API Provider KubeVirt Syncup Meetings: [Tuesdays at 8:00 PT (Pacific Time) (weekly starting Tuesday December 7th, 2021)](https://zoom.us/j/94685513559?pwd=cnI3RUQyZ3RrckpOc1BQNDA1Q1BrZz09)<br>* (cluster-api-provider-nested) Cluster API Provider Nested Office Hours: [Tuesdays at 10:00 PT (Pacific Time) (weekly)](https://zoom.us/j/91929881559?pwd=WllxazhTUzBFN1BNWTRadTA3NGtQQT09)<br>* (cluster-api-provider-vsphere) Cluster API vSphere meeting: [Thursdays at 10:00 PT (Pacific Time) (biweekly starting Thursday June 25th, 2020)](https://zoom.us/j/92253194848?pwd=cVVVNDMxeTl1QVJPUlpvLzNSVU1JZz09)<br>* (etcdadm) etcdadm Office Hours: [Mondays at 09:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/612375927?pwd=MldxRnRSOExCVW1rbjM4ZzBSc3MvUT09)<br>* (image-builder) Image Builder office hours: [Thursdays at 08:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/807524571?pwd=WEFTeDJzeWU3bVFkcWQ0UEdZRkRCdz09)<br>* (kOps) kOps Office Hours: [Fridays at 09:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/97072789944?pwd=VVlUR3dhN2h5TEFQZHZTVVd4SnJUdz09)<br>* (kubeadm) kubeadm Office Hours: [Wednesdays at 09:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/179916854?pwd=dzRhbjFnRGVQRDVUVHY1a29JV2JxUT09)<br>* (minikube) minikube office hours: [Mondays at 11:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/97017029363?pwd=U3MvZ3pMMHM5eWorSjgzUnd5OEFtUT09)<br> -|[Contributor Experience](sig-contributor-experience/README.md)|[contributor-experience](https://github.com/kubernetes/kubernetes/labels/sig%2Fcontributor-experience)|* [Josh Berkus](https://github.com/jberkus), Red Hat<br>* [Bob Killen](https://github.com/mrbobbytables), Google<br>|* [Slack](https://kubernetes.slack.com/messages/sig-contribex)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-contribex)|* Regular SIG Meeting: [Wednesdays at 9:00 PT (Pacific Time) (weekly alternating slack/zoom)](https://zoom.us/j/397264241?pwd=bHNnZVArNFdPaWVJMmttdko0Sktudz09)<br>* (contributor-comms) Contributor Comms - Upstream Marketing Team Meeting: [Fridays at 8:00 PT (Pacific Time) (weekly)](https://zoom.us/j/596959769?pwd=TURBNlZPb3BEWVFmbWlCYXlMVVJiUT09)<br>* (events) Office Hours European Edition (Open Q&A for end-user kubernetes related questions): [Wednesdays at 09:00 ET (Eastern Time) (monthly on 3rd Wednesday)](https://hackmd.io/@k8s/office-hours)<br>* (events) Office Hours Western Edition (Open Q&A for end-user kubernetes related questions): [Wednesdays at 12:00 ET (Eastern Time) (monthly on 3rd Wednesday)]()<br>* (github-management) GitHub Administration Subproject: [Thursdays at 09:00 PT (Pacific Time) (Monthly on 4th Thursday)](https://zoom.us/j/442435463?pwd=Rk1PWWpSSTJDaWJKdzRYb2EyTlkvZz09)<br> +|[CLI](sig-cli/README.md)|[cli](https://github.com/kubernetes/kubernetes/labels/sig%2Fcli)|* [Katrina Verey](https://github.com/KnVerey), Shopify<br>* [Eddie Zaneski](https://github.com/eddiezane), Chainguard, Inc<br>* [Sean Sullivan](https://github.com/seans3), Google<br>|* [Slack](https://kubernetes.slack.com/messages/sig-cli)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-cli)|* Bug Scrub: [Wednesdays at 09:00 PT (Pacific Time) (every four weeks)](https://zoom.us/j/288426795?pwd=UDdoYnFyNjBiS1RHcXRxS1BCNy9wUT09)<br>* KRM Functions Subproject Meeting: [Wednesdays at 10:30 PT (Pacific Time) (biweekly)](https://zoom.us/j/288426795?pwd=UDdoYnFyNjBiS1RHcXRxS1BCNy9wUT09)<br>* Kustomize Bug Scrub: [Wednesdays at 09:00 PT (Pacific Time) (every four weeks)](https://zoom.us/j/288426795?pwd=UDdoYnFyNjBiS1RHcXRxS1BCNy9wUT09)<br>* Regular SIG Meeting: [Wednesdays at 09:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/288426795?pwd=UDdoYnFyNjBiS1RHcXRxS1BCNy9wUT09)<br> +|[Cloud Provider](sig-cloud-provider/README.md)|[cloud-provider](https://github.com/kubernetes/kubernetes/labels/sig%2Fcloud-provider)|* [Andrew Sy Kim](https://github.com/andrewsykim), Google<br>* [Nick Turner](https://github.com/nckturner), Amazon<br>|* [Slack](https://kubernetes.slack.com/messages/sig-cloud-provider)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-cloud-provider)|* Regular SIG Meeting: [Wednesdays at 9:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/508079177?pwd=ZmEvMksxdTFTc0N1eXFLRm91QUlyUT09)<br>* (cloud-provider-extraction-migration) Weekly Sync removing the in-tree cloud providers led by @cheftako and @mcrute: [Thursdays at 13:30 PT (Pacific Time) (weekly)](https://docs.google.com/document/d/1KLsGGzNXQbsPeELCeF_q-f0h0CEGSe20xiwvcR2NlYM/edit)<br>* (provider-alibaba-cloud) Regular Alibaba Cloud Subproject Meeting: [Tuesdays at 12:00 UTC (monthly 2020 start date: Jan. 7th)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>* (provider-aws) Regular AWS Subproject Meeting: [Fridays at 9:00 PT (Pacific Time) (biweekly 2019 start date: Jan. 11th)](https://zoom.us/my/k8ssigaws)<br>* (provider-azure) Azure Subproject Meeting: [Tuesdays at 16:00 PT (Pacific Time) (monthly - third Tuesday)](https://zoom.us/j/586836662)<br>* (provider-gcp) Regular GCP Subproject Meeting: [Thursdays at 16:00 UTC (biweekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>* (provider-ibmcloud) Regular IBM Subproject Meeting: [Wednesdays at 14:00 ET (Eastern Time) (monthly - last Wednesday every month)](https://zoom.us/j/9392903494)<br>* (provider-oci) Regular Oracle Cloud Subproject Meeting: [Tuesdays at 06:00 PT (Pacific Time) (First Tuesday of each month)](https://oracle.zoom.us/j/99910180651?pwd=MjhhVC9jZjU3eGIxdjNTYm1UU3V6dz09)<br>* (provider-openstack) Regular OpenStack Subproject Meeting: [Wednesdays at 08:00 PT (Pacific Time) (biweekly starting Wednesday March 20, 2019)](https://docs.google.com/document/d/1bW3j4hFN4D8rv2LFv-DybB3gcE5ISAaOO_OpvDCgrGg/edit)<br>* (provider-vsphere) Cloud Provider vSphere monthly syncup: [Wednesdays at 09:00 PT (Pacific Time) (monthly - first Wednesday every month)](https://zoom.us/j/584244729)<br> +|[Cluster Lifecycle](sig-cluster-lifecycle/README.md)|[cluster-lifecycle](https://github.com/kubernetes/kubernetes/labels/sig%2Fcluster-lifecycle)|* [Justin Santa Barbara](https://github.com/justinsb), Google<br>* [Lubomir Ivanov](https://github.com/neolit123), VMware<br>* [Vince Prignano](https://github.com/vincepri), Red Hat<br>|* [Slack](https://kubernetes.slack.com/messages/sig-cluster-lifecycle)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-cluster-lifecycle)|* Regular SIG Meeting: [Tuesdays at 09:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/916523531?pwd=eVhPNU5IQWtBYWhmT1N4T0V6bHZFZz09)<br>* (cluster-addons) Cluster Addons meeting: [Tuesdays at 09:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/130096731?pwd=U3pzWloxZ0lpbEtadTZGSERRdENrZz09)<br>* (cluster-api) Cluster API office hours: [Wednesdays at 10:00 PT (Pacific Time) (weekly)](https://zoom.us/j/861487554?pwd=dTVGVVFCblFJc0VBbkFqQlU0dHpiUT09)<br>* (cluster-api-provider-aws) Cluster API Provider AWS office hours: [Mondays at 09:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/423312508?pwd=Tk9OWnZ4WHg2T2xRek9xZXA1eFQ4dz09)<br>* (cluster-api-provider-azure) Cluster API Provider Azure office hours: [Thursdays at 09:00 PT (Pacific Time) (weekly)](https://zoom.us/j/566930821?pwd=N2JuRWljc3hGS3ZnVlBLTk42TFlzQT09)<br>* (cluster-api-provider-digitalocean) Cluster API Provider DigitalOcean office hours: [Thursdays at 09:00 PT (Pacific Time) (monthly, second Thursday of the month)](https://zoom.us/j/91312171751?pwd=bndnMDdJMkhySDVncjZoR1VhdFBTZz09)<br>* (cluster-api-provider-ibmcloud) Cluster API Provider IBM Cloud office hours: [Fridays at 09:00 IST (weekly)](https://zoom.us/j/9392903494)<br>* (cluster-api-provider-kubevirt) Cluster API Provider KubeVirt Syncup Meetings: [Tuesdays at 8:00 PT (Pacific Time) (weekly starting Tuesday December 7th, 2021)](https://zoom.us/j/94685513559?pwd=cnI3RUQyZ3RrckpOc1BQNDA1Q1BrZz09)<br>* (cluster-api-provider-nested) Cluster API Provider Nested Office Hours: [Tuesdays at 10:00 PT (Pacific Time) (weekly)](https://zoom.us/j/91929881559?pwd=WllxazhTUzBFN1BNWTRadTA3NGtQQT09)<br>* (cluster-api-provider-vsphere) Cluster API vSphere meeting: [Thursdays at 10:00 PT (Pacific Time) (biweekly starting Thursday June 25th, 2020)](https://zoom.us/j/92253194848?pwd=cVVVNDMxeTl1QVJPUlpvLzNSVU1JZz09)<br>* (etcdadm) etcdadm Office Hours: [Mondays at 09:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/612375927?pwd=MldxRnRSOExCVW1rbjM4ZzBSc3MvUT09)<br>* (image-builder) Image Builder office hours: [Thursdays at 08:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/807524571?pwd=WEFTeDJzeWU3bVFkcWQ0UEdZRkRCdz09)<br>* (kOps) kOps Office Hours: [Fridays at 09:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/97072789944?pwd=VVlUR3dhN2h5TEFQZHZTVVd4SnJUdz09)<br>* (kubeadm) kubeadm Office Hours: [Wednesdays at 09:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/179916854?pwd=dzRhbjFnRGVQRDVUVHY1a29JV2JxUT09)<br>* (minikube) minikube office hours: [Mondays at 11:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/97017029363?pwd=U3MvZ3pMMHM5eWorSjgzUnd5OEFtUT09)<br> +|[Contributor Experience](sig-contributor-experience/README.md)|[contributor-experience](https://github.com/kubernetes/kubernetes/labels/sig%2Fcontributor-experience)|* [Josh Berkus](https://github.com/jberkus), Red Hat<br>* [Bob Killen](https://github.com/mrbobbytables), Google<br>|* [Slack](https://kubernetes.slack.com/messages/sig-contribex)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-contribex)|* Regular SIG Meeting: [Wednesdays at 9:00 PT (Pacific Time) (weekly alternating slack/zoom)](https://zoom.us/j/397264241?pwd=bHNnZVArNFdPaWVJMmttdko0Sktudz09)<br>* (contributor-comms) Contributor Comms - Upstream Marketing Team Meeting: [Fridays at 8:00 PT (Pacific Time) (weekly)](https://zoom.us/j/596959769?pwd=TURBNlZPb3BEWVFmbWlCYXlMVVJiUT09)<br>* (github-management) GitHub Administration Subproject: [Thursdays at 09:00 PT (Pacific Time) (Monthly on 4th Thursday)](https://zoom.us/j/442435463?pwd=Rk1PWWpSSTJDaWJKdzRYb2EyTlkvZz09)<br> |[Docs](sig-docs/README.md)|[docs](https://github.com/kubernetes/kubernetes/labels/sig%2Fdocs)|* [Divya Mohan](https://github.com/divya-mohan0209), SUSE<br>* [Jim Angel](https://github.com/jimangel), Google<br>* [Natali Vlatko](https://github.com/natalisucks), Wayfair<br>* [Rey Lejano](https://github.com/reylejano), SUSE<br>|* [Slack](https://kubernetes.slack.com/messages/sig-docs)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-docs)|* APAC SIG Meeting: [Wednesdays at 05:30 UTC (monthly - Wednesday, after the fourth Tuesday, every month)](https://docs.google.com/document/d/1emuO4nmaQq3K8JZ9-MQeIygtrCPO9kWv7U7RzTaW4F8/edit)<br>* Korean Team Meeting: [Thursdays at 13:00 UTC (biweekly)](https://docs.google.com/document/d/1h5sMhBpPB5unJmBAS7KzDiPs-_eFQOu5o4UyHwMtFCA/edit)<br>* Localization Subproject Meeting: [Mondays at 15:00 UTC (first Monday of the month)](https://docs.google.com/document/d/1NwO1AN8Ea2zlK8uAdaDAKf1-LZDAFvSewIfrKqfl5No/)<br>* New Contributor Meet and Greet: [Tuesdays at 10:30 UTC (first Tuesday of the month)](https://zoom.us/j/92822621820?pwd=S1p4RnB1RmNSZ3JjYlRRUVd4UjFPZz09)<br>* Regular SIG Meeting: [Tuesdays at 17:30 UTC (weekly - except fourth Tuesday every month)](https://docs.google.com/document/d/1emuO4nmaQq3K8JZ9-MQeIygtrCPO9kWv7U7RzTaW4F8/edit)<br>* Spanish Team Meeting: [Tuesdays at 15:30 UTC (weekly)](https://zoom.us/j/95918289494?pwd=Wk9Oa0xZUkFXSDV5OTFoZEZsTURCZz09)<br> -|[Instrumentation](sig-instrumentation/README.md)|[instrumentation](https://github.com/kubernetes/kubernetes/labels/sig%2Finstrumentation)|* [Elana Hashman](https://github.com/ehashman), Red Hat<br>* [Han Kang](https://github.com/logicalhan), Google<br>|* [Slack](https://kubernetes.slack.com/messages/sig-instrumentation)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-instrumentation)|* Regular SIG Meeting: [Thursdays at 9:30 PT (Pacific Time) (biweekly)](https://zoom.us/j/5342565819?pwd=RlVsK21NVnR1dmE3SWZQSXhveHZPdz09)<br>* Regular Triage Meeting: [Thursdays at 9:30 PT (Pacific Time) (biweekly - alternating with regular meeting)](https://zoom.us/j/5342565819?pwd=RlVsK21NVnR1dmE3SWZQSXhveHZPdz09)<br> -|[K8s Infra](sig-k8s-infra/README.md)|[k8s-infra](https://github.com/kubernetes/kubernetes/labels/sig%2Fk8s-infra)|* [Arnaud Meukam](https://github.com/ameukam), Alter Way<br>* [Davanum Srinivas](https://github.com/dims), VMware<br>|* [Slack](https://kubernetes.slack.com/messages/sig-k8s-infra)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-k8s-infra)|* Regular SIG Meeting: [Wednesdays at 20:00 UTC (bi-weekly)](https://zoom.us/j/93109963352?pwd=SHJTcFR2bVg1akYxSDREUWQzaldrQT09)<br>* (k8s-infra-dns) Regular SIG Meeting: [Wednesdays at 20:00 UTC (bi-weekly)](https://zoom.us/j/93109963352?pwd=SHJTcFR2bVg1akYxSDREUWQzaldrQT09)<br>* (k8s-infra-groups) Regular SIG Meeting: [Wednesdays at 20:00 UTC (bi-weekly)](https://zoom.us/j/93109963352?pwd=SHJTcFR2bVg1akYxSDREUWQzaldrQT09)<br>* (k8s.io) Regular SIG Meeting: [Wednesdays at 20:00 UTC (bi-weekly)](https://zoom.us/j/93109963352?pwd=SHJTcFR2bVg1akYxSDREUWQzaldrQT09)<br>* (registry.k8s.io) Regular SIG Meeting: [Wednesdays at 20:00 UTC (bi-weekly)](https://zoom.us/j/93109963352?pwd=SHJTcFR2bVg1akYxSDREUWQzaldrQT09)<br> +|[Instrumentation](sig-instrumentation/README.md)|[instrumentation](https://github.com/kubernetes/kubernetes/labels/sig%2Finstrumentation)|* [Elana Hashman](https://github.com/ehashman), Apple<br>* [Han Kang](https://github.com/logicalhan), Google<br>|* [Slack](https://kubernetes.slack.com/messages/sig-instrumentation)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-instrumentation)|* Regular SIG Meeting: [Thursdays at 9:30 PT (Pacific Time) (biweekly)](https://zoom.us/j/5342565819?pwd=RlVsK21NVnR1dmE3SWZQSXhveHZPdz09)<br>* Regular Triage Meeting: [Thursdays at 9:30 PT (Pacific Time) (biweekly - alternating with regular meeting)](https://zoom.us/j/5342565819?pwd=RlVsK21NVnR1dmE3SWZQSXhveHZPdz09)<br> +|[K8s Infra](sig-k8s-infra/README.md)|[k8s-infra](https://github.com/kubernetes/kubernetes/labels/sig%2Fk8s-infra)|* [Arnaud Meukam](https://github.com/ameukam), VMware<br>* [Davanum Srinivas](https://github.com/dims), Amazon Web Services<br>|* [Slack](https://kubernetes.slack.com/messages/sig-k8s-infra)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-k8s-infra)|* Regular SIG Meeting: [Wednesdays at 20:00 UTC (bi-weekly)](https://zoom.us/j/93109963352?pwd=SHJTcFR2bVg1akYxSDREUWQzaldrQT09)<br>* (k8s-infra-dns) Regular SIG Meeting: [Wednesdays at 20:00 UTC (bi-weekly)](https://zoom.us/j/93109963352?pwd=SHJTcFR2bVg1akYxSDREUWQzaldrQT09)<br>* (k8s-infra-groups) Regular SIG Meeting: [Wednesdays at 20:00 UTC (bi-weekly)](https://zoom.us/j/93109963352?pwd=SHJTcFR2bVg1akYxSDREUWQzaldrQT09)<br>* (k8s.io) Regular SIG Meeting: [Wednesdays at 20:00 UTC (bi-weekly)](https://zoom.us/j/93109963352?pwd=SHJTcFR2bVg1akYxSDREUWQzaldrQT09)<br>* (porche) Regular SIG Meeting: [Wednesdays at 20:00 UTC (bi-weekly)](https://zoom.us/j/93109963352?pwd=SHJTcFR2bVg1akYxSDREUWQzaldrQT09)<br>* (registry.k8s.io) Regular SIG Meeting: [Wednesdays at 20:00 UTC (bi-weekly)](https://zoom.us/j/93109963352?pwd=SHJTcFR2bVg1akYxSDREUWQzaldrQT09)<br> |[Multicluster](sig-multicluster/README.md)|[multicluster](https://github.com/kubernetes/kubernetes/labels/sig%2Fmulticluster)|* [Jeremy Olmsted-Thompson](https://github.com/jeremyot), Google<br>* [Paul Morie](https://github.com/pmorie), Apple<br>|* [Slack](https://kubernetes.slack.com/messages/sig-multicluster)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-multicluster)|* Regular SIG Meeting: [Tuesdays at 9:30 PT (Pacific Time) (bi-weekly)](https://zoom.us/my/k8s.mc)<br> -|[Network](sig-network/README.md)|[network](https://github.com/kubernetes/kubernetes/labels/sig%2Fnetwork)|* [Casey Davenport](https://github.com/caseydavenport), Tigera<br>* [Dan Williams](https://github.com/dcbw), Red Hat<br>* [Tim Hockin](https://github.com/thockin), Google<br>|* [Slack](https://kubernetes.slack.com/messages/sig-network)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-network)|* Gateway API GAMMA Meeting (APAC Friendly): [Tuesdays at 15:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/96951309977)<br>* Gateway API GAMMA Meeting (EMEA Friendly): [Tuesdays at 08:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/96951309977)<br>* Gateway API Meeting: [Mondays at 15:00 PT (Pacific Time) (weekly)](https://zoom.us/j/441530404)<br>* Network Policy API Meeting: [Mondays at 13:00 PT (Pacific Time) (bi-weekly)](https://zoom.us/j/96264742248)<br>* SIG Network Ingress NGINX Meeting: [Thursdays at 8:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/98377891310)<br>* SIG Network KPNG APAC Meeting: [Wednesdays at 16:00 IST (Indian Standard Time) (weekly)](https://docs.google.com/document/d/1yW3AUp5rYDLYCAtZc6e4zeLbP5HPLXdvuEFeVESOTic/edit)<br>* SIG Network KPNG Meeting: [Fridays at 7:30 PT (Pacific Time) (weekly)](https://docs.google.com/document/d/1yW3AUp5rYDLYCAtZc6e4zeLbP5HPLXdvuEFeVESOTic/edit)<br>* SIG Network Meeting: [Thursdays at 09:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/361123509)<br> +|[Network](sig-network/README.md)|[network](https://github.com/kubernetes/kubernetes/labels/sig%2Fnetwork)|* [Casey Davenport](https://github.com/caseydavenport), Tigera<br>* [Dan Williams](https://github.com/dcbw), Red Hat<br>* [Tim Hockin](https://github.com/thockin), Google<br>|* [Slack](https://kubernetes.slack.com/messages/sig-network)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-network)|* Gateway API GAMMA Meeting (APAC Friendly): [Tuesdays at 15:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/96951309977)<br>* Gateway API GAMMA Meeting (EMEA Friendly): [Tuesdays at 08:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/96951309977)<br>* Gateway API Meeting: [Mondays at 15:00 PT (Pacific Time) (weekly)](https://zoom.us/j/441530404)<br>* Network Policy API Meeting: [Tuesdays at 9:00 PT (Pacific Time) (bi-weekly)](https://zoom.us/j/96264742248)<br>* SIG Network Ingress NGINX Meeting: [Thursdays at 8:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/98377891310)<br>* SIG Network KPNG APAC Meeting: [Wednesdays at 16:00 IST (Indian Standard Time) (weekly)](https://docs.google.com/document/d/1yW3AUp5rYDLYCAtZc6e4zeLbP5HPLXdvuEFeVESOTic/edit)<br>* SIG Network KPNG Meeting: [Fridays at 7:30 PT (Pacific Time) (weekly)](https://docs.google.com/document/d/1yW3AUp5rYDLYCAtZc6e4zeLbP5HPLXdvuEFeVESOTic/edit)<br>* SIG Network Meeting: [Thursdays at 09:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/361123509)<br> |[Node](sig-node/README.md)|[node](https://github.com/kubernetes/kubernetes/labels/sig%2Fnode)|* [Dawn Chen](https://github.com/dchen1107), Google<br>* [Derek Carr](https://github.com/derekwaynecarr), Red Hat<br>|* [Slack](https://kubernetes.slack.com/messages/sig-node)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-node)|* Main SIG Meeting: [Tuesdays at 10:00 PT (Pacific Time) (weekly)](https://zoom.us/j/4799874685)<br>* Weekly CI/Triage Meeting: [Wednesdays at 10:00 PT (Pacific Time) (weekly)](https://zoom.us/j/4799874685)<br> -|[Release](sig-release/README.md)|[release](https://github.com/kubernetes/kubernetes/labels/sig%2Frelease)|* [Stephen Augustus](https://github.com/justaugustus), Cisco<br>* [Sascha Grunert](https://github.com/saschagrunert), Red Hat<br>|* [Slack](https://kubernetes.slack.com/messages/sig-release)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-release)|* Regular SIG Meeting APAC/EU Oriented Time: [Tuesdays at 15:30 UTC (biweekly)](https://zoom.us/j/327142148?pwd=RE9aZWtCc0hhOWs4ZTdXZ0hBM0ROdz09)<br>* Regular SIG Meeting US Oriented Time: [Tuesdays at 17:00 UTC (biweekly)](https://zoom.us/j/327142148?pwd=RE9aZWtCc0hhOWs4ZTdXZ0hBM0ROdz09)<br> +|[Release](sig-release/README.md)|[release](https://github.com/kubernetes/kubernetes/labels/sig%2Frelease)|* [Jeremy Rickard](https://github.com/jeremyrickard), Microsoft<br>* [Stephen Augustus](https://github.com/justaugustus), Cisco<br>* [Sascha Grunert](https://github.com/saschagrunert), Red Hat<br>|* [Slack](https://kubernetes.slack.com/messages/sig-release)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-release)|* Regular SIG Meeting APAC/EU Oriented Time: [Tuesdays at 15:30 UTC (biweekly)](https://zoom.us/j/327142148?pwd=RE9aZWtCc0hhOWs4ZTdXZ0hBM0ROdz09)<br>* Regular SIG Meeting US Oriented Time: [Tuesdays at 17:00 UTC (biweekly)](https://zoom.us/j/327142148?pwd=RE9aZWtCc0hhOWs4ZTdXZ0hBM0ROdz09)<br> |[Scalability](sig-scalability/README.md)|[scalability](https://github.com/kubernetes/kubernetes/labels/sig%2Fscalability)|* [Marcel Zieba](https://github.com/marseel), Google<br>* [Shyam Jeedigunta](https://github.com/shyamjvs), AWS<br>|* [Slack](https://kubernetes.slack.com/messages/sig-scalability)<br>* [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)<br> |[Scheduling](sig-scheduling/README.md)|[scheduling](https://github.com/kubernetes/kubernetes/labels/sig%2Fscheduling)|* [Wei Huang](https://github.com/Huang-Wei), Apple<br>* [Abdullah Gharaibeh](https://github.com/ahg-g), Google<br>|* [Slack](https://kubernetes.slack.com/messages/sig-scheduling)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-scheduling)|* biweekly meeting (NA & Europe): [Thursdays at 17:00 UTC (biweekly starting Thursday June 7, 2018)](https://zoom.us/j/841218129)<br>* descheduler biweekly meeting: [Tuesdays at 17:00 UTC (biweekly starting Tuesday September 13, 2022)](https://zoom.us/j/841218129)<br>* monthly meeting (APAC): [first Thursdays at 02:00 UTC (monthly)](https://zoom.us/j/841218129)<br> |[Security](sig-security/README.md)|[security](https://github.com/kubernetes/kubernetes/labels/sig%2Fsecurity)|* [Ian Coldwater](https://github.com/IanColdwater), Twilio<br>* [Tabitha Sable](https://github.com/tabbysable), Datadog<br>|* [Slack](https://kubernetes.slack.com/messages/sig-security)<br>* [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)<br> |[Storage](sig-storage/README.md)|[storage](https://github.com/kubernetes/kubernetes/labels/sig%2Fstorage)|* [Saad Ali](https://github.com/saad-ali), Google<br>* [Xing Yang](https://github.com/xing-yang), VMware<br>|* [Slack](https://kubernetes.slack.com/messages/sig-storage)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-storage)|* Regular CSI Implementation meeting: [Monday and Wednesdays at 10:00 PT (Pacific Time) (weekly)](https://zoom.us/j/614261834)<br>* Regular SIG Meeting: [Thursdays at 9:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/614261834)<br> -|[Testing](sig-testing/README.md)|[testing](https://github.com/kubernetes/kubernetes/labels/sig%2Ftesting)|* [Benjamin Elder](https://github.com/BenTheElder), Google<br>* [Aaron Crickenberger](https://github.com/spiffxp), Google<br>* [Steve Kuznetsov](https://github.com/stevekuznetsov), Red Hat<br>|* [Slack](https://kubernetes.slack.com/messages/sig-testing)<br>* [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)<br> +|[Testing](sig-testing/README.md)|[testing](https://github.com/kubernetes/kubernetes/labels/sig%2Ftesting)|* [Benjamin Elder](https://github.com/BenTheElder), Google<br>* [Michelle Shepardson](https://github.com/michelle192837), Google<br>* [Aaron Crickenberger](https://github.com/spiffxp), Google<br>* [Steve Kuznetsov](https://github.com/stevekuznetsov), Red Hat<br>|* [Slack](https://kubernetes.slack.com/messages/sig-testing)<br>* [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)<br> |[UI](sig-ui/README.md)|[ui](https://github.com/kubernetes/kubernetes/labels/sig%2Fui)|* [Sebastian Florek](https://github.com/floreks), Kubermatic<br>* [Marcin Maciaszczyk](https://github.com/maciaszczykm), Kubermatic<br>* [Shu Muto](https://github.com/shu-mutou), NEC<br>|* [Slack](https://kubernetes.slack.com/messages/sig-ui)<br>* [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)<br> |[Usability](sig-usability/README.md)|[usability](https://github.com/kubernetes/kubernetes/labels/sig%2Fusability)|* [Himanshu Pandey](https://github.com/hpandeycodeit), VMware<br>* [Gaby Moreno Cesar](https://github.com/morengab), IBM<br>* [Tasha Drew](https://github.com/tashimi), VMware<br>|* [Slack](https://kubernetes.slack.com/messages/sig-usability)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-usability)|* Regular SIG Meeting: [Tuesdays at 9:00 PT (Pacific Time) (every third week)](https://zoom.us/j/3832562240)<br> |[Windows](sig-windows/README.md)|[windows](https://github.com/kubernetes/kubernetes/labels/sig%2Fwindows)|* [Mark Rossetti](https://github.com/marosset), Microsoft<br>|* [Slack](https://kubernetes.slack.com/messages/sig-windows)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-windows)|* Backlog Refinement / Bug Triage Meeting: [Thursdays at 12:30 Eastern Time (ET) (biweekly)](https://zoom.us/j/94389601840?pwd=MCs2SEJQWG0zUWpBS3Nod0ZNMmVXQT09)<br>* Regular SIG Meeting: [Tuesdays at 12:30 Eastern Time (ET) (weekly)](https://zoom.us/j/96892680257?pwd=TVNyMzB4VVMwRGZnUkgzT1dnb2szZz09)<br>* Weekly CI Meeting: [Tuesdays at 12:15 Eastern Time (ET) (weekly)](https://zoom.us/j/96892680257?pwd=TVNyMzB4VVMwRGZnUkgzT1dnb2szZz09)<br> @@ -62,28 +62,27 @@ When the need arises, a [new SIG can be created](sig-wg-lifecycle.md) | Name | Label | Stakeholder SIGs |Organizers | Contact | Meetings | |------|-------|------------------|-----------|---------|----------| |[API Expression](wg-api-expression/README.md)|[api-expression](https://github.com/kubernetes/kubernetes/labels/wg%2Fapi-expression)|* API Machinery<br>* Architecture<br>|* [Antoine Pelisse](https://github.com/apelisse), Google<br>* [Kevin Wiesmueller](https://github.com/kwiesmueller), Google<br>|* [Slack](https://kubernetes.slack.com/messages/wg-api-expression)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-wg-api-expression)|* Regular WG Meeting: [Tuesdays at 9:30 PT (Pacific Time) (biweekly)](https://zoom.us/j/94238112084)<br> -|[Batch](wg-batch/README.md)|[batch](https://github.com/kubernetes/kubernetes/labels/wg%2Fbatch)|* Apps<br>* Autoscaling<br>* Node<br>* Scheduling<br>|* [Wei Huang](https://github.com/Huang-Wei), Apple<br>* [Abdullah Gharaibeh](https://github.com/ahg-g), Google<br>* [Danielle Lancashire](https://github.com/endocrimes), VMware<br>* [Maciej Szulik](https://github.com/soltysh), Red Hat<br>* [Swati Sehgal](https://github.com/swatisehgal), Red Hat<br>|* [Slack](https://kubernetes.slack.com/messages/wg-batch)<br>* [Mailing List](https://groups.google.com/a/kubernetes.io/g/wg-batch)|* Regular Meeting ([Calendar](https://calendar.google.com/calendar/embed?src=8ulop9k0jfpuo0t7kp8d9ubtj4%40group.calendar.google.com)): [Thursdays (starting March 3rd 2022)s at 7AM PT (Pacific Time) (biweekly)](https://zoom.us/j/98329676612?pwd=c0N2bVV1aTh2VzltckdXSitaZXBKQT09)<br> +|[Batch](wg-batch/README.md)|[batch](https://github.com/kubernetes/kubernetes/labels/wg%2Fbatch)|* Apps<br>* Autoscaling<br>* Node<br>* Scheduling<br>|* [Wei Huang](https://github.com/Huang-Wei), Apple<br>* [Abdullah Gharaibeh](https://github.com/ahg-g), Google<br>* [Danielle Lancashire](https://github.com/endocrimes), Independent<br>* [Maciej Szulik](https://github.com/soltysh), Red Hat<br>* [Swati Sehgal](https://github.com/swatisehgal), Red Hat<br>|* [Slack](https://kubernetes.slack.com/messages/wg-batch)<br>* [Mailing List](https://groups.google.com/a/kubernetes.io/g/wg-batch)|* Regular Meeting ([Calendar](https://calendar.google.com/calendar/embed?src=8ulop9k0jfpuo0t7kp8d9ubtj4%40group.calendar.google.com)): [Thursdays (starting March 3rd 2022)s at 7AM PT (Pacific Time) (biweekly)](https://zoom.us/j/98329676612?pwd=c0N2bVV1aTh2VzltckdXSitaZXBKQT09)<br> |[Data Protection](wg-data-protection/README.md)|[data-protection](https://github.com/kubernetes/kubernetes/labels/wg%2Fdata-protection)|* Apps<br>* Storage<br>|* [Xing Yang](https://github.com/xing-yang), VMware<br>* [Xiangqian Yu](https://github.com/yuxiangqian), Google<br>|* [Slack](https://kubernetes.slack.com/messages/wg-data-protection)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-data-protection)|* Regular WG Meeting: [Wednesdays at 9:00 PT (Pacific Time) (bi-weekly)](https://zoom.us/j/6933410772)<br> |[IoT Edge](wg-iot-edge/README.md)|[iot-edge](https://github.com/kubernetes/kubernetes/labels/wg%2Fiot-edge)|* Multicluster<br>* Network<br>|* [Steve Wong](https://github.com/cantbewong), VMware<br>* [Cindy Xing](https://github.com/cindyxing), Microsoft<br>* [Dejan Bosanac](https://github.com/dejanb), Red Hat<br>|* [Slack](https://kubernetes.slack.com/messages/wg-iot-edge)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-wg-iot-edge)|* APAC WG Meeting: [Wednesdays at 5:00 UTC (every four weeks)](https://zoom.us/j/91251176046?pwd=cmdqclovM3R3eDB1VlpuL1ZGU1hnZz09)<br>* Regular WG Meeting (Pacific Time): [Wednesdays at 09:00 PT (every four weeks)](https://zoom.us/j/92778512626?pwd=MXhlemwvYnhkQmkxeXllQ0Z5VGs4Zz09)<br> |[Multitenancy](wg-multitenancy/README.md)|[multitenancy](https://github.com/kubernetes/kubernetes/labels/wg%2Fmultitenancy)|* API Machinery<br>* Auth<br>* Network<br>* Node<br>* Scheduling<br>* Storage<br>|* [Sanjeev Rampal](https://github.com/srampal), Cisco<br>* [Tasha Drew](https://github.com/tashimi), VMware<br>|* [Slack](https://kubernetes.slack.com/messages/wg-multitenancy)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-wg-multitenancy)|* Regular WG Meeting: [Tuesdays at 11:00 PT (Pacific Time) (biweekly)](https://zoom.us/my/k8s.sig.auth)<br> |[Policy](wg-policy/README.md)|[policy](https://github.com/kubernetes/kubernetes/labels/wg%2Fpolicy)|* Architecture<br>* Auth<br>* Multicluster<br>* Network<br>* Node<br>* Scheduling<br>* Storage<br>|* [Jim Bugwadia](https://github.com/JimBugwadia), Kyverno/Nirmata<br>* [Robert Ficcaglia](https://github.com/rficcaglia), SunStone<br>|* [Slack](https://kubernetes.slack.com/messages/wg-policy)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-wg-policy)|* Regular WG Meeting: [Wednesdays at 8:00 PT (Pacific Time) (semimonthly)](https://zoom.us/j/7375677271)<br> |[Reliability](wg-reliability/README.md)|[reliability](https://github.com/kubernetes/kubernetes/labels/wg%2Freliability)|* Architecture<br>* Cluster Lifecycle<br>* Release<br>* Scalability<br>* Testing<br>|* [David Eads](https://github.com/deads2k), Red Hat<br>* [Steve Kuznetsov](https://github.com/stevekuznetsov), Red Hat<br>* [Wojciech Tyczynski](https://github.com/wojtek-t), Google<br>|* [Slack](https://kubernetes.slack.com/messages/wg-reliability)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-wg-reliability)|* Regular WG Meeting: [Mondays at 11:00 PT (Pacific Time) (biweekly)](https://zoom.us/j/97964505804?pwd=R3hzSnArQWJHYmdWUnpSUDh3aXhFUT09)<br> -|[Structured Logging](wg-structured-logging/README.md)|[structured-logging](https://github.com/kubernetes/kubernetes/labels/wg%2Fstructured-logging)|* API Machinery<br>* Architecture<br>* Cloud Provider<br>* Instrumentation<br>* Network<br>* Node<br>* Scheduling<br>* Storage<br>|* [Patrick Ohly](https://github.com/pohly), Intel<br>* [Marek Siarkowicz](https://github.com/serathius), Google<br>|* [Slack](https://kubernetes.slack.com/messages/wg-structured-logging)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-wg-structured-logging)|* Regular Meeting: [Thursdays at 14:30 UTC (biweekly)](https://zoom.us/j/96716142646?pwd=VmgrN29sbmhDREp3R0NtZlpGSlZ4Zz09)<br> +|[Structured Logging](wg-structured-logging/README.md)|[structured-logging](https://github.com/kubernetes/kubernetes/labels/wg%2Fstructured-logging)|* API Machinery<br>* Architecture<br>* Cloud Provider<br>* Instrumentation<br>* Network<br>* Node<br>* Scheduling<br>* Storage<br>|* [Patrick Ohly](https://github.com/pohly), Intel<br>* [Marek Siarkowicz](https://github.com/serathius), Google<br>|* [Slack](https://kubernetes.slack.com/messages/wg-structured-logging)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-wg-structured-logging)|* Regular Meeting: [Thursdays at 15:30 London-UK (biweekly)](https://zoom.us/j/96716142646?pwd=VmgrN29sbmhDREp3R0NtZlpGSlZ4Zz09)<br> ### User Groups | Name | Label |Organizers | Contact | Meetings | |------|-------|------------|--------|----------| -|[Big Data](ug-big-data/README.md)|[big-data](https://github.com/kubernetes/kubernetes/labels/ug%2Fbig-data)|* [Erik Erlandson](https://github.com/erikerlandson), Red Hat<br>* [Anirudh Ramanathan](https://github.com/foxish), Rockset<br>* [Yinan Li](https://github.com/liyinan926), Google<br>|* [Slack](https://kubernetes.slack.com/messages/ug-big-data)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-ug-big-data)|* Regular User Group Meeting: [Wednesdays at 18:00 UTC (biweekly)](https://zoom.us/my/ug.big.data)<br> |[VMware Users](ug-vmware-users/README.md)|[vmware-users](https://github.com/kubernetes/kubernetes/labels/ug%2Fvmware-users)|* [Steve Wong](https://github.com/cantbewong), VMware<br>* [Myles Gray](https://github.com/mylesagray), VMware<br>|* [Slack](https://kubernetes.slack.com/messages/ug-vmware)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-ug-vmware)|* Regular User Group Meeting: [Thursdays at 11:00 PT (Pacific Time) (monthly)](https://docs.google.com/document/d/1ujpqj4hhcIBrSCK2qn6J1r--3QyD96rfDjXTZQ7n7Mw/edit)<br> ### Committees | Name | Label | Members | Contact | |------|--------|---------|---------| -|[Code of Conduct](committee-code-of-conduct/README.md)|[code-of-conduct](https://github.com/kubernetes/kubernetes/labels/committee%2Fcode-of-conduct)|* [Danielle Lancashire](https://github.com/endocrimes), VMware<br>* [Hilliary Lipsig](https://github.com/hlipsig), RedHat<br>* [Jeremy Rickard](https://github.com/jeremyrickard), Microsoft<br>* [Nabarun Pal](https://github.com/palnabarun), VMware<br>* [Xander Grzywinski](https://github.com/salaxander), Microsoft<br>|* [Slack](https://kubernetes.slack.com/messages/code-of-conduct)<br>* [Private Mailing List](conduct@kubernetes.io) +|[Code of Conduct](committee-code-of-conduct/README.md)|[code-of-conduct](https://github.com/kubernetes/kubernetes/labels/committee%2Fcode-of-conduct)|* [Jason DeTiberus](https://github.com/detiber), Cisco<br>* [Danielle Lancashire](https://github.com/endocrimes), Independent<br>* [Hilliary Lipsig](https://github.com/hlipsig), RedHat<br>* [Jeremy Rickard](https://github.com/jeremyrickard), Microsoft<br>* [Xander Grzywinski](https://github.com/salaxander), Microsoft<br>|* [Slack](https://kubernetes.slack.com/messages/code-of-conduct)<br>* [Private Mailing List](conduct@kubernetes.io) |[Security Response](committee-security-response/README.md)|[security-response](https://github.com/kubernetes/kubernetes/labels/committee%2Fsecurity-response)|* [CJ Cullen](https://github.com/cjcullen), Google<br>* [Mo Khan](https://github.com/enj), Microsoft<br>* [Joel Smith](https://github.com/joelsmith), Red Hat<br>* [Luke Hinds](https://github.com/lukehinds), Red Hat<br>* [Micah Hausler](https://github.com/micahhausler), Amazon<br>* [Tabitha Sable](https://github.com/tabbysable), Datadog<br>* [Tim Allclair](https://github.com/tallclair), Google<br>|* [Private Mailing List](security@kubernetes.io) -|[Steering](committee-steering/README.md)|[steering](https://github.com/kubernetes/kubernetes/labels/committee%2Fsteering)|* [Christoph Blecker](https://github.com/cblecker), Red Hat<br>* [Davanum Srinivas](https://github.com/dims), VMware<br>* [Stephen Augustus](https://github.com/justaugustus), Cisco<br>* [Jordan Liggitt](https://github.com/liggitt), Google<br>* [Bob Killen](https://github.com/mrbobbytables), Google<br>* [Paris Pittman](https://github.com/parispittman), Apple<br>* [Tim Pepper](https://github.com/tpepper), VMware<br>|* [Slack](https://kubernetes.slack.com/messages/steering-committee)<br>* [Mailing List](https://groups.google.com/a/kubernetes.io/forum/#!forum/steering)<br>* [Private Mailing List](steering-private@kubernetes.io) +|[Steering](committee-steering/README.md)|[steering](https://github.com/kubernetes/kubernetes/labels/committee%2Fsteering)|* [Benjamin Elder](https://github.com/BenTheElder), Google<br>* [Christoph Blecker](https://github.com/cblecker), Red Hat<br>* [Carlos Tadeu Panato Jr.](https://github.com/cpanato), Chainguard, Inc<br>* [Stephen Augustus](https://github.com/justaugustus), Cisco<br>* [Bob Killen](https://github.com/mrbobbytables), Google<br>* [Nabarun Pal](https://github.com/palnabarun), VMware<br>* [Tim Pepper](https://github.com/tpepper), VMware<br>|* [Slack](https://kubernetes.slack.com/messages/steering-committee)<br>* [Mailing List](https://groups.google.com/a/kubernetes.io/forum/#!forum/steering)<br>* [Private Mailing List](steering-private@kubernetes.io) <!-- BEGIN CUSTOM CONTENT --> <!-- END CUSTOM CONTENT --> diff --git a/sig-multicluster/README.md b/sig-multicluster/README.md index e38bbb29..fc2b923f 100644 --- a/sig-multicluster/README.md +++ b/sig-multicluster/README.md @@ -63,6 +63,9 @@ The following [subprojects][subproject-definition] are owned by sig-multicluster ### mcs-api - **Owners:** - [kubernetes-sigs/mcs-api](https://github.com/kubernetes-sigs/mcs-api/blob/master/OWNERS) +### sig-multicluster-site +- **Owners:** + - [kubernetes-sigs/sig-multicluster-site](https://github.com/kubernetes-sigs/sig-multicluster-site/blob/main/OWNERS) ### work-api - **Owners:** - [kubernetes-sigs/work-api](https://github.com/kubernetes-sigs/work-api/blob/master/OWNERS) diff --git a/sig-network/README.md b/sig-network/README.md index c9c67b09..8ea4b0a2 100644 --- a/sig-network/README.md +++ b/sig-network/README.md @@ -20,7 +20,7 @@ The [charter](charter.md) defines the scope and governance of the Network Specia * [Meeting notes and Agenda](https://docs.google.com/document/d/1s5hQU0CB9ehjFukRmRHQ41f1FA8GX5_1Rv6nHW6NWAA/edit). * Gateway API Meeting: [Mondays at 15:00 PT (Pacific Time)](https://zoom.us/j/441530404) (weekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=15:00&tz=PT%20%28Pacific%20Time%29). * [Meeting notes and Agenda](https://docs.google.com/document/d/1eg-YjOHaQ7UD28htdNxBR3zufebozXKyI28cl2E11tU/edit). -* Network Policy API Meeting: [Mondays at 13:00 PT (Pacific Time)](https://zoom.us/j/96264742248) (bi-weekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=13:00&tz=PT%20%28Pacific%20Time%29). +* Network Policy API Meeting: [Tuesdays at 9:00 PT (Pacific Time)](https://zoom.us/j/96264742248) (bi-weekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=9:00&tz=PT%20%28Pacific%20Time%29). * [Meeting notes and Agenda](https://docs.google.com/document/d/1AtWQy2fNa4qXRag9cCp5_HsefD7bxKe3ea2RPn8jnSs). * SIG Network Ingress NGINX Meeting: [Thursdays at 8:00 PT (Pacific Time)](https://zoom.us/j/98377891310) (biweekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=8:00&tz=PT%20%28Pacific%20Time%29). * [Meeting notes and Agenda](https://docs.google.com/document/d/1DKlpcV6DAW0DsBrzh-OLkZvJQmABCVfRIRWBWjc4zOs/edit). @@ -80,6 +80,7 @@ The following [subprojects][subproject-definition] are owned by sig-network: ### gateway-api - **Owners:** - [kubernetes-sigs/gateway-api](https://github.com/kubernetes-sigs/gateway-api/blob/master/OWNERS) + - [kubernetes-sigs/ingress2gateway](https://github.com/kubernetes-sigs/ingress2gateway/blob/main/OWNERS) - [kubernetes/kubernetes/pkg/controller/endpoint](https://github.com/kubernetes/kubernetes/blob/master/pkg/controller/endpoint/OWNERS) - [kubernetes/kubernetes/pkg/proxy](https://github.com/kubernetes/kubernetes/blob/master/pkg/proxy/OWNERS) - [kubernetes/kubernetes/staging/src/k8s.io/cloud-provider/controllers/service](https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/cloud-provider/controllers/service/OWNERS) diff --git a/sig-network/role-sig-chair.md b/sig-network/role-sig-chair.md new file mode 100644 index 00000000..23e93cca --- /dev/null +++ b/sig-network/role-sig-chair.md @@ -0,0 +1,70 @@ +# Role: SIG Chair + +## Background + +Please see the +[standard description of a SIG chair](https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md#chair), +which does a good job describing the expectations of the more “administrative” +aspect of being a SIG chair. + +## What's expected + +Rather than repeat the doc linked above, this doc will just add some color. + +The minimum effective engagement for a SIG chair is to “run the show” (really +“make sure the show is running” - delegation is good!). That generally means +building an agenda for and running regular meetings, curating our +community-facing metadata, producing annual reports and community updates, +and acting as liaison to other groups (other SIGs and steering, mostly). + +This includes new-issue triage, either doing the triage or leading it (e.g. in +the regular SIG meetings), and KEP tracking. + +## Above and beyond + +The basic expectations above, as valuable as they are, should not require a +huge time commitment. SIG chairs who want to have more impact and are able to +commit more time can engage in a multitude of additional ways. While this +_can_ include being an active code contributor or SIG tech-lead, an effective +SIG chair does not **need** to be a code contributor. + +Some concrete things that SIGs need to do, which the chair-people can +facilitate, participate in, or even do themselves include: + * Active new-issue triage - go through new issues, ask for more info if + needed, apply labels, close or redirect “support” requests, CC people who + might have context, de-dup, triage-accept obvious bugs, ping submitters for + updates, etc. + * Backlog grooming - go through older issues, re-evaluate triage, de-dup, + aggregate similar issues, cross-link issues, link to KEPs, probe for + updates, etc. + * Manage issue and PR assignments - go through issues which are assigned to + people and see if progress is being made or if assignments are stale. + * Curate "help wanted" and "good first issue" issues - file new issues or + improve existing issues (e.g. by adding details or getting others to do so) + to enable new contributors to take them up. + * Manage project board(s) to organize information - things like KEPs, issues, + PRs, or in-progress dev efforts can usually benefit from organizing and + curation. + * Actively manage KEPs - track the KEP lifecycle, update metadata, ping KEP + owners for updates, contribute to KEP content and/or PRR, etc. + * Organize events - new member introductions, KubeCon meetups, local events, + etc. + * Actively solicit topics for regular meetings - reach out to KEP owners or + other efforts which could benefit from SIG discussion, or which other + attendees would benefit from hearing about. + * Docs - create, curate, edit, revise, or restructure docs (API docs, website + docs, etc.) related to the SIG. + * Check in and monitor subprojects - keep an eye out for stale / potential + new OWNERS to elevate or move to emeritus. + * ...get creative! + +Many of these things will need help from major technical contributors or even +the SIG tech-lead(s). SIG chairs are, first and foremost, facilitators, and +the SIG TLs are their partners. + +## Titles vs. actions + +In general, a SIG chair title is something given to people who are _already +doing the work_, rather than an invitation to begin doing it. Existing chairs +are expected to participate in succession planning and should seek to delegate +tasks, in part to build up new chairs. diff --git a/sig-node/OWNERS b/sig-node/OWNERS index dcf3663c..2ea840ee 100644 --- a/sig-node/OWNERS +++ b/sig-node/OWNERS @@ -2,11 +2,11 @@ reviewers: - sig-node-leads - - ehashman - SergeyKanzhelev approvers: - sig-node-leads - - ehashman - SergeyKanzhelev +emeritus_approvers: + - ehashman labels: - sig/node diff --git a/sig-node/README.md b/sig-node/README.md index 0ced890c..d24c3908 100644 --- a/sig-node/README.md +++ b/sig-node/README.md @@ -89,8 +89,10 @@ The following [subprojects][subproject-definition] are owned by sig-node: - [kubernetes/test-infra/config/jobs/kubernetes/node-problem-detector](https://github.com/kubernetes/test-infra/blob/master/config/jobs/kubernetes/node-problem-detector/OWNERS) - **Contact:** - Slack: [#node-problem-detector](https://kubernetes.slack.com/messages/node-problem-detector) -### noderesourcetopology-api +### resource-management - **Owners:** + - [kubernetes/kubernetes/staging/src/k8s.io/dynamic-resource-allocation](https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/dynamic-resource-allocation/OWNERS) + - [kubernetes-sigs/dra-example-driver](https://github.com/kubernetes-sigs/dra-example-driver/blob/main/OWNERS) - [kubernetes/noderesourcetopology-api](https://github.com/kubernetes/noderesourcetopology-api/blob/master/OWNERS) ### security-profiles-operator - **Owners:** diff --git a/sig-release/README.md b/sig-release/README.md index 6b06ef99..c0a79f5f 100644 --- a/sig-release/README.md +++ b/sig-release/README.md @@ -26,6 +26,7 @@ The [charter](charter.md) defines the scope and governance of the Release Specia ### Chairs The Chairs of the SIG run operations and processes governing the SIG. +* Jeremy Rickard (**[@jeremyrickard](https://github.com/jeremyrickard)**), Microsoft * Stephen Augustus (**[@justaugustus](https://github.com/justaugustus)**), Cisco * Sascha Grunert (**[@saschagrunert](https://github.com/saschagrunert)**), Red Hat @@ -33,8 +34,8 @@ The Chairs of the SIG run operations and processes governing the SIG. The Technical Leads of the SIG establish new subprojects, decommission existing subprojects, and resolve cross-subproject technical issues and decisions. +* Verónica López (**[@Verolop](https://github.com/Verolop)**), PlanetScale * Carlos Tadeu Panato Jr. (**[@cpanato](https://github.com/cpanato)**), Chainguard, Inc -* Jeremy Rickard (**[@jeremyrickard](https://github.com/jeremyrickard)**), Microsoft * Adolfo García Veytia (**[@puerco](https://github.com/puerco)**), Chainguard, Inc ## Emeritus Leads @@ -54,7 +55,7 @@ subprojects, and resolve cross-subproject technical issues and decisions. - [@kubernetes/sig-release](https://github.com/orgs/kubernetes/teams/sig-release) - SIG Release Members - [@kubernetes/sig-release-admins](https://github.com/orgs/kubernetes/teams/sig-release-admins) - Admins for SIG Release repositories - [@kubernetes/sig-release-leads](https://github.com/orgs/kubernetes/teams/sig-release-leads) - Chairs, Technical Leads, and Program Managers for SIG Release -- Steering Committee Liaison: Davanum Srinivas (**[@dims](https://github.com/dims)**) +- Steering Committee Liaison: Nabarun Pal (**[@palnabarun](https://github.com/palnabarun)**) ## Working Groups @@ -75,6 +76,7 @@ The Release Engineering subproject is responsible for the [process/procedures](h - [kubernetes-sigs/release-notes](https://github.com/kubernetes-sigs/release-notes/blob/master/OWNERS) - [kubernetes-sigs/release-sdk](https://github.com/kubernetes-sigs/release-sdk/blob/main/OWNERS) - [kubernetes-sigs/release-utils](https://github.com/kubernetes-sigs/release-utils/blob/main/OWNERS) + - [kubernetes-sigs/tejolote](https://github.com/kubernetes-sigs/tejolote/blob/main/OWNERS) - [kubernetes-sigs/testgrid-json-exporter](https://github.com/kubernetes-sigs/testgrid-json-exporter/blob/main/OWNERS) - [kubernetes-sigs/zeitgeist](https://github.com/kubernetes-sigs/zeitgeist/blob/master/OWNERS) - [kubernetes/kubernetes/CHANGELOG](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/OWNERS) @@ -105,9 +107,14 @@ The Kubernetes Release Team is responsible for the day-to-day work required to s - **Contact:** - [Mailing List](https://groups.google.com/a/kubernetes.io/g/release-team) - GitHub Teams: - - [@kubernetes/ci-signal](https://github.com/orgs/kubernetes/teams/ci-signal) + - [@kubernetes/release-ci-signal](https://github.com/orgs/kubernetes/teams/release-ci-signal) - [@kubernetes/release-team](https://github.com/orgs/kubernetes/teams/release-team) - Members of the current Release Team and subproject owners + - [@kubernetes/release-team-bug-triage](https://github.com/orgs/kubernetes/teams/release-team-bug-triage) + - [@kubernetes/release-team-comms](https://github.com/orgs/kubernetes/teams/release-team-comms) + - [@kubernetes/release-team-docs](https://github.com/orgs/kubernetes/teams/release-team-docs) + - [@kubernetes/release-team-enhancements](https://github.com/orgs/kubernetes/teams/release-team-enhancements) - [@kubernetes/release-team-leads](https://github.com/orgs/kubernetes/teams/release-team-leads) - Release Team Leads for the current Kubernetes release cycle + - [@kubernetes/release-team-release-notes](https://github.com/orgs/kubernetes/teams/release-team-release-notes) ### SIG Release Process Documentation Documents and processes related to SIG Release - **Owners:** diff --git a/sig-scalability/configs-and-limits/faq.md b/sig-scalability/configs-and-limits/faq.md index 6b5c4ac0..33f9daa5 100644 --- a/sig-scalability/configs-and-limits/faq.md +++ b/sig-scalability/configs-and-limits/faq.md @@ -62,6 +62,29 @@ summarized as: - if you can't keep your object size below 100kB, reach out to SIG Scalability and discuss the usecase to see how we can make it performant +### How should we code client applications to improve scalability? + +As noted above, LIST requests can be particularly expensive. So consider the following guidelines when working with lists +that may have more than a few thousand small objects, or more than a few hundred large ones. + +1. When defining a new resource type (new CRD) consider expected numbers +of objects that will exist (numbers of CRs). See guidelines for small, medium and large objects +[here](https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/95-custom-resource-definitions#scale-targets-for-ga). +1. When LIST-ing, the load on etcd and API Server depends primarily on the number of objects that _exist_, not the number that are _returned_. So even if you are using a field selector to filter the list and retrieve only a small number of results, these guidelines still apply. (The only exception is retrieving a single object by `metadata.name`, which is fast.) +1. If your code needs to hold an up-to-date list of objects in memory, +avoid repeated LIST calls if possible. Instead consider using the +`Informer` classes that are provided in most Kubernetes client +libraries. Informers automatically combine LIST and WATCH functionality +to efficiently maintain an in-memory collection. +1. If `Informer`s don't suit your needs, consider whether you really need strong consistency. Do you really need to see the most recent data, up to the _exact moment in time_ when you issued the query? If you don't need that, set `ResourceVersion=0`. This will cause your request to be served from the API Server's cache instead of from etcd. Read the [documentation about ResourceVersions](https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions) carefully to understand how it will affect the freshness of the data you receive. +1. If you can't use `Informer`s AND you can't use the API Server cache, + then be sure to [read large lists in chunks](https://kubernetes.io/docs/reference/using-api/api-concepts/#retrieving-large-results-sets-in-chunks). +1. Additionally, if you cannot use `Informer`s, you should also consider how _often_ your application LISTs the resources. In particular, after you read the last object in a large list, do not _immediately_ re-query the same list. Wait a while instead. Don't list more often than you need to. +1. Consider the number of instances of your client application which will be running. For instance, +there is a big difference between having +just one controller listing objects, versus having pods on every node +doing the same thing (e.g. in a daemonset). If there will be many instances of your client application +periodically listing large numbers of objects, your solution will NOT scale to large clusters. ### How do you setup clusters for scalability testing? diff --git a/sig-scalability/slos/pod_startup_latency.md b/sig-scalability/slos/pod_startup_latency.md index 84bde2fe..57611f1c 100644 --- a/sig-scalability/slos/pod_startup_latency.md +++ b/sig-scalability/slos/pod_startup_latency.md @@ -7,8 +7,9 @@ | __Official__ | Startup latency of schedulable<sup>[1](#footnote1)</sup> stateless<sup>[2](#footnote2)</sup> pods, excluding time to pull images and run init containers, measured from pod creation timestamp to when all its containers are reported as started and observed via watch, measured as 99th percentile over last 5 minutes | In default Kubernetes installation, 99th percentile per cluster-day <= 5s | | __WIP__ | Startup latency of schedulable<sup>[1](#footnote1)</sup> stateful<sup>[3](#footnote3)</sup> pods, excluding time to pull images, run init containers, provision volumes (in delayed binding mode) and unmount/detach volumes (from previous pod if needed), measured from pod creation timestamp to when all its containers are reported as started and observed via watch, measured as 99th percentile over last 5 minutes | In default Kubernetes installation, 99th percentile per cluster-day <= X where X depends on storage provider | -<a name="footnote1">[1\]</a>By schedulable pod we mean a pod that can be -scheduled in the cluster without causing any preemption. +<a name="footnote1">[1\]</a>By schedulable pod we mean a pod that has to be immediately +(without actions from any other components) schedulable in the cluster without +causing any preemption. <a name="footnote2">[2\]</a>A `stateless pod` is defined as a pod that doesn't mount volumes with sources other than secrets, config maps, downward API and diff --git a/sig-scheduling/README.md b/sig-scheduling/README.md index 1d8c248d..9ce64d96 100644 --- a/sig-scheduling/README.md +++ b/sig-scheduling/README.md @@ -57,7 +57,7 @@ subprojects, and resolve cross-subproject technical issues and decisions. - [@kubernetes/sig-scheduling-pr-reviews](https://github.com/orgs/kubernetes/teams/sig-scheduling-pr-reviews) - PR Reviews - [@kubernetes/sig-scheduling-proposals](https://github.com/orgs/kubernetes/teams/sig-scheduling-proposals) - Design Proposals - [@kubernetes/sig-scheduling-test-failures](https://github.com/orgs/kubernetes/teams/sig-scheduling-test-failures) - Test Failures and Triage -- Steering Committee Liaison: Jordan Liggitt (**[@liggitt](https://github.com/liggitt)**) +- Steering Committee Liaison: Benjamin Elder (**[@BenTheElder](https://github.com/BenTheElder)**) ## Working Groups diff --git a/sig-security/README.md b/sig-security/README.md index 55b7cd4a..30feaaaf 100644 --- a/sig-security/README.md +++ b/sig-security/README.md @@ -33,7 +33,7 @@ The Chairs of the SIG run operations and processes governing the SIG. - GitHub Teams: - [@kubernetes/sig-security-leads](https://github.com/orgs/kubernetes/teams/sig-security-leads) - SIG Security Leads - [@kubernetes/sig-security-pr-reviews](https://github.com/orgs/kubernetes/teams/sig-security-pr-reviews) - SIG Security PR review notifications -- Steering Committee Liaison: Paris Pittman (**[@parispittman](https://github.com/parispittman)**) +- Steering Committee Liaison: Carlos Tadeu Panato Jr. (**[@cpanato](https://github.com/cpanato)**) ## Subprojects diff --git a/sig-storage/CONTRIBUTING.md b/sig-storage/CONTRIBUTING.md index a8426735..2bfbf2bb 100644 --- a/sig-storage/CONTRIBUTING.md +++ b/sig-storage/CONTRIBUTING.md @@ -4,6 +4,10 @@ We recommend the following presentations, docs, and videos to help get familiar | Date | Title | Link | Description | | --- | --- | --- | --- | +| 2023 January 23 | PV/PVC Controller Deep Dive | [Slides](https://docs.google.com/presentation/d/1XI_XzxlAYF6dqRfQQsoBd-UWRHssH2Ts5KwK5NDIMgg/edit) | A walk through of the PV controller source code following the Dynamic Volume Provisioning with CSI scenario | +| 2022 November 9 | Kubernetes SIG Storage Deep Dive | [Video](https://www.youtube.com/watch?v=_XXn3-yDZA0) | An overview and update of SIG Storage by Xing Yang, VMware & Mauricio Poppe, Google at KubeCon NA 2022. | +| 2022 May 16 | Kubernetes SIG Storage Deep Dive | [Video](https://www.youtube.com/watch?v=dsEeQqRSg74) | An overview and update of SIG Storage by Xing Yang, VMware & Jan Šafránek, Red Hat at KubeCon Europe 2022. | +| 2020 November 20 | Intro & Deep Dive: Kubernetes SIG-Storage | [Video](https://www.youtube.com/watch?v=rnCdvWToPPM&t=2s) | An overview and update of SIG Storage by Xing Yang and Michelle Au at KubeCon/CloudNativeCon NA 2020. | | 2020 November 20 | Intro & Deep Dive: Kubernetes SIG-Storage | [Video](https://www.youtube.com/watch?v=rnCdvWToPPM&t=2s) | An overview and update of SIG Storage by Xing Yang and Michelle Au at KubeCon/CloudNativeCon NA 2020. | | 2020 November 20 | Intro & Deep Dive: Kubernetes Data Protection WG | [Video](https://www.youtube.com/watch?v=g8HEQnLVo04) | An overview of Data Protection WG by Xing Yang and Xiangqian Yu at KubeCon/CloudNativeCon NA 2020. | | 2020 November 18 | Beyond File and Block Storage in Kubernetes | [Video](https://www.youtube.com/watch?v=Y3GgJb71Cwo) | An introduction of Container Object Storage Interface (COSI) by Sidhartha Mani at KubeCon/CloudNativeCon NA 2020. | @@ -21,20 +25,20 @@ We recommend the following presentations, docs, and videos to help get familiar | 2016 March 25 | The State of State | [Video](https://www.youtube.com/watch?v=jsTQ24CLRhI&index=6&list=PLosInM-8doqcBy3BirmLM4S_pmox6qTw3) | The State of State at KubeCon/CloudNativeCon EU 2016 by Matthew Bates | 2016 March 25 | Kubernetes Storage 101 | [Video](https://www.youtube.com/watch?v=ZqTHe6Xj0Ek&list=PLosInM-8doqcBy3BirmLM4S_pmox6qTw3&index=38) | Kubernetes Storage 101 at KubeCon/CloudNativeCon EU 2016 by Erin Boyd -Keep in mind that these artifacts reflect the state of the art at the time they were created. In Kubernetes we try very hard to maintain backwards compatibility, but Kubernetes is a fast moving project and we do add features going forward and attending the Storage SIG meetings and the Storage SIG Google group are both good ways of continually staying up to speed. +Keep in mind that these artifacts reflect the state of the art at the time they were created. In Kubernetes we try very hard to maintain backwards compatibility, but Kubernetes is a fast moving project and we do add features going forward and attending the Storage SIG meetings and the Storage SIG Google group are both good ways of continually staying up to speed. ### How to help We love having folks help in any capacity! We recommend you start by reading the overall [Kubernetes contributor's guide](/contributors/guide) ### Helping with Features -If you have a feature idea, please submit a feature proposal PR first and put it on the [Storage SIG Meeting Agenda](https://docs.google.com/document/d/1-8KEG8AjAgKznS9NFm3qWqkGyCHmvU6HVl0sk5hwoAE/edit#heading=h.bag869lp4lyz). -Our PR review bandwidth is fairly small, as such, we strongly recommend that you do not start writing the implementation before you've -discussed the feature with the community. This helps the community understand what you're trying to do with the proposal and helps the -community and you work through the approach until there is consensus. The community then will also be able to communicate with you how -soon they will be able to review your proposal PR, to set expectations. However, generally speaking once the your proposal PR is merged, -your implementation PR review and merge should go fairly quickly as the review is focused on the implementation quality and not -what you are proposing. We are really trying to improve our test coverage and documentation, so please include functional tests, e2e tests +If you have a feature idea, please submit a feature proposal PR first and put it on the [Storage SIG Meeting Agenda](https://docs.google.com/document/d/1-8KEG8AjAgKznS9NFm3qWqkGyCHmvU6HVl0sk5hwoAE/edit#heading=h.bag869lp4lyz). +Our PR review bandwidth is fairly small, as such, we strongly recommend that you do not start writing the implementation before you've +discussed the feature with the community. This helps the community understand what you're trying to do with the proposal and helps the +community and you work through the approach until there is consensus. The community then will also be able to communicate with you how +soon they will be able to review your proposal PR, to set expectations. However, generally speaking once the your proposal PR is merged, +your implementation PR review and merge should go fairly quickly as the review is focused on the implementation quality and not +what you are proposing. We are really trying to improve our test coverage and documentation, so please include functional tests, e2e tests and documentation in your implementation PR. ### Helping with Issues diff --git a/sig-storage/README.md b/sig-storage/README.md index b1d211a9..ca35d876 100644 --- a/sig-storage/README.md +++ b/sig-storage/README.md @@ -51,7 +51,7 @@ subprojects, and resolve cross-subproject technical issues and decisions. - [@kubernetes/sig-storage-pr-reviews](https://github.com/orgs/kubernetes/teams/sig-storage-pr-reviews) - PR Reviews - [@kubernetes/sig-storage-proposals](https://github.com/orgs/kubernetes/teams/sig-storage-proposals) - Design Proposals - [@kubernetes/sig-storage-test-failures](https://github.com/orgs/kubernetes/teams/sig-storage-test-failures) - Test Failures and Triage -- Steering Committee Liaison: Paris Pittman (**[@parispittman](https://github.com/parispittman)**) +- Steering Committee Liaison: Carlos Tadeu Panato Jr. (**[@cpanato](https://github.com/cpanato)**) ## Working Groups @@ -90,12 +90,10 @@ The following [subprojects][subproject-definition] are owned by sig-storage: - **Owners:** - [kubernetes-csi/cluster-driver-registrar](https://github.com/kubernetes-csi/cluster-driver-registrar/blob/master/OWNERS) - [kubernetes-csi/csi-driver-host-path](https://github.com/kubernetes-csi/csi-driver-host-path/blob/master/OWNERS) - - [kubernetes-csi/csi-driver-image-populator](https://github.com/kubernetes-csi/csi-driver-image-populator/blob/master/OWNERS) - [kubernetes-csi/csi-driver-iscsi](https://github.com/kubernetes-csi/csi-driver-iscsi/blob/master/OWNERS) - [kubernetes-csi/csi-driver-nfs](https://github.com/kubernetes-csi/csi-driver-nfs/blob/master/OWNERS) - [kubernetes-csi/csi-driver-nvmf](https://github.com/kubernetes-csi/csi-driver-nvmf/blob/master/OWNERS) - [kubernetes-csi/csi-driver-smb](https://github.com/kubernetes-csi/csi-driver-smb/blob/master/OWNERS) - - [kubernetes-csi/csi-lib-fc](https://github.com/kubernetes-csi/csi-lib-fc/blob/master/OWNERS) - [kubernetes-csi/csi-lib-iscsi](https://github.com/kubernetes-csi/csi-lib-iscsi/blob/master/OWNERS) - [kubernetes-csi/csi-lib-utils](https://github.com/kubernetes-csi/csi-lib-utils/blob/master/OWNERS) - [kubernetes-csi/csi-proxy](https://github.com/kubernetes-csi/csi-proxy/blob/master/OWNERS) @@ -111,9 +109,7 @@ The following [subprojects][subproject-definition] are owned by sig-storage: - [kubernetes-csi/kubernetes-csi.github.io](https://github.com/kubernetes-csi/kubernetes-csi.github.io/blob/master/OWNERS) - [kubernetes-csi/livenessprobe](https://github.com/kubernetes-csi/livenessprobe/blob/master/OWNERS) - [kubernetes-csi/node-driver-registrar](https://github.com/kubernetes-csi/node-driver-registrar/blob/master/OWNERS) - - [kubernetes/csi-api](https://github.com/kubernetes/csi-api/blob/master/OWNERS) - [kubernetes/csi-translation-lib](https://github.com/kubernetes/csi-translation-lib/blob/master/OWNERS) - - [kubernetes/kubernetes/staging/src/k8s.io/csi-api](https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/csi-api/OWNERS) - [kubernetes/kubernetes/staging/src/k8s.io/csi-translation-lib](https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/csi-translation-lib/OWNERS) ### mount-utils - **Owners:** diff --git a/sig-testing/README.md b/sig-testing/README.md index 06602656..e2a8f2d9 100644 --- a/sig-testing/README.md +++ b/sig-testing/README.md @@ -24,6 +24,7 @@ The [charter](charter.md) defines the scope and governance of the Testing Specia The Chairs of the SIG run operations and processes governing the SIG. * Benjamin Elder (**[@BenTheElder](https://github.com/BenTheElder)**), Google +* Michelle Shepardson (**[@michelle192837](https://github.com/michelle192837)**), Google * Aaron Crickenberger (**[@spiffxp](https://github.com/spiffxp)**), Google * Steve Kuznetsov (**[@stevekuznetsov](https://github.com/stevekuznetsov)**), Red Hat @@ -33,7 +34,9 @@ subprojects, and resolve cross-subproject technical issues and decisions. * Benjamin Elder (**[@BenTheElder](https://github.com/BenTheElder)**), Google * Alvaro Aleman (**[@alvaroaleman](https://github.com/alvaroaleman)**), Red Hat +* Antonio Ojea (**[@aojea](https://github.com/aojea)**), Google * Cole Wagner (**[@cjwagner](https://github.com/cjwagner)**), Google +* Patrick Ohly (**[@pohly](https://github.com/pohly)**), Intel ## Emeritus Leads @@ -47,7 +50,7 @@ subprojects, and resolve cross-subproject technical issues and decisions. - GitHub Teams: - [@kubernetes/sig-testing](https://github.com/orgs/kubernetes/teams/sig-testing) - General Discussion - [@kubernetes/sig-testing-pr-reviews](https://github.com/orgs/kubernetes/teams/sig-testing-pr-reviews) - PR Reviews -- Steering Committee Liaison: Paris Pittman (**[@parispittman](https://github.com/parispittman)**) +- Steering Committee Liaison: Carlos Tadeu Panato Jr. (**[@cpanato](https://github.com/cpanato)**) ## Working Groups diff --git a/sig-usability/README.md b/sig-usability/README.md index c335b4cd..d4ad3c5a 100644 --- a/sig-usability/README.md +++ b/sig-usability/README.md @@ -43,7 +43,7 @@ The Chairs of the SIG run operations and processes governing the SIG. - [@kubernetes/sig-usability-misc](https://github.com/orgs/kubernetes/teams/sig-usability-misc) - General Discussion - [@kubernetes/sig-usability-pr-reviews](https://github.com/orgs/kubernetes/teams/sig-usability-pr-reviews) - PR Reviews - [@kubernetes/sig-usability-proposals](https://github.com/orgs/kubernetes/teams/sig-usability-proposals) - Design Proposals -- Steering Committee Liaison: Davanum Srinivas (**[@dims](https://github.com/dims)**) +- Steering Committee Liaison: Nabarun Pal (**[@palnabarun](https://github.com/palnabarun)**) ## Subprojects diff --git a/sig-windows/README.md b/sig-windows/README.md index 4074161f..c8e054e2 100644 --- a/sig-windows/README.md +++ b/sig-windows/README.md @@ -51,7 +51,7 @@ subprojects, and resolve cross-subproject technical issues and decisions. - [@kubernetes/sig-windows-bugs](https://github.com/orgs/kubernetes/teams/sig-windows-bugs) - Bug Triage and Troubleshooting - [@kubernetes/sig-windows-feature-requests](https://github.com/orgs/kubernetes/teams/sig-windows-feature-requests) - Feature Requests - [@kubernetes/sig-windows-misc](https://github.com/orgs/kubernetes/teams/sig-windows-misc) - General Discussion -- Steering Committee Liaison: Jordan Liggitt (**[@liggitt](https://github.com/liggitt)**) +- Steering Committee Liaison: Benjamin Elder (**[@BenTheElder](https://github.com/BenTheElder)**) ## Subprojects @@ -65,6 +65,9 @@ The following [subprojects][subproject-definition] are owned by sig-windows: ### windows-samples - **Owners:** - [kubernetes-sigs/sig-windows-samples](https://github.com/kubernetes-sigs/sig-windows-samples/blob/master/OWNERS) +### windows-service-proxy +- **Owners:** + - [kubernetes-sigs/windows-service-proxy](https://github.com/kubernetes-sigs/windows-service-proxy/blob/main/OWNERS) ### windows-testing - **Owners:** - [kubernetes-sigs/windows-testing](https://github.com/kubernetes-sigs/windows-testing/blob/master/OWNERS) @@ -27,7 +27,7 @@ sigs: meetings: - description: Kubebuilder and Controller Runtime Meeting day: Thursday - time: "09:00" + time: "11:00" tz: PT (Pacific Time) frequency: biweekly archive_url: https://docs.google.com/document/d/1Ih-2cgg1bUrLwLVTB9tADlPcVdgnuMNBGbUl4D-0TIk/edit?usp=sharing @@ -58,8 +58,8 @@ sigs: - name: sig-api-machinery-test-failures description: Test Failures and Triage liaison: - github: dims - name: Davanum Srinivas + github: palnabarun + name: Nabarun Pal subprojects: - name: component-base owners: @@ -264,7 +264,7 @@ sigs: company: Red Hat - github: dims name: Davanum Srinivas - company: VMware + company: Amazon Web Services - github: johnbelamaric name: John Belamaric company: Google @@ -328,8 +328,8 @@ sigs: - name: sig-architecture-test-failures description: Test Failures and Triage liaison: - github: liggitt - name: Jordan Liggitt + github: BenTheElder + name: Benjamin Elder subprojects: - name: architecture-and-api-governance description: '[Described below](#architecture-and-api-governance-1)' @@ -565,6 +565,11 @@ sigs: - https://raw.githubusercontent.com/kubernetes/kubernetes/master/pkg/kubelet/token/OWNERS - https://raw.githubusercontent.com/kubernetes/kubernetes/master/pkg/serviceaccount/OWNERS - https://raw.githubusercontent.com/kubernetes/kubernetes/master/plugin/pkg/admission/serviceaccount/OWNERS + - name: sig-auth-tools + description: | + Tooling to automate the SIG Auth project boards + owners: + - https://raw.githubusercontent.com/kubernetes-sigs/sig-auth-tools/main/OWNERS - dir: sig-autoscaling name: Autoscaling mission_statement: > @@ -669,7 +674,7 @@ sigs: day: Wednesday time: "09:00" tz: PT (Pacific Time) - frequency: monthly + frequency: every four weeks url: https://zoom.us/j/288426795?pwd=UDdoYnFyNjBiS1RHcXRxS1BCNy9wUT09 archive_url: https://docs.google.com/document/d/1r0YElcXt6G5mOWxwZiXgGu_X6he3F--wKwg-9UBc29I/edit?usp=sharing recordings_url: https://www.youtube.com/playlist?list=PL69nYSiGNLP28HaTzSlFe6RJVxpFmbUvF @@ -685,7 +690,7 @@ sigs: day: Wednesday time: "09:00" tz: PT (Pacific Time) - frequency: monthly + frequency: every four weeks url: https://zoom.us/j/288426795?pwd=UDdoYnFyNjBiS1RHcXRxS1BCNy9wUT09 archive_url: https://docs.google.com/document/d/1r0YElcXt6G5mOWxwZiXgGu_X6he3F--wKwg-9UBc29I/edit?usp=sharing recordings_url: https://www.youtube.com/playlist?list=PL69nYSiGNLP28HaTzSlFe6RJVxpFmbUvF @@ -861,12 +866,13 @@ sigs: recordings_url: https://www.youtube.com/playlist?list=PLWpmsLfcyyD7HAhlLTuwmI9KWuoiaN9nO - name: provider-aws owners: - - https://raw.githubusercontent.com/kubernetes-sigs/aws-alb-ingress-controller/master/OWNERS - https://raw.githubusercontent.com/kubernetes-sigs/aws-ebs-csi-driver/master/OWNERS - https://raw.githubusercontent.com/kubernetes-sigs/aws-efs-csi-driver/master/OWNERS - https://raw.githubusercontent.com/kubernetes-sigs/aws-encryption-provider/master/OWNERS + - https://raw.githubusercontent.com/kubernetes-sigs/aws-file-cache-csi-driver/main/OWNERS - https://raw.githubusercontent.com/kubernetes-sigs/aws-fsx-csi-driver/master/OWNERS - https://raw.githubusercontent.com/kubernetes-sigs/aws-iam-authenticator/master/OWNERS + - https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/main/OWNERS - https://raw.githubusercontent.com/kubernetes-sigs/provider-aws-test-infra/master/OWNERS - https://raw.githubusercontent.com/kubernetes/cloud-provider-aws/master/OWNERS meetings: @@ -887,10 +893,10 @@ sigs: - https://raw.githubusercontent.com/kubernetes-sigs/cloud-provider-azure/master/OWNERS meetings: - description: Azure Subproject Meeting - day: Monday - time: "18:00" + day: Tuesday + time: "16:00" tz: PT (Pacific Time) - frequency: monthly - third Monday + frequency: monthly - third Tuesday url: https://zoom.us/j/586836662 archive_url: https://docs.google.com/document/d/1SpxvmOgHDhnA72Z0lbhBffrfe9inQxZkU9xqlafOW9k/edit recordings_url: https://www.youtube.com/playlist?list=PL69nYSiGNLP2JNdHwB8GxRs2mikK7zyc4 @@ -980,7 +986,7 @@ sigs: company: VMware - github: vincepri name: Vince Prignano - company: VMware + company: Red Hat tech_leads: - github: fabriziopandini name: Fabrizio Pandini @@ -1008,8 +1014,8 @@ sigs: - name: sig-cluster-lifecycle description: SIG Cluster Lifecycle mailing list liaison: - github: dims - name: Davanum Srinivas + github: palnabarun + name: Nabarun Pal subprojects: - name: cluster-addons description: A project for figuring out the best way to install, manage and deliver @@ -1044,6 +1050,11 @@ sigs: url: https://zoom.us/j/861487554?pwd=dTVGVVFCblFJc0VBbkFqQlU0dHpiUT09 archive_url: https://docs.google.com/document/d/1ushaVqAKYnZ2VN_aa3GyKlS4kEd6bSug13xaXOakAQI/edit recordings_url: https://www.youtube.com/playlist?list=PL69nYSiGNLP29D0nYgAGWt1ZFqS9Z7lw4 + - name: cluster-api-addon-provider-helm + description: Implementation of Cluster Add-on Provider for Helm, an add-on orchestration + solution for Cluster API using Helm. + owners: + - https://github.com/kubernetes-sigs/cluster-api-addon-provider-helm/blob/main/OWNERS - name: cluster-api-operator description: Leverages a declarative API and an operator to empower admins to handle the lifecycle of Cluster API providers within the management cluster @@ -1276,6 +1287,12 @@ sigs: mailing_list: https://groups.google.com/forum/#!forum/kubernetes-sig-cluster-lifecycle owners: - https://raw.githubusercontent.com/kubernetes-sigs/kubespray/master/OWNERS + - name: logical-cluster + description: A set of APIs to improve the Kubernetes user experience for cluster + administration by offering utilities to interact with fleet of clusters which + can be managed by Cluster API, or other entities (like cloud providers). + owners: + - https://raw.githubusercontent.com/kubernetes-sigs/logical-cluster/main/OWNERS - name: minikube description: Implements a local Kubernetes cluster for application development on macOS, Linux, and Windows @@ -1283,6 +1300,7 @@ sigs: slack: minikube mailing_list: https://groups.google.com/forum/#!forum/kubernetes-sig-cluster-lifecycle owners: + - https://raw.githubusercontent.com/kubernetes-sigs/minikube-gui/main/OWNERS - https://raw.githubusercontent.com/kubernetes/minikube/master/OWNERS meetings: - description: minikube office hours @@ -1406,22 +1424,6 @@ sigs: slack: sig-contribex owners: - https://raw.githubusercontent.com/kubernetes/community/master/events/OWNERS - meetings: - - description: Office Hours European Edition (Open Q&A for end-user kubernetes - related questions) - day: Wednesday - time: "09:00" - tz: ET (Eastern Time) - frequency: monthly on 3rd Wednesday - url: https://hackmd.io/@k8s/office-hours - - description: Office Hours Western Edition (Open Q&A for end-user kubernetes - related questions) - day: Wednesday - time: "12:00" - tz: ET (Eastern Time) - frequency: monthly on 3rd Wednesday - archive_url: https://hackmd.io/@k8s/office-hours - recordings_url: https://www.youtube.com/playlist?list=PL69nYSiGNLP3azFUvYJjGn45YbF6C-uIg - name: github-management description: Manages and controls Github permissions, repos, and groups, including Org Membership. @@ -1447,8 +1449,7 @@ sigs: recordings_url: https://www.youtube.com/playlist?list=PL69nYSiGNLP2x_48wbOPO0vXQgNTm_xxr - name: mentoring description: Oversees and develops programs for helping contributors ascend the - contributor ladder, including the New Contributor Workshops, Meet Our Contributors, - and other programs. + contributor ladder, including the New Contributor Workshops, and other programs. owners: - https://raw.githubusercontent.com/kubernetes-sigs/contributor-katacoda/main/OWNERS - https://raw.githubusercontent.com/kubernetes-sigs/contributor-playground/master/OWNERS @@ -1592,8 +1593,8 @@ sigs: - name: sig-docs-zh-owners description: Chinese language content liaison: - github: parispittman - name: Paris Pittman + github: cpanato + name: Carlos Tadeu Panato Jr. subprojects: - name: kubernetes-blog owners: @@ -1621,7 +1622,7 @@ sigs: chairs: - github: ehashman name: Elana Hashman - company: Red Hat + company: Apple - github: logicalhan name: Han Kang company: Google @@ -1706,6 +1707,9 @@ sigs: owners: - https://raw.githubusercontent.com/kubernetes-sigs/logtools/main/OWNERS - https://raw.githubusercontent.com/kubernetes/kubernetes/master/staging/src/k8s.io/component-base/logs/OWNERS + - name: usage-metrics-collector + owners: + - https://raw.githubusercontent.com/kubernetes-sigs/usage-metrics-collector/main/OWNERS - dir: sig-k8s-infra name: K8s Infra mission_statement: > @@ -1723,10 +1727,10 @@ sigs: chairs: - github: ameukam name: Arnaud Meukam - company: Alter Way + company: VMware - github: dims name: Davanum Srinivas - company: VMware + company: Amazon Web Services tech_leads: - github: spiffxp name: Aaron Crickenberger @@ -1811,6 +1815,23 @@ sigs: url: https://zoom.us/j/93109963352?pwd=SHJTcFR2bVg1akYxSDREUWQzaldrQT09 archive_url: http://bit.ly/sig-k8s-infra-notes recordings_url: http://bit.ly/sig-k8s-infra-playlist + - name: porche + description: A custom HTTP redirector serving Kubernetes binaries from existing + vendor supported and approved storage services. + contact: + slack: sig-k8s-infra + mailing_list: https://groups.google.com/forum/#!forum/kubernetes-sig-k8s-infra + owners: + - https://raw.githubusercontent.com/kubernetes-sigs/porche/main/OWNERS + meetings: + - description: Regular SIG Meeting + day: Wednesday + time: "20:00" + tz: UTC + frequency: bi-weekly + url: https://zoom.us/j/93109963352?pwd=SHJTcFR2bVg1akYxSDREUWQzaldrQT09 + archive_url: http://bit.ly/sig-k8s-infra-notes + recordings_url: http://bit.ly/sig-k8s-infra-playlist - name: registry.k8s.io description: A custom HTTP redirector serving Kubernetes container image blobs from existing vendor supported container registries. @@ -1894,6 +1915,9 @@ sigs: - name: mcs-api owners: - https://raw.githubusercontent.com/kubernetes-sigs/mcs-api/master/OWNERS + - name: sig-multicluster-site + owners: + - https://raw.githubusercontent.com/kubernetes-sigs/sig-multicluster-site/main/OWNERS - name: work-api owners: - https://raw.githubusercontent.com/kubernetes-sigs/work-api/master/OWNERS @@ -1938,8 +1962,8 @@ sigs: url: https://zoom.us/j/441530404 archive_url: https://docs.google.com/document/d/1eg-YjOHaQ7UD28htdNxBR3zufebozXKyI28cl2E11tU/edit - description: Network Policy API Meeting - day: Monday - time: "13:00" + day: Tuesday + time: "9:00" tz: PT (Pacific Time) frequency: bi-weekly url: https://zoom.us/j/96264742248 @@ -2010,6 +2034,7 @@ sigs: slack: sig-network-gateway-api owners: - https://raw.githubusercontent.com/kubernetes-sigs/gateway-api/master/OWNERS + - https://raw.githubusercontent.com/kubernetes-sigs/ingress2gateway/main/OWNERS - https://raw.githubusercontent.com/kubernetes/kubernetes/master/pkg/controller/endpoint/OWNERS - https://raw.githubusercontent.com/kubernetes/kubernetes/master/pkg/proxy/OWNERS - https://raw.githubusercontent.com/kubernetes/kubernetes/master/staging/src/k8s.io/cloud-provider/controllers/service/OWNERS @@ -2125,8 +2150,10 @@ sigs: owners: - https://raw.githubusercontent.com/kubernetes/node-problem-detector/master/OWNERS - https://raw.githubusercontent.com/kubernetes/test-infra/master/config/jobs/kubernetes/node-problem-detector/OWNERS - - name: noderesourcetopology-api + - name: resource-management owners: + - https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/dynamic-resource-allocation/OWNERS + - https://raw.githubusercontent.com/kubernetes-sigs/dra-example-driver/main/OWNERS - https://raw.githubusercontent.com/kubernetes/noderesourcetopology-api/master/OWNERS - name: security-profiles-operator contact: @@ -2142,6 +2169,9 @@ sigs: label: release leadership: chairs: + - github: jeremyrickard + name: Jeremy Rickard + company: Microsoft - github: justaugustus name: Stephen Augustus company: Cisco @@ -2149,12 +2179,12 @@ sigs: name: Sascha Grunert company: Red Hat tech_leads: + - github: Verolop + name: Verónica López + company: PlanetScale - github: cpanato name: Carlos Tadeu Panato Jr. company: Chainguard, Inc - - github: jeremyrickard - name: Jeremy Rickard - company: Microsoft - github: puerco name: Adolfo García Veytia company: Chainguard, Inc @@ -2200,8 +2230,8 @@ sigs: - name: sig-release-leads description: Chairs, Technical Leads, and Program Managers for SIG Release liaison: - github: dims - name: Davanum Srinivas + github: palnabarun + name: Nabarun Pal subprojects: - name: Release Engineering description: | @@ -2227,6 +2257,7 @@ sigs: - https://raw.githubusercontent.com/kubernetes-sigs/release-notes/master/OWNERS - https://raw.githubusercontent.com/kubernetes-sigs/release-sdk/main/OWNERS - https://raw.githubusercontent.com/kubernetes-sigs/release-utils/main/OWNERS + - https://raw.githubusercontent.com/kubernetes-sigs/tejolote/main/OWNERS - https://raw.githubusercontent.com/kubernetes-sigs/testgrid-json-exporter/main/OWNERS - https://raw.githubusercontent.com/kubernetes-sigs/zeitgeist/master/OWNERS - https://raw.githubusercontent.com/kubernetes/kubernetes/master/CHANGELOG/OWNERS @@ -2244,11 +2275,16 @@ sigs: contact: mailing_list: https://groups.google.com/a/kubernetes.io/g/release-team teams: - - name: ci-signal + - name: release-ci-signal - name: release-team description: Members of the current Release Team and subproject owners + - name: release-team-bug-triage + - name: release-team-comms + - name: release-team-docs + - name: release-team-enhancements - name: release-team-leads description: Release Team Leads for the current Kubernetes release cycle + - name: release-team-release-notes owners: - https://raw.githubusercontent.com/kubernetes-sigs/release-team-shadow-stats/main/OWNERS - https://raw.githubusercontent.com/kubernetes/sig-release/master/release-team/OWNERS @@ -2422,8 +2458,8 @@ sigs: - name: sig-scheduling-test-failures description: Test Failures and Triage liaison: - github: liggitt - name: Jordan Liggitt + github: BenTheElder + name: Benjamin Elder subprojects: - name: cluster-capacity owners: @@ -2485,8 +2521,8 @@ sigs: - name: sig-security-pr-reviews description: SIG Security PR review notifications liaison: - github: parispittman - name: Paris Pittman + github: cpanato + name: Carlos Tadeu Panato Jr. subprojects: - name: security-audit description: Third Party Security Audit @@ -2576,8 +2612,8 @@ sigs: - name: sig-storage-test-failures description: Test Failures and Triage liaison: - github: parispittman - name: Paris Pittman + github: cpanato + name: Carlos Tadeu Panato Jr. subprojects: - name: external-storage owners: @@ -2604,12 +2640,10 @@ sigs: owners: - https://raw.githubusercontent.com/kubernetes-csi/cluster-driver-registrar/master/OWNERS - https://raw.githubusercontent.com/kubernetes-csi/csi-driver-host-path/master/OWNERS - - https://raw.githubusercontent.com/kubernetes-csi/csi-driver-image-populator/master/OWNERS - https://raw.githubusercontent.com/kubernetes-csi/csi-driver-iscsi/master/OWNERS - https://raw.githubusercontent.com/kubernetes-csi/csi-driver-nfs/master/OWNERS - https://raw.githubusercontent.com/kubernetes-csi/csi-driver-nvmf/master/OWNERS - https://raw.githubusercontent.com/kubernetes-csi/csi-driver-smb/master/OWNERS - - https://raw.githubusercontent.com/kubernetes-csi/csi-lib-fc/master/OWNERS - https://raw.githubusercontent.com/kubernetes-csi/csi-lib-iscsi/master/OWNERS - https://raw.githubusercontent.com/kubernetes-csi/csi-lib-utils/master/OWNERS - https://raw.githubusercontent.com/kubernetes-csi/csi-proxy/master/OWNERS @@ -2625,9 +2659,7 @@ sigs: - https://raw.githubusercontent.com/kubernetes-csi/kubernetes-csi.github.io/master/OWNERS - https://raw.githubusercontent.com/kubernetes-csi/livenessprobe/master/OWNERS - https://raw.githubusercontent.com/kubernetes-csi/node-driver-registrar/master/OWNERS - - https://raw.githubusercontent.com/kubernetes/csi-api/master/OWNERS - https://raw.githubusercontent.com/kubernetes/csi-translation-lib/master/OWNERS - - https://raw.githubusercontent.com/kubernetes/kubernetes/master/staging/src/k8s.io/csi-api/OWNERS - https://raw.githubusercontent.com/kubernetes/kubernetes/master/staging/src/k8s.io/csi-translation-lib/OWNERS - name: mount-utils owners: @@ -2658,6 +2690,9 @@ sigs: - github: BenTheElder name: Benjamin Elder company: Google + - github: michelle192837 + name: Michelle Shepardson + company: Google - github: spiffxp name: Aaron Crickenberger company: Google @@ -2671,9 +2706,15 @@ sigs: - github: alvaroaleman name: Alvaro Aleman company: Red Hat + - github: aojea + name: Antonio Ojea + company: Google - github: cjwagner name: Cole Wagner company: Google + - github: pohly + name: Patrick Ohly + company: Intel emeritus_leads: - github: fejta name: Erick Fejta @@ -2697,8 +2738,8 @@ sigs: - name: sig-testing-pr-reviews description: PR Reviews liaison: - github: parispittman - name: Paris Pittman + github: cpanato + name: Carlos Tadeu Panato Jr. subprojects: - name: boskos description: | @@ -2847,8 +2888,8 @@ sigs: - name: sig-usability-proposals description: Design Proposals liaison: - github: dims - name: Davanum Srinivas + github: palnabarun + name: Nabarun Pal subprojects: - name: sig-usability owners: @@ -2917,8 +2958,8 @@ sigs: - name: sig-windows-misc description: General Discussion liaison: - github: liggitt - name: Jordan Liggitt + github: BenTheElder + name: Benjamin Elder subprojects: - name: windows-gmsa owners: @@ -2929,6 +2970,9 @@ sigs: - name: windows-samples owners: - https://raw.githubusercontent.com/kubernetes-sigs/sig-windows-samples/master/OWNERS + - name: windows-service-proxy + owners: + - https://raw.githubusercontent.com/kubernetes-sigs/windows-service-proxy/main/OWNERS - name: windows-testing owners: - https://raw.githubusercontent.com/kubernetes-sigs/windows-testing/master/OWNERS @@ -2970,8 +3014,8 @@ workinggroups: slack: wg-api-expression mailing_list: https://groups.google.com/forum/#!forum/kubernetes-wg-api-expression liaison: - github: liggitt - name: Jordan Liggitt + github: BenTheElder + name: Benjamin Elder - dir: wg-batch name: Batch mission_statement: > @@ -2996,7 +3040,7 @@ workinggroups: company: Google - github: endocrimes name: Danielle Lancashire - company: VMware + company: Independent - github: soltysh name: Maciej Szulik company: Red Hat @@ -3143,8 +3187,8 @@ workinggroups: slack: wg-multitenancy mailing_list: https://groups.google.com/forum/#!forum/kubernetes-wg-multitenancy liaison: - github: liggitt - name: Jordan Liggitt + github: BenTheElder + name: Benjamin Elder - dir: wg-policy name: Policy mission_statement: > @@ -3249,8 +3293,8 @@ workinggroups: meetings: - description: Regular Meeting day: Thursday - time: "14:30" - tz: UTC + time: "15:30" + tz: London-UK frequency: biweekly url: https://zoom.us/j/96716142646?pwd=VmgrN29sbmhDREp3R0NtZlpGSlZ4Zz09 archive_url: https://docs.google.com/document/d/1R9bZ34L9vR1ftH0dFeOp-j50lLh5ijKVwwXJ3LDrY4I/edit?usp=sharing @@ -3259,47 +3303,9 @@ workinggroups: slack: wg-structured-logging mailing_list: https://groups.google.com/forum/#!forum/kubernetes-wg-structured-logging liaison: - github: dims - name: Davanum Srinivas + github: palnabarun + name: Nabarun Pal usergroups: -- dir: ug-big-data - name: Big Data - mission_statement: > - Serve as a community resource for advising big data and data science related software - projects on techniques and best practices for integrating with Kubernetes. Represents - the concerns of users from big data communities to Kubernetes for the purposes - of driving new features and other enhancements, based on big data use cases. - - label: big-data - leadership: - chairs: - - github: erikerlandson - name: Erik Erlandson - company: Red Hat - - github: foxish - name: Anirudh Ramanathan - company: Rockset - - github: liyinan926 - name: Yinan Li - company: Google - meetings: - - description: Regular User Group Meeting - day: Wednesday - time: "18:00" - tz: UTC - frequency: biweekly - url: https://zoom.us/my/ug.big.data - archive_url: https://docs.google.com/document/d/1pnF38NF6N5eM8DlK088XUW85Vms4V2uTsGZvSp8MNIA/edit - recordings_url: https://docs.google.com/document/d/1pnF38NF6N5eM8DlK088XUW85Vms4V2uTsGZvSp8MNIA/edit - contact: - slack: ug-big-data - mailing_list: https://groups.google.com/forum/#!forum/kubernetes-ug-big-data - teams: - - name: ug-big-data - description: General Discussion - liaison: - github: tpepper - name: Tim Pepper - dir: ug-vmware-users name: VMware Users mission_statement: > @@ -3346,18 +3352,18 @@ committees: label: code-of-conduct leadership: chairs: + - github: detiber + name: Jason DeTiberus + company: Cisco - github: endocrimes name: Danielle Lancashire - company: VMware + company: Independent - github: hlipsig name: Hilliary Lipsig company: RedHat - github: jeremyrickard name: Jeremy Rickard company: Microsoft - - github: palnabarun - name: Nabarun Pal - company: VMware - github: salaxander name: Xander Grzywinski company: Microsoft @@ -3372,10 +3378,14 @@ committees: name: Celeste Horgan - github: cpanato name: Carlos Tadeu Panato Jr. + - github: eparis + name: Eric Paris - github: jdumars name: Jaice Singer DuMars - github: karenhchu name: Karen Chu + - github: palnabarun + name: Nabarun Pal - github: parispittman name: Paris Pittman - github: tashimi @@ -3453,24 +3463,24 @@ committees: label: steering leadership: chairs: + - github: BenTheElder + name: Benjamin Elder + company: Google - github: cblecker name: Christoph Blecker company: Red Hat - - github: dims - name: Davanum Srinivas - company: VMware + - github: cpanato + name: Carlos Tadeu Panato Jr. + company: Chainguard, Inc - github: justaugustus name: Stephen Augustus company: Cisco - - github: liggitt - name: Jordan Liggitt - company: Google - github: mrbobbytables name: Bob Killen company: Google - - github: parispittman - name: Paris Pittman - company: Apple + - github: palnabarun + name: Nabarun Pal + company: VMware - github: tpepper name: Tim Pepper company: VMware diff --git a/wg-api-expression/README.md b/wg-api-expression/README.md index 0e8abd94..e2ed0967 100644 --- a/wg-api-expression/README.md +++ b/wg-api-expression/README.md @@ -30,7 +30,7 @@ Enable API authors to better serve API consumers, by improving and documenting a - Slack: [#wg-api-expression](https://kubernetes.slack.com/messages/wg-api-expression) - [Mailing list](https://groups.google.com/forum/#!forum/kubernetes-wg-api-expression) - [Open Community Issues/PRs](https://github.com/kubernetes/community/labels/wg%2Fapi-expression) -- Steering Committee Liaison: Jordan Liggitt (**[@liggitt](https://github.com/liggitt)**) +- Steering Committee Liaison: Benjamin Elder (**[@BenTheElder](https://github.com/BenTheElder)**) <!-- BEGIN CUSTOM CONTENT --> ## Full Mission Statement diff --git a/wg-batch/README.md b/wg-batch/README.md index d25d89d9..2f884897 100644 --- a/wg-batch/README.md +++ b/wg-batch/README.md @@ -28,7 +28,7 @@ The [charter](charter.md) defines the scope and governance of the Batch Working * Wei Huang (**[@Huang-Wei](https://github.com/Huang-Wei)**), Apple * Abdullah Gharaibeh (**[@ahg-g](https://github.com/ahg-g)**), Google -* Danielle Lancashire (**[@endocrimes](https://github.com/endocrimes)**), VMware +* Danielle Lancashire (**[@endocrimes](https://github.com/endocrimes)**), Independent * Maciej Szulik (**[@soltysh](https://github.com/soltysh)**), Red Hat * Swati Sehgal (**[@swatisehgal](https://github.com/swatisehgal)**), Red Hat diff --git a/wg-multitenancy/README.md b/wg-multitenancy/README.md index fc5493d5..f0af114d 100644 --- a/wg-multitenancy/README.md +++ b/wg-multitenancy/README.md @@ -37,7 +37,7 @@ Define the models of multitenancy that Kubernetes will support. Discuss and exec - Slack: [#wg-multitenancy](https://kubernetes.slack.com/messages/wg-multitenancy) - [Mailing list](https://groups.google.com/forum/#!forum/kubernetes-wg-multitenancy) - [Open Community Issues/PRs](https://github.com/kubernetes/community/labels/wg%2Fmultitenancy) -- Steering Committee Liaison: Jordan Liggitt (**[@liggitt](https://github.com/liggitt)**) +- Steering Committee Liaison: Benjamin Elder (**[@BenTheElder](https://github.com/BenTheElder)**) <!-- BEGIN CUSTOM CONTENT --> <!-- END CUSTOM CONTENT --> diff --git a/wg-structured-logging/README.md b/wg-structured-logging/README.md index 9da2a96d..c2a233cd 100644 --- a/wg-structured-logging/README.md +++ b/wg-structured-logging/README.md @@ -24,7 +24,7 @@ The [charter](charter.md) defines the scope and governance of the Structured Log ## Meetings *Joining the [mailing list](https://groups.google.com/forum/#!forum/kubernetes-wg-structured-logging) for the group will typically add invites for the following meetings to your calendar.* -* Regular Meeting: [Thursdays at 14:30 UTC](https://zoom.us/j/96716142646?pwd=VmgrN29sbmhDREp3R0NtZlpGSlZ4Zz09) (biweekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=14:30&tz=UTC). +* Regular Meeting: [Thursdays at 15:30 London-UK](https://zoom.us/j/96716142646?pwd=VmgrN29sbmhDREp3R0NtZlpGSlZ4Zz09) (biweekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=15:30&tz=London-UK). * [Meeting notes and Agenda](https://docs.google.com/document/d/1R9bZ34L9vR1ftH0dFeOp-j50lLh5ijKVwwXJ3LDrY4I/edit?usp=sharing). * [Meeting recordings](https://www.youtube.com/playlist?list=PL69nYSiGNLP2GY3so1z2Cnkvkt5A_x1Aw). @@ -37,7 +37,7 @@ The [charter](charter.md) defines the scope and governance of the Structured Log - Slack: [#wg-structured-logging](https://kubernetes.slack.com/messages/wg-structured-logging) - [Mailing list](https://groups.google.com/forum/#!forum/kubernetes-wg-structured-logging) - [Open Community Issues/PRs](https://github.com/kubernetes/community/labels/wg%2Fstructured-logging) -- Steering Committee Liaison: Davanum Srinivas (**[@dims](https://github.com/dims)**) +- Steering Committee Liaison: Nabarun Pal (**[@palnabarun](https://github.com/palnabarun)**) <!-- BEGIN CUSTOM CONTENT --> <!-- END CUSTOM CONTENT --> |
