Hey, I was looking into the DLC and noticed that many of the hits were actually non-linguistic. In fact all of the first 20 hits that I found were URLs referencing licenses found in LICENSE and in dot files. Since those are nearly all under external control, there isn't any way for the project in question to remove the word master from the URLs.
I would suggest that the tool be adapted to not mark URLs. The exception to this is that CLC could reasonably mark the use of "master" as the main development branch on github. But marking it repeated isn't really reasonable. Improving this is likely to improve the impression people get when first encountering. I know that my first impression was "these are all bogus hits" and my estimation of the tool's utility dropped sharply. Efforts to improve diversity are severely hampered by such spurious impressions. Specific efforts to improve CLC scores by repairing documentation and code are much more difficult when such a high fraction of the hits are spurious. On Sun, Aug 29, 2021 at 9:47 AM 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/ > >
