Add wg naming language evaluation framework#16
Merged
celestehorgan merged 1 commit intomainfrom Nov 16, 2020
Merged
Conversation
xmulligan
reviewed
Nov 13, 2020
Comment on lines
+7
to
+11
| The language evaluation framework is a guidance document developed by the [Kubernetes Naming Working Group](https://github.com/kubernetes/community/tree/master/wg-naming). The version of this documentation found on the Inclusive Naming website is a mirror. | ||
|
|
||
| It outlines a structured framework for evaluating language and terminology for harm to the community. This enables the community to navigate divisive conversations with a measure of clarity. | ||
|
|
||
| The framework was created for an open source technology project. The framework may be applicable to other fields as well. |
Contributor
There was a problem hiding this comment.
Suggested change
| The language evaluation framework is a guidance document developed by the [Kubernetes Naming Working Group](https://github.com/kubernetes/community/tree/master/wg-naming). The version of this documentation found on the Inclusive Naming website is a mirror. | |
| It outlines a structured framework for evaluating language and terminology for harm to the community. This enables the community to navigate divisive conversations with a measure of clarity. | |
| The framework was created for an open source technology project. The framework may be applicable to other fields as well. | |
| The language evaluation framework is a guidance document developed by the [Kubernetes Naming Working Group](https://github.com/kubernetes/community/tree/master/wg-naming). It outlines a structured framework to evaluate language and terminology for harm to the community. This enables the community to navigate divisive conversations with a measure of clarity. | |
| The framework was created for open source technology projecst. The framework may be applicable to other fields as well. | |
| The version of this documentation found on the Inclusive Naming website is a mirror from the Kubernetes Naming Working Group. |
|
|
||
| First-order concerns are language where harm is egregious, overt, and clearly problematic. Second-order concerns are language which is problematic but with a less definite impact. Third-order concerns indicate language that could use improvement but does no demonstrable harm. | ||
|
|
||
| Answer all questions for each term evaluated. |
Contributor
There was a problem hiding this comment.
is part of this sentance missing?
Contributor
There was a problem hiding this comment.
or can this be explained in more detail?
|
|
||
| First-order concerns are characterized by: | ||
|
|
||
| - Overtness: regardless of its use in the context of code or technology, there is little to no ambiguity outside of technology as to whether the language in question indicates harm |
Contributor
There was a problem hiding this comment.
Suggested change
| - Overtness: regardless of its use in the context of code or technology, there is little to no ambiguity outside of technology as to whether the language in question indicates harm | |
| - Overtness: regardless of its use in the context of code or technology, there is little to no ambiguity outside of technology as to whether the language in question causes harm |
| Examples include “master/slave”. | ||
|
|
||
| #### Is the term overtly sexist, transphobic, or pejorative about a gender identity? | ||
|
|
Contributor
There was a problem hiding this comment.
can we add examples too?
| Examples include performing “sanity checks”. | ||
|
|
||
| #### Is the term overtly homophobic? | ||
|
|
Signed-off-by: Celeste Horgan <celeste@cncf.io>
celestehorgan
force-pushed
the
add-wgnaming-docs
branch
from
88af8cb to
d7c917a
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Signed-off-by: Celeste Horgan celeste@cncf.io