diff options
| author | Ayushman <53306550+chetak123@users.noreply.github.com> | 2022-01-05 11:06:32 +0530 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-01-04 21:36:32 -0800 |
| commit | 737df3cb8d324fde312f8e3c6684f6c1e9c5c310 (patch) | |
| tree | 5da885f9d4510d684360917d950b09b18a2a6b64 /committee-steering | |
| parent | 3e644ed46dcd3cd7798c92d534c9614c1460e1ee (diff) | |
Changed all instances of k-dev@ and kubernetes-dev@ to dev@kubernetes.io (#6311)
* Changed all instancesof k-dev@ and kubernetes-dev@ to dev@kubernetes.io
Changes Removed From archive
updated the link
changes made
csv undo
changed links
* Fix last two instances of googlegroups.com
* Revert changes to election docs for past elections
Co-authored-by: Christoph Blecker <admin@toph.ca>
Diffstat (limited to 'committee-steering')
| -rw-r--r-- | committee-steering/governance/README.md | 4 | ||||
| -rw-r--r-- | committee-steering/governance/sig-governance.md | 4 |
2 files changed, 4 insertions, 4 deletions
diff --git a/committee-steering/governance/README.md b/committee-steering/governance/README.md index bd372e2c..8fda6940 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 [kubernetes-dev@googlegroups.com] and/or announcing at the community meeting are a good ways to do this. + Sending mail to [dev@kubernetes.io] and/or announcing at the community meeting are a good ways to do this. If there are questions about this process please reach out to the steering committee at [steering@kubernetes.io]. @@ -68,4 +68,4 @@ See [frequently asked questions] [sigs.yaml]: https://github.com/kubernetes/community/blob/master/sigs.yaml [sig-architecture example]: ../../sig-architecture/charter.md [steering@kubernetes.io]: mailto:steering@kubernetes.io -[kubernetes-dev@googlegroups.com]: mailto:kubernetes-dev@googlegroups.com +[dev@kubernetes.io]: mailto:dev@kubernetes.io diff --git a/committee-steering/governance/sig-governance.md b/committee-steering/governance/sig-governance.md index 77510546..fc1e6108 100644 --- a/committee-steering/governance/sig-governance.md +++ b/committee-steering/governance/sig-governance.md @@ -14,7 +14,7 @@ December repo - Record meetings and make them publicly available on the [Kubernetes Community YouTube playlist] -- Report activity with the community via the kubernetes-dev@ mailing list at +- 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 @@ -187,7 +187,7 @@ Other roles... duties from Chairs and/or Tech Leads on a non-temporary basis - *SHOULD* be documented in SIG charters if the role has delegation away from a sig-governance.md listed role -- *SHOULD* be sent to kubernetes-dev@googlegroups.com for awareness as a notice +- *SHOULD* be sent to dev@kubernetes.io for awareness as a notice and a lazy consensus period when they are newly created - *MAY* Fill in for another named role on a temporary basis #### Subproject Creation |