| fungi | so you'll want to finalize the polls, open them and start adding voter rolls basically the moment nominations close at 23:45 utc | 00:00 |
|---|---|---|
| spotz | Yeah just reading through - https://opendev.org/openstack/election | 00:01 |
| spotz | Looks like gmann has to tag the governance repo? | 00:01 |
| ianychoi[m] | Thank u all and let me allocate some time for smooth election - hope my different Asia time zone helps. knikolla which tz you are? | 00:01 |
| fungi | or you can plug in a raw git ref if absolutely necessary and have that tagged later | 00:02 |
| knikolla | ianychoi[m]: i'm on EST | 00:02 |
| knikolla | Thank you :) | 00:02 |
| fungi | also this is probably the first time we've used civs in roughly a year, so hopefully it hasn't changed too much | 00:02 |
| knikolla | yeah, i was pleasantly surprised to see a need for elections :) | 00:03 |
| spotz | I know from the Board election we needed to remind folks to opt in | 00:03 |
| spotz | We're going to need --tag TAG The governance tag to validate against. Default: oct-2022-elections | 00:04 |
| fungi | right, people won't receive ballots from civs any longer unless they've first told civs they're okay receiving them (apparently someone was using civs to spam people) | 00:04 |
| ianychoi[m] | Election with votes makes us energetic:) | 00:04 |
| spotz | It's just crap timing for me | 00:05 |
| spotz | I'm assuming the tag is the only thing we need from - tox -evenv -- generate-rolls --help | 00:06 |
| spotz | I think there's definitely going to be a time gap from noms end until we can get this started. We need the tag, to generate the rolls, then send the opt in email | 00:07 |
| ianychoi[m] | spotz: I can propose to gov repo for tagging | 00:07 |
| ianychoi[m] | I did it prev times | 00:07 |
| spotz | No campaigning while it got us more candidates we've lost the week for setup as fungi mentioned | 00:08 |
| spotz | thanks ianychoi[m], if you can do anything you've done before that'll speed us up some vs us getting it wrong the first time | 00:08 |
| spotz | I'm all for expediency this election with the late start | 00:10 |
| fungi | i can't recall if the release team was still handling release requests for the governance repo still, or whether they concluded it needed manual tagging | 00:11 |
| fungi | oh, but i can check easilt | 00:11 |
| fungi | easily | 00:11 |
| fungi | looks like yes, release management is handling it, last tag was 0.12.0 | 00:13 |
| fungi | oct-2022-elections is the "old" way from when we did manual tagging, and we stopped that in 2019 from what i can see | 00:14 |
| fungi | 0.13.0 is probably the release request you'll want to submit | 00:14 |
| ianychoi[m] | Sure thank u for the double checking i also remember that we are using version numbers now | 00:16 |
| spotz | jungleboyj: forgot to include you here last night | 12:08 |
| spotz | So are we still waiting for the tagging to be requested? | 12:34 |
| fungi | yeah, i don't see any for an openstack/governance 0.13.0 yet when looking at is:open project:openstack/releases | 12:49 |
| ianychoi[m] | Ah, thought i need to do after nomination closes but have realized now that we can do when election starts.. will see in 2-3 hrs | 12:56 |
| fungi | well, the release team needs the tc chair to +1 the request and then they review and approve the change | 12:57 |
| fungi | as i mentioned earlier, this time people decided to leave no gap between end of nominations and start of voting, so that tag would need to be created as immediately as possible given there are review and automation related delays inherent in the release request | 12:58 |
| spotz | I can see where we should have kept at least a few days for campaigning:( We were fine with no voting | 12:58 |
| fungi | we used to tag governance earlier anyway, basically as soon as the extra-atcs deadline had passed | 12:59 |
| fungi | the idea is just to go into the election with as accurate a picture as possible of who the extra atcs are and which deliverable repositories are "official" at the time of the election. if there's not a lot of pending governance changes which would alter those things, then it doesn't matter how early it gets tagged | 13:00 |
| fungi | it's so that there's a documented "point in time" for the governance repository which was used to determine who the electorate were, in case anyone wants to go back and verify the rolls later | 13:01 |
| gmann | spotz: sure, will propose the tag | 13:10 |
| spotz | Thanks gmann | 13:12 |
| opendevreview | Ian Y. Choi proposed openstack/election master: Match tag version for the current election https://review.opendev.org/c/openstack/election/+/856286 | 13:56 |
| gmann | spotz: ianychoi[m] https://review.opendev.org/c/openstack/releases/+/856287 | 13:58 |
| ianychoi[m] | gmann, spotz: see ^ and https://review.opendev.org/c/openstack/releases/+/856284 and please double-check if there are any issues.. | 13:58 |
| gmann | just saw ianychoi[m] patch. I think we were in racwe | 13:59 |
| gmann | :) | 13:59 |
| ianychoi[m] | :) | 13:59 |
| gmann | ianychoi[m]: which hash you used in your? 57e0b3f09ffe3489cccbc2a8462b9b8d28f7821a | 14:00 |
| gmann | I am using the latest one as per email deadline of today | 14:00 |
| ianychoi[m] | gmann: I used the hash number around before election starts as fungi said that tagging can be done before election goes | 14:01 |
| fungi | we used to tag just after the extra-atcs deadline | 14:02 |
| fungi | but really any commit after that is fine too | 14:02 |
| gmann | it should be of date of email deadline? | 14:02 |
| gmann | ianychoi[m]: I used latest one, I can abandon mine if you can update your patch | 14:03 |
| fungi | e-mail addresses used to determine electorates (other than extra-atcs entries hence the deadline for them) don't get updated in the governance repo, so it doesn't matter | 14:03 |
| fungi | it's just about picking a point in time were we say "this was the state of the governance repository we used to determine who is eligible to vote" | 14:03 |
| fungi | because adding and removing deliverable repositories from teams can alter that, and make it hard to repeat results afterward if you don't know what exact state you were using to generate the rolls for the election | 14:04 |
| ianychoi[m] | Yep, to add from fungi's point, election officials: let's use tag number on configuration.yaml to be aligned like this way: https://review.opendev.org/c/openstack/election/+/856286/1/configuration.yaml | 14:05 |
| ianychoi[m] | My confusion part was.. here on current election homepage: "Yoga-Zed timeframe (Sep 17, 2021 00:00 UTC to Sep 07, 2022 00:00 UTC)" | 14:06 |
| ianychoi[m] | Not sure which were wrong.. but right now, to reflect the homepage's saying, I want to abandon my patch on release repo and would like to vote on gmann's patch :) | 14:06 |
| gmann | ianychoi[m]: I used email election deadline in past also. both hash satisfy but let's use consistently so that it will be easy for future tag release too | 14:06 |
| fungi | ouch, yes that's also problematic if we're saying we'll accept changes merged to repositories up to the moment voting starts. we notmally have weeks there | 14:07 |
| fungi | normally | 14:07 |
| fungi | lesson learned for the election officials and leadership, you really can't "compress" the election schedule without significant pains | 14:07 |
| ianychoi[m] | For past elections, electorate's eligibility period is before PTL nominations | 14:08 |
| opendevreview | Ian Y. Choi proposed openstack/election master: Match tag version for the current election https://review.opendev.org/c/openstack/election/+/856286 | 14:12 |
| ianychoi[m] | Next step seems to execute "tox -evenv -- generate-rolls", which requires tag number to be merged | 14:26 |
| knikolla | o/ | 14:33 |
| fungi | ianychoi[m]: if necessary, you can supply a commit id instead of a tag name and it should work, just use the id of the commit which is going to be tagged for consistency | 15:07 |
| fungi | (at least it used to work) | 15:07 |
| spotz | Give i a shot ianychoi[m]! | 15:12 |
| ianychoi[m] | Thank you.. now I have been recovering memories through Etherpad: https://etherpad.opendev.org/p/TC_PTL_ElectionsAugSep2022 | 15:14 |
| ianychoi[m] | fungi: any quick pointers according to your previous experience on generate-roll command error like https://paste.opendev.org/show/bX2xfeuubpxlsQs47HX2/ ? | 15:20 |
| opendevreview | Grzegorz Grasza proposed openstack/election master: Add Grzegorz Grasza candidacy for Barbican https://review.opendev.org/c/openstack/election/+/856295 | 15:21 |
| fungi | ianychoi[m]: looks like some contributor probably is getting returned with a None e-mail address. could add an error printing statement around that routine with a try/except so we know which account it is | 15:22 |
| ianychoi[m] | Yeah, now I can identify by searching with owner id (account id!) https://review.opendev.org/q/owner:7353 - seems Kevin Carter with Email: undefined | 15:26 |
| knikolla | 7353 | 15:26 |
| knikolla | beat me to it :) | 15:26 |
| ianychoi[m] | For such user, would skipping (not including the e-mail address) for vote be fine? | 15:28 |
| knikolla | After that it prints out MERGING DUPLICATE ACCOUNT: 7353 into 4257, so I think we can just ignore that error for now. | 15:28 |
| ianychoi[m] | Thank knikolla ! | 15:28 |
| knikolla | well, i take that back. the merging of accounts seems incorrect ianychoi[m] | 15:29 |
| knikolla | user 4257 is zane instead of kevin. the the merging seems incorrect. | 15:30 |
| knikolla | pinged on #opendev | 15:34 |
| ianychoi[m] | Now, I am executing on my local environment with such change, and so far I couldn't see the error message knikolla saw: https://paste.opendev.org/show/bjCjeCPaiK1QPWR1eo0B/ | 15:35 |
| fungi | yeah, the merging function in that script relies on matching up e-mail addresses, so it's probably merging two accounts with a matching None address. we should probably skip any accounts with a None address before we get that far into the script | 15:42 |
| fungi | especially now that we've worked through most of the duplicate addresses in existing gerrit accounts and gerrit no longer allows creating new accounts with the same addresses as associated with an existing account | 15:43 |
| fungi | it's mostly there to avoid giving someone multiple ballots if they created more than one account | 15:43 |
| opendevreview | David Wilde proposed openstack/election master: Add Dave Wilde candidacy for Keystone https://review.opendev.org/c/openstack/election/+/856297 | 15:51 |
| ianychoi[m] | Thank you fungi :) | 16:50 |
| ianychoi[m] | "tox -evenv -- generate-rolls" execution has been successfully finished - https://paste.opendev.org/show/bwgIwdPet0qZNOTedbvZ/ | 16:50 |
| ianychoi[m] | So far, seems Ironic PTL and TC election need to be run at least after around 7 hours later. For TC election, making sure to set with 4 seats on CIVS would be double-checked. I believe we can use others as default options | 16:53 |
| knikolla | ianychoi[m]: the user that we were having issues above updated their email address in gerrit. so you might want to add that to the rolls manually or re-run the rolls | 17:47 |
| ianychoi[m] | @knikolla: yep see https://paste.opendev.org/show/b0xspQpeTrHJveu85Zwx/ | 21:56 |
| ianychoi[m] | Note that I need to drive soon and might be back around 0:30 UTC.. will continue, and have sent the raw data to the all election officials via e-mail. | 21:57 |
| knikolla | ianychoi[m]: drive safe. also spotz was suggesting we don't rush this and extend campaigning to until Monday and start election then. | 22:02 |
| spotz | knikolla: ianychoi[m] Only thing I see in the poll is Dan's nick is dansmith but I don't see a way to edit | 23:54 |
| spotz | knikolla: do you want to do the patch and the email or want me to? | 23:55 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!