Every year the Community is required to vote the technical leadership for ONAP projects. It is the time to take a pragmatic look at how we are functioning as a community and ensure that we are set to scale for the challenges ahead.
...
There is no "automatic rollover" for any of these positions, with the exception of those individuals who are Committers. All of others are subject to the annual election process.
| Note |
|---|
Make sure your spam filter does not block mail from civs@cs.cornell.edu or you may not receive a ballot if you are authorized to vote. Ballots can only be resent from the tool, they cannot be sent as a forward from an individual. |
...
- The individual receiving the highest number of votes from all votes cast shall be declared the winner UNLESS other provisions have already been agreed to within a particular subcommittee such as the top two vote getters are elected as joint-Chairs or the top vote getter is elected as Chair and the runner-up is elected Vice-Chair.
- The LF newly (re)-elected Chair 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 their distribution list and with a cc to onap-tsc
Escalations:
Escalate to the TSC if the sitting Chair does not initiate either the announcement or the poll in a timely fashion, or if fewer than 50% +1 of the eligible voters respond to CIVS.
If you have fundamental concerns about the process, any member of the community can always reach out to your LFN Program Manager by sending an email to pmo @ onap.org (minus the blank spaces)
...
Community Coordinator Elections
...