EBN Still Needed?
vkrause at kde.org
Wed Mar 27 17:24:36 GMT 2019
On Tuesday, 26 March 2019 21:15:31 CET Allen Winter wrote:
> I was notified today that the Krazy runs on the EBN have been stuck (due to
> a stale lockfile) for over 3 months. Is this an indication that nobody
> looks at the EBN reports any longer?
> I still maintain Krazy and am happy to make modifications, but I don't see
> the point unless someone actually reads and acts on the reports.
> Note that clazy does replace Krazy on most everything (C++) so it could
> very well be that people are relying on Clazy instead of Krazy.
> This is not about the API dox generation side of things, which of course we
> But has the EBN code and documentation checking service out lived its
> usefulness? Shut it down?
I think for the C++ checks it's indeed due to Clazy/clang-tidy outperforming
Krazy, both in terms of precision and in runtime performance. And for code I'm
working on I usually run these tools locally indeed.
However Krazy is more than C++ checks, and EBN is more than Krazy. I do think
it's very valuable to have the infrastructure to do "global" scans on all our
repositories, see e.g. the work in D19996 for finding insecure http: links
anywhere (code, docs, website content, infrastructure config, etc). Continuous
checks in commit hooks or the CI will help us to catch newly introduced issues
there, but it wont help in getting this fixed everywhere in the existing
License compatibility/maitenance is another topic where global C++ independent
scans are useful (and where krazy already has checks), e.g. to identify and
fix the remaining GPLv2 only material (which is incompatible with GPLv3+ and
Apache 2 licensed work).
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 195 bytes
Desc: This is a digitally signed message part.
More information about the kde-core-devel