Since there's a good influx of volunteer OpenStack technical
election officials this round, I'm dropping back off the duty
roster. I'll still be around to help troubleshoot/patch the tooling
and answer questions.
Change-Id: Ib3c5e52733e189860fd94488a1d5997ca8b20e82
The special election had been completed. Record the results, and
also correct the "tag" used to generate the rolls, since the one
previously listed was from the Wallaby cycle election last year.
Change-Id: Iefba8fa46f3f518af1adb6f7c626d80e7002936a
Our recent Gerrit upgrade has made the emails method of the REST API
require essentially administrator permissions, making it no longer
feasible to find secondary addresses for change owners. Secondary
addresses really only served minor uses in this library anyway,
helping identify redundant accounts (which new Gerrit is forcing us
to clean up) and allowing slightly looser association to foundation
profiles.
Drop our use of the emails method, relying instead on the preferred
address provided with the owner record. In rare cases where an
account lacks a preferred address, substitute the committer address
from the first revision of the change where we initially encounter
that user.
Change-Id: Iee58c38a728343776354260c8b2d3fad09633ffa
During the TC meeting today[*], an immediate special election was
authorized for filling the seat which was left vacant when the prior
election did not receive sufficient nominations to fill all
available seats. We will be holding an election for one remaining
seat in the 2021-Q1 to 2022-Q1 term. As discussed in the meeting
there will be two weeks for nominations (during which time
candidates can also campaign if desired), followed by one week of
voting if we have more than one candidate.
The election setup reflects the full 5 seats for the term, even
though four are already filled, and will display the four already
elected candidates for the term so that we can reuse the same
nominations directory. When the nominations period concludes, only
the candidates not already elected for the term will be added to a
new poll for a single seat.
[*] http://eavesdrop.openstack.org/meetings/tc/2021/tc.2021-03-25-15.00.log.html#l-118
Change-Id: I2f78e3fa3474c1473b7805dc574a69e150e0bc6e
The close_election command treats TC elections as a single-team PTL
election, essentially. The leaderless list, however, is generated
from the full list of projects included in an election which, in a
parallel TC/PTL election will include more projects than just the
TC. Rather than heavily refactor the utility function where that
data is summarized, just delete the leaderless list from the
election results when reporting for the TC round in a parallel
TC/PTL election.
Change-Id: Ia8bb11addb9f70283b3e676d90e5e7b48494b8e1