From alanclark at openstack.org Fri Oct 9 19:22:15 2020 From: alanclark at openstack.org (alanclark at openstack.org) Date: Fri, 9 Oct 2020 13:22:15 -0600 Subject: [OpenStack Foundation] OpenStack BoardMeeting, October 13, 7am - 9am Message-ID: <06a201d69e71$7fa0b560$7ee22020$@openstack.org> A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2208 bytes Desc: not available URL: From amy at demarco.com Sat Oct 17 13:26:49 2020 From: amy at demarco.com (Amy Marrich) Date: Sat, 17 Oct 2020 08:26:49 -0500 Subject: [OpenStack Foundation] Divisive Language stance final(?) draft and Forum session Message-ID: Hi everyone, 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[0] and/or join us this Tuesday during the forum[1]. 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. Thanks, Amy Marrich (spotz) 0 - https://etherpad.opendev.org/p/divisivelanguage 1- https://www.openstack.org/summit/2020/summit-schedule/events/24778/divisive-language-and-what-you-should-know 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 projects. 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, etc. 1. The terms "blacklist" and "whitelist" in various contexts (which might require a variety of different replacements to make sense for those contexts) 1. The use of "master" in non-slavery-related contexts such as revision control branches and documentation builds (pending feedback from our community members) 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... URL: From rv6848 at att.com Mon Oct 19 14:01:31 2020 From: rv6848 at att.com (VAN WYK, RYAN L) Date: Mon, 19 Oct 2020 14:01:31 +0000 Subject: [OpenStack Foundation] [Airship-discuss] Divisive Language stance final(?) draft and Forum session In-Reply-To: References: Message-ID: <851A971D-7EF0-419F-AFA9-E99B214E38F2@att.com> Great work. Thank you for taking this forward. Ryan van Wyk VP – Cloud Platforms m 312.860.0966 | rv6848 at att.com From: Amy Marrich Date: Saturday, October 17, 2020 at 8:27 AM To: "starlingx-discuss at lists.starlingx.io" , "airship-discuss at lists.airshipit.org" , "kata-dev at lists.katacontainers.io" , "zuul-discuss at lists.zuul-ci.org" , openstack-discuss , "foundation at lists.openstack.org" Subject: [Airship-discuss] Divisive Language stance final(?) draft and Forum session Hi everyone, 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[0] and/or join us this Tuesday during the forum[1]. 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. Thanks, Amy Marrich (spotz) 0 - https://etherpad.opendev.org/p/divisivelanguage 1- https://www.openstack.org/summit/2020/summit-schedule/events/24778/divisive-language-and-what-you-should-know 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 projects. 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, etc. 1. The terms "blacklist" and "whitelist" in various contexts (which might require a variety of different replacements to make sense for those contexts) 1. The use of "master" in non-slavery-related contexts such as revision control branches and documentation builds (pending feedback from our community members) 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... URL: From amy at demarco.com Fri Oct 23 13:19:34 2020 From: amy at demarco.com (Amy Marrich) Date: Fri, 23 Oct 2020 08:19:34 -0500 Subject: [OpenStack Foundation] [Diversity][PTG] Diversity and Inclusion WG at the PTG - Divisive Language Message-ID: The Diversity and Inclusion WG will be holding a PTG session Monday from 15:00-17:00 UTC. We will be using Meetpad[0] atleast to start but will change to Zoom if needed. Based on feedback [2] during the Forum session we will be working on providing a more comprehensive list of words and possible alternatives vs the original plan to leave this aspect within the technical groups. Thanks, Amy Marrich (spotz) 0 - https://meetpad.opendev.org/wallaby-ptg-diversity 1 - https://etherpad.opendev.org/p/wallaby-ptg-diversity 2 - https://etherpad.opendev.org/p/vSummit2020__DivisiveLanguage -------------- next part -------------- An HTML attachment was scrubbed... URL: From amy at demarco.com Tue Oct 27 13:57:07 2020 From: amy at demarco.com (Amy Marrich) Date: Tue, 27 Oct 2020 08:57:07 -0500 Subject: [OpenStack Foundation] [PTG] [Diversity] Extra session for Divisive Language discussions Message-ID: During the Monday session there were some questions in regards to technical writing and how things should be worded. I have invited Joanne O'Flynn, a Technical Writer from Red Hat to join us on Thursday at 17:00 UTC to help address these questions. This is not a normal PTG time slot but it was the only option due to time zones and already booked sessions for some of the participants from Monday. Thanks, Amy Marrich (spotz) -------------- next part -------------- An HTML attachment was scrubbed... URL: From amy at demarco.com Tue Oct 27 15:58:29 2020 From: amy at demarco.com (Amy Marrich) Date: Tue, 27 Oct 2020 10:58:29 -0500 Subject: [OpenStack Foundation] [PTG] [Diversity] Extra session for Divisive Language discussions In-Reply-To: References: Message-ID: Link for those who need it - https://meetpad.opendev.org/wallaby-ptg-diversity On Tue, Oct 27, 2020 at 8:57 AM Amy Marrich wrote: > During the Monday session there were some questions in regards to > technical writing and how things should be worded. I have invited Joanne > O'Flynn, a Technical Writer from Red Hat to join us on Thursday at 17:00 > UTC to help address these questions. This is not a normal PTG time slot but > it was the only option due to time zones and already booked sessions for > some of the participants from Monday. > > Thanks, > > Amy Marrich (spotz) > -------------- next part -------------- An HTML attachment was scrubbed... URL: From amy at demarco.com Fri Oct 30 19:24:28 2020 From: amy at demarco.com (Amy Marrich) Date: Fri, 30 Oct 2020 14:24:28 -0500 Subject: [OpenStack Foundation] [Diversity] Diversity & Inclusion WG Meeting 11/2 - Removing Divisive Language Message-ID: The Diversity & Inclusion WG will continue working on the OSF's stance on the removal of Divisive Language within the OSF projects. We will be focusing on the creation of possible words to focus on as well as possible replacements[0] as was requested during our Forum session[1]. The WG invites members of all OSF projects to participate in this effort and to join us at our next meeting Monday, November 2nd, at 17:00 UTC which will be held at https://meetpad.opendev.org/osf-diversity-and-inclusion. If you have any questions please let me and the team know here, on #openstack-diversity on IRC, or you can email me directly. Thanks, Amy Marrich (spotz) 0 - https://etherpad.opendev.org/p/wallaby-ptg-diversity 1- https://etherpad.opendev.org/p/vSummit2020__DivisiveLanguage -------------- next part -------------- An HTML attachment was scrubbed... URL: