+1 I agree with the proposal as well – best to keep the current structure until Beijing Release (May-18). Also, I am happy to participate in the proposed WG to discuss/recommend the new TSC structure.
Regards, Rajesh From: <[email protected]> on behalf of Phil Robb <[email protected]> Date: Wednesday, December 13, 2017 at 5:52 PM To: "Frank Brockners (fbrockne)" <[email protected]> Cc: onap-tsc <[email protected]> Subject: Re: [onap-tsc] Planning for ONAP TSC Elections Thanks for the feedback Frank and your willingness to help on the WG if we choose to go that way. Other TSC members, please let me know your thoughts when you are able. Thanks, Phil. On Wed, Dec 13, 2017 at 4:46 PM, Frank Brockners (fbrockne) <[email protected]<mailto:[email protected]>> wrote: Hi Phil, your suggestion to keep the current structure stable until Beijing is released makes sense. I also support your proposal to form a task force which compiles a suggestion for TSC composition and membership in the “stable” phase moving forward. Other projects which move to LFN have taken a similar approach, i.e. form a WG and aggregate suggestions. Should such a task force be established, I’d like to participate. Thanks, Frank From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Phil Robb Sent: Mittwoch, 13. Dezember 2017 16:03 To: onap-tsc <[email protected]<mailto:[email protected]>> Subject: [onap-tsc] Planning for ONAP TSC Elections Hello ONAP TSC Members: As documented in the ONAP Project Charter, the TSC is tasked with figuring out how to populate the TSC in a meritocratic manner beginning 12 months after the project launch, which was March 2017. Hence it is time to start planning this transition. To kick this process off, I have the following suggestions: - Given that March 2018 is in the middle of the Beijing release cycle, I suggest we postpone the TSC election until directly after the Beijing release in late May. We should discuss and approve our method of populating the TSC by the end of March, but not actually execute it until late May or early June. Please let me know if you think this is a good or bad idea. - I suggest we form a small workgroup to create an initial proposal for discussion with the broader TSC. Some topics to consider when architecting the TSC makeup include: - Constituencies. Are there different constituencies that need representation on the TSC? - PTLs. Having an election of PTLs to populate the TSC one possible way to do it. These PTLs may be from different constituencies, or just At-Large. - Committers-At-Large (CALs). Some seats can come from the committer community at large. - Particular Roles. Possibly have the PTL from the Integration Team, or the Release Manager as voting members of the TSC as an example of "special" roles that should have TSC representation. - Company Caps - To ensure that a single company does not have too much voting power within the TSC, a limit (usually defined as a percentage) is imposed on how many TSC members can come from the same organization (or affiliated organization). - TSC size. Common guidance is to keep the TSC size somewhere between 7 and 19. 11,13, and 15 are common sizes. Depending on how the TSC is populated the size may vary or may be static. Please let me know your thoughts. If you think a workgroup to put an initial proposal together is a good idea, please indicate that. If you think we should have a few open discussions to set an initial direction please indicate that. If a workgroup seems reasonable, and you would like to participate in that group please indicate that as well. I look forward to the discussion. Thanks, Phil. -- Phil Robb Executive Director, OpenDaylight Project VP Operations - Networking & Orchestration, The Linux Foundation (O) 970-229-5949<tel:(970)%20229-5949> (M) 970-420-4292<tel:(970)%20420-4292> Skype: Phil.Robb -- Phil Robb Executive Director, OpenDaylight Project VP Operations - Networking & Orchestration, The Linux Foundation (O) 970-229-5949 (M) 970-420-4292 Skype: Phil.Robb
_______________________________________________ ONAP-TSC mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-tsc
