Friday, 2018-08-10

fungii'm on the fence since we already seem to mostly have things proposed to the election repo this time, but would like to hear from other tc-members on the matter when they're around00:17
tonybOkay00:17
* tonyb cools his heals00:18
*** dklyle has quit IRC00:32
*** dklyle has joined #openstack-tc00:32
*** mtreinish has quit IRC00:45
*** mtreinish has joined #openstack-tc00:46
*** mriedem has quit IRC00:52
*** mtreinish has quit IRC01:06
*** mtreinish has joined #openstack-tc01:08
*** annabelleB has quit IRC01:15
*** rosmaita has quit IRC01:33
*** ricolin has joined #openstack-tc01:53
openstackgerritTrinh Nguyen proposed openstack/governance master: Self-nominate as Searchlight PTL  https://review.openstack.org/59060102:14
*** e0ne has joined #openstack-tc02:16
*** e0ne has quit IRC02:18
openstackgerritTrinh Nguyen proposed openstack/governance master: Update with results from the Stein PTL election  https://review.openstack.org/58969103:12
openstackgerritTrinh Nguyen proposed openstack/governance master: Self-nominate as Searchlight PTL  https://review.openstack.org/59060103:12
*** ianychoi has joined #openstack-tc03:56
*** jpich has joined #openstack-tc07:02
*** evrardjp has joined #openstack-tc07:06
*** jaosorior has quit IRC07:15
*** e0ne has joined #openstack-tc07:59
*** e0ne has quit IRC08:49
*** e0ne has joined #openstack-tc09:14
*** e0ne has quit IRC09:27
*** cdent has joined #openstack-tc09:31
*** e0ne has joined #openstack-tc09:37
*** jaosorior has joined #openstack-tc09:48
*** tosky has joined #openstack-tc10:19
*** e0ne has quit IRC10:21
*** ricolin has quit IRC10:28
*** tosky has quit IRC10:35
*** tosky has joined #openstack-tc10:36
*** dtantsur|afk is now known as dtantsur11:01
openstackgerritJean-Philippe Evrard proposed openstack/governance master: Reorganise OpenStack-Ansible deliverables  https://review.openstack.org/58944611:39
openstackgerritJean-Philippe Evrard proposed openstack/governance master: Reorganise OpenStack-Ansible deliverables  https://review.openstack.org/58944611:42
openstackgerritJean-Philippe Evrard proposed openstack/governance master: Reorganise OpenStack-Ansible deliverables  https://review.openstack.org/58944611:54
*** cdent has quit IRC11:58
*** cdent has joined #openstack-tc12:01
*** jaosorior has quit IRC12:03
*** mriedem has joined #openstack-tc12:05
*** mriedem has quit IRC12:17
TheJuliafungi: I guess I'm worried that we seemingly desire to add more complexity, processes, and expectations, when I can't actually detect what the value-add would be for all involved. Perhaps I need more coffee though.12:39
fungiTheJulia: agreed, asking the election officials to approve tc appointees after the election seems like extra process to me too12:47
fungiespecially given they don't actually have the authority to approve appointments12:48
TheJuliaI guess the better question I should be asking, in order to better understand, is what is broken/bad/not ideal about the current process and what exactly are they trying to fix12:49
fungii'm not sure there is a current process, which is part of the problem12:51
fungiin the past the election officials just told the tc when there was no candidate for a ptl election, and then the tc took it up with the team in question12:52
fungithis time we've apparently asked volunteers for those seats to amend the election results12:52
cmurphyin some cases we asked them to amend governance directly https://review.openstack.org/58861712:53
cmurphyso we've not been consistent12:53
fungiwhich results in the election officials approving them when it's not within their authority (but they're the only ones who can approve them because they're the ones with approval rights on the election repo)12:53
fungiso this is more a question of how we can do better next time, and whether we should really go ahead with alterations to the election results this time as a one-off or not12:55
TheJuliaI think not, I think the process from the TC standpoint as to who/what/why should be documented clearly, since I'm fairly certain that things like this will happen again.12:56
TheJulia(the not was in response to the second half of your last comment fungi)12:57
cmurphyI don't really think it makes sense to keep altering the election results, after all appointments aren't elected12:57
fungipart of the confusion is probably that in a couple past cycles (ocata and queens) appointments made by the tc during the election period were recorded in the election results, but as part of the change which recorded the entirety of the election12:59
evrardjpfungi: I am not understanding the problem: Is that a problem that we tracked/asked volunteers and amend the results, is the problem the lack of process, is the problem that we are changing all the time?12:59
fungiin this case we have appointments we're making after conclusion of the election, so it's questionable whether we should add them to the election reop12:59
fungirepo12:59
evrardjpwith ^ I understand better13:00
fungievrardjp: yeah, i'm not sure if the request for those ptl appointees to update the election repo was intended to provide retroactive consistency in the election info, or if it means something more13:01
evrardjpfungi: what was different in Pike and Rocky?13:01
evrardjpfungi: ok13:01
TheJuliaI have loaded the page erroniously in the past, when I should have looked at the governance yaml file describing who the PTLs are. I can see people going to the election page to verify who the PTL is, but...it is the wrong place outside of an election window or election process13:01
fungiyeah, and the governance repo is certainly where we record the official decision in such matters13:02
fungithe election results are merely intended as a means of informing the tc of the results of community elections13:02
fungiso that they can be recorded accurately into governance13:02
TheJulia"This page does not account for all current statuses, for the most up to date and current information including appointments, please see <link>."13:04
fungianyway, i'm okay just going ahead and approving those additions this time (with my election official hat on) since we (tc members) asked people to submit them, but would like to think a little about whether it's appropriate going forward13:05
*** rosmaita has joined #openstack-tc13:05
cmurphywe haven't merged any of them yet, we could still abandon those reviews and repropose them against governance and reference the abandoned reviews13:07
persiaAs I am without a TC hat, I'd much more prefer explicit instruction from the TC to approve such changes.  Also, I think of the elections repo has being an artefact of how the elections officials have chosen to pursue delegated activities, rather than being a governance artifact itself.13:08
*** jaypipes is now known as leakypipes13:21
*** dansmith is now known as SteelyDan13:31
openstackgerritAde Lee proposed openstack/governance master: update nick for Ade Lee  https://review.openstack.org/59077213:43
*** hongbin_ has joined #openstack-tc14:03
dhellmannIn the past we had meetings where we could hold votes. Today we need some other way to hold a vote, and the changes to the governance repo serve that purpose. Except that some PTLs are serving again, which means we would need to remove their name and re-add it. I did propose that the first time it came up, and the people around at the time seemed to agree it felt a bit silly.14:05
dhellmannHence updating the election repo with the appointment info.14:06
dhellmannI'm not sure why updating that is an issue, since it's clearly saying there was an appointment.14:06
dhellmannI don't have a strong opinion about what the process should be, except that it needs to include a step where the TC actively confirms the appointment. So if the current process doesn't suit, let's figure out something else.14:08
cdentmaybe the ptl entry in projects.yaml needs  a date apppointed key14:10
cdenta date that is outside the norm is a sign that it was something different and thus is a thing that needs its own commit14:10
cdentthe eleection results all get the same date and same commit14:10
cdentor "date appointed" is perhaps optional14:11
cdentsignalling: not elected14:11
cdenta part of me thinks that a ptl that wasn't elected should not show up in the election repo14:11
cmurphyor could just be appointed: true sort of like we're doing in the election repo14:11
cdentwhere it matters is in projects.yaml14:11
*** e0ne has joined #openstack-tc14:11
cmurphy++14:11
cdentcmurphy: yeah, cuz blame could give the date14:11
smcginnisYeah, they weren't actually part of the election, so that just seems a little odd to me.14:12
smcginnisNot saying it's an issue, just one of those things.14:12
dhellmanndoes someone want to write up a process proposal and send it to the -dev list? or even document it in the governance repo somewhere?14:15
persiadhellmann: I think the main problem with updating the election repo is that process doesn't actually require or enforce any TC blessing.  There is also some resistance based on the existing stance of "don't update the candidate data between elections", but that's something easily overridden by TC direction.14:23
dhellmannok, I guess I can understand both of those things.14:23
dhellmannI still want a volunteer to write up something different so we don't have to guess what to do next time. :-)14:24
persiaAlternately, having a stack of changes to projects.yaml, being the election results (removing info), and appointments (restoring) is entirely restricted to TC.14:24
dhellmannusing a stack of changes this time around has proven to be a bit of a pain, because an inexperience person rebased the one setting the election results which reset the approval date if we follow our strict rules14:24
dhellmannit at least wiped out the votes14:24
dhellmannI'm reluctant to say we want a tc member to make whatever patches are involved, but I would like to try to avoid that situation in the future14:25
dhellmannso perhaps we want to shorten the amount of time we wait to approve that initial set of election rules (that would be a house rules change) to avoid the problem14:26
dhellmannthen other volunteers could nominate themselves after that one is approved14:26
persiaI may be out of date, but last I looked, the election results change also didn't expressly reflect "None" in cases where there was no PTL as a result of the election.14:27
dhellmannperhaps it should?14:28
dhellmannusually we just have 1-2 of these and it's not such a pita14:28
persiaThat it perhaps should was discussed ~14 hours ago, but more input from more of the TC was desired before updating the change (especially as that wipes all the votes, etc.)14:29
persiaThere's also the current situation where some folk were instructed to update the elections repo.14:29
persiaI think the summary is that we need one true way going forward, and we may end up with some messiness or cleanup this time, but until we have the way forward, folk are reluctant to set precedent.14:30
dhellmannI am asking for a volunteer to propose *something*. I don't have time to do it today, given the release work.14:31
dhellmannIf we get all of this down in one place we can poke holes and do the usual revision, but I think we've done enough IRC chatting about it and need a more concrete proposal somewhere.14:32
* persia offers to propose *someting* in ~8 hours, and will happily collaborate or defer to someone else if they get to it first14:32
dhellmannpersia : excellent, thank you14:32
cdentdhellmann: I can propose the idea I made up above..14:32
cdentor persia feel free14:32
dhellmanncdent : also good, yes, thank you :-)14:32
dhellmannlet's do it as changes to the house rules section of the governance document14:33
cdentk14:33
dhellmannif we decide it should eventually live elsewhere we can deal with that once we agree on what it is we're moving14:33
persiacdent: I have several things in the next few hours: if your evening is sooner, feel free to do it in advance of me.14:33
cdenti'll do it pretty much now14:33
cdentand then if we (or you) don't like it, we can make another or tweak it14:33
persiaExcellent :)14:34
dhellmannthank you both14:34
fungidhellmann: to me, from an election official standpoint, it's unclear what rules we follow for approval of those changes. are the election officials gauging when a sufficient number of tc members have added a code-review +1?14:35
dhellmannfungi : yeah, that's a fair point. I didn't think that through.14:36
fungiand how many do we need? do we consult the tc member roster to sort out which +1s are from tc members and which aren't?14:37
fungithat sort of thing14:37
*** e0ne has quit IRC14:39
*** annabelleB has joined #openstack-tc14:51
*** tosky has quit IRC15:03
*** e0ne has joined #openstack-tc15:03
*** e0ne has quit IRC15:10
openstackgerritChris Dent proposed openstack/governance master: Add a house rule about how to signal appointed PTLs  https://review.openstack.org/59079015:13
cdentdhellmann, cmurphy, persia, smcginnis ^15:19
cdentfairly short and sweet15:19
smcginniscdent: Thank15:21
smcginniss15:22
cdentmade an email too15:22
cmurphyi like it15:26
openstackgerritChandan Kumar proposed openstack/governance master: Move refstack-client, refstack and python-tempestconf to interop WG  https://review.openstack.org/59017915:29
*** mriedem has joined #openstack-tc15:30
*** ricolin has joined #openstack-tc15:43
*** mriedem has quit IRC16:27
*** jpich has quit IRC16:35
*** annabelleB has quit IRC16:38
*** purplerbot has quit IRC16:38
*** purplerbot has joined #openstack-tc16:38
*** diablo_rojo has joined #openstack-tc16:41
*** annabelleB has joined #openstack-tc16:43
*** dtantsur is now known as dtantsur|afk17:01
*** e0ne has joined #openstack-tc17:11
*** purplerbot has quit IRC17:32
*** purplerbot has joined #openstack-tc17:40
*** purplerbot has quit IRC17:43
*** purplerbot has joined #openstack-tc17:48
*** ricolin has quit IRC17:48
*** purplerbot has quit IRC17:54
*** purplerbot has joined #openstack-tc17:54
*** purplerbot has quit IRC17:55
*** purplerbot has joined #openstack-tc17:56
*** ianychoi has quit IRC18:10
*** ianychoi has joined #openstack-tc18:11
openstackgerritMerged openstack/governance master: update nick for Ade Lee  https://review.openstack.org/59077218:15
openstackgerritMerged openstack/governance master: Update PTL for OpenStack RPM Packaging  https://review.openstack.org/58861718:17
*** zaneb has joined #openstack-tc18:39
*** diablo_rojo has quit IRC18:50
*** annabelleB has quit IRC18:52
*** diablo_rojo has joined #openstack-tc18:54
*** annabelleB has joined #openstack-tc18:59
*** annabelleB has quit IRC19:03
*** diablo_rojo has quit IRC19:28
*** annabelleB has joined #openstack-tc19:31
*** e0ne has quit IRC19:51
*** diablo_rojo has joined #openstack-tc20:14
*** cdent has quit IRC20:17
*** annabelleB has quit IRC20:48
*** annabelleB has joined #openstack-tc20:51
*** diablo_rojo has quit IRC21:02
fungiwhee! http://www.joinfu.com/2018/08/project-mulligan-openstack-redo/21:25
fungisounds less like openstack v2 and more like nova v221:37
*** annabelleB has quit IRC21:58
*** annabelleB has joined #openstack-tc22:01
fungiwhen he says "projects that can stand alone and22:04
fungiprovide a well-defined, small scope of service" i read that as "projects that don't need nova" which is a decidedly nova-centric view22:04
*** annabelleB has quit IRC22:12
*** leakypipes has quit IRC22:31
jrollI was wondering who would post that here first :)22:55
*** rosmaita has quit IRC22:59
*** hongbin_ has quit IRC23:00

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!