gmann | yeah, I have that ready but waiting for this to merge https://review.opendev.org/c/openstack/election/+/825017/4 | 00:03 |
---|---|---|
gmann | election officials: I have created the etherpad to record the progress and action items for the elections https://etherpad.opendev.org/p/TC_PTL_Elections2022#L5 | 00:13 |
gmann | I will send the first email soon and then will kick off the nomination on 8th | 00:14 |
opendevreview | Merged openstack/election master: Setup dates for Z combined election https://review.opendev.org/c/openstack/election/+/825017 | 00:20 |
gmann | site is updated and email also sent https://governance.openstack.org/election/ | 00:26 |
opendevreview | Merged openstack/election master: Set up candidacy directories for Z elections https://review.opendev.org/c/openstack/election/+/828021 | 01:14 |
*** spotz is now known as Guest2040 | 01:32 | |
*** spotz_ is now known as spotz | 01:32 | |
jungleboyj | gmann: E-mail you sent out looks good. Thanks! | 14:14 |
ianychoi[m] | gmann: thanks :) | 14:46 |
gmann | jungleboyj: ianychoi[m] I have generated the nomination kickoff email from template (with few addition of dates for clarity), which I will send tomorrow: please check if everything is correct: L65 in https://etherpad.opendev.org/p/TC_PTL_Elections2022 | 19:45 |
jungleboyj | gmann: Looks good. As we receive candidates is there an easy way to verify that the person has submitted a patch in the appropriate timeframe? | 19:48 |
fungi | jungleboyj: the ci jobs which run will check that, and you can look at the logs from them for links to the samples they found | 19:52 |
fungi | as well as the queries they ran | 19:53 |
jungleboyj | fungi: Thanks. So just part of reviewing the patch they submit. | 19:53 |
fungi | yep | 19:53 |
jungleboyj | Awesome. Thank you! | 19:53 |
* jungleboyj is making an effort to learn so I can actually help. :-) | 19:53 | |
gmann | yeah, jungleboyj its this job ' election-tox-ci-checks-review ' run in check pipeline for every candidacy patch | 19:59 |
gmann | jungleboyj: if any error then we can debug for them like email address is right or different from foundation profile, membership etc | 20:00 |
fungi | but also on a successful run, the log will say why it was successful too | 20:00 |
gmann | yeah | 20:00 |
diablo_rojo_phone | And if I recall you can dig through the logs for actual links to profiles and patches | 20:01 |
diablo_rojo_phone | gmann: if you made tweaks to the email that you think would be beneficial longterm can you update the template? | 20:02 |
gmann | sure, will do | 20:02 |
fungi | diablo_rojo_phone: not just the links to the resulting changes/profiles but also links for the queries which were performed to find those | 20:04 |
fungi | helpful in case you need to manually check things after someone makes an update to their membership or something | 20:04 |
gmann | it is run in verbose mode | 20:05 |
diablo_rojo_phone | Oh yeah - even better :) | 20:07 |
gmann | updated sub as "Combined PTL/TC z cycle Election Nominations Kickoff". I will update template too | 20:49 |
opendevreview | Ghanshyam proposed openstack/election master: Add release cycle info in sub line of template emails https://review.opendev.org/c/openstack/election/+/828192 | 20:50 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!