kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

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>
This commit is contained in:
Ayushman 2022-01-05 11:06:32 +05:30 committed by GitHub
parent 3e644ed46d
commit 737df3cb8d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
17 changed files with 30 additions and 30 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
committee-steering/governance/README.md
View File

@ -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

4
committee-steering/governance/sig-governance.md
View File

@ -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

2
communication/best-practices.md
View File

@ -36,7 +36,7 @@ Create a filter following the procedure below:
label by choosing **New label...** in the dropdown list.
- Click on the **Create filter**.
- Create filter directly for lists:
- **Matches:** list:"kubernetes-dev@googlegroups.com"
- **Matches:** list:"dev@kubernetes.io"
- **Do this:** Apply label "lists/kubernetes-dev"

2
communication/mailing-list-guidelines.md
View File

@ -246,7 +246,7 @@ invites on the shared calendar for an invite to be sent to members of the group.
- Create and share your _"meeting notes"_ Google doc with the following
permissions settings:
- **Can edit** for members of the newly created Mailing List.
- **Can comment** for `kubernetes-dev@googlegroups.com`
- **Can comment** for `dev@kubernetes.io`
- **View only** for anyone with the link. **NOTE:** Depending on
employer organization policy, this may not be possible to configure. The
document should be copied over to an account without the restriction and

4
communication/marketing-team/storytelling-resources/multichannel-communications.md
View File

@ -13,7 +13,7 @@ Our motive is as follows:
## Outbound and inbound communications
All outbound communications will have a single source of truth in kubernetes-dev@googlegroups.com.
All outbound communications will have a single source of truth in dev@kubernetes.io.
Justification for this canonical location:
@ -53,7 +53,7 @@ Based on these tiers, communication will flow through different channels and may
These channels will be used for written communication and tips for using them effectively:
* kubernetes-dev@googlegroups.com
* dev@kubernetes.io
* Single source of truth
* Make sure you're not burying the lead, action items should be clearly stated
* Slack

4
community-membership.md
View File

@ -44,7 +44,7 @@ remain active contributors to the community.
- Filing or commenting on issues on GitHub
- Contributing to SIG, subproject, or community discussions (e.g. meetings, Slack, email discussion
forums, Stack Overflow)
- Subscribed to [kubernetes-dev@googlegroups.com]
- Subscribed to [dev@kubernetes.io]
- Have read the [contributor guide]
- Actively contributing to 1 or more subprojects.
- Sponsored by 2 reviewers. **Note the following requirements for sponsors**:
@ -263,7 +263,7 @@ before being able to contribute effectively.
[Kubernetes GitHub Admin team]: /github-management/README.md#github-administration-team
[Kubernetes GitHub organizations]: /github-management#actively-used-github-organizations
[Kubernetes org]: https://github.com/kubernetes
[kubernetes-dev@googlegroups.com]: https://groups.google.com/forum/#!forum/kubernetes-dev
[dev@kubernetes.io]: https://groups.google.com/a/kubernetes.io/group/dev
[kubernetes-sigs]: https://github.com/kubernetes-sigs
[membership request]: https://github.com/kubernetes/org/issues/new?assignees=&labels=area%2Fgithub-membership&template=membership.yml&title=REQUEST%3A+New+membership+for+%3Cyour-GH-handle%3E
[membership template]: https://github.com/kubernetes/org/blob/main/.github/ISSUE_TEMPLATE/membership.yml

2
contributors/devel/sig-architecture/api_changes.md
View File

@ -516,7 +516,7 @@ eventually removed wholesale, as described in the [deprecation policy](https://k
If your change is going to be backward incompatible or might be a breaking
change for API consumers, please send an announcement to
`kubernetes-dev@googlegroups.com` before the change gets in. If you are unsure,
`dev@kubernetes.io` before the change gets in. If you are unsure,
ask. Also make sure that the change gets documented in the release notes for the
next release by labeling the PR with the "release-note-action-required" github label.

2
contributors/devel/sig-node/e2e-node-tests.md
View File

@ -47,7 +47,7 @@ make test-e2e-node PRINT_HELP=y
Why run tests *remotely*? Tests will be run in a customized testing environment. This environment closely mimics the pre- and post- submit testing performed by the project.
Prerequisites:
- [Join the googlegroup](https://groups.google.com/forum/#!forum/kubernetes-dev) `kubernetes-dev@googlegroups.com`
- [Join the googlegroup](https://groups.google.com/a/kubernetes.io/group/dev) `dev@kubernetes.io`
- *This provides read access to the node test images.*
- Setup a [Google Cloud Platform](https://cloud.google.com/) account and project with Google Compute Engine enabled
- Install and setup the [gcloud sdk](https://cloud.google.com/sdk/downloads)

2
contributors/guide/issue-triage.md
View File

@ -242,7 +242,7 @@ These should be directed to the following:
### User Support Response: Example
If you see support questions on kubernetes-dev@googlegroups.com or issues asking for
If you see support questions on dev@kubernetes.io or issues asking for
support, try to redirect them to Discuss. Example response:
```code

4
events/events-team/best-practices.md
View File

@ -62,7 +62,7 @@ If the event is being held during KubeCon/CloudNativeCon it's important to get a
The Hallway Track is listed as the favorite track at every event. The social/celebration is a longer hallway track that doesn't interfere with content. The social should have fun activities!
## Communication and Advertising
[kubernetes-dev@googlegroups.com][k-dev] is our artery for contributor communication and should be the main news network for contributor events.
[dev@kubernetes.io][k-dev] is our artery for contributor communication and should be the main news network for contributor events.
Other channels:
Slack - [#contributor-summit], [#kubecon], [#kubernetes-contributors]
[Twitter]
@ -117,7 +117,7 @@ Links to docs that aren't a fit for markdown:
[blog post example]: https://kubernetes.io/blog/2018/10/16/kubernetes-2018-north-american-contributor-summit/
[welcome slides]: https://docs.google.com/presentation/d/11eDR_0Dl_MBbeoMDF_mQaJC3shnnd6buhIVei2Ke0SM/edit#slide=id.p
[project board]: https://github.com/orgs/kubernetes/projects
[k-dev]: (https://groups.google.com/forum/#!forum/kubernetes-dev)
[k-dev]: (https://groups.google.com/a/kubernetes.io/group/dev)
[#contributor-summit]: (https://kubernetes.slack.com/messages/contributor-summit)
[#kubecon]: (https://kubernetes.slack.com/messages/kubecon)
[#kubernetes-contributors]: (https://kubernetes.slack.com/messages/kubernetes-contributors)

2
mentoring/programs/google-summer-of-code.md
View File

@ -23,7 +23,7 @@ This [slide deck](https://docs.google.com/presentation/d/1JqcALpsg07eH665ZXQrIvO
## Communication
- Mailing List: development announcements and discussions appear on the Google group `kubernetes-dev` (send mail to kubernetes-dev@googlegroups.com).
- Mailing List: development announcements and discussions appear on the Google group `kubernetes-dev` (send mail to dev@kubernetes.io).
- Slack: #gsoc-apps channel on the Kubernetes Slack. You can get an invite [here](http://slack.k8s.io/).
## Contribute

2
mentoring/programs/group-mentee-guide.md
View File

@ -65,7 +65,7 @@ TODO: add more here
- #meet-our-contributors
- #pr-reviews
- mailing lists
- kubernetes-dev@googlegroups.com
- dev@kubernetes.io
- your respective sig (ie - kubernetes-sig-cli@googlegroups.com)
- contributor office hours
- Kubernetes Community Office Hours

8
sig-contributor-experience/charter.md
View File

@ -15,7 +15,7 @@ We do this by listening - whether it’s through our roadshows to SIG meetings,
- Establish policies, standards and procedures for the use, [moderation], and management of all public platforms officially used by the project, including but not limited to:
- [discuss.kubernetes.io]
- [GitHub Management]
- [Mailing lists] / Google groups for the project as a whole (eg: kubernetes-dev@googlegroups.com) and for individual sigs and wgs where the Chairs have provided us ownership
- [Mailing lists] / Google groups for the project as a whole (eg: dev@kubernetes.io) and for individual sigs and wgs where the Chairs have provided us ownership
- [Slack]
- [/kubernetescommunity] YouTube channel
- [Zoom]
@ -56,13 +56,13 @@ We cross-cut all SIGs and WGs to deliver the following processes:
When implementing policy changes we strive to balance responding quickly to the needs of the community and ensuring a disruption-free experience for project contributors. As such, the amount of notice we provide and the amount of consensus we seek is driven by our estimation of risk. We don't measure risk objectively at this time, but estimate it based on these parameters:
- Low-risk changes impact a small number (<4) of SIGs, WGs, or repos, do not break existing contributor workflows, and are easy to roll back. When implementing low-risk changes we:
- Socialize on kubernetes-sig-contribex@googlegroups.com and our weekly update calls
- We will go to each lead, their mailing lists, slack channel, and/or their update meetings and ask for feedback and a [lazy consensus] process. We will follow up with a post to [kubernetes-dev@]googlegroups.com mailing list
- We will go to each lead, their mailing lists, slack channel, and/or their update meetings and ask for feedback and a [lazy consensus] process. We will follow up with a post to [dev@kubernetes.io] mailing list
- High-risk changes impact a large number (>4) of SIGs, WGs, or repos, break existing contributor workflows, and are not easy to roll back. When implementing high-risk changes we:
- Socialize on kubernetes-sig-contribex@googlegroups.com and our weekly update calls
- Seek [lazy consensus] with a time box of at least 72 business hours with a GitHub issue link (or proposal if not applicable) to the following mailing lists:
- [kubernetes-sig-contribex@]googlegroups.com
- leads@kubernetes.io
- [kubernetes-dev@]googlegroups.com with the GitHub issue link including the subject [NOTICE]: $announcement
- [dev@kubernetes.io] with the GitHub issue link including the subject [NOTICE]: $announcement
- We will also announce it at the Kubernetes Community Meeting
- Depending on how wide of an ecosystem change this is, we may also slack, blog, tweet, and use other channels to get the word out.
- Our standard time box is 72 business hours; however, there may be situations where we need to act quickly but the time period will always be clear and upfront.
@ -109,7 +109,7 @@ Chairs and Technical Leads
[Kubernetes Charter README]: https://git.k8s.io/community/committee-steering/governance/README.md
[lazy consensus]: http://en.osswiki.info/concepts/lazy_consensus
[Contributor Experience Special Interest Group]: https://groups.google.com/forum/#!forum/kubernetes-sig-contribex
[kubernetes-dev@]: https://groups.google.com/forum/#!forum/kubernetes-dev
[dev@kubernetes.io]: https://groups.google.com/a/kubernetes.io/group/dev
[@kubernetesio]: https://www.twitter.com/kubernetesio
[r/kubernetes]: https://kubernetes.reddit.com
[Google Summer of Code]: https://git.k8s.io/community/mentoring/programs/google-summer-of-code.md

2
sig-k8s-infra/charter.md
View File

@ -203,7 +203,7 @@ expect from a globally distributed open source project.
[Kubernetes Charter README]: https://git.k8s.io/community/committee-steering/governance/README.md
[lazy consensus]: http://en.osswiki.info/concepts/lazy_consensus
[kubernetes-dev@]: https://groups.google.com/forum/#!forum/kubernetes-dev
[dev@kubernetes.io]: https://groups.google.com/a/kubernetes.io/group/dev
[sig-k8s-infra@]: https://groups.google.com/forum/#!forum/kubernetes-sig-k8s-infra
[kubernetes/k8s.io]: https://git.k8s.io/k8s.io
[`sigs.yaml`]: https://git.k8s.io/community/sigs.yaml

6
sig-testing/charter.md
View File

@ -75,12 +75,12 @@ time.
- **Medium risk** changes may impact existing contributor workflows, should be
easy to roll back, and may impact all of the project's repos. These should
be shared with SIG Contributor Experience, may require a lazy consensus
issue with [kubernetes-dev@] notice.
issue with [dev@kubernetes.io] notice.
- **High risk changes** likely break existing contributor workflows, may be
difficult to roll back, and likely impact all of the project's repos. These
require a consultation with SIG Contributor Experience, and a lazy consensus
issue with [kubernetes-dev@] notice.
issue with [dev@kubernetes.io] notice.
### Out of Scope
@ -131,6 +131,6 @@ Subprojects are created by Tech Leads following the process defined in [sig-gove
[triage]: https://go.k8s.io/triage
[Release Team test-infra role]: https://git.k8s.io/sig-release/release-team/role-handbooks/test-infra
[kubernetes-dev@]: https://groups.google.com/forum/#!forum/kubernetes-dev
[dev@kubernetes.io]: https://groups.google.com/a/kubernetes.io/group/dev
[kubernetes-sig-testing@]: https://groups.google.com/forum/#!forum/kubernetes-sig-testing
[kubernetes/test-infra]: https://git.k8s.io/test-infra

8
sig-wg-lifecycle.md
View File

@ -13,12 +13,12 @@ Out of scope for this document: [subproject] creation.
- [ ] Send an email to the Steering Committee <steering@kubernetes.io> to scope the SIG and get provisional approval
- [ ] Look at the checklist below for processes and tips that you will need to do while this is going on. It's best to collect this information upfront so you have a smoother process to launch
- [ ] Follow the [SIG charter process] to propose and obtain approval for a charter
- [ ] Announce new SIG on kubernetes-dev@googlegroups.com
- [ ] Announce new SIG on dev@kubernetes.io
### Prerequisites for a WG
- [ ] Read [wg-governance.md]
- [ ] Ensure all WG Organizers, and other leadership roles are [community members]
- [ ] Send email to [kubernetes-dev@googlegroups.com] titled "WG-Creation-Request: WG Foo" with some of the questions answered from wg-goverance.md and wait for community discourse; ask for SIG sponsorship
- [ ] Send email to [dev@kubernetes.io] titled "WG-Creation-Request: WG Foo" with some of the questions answered from wg-goverance.md and wait for community discourse; ask for SIG sponsorship
- [ ] Do the first checklist item in the [GitHub] section below and add a row to the WG section:
- [ ] Label with committee/steering and wait for a simple majority
- [ ] Also add sponsoring SIG Chair/Tech Leads as approvers; you'll get this from the community email above
@ -30,7 +30,7 @@ Out of scope for this document: [subproject] creation.
- [ ] Require to have 2 Chairs to start a User Group.
- [ ] Require to have at least 2 members other than chairs to be a part of the User Group.
- [ ] Requires at least 2 sponsors from steering or lazy consensus (In case of no objection within 7 week days).
- [ ] Send an email to kubernetes-dev@googlegroups.com and steering@kubernetes.io titled "UG-Creation-Request: UG Foo" answering the following questions and wait for community discourse:
- [ ] Send an email to dev@kubernetes.io and steering@kubernetes.io titled "UG-Creation-Request: UG Foo" answering the following questions and wait for community discourse:
- [ ] What topics are in scope for this user group?
- [ ] What is the meeting cadence?
- [ ] Who will chair the group, and ensure it continues to meet the requirements?
@ -90,7 +90,7 @@ Sometimes it might be necessary to sunset a SIG or Working Group. SIGs/WGs may a
- [ ] There is no activity on communication channels.
### Steps:
- [ ] Send an email to kubernetes-dev@googlegroups.com and community@kubernetes.io alerting the community of your intentions to disband or merge. [example]
- [ ] Send an email to dev@kubernetes.io and community@kubernetes.io alerting the community of your intentions to disband or merge. [example]
- This kicks off the process for Contributor Experience’s community managers who will reach out and set an issue against `kubernetes/community` with exact next steps covered below. We can help walk through this when you get there. Most of this is covered in the same creation communication docs as above.
- [ ] Archive the member and lead/chair mailing lists/[GoogleGroups]
- [ ] Check the [slack-guidelines.md] for latest process on archiving the slack channel

2
wg-data-protection/charter.md
View File

@ -79,6 +79,6 @@ This WG will be producing documents as described in the `In Scope` section. If s
[Kubernetes Charter README]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/README.md
[lazy consensus]: http://en.osswiki.info/concepts/lazy_consensus
[kubernetes-dev@]: https://groups.google.com/forum/#!forum/kubernetes-dev
[dev@kubernetes.io]: https://groups.google.com/a/kubernetes.io/group/dev
[wg-data-protection@]: https://groups.google.com/forum/#!forum/kubernetes-wg-data-protection
[kubernetes/k8s.io]: https://git.k8s.io/k8s.io