(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

 

 

Thanks!

-kenny

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#5671): https://lists.onap.org/g/onap-tsc/message/5671
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]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to