If we do proceed with this motion, I think we should separate out PTLs from the other positions. PTLs are responsible for managing a single project, whereas the other positions are responsible for cross-project leadership. In some cases, it makes sense that one of the project leaders also leads the subcommittee (such as closed-loop subcommittee). In others, it helps maintain a connection between the subcommittee work and the projects.
I have no objection to saying that a single person can only lead one cross-project initiative (TSC Chair, Vice Chair, subcommittee Chair), but that shouldn't extend to PTLs. Thanks, Chris From: <onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org>> on behalf of Alla Goldner <alla.gold...@amdocs.com<mailto:alla.gold...@amdocs.com>> Date: Monday, May 7, 2018 at 1:55 AM To: "Gadiyar, Rajesh" <rajesh.gadi...@intel.com<mailto:rajesh.gadi...@intel.com>>, Kenny Paul <kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org>> Cc: onap-tsc <onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>> Subject: Re: [onap-tsc] TSC Members Composition Survey RFC - Respond by 18:00 Pacific time, May 7 Hi all, Also, additional point I’ve been thinking of. Last year we had some proposals on the table to limit number of positions (e.g. chairs, vice-chairs, PTLs etc.) to 1 per single person. It never came to voting, as it was too controversial back then. Perhaps, we have a more mature community now to move forward and see if we can reach consensus also on this point. Best regards, Alla Goldner Open Network Division Amdocs Technology [cid:image001.png@01D3E5FA.3EEC3AD0] From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Gadiyar, Rajesh Sent: Sunday, May 06, 2018 5:43 PM To: Kenny Paul <kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org>> Cc: onap-tsc <onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>> Subject: Re: [onap-tsc] TSC Members Composition Survey RFC - Respond by 18:00 Pacific time, May 7 Hello Kenny, Thanks! Section 2b reads: b. TSC Voting Members i. “Startup Period”: From date of creation of the ONAP Project a Series of LF Projects, LLC (“Project Launch”) until June 30, 2018 (such period the “Startup Period”), the TSC voting members will consist of one appointee from each organization listed as having TSC appointees on ONAP.org. All TSC voting members will be listed on ONAP.org. ii. “Steady State”: After the Startup Period, the size, makeup and procedure for determining voting members of the TSC will be as determined by the TSC and documented on the ONAP web site. I am NOT asking for a redefinition. I am proposing the following: B) Guaranteeing TSC seats for LFN's Platinum Member companies. Another option that came to mind that has not been brought up before is guaranteeing 1 TSC seat for each of the top 15 code contributing companies (rewards meritocracy and actual code contributions to ONAP) and an additional 5 seats reserved for Operators. This will bring the total TSC to 20 members which is reasonable. Regards, Rajesh From: Kenny Paul <kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org>> Date: Friday, May 4, 2018 at 2:12 PM To: Rajesh Gadiyar <rajesh.gadi...@intel.com<mailto:rajesh.gadi...@intel.com>> Cc: onap-tsc <onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>> Subject: Re: [onap-tsc] TSC Members Composition Survey RFC - Respond by 18:00 Pacific time, May 7 Hi Rajesh, please refer to Section 2b of the ONAP Project a Series of LF Projects, LLC Technical Charter<https://www.onap.org/wp-content/uploads/sites/20/2018/01/ONAP-Project-a-Series-of-LF-Projects-LLC-Technical-Charter-12-22-2017-FINAL.pdf> below. in the context of Question #1 unless your request is to redefine both the "Startup Period" and "Steady State" definitions, a specific date is required. I don't think that a redefinition is what you are really asking for. My interpretation of your actual ask is that you would like to see a TSC Composition question added about A) guaranteeing seats for ONAP Platinum Members of record from 2017 or B) guaranteeing seats for any one of the LFN's Platinum Member companies. An alternative interpretation may be that you would like to see qualification options added to Question #11 for C) only candidates from one of the ONAP Platinum Members of record from 2017 are qualified to hold a seat on the ONAP TSC, or D) only candidates from any one of the LFN's Platinum Member companies are qualified to hold a seat on the ONAP TSC. Is A, B, C or D correct, or do you indeed want to redefine the state definitions? b. TSC Voting Members i. “Startup Period”: From date of creation of the ONAP Project a Series of LF Projects, LLC (“Project Launch”) until June 30, 2018 (such period the “Startup Period”), the TSC voting members will consist of one appointee from each organization listed as having TSC appointees on ONAP.org. All TSC voting members will be listed on ONAP.org. ii. “Steady State”: After the Startup Period, the size, makeup and procedure for determining voting members of the TSC will be as determined by the TSC and documented on the ONAP web site. Thanks! -kenny From: "Gadiyar, Rajesh" <rajesh.gadi...@intel.com<mailto:rajesh.gadi...@intel.com>> Date: Friday, May 4, 2018 at 11:08 AM To: Kenny Paul <kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org>> Cc: onap-tsc <onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>> Subject: Re: [onap-tsc] TSC Members Composition Survey RFC - Respond by 18:00 Pacific time, May 7 Hi Kenny: please add an explicit option like I stated below; and let’s provide it as an option for TSC to vote. Many TSC members are supportive of this. “Other” as a write in option does not capture my input. You can still add it as a separate option if you like. Regards, Rajesh On May 4, 2018, at 10:46 AM, Kenny Paul <kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org>> wrote: Hi Rajesh, Again #1 is a "When" question about moving to "Steady State" and not a "What" question about the composition of the TSC. I will add "Other" as a write in option for Question #1 to address alternative time frames. Thanks! -kenny From: "Gadiyar, Rajesh" <rajesh.gadi...@intel.com<mailto:rajesh.gadi...@intel.com>> Date: Friday, May 4, 2018 at 9:37 AM To: Kenny Paul <kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org>> Cc: onap-tsc <onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>> Subject: Re: [onap-tsc] TSC Members Composition Survey RFC - Respond by 18:00 Pacific time, May 7 Hi Kenny: Never has a negative connotation. I am simply proposing an option where all LFN platinum members have a TSC membership (supplemented with a few exta seats for non platinum significant contributors). I am supportive of putting enough guardrails for the qualifications to be a TSC member and the contribution expectations. /R From: Kenny Paul <kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org>> Date: Friday, May 4, 2018 at 8:10 AM To: Rajesh Gadiyar <rajesh.gadi...@intel.com<mailto:rajesh.gadi...@intel.com>> Cc: onap-tsc <onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>> Subject: Re: [onap-tsc] TSC Members Composition Survey RFC - Respond by 18:00 Pacific time, May 7 Hi Rajesh, As this is a "when" question the implication of your suggested #4 is "Never". Am I understanding that correctly? Thanks! -kenny From: "Gadiyar, Rajesh" <rajesh.gadi...@intel.com<mailto:rajesh.gadi...@intel.com>> Date: Thursday, May 3, 2018 at 8:34 PM 1. When should the ONAP TSC move from “Startup” to “Steady” state operations at which point the TSC should be populated, not by Platinum Member designates, but instead by some other means, for which the TSC is responsible for defining? 1. As soon as the new method for populating the TSC is defined 2. After the Beijing Release 3. After the Casablanca Release 4. Keep the current TSC composition with Platinum members automatically get a TSC seat. 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
_______________________________________________ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
