Re: Inclusive terminology in Apache Software - a practical approach

On 20/05/2021 19.43, Kenneth Knowles wrote: I tried it on Beam and noticed that the default exclusion glob of *shakespeare* did not match /sdks/go/data/shakespeare/hamlet.txt It _does_ match, but Rich put that exclusion in *after* the scan had run. On next scan, it should exclude the

Re: Inclusive terminology in Apache Software - a practical approach

On 20/05/2021 19.37, Andrew Wetmore wrote: The "about" link doesn't seem to lead anywhere. Work in progress :D I've yet to figure out what to put there... Virus-free. www.avast.com

Re: Inclusive terminology in Apache Software - a practical approach

I tried it on Beam and noticed that the default exclusion glob of *shakespeare* did not match /sdks/go/data/shakespeare/hamlet.txt Is this the sort of glob where I would use ** to traverse directories, or some such? Kenn On Thu, May 20, 2021 at 10:38 AM Andrew Wetmore wrote: > The "about"

Re: Inclusive terminology in Apache Software - a practical approach

The "about" link doesn't seem to lead anywhere. Virus-free. www.avast.com

Re: Inclusive terminology in Apache Software - a practical approach

On 20/05/2021 16.15, Mark Thomas wrote: I like it. Looks like Tomcat has managed to trigger a false positive in CharsetCache.java. You can exclude files and contexts if you click on 'scan settings...' and edit it. There will later on be a per-occurrence action to ignore or mark as

Re: Inclusive terminology in Apache Software - a practical approach

On 20/05/2021 14:22, Daniel Gruno wrote: Hi folks, following the discussion on inclusive naming, I got to thinking and discussing a bit more with Rich and others about practical approaches we could explore under the EDI banner. And thus, I started work on a scanner service for repositories

Re: Inclusive terminology in Apache Software - a practical approach

On 20/05/2021 15.27, Andrew Wetmore wrote: This is a very good idea, Thanks! On the left and right Y axes of the charts, what are the units of measurement? issues found on the left, files processed (and time spent) on the right. I hope I have added that to the charts now :)

Re: Inclusive terminology in Apache Software - a practical approach

This is a very good idea, On the left and right Y axes of the charts, what are the units of measurement? Virus-free. www.avast.com

Inclusive terminology in Apache Software - a practical approach

Hi folks, following the discussion on inclusive naming, I got to thinking and discussing a bit more with Rich and others about practical approaches we could explore under the EDI banner. And thus, I started work on a scanner service for repositories that could identify places where we can