Thursday, 2019-09-19

*** mriedem is now known as mriedem_afk00:09
*** jamesmcarthur has quit IRC00:14
*** njohnston_ has quit IRC00:19
*** njohnston has joined #openstack-tc00:20
*** markvoelker has joined #openstack-tc00:25
*** markvoelker has quit IRC00:29
*** jamesmcarthur has joined #openstack-tc00:58
*** markvoelker has joined #openstack-tc01:00
*** jamesmcarthur has quit IRC01:10
*** jamesmcarthur has joined #openstack-tc01:10
*** jamesmcarthur has quit IRC01:15
*** mriedem_afk has quit IRC01:21
*** jamesmcarthur has joined #openstack-tc01:49
*** jamesmcarthur has quit IRC01:58
*** ricolin has joined #openstack-tc02:22
*** jamesmcarthur has joined #openstack-tc02:28
*** markvoelker has quit IRC02:47
*** jamesmcarthur has quit IRC03:38
*** jamesmcarthur has joined #openstack-tc03:40
*** jamesmcarthur has quit IRC03:44
*** jamesmcarthur has joined #openstack-tc04:09
*** jamesmcarthur has quit IRC04:16
*** Luzi has joined #openstack-tc04:50
*** jamesmcarthur has joined #openstack-tc04:51
*** jamesmcarthur has quit IRC04:56
*** jamesmcarthur has joined #openstack-tc05:17
*** jamesmcarthur has quit IRC05:22
*** markvoelker has joined #openstack-tc06:27
*** markvoelker has quit IRC06:31
*** jaosorior has joined #openstack-tc06:43
*** e0ne has joined #openstack-tc07:17
*** jamesmcarthur has joined #openstack-tc07:18
*** jamesmcarthur has quit IRC07:23
*** tosky has joined #openstack-tc07:23
*** jaosorior has quit IRC07:51
*** iurygregory has joined #openstack-tc08:00
ttxFun experiment in Octavia to identify reviewbots: https://review.opendev.org/68302808:21
ttxNot sure what we'll do with the results though...08:21
*** markvoelker has joined #openstack-tc08:28
*** markvoelker has quit IRC08:33
*** lpetrut has joined #openstack-tc08:33
*** lpetrut has quit IRC08:39
*** lpetrut has joined #openstack-tc09:05
*** iurygregory has quit IRC09:13
*** iurygregory has joined #openstack-tc09:14
asettleo/09:18
asettlettx, that is interesting09:19
*** tetsuro has joined #openstack-tc09:20
*** markvoelker has joined #openstack-tc10:29
evrardjpapparently it already caught an incorrect review.10:33
asettleHuh interesting10:34
*** tetsuro has quit IRC10:34
*** markvoelker has quit IRC10:34
evrardjpIs it a problem we need to tackle? Or is it only an inconvenience? Do we need a policy OpenStack wide, or can the projects be masters of their destiny?10:36
evrardjpI have the impression that bringing a Backport vote could help PTLs on tracking backports, but I am not sure if: 1) this needs to be a policy more than a recommendation 2) if changing the order will do anything for bots (as it's a probably a one liner to change the order).10:37
asettleevrardjp - honestly, I think those are questions to ask after the experiment is over. Let Octavia do their thing, and then depending on the results, we can talk more to other projects.10:37
asettleBut I think asking whether or not this is a problem to tackle is the horse before the cart.10:37
evrardjpAgreed.10:38
evrardjpI probably wrongly said what I mean too: I wonder if Octavia is alone with this perception, or if there is a general problem (so it would nice to hear from PTLs here)10:39
mugsieit is. I used to be able to look at patches with > n +1 votes, and it was usually at a pretty good state, now it just means a round of bots has been through10:42
*** e0ne has quit IRC10:42
evrardjpso that dillutes the perception of a drive-by but careful review10:44
evrardjpgood feedback mugsie10:44
evrardjpI was more lucky on the projects I am reviewing I guess10:45
*** e0ne has joined #openstack-tc11:21
jrollinteresting11:33
jrollwas mentioned in infra that they wanted to wait to see if TC had an opinion on that, I'm personally fine with it, will mention on the review11:36
jrollagree it is a general problem11:36
mnaserI think we fixed the trailing +1 issue with a certain organization by talking to them11:38
mnaserLet's try to do that first...11:38
njohnstonIt may vary project by project, but in the ones I work with I have not seen more than one or two accounts that tend to +1 just about everything, and those have tailed off recently.  There quickly gets to be a "discount effect" among cores where a +1 from certain name(s) gets mentally blacklisted.  Also they tend to stand out pretty strongly in views like https://www.stackalytics.com/report/contribution/neutron-group/9011:42
*** ijolliffe has joined #openstack-tc11:55
*** tetsuro has joined #openstack-tc11:58
*** ricolin has quit IRC12:06
ttxyeah... i see the main effect to be that it taints the reputation of well-behaving reviewers from the same company(ies)12:06
ttxSince nobody plays "Top #2 contributor" games anymore12:07
ttxBut it's hard to go to a company and say "you seem to be playing stats, you should probably not do that" withuot some sort of proof. It's hard to say a random +1 is automated12:08
ttxReminder taht today is the last day for us to pick sessions to submit to Shanghai -- please fill https://etherpad.openstack.org/p/PVG-TC-brainstorming if you havent yet12:09
ttxThere aren't a ton of available slots apparently, so no need to submit things where we know nobody would show up12:09
*** markvoelker has joined #openstack-tc12:13
*** jamesmcarthur has joined #openstack-tc12:18
*** njohnston has quit IRC12:18
*** njohnston has joined #openstack-tc12:19
mnaserttx: yeah but I think the approach we took was to explain those +1s werent clean reviews so to speak12:22
mnaserNo comments, no info12:23
ttxtrue12:27
smcginnisEvery once in awhile, about every 3-4 weeks it seems, I still get some random accounts that +1 patches I have upvoted.12:29
*** lbragstad has quit IRC12:29
*** lbragstad has joined #openstack-tc12:30
smcginnisWhich only stands out because I vote on patches in a kinda weird mix of repos, so definitely not normal that someone else would just happen to be reviewing cinder, glance, release, and random patches too.12:30
*** jamesmcarthur has quit IRC12:30
*** jamesmcarthur has joined #openstack-tc12:30
*** eandersson has quit IRC12:31
toskyuh, I've seen for ages those "no context, out of the blue" reviews on sahara12:32
toskythe octavia experiment seems interesting :)12:32
*** jamesmcarthur has quit IRC12:36
*** markvoelker has quit IRC12:46
*** lpetrut has quit IRC12:48
*** ijolliffe has quit IRC12:56
*** ijolliffe has joined #openstack-tc13:02
*** jaosorior has joined #openstack-tc13:18
*** mriedem has joined #openstack-tc13:30
*** jamesmcarthur has joined #openstack-tc13:36
*** jamesmcarthur has quit IRC13:36
*** jamesmcarthur has joined #openstack-tc13:36
evrardjpmnaser: agreed on the talk to them approach13:37
evrardjpsmcginnis: either you have a stalker, a fan, or a split personality13:37
evrardjpor maybe all of the above :)13:37
evrardjphahah13:38
smcginnisevrardjp: Hah!13:50
*** jeremyfreudberg has joined #openstack-tc13:52
*** Luzi has quit IRC13:53
*** tetsuro has quit IRC14:00
fungimaybe a terrible idea, but we could routinely generate random honeypot changes and then auto-disable any accounts which leave a +1 or -1 vote on them14:02
fungimake the prose in the commit message clear that's what they are, but change up enough of it that pattern matching on various aspects of the change is futile14:03
fungigranted, that's a significant engineering undertaking to solve a problem which is probably at most a minor nuisance14:04
*** tetsuro has joined #openstack-tc14:06
smcginnisSounds kind of like what I did for third party CI's in Cinder - https://review.opendev.org/#/c/523143/14:15
smcginnisBut yeah, probably overkill.14:15
*** e0ne has quit IRC14:28
*** iurygregory has quit IRC14:46
*** iurygregory has joined #openstack-tc14:47
mnasersmcginnis: oooooof14:51
mnaserthat's an interesting approach14:51
*** tetsuro has quit IRC14:52
*** tetsuro has joined #openstack-tc14:55
*** tosky has quit IRC14:57
*** tosky has joined #openstack-tc14:59
smcginnisThe results were a little better than I feared. Only two were obviously not testing the code they should have been.15:00
*** ricolin_phone has joined #openstack-tc15:00
mnaser\o/15:00
ricolin_phoneo/15:00
evrardjpsmcginnis: I like the commit text15:01
evrardjpand wow on the results.15:01
evrardjphello everyone!15:01
*** e0ne has joined #openstack-tc15:02
fungiyour first office hour as the tc chair. i hope it's all you dreamt it would be ;)15:03
njohnstono/15:03
zanebo/15:03
evrardjpfungi: you cannot imagine! my wildest dreams!15:03
evrardjphahahaha15:03
ricolin_phoneevrardjp: stop there!15:03
ricolin_phoneHahaha15:03
evrardjptc-members I am in definitely looking for a friend to join me as TC furniture. If you're interested by being vice-chair don't hesitate to talk to me :)15:04
evrardjpthat was my first topic for today15:04
evrardjpanyone has a topic before I continue on the more meaty stuff? :)15:05
ttxyes15:05
ttxWe need to file the forum sessions before tomorrow EOD15:05
evrardjpdoes that involve names?15:05
ttxso we urgently need to decide which to file15:06
ricolin_phoneI think we also need to settle down our forum15:06
ttxhttps://etherpad.openstack.org/p/PVG-TC-brainstorming15:06
ricolin_phoneLike tc said:)15:06
evrardjpI thought it was all of the above15:06
ricolin_phonettx15:06
evrardjpttx: I think it is nice to merge Leadership and tips and tricks15:06
ttxyeah, since leadership will be about making it an easier job anyway15:07
evrardjpttx: maybe we can merge 5 and 9 with the topic: Innovation -- bring your crazy ideas15:07
asettleo/15:07
ttxSo Ussuri goals sounds like a no-brainer, we just need a volunteer to file it15:08
evrardjpif we merge 3-4//5-9// and we are short on rooms, maybe we can merge 1-2 too15:08
mnaserim all for dropping 915:08
mnaserttx mentioned that we've discussed it in the past15:08
ttxI nominate gmann in his absence15:08
mnaserand can you imagine taking a year to land a feature15:08
ttxV goals... wondering if we'll have critical mass to discuss that15:09
evrardjpttx: I vote for that :p15:09
njohnstonmnaser: absolutely, it took us 2.5 years to land quality of service in neutron :-)15:09
evrardjpvoluntold!15:09
mnaserwe've always just concluded that 6 months is ok, if anything shaping up for a release that takes 1 whole year would be draining15:09
evrardjpmnaser: I agree on that.15:09
mnaserand a longer PTL cycle so its really doing the opposite of what we're trying to accomplish: make life easier15:09
asettleWhen was the last time the discussion happened? I admit to having heard rumblings about it again recently, which is why I included it. In fairness, I have no strong feelings.15:10
evrardjpttx: for V goals -- it seems like it would be important to still host it. We've complained last time we didn't do it on time, so it makes sense to at least start it.15:10
jrollI would love to debate cycle frequency just to inject the "release continuously" option :)15:10
jrolls/inject/argue for/15:10
evrardjpjroll: :)15:10
ttxI'll file 7, that's disconnected from TC really15:11
evrardjpthis is why I propose to rename that thread to "bring your own (crazy) ideas"15:11
mnaserV goals and crazy ideas are a bit distinct imho15:11
evrardjpsorry15:11
evrardjpI meant jroll's idea and 915:11
asettleevrardjp, I actually kinda like that idea. A session where people can come along and say "I was thinking about this thing..."15:11
ttx++15:11
evrardjpyeah! exactly15:11
asettleOr "I heard rumour about a thing"15:11
evrardjpand we write down15:11
zaneb+1 on a bring your crazy ideas session15:11
jrollI like the idea of "BYO ideas", I don't like conflating it with cycle length or goals15:12
evrardjpjroll: will lead with the release continuously15:12
asettleYeah, it encourages a space for people to openly talk and debate ideas15:12
evrardjpjroll: nope nope nope it was for session 5 /915:12
ttxmnaser: you good filing that expanded one?15:12
jrollevrardjp: I won't be there, in case I haven't said it enough15:12
ttx5+915:12
mnaseri don't really wanna be talking release cycles :)15:12
evrardjpjroll: we'll organize that session at midnight, so you can remote join!15:12
ttxme neither15:13
evrardjpjoke aside...15:13
*** tetsuro has quit IRC15:13
mnaseri want to taalk about new architectures and helping make deployment fo openstack more modern, adopting it with more new technologies15:13
zanebyeah, I agree that 9 is a completely separate topic15:13
mnaserso i would *explicitly* not want that there, because i know some community members will *shrug* reading that and now show up15:13
mnaser*not15:13
mnasercause they just dont wanna go over that conversation15:13
jrollmnaser: ++15:13
zanebwhich we should just not have a session for imho15:13
zanebmnaser: ++15:14
ttxyeah, I've been having that session far too often15:14
zanebdiscussing new architecture ideas is interesting and worthwhile15:14
*** tetsuro has joined #openstack-tc15:14
ttxI'm happy to have a 1:1 discussion with whoever15:14
evrardjpOk I am not sure I understanding what the problem is.15:14
*** tetsuro has quit IRC15:15
zanebdiscussing the release cycle is boring and pointless. if people want to do it, fine, but let's not take up time from another session15:15
evrardjpIsn't the architectural conversation a good convo for "bring your crazy idea"?15:15
jamesmcarthursmcginnis: Here's a link to the csvs for User Survey PTL feedback on Google Docs: https://drive.google.com/drive/folders/1Iy07hjwbON4di-Ly5njGLYXTQSSVbStl?usp=sharing15:15
zanebevrardjp: yes15:15
evrardjpzaneb: I see15:15
mnaser"different release cycles" is on that list, the second peopel see that, they walk out :)15:15
evrardjpyou don't want to phagocyte time15:15
jamesmcarthursmcginnis: I'll have to figure out something else if folks in China need access.15:15
ttxWe have been having that discussion quite a few times already and it always concludes in the same way15:16
evrardjpttx: ok15:16
ttxafter wasting 40 minutes of my life again15:16
evrardjphaha15:16
ttxI've been having that discussion... 10 times I think. Not even kidding15:16
njohnstonwow15:16
zanebevrardjp: I'll have to check the dictionary15:16
evrardjpso let's keep the topic "bring the crazy idea" :)15:16
ttxYes, there is such thing as too often and too rarely... and 6months is still the best way to reconcile both15:17
asettleCool, let's move past that. It was just a suggestion.15:17
evrardjpzaneb: hey, I am not a native english speaker ! :)15:17
evrardjpagreed with asettle15:17
evrardjpso15:17
ttxasettle: I'm happy to discuss it again. But I need to be drinking beer at the same time, and it should be with a smaller group15:17
evrardjphow many session can we have?15:18
ttxshould go faster15:18
evrardjpI like the idea of separating 1 and 215:18
asettlettx - ha! Probably ;) but let's save that beer for another time :)15:18
ttxhard to tell, but there are 22 slots available total I think15:18
ttxso I would be conservative15:18
evrardjpok15:18
asettleevrardjp, how are you thinking of separating them from what they are already?15:18
mnaserzaneb: are you interested in #5 too?15:18
mnaseri know we spoke briefly at the meeting at "future architecture"15:19
mnaserok that answers it :)15:19
zaneb:)15:19
evrardjpasettle: I meant 2 sessions vs 1 grouped session for elements 1 and 215:19
ttxSo that leaves 6 and 815:19
asettleYep keep it as it is15:19
mnaserok ih ave 2 names so ill submit #515:19
ttxI think both are useful, but maybe better done through ML15:19
ttxor me and rico havnig a drink15:19
asettleYeah I'm not sure we need a forum session discussing a SIG guide15:19
asettleThat seems ML orientated15:20
mnasera single drink? :)15:20
ttxI can do a SIG guide over a single drink. 2020 investment opportunities is more of a late night multi-whisky-tasting thing15:20
evrardjp:)15:20
jrollone more thing on #5, do we really think we can fit any other ideas into 40 minutes when "revisit core infra architecture" is to be discussed?15:21
*** ricolin has joined #openstack-tc15:21
asettlejroll, depends on how strict the moderator is15:21
asettleIt's kinda like a lightning talk session, right?15:21
evrardjpCan the upstream investment opportunities be something we prepare all together on the ML and talk the foundation before the summit?15:21
jrollwell15:21
asettleSo maybe you're right, jroll  - perhaps mnaser might be better off suggesting it on it's own?15:21
evrardjp(don't shoot the messenger)15:21
jrollasettle: yes, +115:22
asettleevrardjp, it probably could be. But good conversation can happen at the forum15:22
mnaserto the foundation or the board?15:22
ttxcould be an end of day double-dlot topic15:22
ttxslot15:22
asettlettx, the crazy one? I think that's a good idea15:22
mnaseryeah im not necessarily trying to think of the session being like "what can we change in openstakc" but "how can we fit the new ecosystems better"15:22
ttxIf we finish early, we can go back to hotel15:22
evrardjpmnaser: you're right, even the board15:22
mnaseri mean im not sure there's much the foundation itself can do15:22
mnaserthis can be presented to the board but um15:22
mnaserwe'd be at strike 3 of going over it :)15:22
evrardjpcorrect!15:23
zanebevrardjp: yeah, I not sure what there is to talk about for 2020. presumably we will roll over all the 2019 ones... what we we do with the other 39 minutes?15:23
ttxthe single-slot vs. double-slot is usually decided by the section committee15:23
ttxselection*15:23
evrardjpzaneb: exactly why I proposed to not have the session :)15:23
*** ricolin_phone has quit IRC15:23
evrardjpbut maybe I am too slow to read translate and write, and therefore we were maybe all in agreement15:23
ttxOK, we seem to be in a good place now15:24
ttxI'll chase down the submitters15:24
asettleevrardjp, zaneb it just might be a good time for people to come with their projects to add to the 202015:24
asettleBut could always be done with ML15:24
ttxanything we are critically missing?15:24
* zaneb was attempting to +1 your proposal to not have the session15:24
evrardjpoh :)15:24
evrardjpgot it15:24
zanebasettle: even better, they can propose a patch any time :)15:25
asettlezaneb, \o/ come one, come all15:25
mnaserim ready to hit submit for #515:25
evrardjpmnaser: go ahead :)15:25
asettleSo, evrardjp and tc-members I had an idea for those going to Shanghai. I wasn't too sure if we could do it as a forum session or maybe just an informal hallway track, but since we'll be meeting so much of the Asian contingent that doesn't normally come to north america or europe for the other confs, it would be a good time to do a meet and greet style-session.15:26
mnaserand im done ith that15:26
evrardjpwe do have our meeting room during the event, right?15:26
asettleJust, "this is who we are and what we do"15:26
asettleSpecifically for the TC (and UC?)15:26
evrardjpthat's a good idea to have a meet and greet thing :)15:26
fungiand most importantly, show them it's not mysterious at all and totally within their reach15:27
asettleBasically, yeah15:27
asettleGive people a way to say "Oh I know someone on the TC now, I can help us do X Y Z"15:27
mnaserand everyone will have wechat setup so they can be accessible to them... right?15:27
mnaser:)15:27
evrardjpwould that be part of our meeting room or do you wnat that as a lunch thing, where we could all spread to different tables?15:27
asettleevrardjp, open to suggestion. Does anyone have strong feelings on how we would manage this?15:27
asettleLunch might be a bit hard to manage15:27
asettleAlthough it's nicer to have a less-formal setting15:28
mnaserya i dont know about the logistics and that might throw a wrench in things for prep at the OSF side15:28
evrardjpyeah I am just still in a "throw you crazy ideas" mode15:28
mnaserwe'll probably all be at some $mixer_event15:28
mnaserand i think it has to be the opposite15:28
fungimnaser: maybe it's a good opportunity to explain to them the benefits of messaging solutions used by more than just the people within their political borders, now that we've established (afaik) that the great firewall is not blocking irc access to freenode15:28
evrardjpwell we could just ask?15:28
asettlefungi, that's good to know. I didn't know/see that.15:28
mnaserwe have to go out and approach those folks rather than asking them to come approach us imho15:28
asettlemnaser, that's the whole idea.15:29
asettleLiterally.15:29
evrardjpexactly15:29
evrardjpwe are just trying to find a way :)15:29
mnaserright, so rather than "meet the tc", its "tc lets all go out and socialize into that community"15:29
fungiasettle: we've had people in mainland china not using foreign network access report that they're able to connect to irc just fine, at least15:29
mnasermaybe its a detail thing but personally i think its a huge difference when you are reached out to vs "come talk to us"15:29
fungi(and not on corporate vpns either)15:29
asettlefungi, that's great to know.15:29
mnaseresp if your main language isn't english either15:30
fungimnaser: it's an even better thing to say "here's somewhere everyone can come and have discussions"15:30
evrardjpfungi: It's not easy to have irc conversations when it's not your native language. Sometimes it goes too fast.15:30
asettlemnaser, right, sure. Semantics. My idea remains the same, become available and have a meeting session or location of some kind to provide an inviting and welcoming environment where other members of the community that otherwise wouldn't attend events has the opportunity to interact15:30
evrardjpmnaser: hahah15:30
evrardjpagreed!15:30
fungievrardjp: even when it is in my native language it often goes too fast15:30
fungievrardjp: but telephone conversations are even harder still15:30
mnasertotz15:30
evrardjpI was just proving the thing, mnaser just pointed it out, and I didn't get the chance to catch it immediately because I was 5 lines above :p15:31
mnaserso hence one of those evening events or something where everyone is usually there15:31
asettleAnyway we could "formalise" it a bit?15:31
evrardjpwe'll have a tendency to gather together15:31
mnaseryes, we need to break that15:31
evrardjpwe need to keep that in mind :)15:31
mnaserthats why im saying we need to maek sure we dont stick around each other at those events, i'm sure we'll get to spend *plenty* of other qualtiy time together15:32
asettleAnd nobody is disagreeing with you :)15:32
mnaserformalizing a "the TC will be at X and Y come to us" just feels intimidating to someone whos new to it, imho15:32
mnaserbut anyways, that's just one voice15:33
mnaserothers welcome to chime in :)15:33
asettleHow do we (as a tc body) propose to let contributors know that we're around and hoping to meet people without advertising it?15:33
fungialso worth being aware, it sounds like we probably won't have leadership-oriented identifiers on badges this time (due to cost, i think?)15:33
evrardjpcool15:33
fungiso don't just assume folks will know you're on the tc15:33
evrardjpeveryone the same!15:33
asettlefungi, that's good to know. So we might want to be a bit more verbose? Or perhaps party hats?15:34
evrardjpbut though it makes the logistics a little harder15:34
evrardjpasettle: at FOSDEM, the VLC guys have hats. It's awesome.15:34
fungiasettle: or color-coded leis15:34
asettleDAMN we should have hats15:34
mnaserthe more we are _different_ from the normal contributors15:34
asettlefungi, would match your shirt :P15:34
mnaserthe more its intimidating and the tc feels more inaccessible, imho.15:34
fungidepends on what colors the emeritus lei uses15:35
evrardjpmaybe we should have tshirts that everyone can have?15:35
jrollmnaser: you have a point, but if there's no way for people to tell who is TC, it's also intimidating to try and meet the TC (because you have to meet 10 people before you find a TC person)15:35
evrardjp"Interested by OpenStack! Join the TC!"  We'll carry them and distribute them15:35
asettle^^ that, I'm afraid.15:35
mnaserjroll: i dont think anyone is running around trying to find a tc member to say hi to15:35
jrollI do15:36
* fungi would like to meet the tc15:36
asettleI mean, I would have loved to back in the day. I barely knew who was on the TC15:36
asettleI honestly felt like the TC was so intimidating and untouchable until I met dhellmann15:36
jrollIME, there are lots of people, especially from outside the US, who wait until the summit to introduce themselves to leadership and talk about some topic15:36
evrardjpjroll: that's an important point, can we focus on that?15:36
njohnstonasettle: I had the same experience!15:36
jrollI had so many random "oh hi, you're the PTL! do you have 5 minutes to talk about x?" when I was ironic PTL15:36
asettlenjohnston, he's a gem like that isn't he :D15:37
evrardjpasettle: same for me.15:37
asettlejroll, exactly15:37
zanebmnaser: you're making valid points, but how will people recognise that we are just normal contributors if they don't have a way of recognising us? they may just assume that we are off locked in a room doing god-like things and that they are merely mixing with the plebes15:37
evrardjpit seems like dhellmann is the keystone of this convo. Pun intended.15:37
mnaserfair enough about this15:38
mnaserits too bad our badges dont have the extra things15:38
jroll13 stickers would be cheap :)15:38
evrardjpjroll: any idea on how we can tackle this?15:38
ricolinjroll, about to say that too:)15:38
evrardjpdamn too slow15:38
jrollI liked the "lunch with the TC" events in the j-l days or so, but I guess I'm not sure if others felt the same15:38
evrardjpok15:39
jrollI think it was 5-6 tables with 1-3 TC members each, and people could go talk to them15:39
mnaserbtw we need to also figure out if this is a ptg thing or a summit thing15:39
evrardjpmaybe we can combine?15:39
asettleI'm cool with lunch, maybe we could find an evening that doesn't have an event and organise an informal "we're in the hotel, we're all wearing party hats to look ridiculous, please say hi?"15:39
evrardjpasettle njohnston how did you speak with Doug in the first place?15:39
asettleOr, "we'll say hi to you if you're not wearing a party hat"15:39
ricolinwe got a overlap day, so we can do it that day to cover both PTG and summit:)15:39
asettleevrardjp, the sinking shitfest that was the docs team post-OSIC15:40
evrardjpoh15:40
asettlericolin, that's a good idea. Use the overlap evening to have a "come see us in party hats and have a chat about anything" thing15:40
evrardjpwell15:40
fungimy recollection is the "lunch with the tc" space ended up as random crash-space for people looking for somewhere to sit with their lunch, and so anyone who *was* actually interested in meeting tc members couldn't find an available seat15:40
jroll(again, I won't be there but) I would prefer a lunch thing, by 6pm I am socially exhausted15:40
asettleThat way, we're in a central location, identifiable, and then to mnaser 's point, we're approaching people without party hats?15:40
jrollfungi: that's good data15:40
evrardjpindeed15:41
njohnstonevrardjp: It was at a summit, I decided to go to a session about oslo matters and dependency management of some kind... in Tokyo perhaps?15:41
mnaseri will gladly make lanyards or stickers to avoid wearing a party hat :-)15:41
mnaserbut sure15:41
asettleHAHA mnaser okay, party hats can be vetoed. But basically, come along and we'll chat to you if you're not wearing _thing_15:41
evrardjpI think the party hat makes us more accessible :)15:41
mnaseror the osf can give us drink tickets and you only can only get one from tc members15:41
mnaserbahaha15:41
evrardjpbut hey15:41
evrardjpanyway15:42
evrardjpwe've got two ideas there15:42
evrardjp1) the lunch15:42
evrardjp2) the mixer15:42
zanebmnaser: I spot a tiny flaw in that plan ;)15:42
evrardjpcan we do both?15:42
asettleWe can?15:42
evrardjpsomeone said lunch might be hard to organise... how can we know more?15:42
mnaserbefore we go too far15:42
mnaserwe need to talk to the osf and make sure it can work15:42
mnaserthere might be plans put in place from months ago15:43
ricolinAlso bring the sticker/t-shirt idea to OSF too15:43
asettleI think mnaser answered your question evrardjp - talk to osf15:43
evrardjpok15:43
fungioh, one other "lunch with the tc" anecdote, at least once when we did that by the time the tc members could make their way to the room where it was being held, random folks had already co-opted it as space to eat their own lunch and taken the tc member flags off the tables and stuck them in random corners or under tables15:43
asettleHAHAHA15:44
evrardjphahah15:44
asettleWhy does that not shock me15:44
fungiso even the tc members couldn't find available seats at their designated tables, or find their tables at all for that matter15:44
evrardjpyeah and not everyone is into the "hey can I crash ~your~ my table?"15:44
evrardjpthough it would be a nice icebreaker15:45
evrardjpif that's how you call it15:45
fungior, "hey is there a flag stand stashed under your table? can you let me know if my name is listed on it?15:45
evrardjpor maybe it's my sense of humor talking here15:45
evrardjphahaha15:45
asettleAlright15:47
asettleSo15:47
asettleWhat's next?15:47
asettleOr, anything else?15:47
evrardjpwell we were still at the sessions15:47
evrardjpmaking sure we didn't forget something15:47
ricolindo we have actions out of above discussion?:)15:48
evrardjpI am opening old etherpads :)15:48
evrardjpricolin: yes, talk to the OSF to find out what's possible15:48
evrardjpI will ping ttx as the grand ruler from its french side and see who can I ping15:48
ricolinokay15:49
ricolinevrardjp, thx15:49
evrardjpmaybe it would be worth redoing a "outreach session" now that we'd be in a completely different public?15:50
evrardjp"community feedback"15:51
ricolinI think that will be useful15:52
* ttx catches up15:52
evrardjpthanks mnaser for submitting btw15:52
asettle+115:52
mnasernp15:54
ttxevrardjp: if you send me (or fungi or diablo) an email, I can forward it internally to the summit org people15:56
evrardjpsounds good15:57
*** iurygregory has quit IRC16:08
*** jamesmcarthur has quit IRC16:12
*** e0ne has quit IRC16:14
*** markvoelker has joined #openstack-tc16:15
*** mriedem is now known as mriedem_afk16:15
*** njohnston has quit IRC16:21
*** jeremyfreudberg has quit IRC16:21
*** jamesmcarthur has joined #openstack-tc16:21
fungii suggest the tc go ahead and choose the name for the "v" cycle now: http://lists.openstack.org/pipermail/foundation/2019-September/002794.html16:31
fungithere's probably a very reasonable, consensual option for it16:31
smcginnis++16:32
mnaservexxhost?16:35
* mnaser drops mic and walks out16:35
fungihah, perfect16:35
smcginnis"The OpenStack community is please to announce the release of OpenStack Vexxhost." :D16:36
jrollI'm sure legal would love that one :P16:36
jrollis "OpenStack Vancouver" too easy?16:36
jrollalso \o/ for vancouver in june16:37
fungiyeah, it would not result in the requisite quantity of community angst over the naming process16:37
*** jamesmcarthur has quit IRC16:42
*** jamesmcarthur has joined #openstack-tc16:43
zanebfungi: this sounds a lot like a challenge to find other obscure place names in BC starting with V16:44
fungiyeah, probably none nearby vancouver16:45
fungioh, wait... ;)16:45
*** e0ne has joined #openstack-tc16:45
evrardjp:)16:46
* fungi does actually really enjoy victoria, more than vancouver even16:50
dhellmannasettle , njohnston : it's your turn to set the example now ;-)16:51
ttxwell16:55
ttxTEchnically Vancouver is not a summit16:55
ttxso we have a gap in the rules.16:55
ttxIn theory we should choose from where last summit happened. Which brings us back to Shanghai16:56
fungiright, technically there is no v summit, so we need a new process for that one either way16:56
* ttx goes back in the corner16:56
fungior, yeah, you'd consider the u summit to also be the v summit16:56
ttxthis is how it worked in the past16:56
fungii suppose that's one possible interpretation16:56
ttxThe Cactus/Diablo situation16:57
fungioh, was there no summit between cactus and diablo? that predates me slightly16:57
ttxThere was no summit between Bexar and cactus16:57
fungiahh16:57
ttxso cactus still related to the San Antonio summit16:57
ttxback when we did 3-month releases16:58
ttxgood trivia16:58
fungiindeed16:58
* fungi sticks that in his pocket for later use16:58
ttxSo I'd say that if we want vancouver we still need to adjust the rules one way or another16:58
ttxnot urgent16:58
* ttx disappears16:58
zanebtechnically it says "summit" and not "Summit", so while there will not be a Summit we will be having a summit and Vancouver is thus legit17:00
*** markvoelker has quit IRC17:01
fungii like zaneb's attention to capitalization17:01
fungigood thing we didn't write the rules in german17:01
* zaneb stops trolling and goes to do actual work17:03
*** markvoelker has joined #openstack-tc17:04
*** gmann_afk is now known as gmann17:21
gmannttx: evrardjp main idea of separating those is to discuss implementation details for U cycle and start gathering the idea for V cycle as first phase.17:22
gmannttx: evrardjp if I read it correctly, I need to submit those or those are already submitted ?17:23
zanebgmann: you should submit them17:23
zanebgmann: or tell ttx that you are not going to submit them (in which case he will do it)17:24
gmannzaneb: ok. I will submit. thanks17:24
gmannah, just read the comment on etherpad.17:26
*** ricolin has quit IRC17:31
*** mriedem_afk is now known as mriedem17:33
*** njohnston has joined #openstack-tc17:54
*** aprice has joined #openstack-tc18:11
evrardjpthanks zaneb and gmann18:13
*** jamesmcarthur has quit IRC18:21
*** jamesmcarthur has joined #openstack-tc18:22
gmanndone.18:35
evrardjpzaneb: I like your style on the "summit" conversation ;)19:40
*** jamesmcarthur has quit IRC20:01
*** jamesmcarthur has joined #openstack-tc20:04
*** jamesmcarthur has quit IRC20:20
*** jamesmcarthur has joined #openstack-tc20:21
*** jamesmcarthur has quit IRC20:22
*** e0ne has quit IRC21:00
*** e0ne has joined #openstack-tc21:12
*** ijolliffe has quit IRC21:19
*** markvoelker has quit IRC21:20
*** lbragstad has quit IRC21:37
*** lbragstad has joined #openstack-tc21:37
*** markvoelker has joined #openstack-tc21:48
*** ijolliffe has joined #openstack-tc21:51
*** e0ne has quit IRC22:24
*** notmyname has quit IRC22:30
*** notmyname has joined #openstack-tc22:31
*** markvoelker has quit IRC22:32
*** mriedem is now known as mriedem_away22:41
*** tosky has quit IRC23:12
*** e0ne has joined #openstack-tc23:30
*** e0ne has quit IRC23:30
*** e0ne has joined #openstack-tc23:55
*** e0ne has quit IRC23:55

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