Dear TSC members, I would like to sincerely thank you all for your support. Heartiest Congratulations and best wishes to the new TSC!
I echo what Catherine has said that we all need to ensure ONAP becomes a reference implementation for SDN / NFV. Our ONAP engagement and contribution shall continue with this objective. Best Wishes once again to the entire TSC team. Thanks, Milind From: [email protected] <[email protected]> On Behalf Of Catherine LEFEVRE via Lists.Onap.Org Sent: Thursday, November 21, 2019 3:23 PM To: [email protected] Subject: Re: [onap-tsc] ONAP TSC Election Results Dear ONAP Community, I would like to thank again the TSC members who are departing Stephen Terrill, Chaker Al-Hakim, Milind Jawaldi and Yan Chen. I hope you will continue to remain engaged as contributing members in ONAP. For the new TSC members - Ciaran Johnson, Ranny Haiby, Seshu Kumar and ZongHe Huang - Welcome on Board ! I would like to extend my congratulations for being elected to serve. The Community relies on us to ensure that ONAP will continue to be the reference automation platform for Software Defined Network. Best regards Catherine From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Kenny Paul Sent: Wednesday, November 20, 2019 7:12 PM To: [email protected]<mailto:[email protected]> Subject: [onap-tsc] ONAP TSC Election Results (bcc'd to onap-discuss) I am pleased to announce the results of the ONAP Technical Steering Committee election. As a reminder to all, here is what the TSC is responsible for all technical oversight of the open source Project as per the Technical Charter of ONAP Project a Series of LF Projects, LLC. This includes: * Coordinating the technical direction of the Project * Approving project or system proposals (including, but not limited to, incubation, deprecation, and changes to scope) * Organizing sub-projects and removing projects * Creating sub-committees or working groups to focus on cross-project technical issues and requirements * Appointing representatives to work with other open source or open standards communities * Establishing community norms, workflows, issuing releases, and security issue reporting policies * Establishing, maintaining and modifying policies to ensure the integrity, vetting and security of the ONAP Project code base * Approving and implementing policies and processes for contributing code and coordinating with the Series Manager to resolve matters that may arise * Discussing, seeking consensus, and where necessary, voting on technical matters relating to the code base that affect multiple projects * Coordinating any marketing, events, or communications regarding the Project with the LF Projects Manager or their designee * Establishing work flow procedures for the submission, approval, and closure/archiving of projects * Setting requirements for the promotion of Contributors to Committer status, as applicable * Amending, adjusting, refining and/or eliminating the roles of Contributors/Committers, and create new roles, and publicly document any roles * Establishing the size, makeup and procedure for determining voting members of the TSC Section 4.3 of the ONAP Technical Community Document also highlights the following in the context of the Technical Charter: * Defining ONAP's release vehicles (such as a Coordinated Release) that align with the Project' mission, * Fostering cross-project collaboration, * Serving as ONAP's primary technical liaison body with other consortiums and groups, * Developing an architecture, * Setting simultaneous release dates, * Defining release quality standards, * Defining technical best practices and community norms (including the establishment and maintenance of a Development Process), * Monitoring technical progress, * Mediating technical conflicts between Committers and PTLs, * Organizing inter-project collaboration, * Coordinating technical community engagement with the end-user community. The new membership is effective immediately. Alphabetical by Name. Reserved seats in Bold Alexis de Talhouet Bell Canada Alla Goldner Amdocs Andreas Geissler Deutsche Telekom Bin Yang Windriver Catherine Lefevre AT&T Ciaran Johnston Ericsson Davide Cherubini Vodafone Eric Debeau Orange Jason Hunt IBM Lingli Deng China Mobile Murat Turpcu Turk Telekom Ning So Reliance Jio Ranny Haiby Samsung Seshu Kumar Huawei Srini Addepalli Intel Timo Perala Nokia Viswa Kumar Skand Priya Verizon ZongHe Huang China Telecom Official results: https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_fd493be64cce6c89<https://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__civs.cs.cornell.edu_cgi-2Dbin_results.pl-3Fid-3DE-5Ffd493be64cce6c89%26d%3DDwMFAg%26c%3DLFYZ-o9_HUMeMTSQicvjIg%26r%3Dc31OYuaPawMl_ySS_voXJQ%26m%3DWi_FHtxl_aR2GUhI89BvWDsAagR-Zm6u-if7GEh0P1o%26s%3DJ2ITc_GP9ebocJyKRshoWEkFnMxdpwR1qfwvW7af5jI%26e%3D&data=02%7C01%7Cmilindj%40techmahindra.com%7C2c4ae59ffa854a30478208d76e689696%7Cedf442f5b9944c86a131b42b03a16c95%7C0%7C0%7C637099267815607840&sdata=ncsxRrPkjFHcUMzXZ%2FDfXPHv4fSU%2BecboSj6IFZOPlQ%3D&reserved=0> Thanks! -kenny Caution: Please do not click links or open attachments unless you recognize the sender and know the content is safe. ============================================================================================================================ Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html externally http://tim.techmahindra.com/tim/disclaimer.html internally within TechMahindra. ============================================================================================================================ -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#5680): https://lists.onap.org/g/onap-tsc/message/5680 Mute This Topic: https://lists.onap.org/mt/60965239/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
