IRC log for #oe on 20200703

04:35.32*** join/#oe davidlt (~davidlt@78-63-27-146.static.zebra.lt)
04:56.34*** join/#oe cpriouzeau (~cpriouzea@165.225.94.96)
05:16.53*** join/#oe kroon (~kroon@213.185.29.22)
05:36.47*** join/#oe AndersD (~AndersD@h-98-128-162-82.NA.cust.bahnhof.se)
05:59.17*** join/#oe sstiller (~sstiller@b2b-94-79-174-114.unitymedia.biz)
06:02.48*** join/#oe rob_w (~bob@unaffiliated/rob-w/x-1112029)
06:09.37*** join/#oe ao2 (~ao2@host-87-18-91-100.retail.telecomitalia.it)
06:11.46*** join/#oe leon-anavi (~Leon@78.130.197.211)
06:39.58Letothe2ndarmpi\m/ O \m/
06:40.11Letothe2ndarmpit, even :)
07:07.41*** join/#oe hpsy (~hpsy@85.203.15.8)
07:12.13*** join/#oe nrossi (nrossimatr@gateway/shell/matrix.org/x-rqdbhfgcfcrjnfax)
07:47.07*** join/#oe yann (~yann@91-170-159-152.subs.proxad.net)
08:32.48*** join/#oe florian (~florian_k@Maemo/community/contributor/florian)
10:15.43Crofton|cloudurg that went better than expected
10:17.02Letothe2ndCrofton|cloud: getting up this morning, or what?
10:17.22Crofton|cloudlaughs
10:17.23Crofton|cloudELC
10:17.41Crofton|cloudstill I missed finding the people we didn't know who use OE
10:17.50Letothe2ndhehe
10:18.08Letothe2ndi found it much more ploarizing than a physical event
10:18.32Crofton|cloudhow so?
10:18.39Letothe2ndbut, i think we've had extremely good reach with YPDD
10:18.46Crofton|cloudyeah
10:18.50Crofton|cloudthat had a lot of focus
10:19.33Crofton|cloudwhat was lacking was randomg conversations outside the community, those were hard to find
10:19.56Letothe2ndwell in RL, some things work halfways, others a little less, but hardly ever something is completely awesome or utter crap. this time, i've found the video presentations and all really, really good, and the rest of that conference system to be the utmost worst thing i've ever tried to log into
10:20.45Crofton|cloudwell yes, there was that
10:21.07Crofton|cloudI think the intern worked on the booth stuff :)
10:22.05Letothe2ndno idea what the person in charge smoked, but it wasn't the good stuff
10:23.59Letothe2ndif I had to just throw around ideas, then I would say: in the virtual world, we are not restricted to piggyback YPDD onto OSS/ELC and should really try to ramp it up.
10:31.14Letothe2ndi mean, i have no insight into the manpower/financial effort involved. so explicitly just fantasizing: have an YPDD quarterly, one for each timezone group 1) oceania/japan 2) india 3) europe/africa 4) america
10:37.25*** join/#oe nagua (~nicolas@i5E86668F.versanet.de)
11:10.44Letothe2ndCrofton|cloud: ?
11:24.42Crofton|cloudyeah
11:25.01Letothe2ndCrofton|cloud: usually you tell me where i'm wrong real quick, so i wondered :)
11:25.08Crofton|cloudthe TZ shift idea is interesting
11:25.14Crofton|cloudbreakfast
11:25.53Crofton|cloudThe TZ canbe hard for presenters though. In my fantasy world, I shack up somewhere in the EU for ELCE to avoid gettig up at 0300
11:25.56Letothe2ndCrofton|cloud: jsut speaking from my sessions and the folks reacting to it, a lot of them are in india or the middle east. we should really think of that as an "emerging market"  for us.
11:26.17Crofton|cloudyeah
11:26.38Letothe2ndi actually don't think the TZ shift is so complicated.
11:27.01Letothe2ndgiven a little shuffle, i could totally present in all the cases
11:36.45Crofton|cloudespecially for one day
11:38.36Letothe2ndeactly. at worst, its one time get up early or stay up late.
11:48.06*** join/#oe berton (~berton@181.220.84.90)
12:08.56*** join/#oe mihai (~mihai@unaffiliated/mihai)
13:56.25khemCrofton|cloud: for that we should have encouraged them to speak on channels
13:57.13khemnewbies miss context and immediately feel discourages if a implicit contextual discussions are ongoing
14:03.16khemhttps://www.gamingonlinux.com/2020/06/cadmus-is-a-new-linux-ui-for-managing-microphone-noise-supression
14:03.33khemespecially for aesh29
14:03.35khem:)
14:04.11*** join/#oe sakoman (~steve@rrcs-66-91-142-162.west.biz.rr.com)
14:16.41smurraymight be tougher on staff, but maybe having an explicitly named lab help channel and perhaps a couple of named topic channels might keep things more followable for newcomers
14:24.07khemjonmason: https://git.yoctoproject.org/cgit/cgit.cgi/meta-arm/commit/?id=6f613362f3c1a9376a31a95f1751d59aa09947e9 added meta-arm to depend on meta-arm-toolchain I wonder if trusted-firmware-m should be part of common layer or is meta-arm-bsp better place for it
14:25.48khemsmurray: long ago I was trying to participate in freebsd community, so I know how it is to be one that side of the fence ( and you see I am not in freebsd community )
14:29.48jonmasonkhem: that was the discussion that was happening.  The "solution" is to get multiconfig working so that there is no requirement to use that specific toolchain (and thus remove the dependency)
14:30.46khemjonmason: ok so for now I have to add that binarry toolchain layer ?
14:31.02khemI hope it does not interfere
14:31.10smurraykhem: heh, I mean specifically if something's set up for dev day or similar again ;)
14:31.53smurraykhem: I should have tagged that for Crofton|cloud
14:32.39jonmasonkhem: there are no deps in the toolchain layer on anything else.  And Ross's highest priority is getting multiconfig working (until something else hotter comes along)
14:33.04jonmasonI hate we had to do it that way
14:33.09khemjonmason: yeah, I am one hit away from dropping meta-arm from yoe
14:33.45smurraymaybe put tf-m in a dynamic-layers dir for now?
14:34.11Crofton|cloudsmurray: khem yeah we need to remember to use thinks like mattermost better
14:34.23Crofton|cloudwon't speak teh name of the closed source option
14:34.42jonmasonkhem: hahaha.  That is fair.  I welcome feedback
14:36.13smurrayjonmason: with my AGL hat on, it'll also be quite annoying there to need add that layer to the repo manifest if we try to bump meta-arm
14:36.24smurrayjonmason: especially if it's just temporary
14:38.06smurrayjonmason: imo might be worth some hackery to avoid putting that on people who don't need tf-m, e.g. dynamic layer it wrt meta-arm-toolchain for now, or some BBMASK hack
14:39.33jonmasonsmurray: I believe JPEW was saying something similar.  My cheap cop-out is "patches welcome".
14:39.58jonmasonI believe having tf-m in meta-arm/meta-arm is the correct place
14:40.59jonmasonso it's just a matter of making it right
14:41.28smurrayI'm okay with that, but perhaps just don't add that layer dep for now and document it being needed for the recipe instead
14:43.05jonmasonmeta-arm needs users to be useful.  So if this is a show-stopper I'll do as you suggest and add a comment in there until Ross has a better fix
14:44.24khemjonmason: I think move the recipes that need it under dynamic-layers and it will magically disappear for folks who dont have meta-arm-toolchain in layer mix
14:44.31khemLet me hack it
14:44.35jonmasonI also humbly request people subscribe to the meta-arm mailing list to prevent me from doing things like this in the future :)
14:44.46jonmasonkhem: sounds great, thanks
14:44.57smurraymy bad, I wasn't keeping up this week due to ELC and YPDD
14:45.33smurrayI am subscribed ;)
14:46.31jonmasonsmurray: not your fault.  It was a crazy week.  I think people thought that since no one traveled for the conference that they can make us do a normal week of work in addition to the conference.
14:47.27smurrayjonmason: I tried to do some work, but there was enough multi-tasking just keeping up with the conf that it was mostly a non-starter
14:48.10jonmasonI feel bad for rburton because I think he worked a full UK day, then had the conference until midnight
14:48.51smurrayyikes
15:04.39khemCrofton|cloud: its not only tools, but also I feel like we have to be more welcoming and inclusive
15:05.37Crofton|cloudYeah, we forget how we look sometimes
15:08.25khemjonmason:I sent a patch to ml, my builder perhaps is happier now
15:09.05jonmasonthanks!
15:09.43khemfeels like meta-arm janitor
15:17.44jonmasonkhem: more like meta-arm septic tank emptier ;-)
15:17.52jonmasonrotorooter
15:21.06jonmasonkhem: if you saw the turds we didn't let out....
15:22.13armpithey! easy on my namesake layer
15:25.05*** join/#oe halstead_ (~halstead@drupal.org/user/301087/view)
15:25.46*** join/#oe adelcast (~adelcast@2605:6000:101c:3b5:c255:6326:5d60:1a29)
15:26.23jonmasonit's crappy because of the maintainer, and I've been chastised recently about being too lax
15:30.57*** join/#oe thaytan (~thaytan@180-150-69-32.b49645.syd.nbn.aussiebb.net)
15:32.54smurrayarmpit: what does meta-pit support?
15:37.12armpitsmurray, all the bad things
15:39.44*** join/#oe davidlt (~davidlt@m213-103-61-132.cust.tele2.lt)
15:53.59smurrayarmpit: I feel I should make a joke about it being a BSP layer ;)
17:11.01*** join/#oe RobertBerger (~rber@ppp-2-86-138-91.home.otenet.gr)
17:11.27*** join/#oe nerdboy (~sarnold@gentoo/developer/nerdboy)
17:32.57*** join/#oe florian__ (~florian_k@Maemo/community/contributor/florian)
18:47.43*** join/#oe davidlt (~davidlt@m213-103-61-132.cust.tele2.lt)
19:30.36Letothe2ndarmpit: do we already have a list for meta-pit?
19:45.22*** join/#oe ao2 (~ao2@host-87-18-91-100.retail.telecomitalia.it)
19:45.50khemjonmason: heh true
19:46.17khemyeah meta-arm{pit} ;)
19:47.08Letothe2ndlikes!
19:50.52*** join/#oe khem (~khem@unaffiliated/khem)
20:07.24*** join/#oe davidlt (~davidlt@m213-103-61-132.cust.tele2.lt)
20:36.04armpitbitbake stinky-image-minimal
22:53.08*** join/#oe JaMa (~martin@109.238.218.228)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.