Ilya Maximets <[email protected]> writes: > On 12/21/23 14:50, Simon Horman wrote: >> On Thu, Dec 21, 2023 at 09:12:52AM +0100, Eelco Chaudron wrote: >>> >>> >>> On 14 Dec 2023, at 15:19, Simon Horman wrote: >>> >>>> As a community we should strive to be inclusive. >>>> As such it seems appropriate to adopt an word list, >>>> to help guide the use of inclusive language. >>>> >>>> This patch proposes use of the Inclusive Naming Word List v1.0. >>>> >>>> Link: https://inclusivenaming.org/word-lists/ >>>> Signed-off-by: Simon Horman <[email protected]> >>> >>> Thanks for getting this started Simon. Would it make sense to >>> enhance our checkpatch utility to scan for Tear 1/2/3 words? >> >> Thanks Eelco, >> >> I think that we should aim to avoid introducing new instances of >> such words. And to that end, I think enhancing tooling such as checkpatch >> is an excellent idea. > > These two sentences are a bit contradictory, unless we can add a check > without maintaining a list of words ourselves. Sounds tricky taking > into account that checkpatch script shouldn't make any network requests.
Yes, I agree. I'm not sure what the best approach would be other than having the build / configure process pull such a list? But even then, I prefer we don't do such network requests when making builds (for example, if they fail then the build fails). Maybe we have a manual copy of such list and periodically update it. IE: we try to pull the json file from the inclusive language site and then commit that to the aux build area. It needs some kind of agreement to switch checkpatch to make network requests, but I don't think it is completely banned idea. For example, we could make such an option as an optional behavior (the way the current spellchecking code works), but I (generally) wouldn't want to run without it - and I would probably set the robot to do this as well. > Best regards, Ilya Maximets. > _______________________________________________ > dev mailing list > [email protected] > https://mail.openvswitch.org/mailman/listinfo/ovs-dev _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
