Release Manager Election (2017)

Owned by Phil Robb
Last updated: Jun 01, 2017 by Gildas Lanilis GmailVersion comment
5 min read

What

To aid the ONAP project through the release process, The TSC will elect a Release Manager to facilitate, monitor and report on all aspects of project development, cross project coordination, and the timely creation of release artifacts according to the ONAP Release-1 plan and schedule.

Job Description

The Open Network Automation Platform (ONAP) Project is looking for a Release Manager to guide the regular, timely release of the collection of projects that comprise our platform.  Bring your skills and passion for release planning, cross project coordination, automation, and release delivery to the exciting world of Network Automation.

The Release Manager will take the release plan defined and approved by the ONAP Technical Steering Committee and guide the ONAP development community through the process and procedures needed to coordinate timely and regular software releases, follow-on stable releases, and manage any ad-hoc releases as required.

Primary Responsibilities
- Work with the ONAP TSC and Project PTLs to create and evolve the ONAP release process.
- Develop document, and maintain release automation tools and tracking artifacts as needed
- Coordinate the cross project release cycle, including intermediate milestones and release candidates, final releases, stable and security updates.

- Communicate with Project Technical Leaders, Technical Steering Committee and community at large regarding the status of the release.

- Help identify release-blocking issues to keep release process on schedule
- Deliver timely release artifacts (executable(s), documentation, testing output, etc.)

Qualifications
- Bachelor’s degree in Computer Science related field or equivalent work experience
- 2-5 years of release and/or project management experience
- Excellent communication skills (proficiency in both English and Mandarin a plus)
- Strong understanding of git, gerrit, jenkins, maven and other relevant CI/CD tooling.

- Experience with open source release management a plus

Who

This position may be held by anyone in the ONAP community  Only the TSC votes on the candidates.

How

The election process occurs in two phases; the Nomination phase, and the Election phase.

Nominations open May 31st, 2017.
Nominations close June 7th at 9:00pm Pacific Time
Voting begins June 8th, 2017
Voting Ends June 15th, 2017 at 9:00pm Pacific Time

Nomination Phase

An email is sent from the Election Coordinator (Phil Robb) to the TSC  and discuss distribution lists for ONAP and the subject line is tagged with the keywords [ONAP RELEASE MANAGER ELECTION].
Any member of the ONAP community may nominate themselves to stand for election. Note that no one can nominate another person to run for election.
To submit a nomination, the community member must reply-all to the original nomination email stating their interest to stand for the election.
All nominees are invited to provide their Picture, Biography, and Statement of Intent for the election wiki page so that members of the TSC, and the community, can learn more about the candidate and their intentions for the role of Release Manager. The nominee ordering on the election wiki page will be in ascending alphabetical order by last name.

The length of the Nomination phase is at least 5 business days. This clock starts when the email described above is sent.

Election Phase

Immediately upon the close of the Nomination Phase, an email will be sent from the Election Coordinator (Phil Robb) via the Condorcet Internet Voting Service (CIVS) to each TSC member. This email will have the subject line: “Poll: ONAP RELEASE MANAGER ELECTION”. This email acts as an invitation by the CIVS for each TCS Member to vote. This voting invitation is only sent to the TSC Members. The TSC mailing list is not cc-ed on this email as per the CIVS process. Included in this election invitation will be a pointer to the Election wiki page which contains the names, pictures, biographies, and statements-of-intent for each of the candidates. The email also has instructions and a private URL where each TSC Member is sent to vote.
At the CIVS-provided voting URL, each voter will rank the candidates, where a smaller-numbered rank means that the voter prefers that choice more. Once the ranking is complete, the voter will press the “Submit ranking” button to complete the voting process.
The Election Phase will remain open for at least 5 business days from the time the invitation-to-vote email is sent by the CIVS.
Once the Election Phase has completed, the results of the election, including the votes cast by all participating TSC members, will be made available to the TSC mailing list.

Information on the Candidates

Each Candidate, please provide the following:

  • Name

  • Photo

  • Biography

  • Statement of Intent in being a TSC Vice Chairperson

The Candidates (In ascending alphabetical order by family name)

Candidate: Lanilis (Gildas Lanilis)

Dear ONAP TSC,



I am motivated to serve as ONAP’s Release Manager to support the on-time delivery of our releases. In this role, I will focus my energy on developing a Release framework (templates, tools, processes) so the ONAP community can deliver on time.



Over the past year, I served as OPEN-O’s Release Manager, where we delivered two on-time releases.  I understand what is necessary to support open source simultaneous releases.  I can dedicate 100% of my time to serve as the Release Manager and work hand in hand, transparently and openly, with the TSC’s members, the PTL’s and all the community with the only objective for all of us to be successful. I will help to remove roadblocks and report status to the community. I have also been working on LF cross-project harmonization efforts, and if elected, will continue to work with the respective communities on a common CI/CD toolchain.



I have over 20 years of industry experience, including 7 years as a developer, in delivering great software that helps people in their life. I am a strong supporter of Lean and Agile practices that have helped me as:

  • OPEN-O Release Manager, delivering as planned, on time 2 Open Source OPEN-O releases

  • Enterprise Software Release Manager,  adopting a 4 months release cycle to launch multiple releases to key customers

  • Director Development Best Practices, leading a R&D and Product Management department adopting Agile practices and resulting to a CMMI Level 3 certification

 

Thank you for your trust and support.

Gildas

Bio:

Gildas joined Huawei in 2016 as the OPEN-O Release Manager and is based in Santa Clara, CA, USA. In his role Gildas is running the delicate art of getting things done without formal authority.

Gildas is  coming from Virtual Hold Technology, where he served as Director of Release Management and DevOps Manager for Cloud Applications.

Gildas is a vivid Agile supporter and served at Genesys to lead the introduction of modern development practices and inspired R&D teams to deliver great software.

When he is not running, Gildas enjoys life with his family and cheers up his kids on the San Francisco Bay Area soccer fields or on the sideline of a swimming event. And when comes time to celebrate, nothing better than Champagne, French of course.