Hi Ramki,
I'm sorry but I don't understand your question. Thanks! -kenny From: Ramki Krishnan <ram...@vmware.com> Date: Tuesday, July 10, 2018 at 11:02 PM To: Kenny Paul <kp...@linuxfoundation.org>, "Christopher Donley (Chris)" <christopher.don...@huawei.com>, Stephen Terrill <stephen.terr...@ericsson.com>, "GILBERT, MAZIN E (MAZIN E)" <ma...@research.att.com>, Phil Robb <pr...@linuxfoundation.org> Cc: onap-tsc <ONAP-TSC@lists.onap.org>, Alex Vul <alex....@intel.com>, John Quilty <john.qui...@ericsson.com>, "gihe...@cisco.com" <gihe...@cisco.com>, "zygmunt_lozin...@uk.ibm.com" <zygmunt_lozin...@uk.ibm.com> Subject: RE: [onap-tsc] #lfn IMPORTANT- Proposed TSC Composition Language Hi Kenny, Phil, Can a candidate stand on behalf of multiple companies? Thanks, Ramki From: ONAP-TSC@lists.onap.org <ONAP-TSC@lists.onap.org> On Behalf Of Kenny Paul Sent: Monday, July 9, 2018 3:09 PM To: Christopher Donley (Chris) <christopher.don...@huawei.com>; Stephen Terrill <stephen.terr...@ericsson.com>; GILBERT, MAZIN E (MAZIN E) <ma...@research.att.com> Cc: onap-tsc <ONAP-TSC@lists.onap.org>; Alex Vul <alex....@intel.com>; John Quilty <john.qui...@ericsson.com>; gihe...@cisco.com; zygmunt_lozin...@uk.ibm.com; Phil Robb <pr...@linuxfoundation.org> Subject: Re: [onap-tsc] #lfn IMPORTANT- Proposed TSC Composition Language Hi Chris, Yes, that is correct. The method was agreed to via CIVS however a vote is needed to actually codify it in the language of the Community Doc. Thanks! -kenny From: "Christopher Donley (Chris)" <christopher.don...@huawei.com> Date: Monday, July 9, 2018 at 12:46 PM To: Kenny Paul <kp...@linuxfoundation.org>, Stephen Terrill <stephen.terr...@ericsson.com>, "GILBERT, MAZIN E (MAZIN E)" <ma...@research.att.com> Cc: onap-tsc <ONAP-TSC@lists.onap.org>, Alex Vul <alex....@intel.com>, John Quilty <john.qui...@ericsson.com>, "gihe...@cisco.com" <gihe...@cisco.com>, "zygmunt_lozin...@uk.ibm.com" <zygmunt_lozin...@uk.ibm.com>, Phil Robb <pr...@linuxfoundation.org> Subject: Re: [onap-tsc] #lfn IMPORTANT- Proposed TSC Composition Language I'm OK with the text. So from a procedural perspective, we already agreed upon the method for TSC member selection, and we are simply voting on whether the proposed changes accurately reflect the agreement, correct? Chris From: <ONAP-TSC@lists.onap.org> on behalf of Kenny Paul <kp...@linuxfoundation.org> Date: Monday, July 9, 2018 at 5:28 AM To: Stephen Terrill <stephen.terr...@ericsson.com>, "GILBERT, MAZIN E (MAZIN E)" <ma...@research.att.com> Cc: onap-tsc <ONAP-TSC@lists.onap.org>, Alex Vul <alex....@intel.com>, John Quilty <john.qui...@ericsson.com>, "gihe...@cisco.com" <gihe...@cisco.com>, "zygmunt_lozin...@uk.ibm.com" <zygmunt_lozin...@uk.ibm.com>, Phil Robb <pr...@linuxfoundation.org> Subject: Re: [onap-tsc] #lfn IMPORTANT- Proposed TSC Composition Language Correct Steve. Approving the language in the Technical Community Document must be approved before we can start the actual process. Thanks! -kenny From: Stephen Terrill <stephen.terr...@ericsson.com> Date: Sunday, July 8, 2018 at 3:10 PM To: "GILBERT, MAZIN E (MAZIN E)" <ma...@research.att.com> Cc: Kenny Paul <kp...@linuxfoundation.org>, onap-tsc <ONAP-TSC@lists.onap.org>, Alex Vul <alex....@intel.com>, John Quilty <john.qui...@ericsson.com>, "gihe...@cisco.com" <gihe...@cisco.com>, "zygmunt_lozin...@uk.ibm.com" <zygmunt_lozin...@uk.ibm.com>, Phil Robb <pr...@linuxfoundation.org> Subject: Re: [onap-tsc] #lfn IMPORTANT- Proposed TSC Composition Language Hi, I think this reflects the agreement. I assume it needs to be closed (voted) in order to start the execution of the process. Best Regards, Stephen Terrill On 8 Jul 2018, at 05:27, GILBERT, MAZIN E (MAZIN E) <ma...@research.att.com> wrote: You captured the main points. Thank you! Mazin On Jul 6, 2018, at 7:10 PM, Kenny Paul <kp...@linuxfoundation.org> wrote: TSC Members and assigned proxies for the July 12th meeting, Please look this over and provide feedback on the language if you feel something needs to be changed. I am hoping for an email a vote on this prior to the TSC meeting if there are no issues. I have created a new (post-LFN) indexed ONAP Technical Community Document which includes the proposed new sections below. These also show up in blue font on the wiki page. Sub sections were added to 4.1.1 and to 4.2 Section Modified: 4.1.1 TSC Members Was: [Reserved for future updating after ONAP transitions to “Steady State” as described in the technical charter.] Now: 4.1.1.1 TSC Membership Definitions · Active Community Members: Anyone from the ONAP community with twenty (20) or more measurable contributions during the previous 12-month period, inclusive of code merged, code reviews performed, wiki page edits, or JIRA activities Operator: Any of the original 9 Platinum Service Providers participating in ONAP at the beginning of 2018. (Specifically: AT&T, Bell, CMCC, China Telecom, Orange, Reliance Jio, Turk Telecom, Verizon and Vodafone) 4.1.1.2 Size and Structure The TSC shall consist of eighteen (18) seats Nine (9) seats on the TSC are to be reserved for Operators Only one (1) person from any company, or group of related companies (as defined in section 4.4.4.1) may be a member at any given time. 4.1.1.2 TSC Member Requirements · Excluding the reserved seats provision of section 4.1.1.2, TSC membership is not limited to LFN member companies · TSC members shall be Active Community Members, notwithstanding the exception granted in section 4.2.3.2 Section Modified: 4.2 TSC Operations The entire 4.2.3 section is newly added 4.2.3 TSC Member Elections 4.2.3.1 Candidate and Voter Eligibility · Any Active Community Member (regardless of LFN membership), is eligible to run for a TSC seat, except as provided for in section 4.2.3.2 · Any Active Community Member (regardless of LFN membership), is eligible to vote in a TSC election · Eligibility is effective as of the date and time the nomination process starts, 4.2.3.2 TSC Member Candidates · · There are no limitations on the number of candidates that can run for a TSC seat, nor is there a limit to the number of candidates from any company, or group of related companies that can run in a TSC election · Candidates must self nominate · At least one person from each Operator must run for that Operator's reserved seat · A provision is granted for an Operator to appoint a person to run for their seat, only in the event that the Operator does not have any eligible Active Community Members at the time of nomination process. 4.2.3.2 TSC Member Election Mechanics · · The election of a TSC Member shall consist of a single stack ranked vote of all candidates via CIVS ( Condorcet: http://en.wikipedia.org/wiki/Condorcet_method); · The top ranked candidate from each Operator will be selected, for a total of nine members, one member from each Operator · The top ranked non-Operator candidates (whether affiliated with a company or an individual contributor), will be selected for the remaining nine seats, with no more than one member per company or group of related companies being selected. Best Regards, -kenny Kenny Paul, Technical Program Manager, The Linux Foundation kp...@linuxfoundation.org, 510.766.5945 San Francisco Bay Area, Pacific Time Zone -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#3365): https://lists.onap.org/g/ONAP-TSC/message/3365 Mute This Topic: https://lists.onap.org/mt/23178568/21656 Mute #lfn: https://lists.onap.org/mk?hashtag=lfn&subid=2743226 Group Owner: onap-tsc+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/ONAP-TSC/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
