Thursday, 2019-09-26

*** zhurong has quit IRC00:43
*** zhurong has joined #openstack-tc00:56
*** jamesmcarthur has joined #openstack-tc01:33
*** diablo_rojo has quit IRC01:56
*** njohnston has quit IRC02:29
*** ricolin has joined #openstack-tc02:31
*** jamesmcarthur has quit IRC03:38
*** markvoelker has quit IRC04:08
*** jamesmcarthur has joined #openstack-tc04:09
*** jamesmcarthur has quit IRC04:16
*** jamesmcarthur has joined #openstack-tc04:46
*** jamesmcarthur has quit IRC04:51
*** markvoelker has joined #openstack-tc05:05
*** markvoelker has quit IRC05:11
*** jamesmcarthur has joined #openstack-tc05:22
*** jamesmcarthur has quit IRC05:26
ricolingood afternoon all05:52
ricolino/05:52
*** jamesmcarthur has joined #openstack-tc05:53
*** jamesmcarthur has quit IRC05:57
evrardjpI will miss the office hours today folks, sorry05:59
*** jamesmcarthur has joined #openstack-tc06:04
*** jamesmcarthur has quit IRC06:09
*** jaosorior has quit IRC06:30
*** jamesmcarthur has joined #openstack-tc06:35
*** jamesmcarthur has quit IRC06:39
*** jaosorior has joined #openstack-tc07:05
*** jamesmcarthur has joined #openstack-tc07:35
*** jamesmcarthur has quit IRC07:40
*** lbragstad has quit IRC07:47
*** lbragstad has joined #openstack-tc07:47
*** bnemec has quit IRC07:49
*** bnemec has joined #openstack-tc07:51
*** jamesmcarthur has joined #openstack-tc08:05
*** jamesmcarthur has quit IRC08:10
*** e0ne has joined #openstack-tc08:45
*** jamesmcarthur has joined #openstack-tc08:46
*** lpetrut has joined #openstack-tc08:49
*** jamesmcarthur has quit IRC08:51
*** markvoelker has joined #openstack-tc09:08
*** ricolin has quit IRC09:11
*** markvoelker has quit IRC09:13
*** jaosorior has quit IRC09:17
openstackgerritTom Barron proposed openstack/governance master: Add Goal Champions investment opportunity for 2019  https://review.opendev.org/68098509:41
*** jamesmcarthur has joined #openstack-tc09:47
*** jamesmcarthur has quit IRC09:52
*** jamesmcarthur has joined #openstack-tc10:49
*** jamesmcarthur has quit IRC10:54
*** jamesmcarthur has joined #openstack-tc11:00
*** jaosorior has joined #openstack-tc11:05
*** jamesmcarthur has quit IRC11:11
*** markvoelker has joined #openstack-tc11:17
*** markvoelker has quit IRC11:22
*** jamesmcarthur has joined #openstack-tc11:33
*** tetsuro has quit IRC11:43
*** tetsuro has joined #openstack-tc11:57
*** ianychoi has quit IRC12:00
*** ianychoi has joined #openstack-tc12:03
*** jamesmcarthur has quit IRC12:04
*** markvoelker has joined #openstack-tc12:07
*** ijolliffe has joined #openstack-tc12:48
*** tobberydberg_ is now known as tobberydberg13:01
*** ricolin has joined #openstack-tc13:05
*** mriedem has joined #openstack-tc13:06
ricolino/13:47
*** iurygregory has quit IRC14:11
jrollmay be a bit late for office hours, I've just realized I have another 2 hours of meetings after that so I should probably eat :)14:43
asettleo/14:49
asettleI think I'll miss office hours today, I have some old friends arriving in town at 4pm14:49
* mugsie is fighting terraform, so will be in and out of the meeting14:49
* asettle puts money on terraform 14:50
asettleGoooo terraform!14:50
* mugsie puts money on terraform as well14:50
asettleoof mate14:51
jrollmade it. fastest sandwich maker on the TC.14:56
asettlePut that on your resume14:59
jrollyou don't think it's there already? pft14:59
jungleboyjo/15:00
asettlejroll, my mistake :p15:00
jroll:P15:00
mnasero/15:00
jrollso given it's office hours, just a heads up: ttx and I completed archiving stale github mirrors this morning15:01
ricolino/15:01
jungleboyjThat sounds like fun.15:02
jrollit was pretty cathartic :P15:03
jungleboyjCatharsis is a good thing.15:05
ttxo/15:05
ttxso many non-openstack things15:05
ttxIf you hear complaints, redirect them to http://lists.openstack.org/pipermail/openstack-discuss/2019-September/009615.html15:06
mugsieRIP kosmos :)15:06
ttxailuropoda, we'll miss you15:07
zanebo/15:07
ttxSo ni the news, we'll go ahead and organize some form of "Meet project leaders" event in Shanghai during the mixer on the first day and Wednesday lunch15:08
ttxIt's not just the TC, we could have elected leadership from other projects, PTLs...15:09
mugsiettx: ++15:09
ttxDetails will be coming but the idea would be to run it twice to give everyone a chance15:09
ttx(Monday marketplace mixer + Wednesday lunch)15:09
jrollnice! I like it15:10
ttxwe are still thinking of a visible way to say "talk to me"15:10
ttxstickers on badges are likely not visible enough15:10
mugsiesome sort of hat with a neon down arrow?15:10
ttxyeah that would be my preference15:10
zaneb++15:10
ttxOr some giant ribbon15:10
ricolinAn arrow hat, that's fun:)15:11
jungleboyjttx ++15:11
ttxAlso I'll make sure the location is mentioned on the schedule15:11
ttxso that we are easily found (hopefully)15:11
jungleboyjThat sounds great.15:11
ricolinzaneb and mugsie are easily found, so maybe I can just stay nearby;)15:12
mugsiewell, according to asettle we are the 2 loudest people on the TC :P15:12
ricolinlen(rico+arrow)<len(zane)15:13
ttxdid we decide on the October meeting day?15:13
mugsiei filled in a survey, but not seen any output15:13
zanebmugsie: tc + board apparently15:13
ttxOur chair is traveling today15:13
mugsieand that was with mordred in the room15:13
ttxevrardjp: let us know asap15:13
zanebI think whatever we choose should be as humiliating as possible, both to make us seem more approachable and also to piss off mnaser :P15:14
* jungleboyj giggles15:14
ttxzaneb: a dunk tank?15:14
jungleboyjOh man!15:15
* zaneb is gonna regret this15:15
mnaser>:(15:15
*** jamesmcarthur has joined #openstack-tc15:16
mnaserso uh, what came out of that name discussion?15:17
mnaseri've been mostly watching from the sidelines but it seems like it has pretty much stalled out15:17
* ricolin just filled the survey15:17
mugsieV->Z ?15:17
zanebwe narrowed it down to one, but there's no consensus on whether we should merge. also it needs a rebase15:18
zaneband ttx added another option for W->Z15:18
mugsieyeah, stalled. not enough of a majority to call it a win yet15:18
zanebactually just W-> I think15:18
ttxV + W->15:18
* ricolin wish will be Vancouver too:)15:19
ttxuntil it's replaced again15:19
openstackgerritMohammed Naser proposed openstack/governance master: check-review-status: update age calc  https://review.opendev.org/68478415:19
ricolinI mean for V15:19
ttxmnaser: https://review.opendev.org/#/c/684688/15:19
ttxmnaser: we arrived to the conclusion that none of the proposed options seems to beat "keep it the same", so we need to come up with new things15:20
mnasergoing back now i actually think the version number ain't so bad15:20
ttxmnaser: boo. That's because you don;t like fun15:20
mugsiewe would have to renumber all the projects as well15:21
mnaserrenumbering projects doesnt seem *that* crazy, and they really don't have to renumber if they dont want to15:21
ttxAlso worth noting: Jonathan Bryce offered to run the naming process if we find it too painful15:21
mugsieor OpenStack 2 would have nova 28, designate 12, and trove 1415:21
* jungleboyj is laughing15:21
mnaserwho knows what version of cyborg ships in openstack newton?15:21
jungleboyjMovie quotes.  That is creative.15:21
ttxso handling hate mail should not be the right reason to drop fun naming15:21
mugsiemnaser: no one, but we know that it is the newton version of cyborg15:21
ttxjungleboyj: I know right15:22
mnaseror heck what cinder version in newton?15:22
ttxcinder 915:22
mnaseri always pull up releases.openstack.org15:22
mugsiewe don't use the numbers *becuase* we have an overall noame for the set of versions15:22
mugsieif you have 2 numbers that will be a complete crapshoot15:22
mugsieoverall name*15:23
ttxwell yes. But saying "Cinder version in Newton is 9" is better than "Cinder version in 8 is 2"15:23
jungleboyjThat would be confusing.15:23
jungleboyjttx: ++15:23
ttxand also not fun at all15:23
mugsiesuper confusing15:23
mnaserso then lets bump em all and call it a day :>15:23
ttxmnaser: that ship has sailed... a looong time ago15:23
mnaseri didn't know ttx had that much fun running releaes name things15:23
mnaser:p15:23
ttxI don't, but I appreciate that others do15:23
mugsieand it was a vocal minority that had issues, and kicked all this off15:24
ttxI should try to find the old ML discussion when we stopped syncing release numbers between components15:24
mugsieit was when we moved from date to numbers right?15:24
mnaseralright well im happy for us to keep having fun as long as we don't hold the keys to what makes it to the poll and what doesn't15:25
ttxyes. All shared same date (except Swift, because Swift is... different)15:25
mnaserbecause that kills the fun for other people15:25
mugsiemnaser: I really don't see that as an issue wither15:25
mugsieeither*15:25
mnaser"hey we're a community, please bring up your release name ideas!"15:25
mnaser"thanks for your suggestions but we're just going to poll on the ones we decide to put in"15:25
ttxwe switched from 2015.1 to version numbers in Liberty15:25
ttxSo Kilo was just an alias to 2015.1 really15:26
mugsie"hey we are a communty, please come with feature suggestions" "thats for those we are going to reduce the number we are going to consider for good reasons"15:26
mugsiethanks for those*15:26
jungleboyjI think we need to keep something unique as it is very much part of OpenStack's identity.15:27
mnaseri'm just not comfortable holding some fancy super power that gets to decide what goes in and what doesn't, which was teh biggest issue last time15:27
jungleboyjLike Android using deserts.15:27
ttxmnaser: agree, taht's why I proposed an objective criteria15:27
mnaserright, yeah15:27
ttxbut it can be fun AND have an objective criteria15:27
jungleboyj:-)15:27
ttxjust have to find a creative space, hence... movie quotes15:27
mugsiemnaser: again, from a vocal minority. 99% of the community couldn't care, and probably thing this whole escapde is a waste of time15:28
jungleboyjmugsie:  This is why we can't have nice things.15:28
mugsieand don't care if we have a "super power"15:28
* mnaser sighs15:29
mnaserok, so unless everyone complains, we ignore a vocal miniority, got it15:29
ttxPeople outside of my bubble assure me that having a naming contest is fun and a good thing15:29
mugsiemnaser: no, but we don';t take a small amount of push back as "the whole community"15:29
ttxAnyway, I think Vancouver gives us some time to get it right, so nu hurry15:30
mugsiettx: ++15:30
mnaserso15:30
mnaserin other subjects15:30
mnaseri've been thinking about how little weird the governance has become in terms of board/openstack/osf projects15:31
jungleboyjttx ++ Good timing on Vancouver and I hope there won't be objections.15:31
mnaserthe tc is defined to be there for the board, but really its made up of nothing but openstack-world members15:31
mriedemrandom butting in since jimmy isn't in -dev, is there a place to see the list of selected forum sessions? i don't see anything about forum filters in the schedule on the summit site.15:31
ttxjamesmcarthur: ^15:32
mriedemoh nvm, i'll go to -dev15:32
jamesmcarthurmriedem: we haven't finalized that yet :)15:32
jamesmcarthurthe Forum Selection Committee is still reviewing15:33
mnaserso i'm thinking we can redefine the openstack tc to be the "openstack foundation tc" which hopefully can provide actual technical things to the board, "formed" by a few members from each osf project15:33
mnaserand then each osf project continues to have their own governance15:33
mnaserso openstack/governance remains what it is, but osf/tc is kata+airship+openstack+zuul15:33
ttxmnaser: so we already have a "cross-leadership" group15:33
mugsiethe board has clearly indicated they didn't want that in the past, but it could be interesting, depending on its scope15:33
zanebmnaser: isn't it up to the board? they already considered something like that and decided not to15:34
ttxit is invited at the Board meeting15:34
ttxI'm not sure we need to do anything from our side15:34
ttxI advised them to not invite every TC member15:34
mnaserthe board doesn't exactly control the tc, does it?15:34
mriedemjamesmcarthur: ack thanks15:34
mnaserthe tc can stay the same thing it is15:34
mnaser*we* can redefine the current tc with its charter and form these subgroups within it15:34
mugsiethe board indicated it wanted the osf projects to be goverened directly from the board15:35
ttxmnaser: I don;t know what authority we'd have to redefine governance for other projects15:35
ttxeven if it is to include them15:35
mnaserthats the thing, we don't redefine the governance for other projects, nor do we want to govern them15:35
ttxThe situation currently is:15:35
mugsiewhat do you see this TC doing that isn't being done?15:35
ttxEach OSF project has their own leadership. Only one of them happens to be mentioned in the bylaws15:35
ttxand that is fine15:35
ttxbecause bylaws changes are expensive enough15:36
* mugsie has ideas, but needs to flesh them out a bit, and knows they would be rejected by the board15:36
ttxI'm also against vanity governance groups15:36
ttxI'm not sure what a "OpenStack OSF TC" would do15:36
ttxRules of governance is that you should have a governance body at levels where decisions need to be taken15:37
mugsiettx: honestly. I think it would have osf projects to a higher standard for inclusion in the osf than the board will15:37
mugsiewould hold*15:37
mnaseroh15:37
mnaser"The management of the technical matters relating to the OpenStack Project shall be managed by the Technical Committee."15:37
mnaseri didnt know it said "the OpenStack Project" there15:37
ttxmugsie: ah, ok, you'd like to create a governance body that vets OSF projects. That is different15:37
ttxmnaser: yes it is very specific15:38
mugsielike, and have thought about are two different things :)15:38
mnaserttx: yes but the idea is to have a group (which is representative of the current groups) to help vet these things15:38
ttxwe kind of have that with the current form. Project Leadership is invited by board and their input taken into account15:39
ttxBut we could formalize it15:39
mnaser(not that i have anything against kata or zuul and keep me in check but i dont remember this happening)15:39
ttxThat would likely end up with silly conflicts as to how many seats openstack should have vs. Kata15:39
ttxbut why not15:39
mnaseri'm not stuck to the idea15:40
ttxThat would be a board decision though. We've gone through a two-year long process to define how projects get added, piloted and confirmed. Not sure it wants to reopen that box so soon15:40
mnaseri'm not attached to it but i was curious what others thought of it15:41
mugsieI raised it in Denver - the feedback at the time was a solid no15:43
mnaserfair enough15:46
mnaseranyone else has any fun topics or did i burn out everyone already? :)15:46
jungleboyj*crickets*15:47
ttxmnaser: how is AnisbleFest?15:49
mnaserttx: it was pretty interesting but i'd have to say like i mentioned earlier, we do things so differently (four opens)15:50
*** diablo_rojo has joined #openstack-tc15:50
mnaserthe contributor summit was nice but it was very much like "this is what we're doing, and this is our roadmap, please align yourself" which REALLY felt weird compared to what we do15:50
mugsieyeah, open source driven by a company with an existing product is always a little weird :)15:51
mugsieunfortunately sometimes people think that is the way to do things when they see sucessful projects15:51
mnaserand in all transparency, this is fine, there's nothing wrong with it, it just really hit how different we do things :)15:52
jungleboyjInteresting.15:52
mugsieyeah, I forget sometimes when I go into other projects though :)15:53
mnaserpeople still use openstack believe it or not :)15:53
mugsieno way15:53
mugsie:P15:53
ricolinI was talking with aspiers about project liasons for self-healing SIG and he mention about got idea from TCs saying that project liasons for SIG is a common topic that we might need to solve for SIGs15:53
*** jamesmcarthur has quit IRC15:54
aspiersYes, not just for SIGs but potentially for every project and WG too15:54
* mugsie keeps meaning to write a stats post about how we are not "dead" or a "telco only" project15:54
ricolinAnyone got any background to share?15:54
*** jamesmcarthur has joined #openstack-tc15:54
*** diablo_rojo has quit IRC15:54
mugsiewe sid we should look at it in Denver afaik15:54
mugsiesaid*15:54
*** diablo_rojo has joined #openstack-tc15:55
* mnaser still has many customers that still very much come who needs openstack15:55
aspiersricolin: I started coding an IRC "profilebot" where you could attach #hashtags to your own IRC nick, and then people could search for overlapping hashtags15:55
mugsiewe could update the tooling to show it, but need a good way of getting the info into the governance repo to map tc<->sig15:55
mnaserand its not out of historical context, its a "well we need some infra and there's no other solution for it"15:55
* jungleboyj still has many customers wanting OpenStack15:55
aspiersricolin: I talked to ttx / fungi / maybe others about it, and IIRC fungi / ttx made the good point that maybe this data belongs somewhere better than an IRC bot15:56
aspierse.g. it could form part of people's OpenStack profile15:56
mugsiemnaser: yeap. even the hyper scale providers solutions for on prem / disconnected are in their nacent forms15:56
*** diablo_rojo__ has joined #openstack-tc15:56
*** diablo_rojo has quit IRC15:57
aspiersricolin: e.g. it could be updated via REST API from a web app or IRC bot or CLI or ...15:57
mugsieaspiers: oh, so people with interests in #designate #self-healing and #apis could tag that on the profile page ?15:57
aspiers"<aspiers> profilebot: search #self-healing #designate"15:58
mugsiethats interesting15:58
aspiers"<profilebot> aspiers: these people have those hashtags: mugsie"15:58
aspiersplenty of scope for hashtags here, e.g. #ptl, #core, #suse, #foundation, #operator etc. etc.15:59
aspiersof course this would be opt-in, but I imagine many people would be happy to opt in15:59
*** jamesmcarthur has quit IRC15:59
ricolinaspiers, I actually like that idea, the problem will be how can we make people to use it:)15:59
aspiersnow we just need fungi to remind me how difficult that might be to host within the OpenStack profiles db :)15:59
aspiersricolin: I don't think it would be too hard, e.g. I found a lot of people started using the new ptgbot features immediately16:00
aspiersricolin: if it delivers real value, people will come16:00
aspiersif not, oh well - we built the wrong thing ;-)16:00
evrardjphey. reading log. On top of my travel, my laptop crashed I had to reset it. I can't reach my work environment yet.16:02
evrardjpglad I have irc on my phone for once.16:02
aspiersevrardjp: Yeah, my cat ate my workstation which is why I can't do any work16:02
ricolinaspiers, I mean I don't think we reveal those functionality enough like a dictionary doc that people can just go and find it, also do we have any doc for new joiner?16:02
aspiersricolin: we could certainly include it in our on-boarding docs and training, yes16:02
jungleboyjSeems like a good idea.16:02
evrardjpaspiers too soon for that joke.16:03
*** diablo_rojo__ is now known as diablo_rojo16:03
aspiersevrardjp: sorry :-o X-D16:03
jungleboyjaspiers: ++16:03
ricolinaspiers, and I got three cats....16:03
aspiersricolin: and n-3 workstations? ;-p16:04
ricolinhahaha16:04
*** e0ne has quit IRC16:06
jungleboyjMust be big cats.  :-)16:10
aspiersAt least they will be after eating workstations ;-)16:10
jungleboyj*Laughing*16:12
*** njohnston has joined #openstack-tc16:31
*** markvoelker has quit IRC16:33
aspiersricolin: ah, I found a tiny remnant of the previous conversation with fungi: http://eavesdrop.openstack.org/irclogs/%23openstack-ptg/%23openstack-ptg.2019-04-29.log.html#t2019-04-29T04:18:2916:39
*** markvoelker has joined #openstack-tc16:41
mugsielooking at the amount of work the volunteers who do k8s releases just had to do for a security release, I am glad we decided not to ship / support openstack binaries from the community16:50
mugsiealso make me really glad for the work the release team have done to make all of this so frictonless (for the projects at least)16:52
*** lpetrut has quit IRC16:53
*** dklyle has quit IRC17:01
*** ricolin has quit IRC17:01
*** dklyle has joined #openstack-tc17:01
*** EmilienM is now known as MniLieEm17:15
*** MniLieEm is now known as EmilienM17:15
*** jamesmcarthur has joined #openstack-tc17:51
*** jamesmcarthur_ has joined #openstack-tc18:09
*** jamesmcarthur has quit IRC18:12
*** e0ne has joined #openstack-tc18:30
*** jamesmcarthur_ has quit IRC18:50
*** e0ne has quit IRC19:25
*** lpetrut has joined #openstack-tc19:47
*** diablo_rojo has quit IRC19:48
*** lpetrut has quit IRC19:58
*** njohnston has quit IRC20:10
*** njohnston has joined #openstack-tc20:10
*** ijolliffe has quit IRC20:20
*** e0ne has joined #openstack-tc20:22
*** e0ne has quit IRC20:24
*** markvoelker has quit IRC21:34
*** nicolasbock has joined #openstack-tc21:45
openstackgerritMerged openstack/governance master: Appointing Nicolas Bock as Designate PTL  https://review.opendev.org/68287821:48
*** markvoelker has joined #openstack-tc21:57
*** diablo_rojo has joined #openstack-tc22:16
*** markvoelker has quit IRC22:27
*** mriedem has quit IRC23:25

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