| *** evrardjp has quit IRC | 04:37 | |
| *** evrardjp has joined #openstack-election | 04:37 | |
| tonyb | andymccr: I /win 65 | 04:49 |
|---|---|---|
| tonyb | *sigh* | 04:49 |
| *** lpetrut has joined #openstack-election | 09:56 | |
| evrardjp | how is that patch to governance generated? https://review.opendev.org/#/c/720109/1/reference/members.yaml | 13:56 |
| evrardjp | Is that manual, or do you have a tooling? | 13:56 |
| evrardjp | if it's manual, would you mind if I edit the date of the term, until the TC figures out how we're gonna do things better? | 13:56 |
| evrardjp | if it's automatic tooling, can you show me where it is? | 13:57 |
| fungi | there's a script which does it in the openstack/election, though it had to be worked around this time because it's still not been updated for handling leaderless projects under the newer workflow where we mark them leaderless in governance first | 14:21 |
| fungi | evrardjp: per the readme: tox -e venv update-governance -- --governance-repo ../governance/ | 14:21 |
| fungi | setup.cfg says the update-governance entrypoint calls into https://opendev.org/openstack/election/src/branch/master/openstack_election/cmds/update_governance.py#L107 | 14:23 |
| evrardjp | yeah navigating from the tox should be okay :) | 14:24 |
| evrardjp | but thanks for the detailed link, saves me time! :) | 14:24 |
| evrardjp | but that's just projects, isn't it? | 14:25 |
| evrardjp | That's not the reference/members from governance | 14:25 |
| evrardjp | but if everything is in that repo, grep will help me | 14:26 |
| evrardjp | and it is failing me | 14:26 |
| ianychoi | evrardjp, I just try to understand your question - your question is how to generate the changes on governance repo from the execution on election repo? | 14:31 |
| evrardjp | I am just trying to understand how that patch for updating the TC members was proposed: if it was manual editing of the file, or is there a script handling it. | 14:32 |
| ianychoi | update_governance command updates yaml files on ../governance assuming that governance and election are on the same level directory and the command is executed on election directory level. | 14:33 |
| ianychoi | so the step would be 1) execute update-governance on election repo 2) cd ../governance and 3) git commit & git review on governance repo | 14:34 |
| ianychoi | but not sure whether you would like to understand this step or not.. | 14:34 |
| *** lpetrut has quit IRC | 14:34 | |
| ianychoi | So, I can say the script is currently handling | 14:35 |
| ianychoi | (although my experience is just to update PTL election results, I thought it is similar for TC election results) | 14:36 |
| fungi | evrardjp: oh, yep, sorry, that's in the ptl election section of the readme | 14:39 |
| fungi | ianychoi is right, we don't script the tc results update for governance that i'm aware | 14:39 |
| evrardjp | woot that's the answer I was looking for! So my grep _was_ right! | 14:39 |
| fungi | because it's just updating half a dozen entries in a list in a single rst file | 14:39 |
| evrardjp | correct. | 14:40 |
| ianychoi | fungi, thank u for making it clearer! | 14:40 |
| fungi | so doesn't meet the https://xkcd.com/1205/ rule of thumb | 14:40 |
| evrardjp | It was currently held up on tech details, so I will update the patch that proposed this, if any election official could then +1 it, that would be awesome. I will ping you here for a review ;) | 14:40 |
| evrardjp | fungi: I expected this one ;) | 14:40 |
| ianychoi | evrardjp, as an election official, I will support your update on https://review.opendev.org/#/c/720109/1/reference/members.yaml | 14:41 |
| evrardjp | thanks! | 14:43 |
| evrardjp | sorry for the red-tape there. | 14:43 |
| ianychoi | Thank you for dealing with this - no worries :) | 14:43 |
| evrardjp | ianychoi: https://review.opendev.org/#/c/720109/ should be good to go | 14:48 |
| evrardjp | we'll reword this in governance | 14:48 |
| evrardjp | like tonyb rightfully suggested. | 14:49 |
| evrardjp | Sorry that we bother you with this again. | 14:49 |
| fungi | please don't apologize! | 14:50 |
| fungi | it's all part of holding elections | 14:50 |
| evrardjp | well I feel the need to apologize because it's requiring extra efforts, better spent elsewhere :) | 14:52 |
| fungi | your "thank you" is worth a dozen "i'm sorrys" ;) | 14:56 |
| ianychoi | evrardjp, I also do not need your sorry :) By the way, a question before writing on Gerrit: Would it be better working if you change like "At the next TC first election in 2021"? | 14:56 |
| evrardjp | fungi: haha :) Thank you for doing all of that! | 14:57 |
| evrardjp | fungi: I guess it's also cultural and my personality | 14:57 |
| ianychoi | My understanding now is just that explicitly specifying "March" is not a good idea. I believe election will happen on Fall 2020 and there will be two election in 2021 | 14:58 |
| fungi | "fall" is also ambiguous, because for half the planet that's actually "spring" | 14:58 |
| evrardjp | my goal is to have a "good enough" text so that the change is accepted, https://review.opendev.org/#/c/720477/ going on top | 14:58 |
| ianychoi | Aha | 15:00 |
| evrardjp | so that it clarifies things. We don't need to figure out the perfect wording as of today | 15:00 |
| evrardjp | in fact, if you vote +1, I could merge it, right now! | 15:01 |
| evrardjp | imagine the speed ! | 15:01 |
| * evrardjp still think CI is wonderful | 15:01 | |
| ianychoi | evrardjp, done :) | 15:02 |
| evrardjp | woot! | 15:03 |
| evrardjp | Thanks team! | 15:03 |
| fungi | yep, what's important from an openstack foundation bylaws perspective, as i understand it, is to just make sure that the term of the newly-elected tc members has some stated expiration condition which will be sufficiently flexible | 15:04 |
| ianychoi | Thank you for the effort to for clearer term! | 15:05 |
| ianychoi | (considering the current fluctuating TC duration) | 15:05 |
| *** evrardjp has quit IRC | 16:37 | |
| *** evrardjp has joined #openstack-election | 16:37 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!