Update election timeline for 2019 H2 and add PL/TL election details
This patch updates the election dates and deadlines for the H2 elections in 2019. This patch also adds description for PL/TL election details. The patch furthermore adjusts the text to clarify that only OpenStack Foundation individual members can participate in the elections. Change-Id: I011cb145a691f4323b81c666dd584a8b3e5fc53a
This commit is contained in:
Ildiko Vancsa
parent
f08b9ad831
commit
91b404c4bc
|
|
@ -3,15 +3,19 @@ StarlingX Election
|
|||
==================
|
||||
|
||||
|
||||
+-----------------+--------------------------+--------------------------+
|
||||
| Events | Start Date | End Date |
|
||||
+=================+==========================+==========================+
|
||||
| TSC Nominations | 2019, H2 | 2019, H2 |
|
||||
+-----------------+--------------------------+--------------------------+
|
||||
| TSC Campaign | 2019, H2 | 2019, H2 |
|
||||
+-----------------+--------------------------+--------------------------+
|
||||
| TSC Election | 2019, H2 | 2019, H2 |
|
||||
+-----------------+--------------------------+--------------------------+
|
||||
+-------------------+-----------------------------+-----------------------------+
|
||||
| Events | Start Date | End Date |
|
||||
+===================+=============================+=============================+
|
||||
| TSC Nominations | October 6, 2019, 20:45 UTC | October 13, 2019, 20:45 UTC |
|
||||
+-------------------+-----------------------------+-----------------------------+
|
||||
| PL/TL Nominations | October 6, 2019, 20:45 UTC | October 13, 2019, 20:45 UTC |
|
||||
+-------------------+-----------------------------+-----------------------------+
|
||||
| TSC Campaign | October 13, 2019, 20:45 UTC | October 20, 2019, 20:45 UTC |
|
||||
+-------------------+-----------------------------+-----------------------------+
|
||||
| TSC Election | October 20, 2019, 20:45 UTC | October 27, 2019, 20:45 UTC |
|
||||
+-------------------+-----------------------------+-----------------------------+
|
||||
| PL/TL Election | October 20, 2019, 20:45 UTC | October 27, 2019, 20:45 UTC |
|
||||
+-------------------+-----------------------------+-----------------------------+
|
||||
|
||||
|
||||
See `Election system`_, `PLTL details`_ and `TSC details`_.
|
||||
|
|
@ -41,14 +45,14 @@ Elections will be held using CIVS and a Condorcet algorithm
|
|||
Electorate
|
||||
==========
|
||||
|
||||
The electorate for this election are the individuals who earned the contributor
|
||||
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 May 31, 2019 00:00 UTC deadline so that the emailed ballots are mailed
|
||||
to the correct email address.
|
||||
prior to September 20, 2019 00:00 UTC deadline 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
|
||||
|
|
@ -86,16 +90,15 @@ repository. Here are the required steps:
|
|||
* Commit the candidacy:
|
||||
git add candidates/<election_cycle>/<project_name>/<leadership_role>/<email_address>;
|
||||
git commit
|
||||
* In the text editor add a title and specify your affiliation like:
|
||||
* In the text editor add a title like the following:
|
||||
|
||||
Adding <your_name> candidacy for <project_name> <project_role> role
|
||||
|
||||
Affiliation: <company_name>
|
||||
* 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/2019_H1/fault/pl/dana\@inconnu.org" to submit a PL candidacy
|
||||
named "candidates/2019_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
|
||||
|
|
@ -120,7 +123,7 @@ election. Seats are valid for one-year terms.
|
|||
Electorate
|
||||
----------
|
||||
|
||||
The electorate for this election are the individuals who earned the contributor
|
||||
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.
|
||||
|
||||
|
|
@ -128,13 +131,12 @@ defined by the `TSC charter`_ document.
|
|||
Candidates
|
||||
----------
|
||||
|
||||
Any individual contributor can propose their candidacy.
|
||||
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 commit message for the patch must contain the candidate's current
|
||||
affiliation (company name or 'independent').
|
||||
The candidacy is then confirmed by elections officials through gerrit.
|
||||
See above `How to submit a candidacy`_ documentation.
|
||||
|
||||
|
|
@ -144,7 +146,40 @@ See above `How to submit a candidacy`_ documentation.
|
|||
Project Leads' and Technical Leads' election
|
||||
============================================
|
||||
|
||||
TBD
|
||||
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::
|
||||
|
||||
|
|
@ -155,3 +190,6 @@ TBD
|
|||
.. _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
|
||||
|
|
|
|||
Loading…
Reference in New Issue