[oe] MINUTES: OE TSC 13 March 2012
OpenEmbedded Technical Steering Committee 13 March 2012 Attending: Richard Purdie (RP) Paul Eggleton (bluelightning) Mark Hatle (fray) Tom Rini (Tartarus) Khem (khem) Minutes: Jefro (Jefro) Agenda & Summary 1. pick a chair fray 2. lingering issues a. raise awareness of "janitor" list, QA "bugs" item to stand on agenda => fray to start publicity about "janitor" bugs not done yet, waiting for things to calm down this week 3. new issues a. discuss communication with OE community about release-oriented phases => fray willing to manage page as TSC activity => RP to send email updates, TSC to handle in future => future agenda: document release process RP raised awareness at collab Song sent note to oe-core & yocto lists yesterday RP talked to Dave & Song about making info more public => fray will stay in sync with Dave/RP/Song & create wiki when appropriate b. mips/mips32 tuning issue the mips32 tuning has previous produced "mips" tagged packages [package arch], and so did the default "mips" tuning. This lead to two packages with the same filenames, but very different contents fray fixed the defect.. which is leading to a concern of a filename change at the last minute.. => fray will summarize to list with possible options & ask for comments 4. status a. elections board would like to extend for 2 years to avoid election churn no objections b. infrastructure nothing new c. oe-core release RP is very worried about the quality of the release and number of open bugs Raw Transcript (8:58:05 AM) Jefro: agenda is at http://pastebin.com/23KsmkGJ (8:58:45 AM) RP__: hi (8:58:51 AM) RP__: I'm here put only partially (8:59:09 AM) RP__: with the release and the conferences and the UK holidays, I'm stretched today :( (8:59:13 AM) fray: I'd like a few minutes to talk about the mips/mips32 tuning issue.. it doesn't have to be under the official TSC meeting though (8:59:14 AM) Jefro: 3 1/2 members present then (8:59:29 AM) Jefro: or is khem back online? (8:59:52 AM) Jefro: back in 45 sec (9:00:30 AM) fray: I can flail all I want on this.. but we need a resolution and a technical decision (maintainer or tsc) IMHO (9:02:28 AM) Jefro: sounds like an agenda item for tsc (9:02:45 AM) Jefro: set as 3b (9:02:46 AM) fray: ya.. (9:02:50 AM) RP__: fray: I was just worried about Phil's reply to your patch (9:03:06 AM) RP__: fray: Why isn't your description adding up for him? (9:03:28 AM) fray: Phil isn't the one I'm worried aobut (unless I missed a response) (9:03:50 AM) fray: I agree my description is poor and needs to be revised.. but the contents are one of many possible solutions.. (9:03:59 AM) fray: I could implement them all, but it doesn't make sense to keep trying this.. (9:04:05 AM) fray: (until I have a specific direction) (9:04:24 AM) fray: (what I implemented was Khem's suggestion BTW) (9:04:56 AM) khem: mips1 is default he suggested (9:05:22 AM) fray: I havn't seen that email then.. (9:05:46 AM) Jefro: should we begin? perhaps counting this discussion in minutes (9:06:04 AM) fray: we should begin.. (9:06:14 AM) fray: I can quickly recap the discussion as I know it when we get to 3b (9:06:19 AM) Jefro: ok, thanks (9:06:20 AM) Jefro: who wants to chair? (9:06:28 AM) fray: I'm willing to, if requested (9:06:33 AM) Jefro: sold (9:06:53 AM) ***fray loads agenda (9:06:59 AM) fray: ok.. #1 is done, I've got the honor (9:07:08 AM) fray: @3 -- janitor list and bugs.. (9:07:11 AM) fray: 'er.. #2 (9:07:25 AM) fray: I have not yet publicised it.. I was waiting for things to calm down hopefully this week.. (9:07:35 AM) fray: any comments? or on to 3? (9:07:41 AM) Tartarus: no comments (9:07:43 AM) fray: (and yes, keep it on the agenda) (9:07:49 AM) bluelightning: no comments here (9:08:02 AM) fray: ok.. moving on.. (9:08:09 AM) fray: #3 a -- OS releaste phases.. (9:08:25 AM) fray: again, my work is pending the end of this phase.. (9:08:35 AM) fray: RP -- did you send anything out for the current? (9:08:48 AM) Jefro: fray - should also poll for any other new business (sorry, I should put that in the agenda template) (9:08:57 AM) fray: yes.. sorry (9:09:10 AM) fray: (any new issues?) (9:09:24 AM) fray: my request is a brief discussion and resolution to the MIPS/MIPS32 issue (9:09:27 AM) fray: (3b) (9:09:39 AM) bluelightning: don't think I have anything to raise atm (9:10:02 AM) fray: ok, if anyone thinks of an additional issue, please speak up.. otherwise back to 3a (9:10:18 AM) fray: I suspect RP had to step away.. so we can table that part.. (9:10:30 AM) fray: I agree it needs to be kept on the agenda until we get it decided and completed (9:10:37 AM) fray: anyone else? (9:11:07 AM) fray: ok.. on to 3b -- the mips issue (9:11:22 AM) fray: Let me briefly recap what happened and what the issue is (as I see it) (9:12:03 AM)
[oe] MINUTES: OE TSC 13 March 2012
OpenEmbedded Technical Steering Committee 13 March 2012 Attending: Richard, Paul, Mark, Tom Apologies: Khem Minutes: Jefro Agenda 1. pick a chair -> RP 2. open issues a. IMAGE_FSTYPES (Tartarus) =>poking people to read & reply on list b. need more QA - warnings reduction, stress test of sstate, fixing autobuilder regressions (RP) c. conferences - Collaboration Summit yocto project working day on weds at collab for working day d. raise awareness of "janitor" list, QA "bugs" requires more publicizing, getting more people involved 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 separate janitorial tasks from actual bug fixes =>RP will mention idea to Darren & Sean =>all - please think of other ways to get people involved 3. status a. elections fray reelected Tartarus next, then cycle complete =>RP to ping board, roll into new election right away b. infrastructure RP acknowledge Michael Halstead's work on the OE server in speeding up git access; Paul agrees, much appreciated web issues brought down ltg & ml archives a few weeks ago list archives back now c. oe-core release feature freeze in 1 week final freeze 2-3 weeks from 18 Mar Raw Transcript (9:16:19 AM) RP__: Jefro: do you have an agenda? (9:18:05 AM) ***fray wonders if jefro fell off the internet (9:18:42 AM) RP__: lets assume he has :/ (9:18:49 AM) RP__: agenda items? (9:19:09 AM) RP__: Well, lets start with the janitor and QA bugs (9:19:15 AM) fray: sounds good (9:19:19 AM) fray: (is someone logging?) (9:19:27 AM) ***RP__ is (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 (9:20:00 AM) RP__: I'm rather unhappy about this (9:20:21 AM) RP__: I'm doing my bit to reduce the numbers but I'd appreciate more people helping out (9:20:38 AM) RP__: Sean mentioned there are some sstate issues and that our QA tests probably aren't good enough (9:20:54 AM) RP__: I pointed out that even the QA issues we know about right now aren't getting fixed (9:21:17 AM) RP__: This lead into a discussion about our the Yocto janitor page - this is like the kernel janitors project (9:21:30 AM) RP__: tasks someone could pick up, look into and fix to get into the project (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 (9:22:17 AM) RP__: We need to raise more awareness of the janitor list... (9:22:29 AM) RP__: Any comments or shall I just talk to myself? :) (9:22:43 AM) Tartarus: Good idea, I thought we had said to do that before (9:22:44 AM) fray: yes.. I know there are people willing to do janitor work (in oe as well as the Yocto Project) (9:22:58 AM) fray: we just need to make it clear to folks we've hit a point where janitor work is needed.. (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 (9:23:11 AM) Jefro: sorry - got called away, here now (9:23:14 AM) fray: (actually we're likely past that point.. but anyway..) (9:23:18 AM) Jefro: I'm logging (9:23:23 AM) Jefro: I even have an agenda (9:23:38 AM) RP__: Jefro: If you could share that with us that would be useful :) (9:23:43 AM) Jefro: http://pastebin.com/TqiVP8dw (9:24:08 AM) fray: IMAGE_FSTYPES was Tartarus ;) (9:24:13 AM) Jefro: oops, ok (9:24:23 AM) RP__: What the janitor work needs is one or more people to champion it (9:24:45 AM) RP__: We could ask the membership for volunteers (9:25:01 AM) fray: yes, i think thats a good idea.. (9:25:15 AM) ***RP__ suspects he is chairing (9:25:37 AM) ***bluelightning suspects that is the case ;) (9:25:49 AM) Jefro: who wants to take AR to alert membership for janitor volunteers? (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 (9:26:08 AM) RP__: ;-) (9:26:23 AM) fray: I was justa bout to suggest that.. (9:26:28 AM) RP__: Re: the QA issues in general as well as bug fixing and testing (9:27:24 AM) RP__: Does anyone have any idea how to get more people involved? (9:27:55 AM) RP__: I'm finding it hard going atm and will have to start refusing changes when the builds are broken (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.. (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 (9:28:11 AM) fray: we already have people doing some of the work and probably not realizing it (9:28:18 AM) RP__: Jefro: Totally, I'm raising this as a separa
