Sure, but do you mean in addition to the very functional Coverity Scan that the project already routinely uses?
https://scan.coverity.com/projects/libreoffice Is that just a "belt + suspenders" idea, or is there really substantive advantage to flushing the code base through another quality check? And, whom would you suggest would host it and take the performance hit on their build system? -- View this message in context: http://nabble.documentfoundation.org/Libreoffice-qa-Possibility-of-monitoring-LibreOffice-code-with-SonarQube-tp4180936p4180953.html Sent from the QA mailing list archive at Nabble.com. _______________________________________________ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: https://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
