Divisive Language stance final(?) draft and Forum session
Below is what we hope is the final draft of the OSF's stance on Divisive
Language. If you have any comments please place them on the etherpad
and/or join us this Tuesday during the forum.
Please note that decisions related to what words should be replaced with
are being left with the project's technical leadership with the knowledge
that context is important to determine the best alternative. That said, the
Diversity and Inclusion WG will be available to assist these groups.
Amy Marrich (spotz)
0 - https://etherpad.opendev.org/p/divisivelanguage
1a - https://zoom.us/j/94295083896?pwd=VmZCTFN3eERDK1ltRHRyWDl0eG1hZz09
1b - https://etherpad.opendev.org/p/vSummit2020__DivisiveLanguage
The OpenStack Foundation (OSF) Board of Directors supports removal of
wording identified as oppressive, racist and sexist by members of our
communities from the software and documentation they produce. While we know
there will be challenges, both technical and non-technical, this is an
action we feel is important.
These efforts are the responsibility of the various technical leadership
groups within our communities, and we trust them to make appropriate
decisions about applicability, timelines, minimizing impact to users and
operators, and choosing the changes that make the most sense for their
Contributors will take care to make changes to software in the least
disruptive way possible. While standardized wording is a laudable goal, we
recognize that different implementation contexts might require different
solutions. In many cases the work is also complicated by external
dependencies for these projects, and their capacity to make necessary
changes before we can implement ours.
Terminology to which special attention should be paid includes:
1. The use of "slave," or "master" in reference to slavery-oriented
relationships, as is currently found in databases, the domain name system,
1. The terms "blacklist" and "whitelist" in various contexts (which
might require a variety of different replacements to make sense for those
1. The use of "master" in non-slavery-related contexts such as revision
control branches and documentation builds (pending feedback from our
We shall continue to be vigilant for other language areas that cause
challenges and work with the community to evolve this policy.
-------------- next part --------------
An HTML attachment was scrubbed...