ONAP Community,

I would like to humbly self-nominate for the ONAP TSC election.  I have served on the ONAP TSC since the founding of the community.  I contributed to the original architectural principles and have led coordination of the S3P/Platform Maturity Requirements for the past few releases.  I am also the acting chair for Linux Foundation Networking’s Technical Advisory Council and represent the TAC on the LFN Governing Board and Strategic Planning Council. I lead IBM’s open source networking efforts and thus support IBM’s consistent ONAP contributions.  I have also represented the community, previously presenting at industry conferences (KubeCon, SDN/NFV World Congress, and ONS) on ONAP and related topics.  

I would enjoy the opportunity to continue working in the ONAP community as a TSC representative.  If re-elected, I would focus on refining the platform maturity requirements to ensure they are achievable while meeting the needs of operators’ production deployments. I would also promote the themes of simplicity & modularity in ONAP, which may require a tighter focus on core functionality.  Finally, I would continue to encourage the community to leverage existing cloud-based technologies and platforms, allowing the ONAP community to focus on their specialty areas of networking and automation.

I am a Distinguished Engineer at IBM and have worked in the telecommunications industry for 19 years, including the past 6 years focused on SDN/NFV. My technology focus areas are cloud, edge, and responsible use of software.

Thank you for your consideration.
 
Bitergia stats:
 

Regards,
Jason Hunt
Distinguished Engineer, IBM

Phone: +1-314-749-7422
Email: [email protected]
Twitter: @DJHunt
 
 
----- Original message -----
From: "Jim Baker" <[email protected]>
Sent by: [email protected]
To: onap-tsc <[email protected]>, [email protected]
Cc: Arpit Joshipura <[email protected]>, Heather Kirksey <[email protected]>
Subject: [EXTERNAL] [onap-tsc] 2019 ONAP TSC Elections - Call for nominations
Date: Mon, Oct 21, 2019 11:15 AM
 

Dear ONAP Community,

 

Nominations for seats on the ONAP TSC officially open @ 9:00 Pacific Time, Monday, October 21, 2019

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 20:00 Pacific Time, Sunday, Oct 20, 2019

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.

#1 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, Nov 1st.

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  2019 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 9:00 Pacific Time, Monday, Oct 21, 2019

·         The nomination phase ends 17:00 Pacific Time, Friday, Nov 1, 2019    

#2 Election Phase

Who is eligible to Vote: Any Active Community Members as of 20:00 Pacific Time, Sunday, Oct 20, 2019


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
 
--
Jim Baker
Linux Foundation Networking - Technical Program Manager
mobile: +1 970 227 6007
 

_._,_._,_

Links:

You receive all messages sent to this group.

View/Reply Online (#5550) | Reply To Group | Reply To Sender | Mute This Topic | New Topic

Your Subscription | Contact Group Owner | Unsubscribe [[email protected]]

_._,_._,_

Reply via email to