To aid the ONAP project through the release process, the ONAP Technical Steering Committee (TSC) will elect a Release Manager from the community 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 plan and schedule. This position may be held by anyone in the ONAP community regardless of membership status or prior history of contributions to the Project

Description of Job Role

The ONAP Release Manager guides the individual projects that comprise the ONAP platform to the timely delivery of regular software releases, follow-on stable releases, and manage any ad-hoc releases as required.  The Release Manager works directly with the community to formulate a release plan (currently on a Spring/Fall cadence) from inception through approval by the TSC. Once approved, the Release Manager then guides the ONAP development community through the process and procedures needed to execute against that plan.  A passion for release planning, cross project coordination, automation, and release delivery, as well as the ability to effectively partner with contributors from around the globe are required to be effective in this position.

Primary Responsibilities
- Work with the ONAP TSC, Project Technical Leads (PTLs) and Subcommittee Chairs 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.
- Regularly communicate the status of the release to PTLs, the TSC, the LF and the community at large.
- Help identify release-blocking issues to keep release process on schedule
- Deliver timely release artifacts (executable(s), documentation, testing output, etc.)

In addition, the TSC has currently designated the Release Manager as the Infrastructure Coordinator for ONAP.   The Infrastructure Coordinator's role is to ace as the TSC's  delegate, responsible for reviewing and approving  repository creation requests, new Committer requests and coordinating with LF release engineering staff on other issues pertaining to infrastructure requirements. (This role may be split out at the TSC's discretion in the future).

Typical 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.
- Previous experience with open source release management is strongly recommended

How to nominate yourself

The election process occurs in two phases; the Nomination phase, and the Election phase, following the process documented here, (Community Coordinator Elections):

Self Nomination Phase
An email tagged as "ONAP RELEASE MANAGER ELECTION" has be sent by the LF to the onap-tsc distribution list. (https://lists.onap.org/g/ONAP-TSC/message/3698)  Individuals interested in running for this position must reply-all to that email with your intention to run.  Candidates are strongly recommended that candidates include a biography and statement of intent on why you would be a good person to hold this position.

In addition, it is requested that candidates also fill in the Information on the Candidates section of this wiki page with that same information. Note that filling out the wiki page is NOT in lieu of sending the email as required.

• The nomination phase begins with the receipt of the announcement ( as verified by checking groups.io )
• The nomination phase ends 10:30 PM Pacific Time, Thursday,  Sep. 20th (one calendar week) after the announcement 

Election Phase

If there are multiple nominees: A Condorcet election will be initiated by the LF using the CIVS voting system.  All TSC members will receive an invitation to vote. In the case of multiple candidates the timing is as follows:

• The election phase will begin on with the distribution of the CIVS poll via email
• The election phase will end four (4) full business days later in the same time zone the poll was initiated from

Election Results The LF will update the Voting Results History page with their name, date, and link either to the publicly viewable CIVS results or vote email thread and send an email to the distribution list and to onap-tsc

Information on the Candidates