ianychoi[m] | I am processing open nomination reviews: double-checking & approvals if needed | 00:01 |
---|---|---|
opendevreview | Merged openstack/election master: Adding Takashi Kajinami candidacy for Storlets PTL https://review.opendev.org/c/openstack/election/+/893123 | 00:11 |
opendevreview | Merged openstack/election master: Adding Takashi Kajinami candidacy for Heat PTL https://review.opendev.org/c/openstack/election/+/893126 | 00:13 |
opendevreview | Merged openstack/election master: Add Pranali Deore's candidacy for Glance PTL 2024.1 https://review.opendev.org/c/openstack/election/+/893128 | 00:15 |
opendevreview | Merged openstack/election master: Adding Takashi Kajinami candidacy for Puppet OpenStack PTL https://review.opendev.org/c/openstack/election/+/893130 | 00:18 |
opendevreview | Merged openstack/election master: Add Dave Wilde candicacy for Keystone 2024.1 PTL https://review.opendev.org/c/openstack/election/+/893179 | 00:25 |
opendevreview | Merged openstack/election master: Tim Burke candidacy for Swift PTL (Caracal) https://review.opendev.org/c/openstack/election/+/893281 | 00:25 |
opendevreview | Ian Y. Choi proposed openstack/election master: [WIP] Fix on combined election nomination end template https://review.opendev.org/c/openstack/election/+/893297 | 00:45 |
opendevreview | Ian Y. Choi proposed openstack/election master: Update governance tag 0.15.0 to configuration https://review.opendev.org/c/openstack/election/+/893299 | 01:00 |
ianychoi[m] | Finally done with announcement: https://lists.openstack.org/pipermail/openstack-discuss/2023-August/034925.html and https://lists.openstack.org/pipermail/openstack-discuss/2023-August/034927.html | 01:01 |
ianychoi[m] | gmann: About a corresponding patch ^^, I think TC can finalize tag to releases before election starts to reflect tag number to configuration.yaml. For example, current election web page renders tag number as "to-be-released": https://governance.openstack.org/election/#project-team-leads-election | 01:03 |
ianychoi[m] | From my remembrance, tagging governance is to store the state of governance for the timing of election so tagging before election starts would be also fair in my opinion. Any comments/idea on this? | 01:05 |
fungi | yes, it's so that we can accurately track what the state of the list of project repositories and extra contributors lists are, in order to be able to independently verify electoral rolls | 01:13 |
opendevreview | Wenping Song proposed openstack/election master: Add Wenping Song candidacy for Cyborg PTL https://review.opendev.org/c/openstack/election/+/893300 | 01:35 |
opendevreview | inspurericzhang proposed openstack/election master: Adding Eric Zhang candidacy for Venus https://review.opendev.org/c/openstack/election/+/893303 | 02:22 |
opendevreview | XueFengLiu proposed openstack/election master: Adding XueFeng Liu candidacy for Senlin PTL https://review.opendev.org/c/openstack/election/+/892880 | 03:08 |
opendevreview | XueFengLiu proposed openstack/election master: Adding XueFeng Liu candidacy for Senlin PTL https://review.opendev.org/c/openstack/election/+/892880 | 03:10 |
opendevreview | XueFengLiu proposed openstack/election master: Add XueFeng Liu candidacy for Senlin 2024.1 PTL https://review.opendev.org/c/openstack/election/+/892880 | 03:41 |
gmann | ianychoi[m]: purpose of tag is right but when it needs to be done seems in question. I think it needs to be tag after email_deadline of electionnot before the start of election right? that is why we put "to-be-released" and once email_deadline reach we release and update the election config | 15:59 |
gmann | reason for that is electorate are considered from that duration (till election timeframe/email deadline) and if any new project gets added in OpenStack during election nominations then it will miss out their contributors to be electorate. | 16:01 |
fungi | yes, but making the cut-off earlier allows the election officials some breathing room and gives them more time to generate and check over the rolls | 16:09 |
fungi | back when i was officiating, we'd usually take a week generating and regenerating rolls and checking for concerns or potential errors | 16:10 |
fungi | having only a day or two to get that done puts a lot of unnecessary pressure on the officials | 16:10 |
fungi | we set the e-mail deadline at the end of the nomination period so that the campaign period could be used to handle the rolls and setting up and checking over the polls too | 16:12 |
fungi | and that was the reason we made the campaign period a week long | 16:12 |
fungi | not because we thought community q&a would take that long, but because we needed that extra time to do a good job on all the setup behind the scenes to get ready to run the elections | 16:13 |
opendevreview | Merged openstack/election master: Update governance tag 0.15.0 to configuration https://review.opendev.org/c/openstack/election/+/893299 | 16:59 |
gmann | yeah, 1 week of campaign should give some time at least | 17:01 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!