Thursday, 2019-08-22

*** jamesmcarthur has joined #openstack-tc00:05
*** markvoelker has joined #openstack-tc00:25
*** jamesmcarthur has quit IRC00:26
*** markvoelker has quit IRC00:30
*** jamesmcarthur has joined #openstack-tc00:38
*** lbragstad has quit IRC00:55
*** hogepodge has quit IRC00:55
*** diablo_rojo_phon has quit IRC00:55
*** ChanServ has quit IRC00:55
*** mtreinish has quit IRC00:55
*** gagehugo has quit IRC00:56
*** bodgix has quit IRC00:56
*** eandersson has quit IRC00:56
*** evrardjp has quit IRC00:56
*** weshay has quit IRC00:56
*** smcginnis has quit IRC00:56
*** camelCaser has quit IRC00:56
*** stephenfin has quit IRC00:56
*** knikolla has quit IRC00:56
*** notmyname has quit IRC00:56
*** sapd1 has quit IRC00:56
*** dansmith has quit IRC00:56
*** tbarron has quit IRC00:56
*** irclogbot_1 has quit IRC00:56
*** openstackgerrit has quit IRC00:56
*** tonyb has quit IRC00:56
*** scas has quit IRC00:56
*** johnsom has quit IRC00:56
*** tjgresha has quit IRC00:56
*** dirk has quit IRC00:56
*** purplerbot has quit IRC00:56
*** ianw has quit IRC00:56
*** dtroyer has quit IRC00:56
*** tobberydberg has quit IRC00:56
*** jbryce has quit IRC00:56
*** aprice has quit IRC00:56
*** kmalloc has quit IRC00:56
*** tiffanie has quit IRC00:56
*** cmurphy has quit IRC00:56
*** logan- has quit IRC00:56
*** zaneb has quit IRC00:56
*** persia has quit IRC00:56
*** fungi has quit IRC00:56
*** whoami-rajat has quit IRC00:56
*** jroll has quit IRC00:56
*** ildikov has quit IRC00:56
*** tonyb[m] has quit IRC00:56
*** jrosser has quit IRC00:56
*** lxkong has quit IRC00:56
*** mugsie has quit IRC00:56
*** andreaf has quit IRC00:56
*** masayukig has quit IRC00:56
*** gmann has quit IRC00:56
*** ttx has quit IRC00:56
*** asettle has quit IRC00:56
*** corvus has quit IRC00:56
*** amotoki has quit IRC00:56
*** csatari has quit IRC00:56
*** coreycb has quit IRC00:56
*** dhellmann has quit IRC00:56
*** mnaser has quit IRC00:56
*** TheJulia has quit IRC00:56
*** wxy-xiyuan has quit IRC00:56
*** melwitt has quit IRC00:56
*** aspiers has quit IRC00:56
*** mwhahaha has quit IRC00:56
*** mgagne has quit IRC00:56
*** EmilienM has quit IRC00:56
*** bauzas has quit IRC00:56
*** Jeffrey4l has quit IRC00:56
*** dtruong has quit IRC00:56
*** dklyle has quit IRC00:56
*** adriant has quit IRC00:56
*** redrobot has quit IRC00:56
*** dmellado has quit IRC00:56
*** gouthamr has quit IRC00:56
*** spotz has quit IRC00:56
*** spotz has joined #openstack-tc01:14
*** gouthamr has joined #openstack-tc01:14
*** dmellado has joined #openstack-tc01:14
*** redrobot has joined #openstack-tc01:14
*** adriant has joined #openstack-tc01:14
*** dklyle has joined #openstack-tc01:14
*** dtruong has joined #openstack-tc01:14
*** Jeffrey4l has joined #openstack-tc01:14
*** weshay has joined #openstack-tc01:14
*** evrardjp has joined #openstack-tc01:14
*** eandersson has joined #openstack-tc01:14
*** bodgix has joined #openstack-tc01:14
*** gagehugo has joined #openstack-tc01:14
*** scas has joined #openstack-tc01:14
*** tonyb has joined #openstack-tc01:14
*** openstackgerrit has joined #openstack-tc01:14
*** diablo_rojo_phon has joined #openstack-tc01:14
*** hogepodge has joined #openstack-tc01:14
*** lbragstad has joined #openstack-tc01:14
*** bauzas has joined #openstack-tc01:14
*** EmilienM has joined #openstack-tc01:14
*** mgagne has joined #openstack-tc01:14
*** tbarron has joined #openstack-tc01:14
*** dansmith has joined #openstack-tc01:14
*** sapd1 has joined #openstack-tc01:14
*** notmyname has joined #openstack-tc01:14
*** knikolla has joined #openstack-tc01:14
*** stephenfin has joined #openstack-tc01:14
*** camelCaser has joined #openstack-tc01:14
*** smcginnis has joined #openstack-tc01:14
*** mtreinish has joined #openstack-tc01:14
*** mwhahaha has joined #openstack-tc01:14
*** aspiers has joined #openstack-tc01:14
*** melwitt has joined #openstack-tc01:14
*** wxy-xiyuan has joined #openstack-tc01:14
*** TheJulia has joined #openstack-tc01:14
*** mnaser has joined #openstack-tc01:14
*** dhellmann has joined #openstack-tc01:14
*** coreycb has joined #openstack-tc01:14
*** csatari has joined #openstack-tc01:14
*** ChanServ has joined #openstack-tc01:14
*** card.freenode.net sets mode: +o ChanServ01:14
*** johnsom has joined #openstack-tc01:14
*** purplerbot has joined #openstack-tc01:14
*** ianw has joined #openstack-tc01:14
*** dtroyer has joined #openstack-tc01:14
*** tobberydberg has joined #openstack-tc01:14
*** asettle has joined #openstack-tc01:15
*** ttx has joined #openstack-tc01:15
*** corvus has joined #openstack-tc01:15
*** amotoki has joined #openstack-tc01:15
*** jamesmcarthur has quit IRC01:19
*** zaneb has joined #openstack-tc01:21
*** mugsie has joined #openstack-tc01:21
*** persia has joined #openstack-tc01:22
*** gmann has joined #openstack-tc01:23
*** irclogbot_1 has joined #openstack-tc01:25
*** gmann has quit IRC01:27
*** gmann has joined #openstack-tc01:28
*** fungi has joined #openstack-tc01:37
*** cmurphy has joined #openstack-tc01:57
*** morgan has joined #openstack-tc02:02
*** jroll has joined #openstack-tc02:03
*** ianychoi has quit IRC02:19
*** ianychoi has joined #openstack-tc02:19
*** ricolin has joined #openstack-tc02:21
*** jamesmcarthur has joined #openstack-tc02:28
*** markvoelker has joined #openstack-tc02:32
*** zhipeng has joined #openstack-tc02:50
*** jamesmcarthur has quit IRC02:52
*** jamesmcarthur has joined #openstack-tc02:54
*** markvoelker has quit IRC03:20
*** markvoelker has joined #openstack-tc03:21
*** markvoelker has quit IRC03:25
*** markvoelker has joined #openstack-tc03:46
*** markvoelker has quit IRC03:56
*** markvoelker has joined #openstack-tc03:57
*** markvoelker has quit IRC03:57
*** markvoelker has joined #openstack-tc03:58
*** markvoelker has quit IRC04:08
*** markvoelker has joined #openstack-tc04:09
*** markvoelker has quit IRC04:14
*** jamesmcarthur has quit IRC04:26
*** jaosorior has joined #openstack-tc05:29
*** ianychoi has quit IRC06:15
*** ianychoi has joined #openstack-tc06:19
*** ianychoi has quit IRC06:28
*** ianychoi has joined #openstack-tc06:29
*** ianychoi has quit IRC06:52
*** ianychoi has joined #openstack-tc06:54
*** dirk1 has joined #openstack-tc07:27
*** dirk1 is now known as dirk07:30
*** e0ne has joined #openstack-tc07:37
*** ianychoi has quit IRC07:52
*** ianychoi has joined #openstack-tc07:54
*** lpetrut has joined #openstack-tc08:24
*** markvoelker has joined #openstack-tc08:37
*** tdasilva has joined #openstack-tc08:38
*** markvoelker has quit IRC08:45
openstackgerritThierry Carrez proposed openstack/governance master: Subsequent fixes in goal selection process changes  https://review.opendev.org/67793808:47
*** tdasilva_ has joined #openstack-tc08:51
*** tdasilva has quit IRC08:52
*** tdasilva_ is now known as tdasilva08:52
*** tdasilva_ has joined #openstack-tc08:55
*** tdasilva_ has quit IRC08:55
*** tdasilva has quit IRC08:58
*** tdasilva has joined #openstack-tc09:03
*** e0ne has quit IRC09:42
*** e0ne has joined #openstack-tc09:56
openstackgerritThierry Carrez proposed openstack/governance master: Subsequent fixes in goal selection process changes  https://review.opendev.org/67793810:30
*** markvoelker has joined #openstack-tc10:40
*** markvoelker has quit IRC10:45
*** markvoelker has joined #openstack-tc11:10
*** markvoelker has quit IRC11:15
*** markvoelker has joined #openstack-tc11:40
*** markvoelker has quit IRC11:45
*** jamesmcarthur has joined #openstack-tc11:52
*** markvoelker has joined #openstack-tc11:54
*** jamesmcarthur has quit IRC12:04
*** jamesmcarthur has joined #openstack-tc12:07
*** ianychoi has quit IRC12:07
*** ianychoi has joined #openstack-tc12:09
*** adriant has quit IRC12:26
*** ianychoi has quit IRC12:27
*** adriant has joined #openstack-tc12:27
*** ianychoi has joined #openstack-tc12:28
*** jamesmcarthur has quit IRC12:30
*** jamesmcarthur has joined #openstack-tc12:48
mnaseras a contributor, i'd like to know what i can do about a project that pretty much doesn't care about doing reviews13:02
mnaseri see other patches pushed up and merged (by the cores amongst them), i see patches getting +2s from cores to folks in their org but the rest just sits idle, even trivial stuff, till it hits a merge conflict13:02
mnaseri have 2 month old patches i'm bumping and pushing, with many non cores giving +1s and cores just ignoring them13:03
* mnaser is grown tired as a contributor and thinks this is bad13:03
*** jamesmcarthur has quit IRC13:04
*** jamesmcarthur has joined #openstack-tc13:04
fungii expect we have plenty of proposed infra changes which have gone unacknowledged for longer than that13:06
fungii don't feel good about it, but i also don't have a great answer13:06
fungiwhen there are more people proposing things than reviewing them, that has a tendency to happen. obviously adding more reviewers becomes a priority, or dividing the responsibilities into additional teams if the team size has exceeded their ability to effectively coordinate with each other on reviewing13:08
mnaserfungi: but the team is just 2 cores and they have refused to add more people for some reason13:11
fungiin that case, i wonder whether there are other dynamics at work13:12
dhellmannis this one of our teams?13:14
asettlemnaser, that seems odd.13:14
mnaserthe magnum team is 5 cores, 3 are inactive, two are only active13:15
jrolldid they give *any* reason for not adding more cores?13:15
mnaseri've asked that they add new people, gave them a list of some that seem to be active in reviews, "its a good idea" and they didn't do it13:15
mnaseri've been going on and on about this for a while, i still have trivial patches sitting for weeks/months13:15
mnaserand here's the thing that really pisses me off13:16
mnaserthe default networking driver is flannel in magnum13:17
mnaseri tried to make the conformance tests work forever again (in flannel) and all my patches were pretty much ignored13:17
mnaserwe lost conformance, and then when i complained last time, they "somehow" magically got it again13:17
mnaserthe ptl ran it against a non-default configuration (using calico) -- the *NON DEFUALT* networking driver https://raw.githubusercontent.com/cncf/k8s-conformance/master/v1.13/openstack-magnum/e2e.log13:18
mnaserbut also happens to be the one that the employer of the ptl runs by default13:18
mnaserwhich means all the current ptl has cared about is making sure their use cases arent broken, and the "default" network method is not even tested13:18
mnaserthe worst part is that it wasn't even documented that they used another network driver (not flannel) in the conformance instructions: https://github.com/cncf/k8s-conformance/tree/master/v1.13/openstack-magnum13:19
dhellmannI don't see flwang here in channel13:19
dhellmannI expect that's related to timezones13:19
mnaser(warning, big file -- https://raw.githubusercontent.com/cncf/k8s-conformance/master/v1.13/openstack-magnum/e2e.log -- but you see the calico daemonset go up in the logs there)13:20
dhellmannif the magnum team isn't meeting the requirements set out for being part of the list of official project teams, then it's up to the TC to address that13:20
dhellmannI don't know that maintaining k8s conformance fits that, really, but the team management and reviewer list issue does13:21
*** mriedem has joined #openstack-tc13:21
dhellmannthe former seems like a symptom of the latter anyway13:21
mnaserto me it feels like "openstack first" is not being respected, it's more like "what works for me first"13:21
mnaserwe all have to maintain and deal with stuff we don't run in openstack, but its open source and give-and-take13:22
dhellmannyeah, it seems like if there was more input from more reviewers that would naturally happen13:22
dhellmannwe're about to have an election, so it seems like putting together a list of proposed ways to deal with that should happen soon so we can let the team know13:24
fungiright, the two ways of officially dealing with a problem like this are 1. get someone else to run for ptl against the current ptl, or 2. escalate the issue to the tc to decide whether the project remains part of openstack13:25
mnasercan you run as a ptl if you dont have a single commit in the project13:25
funginot the way our current project governance is designed13:25
fungioptionally, someone can propose a fork of a project with a new team volunteering to maintain it, and the tc can both accept the new project and declare the old project no longer part of openstack, i guess13:26
asettleThat seems... controversial. Has that happened before?13:26
mnaserhttps://www.stackalytics.com/?module=magnum-group&release=train&metric=commits13:27
fungiasettle: not really, no. but no two problems are alike and so their solutions usually aren't either13:27
mnaseri've managed to get 3 in, so i guess in that case13:27
dhellmannanother way to deal with it would be to add people to the review team ourselves13:27
mugsieasettle: nearly (but it was the ptl of the project being forked that proposed the fork)13:27
mnasertbh i suggested two candidates who were good (imho) and hogepodge seems to put some reviews lately too (i dont wnat to sign him up for work though, but he'd be excellent given his involvement inside k8s side of things)13:29
asettlefungi, good point13:29
*** bnemec has joined #openstack-tc13:29
mugsiemnaser: me and evrardjp are the TC liasons, we could reach out initially (if you think that would help)13:29
asettlemnaser, I admittedly just put up a trivial patch myself. Now I'm like D:13:29
asettlemugsie, no harm in trying? That's what that function is designed to do13:29
dhellmannmugsie : I think telling the team they're under scrutiny is definitely called for13:30
mugsieOK, I will send an email to the PTL today13:30
mnaser*personally* i've hit a point where i'm writing a k8s deployment library and then use magnum's "plugin" system to use magnum (but with our own deployment tooling) to keep the api still there13:30
mnaserwhat sucks to me is that the 'new user' experience sucks and the default configs don't work, so we're going to be in a "openstack sucks" world if this continues imho13:30
mnaseralso, this isn't the first time we reach out to them, i think fungi may have done that in the past?13:30
mugsieyeah, that defintitely sucks13:31
mnaserfyi someone reached out13:31
fungiricolin did13:31
dhellmann"reaching out" is different from saying "we're about to fix this if you don't"13:31
mnaserhttp://lists.openstack.org/pipermail/openstack-discuss/2019-July/008137.html13:32
fungialso hogepodge i think13:32
mnaser"everything is ok"13:32
dhellmannyes, then we need to explain that everything is not ok13:32
fungii merely replied to their status update with a question about the kubernetes conformance situation13:32
asettleOut of curiosity, is the other core also based in New Zealand?13:33
mnaserits also still being deployed on an eol version of fedora (27) *and* fedora atomic is entirely disappearing13:33
asettleslash same company13:33
mnaserno, they're at cern so utc i guess13:33
asettleJust Feilong then?13:34
mnaserand 3 other inactive cores13:34
asettleHuh okay13:34
mnaserno reviews for months13:34
asettleI was just pondering if they were keeping it "in the family" so to speak13:34
asettleBut nope13:34
hogepodgehi, I'm awake13:34
mnaserto me when i see https://review.opendev.org/#/q/project:openstack/magnum+is:open and look at the few little reviews done13:34
mnaseri see mine sit for months13:34
mnaserand then i see https://review.opendev.org/#/c/676690/ get a +2 within a few hours13:34
mnaserfrom a 'fellow co-worker'13:35
asettleHoly shit13:35
hogepodgeI ran through a whole host of patches about a month ago to get an understanding of what was happening and try to prime myself for more contributions.13:35
asettleThis goes back as far as Jan 201713:35
fungidhellmann: i think the way we've established our governance places responsibility for things like choosing reviewers on the ptl. if the tc is going to make an end-run around a ptl's responsibilities then it is probably necessary to remove/replace the ptl (which is probably the same as removing/replacing the project itself)13:35
mnaseron a change that doesnt even have unit tests, granted, it's trivial, but c'mon13:35
dhellmannfungi : I could go along with that interpretation, if we had another PTL to put in place.13:35
fungiif the tc overrides a ptl's decisions, then it's basically already not recognizing them as ptl13:36
mnaserto go to an example how much reviews are not being looked at, the ptl has submitted patches that does the same fixes that i've done but have gone unreviewed lol13:36
mnaseri.e. in https://review.opendev.org/#/c/677581/ sitepackages is removed, which is exactly what i did in https://review.opendev.org/#/c/674474/ .. 3 weeks ago13:37
mnaser(and still is in the first 25 unmerged patches, so its not like its thrown deep in the trenches)13:37
* mnaser is just trying to give examples so if i'm being over the top, please call me out13:37
mugsiewell, one is a bigger change, so I can understand why it is included there13:38
mugsiebut yours is so small, it should have been merged quicker13:39
*** lbragstad has left #openstack-tc13:39
fungiat any rate, i think bringing all this up on the mailing list is a good idea, even if it does seem confrontational, better to have it in the open than in the relative secret of an irc channel with only 74 people present13:40
mugsie(I am assuming https://review.opendev.org/#/c/677581/6 is only a test, and will be updated to not break the PTI)13:40
fungibut also, as was pointed out, elections are coming up, so if it can wait a couple more weeks that's an opportunity for a change in leadership without needing to take exceptional steps13:40
hogepodgeasettle: yes, 184 open requests going back to January 201713:41
mnaserif you are elected as a ptl but you're not a core, i assume it would be perfectly ok to just be added into the core team?13:41
jrollyes13:42
jrollthere's precedent for it (trove)13:42
mugsiewell, core team servers at the PTLs discresson13:42
fungiif you are elected ptl you can replace the entire core review team13:42
mugsieserves*13:42
fungianyway, i'd much rather see energy go into campaigning to establish different leadership following normal process than oust a ptl a few weeks before the end of their term13:43
hogepodgefungi: +1 to that, as someone who once woke up to an angry IRC thread it doesn't feel good, but I also understand mnaser's frustrations. This conversation is also on the record, and can be referenced.13:43
mnaseragreed13:43
mnasergiven that i really care about magnum, i may run for ptl and try to improve all that situation then13:43
fungiyes, it's a discussion which is public record, but much harder for someone who isn't around to respond to and participate in13:44
ricolinIn this case, I think it's also worth to encourage people doing more review and become a potential core candidate. Do see some possible candidates which we can encourage PTL to reach out13:44
ricolinhttps://www.stackalytics.com/report/contribution/magnum-group/18013:44
mugsiericolin: as mnaser said, that has been tried, and the team did not do anything with the names13:44
fungiricolin: i agree, but mnaser said he did that13:44
fungi(months ago even)13:44
mnaseri sent a personal email which ill gladly forward, with 2 names that i thought might be good13:45
mnaseri got a "good idea" and no action13:45
ricolinmugsie, fungi it's alway nice to remind ptl again and again, during we try to find another solution here:)13:45
zanebmugsie: maybe in your email point out bnemec's PTL tips and tricks etherpad from the summit? it sounds like they could benefit from some tooling like e.g. a gerrit dashboard to help keep on top of reviews and not duplicate fixes13:46
fungiabsolutely. we should remind them through the mailing list13:46
fungiremind them that adding more reviewers is a "good idea" that is13:46
fungiit's already been observed that providing this feedback in private isn't having an effect, and we shouldn't be hiding our concerns from public view anyway13:47
fungiwe are *open* stack after all13:47
*** altlogbot_3 has joined #openstack-tc13:47
ricolinfungi, +1 on that13:47
*** altlogbot_3 has quit IRC13:48
*** jamesmcarthur has quit IRC13:52
*** altlogbot_1 has joined #openstack-tc13:52
asettlemugsie, -I transferred ben's etherpad to the PTL document we have in governance :) that might be more "official"13:54
asettlehttps://docs.openstack.org/project-team-guide/ptl.html13:54
asettlehttps://docs.openstack.org/project-team-guide/ptl.html#tips-and-tricks <- specifically13:54
*** jamesmcarthur has joined #openstack-tc13:56
mugsieasettle: ty14:00
*** jamesmcarthur has quit IRC14:02
*** spsurya has joined #openstack-tc14:10
zanebasettle: you are awesome14:18
*** jamesmcarthur has joined #openstack-tc14:33
asettlezaneb, :D :D14:37
*** jamesmcarthur has quit IRC14:40
jrollwas going to mention this during office hours, but I suspect that will be all naming process discussion, so dumping it now: re large scale sig, verizon media would love to participate, but probably can't contribute any resources doing lots of work until early/mid next year :/14:43
jrolltoo many spoons, not enough people14:43
jrollmnaser: ttx: ^ since you kickstarted that discussion14:44
mnaserthat's cool14:44
*** jaosorior has quit IRC14:44
mnaserpersonally i'm happy to hear people say "i dont have time right now"14:44
mnasermeans interest is there and they're just too busy, which is totally cool, rather have that than signing up but unable to keep up D:14:45
jrollI wish for irony's sake, that the reason was that we were too busy fighting scaling issues :P14:45
jrollyep14:45
* jroll is a realist14:45
mnaserspeaking of naming14:45
mnaseranother cool idea is uh based after chemical elements table14:46
mnaseri think thats how ODL does it14:46
mnaser"The naming convention for each OpenDaylight release follows the atomic number of elements in the periodic table, per the release calendar below."14:47
mnaserthat would give us ~100 release names :P14:47
jrollhm, can we follow ICAO just for the W release?14:48
mugsiemnaser: that is how Azure does it as well14:48
jrollthough I think whatever cycle dublin was should have been OpenStack Whisky, so maybe it's too late14:48
mugsiejroll: only if the summit is in Dublin or Edinburagh14:48
jroll++14:48
mnasermugsie: i assume that happens internally14:48
jrollsnowpocalypse cycle was definitely heavily influenced by whisky14:48
mnasercause i tried to google a few combos of azure + $word14:48
asettleSnowpenstack gives me flashbacks14:49
mugsiewe have some internal names, but they are public as well14:49
* asettle makes side eyes at mugsie 14:49
* mugsie plays innocent14:49
jrollI almost feel like we need a condorcet poll for these options, heh14:55
asettle>.>14:56
dhellmannmugsie , jroll : they make some good whisky in kentucky, too14:59
dhellmannalso japan :-)14:59
*** lbragstad has joined #openstack-tc15:00
mnaserit's office hours15:00
lbragstado/15:00
ricolino/15:00
jrolldhellmann: they only make whiskey in kentucky :P15:01
jrollbut yes, would support a louisville summit for W :)15:01
jroll\o15:01
ttxjroll: yes "not right now" is a good answer15:01
asettle\o/15:02
fungijroll: irony would be if we needed to come up with a process for naming the available options ;)15:02
mnaserfungi: do you happen to know when the next rename is schedules15:02
mnaserscheduled15:02
dhellmannfungi , diablo_rojo_phon : where do we stand on starting the election process?15:02
ttxtc-members: please reply to http://lists.openstack.org/pipermail/openstack-discuss/2019-August/008649.html if you are interested in helping forum topic suggestions15:02
ttxWe need two volunteers, ideally people not comint for reelection and not Foundation staff15:03
fungimnaser: usually we discuss scheduling project rename outages in the weekly infra meeting to figure out when folks will be available to perform the maintenance15:03
ttxThat leaves asettle mugsie jroll mnaser ricolin zaneb15:04
jrollI thought I already volunteered, guess I'll reply to the new thread15:04
ttxISTR some of you volunteered already, so just reply to that thread saying so :)15:04
ricolinttx I recall that I said I will do it during last meeting:)15:04
mnaseri believe mugsie was a maybe too :)15:04
fungidhellmann: my plan for today is to mock up the pre-nomination-period announcement in an etherpad today, get some input from other election officials and send it out by my evening15:04
asettlettx, dang. I'm not going. But I suppose I can help? From afar?15:04
jrollyou can!15:04
asettleUgh15:05
mnaserasettle: you dont have to be there to help :)15:05
asettleHahahha15:05
jrollI'm not going either, but am helping with this15:05
asettleokay, I'll team up with jroll15:05
asettleBEST FRANDS 4 EVA15:05
mnaserfungi: sorry, just asked because https://review.opendev.org/#/c/669306/ has sat around for a little while15:05
ttxwe just need two tho :)15:05
fungidhellmann: at this point we're just needing to remind folks that nominations start next week15:05
jroll\o/15:05
asettlettx, am I the second or am I the third?15:05
ttxI saw jroll and ricolin's hands up before yours15:05
dhellmannfungi : ok, I'll watch for that email then, thanks15:06
jrollasettle: https://i.pinimg.com/originals/24/ae/51/24ae51a74dc129549d1c2b69b6415c1f.jpg15:06
asettlettx, coolio15:06
asettleConsider me a back up dancer than15:06
mnaserfirst two to reply to mailing list win it :)15:06
ttxyes that is really what decides it, not me15:06
fungimnaser: yeah, clarkb was expecting to need to batch up more renames after the opendev migration, but turns out there weren't many which didn't get taken care of in the first followup batch, so we just need to go ahead and do a single rename i guess15:06
asettlejroll, YES https://media1.giphy.com/media/KZfdN1ZrGf5FOZsFTO/giphy.gif15:06
ttxOr a mud fight15:06
mnaserfungi: great, thanks! :>15:06
asettlejroll, ricolin - responded. But I'm happy if either of you would prefer to do it15:08
ttxfungi: any idea when the next rename window will be ? We need kayobe in to include it in Train release process15:08
ttxand it's difficult to process as long as it's still at x/kayobe15:08
ricolinasettle, go ahead, I just like to make sure it's covered by any of us. :)15:09
fungittx: usually we discuss scheduling project rename outages in the weekly infra meeting to figure out when folks will be available to perform the maintenance15:09
ttxok, so none planned at the moment? I can file a formal request during next week meeting15:10
*** lbragstad has quit IRC15:10
evrardjpwow quite a bit to catch up15:10
fungittx: yeah, if we get renames added as an item on the agenda by monday we'll remember to talk about it in the meeting15:11
fungihttps://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting15:11
*** lbragstad has joined #openstack-tc15:11
ttxok, let me add that15:12
fungiit looks like kayobe is several repos, so at present count we're up to 415:12
fungi4 requested repo renames that is15:12
ttxfungi: I'll try to remember to attend -- if not you can explain as the RelMgt team's infra liaison15:14
fungiabsolutely15:16
mnaserhttps://review.opendev.org/#/c/675788/ i'm inclined to abandon this change given that it seems no one is supporting this option15:17
mugsiemnaser: I would wait for this whole thing to work out, then mass abandon the unused ones15:18
jrollI think it's worth leaving them all until we agree on one15:18
jrollyeah15:18
mnaserfair enough :>15:18
fungiwell, i was previously +1 on it but it's been rebased since i last voted15:18
jrollit's still early, most of the community probably hasn't even read them all yet15:18
mnaserregardless, i'm pretty happy about the fact that people are speaking up :)15:19
jroll++15:19
mugsieand it could take a few days to get everyone who wants to to join in15:19
mugsielife / work and all that15:19
asettleTotally15:19
mnaserttx: just +w https://review.opendev.org/#/c/667932/4 -- thanks for your work on this :)15:20
ttxRe: naming I think two early decisions need to be made, before deciding on one option15:20
ttx(1) do we update the process doc to match the current process, before dumping it15:20
ttx(2) are we looking for a V-Z solution or a solution that can/should survive post-Z15:21
ttxPersonally I'd rather choose now for post-Z and avoid this discussion again15:21
asettlettx, in my discussion with corvus yesterday. I suggested that this current topic is to solve the problem for V-Z, allowing for discussion for post Z to appear.15:21
asettleThere are suggestions to abandon the alphabet now and I think that's goin to result in an incredibly confused user base15:22
asettleAnd we need to seriously be considering them before our own squabbles15:22
mugsieI think 1 - yes. update the doc to reflect the current reality15:22
asettleIMHO, finishing Z is important. This conversation can generate further discussion. We don't have to have it "again" per say15:22
zanebIMHO we don't need to wait for the outcome of this discussion before we merge the fixes to the current process that bring it in line with out actual practice15:23
mugsie2 - lets worry about V-Z first,  then post Z.15:23
asettlezaneb agreed15:23
jrollzaneb: +1, we should get your changes shipped15:23
ttxOK. I'm tempted by ICAO names, if we are only solving for V-Z15:23
zanebafter that we have two more issues: do we change before Z, and what do we change to after Z15:23
*** lbragstad has quit IRC15:23
ttxIf we are looking for a V-postZ solution, then I like karge cities15:23
mnaserpersonally i think large cities makes more sense15:24
asettleThat is the best one to set us up for post Z15:24
mnaserbut karge ones are ok15:24
*** lbragstad has joined #openstack-tc15:24
mnaseri guess15:24
mnaser:>15:24
ttxkarge cities are nice15:24
zanebpersonally I don't think that the process is so broken that it needs to change before Z15:24
asettleThey are15:24
mugsiezaneb: ++15:24
corvuszaneb: we agree on that15:24
asettleI agree also.15:24
zanebbut I think this is down to a difference in governing philosophy15:24
ttxHmm, not sure... V-Z is likely to trigger tension again, due to lack of lots of candidates15:25
ttxwhich means more exceptions15:25
corvusoh no15:25
corvusi misread zaneb's statement15:25
ttxwhich means more subjectivity15:25
corvusi very much think that the process is so broken that it needs to change before Z15:25
asettlecorvus, okay cool cause we all just did a bit of this: https://media0.giphy.com/media/Ow59c0pwTPruU/source.gif15:25
mnaserim torn.  i've seen other communities decide release names in advance for the next few cycles which makes life easy15:25
ttxcorvus: I agree with you15:25
mnaser*but* that also means it puts us in a weird spot that you are a z contributor and you never got to pick the name15:26
zanebfor a long time the TC operated on the principle that all decisions should be 100% objective, and that any subjective content is bad and must be eliminated by hashing out all of the edge cases and documenting them beforehand so there can be no argument15:26
ttxI feel like if we don't change before Z, then we are back to "easy" letters again and then we can have the discussion when we hit K15:26
asettlemnaser, I think that point is moot at this stage. Also, I'm sorry, if you're upset that you didn't get to pick a release name I'm not entirely convinced your priorities are right15:26
corvusi strongly disagree that zaneb's changes actually bring the prcoss into alignment with practice.  but if we can get on board with finding a way to change it before z, then we can set that aside.15:26
asettleIt's a _release name_ not your first born15:26
fungimnaser: well, also sticking with the current set of requirements makes it very hard to pick release names in advance because we don't know sometimes more than 6 months ahead where the conference will be held15:26
fungi(for example, no word yet on where the v conference will happen)15:27
ttxAlso worth noting the naming process changed a few times already15:27
ricolinwe definitely need to clarify what's TC's role in https://governance.openstack.org/tc/reference/release-naming.html and clarify the process like making words like 'the process should consider potential issues of trademark.' more official or simply just remove it out15:27
mugsiettx: I think the issue with post Z is with letters as much as finding the names15:27
ttxIt used to be me throwing names at a whiteboard with a dart as trhe last session of the design summit15:27
ttxthen we thought it would be fun to turn it into a contest15:27
asettlettx, ha!15:28
fungiricolin: i always interpreted that as it was the osf's responsibility to consider trademark issues, and the tc didn't need to concern itself with those15:28
zanebmy personal philosophy is that we elected a bunch of intelligent people and me to the TC, and that we're quite capable of making a subjective decision in context on the merits (particularly of something like this). and if we consistently get it wrong then people will vote for someone else next time (maybe it will even increase TC election voter turnout ;)15:28
ttxIt was fun, until a point15:28
corvusit's really not fun anymore.  this process has been very traumatic for me.15:28
ricolinfungi, in that case, remove the words from reference doc might be a good idea:)15:28
* mnaser is not on the tc to pick release names15:28
ttxcorvus: same here. I made the decision a while ago to no longer get involved15:29
ttxbecause I don;t really care, and some people apparently do15:29
fungiricolin: well, they're in there because we need to make it apparent that the top name chosen by the community may still be rejected by the osf once trademark search is performed15:29
ttxI only care about a codename being given so that we can refer to it15:29
ttxand I think alpha names are easier to remember/use15:29
ttxI could care less how the name was selected, and the more inclusive the process was, the more pain it triggered15:30
mnaseri think as tc all we need to do is come up with some framework that given any letter input will result in a consistent name output.15:30
ricolinfungi, the words you just put in might be a better replacement if that's something all agree on15:30
fungifor point of reference, debian just lets the release team decide what each code name will be15:30
fungiand that seems to work fine for their rather large and diverse community15:31
fungigranted there is occasional rumbling over choice of names15:31
ttxfungi: that is what we started doing15:31
ttxarguably they operate from a narrow set of names too15:31
fungiand regular calls to just stop using names and switch to referring everything by release number15:31
ttxAlso Debian is arguably more of a "thing" that can use numbers15:31
ttxLike you upgrade "Debian"15:32
fungiwell, you upgrade "openstack" too15:32
asettleSure, but it's always referenced by what you're upgrading to...15:32
ttxYou routinely combine component versions though15:32
asettleAnd from15:32
fungii still think referring to coordinated releases by their count would work, but i respect that most others participating in this conversation disagree15:32
mugsiebut openstak v20 including nova v20, neutron v17, and trove v9 is very confusing15:32
ttxI.e. I run the Train version of Ironic and the Stein version of Nova (citation: CERN)15:32
corvusi'd like to find a solution for v-z that doesn't involve people from the community having bad experiences15:32
corvuswithout specifying which method, is that a goal that folks on the tc can get behind?15:33
ttxIf I said I run Ironic 11.0.0 and Nova 22.0.1 you would have no idea I combined versions.15:33
openstackgerritMerged openstack/governance master: Separate goal definition from goal selection  https://review.opendev.org/66793215:33
ttxAnd if I said I run Ironic 11.0.0 from OpenStack 23 and Nova 23.0.0 from OpenStack 22, you would be VERY confused15:34
fungii don't think i would be confused, but it sounds like others might15:34
ttxWhich is why I'd rather stick to codenames15:34
asettlecorvus, I don't think there's a debate whether or not we support finding a solution.15:34
zanebttx++15:35
ricolinttx +1 on that too15:35
corvusasettle: ok, there was some +1 to zaneb's earlier suggestion that it's not broken enough that we need to change the process before z15:35
ttxPretty sure people can understand that we do an alpha cycle and that a>z sometimes15:36
corvus(which i mistakenly +1d, but actually -1)15:36
asettlecorvus, sure. But since there is still objections, a solution needs to be found regardless. I think everyone could agree on that, whether or not they believe it's fine the wya it is.15:36
corvusif it's the case that there is no appetite for changing the process before z, then i will back out of this15:36
*** jamesmcarthur has joined #openstack-tc15:36
openstackgerritGraham Hayes proposed openstack/governance master: Require the TC to choose the release name  https://review.opendev.org/67804615:37
corvusbecause i really can't countenance being involved in the current system (or zaneb's proposed changes to it) at all again.  i'm here to fix this for V.15:37
* jroll wishes he could follow this conversation quickly enough to contribute15:37
ttxMy pet proposal would be to use ICAO names for V-Z, and then large(st) cities for the new round15:37
corvusttx: both of those seem to be garnering enough +0 or +1 feedback to be feasible i think15:38
corvusit does look like (in early tallies) that numbers are right out.15:38
ttxand if we want one single solution, switch to large cities now. But given how few solutions there are around X, that would likely mean to find another solution in 13 years15:38
asettlePerhaps we need to stop talking about our personal preferences - it appears to be making it a bit confusing. We currently have reviews in place, an email out to the community. I think what the tc-members need to decide upon was ttx original question regarding if this is a solution for U-Z or if we should dive right in and decide what's happening post-Z?15:39
ttxasettle: I'm not sure of that.15:39
asettleOf?15:39
ttxIt's a topic (naming) where everyone likes to have an opinion15:39
mugsieIMHO this current round of discussion is V->Z15:39
ttxIt feels like one of those cases where we should actually use the power that is granted on us15:39
asettleSure? Everyone's engaging in that opinion via the reviews, no?15:40
ttxbecause pushing it to the community is likely to create MORE dissatisfaction15:40
ttxLike "why not the ATC-named solution?? Do u hate contributors??"15:40
ricolinpersonally prefer votes than review since all opinions is already there for review, but I'm fine ether way15:41
asettleHAHA okay. I trust you on that. I'm just not seeing how in office hours we're going to solve for X15:41
*** jamesmcarthur has quit IRC15:41
ttxIf we said "given the trainwreck that U was, and in order to avoid other trainwrecks as we enter the sorry part of the alphabet, here is the new rule" I feel like that would be easier to accept than "let's have a 3-month debate on how releases should be named and then pick someone else's solution"15:42
ttxDeciding acknowledges that it is a personal preference exercise anyway15:42
ttxthere is no "best option" imho, naming is not an engineering problem :)15:43
asettlettx, that's a good point15:43
ttxAnd now you make me care about it again. Damn you!15:43
asettleI mean, I'm easy. Provided we have an idea of where we're going and we move on15:43
ttxI mean, come on, who can resist OpenStack Xray.15:44
asettleo.o15:46
ricolinttx X-man might bit it!, just saying!15:46
ttx(that is the issue with deterministic systems, people end up judging the result rather than the system)15:47
zanebI'm still trying to work out if the ATC proposal is satire15:47
*** lpetrut has quit IRC15:48
asettleHO I hadn't seen that one15:48
ttxCan't wait to use OpenStack Zane though15:48
asettleHahahahahahahha15:48
asettleShame we've gone past OpenStack Settle but I could have really got around that15:48
zanebttx: I can't imagine any circumstances in which I would consent to being nominated for that, and the prospect of releases being named after the most gigantic egotists in the community is frankly horrifying15:50
ttxMy hubris is as large as anyone else's, but self-nominating myself for the C release to be named "OpenStack Carrez" sounds a bit too much15:50
ttxzaneb: lol15:50
mnaseri mean15:50
mnaserit's an idea15:50
mnaseri don't know why we have to make fun of it, but it's better than nothing :)15:50
asettleI understand Jeremy's reasoning behind it. I get his meaning. But I agree with Zane on this one.15:50
zanebhttps://gph.is/2eEpqnx15:51
asettlezaneb, thats good drama15:51
zanebspeaking of which, did y'all see that new project proposal?15:51
mnaseri replied to openstack-admin and its interesting15:52
zanebI meant to say, in unrelated news15:52
jrollI had a hard time replying, once I saw it puts its tentacles in every db, that's terrifying :)15:52
asettlezaneb, no?15:52
asettleOh!15:52
asettleYes I did15:52
mnaserjroll: i can kinda imagine the pain though15:52
mnaserour apis are slow15:52
jrolloh for sure15:52
mnaserso i understand why, but i also disagree15:52
jrollbut imagine the pain of tracking every patch that touches the db model15:53
jrollor worse, the pain of your dashboard getting owned15:53
mnaseri am 100% in agreement with you :) i just think that exposes that our apis are slow if that's the best way to pull info quickly15:53
mnaserwe need to improve those15:53
jrollyeah15:54
ttxzaneb: link?15:54
jrollthe searchlight mention was on point15:54
zanebttx: http://lists.openstack.org/pipermail/openstack-discuss/2019-August/008602.html15:55
zanebjroll++15:55
ttxzaneb: thx, somehow I missed it15:55
ttxzaneb: Looks like the 'I like my name on things' proposal is serious... there is now a ML thread about it15:56
zanebI can't even15:57
asettleYerp - he mentioned that in the review15:57
zanebstill could be satire15:58
ttxthe cat is out of the bag. Now "choosing the release naming process" will replace "choosing the release name" as the frustration factory15:59
corvusi see no reason not to take it at face value.  i may be being trolled, but i'll take that risk to treat suggestions with respect.15:59
corvuswe did name a release "rocky".15:59
asettleAnd boy what a smooth one it was16:00
*** jamesmcarthur has joined #openstack-tc16:01
*** ricolin_ has joined #openstack-tc16:01
*** lbragstad has quit IRC16:03
*** lbragstad has joined #openstack-tc16:04
*** ricolin has quit IRC16:04
*** lbragstad has quit IRC16:04
*** ricolin_ is now known as ricolin16:05
*** lbragstad has joined #openstack-tc16:05
*** lbragstad has quit IRC16:06
*** lbragstad has joined #openstack-tc16:06
* ricolin re-post messages because it's not showing in logs due to network disconnect16:07
ricolinIMO, I don't think the issue is to find a perfect solution, it's to find a rule and said if the concerns or conflict is happen, here's how this going to resolve and who holds the final decision. Otherwise, this will goes on forever16:07
*** jamesmcarthur has quit IRC16:09
*** ricolin has quit IRC16:11
*** ricolin has joined #openstack-tc16:11
*** altlogbot_1 has quit IRC16:14
*** ianychoi has quit IRC16:15
*** altlogbot_3 has joined #openstack-tc16:15
*** ianychoi has joined #openstack-tc16:17
*** ianychoi has quit IRC16:19
*** morgan is now known as kmalloc16:19
*** ianychoi has joined #openstack-tc16:19
mnaseri agree with corvus.  i don't think it's fair that we call it 'satire'16:39
mnaserit's a bit disrespectful for someone who's trying to come up with an idea, i don't care how much you disagree with it16:40
mnaserhard enough for the community to be involved in tc activity these days16:41
mnaserif we make fun of actual _attempts_ at being involved in the process, that's just disappointing out of us16:41
mnaserjeremy has/was seriously involved in the process of the release naming and sees to genuinely care, as he has expressed in past reviews and even in ML posts before we got to this stage16:41
jrollhuh, I'm not sure I hate that proposal16:50
funginon-ascii release names certainly would exercise some corner cases in our tooling16:52
fungias well as an opportunity to teach users how to type characters which don't appear on their personal keyboards16:52
*** e0ne has quit IRC16:54
*** markvoelker has quit IRC16:57
*** markvoelker has joined #openstack-tc17:00
*** bnemec has quit IRC17:00
*** jeremyfreudberg has joined #openstack-tc17:05
* jeremyfreudberg catches up on eavesdrop.o.o17:06
jeremyfreudbergso, i sorta forgot that office hours were happening today, otherwise i totally would have attended17:06
jeremyfreudbergi'm not offended that some people perceived my proposal as satire17:06
jeremyfreudbergin any case i thought making such a proposal, one which would capture a certain spirit of 'the story of openstack', was important17:07
jeremyfreudbergi wouldn't want people to look back in couple years' time and wonder why nothing capturing said spirit was proposed17:08
jeremyfreudbergof course i do recognize certain flaws in my idea17:08
fungijeremyfreudberg: it looks like a well-thought-out suggestion, thanks for putting it together!17:18
*** e0ne has joined #openstack-tc17:59
*** e0ne has quit IRC18:11
*** e0ne has joined #openstack-tc18:11
*** irclogbot_1 has quit IRC18:14
*** e0ne has quit IRC18:14
*** irclogbot_1 has joined #openstack-tc18:16
*** altlogbot_3 has quit IRC18:29
*** bnemec has joined #openstack-tc18:34
*** e0ne has joined #openstack-tc18:52
*** spsurya has quit IRC18:52
*** ricolin has quit IRC18:59
*** jrosser has joined #openstack-tc19:29
*** adriant has quit IRC19:57
*** markvoelker has quit IRC20:16
*** markvoelker has joined #openstack-tc20:30
*** jeremyfreudberg has quit IRC20:54
*** e0ne has quit IRC20:56
*** markvoelker has quit IRC21:35
*** mriedem is now known as mriedem_away21:54
*** bnemec has quit IRC22:03
*** markvoelker has joined #openstack-tc22:21
*** markvoelker has quit IRC22:25
*** markvoelker has joined #openstack-tc22:41
*** markvoelker has quit IRC22:51
fungidhellmann: election season e-mail posted as http://lists.openstack.org/pipermail/openstack-discuss/2019-August/008679.html23:12
cmurphyfungi: i will be afk for the entire nomination period, will it be okay if i submit my self-nomination early?23:15
fungicmurphy: absolutely! you'll be confirmed by the officials shortly after the nomination period opens23:20
cmurphyfungi: thanks!23:30
fungithanks for asking!23:32
fungicmurphy: note that the cycle name this time is "u"23:32
*** ricolin has joined #openstack-tc23:59

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