<span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; background-color: rgb(255, 255, 255); "><div>These minutes will be available soon on the OE wiki</div><div><br></div><div>MINUTES: OE-TSC meeting 29-Sep-2011</div>
<div><br></div><div>Attending: Mark, Richard, Khem</div><div>Apologies: Tom, Koen</div><div>Notes: Jefro</div><div><br></div><div>--------------------------------------------------------</div><div>Agenda</div><div><br></div>
<div>1. pick a moderator</div><div>2. agenda items</div><div> a. continuing minutes issues</div><div> b. patchwork replacement</div><div> c. patches to classic OE, tracking into layers?</div><div><br></div><div>3. status on open subjects</div>
<div> a. release</div><div> b. git</div><div> </div><div>--------------------------------------------------------</div><div>1. Jefro</div><div><br></div><div>2. a. some minutes not making it to mailing list, Jefro to post on wiki</div>
<div> b. yocto evaluating gerrit, possible patchwork replacement for OE, khem will research</div><div> c. acknowledged need for more resources, oe-core being tracked well</div><div><br></div><div>3. a. release coming together</div>
<div> b. git moving to its final destination we expect no use visible problems except for RP</div><div> khem ok's RPs changes, fray hasn't looked yet</div><div><br></div><div>--------------------------------------------------------</div>
<div>Raw Transcript</div><div><br></div><div>(12:57:11 PM) khem: I have to be go at 1:30 though which is half way</div><div>(1:04:28 PM) khem: koen is travelling last time he said</div><div>(1:04:42 PM) khem: but I dont remember if he was to be back today</div>
<div>(1:04:44 PM) fray: sorry I'm late.. just got home</div><div>(1:04:45 PM) khem: or wednesday</div><div>(1:05:06 PM) fray: (was at ESC Boston giving a Yocto presentation... and yes I mentioned oe and oe-core as well) ;)</div>
<div>(1:05:20 PM) khem: hello fray</div><div>(1:05:32 PM) khem: how was ESC</div><div>(1:05:35 PM) ***RP__ has put off some stuff to be here now so I hope this is going to be worthwhile...</div><div>(1:05:51 PM) RP__: Jefro: Did you manage to get wiki admin rights?</div>
<div>(1:06:02 PM) RP__: well, edit rights even</div><div>(1:06:10 PM) khem: RP__: is it for oe.wiki</div><div>(1:06:13 PM) Jefro: RP__ not yet - still working on that</div><div>(1:06:17 PM) RP__: khem: yes</div><div>(1:06:20 PM) Jefro: khem do you happen to have admin rights?</div>
<div>(1:06:30 PM) RP__: Jefro: You could ask khem/fray ;-)</div><div>(1:06:33 PM) khem: Jeffro, I dont think so</div><div>(1:06:37 PM) RP__: and someone could bump me whilst they're at it</div><div>(1:06:40 PM) RP__: khem: you do</div>
<div>(1:06:55 PM) fray: I don't have admin rights either..</div><div>(1:06:57 PM) khem: Jefro: but I do have some super cow powers</div><div>(1:07:19 PM) khem: so Jefro needs to be added ?</div><div>(1:07:34 PM) RP__: <a href="http://wiki.openembedded.org/index.php?title=Special:ListUsers&group=bureaucrat" target="_blank" style="color: rgb(0, 0, 204); ">http://wiki.openembedded.org/index.php?title=Special:ListUsers&group=bureaucrat</a></div>
<div>(1:07:36 PM) Jefro: I have an account, I just need to have editing/creating rights</div><div>(1:07:46 PM) Jefro: and Richard needs to have his rights bumped</div><div>(1:07:47 PM) khem: ok</div><div>(1:07:53 PM) fray: for editing Khem found the right person to bump me up</div>
<div>(1:07:57 PM) khem: I can take it to next level</div><div>(1:08:00 PM) khem: consider it done</div><div>(1:08:00 PM) Jefro: if you think he is trustworthy, that is</div><div>(1:08:10 PM) RP__: khem: can you bump me whilst you're in there please</div>
<div>(1:08:13 PM) Jefro: khem awesome, thanks</div><div>(1:08:32 PM) RP__: people keep asking me for things...</div><div>(1:08:42 PM) khem: RP__: if I figure out yes</div><div>(1:09:45 PM) Jefro: with three people there is a quorum, do you guys want to meet?</div>
<div>(1:09:50 PM) RP__: ok, so we have enough for a quorum but we lose khem in 20 mins</div><div>(1:09:58 PM) RP__: what do we need to talk about?</div><div>(1:10:07 PM) Jefro: better be a quick one. agenda items?</div><div>
(1:10:27 PM) RP__: I think Phil's question about minutes and so forth needs an answer. I think Jefro is on that and my thanks for taking care of it :)</div><div>(1:11:02 PM) RP__: The release seems to be coming together and I'm feeling better about the quality</div>
<div>(1:11:04 PM) fray: I thought we had released all of the minutes for the meetings we -did- have.. there were a number where we didn't achive quorum</div><div>(1:11:12 PM) khem: Jefro whats your login</div><div>(1:11:13 PM) RP__: I'm trying to communicate the situation better on the mailing lists</div>
<div>(1:11:18 PM) RP__: summaries and so on</div><div>(1:11:23 PM) Jefro: RP__ yes, I am ready to post all the minutes since March, just need a login. khem: Jefro</div><div>(1:11:59 PM) Jefro: there are two instances where email I sent to the lists didn't get disseminated</div>
<div>(1:11:59 PM) RP__: fray: I don't think they've been making the lists. Jefro needs to figure out why. You're not posting to the <a href="mailto:lists@linuxtogo.org" target="_blank" style="color: rgb(0, 0, 204); ">lists@linuxtogo.org</a> address are you?</div>
<div>(1:12:26 PM) Jefro: it was either pilot error on my part, or something clogged in the ethertubes. I post to..</div><div>(1:13:03 PM) Jefro: openembedded-core <<a href="mailto:openembedded-core@lists.openembedded.org" target="_blank" style="color: rgb(0, 0, 204); ">openembedded-core@lists.openembedded.org</a>>,</div>
<div>(1:13:03 PM) Jefro: <a href="mailto:openembedded-devel@lists.openembedded.org" target="_blank" style="color: rgb(0, 0, 204); ">openembedded-devel@lists.openembedded.org</a>,</div><div>(1:13:03 PM) Jefro: tsc <<a href="mailto:tsc@lists.openembedded.org" target="_blank" style="color: rgb(0, 0, 204); ">tsc@lists.openembedded.org</a>></div>
<div>(1:13:29 PM) RP__: those should be fine</div><div>(1:13:38 PM) RP__: posting from the address you're subbed with?</div><div>(1:13:47 PM) Jefro: yes: <a href="mailto:jefro@jefro.net" target="_blank" style="color: rgb(0, 0, 204); ">jefro@jefro.net</a></div>
<div>(1:14:29 PM) RP__: Jefro: dunno then. we need to watch this though</div><div>(1:14:44 PM) Jefro: the two that appear to be missing from the lists are in my Sent box, so make of that what you will. (as official signed-off versions) I will be adding them to the wiki from here on out, and will double-check the archive each week to make sure it has gone out.</div>
<div>(1:15:00 PM) Jefro: I have had mysterious email issues before. Maybe I pissed off the google gods.</div><div>(1:15:15 PM) fray: ...maybe google doesn't like OE? ;)</div><div>(1:15:55 PM) khem: I would like to bring up have patchwork replaced with something</div>
<div>(1:16:53 PM) Jefro: I have an AR to make sure minutes are settled & will report back next week. Should we move to khem's issues with patchwork?</div><div>(1:17:03 PM) fray: ya</div><div>(1:17:11 PM) khem: Jefro: you should be good with wiki now</div>
<div>(1:17:23 PM) RP__: Yocto people plan to evaluate gerrit</div><div>(1:17:54 PM) RP__: we're waiting on sysadmin resources to set it up. We've spent out sysadmin credit getting the <a href="http://kernel.org/linuxfoundation" target="_blank" style="color: rgb(0, 0, 204); ">kernel.org/linuxfoundation</a> server mess resoled</div>
<div>(1:17:58 PM) khem: since we are moving the OE services to a new server it could be that we drop patchwork and not go through hassles of setting it up</div><div>(1:17:58 PM) RP__: resolved</div><div>(1:19:06 PM) khem: koen uses patchwork for his maintenance activity so some alternative would be nice to have</div>
<div>(1:19:25 PM) khem: ok gerrit seems a plausible thing</div><div>(1:19:54 PM) khem: I have not used it thus far but may be we should plan on setting some pilot project using it</div><div>(1:20:26 PM) RP__: khem: that is yocto's plan</div>
<div>(1:20:53 PM) khem: RP__: ok</div><div>(1:21:39 PM) fray: just from an OE admin resources point of view.. does it make sense to let the Yocto folks get it going there and then see if it's useful and bring it into OE if it is? (or do we not want to wait on Yocto to do a first pilot?)</div>
<div>(1:22:11 PM) khem: depends when yocto has pilots going</div><div>(1:22:21 PM) khem: I would prefer something soon</div><div>(1:22:38 PM) ***RP__ suspects it would be early novemeber</div><div>(1:22:53 PM) RP__: release takes preference right now</div>
<div>(1:22:59 PM) khem: ok</div><div>(1:23:19 PM) khem: I will read about it in coming days</div><div>(1:23:24 PM) khem: just to understand the beast</div><div>(1:24:07 PM) RP__: khem: sounds like a plan</div><div>(1:24:14 PM) RP__: Anything else we need to touch upon?</div>
<div>(1:25:05 PM) khem: RP__: folks post patches to oe against classic oe tree I dont know if we are doing a good job of tracking them into layers</div><div>(1:25:44 PM) RP__: khem: I'm only tracking oe-core atm, not enough bandwidth to do more</div>
<div>(1:26:21 PM) fray: likewise, for the most part I'm tracking oe-core, and specific other things I notice like prelink and toolchain issues..</div><div>(1:26:32 PM) khem: RP__: if someone could do once a week review of oe-dev ml for such patches would suffice</div>
<div>(1:26:57 PM) ***khem is dirt deep in work</div><div>(1:27:26 PM) RP__: khem: I think people need to be encouraged to start using OE core...</div><div>(1:27:50 PM) fray: rp__ my expectation is that with the stable release people (working on anything but existing product) should switch to oe-core</div>
<div>(1:27:54 PM) RP__: khem: rely on me to go find the patches, rebase them against a different tree, post them on the oe-core list for review and then merge them isn't faire</div><div>(1:27:58 PM) fray: since that will be the latest "Stable"</div>
<div>(1:28:05 PM) khem: RP__: most of them are these patches are however from folks who deployed oe.dev release as I see</div><div>(1:28:18 PM) khem: yes folks has been asking for oe.core stable</div><div>(1:28:32 PM) RP__: khem: Its called 2011.1 :)</div>
<div>(1:28:36 PM) khem: so I see the branch that should bring in some more people</div><div>(1:28:37 PM) fray: I told the crowd at ESC Boston "in a few weeks" ;)</div><div>(1:28:44 PM) fray: lets hope I didn't lie</div>
<div>(1:29:49 PM) RP__: Did anyone have a chance to look at my performance tweaks?</div><div>(1:30:06 PM) RP__: Any concerns about disabling NLS for cross tools? I'm wondering native next...</div><div>(1:30:13 PM) RP__: also parallel make install</div>
<div>(1:30:17 PM) khem: Another FYI is that git will be moving to its final destination we expect no use visible problems except for RP</div><div>(1:30:20 PM) RP__: dropping help2man-native</div><div>(1:30:34 PM) khem: RP__: those changes look good.</div>
<div>(1:30:52 PM) fray: RP__ I havn't reviewed them due to my absense.. but I expect to</div><div>(1:30:54 PM) khem: I dont know if disabling NLS would be good or not</div><div>(1:31:14 PM) khem: since it might not emit errors in right language</div>
<div>(1:31:15 PM) RP__: khem: given we force the C locale, we currently don't use nls</div><div>(1:31:20 PM) khem: oh</div><div>(1:31:23 PM) khem: right</div><div>(1:31:43 PM) khem: well do we use that for cross gcc ?</div>
<div>(1:31:49 PM) khem: or target parts of it</div><div>(1:32:03 PM) RP__: target pieces would use NLS</div><div>(1:32:07 PM) fray: ya.. ridding hte host tooling of locales isn't a bad idea.. the only thing is there will likely be some folks who want localized messages when doing cross development.. but if it's difficult -- it's likely not worth the effrort</div>
<div>(1:32:22 PM) khem: yes Japan comes to mind</div><div>(1:32:33 PM) khem: ok I have to leave</div><div>(1:32:37 PM) fray: I don't see it as useful for anything but the toolchain</div><div>(1:32:42 PM) RP__: ok, ttfn khem!</div>
<div>(1:32:46 PM) khem: I will read the minutes</div><div>(1:32:48 PM) khem: ttyl</div><div>(1:32:52 PM) fray: ttyl!</div><div>(1:33:12 PM) RP__: fray: SDK toolchain is find, target toolchain is fine. cross toolchain, we currently force it to run with the C locale</div>
<div>(1:33:26 PM) RP__: so we can parse error output for things like host contamination</div><div>(1:33:40 PM) fray: it's the people writing apps (external of bitbake/oe-core) that are the ones I suspect would want them</div>
<div>(1:33:40 PM) RP__: so it would need big fixes to make locales work properly there</div><div>(1:33:48 PM) fray: inside of bitbake/oe-core.. we absolutely should for the C locale</div><div>(1:34:05 PM) fray: (that is should -force- the C locale)</div>
<div>(1:34:13 PM) RP__: right, it does</div><div>(1:34:20 PM) Jefro: khem - thanks for wiki!</div><div>(1:35:59 PM) RP__: I think we can probably close the meeting there</div><div>(1:36:20 PM) Jefro: sounds good - meeting officially adjourned, minutes later today</div>
</span><div><br></div>-- <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>