From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Hall Subject: Re: Coverity policy for upstream (base) drivers. Date: Fri, 13 Nov 2015 13:49:11 -0500 Message-ID: <20151113184911.GA25051@mhcomputing.net> References: <20151112140508.79489210@xeon-e3> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "dev@dpdk.org" , Stephen Hemminger To: "Mcnamara, John" Return-path: Received: from mail.mhcomputing.net (master.mhcomputing.net [74.208.228.170]) by dpdk.org (Postfix) with ESMTP id E09C0C11C for ; Fri, 13 Nov 2015 19:49:14 +0100 (CET) Content-Disposition: inline In-Reply-To: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Fri, Nov 13, 2015 at 12:12:04AM +0000, Mcnamara, John wrote: > If people haven't already done so I would urge them to sign up and view/fix the defects. > > https://scan.coverity.com/users/sign_up > https://scan.coverity.com/projects/4005 (DPDK) Hi John, I got signed up. Thanks for spearheading this. >>From past experience squashing SA defects on my own code and several previous employers I would like to recommend we band together and configure a SonarQube instance. http://www.sonarqube.org/ This is a really awesome SA, QA, Unit Test, etc. Data aggregation tool. It gives a really nice executive-level view of what is going on in the code. I wrote some custom scripts that integrated between SonarQube and git to email people who checked in new SA defects across all of the aggregated SA tools included in the SonarQube universe. Matthew.