On 29/08/2021 12.07, sebb wrote:
AFAICT there are far too many false positives for this to be useful currently.
Agreed, we need projects to assess and configure the scan settings
themselves in the long run.
This is especially true of short words like 'he', which is also a
valid language code (Hebrew).
Also, whilst 'master' may be a problematic word, there may be little
that a project can do if it appears in a URL.
True, many projects will want to not scan for that word, and they can
remove it altogether or by context.
Further, it only appears to be possible to ignore a single instance of a word.
If the same word appears multiple times, each one has to be ignored.
Not really practical if the word appears over 1800 times.
Words can be ignored completely or by context in the scan settings,
either by removing the word from the list of words it scans for (middle
column) or by adding regex contexts where the word should not be counted
(right side column).
Sebb
(he/him/his)
On Sun, 29 Aug 2021 at 17:46, Daniel Gruno <humbed...@apache.org> wrote:
[This email was sent to all (P)PMCS at the ASF]
Words matter. The words we choose influence the kinds of communities we
build, the tone we set for our participants, and who will feel welcome
in our projects.
With the growing awareness in the software industry that we routinely
use sexist, racist, ableist words in our code and documentation, it’s
important that you have tooling that helps you discover if your project
is part of the problem.
The CLC - Conscious Language Checker - is such a tool, and gives you
insight into what words and phrases appear in your code and docs that
might make your project less welcoming to certain parts of your
potential community. We’ve taken the liberty to add your project’s
repositories to what we’re scanning, and encourage you to have a look at
https://clc.diversity.apache.org/. Then come to the Diversity mailing
list - https://lists.apache.org/list.html?dev@diversity.apache.org - if
you want to discuss best practices in adjusting your language choices.
It is important to note that the CLC instance we have running is using
default settings for all projects. Thus, a project may disagree with
what the scanner considers problematic. This is all configurable, and
requires you to log in via ASF Oauth. Once logged in, you may edit your
project's settings to your liking. New scans happen every 12 hours.
We ask that people do not add or remove project repositories without
prior notice to dev@diversity.apache.org.
With regards,
Daniel and Rich, on behalf of the Equity, Diversity & Inclusion
committee at the ASF.
Helpful resources:
Dashboard: https://clc.diversity.apache.org/
CLC code: https://github.com/Humbedooh/clc
Inclusive Naming Initiative: https://inclusivenaming.org/
