Jump to: navigation, search

Difference between revisions of "Diversity/Inclusivity"

(oops, removed some duplication)
(Include link to the Board's statement of support)
 
(9 intermediate revisions by 2 users not shown)
Line 1: Line 1:
Open Infrastructure Foundation projects are committed to the use of inclusive language, avoiding unnecessary use of language which is commonly associated with oppression, racism, and sexism. Some words, phrases, and jargon which evoke connotations at odds with community values have found their way into common engineering parlance, and from there into our source code and documentation. Where possible, contributors to our projects opt for more more fitting and less exclusionary terminology. For these reasons the following terms have been identified by contributors as problematic, and so we seek recommendations for suitable alternatives (note that as English is the standard language for Open Infrastructure Project interfaces, documentation, and communication, these examples are English-focused).
+
(see also: [https://wiki.openstack.org/wiki/Governance/Foundation/Inclusive_Language Open Infrastructure Foundation Board of Directors Statement of Support for Use of Inclusive Language])
  
'''slave''', or '''master''' in slavery-related contexts: the MariaDB community is moving to ''primary/replica'', MySQL leaning towards ''source/replica'', Jenkins is going to ''manager/worker'', Python community suggestions are ''parent/child'' or ''server/client'' or ''employer/worker'', DNS(IETF)  is going with ''primary/secondary'' servers, Django are looking at ''leader/follower'', HSRP/VRRP/CARP protocols have traditionally used ''active/standby''; for non-slavery-related contexts it's worth noting that there's significant activity in the Git upstream community to make the standard branch name ''main'' instead of '''master'''
+
Open Infrastructure Foundation projects are committed to the use of inclusive language, avoiding unnecessary use of language which is commonly associated with oppression, racism, sexism, heterosexism, ablism, and similar forms of discrimination. Some words, phrases, and jargon which evoke connotations at odds with community values have found their way into common engineering parlance, and from there into our source code and documentation. Where possible, contributors to our projects opt for more more fitting and less exclusionary terminology. For these reasons the following terms have been identified by contributors as problematic, and so we seek recommendations for suitable alternatives (note that as English is the standard language for Open Infrastructure Project interfaces, documentation, and communication, these examples are English-focused).
 +
 
 +
'''slave''', or '''master''' in slavery-related contexts: the MariaDB community is moving to ''primary/replica'', MySQL leaning towards ''source/replica'', Jenkins is going to ''manager/worker'', Python community suggestions are ''parent/child'' or ''server/client'' or ''employer/worker'', DNS(IETF)  is going with ''primary/secondary'' servers, Django are looking at ''leader/follower'', HSRP/VRRP/CARP protocols have traditionally used ''active/standby''
 +
 
 +
'''master''' in non-slavery-related contexts: there seems to be some consensus building in the Git upstream community to make the standard branch name ''main'' instead of '''master''', but the discussion is far from settled yet; the [https://opendev.org/ OpenDev Collaboratory] is seeking projects who are interested in identifying any remaining challenges related to hosting a new repositories with a default branch name other than '''master''', before considering what might be involved in switching the default branch names for existing repositories
  
 
'''blacklist/whitelist''': ''deny/allow'', ''reject/accept'', ''exclude/include'', ''block/pass''
 
'''blacklist/whitelist''': ''deny/allow'', ''reject/accept'', ''exclude/include'', ''block/pass''
Line 19: Line 23:
 
'''rule of thumb''': ''guideline''
 
'''rule of thumb''': ''guideline''
  
'''sanity check''' ''status check'', ''check in'', ''validation''
+
'''sanity check''': ''status check'', ''check in'', ''validation''
  
 
'''crippled''': ''limited'', ''restricted''
 
'''crippled''': ''limited'', ''restricted''
  
'''native''': ''natural'', ''basic'', ''base'', ''original''. ''normal'', ''typical'', ''standard''
+
'''native''': ''natural'', ''basic'', ''base'', ''original'', ''normal'', ''typical'', ''standard''
  
 
'''cakewalk''': ''easy'', ''straightforward''
 
'''cakewalk''': ''easy'', ''straightforward''
Line 30: Line 34:
  
 
'''kosher''': ''acceptable'', ''clean''
 
'''kosher''': ''acceptable'', ''clean''
 +
 +
'''pronouns''':  When listing a gender pronoun such as "he, his, or him" or "she, hers, or her", gender neutral wording should be used "they, their, or them".
 +
 +
'''chairman''': "chair", "chairperson"

Latest revision as of 14:04, 21 October 2021

(see also: Open Infrastructure Foundation Board of Directors Statement of Support for Use of Inclusive Language)

Open Infrastructure Foundation projects are committed to the use of inclusive language, avoiding unnecessary use of language which is commonly associated with oppression, racism, sexism, heterosexism, ablism, and similar forms of discrimination. Some words, phrases, and jargon which evoke connotations at odds with community values have found their way into common engineering parlance, and from there into our source code and documentation. Where possible, contributors to our projects opt for more more fitting and less exclusionary terminology. For these reasons the following terms have been identified by contributors as problematic, and so we seek recommendations for suitable alternatives (note that as English is the standard language for Open Infrastructure Project interfaces, documentation, and communication, these examples are English-focused).

slave, or master in slavery-related contexts: the MariaDB community is moving to primary/replica, MySQL leaning towards source/replica, Jenkins is going to manager/worker, Python community suggestions are parent/child or server/client or employer/worker, DNS(IETF) is going with primary/secondary servers, Django are looking at leader/follower, HSRP/VRRP/CARP protocols have traditionally used active/standby

master in non-slavery-related contexts: there seems to be some consensus building in the Git upstream community to make the standard branch name main instead of master, but the discussion is far from settled yet; the OpenDev Collaboratory is seeking projects who are interested in identifying any remaining challenges related to hosting a new repositories with a default branch name other than master, before considering what might be involved in switching the default branch names for existing repositories

blacklist/whitelist: deny/allow, reject/accept, exclude/include, block/pass

blackhat/whitehat: malicious/ethical

blackout: restrict, outage, redact

segregate: separate

man hour/man day: workhour/workday, person hour/person day, FTE hour/FTE day

manpower: worker, workforce, staff, labor

manned: staffed

rule of thumb: guideline

sanity check: status check, check in, validation

crippled: limited, restricted

native: natural, basic, base, original, normal, typical, standard

cakewalk: easy, straightforward

guru: expert, leader

kosher: acceptable, clean

pronouns: When listing a gender pronoun such as "he, his, or him" or "she, hers, or her", gender neutral wording should be used "they, their, or them".

chairman: "chair", "chairperson"