+1 From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of SPATSCHECK, OLIVER Sent: Friday, June 30, 2017 11:57 AM To: Andrew Grimberg <agrimb...@linuxfoundation.org> Cc: t...@lists.onap.org Subject: Re: [onap-tsc] Committers and voting - Please read.
***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. +1 On Jun 30, 2017, at 11:41 AM, Andrew Grimberg <agrimb...@linuxfoundation.org<mailto:agrimb...@linuxfoundation.org>> wrote: To help weed things down I would suggest that every repository in a project be required to define a distinct list of committers and not allow an umbrella project to define top level committers. That list may be the same across several of them, but they should be distinct to each repository and hold to the same configuration of just a few committers per repository. It may mean a bit more administrative overhead for the management, and definitely for the set-up but it will clearly define who does, and does not have domain knowledge on a particular set of code.
_______________________________________________ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
