Over a week ago, @lzap published an RFC about removing the term blacklist from Foreman templates. A short discussion about this took place on the related Pull Request. With a wider discussion taking place in the tech, open source, and academic worlds (please see Further Information at the bottom of this post for some links), the community management team wants to take a moment to outline our thoughts on this in the context of the Foreman community. While normally RFCs and PRs go through a longer process, we think it is important to address this specific RFC and outline some action items.
This issue goes back many years, and I am glad more people are addressing it. However I think you are sending out he wrong message with âHowever, when certain terminology that seems harmless is highlighted as exclusionary, bigoted, and a vestige of societal legacies that are oppressive, as much as we would like to remain neutral on politics, inaction on language like this can imply an attitude or stance that is not a reflection of our community members and is not in line with our community guidelines.â
âŚthat makes people become extremely defensive often to the point they will go out of there way to use the terminology as an reaction/response, it is also highly offense an unfair to them.
The reason we should change words is because of a cultural sensitivity which some people understandably find uncomfortable to use or hear, and given the âbigger pictureâ (which has existed for many years), it is a small price worth paying.
Let us change terminology because we are nice and considerate to others.
Hello and welcome to the community!
Thanks for your feedback.
This paragraph was addressing a legacy stance held by this community to avoid political issues as much as is possible. It wasnât a boilerplate text but written to address issues that arose and led to the community team having to address this. I hope that makes sense. Overall, we want to be nice and focus on technical topics around Foreman
One example where we use master/slave is our nic bonding because thatâs the terminology used for bonding. Network Teaming is an an alternative solution to bonding which has technical benefits as well. Feature #17033: Add Network Teaming configuration for hosts - Foreman is open for over 3 years even though Network Teaming is the recommended solution since RHEL 7. There is a comparison and the lower performance overhead compared to bonding alone makes it a feature we should support.
