On 06/30/2017 07:00 AM, SPATSCHECK, OLIVER  (OLIVER) wrote:

> I think the TSC needs to either step up and enforce it’s own rules or
> abandon the rule altogether. The current status quo punish people which
> play by the rules which I would think is not the intend of the TSC.
> 
> I would be interested to hear how the open source “gurus” have handled
> this in the past as I suspect this has happened before in other projects.

Oliver,

As you state, the TSC sort of needs to be more willing to vote -1 on
creation if the committer list is really bad. Our other communities have
generally held the line during the review process so don't really have
the problem. What we've seen instead is that as a project matures the
list may grow to be a bit larger than is initially thought to be good,
but the number of committers tends to flex up to what is needed instead
of trying to trim down.

What you end up needing to do is have the PTL start working on trimming
the committer list and have current committers voluntarily step down.

I'll also note, that the large lists of committers is also likely partly
a result of the umbrella project methodology of committer definition as
person X may need committer on sub-project Y but with how the lists are
currently defined, it's basically only at the top level umbrella level.

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.

-Andy-

-- 
Andrew J Grimberg
Lead, IT Release Engineering
The Linux Foundation

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
ONAP-TSC mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-tsc

Reply via email to