Hi, Chris, all, With all respect to all opinions expressed (being it your, mine, or someone else’s opinion), our individual opinions will be expressed by our corresponding voting. I think we are mixing different points/questions into a single voting discussion, trying to agree on a single proposal, while, instead, we should take the following questions (and corresponding multiple voting) separately. For example, size of TSC is one point to decide on, timeframe of moving to the steady state is another one, etc.
I identify the following points we need to decide on, each one separately: 1. Timeframe of moving to the steady state (e.g. now or in November) 2. Size of the TSC 3. Maximal number of the same company representatives to the TSC 4. TSC structure (and here we can take, as a basis, all questions Kenny has raised by his email or more, if some points are not covered) 5. Voters eligibility criteria 6. More? Best regards, Alla Goldner Open Network Division Amdocs Technology [cid:image001.png@01D3D8E8.0C103F40] From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Christopher Donley (Chris) Sent: Friday, April 20, 2018 8:24 PM To: Kenny Paul <kp...@linuxfoundation.org>; Phil Robb <pr...@linuxfoundation.org>; onap-tsc@lists.onap.org Subject: Re: [onap-tsc] TSC Composition Proposal Kenny, I think that's the wrong way to frame this. I don't object to any company being represented on the TSC, but I think we need to look at the needs of the community and what leadership structure would best support it. Earlier, Mazin expressed his principles for the new TSC. Here are mine: 1. Everyone on the TSC needs to have 'skin in the game'. Everyone needs to be engaged and making a contribution. Further, we all need to be accountable to the community. As Alex mentioned on one of our calls, ONAP is a large and complicated project, and we need different contributions from people with different skill sets. I think that is valid and important, and and we should recognize myriad contributions. Also, in your feeback slide, you wrote that the TSC was perceived to be: • Company Centric - Not Community Focused • Only a few engage beyond their own company walls or organizational silos • One-way conversations are common versus interactive dialogs with the Community Decisions seem to be made in private by a small subset of people • Opposing Community viewpoints or concerns are often marginalized I think holding elections, where the TSC is accountable to the community, will help with this. 2. The TSC should be of reasonable size to make timely decisions. From my past experience, this is somewhere between 12-15 people. As it is now, we're having trouble reaching quorum with 18. I don't want to see the size of the TSC expanded where it reduces effectiveness. Also, looking at Bitergia, it appears that only 20 companies are contributing to ONAP. I don't want to see the TSC larger than that – then we're starting to get into companies with negligible (or no) contributions. I suggest we target 15 for steady-state, while allowing additional seats for a year for newly-joined platinum members. 3. I have no objections to allowing platinum members who joined less than a year ago to maintain their seat while they formulate their strategy and begin to make contributions. Chris From: <onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org>> on behalf of Kenny Paul <kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org>> Date: Thursday, April 19, 2018 at 6:37 PM To: Phil Robb <pr...@linuxfoundation.org<mailto:pr...@linuxfoundation.org>>, "onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>" <onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>> Subject: Re: [onap-tsc] TSC Composition Proposal Hi TSC Members, I am attempting to get my head around a couple aspects of the discussion. I think that there are a few things we can knock down in advance of next week, which is all I am trying to accomplish here. NOTE- THESE ARE NOT VOTES, but if there are objections or concerns, let's discuss them as they tie into Phil's voting proposals. When considering each of these please DO NOT worry about any potential "order of operations" logic. Each question should be considered as a unique, independent, stand-alone question. If you have no objection to the question you are reading, just move along to the next one. If you have an objection simply state why you think it is a bad idea. :-) - Are there any objections to the former ONAP Platinum Service Provider Members that joined the Program after the launch (specifically Turk Telekom, Verizon, and Vodafone), being allowed to keep an appointed representative on the TSC for [election date] plus 12 months? - Are there any objections to any former ONAP Platinum Service Provider Members (specifically AT&T, Bell Canada, China Mobile, China Telecom, Orange, Reliance Jio, Turk Telekom, Vodafone & Verizon) being able to appoint a representative to the TSC for [election date] plus 12 months if someone from their company does not get elected? - Are there any objections to any former ONAP Platinum Members (i.e all of the existing TSC Companies + Verizon) being able to appoint a representative to the TSC for [election date] plus 12 months if someone from their company does not get elected? - Are there any objections to a service provider LFN Platinum Member that joins the ONAP Program from being able to appoint a representative to the TSC from the time they join ONAP until the first scheduled TSC election following 12 months of ONAP TSC membership? - Are there any objections to any LFN Platinum Member that joins the ONAP Program from being able to appoint a representative to the TSC from the time they join ONAP until the first scheduled TSC election following 12 months of ONAP TSC membership? - Are there any objections to a service provider LFN Member at any membership level that joins the ONAP Program from being able to appoint a representative to the TSC from the time they join ONAP until the first scheduled TSC election following 12 months of ONAP TSC membership? -kenny 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-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc