Re: [onap-tsc] CALL FOR NOMINATIONS: ONAP TSC ELECTION

[Milind Jalwadi]

Hi ONAP Community members,

I would like to nominate myself for the ONAP TSC seat. A profile of myself is 
specified below for your kind consideration -

Biography
Milind has over 18+ years of IT experience with the blend of both Telecom 
domain and technology.
Milind has been in Telecom domain and been an active witness of transformation 
in the industry from the SS7 / Intelligent Networks (IN) days till date as we 
are witnessing another big transformation in the telecom industry. Through Tech 
Mahindra, Milind has been instrumental in assisting various telecom operators 
successfully reap the benefits of the transformation at the respective stages 
of evolution.
Milind is a co-author of patent claim titled "System and methods to achieve 
interworking between RCS and non RCS networks" which is currently under 
examination. He has also show-cased TechM solutions at industry events such as 
Mobile World Congress.
He holds a bachelor degree in computer engineering and is currently leading SDN 
and NFV initiatives within Tech Mahindra.

Candidate's Statement
In the community endeavor to make ONAP adaptable by telecom operators of all 
sizes, I would like to nominate myself for the ONAP TSC seat and contribute in 
making ONAP a preferred open source choice for operator's SDN / NFV solution.
Summary of my important ONAP contributions -
Proposed new stories along with the solution design in Policy and SO components 
to support multiple scale-out operations for any given VF module and without 
any involvement of manual steps.
Please refer the JIRA links -
https://jira.onap.org/browse/POLICY-503
https://jira.onap.org/browse/SO-361
https://jira.onap.org/browse/POLICY-610
https://jira.onap.org/browse/SO-588
https://jira.onap.org/browse/POLICY-502

Ideas on modeling VNFCs, VNFs and service suggested. Refer -
https://wiki.onap.org/pages/viewpage.action?pageId=1015852=11929829#comment-11929829

Link To Bitergia stats:
https://onap.biterg.io/goto/09dbf13de1eae1f11fe8b0bc1acc18d0

Stats from https://wiki.onap.org/pages/viewpage.action?pageId=38113224

[cid:image002.png@01D42D6D.0223E8E0]

Thanks,
Milind Jalwadi

-



[https://lists.onap.org/g/ONAP-TSC/profilephoto/2743359]Kenny Paul
Jul 18   #3391  

Nominations for seats on the ONAP TSC officially open @ 17:00 Pacific Time, 
Tuesday, July 17, 2018
If you are interested in running for a seat on the TSC, please read all of this 
information carefully


Who is eligible to Run:  Any Active Community Members as of 17:00 Pacific Time, 
Tuesday, July 17, 2018- There is NO limit to the number of candidates from any 
single company that can run for a seat.

4.1.1.1 TSC Membership 
Definitions
  Active Community Member: 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



Self-Nomination Phase

Individuals interested in running for a TSC position MUST REPLY-ALL TO THIS 
ORIGINAL EMAIL with your intention to run before 17:00 Pacific time, July 31st.

NOTE: Replying to another candidate's self-nomination email announcing your own 
self-nomination is considered a blatant disregard for open source community 
norms. If you do that, you should probably re-assess both your qualifications 
and motivations for leading a collaborative community such as this.

Your self-nomination email must include a link to your stats in Bitergia 
(instructions on how to do 
this).
It is strongly recommended that candidates also include a small head-shot, a 
short biography and statement of intent on why you would be a good person to 
hold a seat on the TSC.

As a courtesy, it is also requested that you fill in the  2018 TSC Election 
Candidates wiki 
page with that same information. Filling out the wiki page is NOT in lieu of 
sending the email as required, but it will greatly help facilitate the process 
of the elections.



Special Provision for the original 9 ONAP Operators:  There are 9 seats 
reserved for the nine original ONAP Platinum Service Provider members. Each of 
these Operators is REQUIRED to have at least one person nominate themselves for 
their seat on the TSC. If and only if an Operator does not have any eligible 
Active Community Members at the time of nomination process, they may appoint a 
nominee to run in the election.  In such cases, the nominee must indicate that 
they are exercising a provisional nomination in their email. (Refer to 4.2.3.2 
TSC Member 
Candidates)
*
* The nomination 

Re: [onap-tsc] CALL FOR NOMINATIONS: ONAP TSC ELECTION

[Chen Yan]

 
 
  
  
  
  Dear ONAP Community,   I would like to self-nominate for the ONAP TSC election, representing China Telecom (Platinum Service Provider Seat).
  
   
  In the past 2 years, I have been serving on the open source communities extensively, including the contribution to ODL,working as the Open-O project TSC, and leading China Telecom contributions in ONAP Benchmark sub-Project. Meanwhile our team established ONAP Lab at China Telecom, successfully achieved vCPE use case E2E connection based on ONAP Beijing Release. Also I was the main contact for the past Casablanca Developer Event hosted in Beijing. And currently, I am ONAP EUG member and LFN MAC member, created and kept promoting the ONAP Tencent Channel.
  
   
  I would enjoy the opportunity to continue working in the ONAP community as a TSC representative, and engage myself in improving ONAP maturity and accelerating its potential adoption by operators as the de-facto automation platform.
  
  Please refer to below link for my Bitergia stats as an active community/code contributor: 
  https://onap.biterg.io/goto/229c081f65d6ab8285c664cf117a82e6 
  
  Short Bio:
   I am a Project Manager at China Telecom Beijing Research Institute and have worked in the telecommunications industry for more than 10 years, including the past 4 years focused on SDN/NFV, mobile network and cloud. Currently I am a core member of the team for architecture and service enabling design of future operation support platform.   Thank You & All the Best Yan Chen China Telecom Email: chenyan@chinatelecom.cn
  
  -- 原始邮件 --发件人：Kenny Paul "kp...@linuxfoundation.org"时　间：2018/07/18 08:02:36 星期三收件人：onap-tsc "ONAP-TSC@lists.onap.org"抄送人：主　题：[onap-tsc] CALL FOR NOMINATIONS: ONAP TSC ELECTION
  
   Nominations for seats on the ONAP TSC officially open @ 17:00 Pacific Time, Tuesday, July 17, 2018
   If you are interested in running for a seat on the TSC, please read all of this information carefully

   Who is eligible to Run: Any Active Community Members as of 17:00 Pacific Time, Tuesday, July 17, 2018- There is NO limit to the number of candidates from any single company that can run for a seat.
   4.1.1.1 TSC Membership Definitions Active Community Member: 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

   Self-Nomination Phase 
   Individuals interested in running for a TSC position MUST REPLY-ALL TO THIS ORIGINAL EMAIL with your intention to run before 17:00 Pacific time, July 31st. 
   NOTE: Replying to another candidate's self-nomination email announcing your own self-nomination is considered a blatant disregard for open source community norms. If you do that, you should probably re-assess both your qualifications and motivations for leading a collaborative community such as this. 
   Your self-nomination email must include a link to your stats in Bitergia (instructions on how to do this). It is strongly recommended that candidates also include a small head-shot, a short biography and statement of intent on why you would be a good person to hold a seat on the TSC.  
   As a courtesy, it is also requested that you fill in the 2018 TSC Election Candidates wiki page with that same information. Filling out the wiki page is NOT in lieu of sending the email as required, but it will greatly help facilitate the process of the elections.

   Special Provision for the original 9 ONAP Operators: There are 9 seats reserved for the nine original ONAP Platinum Service Provider members. Each of these Operators is REQUIRED to have at least one person nominate themselves for their seat on the TSC. If and only if an Operator does not have any eligible Active Community Members at the time of nomination process, they may appoint a nominee to run in the election. In such cases, the nominee must indicate that they are exercising a provisional nomination in their email. (Refer to 4.2.3.2 TSC Member Candidates) 
   ·   
   ·  The nomination phase begins 17:00 Pacific Time, Tuesday, July 17, 2018
   ·  The nomination phase ends 17:00 Pacific Time, Tuesday, July 31, 2018
   ·   
   Election Phase

   Who is eligible to Vote: Any Active Community Members as of 17:00 Pacific Time, Tuesday, July 17, 2018
   A Condorcet election will be held using the CIVS voting system. Active Community Members will receive an invitation to vote from CIVS.
   ·  The election phase will begin with the distribution of the CIVS poll via email from the application
   ·  The election phase will end two (2) weeks later in the same time zone the poll was initiated from
   Election Results  
   ·   
   
The election of TSC Members shall consist of a single stack ranked vote of all candidates  
Only the top ranked candidates from any single company will be elected; if the top 10 vote gette

Re: [onap-tsc] CALL FOR NOMINATIONS: ONAP TSC ELECTION

[Ning So]

ONAP Community,

I would like to humbly self-nominate for the ONAP TSC election.  I have 
frequently served as the proxy of Reliance Jio to ONAP TSC since the founding 
of the community last year.  I have participated in the ONAP TSC weekly 
meetings frequently.  I have also been working on a new ONAP project proposal 
called Open Test Framework in the recent months.

I would enjoy the opportunity to continue working in the ONAP community as a 
TSC representative, contributing to the maturity and adoption of the platform 
in the field, and ensuring practicality and consumability of ONAP in the 
operator environment.

I am the Head of Advanced Technical Services at Reliance Jio, and have worked 
in the telecommunications industry for over 20 years.  I am leading a team of 
senior network architects covering the company's end-to-end network strategy, 
evolution, engineering, and operations on both wireless and wireline networks.  
I have been actively working on  SDN/NFV related technologies since the very 
early days of their technical inception.  I founded and ran a SDN/NFV 
Orchestration company before I joined Reliance Jio.  I have led network 
architecture, planning, and engineering teams working on Cloud /Data Center 
Networks and IP/MPLS/Ethernet networks at other Tier 1 operators. I was also 
actively involved in IETF community for many years

Thank you for your consideration.

Bitergia stats:
https://onap.biterg.io/goto/bcf30dc513ea2041588437509c241d8a


Ning So



From:"Kenny Paul" 
mailto:kp...@linuxfoundation.org>>
To:onap-tsc mailto:ONAP-TSC@lists.onap.org>>
Date:07/17/2018 07:02 PM
Subject:    [onap-tsc] CALL FOR NOMINATIONS: ONAP TSC ELECTION
Sent by:ONAP-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org>




Nominations for seats on the ONAP TSC officially open @ 17:00 Pacific Time, 
Tuesday, July 17, 2018
If you are interested in running for a seat on the TSC, please read all of this 
information carefully


Who is eligible to Run:  Any Active Community Members as of 17:00 Pacific Time, 
Tuesday, July 17, 2018- There is NO limit to the number of candidates fromany 
single company that can run for a seat.

4.1.1.1 TSC Membership 
Definitions<https://wiki.onap.org/display/DW/ONAP+Technical+Community+Document#ONAPTechnicalCommunityDocument-4.1.1.1TSCMembershipDefinitions>
 Active Community Member: 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



Self-Nomination Phase

Individuals interested in running for a TSC position MUST REPLY-ALL TO THIS 
ORIGINAL EMAIL with your intention to run before 17:00 Pacific time, July 31st.

NOTE: Replying to another candidate's self-nomination email announcing your own 
self-nomination is considered a blatant disregard for open source community 
norms. If you do that, you should probably re-assess both your qualifications 
and motivations for leading a collaborative community such as this.

Your self-nomination email must include a link to your stats in 
Bitergia(instructions on how to do 
this)<https://wiki.onap.org/display/DW/Getting+Your+Stats+From+Bitergia>.
It is strongly recommended that candidates also include a small head-shot, a 
short biography and statement of intent on why you would be a good person to 
hold a seat on the TSC.

As a courtesy,it is also requested that you fill in the  2018 TSC Election 
Candidates<https://wiki.onap.org/display/DW/2018+TSC+Election+Candidates>wiki 
pagewith that same information. Filling out the wiki page is NOT in lieu of 
sending the email as required, but it will greatly help facilitate the process 
of the elections.



Special Provision for the original 9 ONAP Operators:  There are 9 seats 
reserved for the nine original ONAP Platinum Service Provider members. Each of 
these Operators is REQUIRED to have at least one person nominate themselves for 
their seat on the TSC. If and only if an Operator does not have any eligible 
Active Community Members at the time of nomination process, they may appoint a 
nominee to run in the election.  In such cases, the nominee must indicate that 
they are exercising a provisional nomination in their email. (Refer to 4.2.3.2 
TSC Member 
Candidates<https://wiki.onap.org/display/DW/ONAP+Technical+Community+Document#ONAPTechnicalCommunityDocument-4.2.3.2TSCMemberCandidates>)
*
* The nomination phase begins 17:00 Pacific Time, Tuesday, July 17, 2018
* The nomination phase ends 17:00 Pacific Time, Tuesday, July 31, 2018
*

Election Phase



Who is eligible to Vote:Any Active Community Members as of 17:00 Pacific Time, 
Tuesday, July 17, 2018

A Condorcet election will be held using the CIVS voting 
system<https://wiki.onap.org/display/DW/Voting+Best+Practices>. Active 
Comm

Re: [onap-tsc] CALL FOR NOMINATIONS: ONAP TSC ELECTION

[Kenny Paul]

We did receive the required 18 nominations by the 5:00 deadline today. Thank 
you to all that responded on time!

 

HOWEVER, not all of the self-nominations are qualified as per the provisions of 
the Community document 4.2.3 TSC Member Elections

As such I am invoking the provision approved by the TSC to extend the 
nomination period by one week, until 5 PM Pacific, August 7th 
Any new nominees are still bound by the original provisions of the call for 
nominations. https://lists.onap.org/g/ONAP-TSC/message/3391
 

Please note that I have locked the candidate wiki page at this time. Any 
updates will need to be routed through me.

 

Given the concerns raised on the TSC list regarding some aspects of the 
election and qualifications, I would propose making that discussion the top 
priority for this week's TSC meeting. I'll try to compress housekeeping and 
request some time on the PTL agenda for the landing page template. The current 
agenda includes the following:

 

10 m Housekeeping 

Kenny Paul

 

10 m  Release Status   

Gildas Lanilis

 

10 m  Integration Status  

Helen Chen

 

15 m  LFN Compliance and Verification Committee  

Chris Donley

 

10 m  Proposal for a TSC policy on Release Maintenance (Rescheduled from July 5)

Stephen Terrill

 

10 m  Proposal on a TSC policy on upgrade (Rescheduled from July 5)

Stephen Terrill   

 

10 M  LFN Marketing Structure & Resources  

Lisa Caywood

 

10 M  Develoiper On-boarding & Mentoring

Lisa Caywood    

 

5 M    Project Landing Page Proposal Approval (Rescheduled from July 19) 

Kenny Paul

 

10 M   JIRA workflow proposal update 

Randa Maher 

 

 

Thanks!

-kenny

 

 

From:  on behalf of Kenny Paul 

Date: Tuesday, July 17, 2018 at 5:02 PM
To: onap-tsc 
Subject: [onap-tsc] CALL FOR NOMINATIONS: ONAP TSC ELECTION

 
Nominations for seats on the ONAP TSC officially open @ 17:00 Pacific Time, 
Tuesday, July 17, 2018
If you are interested in running for a seat on the TSC, please read all of this 
information carefully
 
Who is eligible to Run:  Any Active Community Members as of 17:00 Pacific Time, 
Tuesday, July 17, 2018- There is NO limit to the number of candidates from any 
single company that can run for a seat.

4.1.1.1 TSC Membership Definitions  Active Community Member: 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

 

Self-Nomination Phase



Individuals interested in running for a TSC position MUST REPLY-ALL TO THIS 
ORIGINAL EMAIL with your intention to run before 17:00 Pacific time, July 31st.

NOTE: Replying to another candidate's self-nomination email announcing your own 
self-nomination is considered a blatant disregard for open source community 
norms. If you do that, you should probably re-assess both your qualifications 
and motivations for leading a collaborative community such as this.

Your self-nomination email must include a link to your stats in Bitergia 
(instructions on how to do this).   
It is strongly recommended that candidates also include a small head-shot, a 
short biography and statement of intent on why you would be a good person to 
hold a seat on the TSC. 



As a courtesy, it is also requested that you fill in the  2018 TSC Election 
Candidates wiki page with that same information. Filling out the wiki page is 
NOT in lieu of sending the email as required, but it will greatly help 
facilitate the process of the elections.

 

Special Provision for the original 9 ONAP Operators:  There are 9 seats 
reserved for the nine original ONAP Platinum Service Provider members. Each of 
these Operators is REQUIRED to have at least one person nominate themselves for 
their seat on the TSC. If and only if an Operator does not have any eligible 
Active Community Members at the time of nomination process, they may appoint a 
nominee to run in the election.  In such cases, the nominee must indicate that 
they are exercising a provisional nomination in their email. (Refer to 4.2.3.2 
TSC Member Candidates)

·

· The nomination phase begins 17:00 Pacific Time, Tuesday, July 17, 2018

· The nomination phase ends 17:00 Pacific Time, Tuesday, July 31, 2018

·

Election Phase

 

Who is eligible to Vote: Any Active Community Members as of 17:00 Pacific Time, 
Tuesday, July 17, 2018


A Condorcet election will be held using the CIVS voting system.  Active 
Community Members will receive an invitation to vote from CIVS.

· The election phase will begin with the distribution of the CIVS poll 
via email from the application

· The election phase will end two (2) weeks later in the same time zone 
the poll was initiated from

Election Results 

·
The election of TSC Members shall consist of a single stack ranked vote of all 
candidates 
Only the top ranked candidates from any single company will be

Re: [onap-tsc] CALL FOR NOMINATIONS: ONAP TSC ELECTION

[Lingli Deng]

Dear ONAP community, 



 


I would like to humbly self-nominate for a seat on the ONAP TSC.


 


For the last three years, I have been working extensitively in the open source 
communities related to SDN/NFV transformation representing China Mobile, from 
OPNFV, to OPEN-O and ONAP. 


For the last year, our team has been contributing to leading three usecases, 
managing two core projects, contributing to six other core projects, and 
hosting four community events in China. 


As the TSC Vice Chair, I have been working hard to maximizing the 
architecture39s modularity and maturity in providing both open source module 
code contribution as well as organizing PoCs with either opensource or 
commercial modules, to aligning ONAP design/run-time models and APIs with 
existing industry SDOs for the potential of wider adoption and smooth 
evolution. 


I would like to continue working for ONAP TSC, and help to improve the 
community diversity and futher improve architecture modularity, industry 
convergence, and quicker adoption. 


 


Please refer to below link for my Bitergia stats as an active community/code 
contributor:


https://onap.biterg.io/goto/dd56433f8c7f110c547a87337364ea97


 


Short Bio:


Lingli Deng is a Technical Manager at China Mobile Research Institute. She 
obtained her Doctor’s degree in Computer Application Technology from the 
Institute of Software, Chinese Academy of Sciences and joined China Mobile in 
2009. She was a core member of the Novonet project which drives SDN/NFV 
strategy for China Mobile, and has been working on evaluation and introduction 
of data plane acceleration technology, running the Novonet Testing Lab and 
planning the SDN/NFV trial network for the company. She is currently leading 
China Mobile ONAP R team and serving as the LFN TAC representative.


 


Thanks,


Lingli/邓灵莉中国移动通信研究院denglin...@chinamobile.com


 


 



From:  on behalf of Kenny Paul 
 Date: Wednesday, July 18, 2018 at 8:02 AM To: 
onap-tsc  Subject: [onap-tsc] CALL FOR NOMINATIONS: 
ONAP TSC ELECTION



 


Nominations for seats on the ONAP TSC officially open @ 17:00 Pacific Time, 
Tuesday, July 17, 2018If you are interested in running for a seat on the TSC, 
please read all of this information carefully 
Who is eligible to Run:  Any Active  Community Members as of 17:00 Pacific 
Time, Tuesday, July 17, 2018- There is NO limit to the number of candidates 
from  any single company that can run for a seat.


4.1.1.1  TSC Membership Definitions  Active  Community Member: 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


 


Self-Nomination Phase 


Individuals interested in running for a TSC position MUST  REPLY-ALL TO THIS 
ORIGINAL EMAIL with  your intention to run before 17:00 Pacific time, July 31st.


NOTE: Replying to another candidate39s self-nomination email announcing your 
own self-nomination is  considered a blatant disregard for open source 
community norms. If you do that, you  should probably re-assess both your 
qualifications and motivations for leading a collaborative community such as 
this.


Your self-nomination email must include a link to your stats in Bitergia 
(instructions  on how to do this).   It is strongly recommended that candidates 
also include a small head-shot, a short biography and statement of intent on 
why you would be a good person to hold a seat on the TSC. 


As a courtesy, it  is also requested that you fill in the  2018  TSC Election 
Candidates wiki  page with that same information. Filling out the wiki page is 
NOT in lieu of sending the email as required, but it will greatly  help 
facilitate the process of the elections.


 


Special Provision for the original 9 ONAP Operators:   There are 9 seats 
reserved for the nine original ONAP Platinum Service Provider members. Each of 
these Operators is REQUIRED to have at least one person nominate themselves for 
their seat on the TSC. If and only if an  Operator does not have any eligible 
Active Community Members at the time of nomination process, they may appoint a 
nominee to run in the election.  In such cases, the nominee must indicate that 
they are exercising a provisional nomination in their email.  (Refer to 4.2.3.2 
 TSC Member Candidates)


·


· The nomination phase begins 17:00 Pacific Time, Tuesday, July 17, 2018


· The nomination phase ends 17:00 Pacific Time, Tuesday, July 31, 2018


·


Election Phase


 


Who is eligible to Vote: Any  Active Community Members as of 17:00 Pacific 
Time, Tuesday, July 17, 2018


 A Condorcet election will be held using the CIVS  voting system.   Active 
Community Members will receive an invitation to vote from CIVS.


· The election phase will begin with the distribution of the CIVS poll 
via email from the application


· The election phase will end two (2

Re: [onap-tsc] CALL FOR NOMINATIONS: ONAP TSC ELECTION

[Xinhui Li]

Dear ONAP community,

I would like to humbly self-nominate for a seat on the ONAP TSC.

With more than 4 years’ experience with OpenStack open community and over 15 
months’ experience with ONAP, I have led the development efforts of ONAP in 
VMware. Along the past year, VMware continues to be one of the top ten 
contributing companies in ONAP. I have been a TSC member of ONAP since its 
inception. I had been the PTL for Multi VIM/Cloud (commits 80, Jira 64) and 
successfully delivered the releases of Amsterdam and Beijing with the global 
team. I would like to help technical focus of the TSC around cloud 
infrastructure, contribute to foster a diverse community and ensure ONAP 
maintains its leadership as a carrier-grade Telco orchestration platform.

Please refer to below link for my Bitergia stats as an active community/code 
contributor:
https://onap.biterg.io/goto/93c0e278eeab0737885259a0d582fdad

Short Bio:
Xinhui Li is Senior Architect of VMware NFV R and leads the team working on 
NFV product development and integration with open ecosystem. Besides NFV 
product development/integration, she serves as a core reviewer of OpenStack 
community since 2015. She is also contributing to ETSI MEC (Multi-access Edge 
Computing) as ISG member. She focuses on distributed system design and 
optimization with 14 global patents, 4 industry white papers, and 6 academy 
papers published in international journals/conferences of PIC top/target level. 
In the past three years, she has more than 18 tech submissions accepted by 
OpenStack Summit, OPNFV summit, ONS and Hadoop summit. She holds a M.S. in 
Computer Architecture from China Academy of Sciences.

Thanks,
Xinhui Li
Sr. Architect, VMware NFV Team

From:  on behalf of Kenny Paul 

Date: Wednesday, July 18, 2018 at 8:02 AM
To: onap-tsc 
Subject: [onap-tsc] CALL FOR NOMINATIONS: ONAP TSC ELECTION

Nominations for seats on the ONAP TSC officially open @ 17:00 Pacific Time, 
Tuesday, July 17, 2018
If you are interested in running for a seat on the TSC, please read all of this 
information carefully


Who is eligible to Run:  Any Active Community Members as of 17:00 Pacific Time, 
Tuesday, July 17, 2018- There is NO limit to the number of candidates from any 
single company that can run for a seat.

4.1.1.1 TSC Membership 
Definitions<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.onap.org%2Fdisplay%2FDW%2FONAP%2BTechnical%2BCommunity%2BDocument%23ONAPTechnicalCommunityDocument-4.1.1.1TSCMembershipDefinitions=02%7C01%7Clxinhui%40vmware.com%7C3648d23596ff49fd303c08d5ec41c901%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C636674689650061941=9G490%2BNdm7Ka4TGvETkAAuYqfm5fW%2FV%2Bder4p2RdQCk%3D=0>
  Active Community Member: 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



Self-Nomination Phase



Individuals interested in running for a TSC position MUST REPLY-ALL TO THIS 
ORIGINAL EMAIL with your intention to run before 17:00 Pacific time, July 31st.

NOTE: Replying to another candidate's self-nomination email announcing your own 
self-nomination is considered a blatant disregard for open source community 
norms. If you do that, you should probably re-assess both your qualifications 
and motivations for leading a collaborative community such as this.

Your self-nomination email must include a link to your stats in Bitergia 
(instructions on how to do 
this)<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.onap.org%2Fdisplay%2FDW%2FGetting%2BYour%2BStats%2BFrom%2BBitergia=02%7C01%7Clxinhui%40vmware.com%7C3648d23596ff49fd303c08d5ec41c901%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C636674689650071946=drf4ExUD3IlzSoiEreD2Zy2wmutZxWcLxNVOxYHn2ko%3D=0>.
It is strongly recommended that candidates also include a small head-shot, a 
short biography and statement of intent on why you would be a good person to 
hold a seat on the TSC.



As a courtesy, it is also requested that you fill in the  2018 TSC Election 
Candidates<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.onap.org%2Fdisplay%2FDW%2F2018%2BTSC%2BElection%2BCandidates=02%7C01%7Clxinhui%40vmware.com%7C3648d23596ff49fd303c08d5ec41c901%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C1%7C0%7C636674689650071946=CF9LuXrKsD8HbKFhjoafsHte4omznB9JCHyEzTi2lBo%3D=0>
 wiki page with that same information. Filling out the wiki page is NOT in lieu 
of sending the email as required, but it will greatly help facilitate the 
process of the elections.



Special Provision for the original 9 ONAP Operators:  There are 9 seats 
reserved for the nine original ONAP Platinum Service Provider members. Each of 
these Operators is REQUIRED to have at least one person nominate themselves for 
their seat on the TSC. If and only if an Operator does not have any eligible 
Active Community Members at the time of 

Re: [onap-tsc] CALL FOR NOMINATIONS: ONAP TSC ELECTION

[Murat Turpcu]

Dear ONAP community members,

I would like to nominate myself as a TSC member of the ONAP project, 
representing Turk Telekom (Platinum Service Provider Seat).
I have been representing Turk Telekom as a TSC member since February. I am 
responsible for increasing the awareness of ONAP within the Turk Telekom, 
determining the usacase scenarios, consolidating the requirements, defining the 
road-map and planning and implementing them.

ONAP is a big part of future plans in Turk Telekom. Analysis and integration 
preparations are being made to deploy and use ONAP in live systems. For this 
purpose our subsidiarys like NETSIA and ARGELA are actively contributing on 
code development of ONAP.

My ONAP stats : Provisional


I have been working for Telco business since 2007, and currently working for 
Turk Telekom as Senior Architect. The focus of my studies is the realization of 
IT and NW transformation that will meet the new generation business needs of 
Turkish telecom systems.

Best Regards,

From: ONAP-TSC@lists.onap.org  On Behalf Of Kenny Paul
Sent: 18 Temmuz 2018 Çarşamba 03:03
To: onap-tsc 
Subject: [onap-tsc] CALL FOR NOMINATIONS: ONAP TSC ELECTION

Nominations for seats on the ONAP TSC officially open @ 17:00 Pacific Time, 
Tuesday, July 17, 2018
If you are interested in running for a seat on the TSC, please read all of this 
information carefully


Who is eligible to Run:  Any Active Community Members as of 17:00 Pacific Time, 
Tuesday, July 17, 2018- There is NO limit to the number of candidates from any 
single company that can run for a seat.

4.1.1.1 TSC Membership 
Definitions<https://wiki.onap.org/display/DW/ONAP+Technical+Community+Document#ONAPTechnicalCommunityDocument-4.1.1.1TSCMembershipDefinitions>
  Active Community Member: 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



Self-Nomination Phase

Individuals interested in running for a TSC position MUST REPLY-ALL TO THIS 
ORIGINAL EMAIL with your intention to run before 17:00 Pacific time, July 31st.

NOTE: Replying to another candidate's self-nomination email announcing your own 
self-nomination is considered a blatant disregard for open source community 
norms. If you do that, you should probably re-assess both your qualifications 
and motivations for leading a collaborative community such as this.

Your self-nomination email must include a link to your stats in Bitergia 
(instructions on how to do 
this)<https://wiki.onap.org/display/DW/Getting+Your+Stats+From+Bitergia>.
It is strongly recommended that candidates also include a small head-shot, a 
short biography and statement of intent on why you would be a good person to 
hold a seat on the TSC.

As a courtesy, it is also requested that you fill in the  2018 TSC Election 
Candidates<https://wiki.onap.org/display/DW/2018+TSC+Election+Candidates> wiki 
page with that same information. Filling out the wiki page is NOT in lieu of 
sending the email as required, but it will greatly help facilitate the process 
of the elections.



Special Provision for the original 9 ONAP Operators:  There are 9 seats 
reserved for the nine original ONAP Platinum Service Provider members. Each of 
these Operators is REQUIRED to have at least one person nominate themselves for 
their seat on the TSC. If and only if an Operator does not have any eligible 
Active Community Members at the time of nomination process, they may appoint a 
nominee to run in the election.  In such cases, the nominee must indicate that 
they are exercising a provisional nomination in their email. (Refer to 4.2.3.2 
TSC Member 
Candidates<https://wiki.onap.org/display/DW/ONAP+Technical+Community+Document#ONAPTechnicalCommunityDocument-4.2.3.2TSCMemberCandidates>)
·
· The nomination phase begins 17:00 Pacific Time, Tuesday, July 17, 2018
· The nomination phase ends 17:00 Pacific Time, Tuesday, July 31, 2018
·

Election Phase



Who is eligible to Vote: Any Active Community Members as of 17:00 Pacific Time, 
Tuesday, July 17, 2018

A Condorcet election will be held using the CIVS voting 
system<https://wiki.onap.org/display/DW/Voting+Best+Practices>.  Active 
Community Members will receive an invitation to vote from CIVS.
· The election phase will begin with the distribution of the CIVS poll 
via email from the application
· The election phase will end two (2) weeks later in the same time zone 
the poll was initiated from

Election Results
·

  *   The election of TSC Members shall consist of a single stack ranked vote 
of all candidates
  *   Only the top ranked candidates from any single company will be elected; 
if the top 10 vote getters are all from the same company, only the person with 
the highest number of votes out of all 10 will be elected from that company.
  *   The top ranked candidate from 

Re: [onap-tsc] CALL FOR NOMINATIONS: ONAP TSC ELECTION

[Marc Fiedler]

Dear ONAP community,

since Deutsche Telekom has lately joined, we are happy to contribute to ONAP.

Therefore I would like to nominate myself as a TSC member of the ONAP project 
representing Deutsche Telekom AG  (Platinum Service Provider).

Within in the last 17 years in Deutsche Telekom I’ve helped to drive and manage 
different technology projects across real-time network service management, 
virtualization technologies, datacenter projects, operations processes and 
latest I am responsible to drive the ONAP evaluation and development inside of 
DT.

Deutsche Telekom want to actively get involved in different projects across the 
ONAP landscape, hot topics are DCAE, APP-C, OOM and more. Personally I want to 
support the ONAP community and the TSC to help making the next steps towards 
future releases, mature the “3SP” and last but not least drive ONAP as an 
enabler for 5G globally.


My ONAP stats: - (DT has only joined last month)



About myself:



I’m working as an Senior Architect at DT - Technology Innovation within the OSS 
Automation team and are responsible for ONAP Evaluation and Development.

Best regards,
Marc


Von: ONAP-TSC@lists.onap.org [mailto:ONAP-TSC@lists.onap.org] Im Auftrag von 
Kenny Paul
Gesendet: Mittwoch, 18. Juli 2018 02:03
An: onap-tsc 
Betreff: [onap-tsc] CALL FOR NOMINATIONS: ONAP TSC ELECTION

Nominations for seats on the ONAP TSC officially open @ 17:00 Pacific Time, 
Tuesday, July 17, 2018
If you are interested in running for a seat on the TSC, please read all of this 
information carefully


Who is eligible to Run:  Any Active Community Members as of 17:00 Pacific Time, 
Tuesday, July 17, 2018- There is NO limit to the number of candidates from any 
single company that can run for a seat.

4.1.1.1 TSC Membership 
Definitions<https://wiki.onap.org/display/DW/ONAP+Technical+Community+Document#ONAPTechnicalCommunityDocument-4.1.1.1TSCMembershipDefinitions>
  Active Community Member: 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



Self-Nomination Phase

Individuals interested in running for a TSC position MUST REPLY-ALL TO THIS 
ORIGINAL EMAIL with your intention to run before 17:00 Pacific time, July 31st.

NOTE: Replying to another candidate's self-nomination email announcing your own 
self-nomination is considered a blatant disregard for open source community 
norms. If you do that, you should probably re-assess both your qualifications 
and motivations for leading a collaborative community such as this.

Your self-nomination email must include a link to your stats in Bitergia 
(instructions on how to do 
this)<https://wiki.onap.org/display/DW/Getting+Your+Stats+From+Bitergia>.
It is strongly recommended that candidates also include a small head-shot, a 
short biography and statement of intent on why you would be a good person to 
hold a seat on the TSC.

As a courtesy, it is also requested that you fill in the  2018 TSC Election 
Candidates<https://wiki.onap.org/display/DW/2018+TSC+Election+Candidates> wiki 
page with that same information. Filling out the wiki page is NOT in lieu of 
sending the email as required, but it will greatly help facilitate the process 
of the elections.



Special Provision for the original 9 ONAP Operators:  There are 9 seats 
reserved for the nine original ONAP Platinum Service Provider members. Each of 
these Operators is REQUIRED to have at least one person nominate themselves for 
their seat on the TSC. If and only if an Operator does not have any eligible 
Active Community Members at the time of nomination process, they may appoint a 
nominee to run in the election.  In such cases, the nominee must indicate that 
they are exercising a provisional nomination in their email. (Refer to 4.2.3.2 
TSC Member 
Candidates<https://wiki.onap.org/display/DW/ONAP+Technical+Community+Document#ONAPTechnicalCommunityDocument-4.2.3.2TSCMemberCandidates>)
·
· The nomination phase begins 17:00 Pacific Time, Tuesday, July 17, 2018
· The nomination phase ends 17:00 Pacific Time, Tuesday, July 31, 2018
·

Election Phase



Who is eligible to Vote: Any Active Community Members as of 17:00 Pacific Time, 
Tuesday, July 17, 2018

A Condorcet election will be held using the CIVS voting 
system<https://wiki.onap.org/display/DW/Voting+Best+Practices>.  Active 
Community Members will receive an invitation to vote from CIVS.
· The election phase will begin with the distribution of the CIVS poll 
via email from the application
· The election phase will end two (2) weeks later in the same time zone 
the poll was initiated from

Election Results
·

  *   The election of TSC Members shall consist of a single stack ranked vote 
of all candidates
  *   Only the top ranked candidates from any single company will be elected; 
if the top 10 vote

Re: [onap-tsc] CALL FOR NOMINATIONS: ONAP TSC ELECTION

[Susana Sabater]

Dear all,
I would like to provisionally self-nominate for an operator seat on the  ONAP 
TSC.
As a senior manager in Vodafone Group R, I am in charge of network 
architectures and industry standards, with focus on latest generations of 
mobile networks, introducing automation and leveraging NFV, SDN and cloud 
concepts.
I have been part of the telco industry for more than 25 years, on software 
development, systems architecture, design and testing, strategy and industry 
engagement. I have been working in NFV/SDN environment for the last 7 years, 
being a major contributor towards standard NFV architectures and adoption of 
those by the newest generations of telco networks (e.g. 5G).
My main objective in ONAP is helping the industry to create bridges between 
standardization and open source as to complement and maximize the benefits that 
both approaches bring to network operators and vendors, considering the 
upcoming challenges of telco deployments.
Considering my experience in the industry and deep engagement in different 
areas, I am confident I can contribute to the success of ONAP as a platform 
serving the global community.

My Bitergia statistics are: 
https://onap.biterg.io/goto/c44f47edc2eda039aa533c0126a9803f

Cheers
/Susana

From: ONAP-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org> 
[mailto:ONAP-TSC@lists.onap.org] On Behalf Of Kenny Paul
Sent: Tuesday, July 17, 2018 5:03 PM
To: onap-tsc mailto:ONAP-TSC@lists.onap.org>>
Subject: [onap-tsc] CALL FOR NOMINATIONS: ONAP TSC ELECTION

Nominations for seats on the ONAP TSC officially open @ 17:00 Pacific Time, 
Tuesday, July 17, 2018
If you are interested in running for a seat on the TSC, please read all of this 
information carefully


Who is eligible to Run:  Any Active Community Members as of 17:00 Pacific Time, 
Tuesday, July 17, 2018- There is NO limit to the number of candidates from any 
single company that can run for a seat.

4.1.1.1 TSC Membership 
Definitions<https://wiki.onap.org/display/DW/ONAP+Technical+Community+Document#ONAPTechnicalCommunityDocument-4.1.1.1TSCMembershipDefinitions>
  Active Community Member: 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



Self-Nomination Phase

Individuals interested in running for a TSC position MUST REPLY-ALL TO THIS 
ORIGINAL EMAIL with your intention to run before 17:00 Pacific time, July 31st.

NOTE: Replying to another candidate's self-nomination email announcing your own 
self-nomination is considered a blatant disregard for open source community 
norms. If you do that, you should probably re-assess both your qualifications 
and motivations for leading a collaborative community such as this.

Your self-nomination email must include a link to your stats in Bitergia 
(instructions on how to do 
this)<https://wiki.onap.org/display/DW/Getting+Your+Stats+From+Bitergia>.
It is strongly recommended that candidates also include a small head-shot, a 
short biography and statement of intent on why you would be a good person to 
hold a seat on the TSC.

As a courtesy, it is also requested that you fill in the  2018 TSC Election 
Candidates<https://wiki.onap.org/display/DW/2018+TSC+Election+Candidates> wiki 
page with that same information. Filling out the wiki page is NOT in lieu of 
sending the email as required, but it will greatly help facilitate the process 
of the elections.



Special Provision for the original 9 ONAP Operators:  There are 9 seats 
reserved for the nine original ONAP Platinum Service Provider members. Each of 
these Operators is REQUIRED to have at least one person nominate themselves for 
their seat on the TSC. If and only if an Operator does not have any eligible 
Active Community Members at the time of nomination process, they may appoint a 
nominee to run in the election.  In such cases, the nominee must indicate that 
they are exercising a provisional nomination in their email. (Refer to 4.2.3.2 
TSC Member 
Candidates<https://wiki.onap.org/display/DW/ONAP+Technical+Community+Document#ONAPTechnicalCommunityDocument-4.2.3.2TSCMemberCandidates>)
·
· The nomination phase begins 17:00 Pacific Time, Tuesday, July 17, 2018
· The nomination phase ends 17:00 Pacific Time, Tuesday, July 31, 2018
·

Election Phase



Who is eligible to Vote: Any Active Community Members as of 17:00 Pacific Time, 
Tuesday, July 17, 2018

A Condorcet election will be held using the CIVS voting 
system<https://wiki.onap.org/display/DW/Voting+Best+Practices>.  Active 
Community Members will receive an invitation to vote from CIVS.
· The election phase will begin with the distribution of the CIVS poll 
via email from the application
· The election phase will end two (2) weeks later in the same time zone 
the poll was initiated from

Election Results
·

  *   The electio

Re: [onap-tsc] CALL FOR NOMINATIONS: ONAP TSC ELECTION

[Eric Debeau]

Dear ONAP community members,

I would like to nominate myself as a TSC member of the ONAP project 
representing Orange (seat as Platinum Service Provider).

I have been involved in SDN/NFV activities for 5 years, leading a team focusing 
in open source communities (ONAP, OPNFV, Acumos). I contributed in various ONAP 
projects (Documentation, Integration, ExternalAPI…) and sub-committees 
(architecture, use-case…) and I am the current Orange TSC member. I also 
promoted ONAP in various events (OSN Days, ONS Summit, SDN World Congress…).

ONAP is a key project for service providers and I will focus my energy to make 
ONAP a success. Acting as a TSC member, I would like to accelerate the ONAP 
deployment in production focusing on the key requirements and to bring more 
technical topics within the TSC.

My ONAP stats: https://onap.biterg.io/goto/6a4383ca05cf22196ac3c13df6382a86 ( 
https://onap.biterg.io/goto/6a4383ca05cf22196ac3c13df6382a86 )

My short bio:

Eric Debeau has a solid 20 years experience in the telecommunications area with 
a particular focus to adopt IT techniques in networks and OSS domains. Through 
his broad experience as network architect (SDH, VoIP, IMS), he is recognized as 
an Orange expert in future network domain. He is currently leading a team 
working on the core network evolution leveraging IT techniques mainly covering 
NFV and network data analytics. His team is very open-source focused with 
strong involvement in OPNFV and now in ONAP. Eric Debeau is very involved in 
various open-source communities (ONAP TSC member) and he is responsible to 
coordinate the Orange contributions to ONAP project. He contributed in various 
open-source community summits, published various technical papers and holds 
several patents.

My head-shot:

Best Regards

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

View/Reply Online (#3529): https://lists.onap.org/g/ONAP-TSC/message/3529
Mute This Topic: https://lists.onap.org/mt/23599386/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] CALL FOR NOMINATIONS: ONAP TSC ELECTION

[Srini]

Hi,

I would like to self-nominate for a seat on the  ONAP TSC.

I have been working on ONAP and related areas since September,2017 when I 
started my current role as ONAP chief architect in Intel.  I have been 
technically/strategically leading group of ONAP engineers within Intel to 
contribute to ONAP releases. Some of my contributions include architecture of

-Policy based HPA feature in OOF, Multi-Cloud & A

-Secret Management Service to secure the ONAP secrets such as passwords

-CA Private key security using PKCS11 with Hardware root of trust.

-Distributed KV Store for configuration.

-Kubernetes plugin to do LCM of containerized VNFs and orchestrate both 
VMs & containers.

-ISTIO based Service mesh technology for ONAP.

-Many edge automation activities : ONAP offload to regional 
controllers,  Secure connectivity via IPSEC between ONAP and Edge locations and 
Aggregation of node statistics to site granularity.

I have led many big technical projects in my career and had been working in 
NFV/SDN world for last 6 years. ONAP success is my major goal of my current 
role. With my experience in open source, networking , security, edge, micro 
services and service mesh technologies, I am confident that I will 
contribute/collaborate technically/strategically with rest of the community and 
be a constructive technical contributor/architect to the ONAP project.

Short Bio:
Srini Addepalli has over 22+ years of experience in networking and security. He 
has been in Intel for last 3 years working as Sr. Principal Engineer & Senior 
Architect.  In his current role, he technically leads the software engineering 
& architecture activities related to network orchestration and 
network/infrastructure security with specific focus on  ONAP, edge and 
Kubernetes.Previously he worked in many roles including CTO of a network 
security software company Intoto Inc (acquired by Freescale), Fellow & Chief 
architect at Freescale leading advanced technology group. In his previous jobs, 
he was instrumental in strategy & creation of UTM solutions, autonomous 
acceleration of L3, L4, IPsec, Openflow, & Cloud RAN functions, network 
security/packet-processing software solutions and infrastructure security 
solutions.

My Bitergia statistics are: 
https://onap.biterg.io/goto/89070a01240d07735ab8d8292a5ff29d

Thanks
Srini
(Srinivasa Addepalli)


From: ONAP-TSC@lists.onap.org [mailto:ONAP-TSC@lists.onap.org] On Behalf Of 
Kenny Paul
Sent: Tuesday, July 17, 2018 5:03 PM
To: onap-tsc 
Subject: [onap-tsc] CALL FOR NOMINATIONS: ONAP TSC ELECTION

Nominations for seats on the ONAP TSC officially open @ 17:00 Pacific Time, 
Tuesday, July 17, 2018
If you are interested in running for a seat on the TSC, please read all of this 
information carefully


Who is eligible to Run:  Any Active Community Members as of 17:00 Pacific Time, 
Tuesday, July 17, 2018- There is NO limit to the number of candidates from any 
single company that can run for a seat.

4.1.1.1 TSC Membership 
Definitions<https://wiki.onap.org/display/DW/ONAP+Technical+Community+Document#ONAPTechnicalCommunityDocument-4.1.1.1TSCMembershipDefinitions>
  Active Community Member: 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



Self-Nomination Phase

Individuals interested in running for a TSC position MUST REPLY-ALL TO THIS 
ORIGINAL EMAIL with your intention to run before 17:00 Pacific time, July 31st.

NOTE: Replying to another candidate's self-nomination email announcing your own 
self-nomination is considered a blatant disregard for open source community 
norms. If you do that, you should probably re-assess both your qualifications 
and motivations for leading a collaborative community such as this.

Your self-nomination email must include a link to your stats in Bitergia 
(instructions on how to do 
this)<https://wiki.onap.org/display/DW/Getting+Your+Stats+From+Bitergia>.
It is strongly recommended that candidates also include a small head-shot, a 
short biography and statement of intent on why you would be a good person to 
hold a seat on the TSC.

As a courtesy, it is also requested that you fill in the  2018 TSC Election 
Candidates<https://wiki.onap.org/display/DW/2018+TSC+Election+Candidates> wiki 
page with that same information. Filling out the wiki page is NOT in lieu of 
sending the email as required, but it will greatly help facilitate the process 
of the elections.



Special Provision for the original 9 ONAP Operators:  There are 9 seats 
reserved for the nine original ONAP Platinum Service Provider members. Each of 
these Operators is REQUIRED to have at least one person nominate themselves for 
their seat on the TSC. If and only if an Operator does not have any eligible 
Active Community Membe

Re: [onap-tsc] CALL FOR NOMINATIONS: ONAP TSC ELECTION

[Frank Brockners via Lists.Onap.Org]

Dear ONAP community,

I would like to nominate myself as a TSC member of the ONAP project.

As a Distinguished Engineer in Cisco’s Chief Technology and Architecture 
Office, I’m driving software and architecture development for software defined 
devices – with a strong focus on open source. I’ve worked with several projects 
that reside under the roof of Linux Foundation networking, including ONAP (TSC 
member since Sep/2017), OPNFV (TSC member since its inception, Sept/2014), 
OpenDaylight, FD.io, and PNDA. I’m also very active in the IETF – integrating 
standards development and open source code development as part of the in-situ 
OAM effort. One of my focus areas in open source has been to integrate code and 
communities, e.g. OPNFV FastDataStacks which integrates OpenStack, OpenDaylight 
and FD.io, or more recently PNDA with ONAP DCAE, as well as the 
Lab-as-a-Service initiative that is to give developers much required lab 
resources for all of the LFN projects.
Moving forward, I want to help accelerate ONAP’s move to a meritocratic 
community and build additional bridges and stronger ties to other projects – 
within and outside the LFN.
I hold a diploma degree in Electrical Engineering (Aachen University) and a 
PhD/Dr degree in Information Science (University of Cologne).

My Bitergia stats: https://onap.biterg.io/goto/68aec4d8375401b4e5b65b5dc832164f

[cid:image003.jpg@01D42411.0FF7D090]

Regards, Frank


From: ONAP-TSC@lists.onap.org  On Behalf Of Kenny Paul
Sent: Mittwoch, 18. Juli 2018 02:03
To: onap-tsc 
Subject: [onap-tsc] CALL FOR NOMINATIONS: ONAP TSC ELECTION

Nominations for seats on the ONAP TSC officially open @ 17:00 Pacific Time, 
Tuesday, July 17, 2018
If you are interested in running for a seat on the TSC, please read all of this 
information carefully


Who is eligible to Run:  Any Active Community Members as of 17:00 Pacific Time, 
Tuesday, July 17, 2018- There is NO limit to the number of candidates from any 
single company that can run for a seat.

4.1.1.1 TSC Membership 
Definitions<https://wiki.onap.org/display/DW/ONAP+Technical+Community+Document#ONAPTechnicalCommunityDocument-4.1.1.1TSCMembershipDefinitions>
  Active Community Member: 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



Self-Nomination Phase

Individuals interested in running for a TSC position MUST REPLY-ALL TO THIS 
ORIGINAL EMAIL with your intention to run before 17:00 Pacific time, July 31st.

NOTE: Replying to another candidate's self-nomination email announcing your own 
self-nomination is considered a blatant disregard for open source community 
norms. If you do that, you should probably re-assess both your qualifications 
and motivations for leading a collaborative community such as this.

Your self-nomination email must include a link to your stats in Bitergia 
(instructions on how to do 
this)<https://wiki.onap.org/display/DW/Getting+Your+Stats+From+Bitergia>.
It is strongly recommended that candidates also include a small head-shot, a 
short biography and statement of intent on why you would be a good person to 
hold a seat on the TSC.

As a courtesy, it is also requested that you fill in the  2018 TSC Election 
Candidates<https://wiki.onap.org/display/DW/2018+TSC+Election+Candidates> wiki 
page with that same information. Filling out the wiki page is NOT in lieu of 
sending the email as required, but it will greatly help facilitate the process 
of the elections.



Special Provision for the original 9 ONAP Operators:  There are 9 seats 
reserved for the nine original ONAP Platinum Service Provider members. Each of 
these Operators is REQUIRED to have at least one person nominate themselves for 
their seat on the TSC. If and only if an Operator does not have any eligible 
Active Community Members at the time of nomination process, they may appoint a 
nominee to run in the election.  In such cases, the nominee must indicate that 
they are exercising a provisional nomination in their email. (Refer to 4.2.3.2 
TSC Member 
Candidates<https://wiki.onap.org/display/DW/ONAP+Technical+Community+Document#ONAPTechnicalCommunityDocument-4.2.3.2TSCMemberCandidates>)
·
·   The nomination phase begins 17:00 Pacific Time, Tuesday, July 17, 2018
·   The nomination phase ends 17:00 Pacific Time, Tuesday, July 31, 2018
·

Election Phase



Who is eligible to Vote: Any Active Community Members as of 17:00 Pacific Time, 
Tuesday, July 17, 2018

A Condorcet election will be held using the CIVS voting 
system<https://wiki.onap.org/display/DW/Voting+Best+Practices>.  Active 
Community Members will receive an invitation to vote from CIVS.
·   The election phase will begin with the distribution of the CIVS poll 
via email from the application
·   The election phase will end two (2) weeks later in the same time zone 
the pol

Re: [onap-tsc] CALL FOR NOMINATIONS: ONAP TSC ELECTION

[Christopher Donley]

Dear TSC,

I would like to self-nominate for a seat on the TSC.  Over the past year, I 
have made 166 commits, created 79 wiki pages, and created 262 Jira tickets: 
https://onap.biterg.io/goto/e5ac923846d3f306d72a7ae70429a3bb

In ONAP, I have been active chairing the Architecture Subcommittee and leading 
the VNFSDK project.  I also chair the LFN Compliance & Verification Committee, 
and previously chaired the OPEN-O TSC.  I have also worked on network standards 
and specifications since 2006, including through IETF, MEF, ETSI, and 
CableLabs.  Having participated in ONAP (and similar communities) through 
multiple roles, I bring knowledge and experience to help the TSC deliver our 
releases on time by focusing on building our community and supporting our 
developers through improvements to our tools and development processes.

I hold an MBA in Technology Management from the University of Colorado and a BA 
in Engineering from Dartmouth.

Chris

[X]

From: mailto:ONAP-TSC@lists.onap.org>> on behalf of 
Kenny Paul mailto:kp...@linuxfoundation.org>>
Date: Tuesday, July 17, 2018 at 5:02 PM
To: onap-tsc mailto:ONAP-TSC@lists.onap.org>>
Subject: [onap-tsc] CALL FOR NOMINATIONS: ONAP TSC ELECTION

Nominations for seats on the ONAP TSC officially open @ 17:00 Pacific Time, 
Tuesday, July 17, 2018
If you are interested in running for a seat on the TSC, please read all of this 
information carefully


Who is eligible to Run:  Any Active Community Members as of 17:00 Pacific Time, 
Tuesday, July 17, 2018- There is NO limit to the number of candidates from any 
single company that can run for a seat.

4.1.1.1 TSC Membership 
Definitions<https://wiki.onap.org/display/DW/ONAP+Technical+Community+Document#ONAPTechnicalCommunityDocument-4.1.1.1TSCMembershipDefinitions>
  Active Community Member: 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



Self-Nomination Phase


Individuals interested in running for a TSC position MUST REPLY-ALL TO THIS 
ORIGINAL EMAIL with your intention to run before 17:00 Pacific time, July 31st.

NOTE: Replying to another candidate's self-nomination email announcing your own 
self-nomination is considered a blatant disregard for open source community 
norms. If you do that, you should probably re-assess both your qualifications 
and motivations for leading a collaborative community such as this.

Your self-nomination email must include a link to your stats in Bitergia 
(instructions on how to do 
this)<https://wiki.onap.org/display/DW/Getting+Your+Stats+From+Bitergia>.
It is strongly recommended that candidates also include a small head-shot, a 
short biography and statement of intent on why you would be a good person to 
hold a seat on the TSC.


As a courtesy, it is also requested that you fill in the  2018 TSC Election 
Candidates<https://wiki.onap.org/display/DW/2018+TSC+Election+Candidates> wiki 
pagewith that same information. Filling out the wiki page is NOT in lieu of 
sending the email as required, but it will greatly help facilitate the process 
of the elections.



Special Provision for the original 9 ONAP Operators:  There are 9 seats 
reserved for the nine original ONAP Platinum Service Provider members. Each of 
these Operators is REQUIRED to have at least one person nominate themselves for 
their seat on the TSC. If and only if an Operator does not have any eligible 
Active Community Members at the time of nomination process, they may appoint a 
nominee to run in the election.  In such cases, the nominee must indicate that 
they are exercising a provisional nomination in their email. (Refer to 4.2.3.2 
TSC Member 
Candidates<https://wiki.onap.org/display/DW/ONAP+Technical+Community+Document#ONAPTechnicalCommunityDocument-4.2.3.2TSCMemberCandidates>)
·
· The nomination phase begins 17:00 Pacific Time, Tuesday, July 17, 2018
· The nomination phase ends 17:00 Pacific Time, Tuesday, July 31, 2018
·

Election Phase



Who is eligible to Vote: Any Active Community Members as of 17:00 Pacific Time, 
Tuesday, July 17, 2018

A Condorcet election will be held using the CIVS voting 
system<https://wiki.onap.org/display/DW/Voting+Best+Practices>.  Active 
Community Members will receive an invitation to vote from CIVS.
· The election phase will begin with the distribution of the CIVS poll 
via email from the application
· The election phase will end two (2) weeks later in the same time zone 
the poll was initiated from

Election Results
·

  *   The election of TSC Members shall consist of a single stack ranked vote 
of all candidates
  *   Only the top ranked candidates from any single company will be elected; 
if the top 10 vote getters are all from the same company, only the person with 
the highest number of votes out of all 10 will be elected fr

Re: [onap-tsc] CALL FOR NOMINATIONS: ONAP TSC ELECTION

[Alla Goldner]

Dear ONAP community,

I would like to nominate myself as a TSC member of the ONAP project.
I lead ONAP activities and internal decision-making at Amdocs. My 
responsibilities include defining and implementing Amdocs’ ONAP strategy, 
working directly with ONAP members from Service Providers, vendors and 
partners, and managing Amdocs’ internal ONAP TSC. My current focus is NFV and 
SDN network evolution, and in particular, the standardization and open-source 
domains. With over 20 years of experience in developing technology strategy and 
system architecture at global companies including Alcatel, Motorola, and Intel, 
I also have extensive experience in leading standardization efforts in 3GPP, 
IETF, ETSI NFV, BBF and have multiple patents in the communication and 
networking areas.
I hold an MSc in Technology Management from NYU and a BSc in Mathematics and 
Computer Science from Tel Aviv University.
I have been a TSC member of ONAP since its inception and have been the chair of 
ONAP’s Usecase subcommittee. I have also served as a member of Program 
Committees for several ONAP Developer Forums and as a moderator for Usecase 
subcommittee mailing list. ONAP success is my major goal and I hope to continue 
serve as a TSC member in order to shape ONAP future development and deployment 
by multiple Service Providers.

My Bitergia statistics are: 
https://onap.biterg.io/goto/147ec9d45746014b7dbda899cad4928d



Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image002.png@01D42062.D1E77DC0]

From: mailto:ONAP-TSC@lists.onap.org>> on behalf of 
Kenny Paul mailto:kp...@linuxfoundation.org>>
Date: Tuesday, July 17, 2018 at 8:02 PM
To: onap-tsc mailto:ONAP-TSC@lists.onap.org>>
Subject: [onap-tsc] CALL FOR NOMINATIONS: ONAP TSC ELECTION

Nominations for seats on the ONAP TSC officially open @ 17:00 Pacific Time, 
Tuesday, July 17, 2018
If you are interested in running for a seat on the TSC, please read all of this 
information carefully


Who is eligible to Run:  Any Active Community Members as of 17:00 Pacific Time, 
Tuesday, July 17, 2018- There is NO limit to the number of candidates from any 
single company that can run for a seat.

4.1.1.1 TSC Membership 
Definitions<https://wiki.onap.org/display/DW/ONAP+Technical+Community+Document#ONAPTechnicalCommunityDocument-4.1.1.1TSCMembershipDefinitions>
  Active Community Member: 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



Self-Nomination Phase


Individuals interested in running for a TSC position MUST REPLY-ALL TO THIS 
ORIGINAL EMAIL with your intention to run before 17:00 Pacific time, July 31st.

NOTE: Replying to another candidate's self-nomination email announcing your own 
self-nomination is considered a blatant disregard for open source community 
norms. If you do that, you should probably re-assess both your qualifications 
and motivations for leading a collaborative community such as this.

Your self-nomination email must include a link to your stats in Bitergia 
(instructions on how to do 
this)<https://wiki.onap.org/display/DW/Getting+Your+Stats+From+Bitergia>.
It is strongly recommended that candidates also include a small head-shot, a 
short biography and statement of intent on why you would be a good person to 
hold a seat on the TSC.


As a courtesy, it is also requested that you fill in the  2018 TSC Election 
Candidates<https://wiki.onap.org/display/DW/2018+TSC+Election+Candidates> wiki 
page with that same information. Filling out the wiki page is NOT in lieu of 
sending the email as required, but it will greatly help facilitate the process 
of the elections.



Special Provision for the original 9 ONAP Operators:  There are 9 seats 
reserved for the nine original ONAP Platinum Service Provider members. Each of 
these Operators is REQUIRED to have at least one person nominate themselves for 
their seat on the TSC. If and only if an Operator does not have any eligible 
Active Community Members at the time of nomination process, they may appoint a 
nominee to run in the election.  In such cases, the nominee must indicate that 
they are exercising a provisional nomination in their email. (Refer to 4.2.3.2 
TSC Member 
Candidates<https://wiki.onap.org/display/DW/ONAP+Technical+Community+Document#ONAPTechnicalCommunityDocument-4.2.3.2TSCMemberCandidates>)
·
· The nomination phase begins 17:00 Pacific Time, Tuesday, July 17, 2018
· The nomination phase ends 17:00 Pacific Time, Tuesday, July 31, 2018
·

Election Phase



Who is eligible to Vote: Any Active Community Members as of 17:00 Pacific Time, 
Tuesday, July 17, 2018

A Condorcet election will be held using the CIVS voting 
system<https://wiki.onap.org/display/DW/Voting+Best+Practices>.  Active 
Community Members will receive an invitation

Re: [onap-tsc] CALL FOR NOMINATIONS: ONAP TSC ELECTION

[David Sauvageau]

Dear ONAP community,

I would like to nominate myself as a TSC member of the ONAP project [ONAP 
Platinum Service Provider seat]

With more than 14 year experience in Telecom industry in software design & 
development and 18 months experience with ONAP, I have led the software 
delivery and operations of ONAP in a production environment in Bell Canada, I 
have been a TSC member of ONAP since its inception and have been the PTL for 
OOM. As a TSC member, I want to help driving the adoption ONAP in production 
environments by making it more open, community-driven, agile, aligned to 
operator’s needs, and I’d like to help bringing a more technical focus as part 
of the TSC.

My Bitergia stats: https://onap.biterg.io/goto/ac8303d60f1955ce3c6c845bd2e0d107
[cid:image001.jpg@01D41F4E.512A64F0]
Thanks.

From:  on behalf of Kenny Paul 

Date: Tuesday, July 17, 2018 at 8:02 PM
To: onap-tsc 
Subject: [onap-tsc] CALL FOR NOMINATIONS: ONAP TSC ELECTION

Nominations for seats on the ONAP TSC officially open @ 17:00 Pacific Time, 
Tuesday, July 17, 2018
If you are interested in running for a seat on the TSC, please read all of this 
information carefully


Who is eligible to Run:  Any Active Community Members as of 17:00 Pacific Time, 
Tuesday, July 17, 2018- There is NO limit to the number of candidates from any 
single company that can run for a seat.

4.1.1.1 TSC Membership 
Definitions<https://wiki.onap.org/display/DW/ONAP+Technical+Community+Document#ONAPTechnicalCommunityDocument-4.1.1.1TSCMembershipDefinitions>
  Active Community Member: 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



Self-Nomination Phase



Individuals interested in running for a TSC position MUST REPLY-ALL TO THIS 
ORIGINAL EMAIL with your intention to run before 17:00 Pacific time, July 31st.

NOTE: Replying to another candidate's self-nomination email announcing your own 
self-nomination is considered a blatant disregard for open source community 
norms. If you do that, you should probably re-assess both your qualifications 
and motivations for leading a collaborative community such as this.

Your self-nomination email must include a link to your stats in Bitergia 
(instructions on how to do 
this)<https://wiki.onap.org/display/DW/Getting+Your+Stats+From+Bitergia>.
It is strongly recommended that candidates also include a small head-shot, a 
short biography and statement of intent on why you would be a good person to 
hold a seat on the TSC.



As a courtesy, it is also requested that you fill in the  2018 TSC Election 
Candidates<https://wiki.onap.org/display/DW/2018+TSC+Election+Candidates> wiki 
page with that same information. Filling out the wiki page is NOT in lieu of 
sending the email as required, but it will greatly help facilitate the process 
of the elections.



Special Provision for the original 9 ONAP Operators:  There are 9 seats 
reserved for the nine original ONAP Platinum Service Provider members. Each of 
these Operators is REQUIRED to have at least one person nominate themselves for 
their seat on the TSC. If and only if an Operator does not have any eligible 
Active Community Members at the time of nomination process, they may appoint a 
nominee to run in the election.  In such cases, the nominee must indicate that 
they are exercising a provisional nomination in their email. (Refer to 4.2.3.2 
TSC Member 
Candidates<https://wiki.onap.org/display/DW/ONAP+Technical+Community+Document#ONAPTechnicalCommunityDocument-4.2.3.2TSCMemberCandidates>)
·
· The nomination phase begins 17:00 Pacific Time, Tuesday, July 17, 2018
· The nomination phase ends 17:00 Pacific Time, Tuesday, July 31, 2018
·

Election Phase



Who is eligible to Vote: Any Active Community Members as of 17:00 Pacific Time, 
Tuesday, July 17, 2018

A Condorcet election will be held using the CIVS voting 
system<https://wiki.onap.org/display/DW/Voting+Best+Practices>.  Active 
Community Members will receive an invitation to vote from CIVS.
· The election phase will begin with the distribution of the CIVS poll 
via email from the application
· The election phase will end two (2) weeks later in the same time zone 
the poll was initiated from

Election Results
·

  *   The election of TSC Members shall consist of a single stack ranked vote 
of all candidates
  *   Only the top ranked candidates from any single company will be elected; 
if the top 10 vote getters are all from the same company, only the person with 
the highest number of votes out of all 10 will be elected from that company.
  *   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 sel

[onap-tsc] CALL FOR NOMINATIONS: ONAP TSC ELECTION

[Kenny Paul]

Nominations for seats on the ONAP TSC officially open @ 17:00 Pacific Time, 
Tuesday, July 17, 2018
If you are interested in running for a seat on the TSC, please read all of this 
information carefully
 
Who is eligible to Run:  Any Active Community Members as of 17:00 Pacific Time, 
Tuesday, July 17, 2018- There is NO limit to the number of candidates from any 
single company that can run for a seat.

4.1.1.1 TSC Membership Definitions  Active Community Member: 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

 

Self-Nomination Phase


Individuals interested in running for a TSC position MUST REPLY-ALL TO THIS 
ORIGINAL EMAIL with your intention to run before 17:00 Pacific time, July 31st.

NOTE: Replying to another candidate's self-nomination email announcing your own 
self-nomination is considered a blatant disregard for open source community 
norms. If you do that, you should probably re-assess both your qualifications 
and motivations for leading a collaborative community such as this.

Your self-nomination email must include a link to your stats in Bitergia 
(instructions on how to do this).   
It is strongly recommended that candidates also include a small head-shot, a 
short biography and statement of intent on why you would be a good person to 
hold a seat on the TSC. 


As a courtesy, it is also requested that you fill in the  2018 TSC Election 
Candidates wiki page with that same information. Filling out the wiki page is 
NOT in lieu of sending the email as required, but it will greatly help 
facilitate the process of the elections.

 

Special Provision for the original 9 ONAP Operators:  There are 9 seats 
reserved for the nine original ONAP Platinum Service Provider members. Each of 
these Operators is REQUIRED to have at least one person nominate themselves for 
their seat on the TSC. If and only if an Operator does not have any eligible 
Active Community Members at the time of nomination process, they may appoint a 
nominee to run in the election.  In such cases, the nominee must indicate that 
they are exercising a provisional nomination in their email. (Refer to 4.2.3.2 
TSC Member Candidates)

·

· The nomination phase begins 17:00 Pacific Time, Tuesday, July 17, 2018

· The nomination phase ends 17:00 Pacific Time, Tuesday, July 31, 2018

·

Election Phase

 

Who is eligible to Vote: Any Active Community Members as of 17:00 Pacific Time, 
Tuesday, July 17, 2018


A Condorcet election will be held using the CIVS voting system.  Active 
Community Members will receive an invitation to vote from CIVS.

· The election phase will begin with the distribution of the CIVS poll 
via email from the application

· The election phase will end two (2) weeks later in the same time zone 
the poll was initiated from

Election Results 

·
The election of TSC Members shall consist of a single stack ranked vote of all 
candidates 
Only the top ranked candidates from any single company will be elected; if the 
top 10 vote getters are all from the same company, only the person with the 
highest number of votes out of all 10 will be elected from that company.
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.
The LF will update the Voting Results History page with their name, date, and 
link to the publicly viewable CIVS results and send an email to the 
distribution list and to onap-tsc
 

 

 

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 (#3391): https://lists.onap.org/g/ONAP-TSC/message/3391
Mute This Topic: https://lists.onap.org/mt/23599386/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-