On 5/22/24 09:46, Ales Musil wrote:
> On Tue, May 7, 2024 at 10:16 PM Mark Michelson <[email protected]> wrote:
> 
>> There is a growing movement to be more inclusive in the language used in
>> code and its documentation.
>>
>> For this task, the following site was used to find a list of words that
>> should be avoided: https://inclusivenaming.org/word-lists/ .
>>
>> Each of their tier 1, tier 2, and tier 3 words were searched in the code
>> and replaced as necessary.
>>
>> Each commit is focused around the replacement of a single word from the
>> word lists. In each case, the commit message will explain if there are
>> any exceptions where the word was not replaced.
>>
>> There are some words you will find in the linked word list that are not
>> addressed at all in these commits:
>>
>> * "segregate": This words appears only in an old NEWS entry. Changing
>>   this would be more odd than leaving it alone. Considering this is a
>>   tier 3 word on the linked word list, I opted to leave it as-is.
>> * "man-in-the-middle": This appears in all ovn-*ctl utility manpages.
>>   However, this is generated from an included file in the ovs submodule.
>>   Therefore, changing this in OVN would require a change in OVS instead.
>>
>> The rest of the words in the list that are not addressed in this series
>> do not appear anywhere in the OVN repository, as far as I could find.
>>

[...]

>>
> The whole series looks good to me, thanks!
> 
> Acked-by: Ales Musil <[email protected]>

Thanks, Mark and Ales, I applied this to main!

However, should we follow up with guidelines, similar to what OvS did?
https://github.com/openvswitch/ovs/commit/df5e5cf4318a64019d0f9bdf4fbfb398d1757269

I admit I was surprised by some of the words in the list (not a native
speaker here so that probably explains why).  I'm definitely OK with
changing them but I think it's good to have a reference we can go back to.

What do you think?

Thanks,
Dumitru

_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Reply via email to