Hi all, I agree with the defined below, perhaps we should introduce additional contribution measures, on top of number of Git commits e.g. number of affected/new files, number of code lines etc.
Just my 2 cents :) Best regards, Alla Goldner Open Network Division Amdocs Technology [cid:image003.png@01D32DF7.58233230] From: onap-tsc-private-boun...@lists.onap.org [mailto:onap-tsc-private-boun...@lists.onap.org] On Behalf Of Gildas Lanilis Sent: Thursday, September 14, 2017 11:56 PM To: GILBERT, MAZIN E <ma...@research.att.com>; onap-discuss@lists.onap.org; onap-tsc-priv...@lists.onap.org Subject: Re: [onap-tsc-private] ONAP TSC measures of success Hi, I would recommend looking at: 1. Number of code contribution (Git commits) 2. Mailing list activities Thanks, Gildas ONAP Release Manager 1 415 238 6287 From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Dhananjay Pavgi Sent: Thursday, September 14, 2017 3:43 AM To: GILBERT, MAZIN E (MAZIN E) <ma...@research.att.com<mailto:ma...@research.att.com>>; onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; onap-...@lists.onap.org<mailto:onap-...@lists.onap.org> P <onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>> Subject: Re: [onap-tsc] ONAP TSC measures of success Dear All, Couple of other measures that could be considered: 1. JUNit test coverage across LOC : Indicator of Code Quality (i.e. being unit tested) 2. Number of VNFs successfully on boarded and tested : Indicator of VNF adoption rate for ONAP 3. Number of Integration Test cases covered : Indicator of platform maturity for E-2-E use. thanks & regards, Dhananjay Pavgi Mobile : +91 98220 22264 [cid:image002.png@01CE7323.F2727500] [ONAP_logo_Sig] www.techmahindra.com<http://www.techmahindra.com/> Platinum Member. Visit : http://www.onap.org<http://www.onap.org/> From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of GILBERT, MAZIN E (MAZIN E) Sent: Wednesday, September 13, 2017 10:26 PM To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; onap-...@lists.onap.org<mailto:onap-...@lists.onap.org> P <onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>> Subject: [onap-tsc] ONAP TSC measures of success Dear ONAP Community, I want to start an email dialog which we will follow up in our Paris meeting on technical measures of success of the ONAP platform. What measures we should track and make publicly visible in PR events? I know LOC has been used already. This seems like one of 2-3 other measures we should be tracking. Those measures should be agnostic to any particular release and publicly recognized. Please share your thoughts and ideas. thanks! Mazin ============================================================================================================================ Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html externally http://tim.techmahindra.com/tim/disclaimer.html internally within TechMahindra. ============================================================================================================================ This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer <https://www.amdocs.com/about/email-disclaimer>
_______________________________________________ onap-discuss mailing list onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss
