On 28 February 2016 at 15:59, Jaroslaw Staniek <stan...@kde.org> wrote:
> 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. > PS: If someone wants to help for Kexi in particular, learn something and see what kind of human errors Coverity finds: please contact me so I assign you to this patch review: https://phabricator.kde.org/D1024 > -- > 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 > -- 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@kde.org https://mail.kde.org/mailman/listinfo/calligra-devel