IRC log for #oe on 20140909

00:05.08*** join/#oe RagBal (~RagBal@54694E34.cm-12-2b.dynamic.ziggo.nl)
00:30.34*** join/#oe stefan_ (~chatzilla@modemcable149.221-203-24.mc.videotron.ca)
00:30.34*** join/#oe Vutral (~ss@vutral.net)
00:30.34*** join/#oe Vutral (~ss@mirbsd/special/Vutral)
00:33.14*** join/#oe systmkor (~systmkor@unaffiliated/systmkor)
00:43.30*** join/#oe Vutral (~ss@mirbsd/special/Vutral)
00:48.12*** join/#oe NvrBst (~NvrBst@gateway/tor-sasl/nvrbst)
00:53.19*** join/#oe RagBal (~RagBal@54694E34.cm-12-2b.dynamic.ziggo.nl)
00:54.22*** join/#oe cbrake (~Thunderbi@cable2-pool191-cs-105.doycomm.com)
01:18.54*** join/#oe Vutral (~ss@mirbsd/special/Vutral)
01:28.50*** join/#oe Vutral_ (~ss@vutral.net)
01:30.06*** join/#oe bzb (~bzb@192-0-226-240.cpe.teksavvy.com)
02:14.47*** join/#oe Crofton (~balister@pool-71-171-45-156.ronkva.east.verizon.net)
02:37.20*** join/#oe DJWillis (~djwillis@cpc2-trow6-2-0-cust204.aztw.cable.virginm.net)
02:37.24*** join/#oe s3v3n62mm2 (~s3v3n62mm@p5DDC244B.dip0.t-ipconnect.de)
02:39.09*** join/#oe fray_ (U2FsdGVkX1@gate.crashing.org)
02:43.21*** join/#oe stefan_ (~chatzilla@bas2-montreal29-1177925150.dsl.bell.ca)
02:53.39*** join/#oe Vutral (~ss@mirbsd/special/Vutral)
03:00.05*** join/#oe Vutral (~ss@mirbsd/special/Vutral)
03:24.20*** join/#oe DJW|Home (~djwillis@cpc2-trow6-2-0-cust204.aztw.cable.virginm.net)
03:31.45*** join/#oe mwester2 (~mwester@184-158-60-27.dyn.centurytel.net)
03:34.36*** join/#oe ndec (~ndec@2001:41d0:8:e632::1)
03:34.51*** join/#oe ndec (~ndec@linaro/ndec)
03:35.18*** join/#oe jonmasters_ (~jcm@edison.jonmasters.org)
03:36.41*** join/#oe nullpupp1 (~dustin@freematrix/staff/nullpuppy)
03:38.29*** join/#oe dvhart_ (~dvhart@134.134.139.72)
03:39.38*** join/#oe Vutral (~ss@mirbsd/special/Vutral)
03:40.12*** join/#oe LarrySteeze|Away (LarrySteez@unaffiliated/larrysteeze)
03:41.36*** join/#oe darkschneider (~gab@93-32-55-33.ip32.fastwebnet.it)
03:42.38*** join/#oe sgw_ (~sgw@c-67-171-230-40.hsd1.wa.comcast.net)
03:42.38*** join/#oe joeythesaint (~joe@209.141.56.162)
03:42.38*** join/#oe ladu (~pi@h52n6-fk-a12.ias.bredband.telia.com)
03:42.38*** join/#oe tgall_foo (~tgall@linaro/tgall-foo)
03:42.38*** join/#oe rtollert (~rtollert@130.164.62.231)
03:42.43*** join/#oe scoutcamper (scoutcampe@nasadmin/webteam/scoutcamper)
03:45.53*** join/#oe ka6sox (ka6sox@cryptkcoding.com)
03:45.53*** join/#oe p0g0_ (~pogo@69.176.56.189.MRTC.static.mrtc.com)
03:45.53*** join/#oe koen (~koen@cl-267.ams-05.nl.sixxs.net)
03:46.30*** join/#oe ka6sox (ka6sox@nasadmin/ka6sox)
03:56.59*** join/#oe GusBricker (~GusBricke@cre1513898.lnk.telstra.net)
04:08.28*** join/#oe kergoth (~kergoth@covenant.kergoth.com)
04:33.23*** join/#oe darknighte (~darknight@pdpc/supporter/professional/darknighte)
04:48.18*** join/#oe nitink (~nitink@134.134.137.71)
04:48.47*** join/#oe ccube (ccube@nx.mindrunner.de)
04:50.26*** join/#oe morphis (morphis@fiona.nas-admin.org)
05:16.31*** join/#oe clio (~andrej@85.159.109.222)
05:16.34*** join/#oe sr105|away (~sr105@65349hfc19.tampabay.res.rr.com)
05:56.26*** join/#oe roric (~roric@c-107ae455.213-3-64736c14.cust.bredbandsbolaget.se)
05:56.27*** join/#oe g1zer0 (~gizero@host168-65-static.12-87-b.business.telecomitalia.it)
06:04.36*** join/#oe jbrianceau_away (uid10952@gateway/web/irccloud.com/x-xvrraqavoeeafalh)
06:07.43*** join/#oe diego_r (~diego@host65-246-static.10-188-b.business.telecomitalia.it)
06:09.06*** join/#oe SorenHolm (~quassel@5634f347.rev.stofanet.dk)
06:12.56*** join/#oe stiandre (~stiandre@109.247.13.242)
06:13.21*** join/#oe DJWillis (~djwillis@cpc2-trow6-2-0-cust204.aztw.cable.virginm.net)
06:17.44*** join/#oe rob_w (~bob@unaffiliated/rob-w/x-1112029)
06:39.57*** join/#oe woglinde (~henning@fb-n15-11.unbelievable-machine.net)
06:40.03*** join/#oe tasslehoff (~Tasslehof@ti0260a430-0319.bb.online.no)
06:40.41*** join/#oe Vutral (~ss@mirbsd/special/Vutral)
06:59.18*** join/#oe systmkor (~systmkor@unaffiliated/systmkor)
07:11.11*** join/#oe ao2 (~ao2@2001:1418:117::1)
07:18.56*** join/#oe florian (~fuchs@Maemo/community/contributor/florian)
07:23.27mckoangood morning
07:36.46woglindehi mckoan
07:41.19mckoanhi woglinde
07:49.25*** join/#oe Jafura (~Jean-Fran@2a02:2788:114:11ce:1115:501e:e319:d87a)
07:54.00*** join/#oe DJW|Home (~djwillis@cpc2-trow6-2-0-cust204.aztw.cable.virginm.net)
07:54.13*** join/#oe ao2 (~ao2@2001:1418:117::1)
07:56.24*** join/#oe fusman (~fahad@110.93.212.98)
08:04.22*** join/#oe kristoffer (~kristoffe@ua-83-227-162-207.cust.bredbandsbolaget.se)
08:05.47*** join/#oe lumag (~lumag@nat-min.mentorg.com)
08:09.20*** join/#oe anarsoul (~anarsoul@178.124.194.242)
08:21.43*** join/#oe dany1 (~Thunderbi@sestofw01.enea.se)
08:28.53*** join/#oe bluelightning (~paul@83.217.123.106)
08:28.55*** join/#oe bluelightning (~paul@pdpc/supporter/professional/bluelightning)
08:32.35bluelightningmorning all
08:36.45mckoanhi bluelightning
08:41.31woglindehi bluelightning
08:41.48*** join/#oe RushPL (~quassel@dragon.rushbase.net)
08:44.52*** join/#oe belen (Adium@nat/intel/x-ewwgquroceacrmin)
08:59.56bluelightninghi mckoan, woglinde
09:21.40*** join/#oe cat5 (5bb7ac44@gateway/web/freenode/ip.91.183.172.68)
09:46.54*** join/#oe GusBricker (~GusBricke@cre1513898.lnk.telstra.net)
09:59.48*** join/#oe stefan_schmidt (~stefan@pD9F78234.dip0.t-ipconnect.de)
10:04.29*** join/#oe fray_ (U2FsdGVkX1@gate.crashing.org)
10:06.22*** join/#oe Vutral (~ss@mirbsd/special/Vutral)
10:07.20*** join/#oe stefan1234 (~stefan@p4FF83CE1.dip0.t-ipconnect.de)
10:07.30heeenis there an easy way to have two versions of a component in the build
10:07.55heeenlike say I want to have qtwayland some upstream version and qtwayland the version we have in the build right now
10:08.14heeenwithout having to juggle local.conf and bb files around
10:08.56bluelightningheeen: not really, without giving them a different name - if they are the same name then PREFERRED_VERSION needs to be used to select the one to be built
10:09.16bluelightning(same PN, I mean)
10:46.27*** join/#oe Vutral (~ss@mirbsd/special/Vutral)
11:16.17*** join/#oe abelloni (~abelloni@128-79-216-6.hfc.dyn.abo.bbox.fr)
11:21.43*** join/#oe roric (~roric@83.140.117.51)
11:24.04heeenhas anyone treied to do static code analysis from out of oe
11:24.09heeen*tried
11:24.21heeenlike http://clang-analyzer.llvm.org/
11:29.55*** join/#oe fray_ (U2FsdGVkX1@gate.crashing.org)
11:30.28*** join/#oe ldnunes (~ldnunes_@177.35.70.10)
11:32.16*** join/#oe Vutral (~ss@mirbsd/special/Vutral)
11:33.28*** join/#oe thaytan (~thaytan@113.94.233.220.static.exetel.com.au)
11:52.20*** join/#oe stefan_ (~chatzilla@bas2-montreal29-1177925150.dsl.bell.ca)
11:54.30*** join/#oe SorenHolm (~quassel@5634f347.rev.stofanet.dk)
11:59.12*** join/#oe tasslehoff (~Tasslehof@ti0260a430-0319.bb.online.no)
12:04.06*** join/#oe sgw_ (~sgw@c-67-171-230-40.hsd1.wa.comcast.net)
12:04.45*** join/#oe ladu (~pi@h52n6-fk-a12.ias.bredband.telia.com)
12:04.58*** join/#oe ldnunes (~ldnunes_@177.35.70.10)
12:05.48*** join/#oe joeythesaint (~joe@209.141.56.162)
12:05.48*** join/#oe tgall_foo (~tgall@linaro/tgall-foo)
12:05.48*** join/#oe rtollert (~rtollert@130.164.62.231)
12:16.45*** join/#oe bryan_ (3df6bac6@gateway/web/freenode/ip.61.246.186.198)
12:17.55bryan_Hi, does anybody worked on open embedded classic to support Citrix Receiver 13
12:18.10bryan_bitbake
12:18.19woglinde?
12:19.04bryan_we need to build a OS image where we need to run Citrix ICAClient 13 version
12:19.26woglindebitbake is a tool to read recipes and classes and do something
12:19.30bryan_we are able to do it using OE-CORE
12:19.42woglindethan use oe-core
12:19.48woglindethere is no support for classic
12:19.53bryan_as it contains latest packages which required by ICAClient 13
12:20.05bryan_but now we need to do it using for OE-Classic
12:20.15woglindewhy?
12:20.20woglindeyou will not be happy
12:21.00bryan_to provide support of latest receiver on old product having OS image built through oe-classic
12:21.50bryan_if u have any idea how can we compile latest recipes of oe-core on oe-classic
12:22.10bryan_and ofcourse there bitbake would be different version
12:22.12Crofton|workbryan_, basically, you will need to backport the recipe to classic
12:22.17bryan_yes
12:22.37Crofton|workI think most people have been forward porting old recipes to oe-core
12:22.56Crofton|workthe number of people using classic is shrinking
12:23.15bryan_e.g. gtk+2.20.1 & above, glibc-2.11.3 & above
12:23.52bryan_yes we know but we need to do it for one existing product
12:24.19bryan_ICAClient 13 require latest gtk and glibc support
12:24.28bryan_while we have old one compiled
12:26.58*** join/#oe dv__ (~quassel@chello062178118086.5.14.vie.surfer.at)
12:28.31*** join/#oe jackmitchell (~Thunderbi@cbnluk-gw0.cambridgebroadband.com)
12:28.59bryan_where can we find recipes for gtk+2.20.1 & above, glibc-2.11.3 & above for openembedded -classic version
12:29.24*** join/#oe woglinde (~henning@fb-n15-11.unbelievable-machine.net)
12:30.51bluelightningbasically what is in OE-Classic is all we have: http://cgit.openembedded.org/openembedded/tree/recipes/gtk+
12:48.19*** join/#oe roric (~roric@83.140.117.51)
12:57.18*** join/#oe Vutral (~ss@mirbsd/special/Vutral)
13:02.45*** join/#oe DJWillis (~djwillis@cpc2-trow6-2-0-cust204.aztw.cable.virginm.net)
13:28.44*** join/#oe ldnunes (~ldnunes_@177.35.70.10)
13:32.26*** join/#oe Rootert (~Rootert@54694E34.cm-12-2b.dynamic.ziggo.nl)
13:32.39*** join/#oe RagBal (~RagBal@54694E34.cm-12-2b.dynamic.ziggo.nl)
13:50.11*** join/#oe darknighte (~darknight@pdpc/supporter/professional/darknighte)
13:51.09*** join/#oe fusman (~fahad@39.42.209.33)
13:53.48*** join/#oe Vutral (~ss@mirbsd/special/Vutral)
14:04.01*** join/#oe nitink (nitink@nat/intel/x-kdkulkettpwptlru)
14:24.05*** join/#oe NvrBst (~NvrBst@gateway/tor-sasl/nvrbst)
14:35.39*** join/#oe DJW|Home (~djwillis@cpc2-trow6-2-0-cust204.aztw.cable.virginm.net)
14:57.04*** join/#oe mwester (~mwester@nslu2-linux/mwester)
14:59.51nerdboymoin
15:02.59*** join/#oe SorenHolm (~quassel@5634f347.rev.stofanet.dk)
15:06.36*** join/#oe cbrake (~Thunderbi@cable2-pool191-cs-105.doycomm.com)
15:09.27*** join/#oe Vutral (~ss@mirbsd/special/Vutral)
15:17.50*** join/#oe fray_ (U2FsdGVkX1@gate.crashing.org)
15:29.12*** join/#oe cbrake (~Thunderbi@cable2-pool191-cs-105.doycomm.com)
15:37.10*** join/#oe ao2 (~ao2@2001:1418:117::1)
15:42.06bluelightningjust a reminder, the OE TSC public meeting starts in this channel in just under 20 minutes; all are welcome to participate
15:43.17*** join/#oe cbrake (~Thunderbi@cable2-pool191-cs-105.doycomm.com)
15:44.03nerdboybluelightning: did you bring donuts?
15:44.20*** join/#oe cbrake (~Thunderbi@cable2-pool191-cs-105.doycomm.com)
15:44.25bluelightningnerdboy: I didn't, sorry :)
15:48.26*** join/#oe fray_ (U2FsdGVkX1@gate.crashing.org)
15:56.02*** join/#oe pabigot (~pab@c-66-41-60-82.hsd1.mn.comcast.net)
15:59.26*** join/#oe keogh (d997f20f@gateway/web/freenode/ip.217.151.242.15)
16:00.05fabokhem: around?
16:00.48fraytime for the first OE-TSC meeting in a while?
16:00.59bluelightningok, so who is here? khem, koen, RP, fray ?
16:01.11bluelightningI guess fray is here...
16:01.18fabokoen is on vac so I doubt he's around
16:01.27bluelightningfabo: ok, thanks
16:01.44bluelightningI think jefro is sick so I guess I can record some minutes
16:02.51bluelightningAFAIK khem should be here shortly
16:02.53bluelightninganyone have anything they would like to raise while we're waiting?
16:03.11*** join/#oe fray_tsc (~mhatle@192.40.192.95)
16:05.17fray_tsc...so very quiet... :)  everyone still in vacation mode (or just catching up from the summer vacations)  ;)
16:05.25bluelightningpossibly yes
16:05.35RPis here
16:05.37*** join/#oe Jefro (~jefro@c-174-62-65-63.hsd1.ca.comcast.net)
16:05.40fray_tsc:)
16:05.51bluelightninghi RP, Jefro
16:06.09Jefrogood morning TSC
16:06.11bluelightningJefro: hope you're feeling OK?
16:06.28Jefrobluelightning thanks - not at all actually, I'll just watch from the corner
16:06.42bluelightningJefro: ok, no worries
16:07.41bluelightningso I don't have an agenda prepared for this meeting
16:08.41fray_tscI figure we'll do the quick what have we been doing, whats coming up (soon).. and then open the floor
16:09.00bluelightningsounds good
16:09.11fray_tscSo what have we been doing then?  :)
16:09.12bluelightningRP: would you mind giving us a status update?
16:09.17RPbluelightning: sure
16:09.20bluelightningfor OE-Core that is
16:09.34RPBasically, we're past the feature freeze point and now into stablisation
16:09.58RPThere are some patches pending which are still in the final review cycles but we're pretty close to release
16:10.10RPwe don't have a lot of bugfixes coming in as yet though :/
16:10.42fray_tscI know I'm still trying to keep up.... :)
16:10.51khemI am here
16:10.55bluelightninghi khem
16:10.56RPany questions?
16:11.06RPor anything anyone wants me to go into more detail on
16:11.21fray_tscI think the biggest recent change has been the eglibc 2.19 -> glibc 2.20 switch.. (and for those that don't know, they're compatible and there shouldn't have to be anything for you to change)  ;)
16:11.39RPI did merge the eglibc -> glibc very late but in the end decided it should go in
16:11.53RPeglibc is a dead end now
16:11.59*** join/#oe cbrake (~Thunderbi@cable2-pool191-cs-105.doycomm.com)
16:12.04khemonly caveat is that we didnt offer an upgrade path
16:12.12RPthanks to Khem's hard work
16:12.18bluelightningkhem: a runtime one you mean?
16:12.22RPkhem: yes, I didn't realise that at the time :/
16:12.25khemyw
16:12.49fray_tscI thought that had been fixed... (appropriate replaces and such added)
16:12.58khemyes, but we can submit that as a followup however, the gconv etc can be hairy
16:14.12fray_tscok.. any questions from anyone (or comments)?
16:14.17bluelightningit may be as easy as a few lines of python dynamically adding RPROVIDES / RREPLACES / RCONFLICTS
16:14.24khemDo we have any updates on locked sstate
16:14.26fray_tscbluelightning ya..
16:15.04RPkhem: the patches are there, there is some discussion on them, I am thinking we should merge them though, assuming we can resolve the current questions
16:15.41fray_tscya, the only remaining issues are how to merge in some of the work on "read-only or error" sstate, and the external signing/validation stuff..
16:16.07fray_tsc(I talked to the submitter this morning about it, and he is working to merge them together)
16:17.21khemfor dev workflow this could help
16:17.30*** join/#oe Vutral (~ss@mirbsd/special/Vutral)
16:17.34bluelightningkhem: it's definitely important for that yes
16:18.07fray_tscya  locked and read-only [or error] are both very useful
16:18.07bluelightningspeaking of dev workflow, the parts I've been working on aren't yet ready to merge; at this stage I'm thinking they probably aren't going to make 1.7
16:18.11RPkhem: agreed, its a key building block of that and I think it would be good to have in the release for that reason
16:18.51khemcurrently, folks want OE layers and sourcecode to have same workflow
16:19.10khemand are resorting to EXTERNALSRC heavily
16:19.18bluelightningwhat I will do is try to get the changes to existing parts of the core (those that are still outstanding, anyway) sent by EOD tomorrow
16:19.39bluelightningthen at least it might be possible to add the rest on via an additional layer if people are interested in playing with it
16:20.25bluelightningkhem: what I've been working on is kind of along those lines
16:21.05fray_tscok.. so does that cover the whats next as well?  (I suspect we need to mention the bug fix "end" dates.. and release dates.. along w/ ELC-E
16:21.18bluelightningpart of it probably yes
16:21.32bluelightningwe should have those dates though
16:22.24RPfray_tsc: basically, next is bug fixing and release. We also need to start to think about 1.8
16:22.33RPdeveloper workflow remains the number one priority afaict
16:22.42fray_tscagreed..
16:23.07fray_tscELC-E is mid October..  so a bunch of folks will be gone for a few days around that period..
16:23.32fray_tscso I hope we have all of the critical issues discovered and resolved before then.. so when ELC-E is over the final build push can commence..  does that match your expectations?
16:23.32bluelightningfray_tsc: not just gone, but hopefully able to meet in person with other folks who are going :)
16:23.38khemyes,
16:23.46fray_tscyup.. gone as in, probably not online and merging code.. :)
16:23.54bluelightningright, indeed
16:24.08fray_tsc(I'll be at ELC-E BTW)
16:24.14khemI have posted a followup for glibc now that 2.20 has been branched out
16:24.21bluelightningI'm not yet sure if I will be able to go
16:24.35khemso far I will be there too, unless germany decides not to give me a visa
16:24.45RPis planning to go
16:25.18RPfray_tsc: I'm kind of hoping we might be able to release before it
16:25.38fray_tscI do too.. ;)  but I'm leaving a margin of error in my expectations.. ;)
16:25.49khemI think something we need to think about it have editor itegrated into toaster
16:25.52fray_tscso when should people plan to have all of their pet bugs fixed?  First week of Oct?
16:25.56fray_tscor is that too late?
16:26.09RPfray_tsc: yes
16:26.15khemsomeway for folks to use UIs to configure as well as edit code in future
16:26.32RPfray_tsc: at this point in the release cycle we reserve the right to release the first good RC we get
16:26.47bluelightningkhem: we don't have plans to add that at the moment; it'd be nice but we really need extra help to do things like that
16:27.12RPkhem: it needs developers to do it and there just simply aren't enough people with time to work on it to make it happen
16:27.32RPfrom a conceptual standpoint, we all like the idea
16:27.37bluelightningagreed
16:28.04RPtechnologically there aren't major issues either
16:28.09RPchallenges, sure :)
16:28.57bluelightningthe base is all there now - as of recently you can even start builds from toaster (though that code probably needs some stabilisation, it is merged)
16:30.50bluelightningok, so if there's nothing further on that we can open it up to the floor - anything anyone would like to discuss?
16:30.54bluelightningdon't be shy ;)
16:30.59fray_tscok..  got one thing (open floor conversation)
16:31.06bluelightningfire away
16:31.37fray_tscrecently there was a post to the oe-core list from someone complaining we've gotten to nit-picky to new developers, causing them to not want to contribute..  so my question is.. 1) have we gotten too nitpicky?   2) what should we change if it's a concern..
16:31.54fray_tscmy PERSONAL feelings is we haven't gotten too nitpicky.. it can get annoying, but it's keeping the quality level up
16:32.08fray_tsc(even though I fall victim to forgotten upstream-status and others occasionally)
16:33.11bluelightningI'm not sure we've got too nitpicky, but I have been told that there have been instances where people have felt that review replies could be a little less terse
16:33.36bluelightningI also think that we need more people reviewing so that we can get any review to the submitter as early as possible
16:33.57fray_tscI certainly don't disagree with either of those..
16:34.14bluelightningif people feel like some of this is nitpicking, it's amplified 100x by such comments coming back a week or two after the patch has been sent
16:35.13bluelightninganyone can reply reviewing patches on the mailing list and I would encourage everyone that feels inclined to do so
16:35.20fray_tscare we at a point in the YP where (post 1.7) we need to find subsystem "maintainers".. people who become more responsible for the first round of comments before RP has to look at it?
16:35.40bluelightningbut if the submitter is someone who doesn't necessarily have a way of knowing better, please be polite ;)
16:35.41fray_tscabsolutely the community as a whole I hope is reviewing changes.. but I know I skip things in systems I'm not directly knowledgable on..
16:37.42bluelightningright, I think we all do
16:37.45fray_tsccommunity feedback?
16:37.50pabigotFWIW: IMO the expectations for contributions to YP/OE are very clearly documented, and are reasonable and justifiable for preserving quality and
16:37.51pabigotmaintainability.
16:37.57pabigotIt can be hard for newcomers to calibrate their expectations for responsiveness and turnaround; I don't know of a resolution other than watching the lists for a while to see how things are done.
16:39.03fray_tscmy personal experience is every community is different.. in this one, if you don't get a response it's the submitters responsibility to ping asking..  (people get busy.. especially in the summer and near a release time)
16:39.30fray_tscsome communities (especially smaller ones) send and forget seems to work, but I tell the people I work with thats not the case here..
16:40.51bluelightningI do hope we have at least the possibility to improve patchwork to the point where you can see what's happened to your patch
16:42.44bluelightningthere's some folks here doing some work upstream on patchwork, I hope that will result in improved usability for us
16:44.09bluelightningif it were at least able to accurately track the patch queue (at the moment it misses some posted patches and misses the merges of others), and possibly even provide a way to notify submitters if they wish, that would at least cut down the pings where the patch has already been merged
16:45.30fabosome use cases are questionable. I do suspect you haven't been affected by one of those nitpick comments.
16:46.40fabofwiw, I'm one the guy replying on this particular thread. as a contributor, I think we should look at both sides and obviously frustrations for both
16:47.35faboI don't think it's acceptable to have a patch sitting for 2 weeks without a feedback
16:47.56fabothere's an obvious lack of manpower
16:48.04bluelightningfabo: it's definitely a balance, and ideally I would have to agree
16:48.47bluelightningre manpower we can only really hope to improve the situation if more folks get involved with review and maintainership
16:49.49bluelightningwe're open to suggestions though if you have any...
16:50.23faboI'm afraid there's no magic here. more eyes and people to step up
16:52.57bluelightningindeed
16:53.22bluelightningok, so there's 7 mins left, anything else people would like to talk about?
16:55.00Crofton|workI'm late
16:55.20Crofton|workmy only comment is we should all try to scan patches for obvious commit message issues
16:55.31Crofton|worksince that rquires little expertise
16:56.58*** join/#oe stiandre (~stiandre@214.97.45.31.customer.cdi.no)
17:01.10fray_tscseems like thats everything then..
17:01.17fray_tscthanks for the input..
17:01.48fraygoes back to his regular IRC client.. ;)
17:03.02*** part/#oe pabigot (~pab@c-66-41-60-82.hsd1.mn.comcast.net)
17:05.22khemwell we should look at gerrit
17:05.33khemfor better patch workflow management
17:05.44*** join/#oe scot (~scot@130.164.62.160)
17:05.53*** join/#oe roric (~roric@c-107ae455.213-3-64736c14.cust.bredbandsbolaget.se)
17:06.38*** part/#oe keogh (d997f20f@gateway/web/freenode/ip.217.151.242.15)
17:07.11*** join/#oe Jafura (~Jean-Fran@ptr-178-50-67-4.dyn.mobistar.be)
17:10.12bluelightningkhem: gerrit makes some pretty major changes to the maintainer workflow, I don't think RP is keen on it for that reason
17:14.19khemit doess but its a well known workflow
17:14.46khemIt has good audit trail
17:14.55khemand good integration with automation
17:15.10khemso folks can really track their patch at each step
17:15.30khemright now there is no obvious links like that
17:15.49khemwe see a patch is in master-next and whats happening with it there after is less obvious
17:19.52kheme.g. yocto ABs output would be reported back to gerrit reviews etc. are good things
17:23.50*** join/#oe fray_ (U2FsdGVkX1@gate.crashing.org)
17:25.33Crofton|workRP, doesn't scale
17:35.41*** join/#oe jackmitch|home (~Thunderbi@cpc22-cmbg15-2-0-cust21.5-4.cable.virginm.net)
17:45.18*** join/#oe roric (~roric@c-107ae455.213-3-64736c14.cust.bredbandsbolaget.se)
17:49.29*** join/#oe florian (~fuchs@Maemo/community/contributor/florian)
17:50.06*** join/#oe darkschneider (~gab@93-32-55-33.ip32.fastwebnet.it)
17:50.36*** join/#oe Vutral (~ss@mirbsd/special/Vutral)
18:02.13*** join/#oe kroon (~kroon@host-95-199-27-182.mobileonline.telia.com)
18:04.19*** join/#oe nslu2-log (~nslu2-log@140.211.169.184)
18:05.41kroonAnyone used nemiver+OE sdk's gdb, as a grapical frontend for remote debugging ?
18:06.34kroonOr does everyone use Eclipse
18:15.57*** join/#oe SorenHolm (~quassel@5634f347.rev.stofanet.dk)
18:17.57*** join/#oe roric (~roric@c-107ae455.213-3-64736c14.cust.bredbandsbolaget.se)
18:38.43dv__Jama sure has been off for a long time now
18:52.53*** join/#oe Jefro (~jefro@c-174-62-65-63.hsd1.ca.comcast.net)
18:53.20khemdv__: yes do you need something urgent ?
19:15.52*** join/#oe darknighte (~darknight@75.108.25.58)
19:17.33RPkhem: fwiw I tried using gerrit for a different project recently. I have to say that whilst I've disliked it in the past, I now passionately hate it :(
19:17.53*** join/#oe belen (~Adium@190.227.187.81.in-addr.arpa)
19:18.04khemRP: heh, quite opposite experience for me.
19:18.07RPI appreciate there are some good sides to it but they are outweighed for example by the horrible UI
19:18.11khemI liked the audit trail
19:18.16khemand verification builds
19:18.29khemthe tooling you can automate with it is amazing
19:19.03khembut OE is not a typical project suitable
19:19.12khemfor gerrit I observed
19:19.20RPkhem: to be quite blunt, its irrelevant if the UI itself is no good
19:19.49khemRP: yes UI is not best but with 2.9 its lot better
19:19.53RPI didn't feel "oh, this thing needs some minor fixups", I just could not do what I needed to be able to do with it :(
19:21.07RPkhem: I just checked and this was 2.9 :(
19:21.16*** join/#oe Jafura (~Jean-Fran@ptr-178-50-84-115.dyn.mobistar.be)
19:21.57*** join/#oe darknighte_ (~darknight@pdpc/supporter/professional/darknighte)
19:40.42*** join/#oe jackmitch|home (~Thunderbi@cpc22-cmbg15-2-0-cust21.5-4.cable.virginm.net)
19:41.19khemRP: hmmm I liked web interface of reviewboard to be more intuitive
19:41.33khembut gerrit I discounted due to value it offerred otherwsie
19:59.45*** join/#oe systmkor (~systmkor@unaffiliated/systmkor)
20:17.25*** join/#oe Jafura (~Jean-Fran@2a02:2788:114:11ce:255f:41e0:c404:8b4e)
20:17.33*** join/#oe systmkor (~systmkor@unaffiliated/systmkor)
20:26.32*** join/#oe nitink (~nitink@134.134.137.71)
20:34.07*** join/#oe s3v3n62mm (~s3v3n62mm@p5DDC244B.dip0.t-ipconnect.de)
20:39.31*** join/#oe stefan_ (~chatzilla@bas2-montreal29-1177925150.dsl.bell.ca)
20:41.07*** join/#oe stefan_ (~chatzilla@bas2-montreal29-1177925150.dsl.bell.ca)
20:49.44*** join/#oe ftagius (~fagius@99-178-168-231.lightspeed.rlghnc.sbcglobal.net)
20:59.09*** join/#oe jackmitch|home (~Thunderbi@cpc22-cmbg15-2-0-cust21.5-4.cable.virginm.net)
21:01.32*** join/#oe eFfeM (~frans@c73189.upc-c.chello.nl)
21:02.27*** join/#oe joaohfreitas (~joaohf@201.53.216.189)
21:03.11*** join/#oe kroon (~kroon@89-253-118-72.customers.ownit.se)
21:08.58*** join/#oe Vutral (~ss@mirbsd/special/Vutral)
21:19.17*** part/#oe eFfeM (~frans@c73189.upc-c.chello.nl)
21:40.01*** join/#oe stefan_schmidt (~stefan@p4FF82859.dip0.t-ipconnect.de)
22:04.20*** join/#oe hrw (~hrw@redhat/hrw)
22:16.41*** join/#oe bluelightning (~paul@pdpc/supporter/professional/bluelightning)
22:20.10*** join/#oe darknighte (~darknight@pdpc/supporter/professional/darknighte)
22:40.55*** join/#oe systmkor (~systmkor@unaffiliated/systmkor)
22:41.16*** join/#oe Coli (d8f93106@gateway/web/freenode/ip.216.249.49.6)
22:49.02*** join/#oe jbrianceau_away (uid10952@gateway/web/irccloud.com/x-wtblfuytorhnbrez)
23:01.39*** join/#oe stiandre (~stiandre@214.97.45.31.customer.cdi.no)
23:43.45*** join/#oe Vutral (~ss@mirbsd/special/Vutral)

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