<div>OpenEmbedded Technical Steering Committee</div><div>13 March 2012</div><div><br></div><div>Attending: Richard, Paul, Mark, Tom</div><div>Apologies: Khem</div><div>Minutes: Jefro</div><div><br></div><div>________________________________________________</div>
<div>Agenda</div><div><br></div><div>1. pick a chair</div><div>-> RP</div><div><br></div><div>2. open issues</div><div><br></div><div> a. IMAGE_FSTYPES (Tartarus)</div><div>=> poking people to read & reply on list</div>
<div><br></div><div> b. need more QA - warnings reduction, stress test of sstate, </div><div> fixing autobuilder regressions (RP)</div><div><br></div><div> c. conferences - Collaboration Summit</div><div> yocto project working day on weds at collab</div>
<div> for working day</div><div><br></div><div> d. raise awareness of "janitor" list, QA "bugs"</div><div> requires more publicizing, getting more people involved</div><div> going to rework the wiki page into the bugzilla so we track </div>
<div> things in one place, then generate a summary of open tasks </div><div> for the wiki automagically</div><div> separate janitorial tasks from actual bug fixes</div><div>=> RP will mention idea to Darren & Sean</div>
<div>=> all - please think of other ways to get people involved</div><div><br></div><div>3. status</div><div><br></div><div> a. elections</div><div> fray reelected</div><div> Tartarus next, then cycle complete</div>
<div>=> RP to ping board, roll into new election right away</div><div><br></div><div> b. infrastructure</div><div> RP acknowledge Michael Halstead's work on the OE server </div><div> in speeding up git access; Paul agrees, much appreciated</div>
<div> web issues brought down ltg & ml archives a few weeks ago</div><div> list archives back now</div><div><br></div><div> c. oe-core release</div><div> feature freeze in 1 week</div><div> final freeze 2-3 weeks from 18 Mar</div>
<div><br></div><div>________________________________________________</div><div>Raw Transcript</div><div><br></div><div>(9:16:19 AM) RP__: Jefro: do you have an agenda?</div><div>(9:18:05 AM) ***fray wonders if jefro fell off the internet</div>
<div>(9:18:42 AM) RP__: lets assume he has :/</div><div>(9:18:49 AM) RP__: agenda items?</div><div>(9:19:09 AM) RP__: Well, lets start with the janitor and QA bugs</div><div>(9:19:15 AM) fray: sounds good</div><div>(9:19:19 AM) fray: (is someone logging?)</div>
<div>(9:19:27 AM) ***RP__ is</div><div>(9:19:51 AM) RP__: For those who were in the Yocto technical meeting before, I laboured a point about the number of warnings our builds generate</div><div>(9:20:00 AM) RP__: I'm rather unhappy about this</div>
<div>(9:20:21 AM) RP__: I'm doing my bit to reduce the numbers but I'd appreciate more people helping out</div><div>(9:20:38 AM) RP__: Sean mentioned there are some sstate issues and that our QA tests probably aren't good enough</div>
<div>(9:20:54 AM) RP__: I pointed out that even the QA issues we know about right now aren't getting fixed</div><div>(9:21:17 AM) RP__: This lead into a discussion about our the Yocto janitor page - this is like the kernel janitors project</div>
<div>(9:21:30 AM) RP__: tasks someone could pick up, look into and fix to get into the project</div><div>(9:21:55 AM) RP__: We're going to rework the wiki page into the bugzilla so we track things in one place, then generate a summary of open tasks for the wiki automagically</div>
<div>(9:22:17 AM) RP__: We need to raise more awareness of the janitor list...</div><div>(9:22:29 AM) RP__: Any comments or shall I just talk to myself? :)</div><div>(9:22:43 AM) Tartarus: Good idea, I thought we had said to do that before</div>
<div>(9:22:44 AM) fray: yes.. I know there are people willing to do janitor work (in oe as well as the Yocto Project)</div><div>(9:22:58 AM) fray: we just need to make it clear to folks we've hit a point where janitor work is needed..</div>
<div>(9:23:10 AM) RP__: Tartarus: I think we've said it but we've not done much about it and its not publicised much</div><div>(9:23:11 AM) Jefro: sorry - got called away, here now</div><div>(9:23:14 AM) fray: (actually we're likely past that point.. but anyway..)</div>
<div>(9:23:18 AM) Jefro: I'm logging</div><div>(9:23:23 AM) Jefro: I even have an agenda</div><div>(9:23:38 AM) RP__: Jefro: If you could share that with us that would be useful :)</div><div>(9:23:43 AM) Jefro: <a href="http://pastebin.com/TqiVP8dw">http://pastebin.com/TqiVP8dw</a></div>
<div>(9:24:08 AM) fray: IMAGE_FSTYPES was Tartarus ;)</div><div>(9:24:13 AM) Jefro: oops, ok</div><div>(9:24:23 AM) RP__: What the janitor work needs is one or more people to champion it</div><div>(9:24:45 AM) RP__: We could ask the membership for volunteers</div>
<div>(9:25:01 AM) fray: yes, i think thats a good idea..</div><div>(9:25:15 AM) ***RP__ suspects he is chairing</div><div>(9:25:37 AM) ***bluelightning suspects that is the case ;)</div><div>(9:25:49 AM) Jefro: who wants to take AR to alert membership for janitor volunteers?</div>
<div>(9:26:04 AM) RP__: ok, I will mention the above idea to Darren and see if I can convince him and Sean to take this on</div><div>(9:26:08 AM) RP__: ;-)</div><div>(9:26:23 AM) fray: I was justa bout to suggest that..</div>
<div>(9:26:28 AM) RP__: Re: the QA issues in general as well as bug fixing and testing</div><div>(9:27:24 AM) RP__: Does anyone have any idea how to get more people involved?</div><div>(9:27:55 AM) RP__: I'm finding it hard going atm and will have to start refusing changes when the builds are broken</div>
<div>(9:27:56 AM) fray: I think a request to the oe-core list and a page indicating what is needed is hte best way to start..</div><div>(9:28:06 AM) Jefro: it might be useful to separate janitorial duties from actual bug fixing, so those of us with less technical expertise can lend time</div>
<div>(9:28:11 AM) fray: we already have people doing some of the work and probably not realizing it</div><div>(9:28:18 AM) RP__: Jefro: Totally, I'm raising this as a separate topic</div><div>(9:28:25 AM) Jefro: ok</div>
<div>(9:28:46 AM) RP__: For example, someone sends a patch X, it merges, it breaks things</div><div>(9:29:11 AM) RP__: At present I spend a lot of time fixing things since the breakage starts affecting people who have no interest in the patch</div>
<div>(9:29:35 AM) bluelightning: RP__: do you have some recent examples?</div><div>(9:29:52 AM) RP__: bluelightning: Adding python to gdb-cross-candian</div><div>(9:30:06 AM) bluelightning: ah yes :/</div><div>(9:30:07 AM) RP__: took out meta-toolchain on rpm</div>
<div>(9:30:23 AM) RP__: This kind of stuff becomes my problem :(</div><div>(9:31:02 AM) RP__: Since there are no comments, might as well move on. I don't have answers either</div><div>(9:31:14 AM) RP__: IMAGE_FSTYPES - was there anything you wanted to add Tartarus</div>
<div>(9:31:16 AM) RP__: ?</div><div>(9:31:22 AM) Tartarus: Just poking people to read, reply</div><div>(9:31:35 AM) fray: (and ya, I don't have any answers either..)</div><div>(9:32:13 AM) RP__: ok, Jefro - do you have the collab summit agenda</div>
<div>(9:32:14 AM) RP__: ?</div><div>(9:32:24 AM) ***RP__ notes himself duly poked </div><div>(9:32:26 AM) Jefro: yes, it is on the collab summit events page - link in 2 sec</div><div>(9:32:39 AM) Jefro: <a href="https://events.linuxfoundation.org/events/collaboration-summit/schedule">https://events.linuxfoundation.org/events/collaboration-summit/schedule</a></div>
<div>(9:32:49 AM) RP__: We're looking to have a Yocto work session at collab summt</div><div>(9:33:00 AM) Jefro: the yocto project workgroup day is on Weds 9am-5pm (or later)</div><div>(9:33:07 AM) RP__: This is following a BSP summit at Mentor's Freemont site earlier in the week</div>
<div>(9:33:09 AM) Jefro: actual working session is in afternoon</div><div>(9:33:45 AM) RP__: I really don't know who we're going to get at collab or what they're going to find useful to do</div><div>(9:33:55 AM) Jefro: I noted to the OE lists about Collab Summit and encouraged people to request an invitation (at Philip's request)</div>
<div>(9:33:56 AM) RP__: I wanted to give the TSC an opportunity to suggest things</div><div>(9:35:06 AM) ***Jefro hears crickets</div><div>(9:35:10 AM) RP__: While people are mulling that over and since I've already put input into it, let me touch on elections. We welcome back fray, congratulations! :)</div>
<div>(9:35:30 AM) RP__: Do we want to roll into another election for Tartarus straight away?</div><div>(9:35:46 AM) Tartarus: I'd be good with that</div><div>(9:35:49 AM) RP__: We seem to take our time over these things so we might as well set the ball rolling</div>
<div>(9:36:25 AM) Jefro: will someone ping the board?</div><div>(9:36:28 AM) ***RP__ is going to assume people will jump in with earlier topics if they have anything to add</div><div>(9:36:31 AM) ***RP__ can do so</div><div>
(9:36:52 AM) ***RP__ is taking no comment from fray and bluelightning as agreement</div><div>(9:37:02 AM) fray: yup</div><div>(9:37:04 AM) bluelightning: sounds OK to me</div><div>(9:37:18 AM) RP__: re: Infrastructure, I wanted to acknowledge Michael Halsted's work on the OE server in speeding up git access</div>
<div>(9:37:33 AM) bluelightning: yes, that is very much appreciated</div><div>(9:37:45 AM) bluelightning: it has been slow for a very long time</div><div>(9:37:49 AM) RP__: Does anyone have anything to add on infrsatructure?</div>
<div>(9:38:25 AM) bluelightning: did the web issues that brought down ltg (and hence our mailing list archives) get resolved?</div><div>(9:38:41 AM) bluelightning: that was a couple of weeks ago now</div><div>(9:38:43 AM) RP__: bluelightning: I think we got the list archives back</div>
<div>(9:38:55 AM) RP__: bluelightning: whether their forum problem got resolved or not I don't know</div><div>(9:39:06 AM) RP__: bluelightning: that doesn't really affect us</div><div>(9:39:19 AM) bluelightning: indirectly if stuff goes down, it does...</div>
<div>(9:40:18 AM) RP__: bluelightning: well, I think they've agreed not to do that now...</div><div>(9:40:31 AM) RP__: bluelightning: i.e. they've taken down one vhost, not them all</div><div>(9:40:41 AM) bluelightning: ok cool, that should resolve that for the future</div>
<div>(9:40:54 AM) bluelightning: it did seem a touch heavy handed :/</div><div>(9:41:00 AM) RP__: So, if nothing else there, oe-core status</div><div>(9:41:19 AM) RP__: I've been fighting to reduce the warnings and fix the autobuilder failures</div>
<div>(9:41:29 AM) RP__: We have a feature freeze point in about a week now</div><div>(9:41:42 AM) fray: RP__ what is the proposed bug fix/final freeze date?</div><div>(9:42:16 AM) RP__: fray: not sure, 2-3 weeks after the 18th I think</div>
<div>(9:42:24 AM) RP__: that's when we roll -rc1</div><div>(9:42:27 AM) fray: ok.. rough idea is good enough for the minutes..</div><div>(9:42:41 AM) RP__: its on the yocto calender</div><div>(9:43:10 AM) RP__: Builds aren't looking too red on the autobuilder although there are some puzzling failures on some of the newer tests</div>
<div>(9:43:14 AM) Jefro: <a href="https://wiki.yoctoproject.org/wiki/YoctoCalendar">https://wiki.yoctoproject.org/wiki/YoctoCalendar</a></div><div>(9:43:19 AM) RP__: Any other questions, other business?</div><div>(9:44:12 AM) ***Jefro will get minutes out early this time & catch up on old ones</div>
<div>(9:44:59 AM) RP__: If nothing else I'll close the meeting...</div><div>(9:45:09 AM) bluelightning: nothing here</div><div>(9:45:28 AM) Tartarus: nothing here</div><div>(9:45:31 AM) fray: nothing</div><div>(9:46:30 AM) ***RP__ closes</div>
<div><br></div><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>