<span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; background-color: rgb(255, 255, 255); "><div>MINUTES: OE-TSC meeting 6-Oct-2011</div><div><br></div><div>Attending: Mark, Richard, Khem, Koen, Tom</div>
<div>Notes: Jefro </div><div><br></div><div>--------------------------------------------------------</div><div>Agenda & Results</div><div><br></div><div>1. pick a moderator</div><div><span style="white-space: pre-wrap; "> </span>RP</div>
<div><br></div><div>2. new items:</div><div> maintainer files</div><div><span style="white-space: pre-wrap; "> </span>bitbake doesn't have one</div><div><span style="white-space: pre-wrap; "> </span>acknowledged need for READMEs in bitbake, main directory, oe-core layers</div>
<div><span style="white-space: pre-wrap; "> </span>possibly add knowledge to pull request scripts</div><div> PACKAGECONFIG</div><div> concept generally positive, continue discussing on list</div><div> ELCE</div>
<div><span style="white-space: pre-wrap; "> </span>RP: reminder about GA proxy voting</div><div><span style="white-space: pre-wrap; "> </span>GA plans - Jefro finding a room, Philip B. gathering RSVPs</div><div><span style="white-space: pre-wrap; "> </span>need a new place for bitbake tarball downloads</div>
<div><span style="white-space: pre-wrap; "> </span>Khem can ask Tom K. to revive <a href="http://downloads.oe.org/" target="_blank" style="color: rgb(0, 0, 204); ">downloads.oe.org</a></div><div><br></div><div>3. status on old items:</div>
<div><span style="white-space: pre-wrap; "> </span>oe-core release</div><div><span style="white-space: pre-wrap; "> </span>need BSP tarballs (TI), "official" is preferred (having a maintainer is a good start)</div>
<div><span style="white-space: pre-wrap; "> </span>oe-core needs promotion, needs plans in place for release</div><div><span style="white-space: pre-wrap; "> </span>OE infrastructure moving around, admin issues need a lead</div>
<div><span style="white-space: pre-wrap; "> </span>release bitbake as well</div><div><span style="white-space: pre-wrap; "> </span>elections</div><div><span style="white-space: pre-wrap; "> </span>Denys sent mail, khem standing down & up</div>
<div><span style="white-space: pre-wrap; "> </span>infrastructure</div><div><span style="white-space: pre-wrap; "> </span>new server "opal", 64 bit VM</div><div><span style="white-space: pre-wrap; "> </span>transitioning all services from melo to opal</div>
<div><span style="white-space: pre-wrap; "> </span>wiki runs on it, moving git over</div><div><span style="white-space: pre-wrap; "> </span>some difficulty using nginx, Tartarus knows someone good with it</div><div><span style="white-space: pre-wrap; "> </span>yocto also uses nginx, RP and Tom will both pass on questions</div>
<div><span style="white-space: pre-wrap; "> </span>note: berlios closing at end of year,</div><div><span style="white-space: pre-wrap; "> </span>yocto</div><div><span style="white-space: pre-wrap; "> </span>1.2 feature list shaping up</div>
<div><span style="white-space: pre-wrap; "> </span>rc4 release build successful, waiting now on QA</div><div><span style="white-space: pre-wrap; "> </span>TI had strategic meeting for 1.2/1.3 wish list, going through yocto channels</div>
<div><span style="white-space: pre-wrap; "> </span>WR focusing on workflow improvements</div><div><br></div><div>--------------------------------------------------------</div><div>Raw Transcript:</div><div><br></div><div>
(1:02:44 PM) fray: ok.. I;m here now</div><div>(1:03:31 PM) RP__: quorum :)</div><div>(1:03:51 PM) khem: ok it was not pear but peaches took a bit longer :)</div><div>(1:03:53 PM) RP__: Anything for the agenda?</div><div>
(1:04:05 PM) khem: Infra update</div><div>(1:04:14 PM) fray: maintainer files or something similar for "newbies" to know where to send patches</div><div>(1:04:19 PM) khem: move of git to new server is under work</div>
<div>(1:04:21 PM) RP__: Yocto Feature List for 1.2 is shaping up: <a href="https://wiki.yoctoproject.org/wiki/Yocto_1.2_Features" target="_blank" style="color: rgb(0, 0, 204); ">https://wiki.yoctoproject.org/wiki/Yocto_1.2_Features</a></div>
<div>(1:04:47 PM) RP__: Yocto -rc4 release build was successful, waiting on QA now but its looking pretty much done</div><div>(1:05:07 PM) RP__: fray: no brainer, I agree we need it, just need the patches</div><div>(1:05:23 PM) RP__: khem: this is a file at the top level of the tree saying where patches should go etc.</div>
<div>(1:05:29 PM) Tartarus [<a href="mailto:trini@pixelshelf.com" target="_blank" style="color: rgb(0, 0, 204); ">trini@pixelshelf.com</a>] entered the room.</div><div>(1:05:29 PM) mode (+v Tartarus) by ChanServ</div><div>
(1:05:35 PM) Tartarus: Sorry I'm late</div><div>(1:05:38 PM) Tartarus: just got internet back up</div><div>(1:05:49 PM) Jefro: welcome back :)</div><div>(1:05:55 PM) fray: RP__ yup.. I think that'll take all of 2 minutes to discuss.. I just want it in the minutes</div>
<div>(1:05:57 PM) khem: RP__: README at top says about this</div><div>(1:05:59 PM) ***RP__ has pasted the last few lines</div><div>(1:06:05 PM) Tartarus: no new items from me</div><div>(1:06:09 PM) RP__: khem: bitbake doesn't have one for example</div>
<div>(1:06:49 PM) khem: ok</div><div>(1:06:52 PM) khem: that should be added</div><div>(1:06:54 PM) RP__: Tartarus: we have four of us (koen isn't here)</div><div>(1:07:01 PM) RP__: + Jefro :)</div><div>(1:07:16 PM) RP__: ok, any other agenda items?</div>
<div>(1:07:23 PM) khem: and may be we can think of adding knowledge to pull request scripts</div><div>(1:07:25 PM) RP__: We could quickly touch on PACKAGECONFIG I guess</div><div>(1:07:38 PM) khem: that may be a bit stretch</div>
<div>(1:07:40 PM) Jefro: 1. pick a chair (RP__ already fulfilling that function)</div><div>(1:08:33 PM) RP__: ELCE and TSC election?</div><div>(1:08:34 PM) khem: RP__: is PACKAGECONFIG same as gentoo's USE flags</div>
<div>(1:08:47 PM) RP__: khem: yes and no ;-)</div><div>(1:09:10 PM) khem: similar I would say</div><div>(1:09:19 PM) RP__: ok, we have an agenda then</div><div>(1:09:33 PM) RP__: do we need to talk about readme files in repos further?</div>
<div>(1:09:41 PM) RP__: We did already as a TSC advise README files</div><div>(1:09:56 PM) RP__: Stating how patches should be submitted seems like a good thing to have there</div><div>(1:10:03 PM) fray: just wanted to mention the "problem"</div>
<div>(1:10:17 PM) khem: I think README are good since github displays them on front page if repo is hosted on github</div><div>(1:10:18 PM) fray: I had a user download oe-core and they fixed a problem. but they had to ask me where to send the fix..</div>
<div>(1:10:30 PM) khem: and kind of cool when one browses it</div><div>(1:10:44 PM) fray: a simple maintainers page or similar (readme is fine) that says "here is the mailing list to use to send patches" or here is the maintainer, etc.. is what is needed..</div>
<div>(1:10:59 PM) fray: they were able ot find (immediately) the commit guidelines and policies on the oe page, but not where to send their patches</div><div>(1:11:09 PM) khem: fray: README are pretty common and easy for users to find</div>
<div>(1:11:12 PM) fray: so we should solve that...</div><div>(1:11:20 PM) RP__: fray: no argument here</div><div>(1:11:26 PM) fray: yup, no worries.. and this includes adding one to bitbake -- assuming the maintainers there will accept it</div>
<div>(1:11:43 PM) khem: I think most of meta-* layers have it</div><div>(1:11:48 PM) RP__: fray: I suspect they will</div><div>(1:11:50 PM) fray: (I started to put together one, but wasn't sure what to put into it.. so I stopped)</div>
<div>(1:11:53 PM) fray: RP ;)</div><div>(1:12:14 PM) fray: khem, ya I thought so too.. it's the main meta layer and the oe-core stuff that doesn't seem to have one.. (if it does, I'm blind)</div><div>(1:12:30 PM) RP__: I suspect we just overlooked OE-Core</div>
<div>(1:12:36 PM) fray: ok, anyway that was the one issue I had.. we can move on.. :)</div><div>(1:12:38 PM) RP__: and Poky could do with a variant of that</div><div>(1:12:41 PM) khem: yeah the layers in oe-core do need one I guess</div>
<div>(1:12:59 PM) RP__: khem: I don't think the layers do but the main repo itself it would be good for...</div><div>(1:13:10 PM) fray: yup.. bitbake, main directory and oe-core layers (meta)</div><div>(1:13:16 PM) khem: RP__: collectively yes</div>
<div>(1:13:27 PM) fray: RP__ I would put one in the meta for consistency with external layers.. but that's me</div><div>(1:14:00 PM) khem: they go to same ml but READMEs minght be different for different layers thats what I though it wont harm to have the ml name duplicated into them if Such READMEs existi</div>
<div>(1:14:19 PM) RP__: lets take the patches to the mailing lists</div><div>(1:14:23 PM) RP__: infra update?</div><div>(1:14:26 PM) fray: yup.. works for me</div><div>(1:15:07 PM) khem: We have a new server called opal</div>
<div>(1:15:16 PM) khem: where all services which are on melo</div><div>(1:15:21 PM) khem: currently are shifting</div><div>(1:15:28 PM) khem: its a 64bit VM</div><div>(1:15:45 PM) khem: currently wiki runs on it and we are moving git over</div>
<div>(1:15:54 PM) khem: currently working on configuring cgit</div><div>(1:16:07 PM) khem: since it uses nginx and not apache</div><div>(1:16:20 PM) khem: its a bit of challange to get CGI scripts running</div><div>(1:16:34 PM) khem: but we have figured out</div>
<div>(1:16:37 PM) Tartarus: What kind of nginx problems are we having?</div><div>(1:16:37 PM) RP__: yocto uses nginx too</div><div>(1:16:41 PM) Tartarus: I know a guy that's good with it..</div><div>(1:16:47 PM) RP__: causes problems with the caching :(</div>
<div>(1:16:49 PM) khem: RP__: cool</div><div>(1:17:04 PM) khem: then can you send the yocto config for cgit</div><div>(1:17:10 PM) khem: for nginx</div><div>(1:17:48 PM) khem: is needs spawn-fcgi</div><div>(1:17:52 PM) khem: too right ?</div>
<div>(1:18:06 PM) ***koen arrives</div><div>(1:18:11 PM) koen: apologies for being late</div><div>(1:18:19 PM) khem: welcome koen</div><div>(1:19:03 PM) khem: once cgit is configured then we will have only patchwork left on melo</div>
<div>(1:19:23 PM) RP__: khem: I can try, I'm not familiar with where to find them though</div><div>(1:19:41 PM) khem: RP__: /etc/nginx/sites-available/</div><div>(1:20:08 PM) khem: RP__: or whoever configured cgit with nginx can be handy here</div>
<div>(1:20:18 PM) khem: so some HOWTO can speed it up</div><div>(1:20:25 PM) khem: instead of figuring out</div><div>(1:20:41 PM) Tartarus: So do we need configure help w/ nginx or no?</div><div>(1:20:48 PM) khem: yes</div>
<div>(1:20:48 PM) RP__: khem: looks like there is a fastcgi server configured on localhost</div><div>(1:21:01 PM) khem: yeah that kind of info is needed</div><div>(1:21:13 PM) khem: how thats done and how it interfaces with nginx</div>
<div>(1:21:19 PM) Tartarus: OK, well if folks can give me context + questions I can pass it along</div><div>(1:21:30 PM) Tartarus: and if you can hop on efnet instead might be able to chat w/ the guy :)</div><div>(1:21:42 PM) khem: Tartarus: setting up cgit with nginx on ubuntu 10.10 64bit</div>
<div>(1:21:47 PM) RP__: khem: I'll see what I can pass on</div><div>(1:21:48 PM) khem: Tartarus: we need howto</div><div>(1:21:53 PM) khem: thanks</div><div>(1:22:06 PM) khem: errr 10.04 not 10.10</div><div>(1:22:40 PM) RP__: So, moving on, I think my comments earlier mentioned what I wanted to say:</div>
<div>(1:22:41 PM) RP__: Yocto Feature List for 1.2 is shaping up: <a href="https://wiki.yoctoproject.org/wiki/Yocto_1.2_Features" target="_blank" style="color: rgb(0, 0, 204); ">https://wiki.yoctoproject.org/wiki/Yocto_1.2_Features</a></div>
<div>(1:22:41 PM) RP__: Yocto -rc4 release build was successful, waiting on QA now but its looking pretty much done</div><div>(1:22:43 PM) Tartarus: Is it just not working or a specific error?</div><div>(1:22:55 PM) RP__: koen: any topics?</div>
<div>(1:23:08 PM) koen: we finally had our TI strategic meeting for what we want in 1.2/1.3</div><div>(1:23:24 PM) koen: but that will go through yocto channels</div><div>(1:23:41 PM) khem: koen: ok anything thats interesting for oe-core ?</div>
<div>(1:23:47 PM) fray: as an OE TSC -- we need input from the OE members / users on what they want/need..</div><div>(1:23:50 PM) RP__: koen: ok, cool. The sooner the better since planning is well under way now ;-)</div><div>
(1:23:59 PM) koen: for the oe-core release download page we need BSP tarballs as well</div><div>(1:24:10 PM) fray: as a WR person for a second, we're going to be focusing on workflow improvements...</div><div>(1:24:28 PM) koen: and vet the bsp to weed out crappy ones from the good ones</div>
<div>(1:24:44 PM) khem: Tartarus: ground up would be good. We have nginx working but not with cgit</div><div>(1:24:54 PM) Tartarus: ok</div><div>(1:24:59 PM) RP__: koen: The hard bit is defining crappy</div><div>(1:25:06 PM) Tartarus: I'll see how annoyed at me my friend is for nothing more specific :)</div>
<div>(1:25:18 PM) khem: I think bsp's that are official would be preferred</div><div>(1:25:24 PM) khem: now define official</div><div>(1:25:37 PM) Tartarus: he's not done it before, heh</div><div>(1:25:48 PM) ***fray is simply happy with BSPs that have maintainers.. ;)</div>
<div>(1:27:24 PM) koen: and for the oe-core release, oe-core needs to get promoted</div><div>(1:27:29 PM) RP__: ok, any input to the planning process is welcome, no promises anything gets done but people are free to raise issues</div>
<div>(1:28:52 PM) khem: koen: I would say its distro choice to pick a bsp</div><div>(1:29:12 PM) koen: khem: try to find BSPs</div><div>(1:29:37 PM) koen: the yocto website is completely silent on !poky</div><div>(1:29:45 PM) koen: the OE website is...</div>
<div>(1:30:03 PM) ***Jefro notes meeting midpoint, still to discuss: PACKAGECONFIG, ELCE, elections</div><div>(1:30:17 PM) koen: denys sent out a mail for the elections</div><div>(1:30:29 PM) khem: koen: thats something for yocto I guess</div>
<div>(1:30:33 PM) RP__: koen: Its a good point, Yocto has been driving the release process but we haven't really got plans in place for the OE-Core part of the release</div><div>(1:31:01 PM) RP__: It doesn't help that the OE infrastructure is moving around and nobody seems to want to take the lead on some of the admin type issues</div>
<div>(1:31:16 PM) RP__: Speaking of infrastrcture btw, Berlios is closing end of the yewar</div><div>(1:31:24 PM) RP__: we need a new place for bitbake tarball downloads</div><div>(1:31:54 PM) khem: RP__: we can put them in <a href="http://sources.oe.org/" target="_blank" style="color: rgb(0, 0, 204); ">sources.oe.org</a></div>
<div>(1:32:40 PM) RP__: khem: I think separating out the release tarballs might be nicer for people</div><div>(1:33:26 PM) RP__: Is anyone willing to help sort an OE release process?</div><div>(1:33:29 PM) koen: can we get <a href="http://downloads.oe.org/" target="_blank" style="color: rgb(0, 0, 204); ">downloads.oe.org</a> back?</div>
<div>(1:34:01 PM) khem: koen: isnt that now <a href="http://sources.oe.org/" target="_blank" style="color: rgb(0, 0, 204); ">sources.oe.org</a> ?</div><div>(1:34:06 PM) koen: no</div><div>(1:34:28 PM) koen: <a href="http://downloades.oe.org/" target="_blank" style="color: rgb(0, 0, 204); ">downloades.oe.org</a> was for things like oe .deb and rpm packages</div>
<div>(1:34:38 PM) RP__: We could use <a href="http://downloads.yoctoproject.org/" target="_blank" style="color: rgb(0, 0, 204); ">downloads.yoctoproject.org</a> but I suspect people would not like that</div><div>(1:34:47 PM) fray: RP__ I'm willing to help, but I fear ignorance on a lot of the previous oe history.. so if we want to try to do things the way they've been done, I'm not sure how helpful I can be</div>
<div>(1:35:14 PM) fray: how was the last oe-dev "released"? Was it more then simply a tag/branch?</div><div>(1:35:15 PM) khem: RP__: I can help with oe parts on release</div><div>(1:35:28 PM) RP__: fray: no, but we need to do better</div>
<div>(1:35:40 PM) Tartarus: fray, pre oe-core we did weekly snapshots and asked for testing then branched</div><div>(1:35:41 PM) fray: ok.. I hadn't realized people wanted more</div><div>(1:35:58 PM) RP__: khem: thanks. I think a dedicated <a href="http://downloads.oe.org/" target="_blank" style="color: rgb(0, 0, 204); ">downloads.oe.org</a> might be good and some way of placing tarballs there for people like me</div>
<div>(1:36:13 PM) khem: RP__: ok</div><div>(1:36:22 PM) khem: I will ask Tom to set one up</div><div>(1:36:34 PM) RP__: The rest of it is likely then getting an announcement together and so on</div><div>(1:36:48 PM) khem: RP__: cgit also exports tarballs</div>
<div>(1:37:00 PM) koen: khem: that's not a real option</div><div>(1:37:04 PM) RP__: khem: which change checksum depending on the date</div><div>(1:37:09 PM) khem: I get it</div><div>(1:37:28 PM) RP__: khem: Also need to coordinate anyone else wanting to release tarballs of layers etc</div>
<div>(1:37:35 PM) khem: OK,</div><div>(1:37:49 PM) RP__: khem: Thanks for helping there, I appreciate it :)</div><div>(1:37:59 PM) fray: RP__ isn't the release of layers made after the initial oe-core release?</div><div>
(1:38:34 PM) RP__: fray: yes, but people likely need to know about it and may want to coordinate with the annoucement</div><div>(1:38:46 PM) RP__: we have a pretty good idea what the release will look like now for example</div>
<div>(1:39:06 PM) RP__: If we have the site I can put the bitbake tarballs there too</div><div>(1:39:45 PM) RP__: ok, PACKAGECONFIG - its a fairly major change</div><div>(1:40:01 PM) RP__: but we preciously discussed it and now looks like a good time to bring it in</div>
<div>(1:40:19 PM) RP__: I just wanted to check if there were any strong feelings or we just continue on list?</div><div>(1:40:20 PM) ***fray REALLY likes the concept of packageconfig</div><div>(1:41:08 PM) RP__: oh, bitbake release - a good idea alongside the oe-core release?</div>
<div>(1:41:21 PM) fray: absolutely</div><div>(1:41:33 PM) RP__: elce is soon, I don't have anything specific to discuss on that</div><div>(1:41:50 PM) fray: as far as attendance for elce goes, it doesnt look like I will be there..</div>
<div>(1:41:58 PM) RP__: :(</div><div>(1:42:02 PM) ***Tartarus also won't be</div><div>(1:42:07 PM) RP__: I'd gently remind people about AGM proxy voting</div><div>(1:42:17 PM) fray: I'm still trying to figure out if I'll be able to fly in for a day or so for the OE eV meeting and such..</div>
<div>(1:42:19 PM) ***khem wont be there either</div><div>(1:42:21 PM) RP__: er, s/AGM/GA/</div><div>(1:43:07 PM) ***RP__ will be there and has booked tickets now</div><div>(1:43:36 PM) khem: I have volunteered koen to be my proxy</div>
<div>(1:43:37 PM) RP__: election wise I was pleased to see the board has announced another election</div><div>(1:43:44 PM) khem: koen: that pact still stands I believe</div><div>(1:43:51 PM) fray: ya, I've volunteers Saul Wold to be mine.. ;)</div>
<div>(1:44:39 PM) ***Jefro notes - so far there are 11 people who have announced attendance at the GA</div><div>(1:44:54 PM) RP__: khem: I'm sorry to hear you're standing down but I'm guessing you're standing again :)</div>
<div>(1:45:19 PM) RP__: Jefro: some may have replied offlist to philip (I did)</div><div>(1:45:52 PM) Jefro: RP__ good point (I am setting up a room and need to know how big)</div><div>(1:47:02 PM) RP__: ok, we're through the topics - any other business?</div>
<div>(1:47:20 PM) RP__: I'm pressing on assuming people will jump in with anything that they want to say</div><div>(1:47:30 PM) khem: RP__: I have to make my mind.</div><div>(1:47:35 PM) khem: RP__: havent decided yet</div>
<div>(1:47:36 PM) ***Tartarus has no other business</div><div>(1:48:28 PM) Jefro: I could chime in & say that I fulfilled my action item to put together a wiki page with TSC minutes</div><div>(1:49:01 PM) RP__: khem: ok, your input has been valuable here but I can understand its also a commitment and the TSC's role is kind of ever changing</div>
<div>(1:49:04 PM) khem: I am reading about gerrit and other similar tools and try to make gold work on oe</div><div>(1:49:17 PM) RP__: Jefro: Thanks for doing that, its much appreciated!</div><div>(1:49:34 PM) fray: jefro, and a good wiki page it is....</div>
<div>(1:49:47 PM) Jefro: :) I only added links to minutes, someone else created the page</div><div>(1:50:46 PM) koen: gerrit pretty much requires using repo</div><div>(1:50:57 PM) ***koen isn't a big fan of either</div>
<div>(1:51:31 PM) Jefro: RP__ meeting adjourned?</div><div>(1:51:37 PM) RP__: hmm, I didn;t know it needed repo</div><div>(1:51:44 PM) RP__: Jefro: yes, meeting closed</div><div>(1:51:48 PM) RP__: thanks all!</div><div><br>
</div><font color="#888888"></font></span><font color="#888888"></font><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>