Mazin,

your email triggered me to actually go through the wiki and get some stats. I 
attached a spreadsheet with committers per company and project (I did this 
manually so there might be some minor mistakes but the trend holds). Also the 
companies are sorted by appearance so the order is random.

Seems the TSC has failed miserably enforcing it’s own policies.

The average number of committers is 8.6. The max is 26 the min is 1.  Based on 
the 27 approved projects on the wiki 15 are not in compliance of the policy. 
There are 10 projects with more then 10 committers.

Looking at some of the trends it seems to be a self feeding process one company 
adds more then the others don’t want to be “left out” and respond in kind. So 
it’s more driven by ego/politics then merit in most cases I can see.

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



On Jun 29, 2017, at 9:35 PM, GILBERT, MAZIN E (MAZIN E) 
<[email protected]<mailto:[email protected]>> wrote:

*** Security Advisory: This Message Originated Outside of AT&T ***.
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.

ONAP Community,

I have sent a note on this before, so my apology for sending it again.
It is important that this community follow the guidelines of the TSC on
committers and PTLs. We have provided guidelines that projects should
have between 3-5 committers that have actual development experience
and deep knowledge in the software or release software. While I love
the passion and involvement of the community, I see few projects that
misused those directions and ended up with committers in excess of 10, some
signed up the last minute to steer the PTL vote.

I hesitated to manage and clean-up the committers per advice from
the Linux Foundation, but I will ask the TSC to enforce those guidelines
in future to ensure fair outcomes across all projects.

Thank you.. I will soon share some great news of new exciting members who
are joining ONAP. Thank you again for your hard work to making ONAP
a success and let’s make the Amsterdam Release a blast.

Mazin

_______________________________________________
ONAP-TSC mailing list
[email protected]<mailto:[email protected]>
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Dtsc&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=3WBYkehchaQg0p_gO26aU_ahomnFHCk_-us7kcQebm4&m=rUHhj9ph_CQ3Np2G-F9zUffASbFXC8e__XGg_VFgjtE&s=AOatY2_khrWMjoCancKkJNqTK5U3Z5woGJ-3-uMx4jY&e=

Attachment: CommiterMatrix.xlsx
Description: CommiterMatrix.xlsx

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

Reply via email to