Merge pull request #5938 from justaugustus/wg-naming-bye

governance: Dissolution of WG Naming

3 files changed, 180 insertions, 0 deletions

diff --git a/archive/wg-naming/OWNERS b/archive/wg-naming/OWNERS
new file mode 100644
index 00000000..b85dde17
--- /dev/null
+++ b/archive/wg-naming/OWNERS
@@ -0,0 +1,8 @@
+# See the OWNERS docs at https://go.k8s.io/owners
+
+reviewers:
+  - wg-naming-leads
+approvers:
+  - wg-naming-leads
+labels:
+  - wg/naming
diff --git a/archive/wg-naming/README.md b/archive/wg-naming/README.md
new file mode 100644
index 00000000..785b0d2b
--- /dev/null
+++ b/archive/wg-naming/README.md
@@ -0,0 +1,87 @@
+<!---
+This is an autogenerated file!
+
+Please do not edit this file directly, but instead make changes to the
+sigs.yaml file in the project root.
+
+To understand how this file is generated, see https://git.k8s.io/community/generator/README.md
+--->
+# Naming Working Group
+
+
+## Stakeholder SIGs
+* SIG Architecture
+* SIG Contributor Experience
+* SIG Docs
+
+## Meetings
+* Regular WG Meeting: [Mondays at 10:30 PT (Pacific Time)](https://zoom.us/j/91522666403?pwd=WnRSNlNhNXhDWkR2ZU9ydGpsNWxtZz09) (monthly - second Monday of month). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=10:30&tz=PT%20%28Pacific%20Time%29).
+  * [Meeting notes and Agenda](https://bit.ly/k8s-wg-naming-agenda).
+  * [Meeting recordings](https://www.youtube.com/playlist?list=PL69nYSiGNLP3BrAtDHyr8KTUfhBhCG7CD).
+
+## Organizers
+
+* Celeste Horgan (**[@celestehorgan](https://github.com/celestehorgan)**), CNCF
+* Jaice Singer DuMars (**[@jdumars](https://github.com/jdumars)**), Apple
+* Stephen Augustus (**[@justaugustus](https://github.com/justaugustus)**), Cisco
+
+## Emeritus Organizers
+
+* Zach Corleissen (**[@zacharysarah](https://github.com/zacharysarah)**)
+
+## Contact
+- Slack: [#wg-naming](https://kubernetes.slack.com/messages/wg-naming)
+- [Mailing list](https://groups.google.com/forum/#!forum/kubernetes-wg-naming)
+- [Open Community Issues/PRs](https://github.com/kubernetes/community/labels/wg%2Fnaming)
+- Steering Committee Liaison: Bob Killen (**[@mrbobbytables](https://github.com/mrbobbytables)**)
+<!-- BEGIN CUSTOM CONTENT -->
+
+**The following section will be reworked and formalized as a charter once the
+Working Group has been approved by the Steering Committee.**
+
+## Goals
+
+- Evaluate language and naming choices within the Kubernetes project, with
+  a specific initial focus of:
+  - Removing barriers to contribution and adoption by replacing harmful language with neutral terms whenever possible, including but not limited to language linked to racism, sexism, homophobia, transphobia, ableism, or discrimination against any protected or historically underrepresented group.
+  - Improving clarity of codebases and documentation by replacing idioms,
+    metaphors and slang specific to the English language
+- Create a list of harmful terms with proposed replacements
+- Define how any member of the Kubernetes project can
+  recommend language, how others can evaluate that proposal, and how to 
+  implement replacements across all codebases.
+  - Provide an easily findable location for language recommendations and
+    follow-up issues, similar to an architectural decision record
+  - Define long-term ownership of this process
+- Work with stakeholder SIGs to implement the changes recommended. We
+  anticipate the following:
+  - Provide stakeholder SIGs with guidance on naming, language conventions, and
+    processes
+  - Collaborate with SIG Architecture and other stakeholders on an
+    implementation timeline and strategies for dealing with follow-up issues
+    from renaming, like deprecations
+  - Collaborate with SIG Docs and SIG Contributor Experience on documenting
+    language recommendations and processes
+  - Work with the Code of Conduct Committee to add code architecture to the COC
+
+## Dissolution Criteria
+
+Once the Kubernetes community has:
+
+- A process in place to evaluate language changes on an ongoing basis
+- A binding list of terms to avoid in codebases across the project
+- A timeline on which to replace component names in the kubernetes/kubernetes
+  codebase
+- Defined long-term ownership of the policies and processes this WG creates
+
+this WG will dissolve.
+
+## Post-formation Discussion Points
+
+- Discuss appropriate process for branch renaming with GitHub Administration
+  subproject (SIG ContribEx)
+- Work with the Code of Conduct Committee to add code architecture to the COC
+- A timeline on which to replace component names in the kubernetes/kubernetes
+- Clarify that WG should not dissolve until after changes have been made
+
+<!-- END CUSTOM CONTENT -->
diff --git a/archive/wg-naming/governance.md b/archive/wg-naming/governance.md
new file mode 100644
index 00000000..5f15a42f
--- /dev/null
+++ b/archive/wg-naming/governance.md
@@ -0,0 +1,85 @@
+# WG Naming governance
+
+## Uphold project values
+
+WG Naming upholds the Kubernetes project's [core values](/values.md).
+
+### Inclusive is better than exclusive
+
+> Broadly successful and useful technology requires different perspectives and skill sets which can only be heard in a welcoming and respectful environment.
+
+This document covers some specific ways in which WG Naming offers respect and welcome.
+
+> Our community shows respect for the time and effort put into a discussion regardless of where a contributor is on their growth path.
+
+Like other SIGs and working groups, WG Naming has prerequisite skills, training, and experience that are necessary for meaningful contribution. For example:
+
+  - Education or professional experience in dismantling systemic discrimination
+  - Demonstrable familiarity with current antidiscrimination resources
+  - A track record of supporting inclusion in the Kubernetes project
+
+WG Naming has many stakeholders, with many people eager to add their voices. WG Naming invites folks who are new to antiracism or inclusive language, and folks less experienced with frameworks of discrimination to participate by observing and learning. WG Naming invites contributors who meet prerequisites to contribute within the scope of WG Naming’s goals.
+
+### Resources for antidiscrimination
+
+- https://developers.google.com/style/inclusive-documentation
+- https://www.antiracismresources.info/#online-resources
+- _How to Be An Antiracist_, Ibrahim X. Kendi
+- _So You Want to Talk About Race_, Ijeoma Oluo
+
+### Scope of discussion
+
+WG Naming actively moderates discussion for speech that affirms the humanity of underrepresented minorities and affirms their ongoing experience of discrimination. For example: specific suggestions for replacement terms are welcome. Disagreement over the presence and impact of racism is not welcome.
+
+## Follow the community code of conduct
+
+Like all WGs and SIGs, WG Naming expects contributors to follow the [Kubernetes Code of Conduct (CoC)]. 
+
+We raise this section’s topics as potential blockers to the work of WG Naming, since experience has shown they are a common and detrimental response.
+
+From the CoC:
+
+> Examples of unacceptable behavior by participants include:
+>
+>   - Personal attacks
+>   - Trolling or insulting/derogatory comments
+
+**Note:** the CoC governs conduct, not intent. WG Naming leads may refer unacceptable conduct to the Code of Conduct Committee regardless of professed intent.
+
+[Kubernetes Code of Conduct (CoC)]: /code-of-conduct.md
+
+### Personal attacks
+
+Personal attacks include denying or questioning the lived experience of underrepresented minorities. For example: arguing that problematic terms "aren't racist", or any statements reducible or equivalent to "all lives matter".
+
+### Trolling
+
+Trolling includes:
+
+- [Concern trolling](https://en.wiktionary.org/wiki/concern_troll)
+
+- Derailing behavior
+
+    Behavior that distracts from WG Naming's purpose or attempts to redirect participants' energy into minutiae or unrelated topics or goals.
+
+    For example: 
+      - insisting that previous decisions be re-argued
+      - insisting that WG Naming can take no action until all possible inequities are addressed
+
+- [Sea lioning](https://www.forbes.com/sites/marshallshepherd/2019/03/07/sealioning-is-a-common-trolling-tactic-on-social-media-what-is-it/)
+
+  Endless demands for evidence; refusing to accept or acknowledge peer-reviewed scientific research; insisting that one's ignorance, whether real or feigned, be satisfied by the WG group to an individual's satisfaction.
+
+  See the original Wondermark comic: [sea lions](http://wondermark.com/1k62/)
+
+- [Brigading](https://en.wikipedia.org/wiki/Vote_brigading)
+
+  Attempting to overrepresent a viewpoint through participation bias
+
+## Deviations from [sig-governance]
+
+WG Naming leads may close or end meetings at their discretion to shut down trolling or protect the safety of community members.
+
+WG Naming [restricts the scope of discussion](#scope-of-discussion).
+
+[sig-governance]: /committee-steering/governance/sig-governance.md