b21945d123
This patch updates the interim election timeline as we still need to fill the Distro and Test PL and TL positions since the regular election cycle didn't succeed with that. This patch adds these details to the timeline and updates the regular election timelines to reflect to the plans for 2022. Change-Id: Ied203ca25c2333f26ee43f687d7a64d1303b3311 Signed-off-by: Ildiko Vancsa <ildiko.vancsa@gmail.com>
225 lines
8.4 KiB
ReStructuredText
225 lines
8.4 KiB
ReStructuredText
==================
|
|
StarlingX Election
|
|
==================
|
|
|
|
StarlingX Interim Election Timeline
|
|
===================================
|
|
|
|
We are electing 2 TSC seats for a half-year term and PLs and TLs for the Distro
|
|
and Test sub-projects.
|
|
|
|
+-------------------+-----------------------------+-----------------------------+
|
|
| Events | Start Date | End Date |
|
|
+===================+=============================+=============================+
|
|
| TSC Nominations | November 16, 2021, 20:45 UTC| November 23, 2021, 20:45 UTC|
|
|
+-------------------+-----------------------------+-----------------------------+
|
|
| TSC Campaign | November 23, 2021, 20:45 UTC| November 30, 2021, 20:45 UTC|
|
|
+-------------------+-----------------------------+-----------------------------+
|
|
| TSC Election | November 30, 2021, 20:45 UTC| December 07, 2021, 20:45 UTC|
|
|
+-------------------+-----------------------------+-----------------------------+
|
|
| PL/TL Nominations | November 16, 2021, 20:45 UTC| November 23, 2021, 20:45 UTC|
|
|
+-------------------+-----------------------------+-----------------------------+
|
|
| PL/TL Election | November 30, 2021, 20:45 UTC| December 07, 2021, 20:45 UTC|
|
|
+-------------------+-----------------------------+-----------------------------+
|
|
|
|
|
|
StarlingX PL, TL and TSC Elections Timeline
|
|
===========================================
|
|
|
|
+-------------------+-----------------------------+-----------------------------+
|
|
| Events | Start Date | End Date |
|
|
+===================+=============================+=============================+
|
|
| TSC Nominations | H1, 2022 | H1, 2022 |
|
|
+-------------------+-----------------------------+-----------------------------+
|
|
| TSC Campaign | H1, 2022 | H1, 2022 |
|
|
+-------------------+-----------------------------+-----------------------------+
|
|
| TSC Election | H1, 2022 | H1, 2022 |
|
|
+-------------------+-----------------------------+-----------------------------+
|
|
| PL/TL Nominations | H2, 2022 | H2, 2022 |
|
|
+-------------------+-----------------------------+-----------------------------+
|
|
| PL/TL Election | H2, 2022 | H2, 2022 |
|
|
+-------------------+-----------------------------+-----------------------------+
|
|
|
|
See `Election system`_, `PLTL details`_ and `TSC details`_.
|
|
|
|
|
|
Election Officials
|
|
==================
|
|
|
|
* Ildiko Vancsa (ildikov), ildiko at openstack dot org
|
|
* Bill Zvonar (), Bill.Zvonar at windriver dot com
|
|
* Yong Hu (), yong.hu at intel dot com
|
|
|
|
For any questions, please contact officials by mail or over irc at
|
|
#starlingx Freenode channel.
|
|
|
|
|
|
.. _Election system:
|
|
|
|
Election System
|
|
===============
|
|
|
|
Elections will be held using CIVS and a Condorcet algorithm
|
|
(Schulze/Beatpath/CSSD variant). Any tie will be broken using
|
|
`Governance_TieBreaking`_.
|
|
|
|
|
|
Electorate
|
|
==========
|
|
|
|
The electorate for this election are individuals who earned the contributor
|
|
status some time in the past 12 months prior to the nomination period starts as
|
|
defined by the `TSC charter`_ document.
|
|
|
|
The electorate is requested to confirm their email address in gerrit,
|
|
review.opendev.org > Settings > Contact Information > Preferred Email,
|
|
prior to October 22, 2021 so that the emailed ballots are mailed to the correct
|
|
email address.
|
|
|
|
The electorate is expected to abide by the following general resolution:
|
|
https://docs.starlingx.io/governance/resolutions/20190520_election_activities.html
|
|
|
|
Candidates
|
|
==========
|
|
|
|
Any member of an election electorate can propose their candidacy for the same
|
|
election. Nominees propose their candidacy by submitting a text file to the
|
|
starlingx/election repository. See documentation below.
|
|
|
|
|
|
.. _How to submit a candidacy:
|
|
|
|
How to submit a candidacy
|
|
=========================
|
|
|
|
Each candidate must nominate themselves for each elected position, and are
|
|
encouraged to submit their own candidacy to gerrit, although where
|
|
appropriate, others may submit a candidacy for those who have already
|
|
self-nominated by other means.
|
|
|
|
If you are not already familiar with StarlingX development workflow, see this
|
|
more detailed documentation:
|
|
https://docs.starlingx.io/contributor/index.html
|
|
|
|
Candidacies now need to be submitted as a text file to the starlingx/election
|
|
repository. Here are the required steps:
|
|
|
|
* Clone the election repository:
|
|
git clone https://opendev.org/starlingx/election.git ; cd election
|
|
* Create a new file
|
|
candidates/<election_cycle>/<project_name>/<leadership_role>/<email_address>
|
|
containing the candidate statement.
|
|
* Commit the candidacy:
|
|
git add candidates/<election_cycle>/<project_name>/<leadership_role>/<email_address>;
|
|
git commit
|
|
* In the text editor add a title like the following:
|
|
|
|
Adding <your_name> candidacy for <project_name> <project_role> role
|
|
|
|
* Save the text and exit the text editor
|
|
* Submit your candidacy: git review
|
|
|
|
For example Dana Developer (ddev on IRC) would compose a platform in a file
|
|
named "candidates/2020_H2/fault/pl/dana\@inconnu.org" to submit a PL candidacy
|
|
for the Fault Management project elections.
|
|
|
|
After the candidacy is submitted to gerrit, verification and approval will
|
|
be performed by elections officials, followed by an update to the approved
|
|
candidate list.
|
|
|
|
|
|
.. _TSC details:
|
|
|
|
Technical Steering Committee's election
|
|
=======================================
|
|
|
|
Elected Positions
|
|
-----------------
|
|
|
|
Under the rules of the `TSC charter`_, we need to renew 3 TSC seats for this
|
|
election. Seats are valid for one-year terms.
|
|
|
|
* Technical Steering Committee member - 3 positions.
|
|
|
|
Interim Elected Positions
|
|
-------------------------
|
|
|
|
Under the rules of the `TSC charter`_, we need to fill 2 TSC seats for this
|
|
election. Seats are valid for 6-month terms.
|
|
|
|
* Technical Steering Committee member - 2 positions.
|
|
|
|
Electorate
|
|
----------
|
|
|
|
The electorate for this election are individuals who earned the contributor
|
|
status some time in the past 12 months prior to the nomination period starts as
|
|
defined by the `TSC charter`_ document.
|
|
|
|
|
|
Candidates
|
|
----------
|
|
|
|
Any contributor who is an individual member of the foundation can propose their
|
|
candidacy.
|
|
|
|
Nominees propose their candidacy by submitting a text file to the
|
|
starlingx/election repository. The file must be placed in
|
|
candidates/<electcycle>/TSC/<email_address>.
|
|
The candidacy is then confirmed by elections officials through gerrit.
|
|
See above `How to submit a candidacy`_ documentation.
|
|
|
|
|
|
.. _PLTL details:
|
|
|
|
Project Leads' and Technical Leads' election
|
|
============================================
|
|
|
|
Elected Positions
|
|
-----------------
|
|
|
|
Every `official project team`__ must elect a `PL`_ and a `TL`_. PLs and TLs are
|
|
elected for a one year period.
|
|
|
|
__ `official project teams`_
|
|
|
|
|
|
Electorate
|
|
----------
|
|
|
|
Except otherwise-noted in the project team description, the electorate for a
|
|
given PL and TL election are the individuals that are also committers for one
|
|
of the team's repositories over the past 12 months prior to the nomination
|
|
period starts as defined by the `TSC charter`_ document.
|
|
|
|
|
|
Candidates
|
|
----------
|
|
|
|
Any contributor who is an individual member of the foundation can propose their
|
|
candidacy to run for PL.
|
|
|
|
Any contributor who is an individual member of the foundation and a `core
|
|
reviewer`_ to the given project can propose their candidacy to run for TL of
|
|
the given project.
|
|
|
|
Nominees propose their candidacy by submitting a text file to the
|
|
starlingx/election repository. The file must be placed in
|
|
candidates/<electcycle>/<project_name>/<leadership_role>/<email_address>.
|
|
The candidacy is then confirmed by elections officials through gerrit.
|
|
See above `How to submit a candidacy`_ documentation.
|
|
|
|
|
|
.. seealso::
|
|
|
|
See the `Election Officiating Guidelines`_ page in the wiki for details on the
|
|
election process.
|
|
|
|
.. _Election Officiating Guidelines: https://wiki.openstack.org/wiki/Election_Officiating_Guidelines
|
|
.. _Governance_TieBreaking: https://wiki.openstack.org/wiki/Governance/TieBreaking
|
|
.. _TSC charter: https://docs.starlingx.io/governance/reference/tsc/stx_charter.html
|
|
.. _official project teams: https://docs.starlingx.io/governance/reference/tsc/projects/index.html
|
|
.. _PL: https://docs.starlingx.io/governance/reference/tsc/stx_charter.html#project-lead
|
|
.. _TL: https://docs.starlingx.io/governance/reference/tsc/stx_charter.html#technical-lead
|
|
.. _core reviewer: https://docs.starlingx.io/governance/reference/tsc/stx_charter.html#core-reviewer
|