<span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; background-color: rgb(255, 255, 255); "><div>OE-TSC meeting 4 August, 2011</div><div><br></div><div>Note: There was no meeting on July 28 due to a lack of quorum</div>
<div><br></div><div>Attendees: Richard, Khem, Tom, Mark</div><div>Apologies: Koen</div><div>Note: Jefro</div><div><br></div><div><br></div><div>Minutes:</div><div><br></div><div>01) choose a meeting chair</div><div><br></div>
<div>RP</div><div><br></div><div>02) new topics</div><div><br></div><div>a. request for post 1.1 focus areas for yocto</div><div><br></div><div>03) action items from last week</div><div><br></div><div>--> write up which scripts to use (khem)</div>
<div>done</div><div><br></div><div>05) Status updates</div><div><br></div><div>multilib is painful, but getting there</div><div><br></div><div> - elections</div><div>quiet period</div><div><br></div><div> - oe-core</div>
<div>--> RP to issue an RFC on fray's multilib stuff</div><div>done</div><div> - bsp guidelines</div><div><span style="white-space: pre-wrap; "> </span> </div><div><span style="white-space: pre-wrap; "> </span> - "normal" linux recipe in oe-core that people can bbappend</div>
<div><br></div><div> - metadata layer splitting</div><div><br></div><div> - infrastructure</div><div><br></div><div><br></div><div>Raw Transcript:</div><div><br></div><div><br></div><div>(1:21:46 PM) RP__: Ok, so meeting wise is there much the TSC needs to discuss?</div>
<div>(1:21:57 PM) fray: I don't have any thing specific right now</div><div>(1:22:22 PM) Tartarus: just general status I guess</div><div>(1:22:24 PM) RP__: multilib has been a pain but I think we're getting there with it now</div>
<div>(1:22:53 PM) Jefro: do we want a formal meeting, or just to catch up with status? there were a few action items from last meeting (2 weeks ago)</div><div>(1:23:06 PM) RP__: stablility hasn't been good, again, I think we're hunting down the regressions. The system wide ones should be fixed, there are odd issues remaining build wise</div>
<div>(1:23:18 PM) RP__: Jefro: We could recap the action items?</div><div>(1:23:30 PM) Jefro: yes, coming up in just a sec</div><div>(1:23:52 PM) Tartarus: RP__: where do we stand with more build resources?</div><div>(1:23:56 PM) Tartarus: still "soon" ?</div>
<div>(1:24:04 PM) RP__: (beagleboard is broken on rpm as the long list of package architectures broken rpm, there is an odd rpm locking issue floating around and a qemuarm perl one)</div><div>(1:24:22 PM) RP__: Tartarus: The delivery of LF machines is cut down to the OE ones</div>
<div>(1:24:23 PM) fray: RP__ I sent a patch for beagleboard earlier.. I think it's being validated</div><div>(1:24:45 PM) Tartarus: RP__: didn't quite parse that, again please?</div><div>(1:24:46 PM) RP__: Tartarus: Intel has managed to get some more autobuilder resources which are coming online piece by piece</div>
<div>(1:24:51 PM) fray: (sent a patch to Saul to look into that is)</div><div>(1:24:55 PM) Tartarus: RP__: ok, good</div><div>(1:25:03 PM) RP__: Tartarus: I'd said the LF was going to get us some machines, that won't happen</div>
<div>(1:25:10 PM) ***Tartarus has the Mentor stuff setup and handed off to others, we'll see how it goes</div><div>(1:25:12 PM) RP__: Only the ones promised to OE will</div><div>(1:25:14 PM) Jefro: <a href="http://pastebin.com/qbPGBBKK" target="_blank" style="color: rgb(0, 0, 204); ">http://pastebin.com/qbPGBBKK</a></div>
<div>(1:25:31 PM) khem: RP__: are those also the oe machines that LF was to provide ?</div><div>(1:25:33 PM) RP__: fray: thanks</div><div>(1:25:35 PM) ***Jefro notes, that link is for agenda</div><div>(1:25:46 PM) khem: oh OE will ok</div>
<div>(1:26:01 PM) khem: RP__: any idea timewise when that will happen</div><div>(1:26:22 PM) RP__: khem: Tom King and Mike Wooster are discussing</div><div>(1:26:26 PM) khem: ok</div><div>(1:27:32 PM) khem: I have managed to run core-image-sato builds for all qemus within 24 hrs</div>
<div>(1:27:44 PM) khem: something we would want for daily testing</div><div>(1:29:46 PM) RP__: ok, do we want to work through the agenda?</div><div>(1:29:51 PM) RP__: I can chair</div><div>(1:29:55 PM) ***Jefro notes RP is chair</div>
<div>(1:29:56 PM) RP__: Any additional topics?</div><div>(1:30:10 PM) ***RP__ notes the request for post 1.1 focus areas for yocto</div><div>(1:30:42 PM) RP__: khem: any update on item 3 (write up which scripts to use)?</div>
<div>(1:30:42 PM) ***Jefro notes for minutes</div><div>(1:31:07 PM) RP__: elections, I think we're ok there right now</div><div>(1:31:22 PM) RP__: OE-Core, multilib has moved forwards so we can consider that done</div>
<div>(1:31:35 PM) RP__: So its really down to other status updates :)</div><div>(1:31:46 PM) ***RP__ aims for the record for the official meeting</div><div>(1:32:04 PM) RP__: others can jump in... :)</div><div>(1:32:30 PM) fray: only other thing I can think of is that I still intend to work on the ARM arch.. but havn't had time due to "life"</div>
<div>(1:32:40 PM) fray: in short the changes are minor compared to what is there..</div><div>(1:33:15 PM) RP__: I agree there are some tweaks still needed in places</div><div>(1:33:35 PM) fray: key is I think the big overhaul work is done at this point</div>
<div>(1:33:38 PM) RP__: I really want to get builds working again and then start resolving those issues</div><div>(1:33:54 PM) RP__: Also note that we're going to make a big effort to clean up the various open bugs</div>
<div>(1:34:03 PM) RP__: We've too many of them atm</div><div>(1:34:25 PM) khem: someone was here ..</div><div>(1:34:31 PM) khem: yes my AR is done</div><div>(1:34:44 PM) khem: Paul E replied with the querries</div><div>
(1:34:51 PM) khem: that were raised</div><div>(1:36:03 PM) RP__: SO unless anyone has anything else they want to add/ask/comment on, I think we're done</div></span><br>-- <br>Jeff Osier-Mixon <a href="http://jefro.net/blog" target="_blank">http://jefro.net/blog</a><div>
Yocto Project Community Manager @Intel <a href="http://yoctoproject.org" target="_blank">http://yoctoproject.org</a></div><br>