Static code analysis - the easiest way to improve

[Tomas Mecir]

Well, I'd like to, but when I log in and try to access the KDE stuff,
I can see the summary, but accessing the actual defect list gives me a
red box with this:

It may take a few minutes before you can view your defects, when you
change your email or password or sign-in with Github for the first
time.

Been that way for more than a week now - tried both github and
password login. Someone else was reporting the same problem, I think.
Any ideas?

Tomas


2016-02-28 15:59 GMT+01:00 Jaroslaw Staniek <staniek at kde.org>:
> Hi,
> Just to remind. If someone has some time to fix bugs, KDE
> apps/Calligra/Frameworks static analysis is the easiest way to improve
> Calligra.
> Code defects are well explained (like uninitialized variables or
> NULL-related failures). Much easier than actually reading that bug reports,
> analysing them and testing.
>
> So please, these are low-hanging fruits. Hundreds of them.
>
> Visit:
> https://scan.coverity.com/projects/kde
> You can request access if you don't have it yet.
>
> Let us know in this thread if code you're interested in isn't there.
>
> --
> regards, Jaroslaw Staniek
>
> KDE:
> : A world-wide network of software engineers, artists, writers, translators
> : and facilitators committed to Free Software development - http://kde.org
> Calligra Suite:
> : A graphic art and office suite - http://calligra.org
> Kexi:
> : A visual database apps builder - http://calligra.org/kexi
> Qt Certified Specialist:
> : http://www.linkedin.com/in/jstaniek
>
> _______________________________________________
> calligra-devel mailing list
> calligra-devel at kde.org
> https://mail.kde.org/mailman/listinfo/calligra-devel
>