| ianychoi[m] | Have sent nominations end: http://lists.openstack.org/pipermail/openstack-discuss/2021-August/024401.html and TC campaigning kick-off e-mails: http://lists.openstack.org/pipermail/openstack-discuss/2021-August/024402.html | 00:08 |
|---|---|---|
| fungi | great work! so at this point you just need the cyborg electorate and poll setup, you've got a week to get those generated and set up | 00:13 |
| ianychoi[m] | Yep 1) asking to TC 2) generating a poll - 2 works needed AFAIK. I am not familiar with 2 so might need others help | 00:13 |
| spotz | I dont think we need a TC Campaign to be honest unless we got a 5th in when I wasn't looking | 00:18 |
| ianychoi[m] | Oh.. but still might be worth Q&A | 00:18 |
| ianychoi[m] | spotz: would you help move forward? E.g., sending an e-mail that it is just for Q&A time to new candidates although election does not need? | 00:20 |
| spotz | ianychoi[m]: Do we need to? With no election answers won't affect anything | 00:21 |
| ianychoi[m] | spotz: or you can send an e-mail that we close since no election will happen | 00:22 |
| ianychoi[m] | I don't have a strong opinion. Just have been doing next steps on the tool.. | 00:22 |
| spotz | ianychoi[m]: Yeah I get you, having everything status quo just helps us with any TC related tasks for the empty PTL slots, etc | 00:24 |
| ianychoi[m] | Thank you :) | 00:26 |
| spotz | ianychoi[m]: working on the closing the TC election patch stuff | 00:27 |
| opendevreview | Amy Marrich proposed openstack/election master: Update REEADME for correct location and close out TC election https://review.opendev.org/c/openstack/election/+/805918 | 00:34 |
| opendevreview | Amy Marrich proposed openstack/election master: Update README for correct location and close out TC election https://review.opendev.org/c/openstack/election/+/805918 | 00:35 |
| spotz | ianychoi[m]: Ok I modified the announce email to be relevent to the no campaign and election needed. Hitting send in 5 if no objections | 00:50 |
| ianychoi[m] | No objection from me - thanks a lot | 00:53 |
| spotz | sent:) | 00:55 |
| ianychoi[m] | Great!! | 00:56 |
| hspease | Thanks for getting those emails out :) @spotz @ianychoi[m] | 02:42 |
| ianychoi[m] | Thank u too @hspease | 02:45 |
| fungi | spotz: i haven't approved your message to openstack-announce yet and wanted to discuss it. in the past we haven't in the past announced technical election results on that ml, we try to keep it very low-volume and it normally only use it for the coordinated release announcements and security advisories | 12:18 |
| spotz | fungi I only sent it there as it was in results/yoga/announce_tc.rst. | 12:19 |
| spotz | Which I diid rewriite to omeet the circumstances so I'm fine with you nulling it | 12:20 |
| fungi | ahh, i wonder if we sent it there at some point in the past, but i wasn't finding evidence of that in the list archives | 12:21 |
| fungi | if we have, it hasn't been for a long while anyway | 12:21 |
| spotz | Yeah I was a little surprised but it was there cause we haven't sent any other election emails therer | 12:22 |
| fungi | looks like tony put it in the template back when it was added in early 2017, and i see one time i sent it there a couple years ago: http://lists.openstack.org/pipermail/openstack-announce/2019-September/002022.html | 12:26 |
| fungi | oh, tony also sent one a year prior to that: http://lists.openstack.org/pipermail/openstack-announce/2018-August/002016.html | 12:27 |
| fungi | and tristan once a year before then: http://lists.openstack.org/pipermail/openstack-announce/2017-April/002007.html | 12:29 |
| fungi | so we've inconsistently sent them to openstack-announce, but less often than not | 12:29 |
| fungi | we could try to revive that tradition and be more consistent about it, or go to just announcing election results on the discuss ml (since that's where all the other election communications go anyway( | 12:30 |
| spotz | fungi Yeah I'd say just discuss and I'll look at pulling it from the template | 12:32 |
| fungi | thanks spotz! i'm good either way. i'll go ahead and discard the copy in the announce ml mod queue in that case | 12:32 |
| spotz | fungi: If it's the only thing we send there it's not fair to the PTLs if that makes sense | 12:33 |
| fungi | if the election officials confer and conclude they'd rather go back to sending to -announce as well (and do it more consistently) you can always resend it | 12:34 |
| fungi | and yeah, the one i sent in 2019 was a combined election results e-mail which included the ptls and tc members both | 12:34 |
| spotz | Actually it looks like the PTL results template has it too | 12:35 |
| spotz | We'll discuss and then remove from the templates or leave alone | 12:35 |
| spotz | And maybe another update too othe readme too say send results there | 12:36 |
| fungi | right, it's both templates, and git grep also turns up a hit in the ussuri results yaml file (i guess because that one time i referred to the copy there instead of the one from the discuss ml) | 12:36 |
| spotz | yeah I did grep -lir :) | 12:36 |
| spotz | I also added in my email if you'd like to run in the future join the channel and see what we do:) I think it's important too know what you're getting into before jumping in | 12:38 |
| fungi | great idea! | 12:39 |
| fungi | always good to remind the rest of the community how and where they could pitch in if interested | 12:39 |
| spotz | yep yep | 12:40 |
| fungi | just a word of warning on the cyborg ptl runoff, it looks like the project probably has around a dozen electors for ptl, and i wouldn't be surprised if none of them has done the thing to allow civs to send them e-mail (many of their addresses might not even be current and accepting messages at all for that matter) | 12:44 |
| fungi | there's no requirement for quorum, but still the results of the election could be questionable or easily influenced with so few votes cast | 12:45 |
| fungi | of course, if you get no votes cast, that presents a problem as well | 12:46 |
| fungi | with numbers this small, that's a distinct possibility too | 12:46 |
| spotz | ok | 13:50 |
| ianychoi[m] | (following up conversations) | 13:54 |
| ianychoi[m] | I think sharing the summary of combined election results with openstack-announce is a good idea | 14:08 |
| ianychoi[m] | Regarding cyborg, not 100% sure but looks like that it is better than previous cycle since there no Cyborg PTL candidate - I have thought that discussing with current PTL would be great | 14:12 |
| fungi | yeah, having ptl candidates is good, just pointing out that the number of people who can vote for them is very small, and possibly so small you may end up with no votes | 14:15 |
| fungi | especially when you take connectedness of the team with the rest of the community into account | 14:15 |
| ianychoi[m] | On the other hand election needs to happen - some possible ways from my current head: 1) encouraging via individual e-mails for more votes 2) current candidates need to run for campaign period ... | 14:21 |
| ianychoi[m] | Not sure how to move forward this | 14:22 |
| opendevreview | Merged openstack/election master: Add build folder in .gitignore https://review.opendev.org/c/openstack/election/+/801546 | 14:44 |
| opendevreview | Merged openstack/election master: bump py35,py37 to py3 in tox.ini https://review.opendev.org/c/openstack/election/+/757376 | 18:16 |
| spotz | ianychoi[m]: from what I interpretted to fungi is we should mail all the Cyborg people with instructions hoow to confirm their email foro the system and give them a few days then do the electiion | 21:43 |
| fungi | you could send something to the discuss ml with [cyborg] in the subject, and/or make sure it gets mentioned in their weekly meeting(s) | 21:44 |
| fungi | also it doesn't have to be election officials reaching out to the cyborg contributors, if say someone (or multiple someones) on the tc or the cyborg ptl/candidates want to do that outreach | 21:44 |
| fungi | i'm just suggesting raising the profile of this new behavior change in civs for the 18 specific people for whom it matters this time | 21:45 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!