[16:00] <barry> #startmeeting
[16:00] <MootBot> Meeting started at 10:00. The chair is barry.
[16:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[16:00] <barry> hi everybody and welcome to this week's platform foundations meeting
[16:00] <barry> who's here today?
[16:01] <ev> hi
[16:01] <barry> [LINK] https://wiki.ubuntu.com/FoundationsTeam/Meetings/2010/0526
[16:01] <MootBot> LINK received:  https://wiki.ubuntu.com/FoundationsTeam/Meetings/2010/0526
[16:01] <mvo> hi
[16:01] <barry> cjwatson sends his apologies
[16:03] <mvo> looks like a small meeting :)
[16:03] <barry> doko, Keybuk: ping
[16:03] <Keybuk> hey
[16:03] <Keybuk> in a flame-war on fedora-devel-list
[16:03] <Keybuk> it's fun ;)
[16:03] <mvo> about what?
[16:03] <Keybuk> guess :p
[16:03] <mvo> heh :)
[16:03] <barry> :)
[16:03] <barry> [TOPIC] lightning round
[16:03] <MootBot> New Topic:  lightning round
[16:04] <barry> order: surbhi, barry, mvo, ev, Keybuk, doko
[16:04] <barry> but surbhi's not here, so...
[16:04] <barry> cj bug 545306 (SystemError); cj bug triage and pushed 2.0.1 to PPA (will ask mvo for sponsor upload); wikkid branch review for thumper, implemented packaging branch, blog post; hr goodness; sprint travel; maverick work items; dmb meeting (though my app is deferred until next meeting); foundations-m-python-continuous-integration discussion; quickly python-lib & bug 585617.  eot.
[16:05] <mvo> did: software-center work (branch merge backlog), update-manager SRU
[16:05] <mvo> working on: language-selector dbusification, workitems/specs
[16:05] <mvo> (done)
[16:05] <Keybuk> Watching and listening back to UDS recordings, and building up notes, etc.
[16:05] <Keybuk> Begun work on the Upstart 0.10 roadmap, going to be a largish document to pass around.
[16:05] <Keybuk> Some discussions with Fedora/RH people.
[16:05] <Keybuk> ~
[16:05] <doko> pong
[16:06] <barry> oops, we skipped ev :)
[16:06] <Keybuk> ev was too slow
[16:06] <barry> :)
[16:07] <barry> ev?
[16:07] <doko> done: eglibc-2.12 merge, gcc-4.3/gdc-4.3 updates, bank holiday, sick day
[16:07] <doko> --
[16:07] <ev> performance reviews, helping summer of code student (xnox) get usb-creator into debian, making a new usb disk for the shop, reviewing the new work Michael has done on the installer design spec, hacking on hudson to model the behavior I'm after for remastering CDs with a new ubiquity and testing them on lots of hardware.  Looks like I need to extend the locks-and-latches plugin to support shared locks.
[16:07] <ev> blocked: installer design spec (partially - I intend to start work on the multilayered debconf today/tomorrow)
[16:07] <ev> --
[16:07] <ev> sorry, ZNC disconnect
[16:08] <barry> [TOPIC] Outstanding actions from last meeting
[16:08] <MootBot> New Topic:  Outstanding actions from last meeting
[16:08] <ev> oh, and specs of course
[16:08] <barry> i think there were none?
[16:08] <ev> I don't recall any
[16:08] <barry> [TOPIC] Outstanding feature freeze exceptions
[16:08] <MootBot> New Topic:  Outstanding feature freeze exceptions
[16:08] <barry> probably not relevant at this point in the cycle?
[16:09] <barry> [TOPIC] Farming out tasks that aren't being handled
[16:09] <MootBot> New Topic:  Farming out tasks that aren't being handled
[16:09] <barry> nor is that i think...
[16:10] <barry> [TOPIC] Sponsorship queue
[16:10] <MootBot> New Topic:  Sponsorship queue
[16:10] <barry> [LINK] http://qa.ubuntu.com/reports/sponsoring/
[16:10] <MootBot> LINK received:  http://qa.ubuntu.com/reports/sponsoring/
[16:10] <dholbach> yes, please!
[16:11] <barry> since i don't have upload rights yet, is there anything i can do to help?  seems like we have a lot in this queue
[16:12] <dholbach> it'd be nice if everybody spent a bit of time getting stuff off the list that is not appropriate, https://wiki.ubuntu.com/UbuntuDevelopment/CodeReviews has more info about it
[16:12] <ScottK> barry: There are more than a few distribute/python-setuptools bugs that could use some attention from someone who understands how it's supposed to work.
[16:12] <dholbach> barry: if you find something that still needs work, I'm sure somebody on your team can lend you the powers to get it off the list temporarily :)
[16:13] <mvo> barry: if you have specific items that just need a upload I can do that
[16:13] <barry> ScottK, dholbach cool thanks.  i'll try to get some of that
[16:13] <barry> mvo: thanks
[16:13] <dholbach> awesome!
[16:13] <dholbach> thanks guys
[16:14] <barry> anything else on sponsorship?
[16:14] <barry> [TOPIC] Any business from activity reports
[16:14] <MootBot> New Topic:  Any business from activity reports
[16:15] <barry> ev: how's gsoc going?
[16:15] <ev> barry: brilliantly
[16:15] <ev> Dmitrijs has really hit the ground running
[16:15] <cjwatson> here, sorry I'm late
[16:16] <barry> awesome!  thanks so much for mentoring the next generation of ubuntu hackers :)
[16:16] <cjwatson> done: finished writing up specs; dove into merging; added packageset seed permission exceptions
[16:16] <mvo> my guy (donkult) is also doing great in SoC
[16:16] <cjwatson> todo: didn't really manage to get started on foundations-m-cd-boot much, except for bringing it up with upstream, so will do some more on that this week
[16:16] <ev> I've already merged a few branches from him and as mentioned, he's actively working to get usb-creator in Debian.  He's milestoned a console frontend for early next month.
[16:16] <barry> cjwatson: thanks
[16:16] <barry> ev: nice; mvo, sorry what is your guy working on again?
[16:17] <mvo> barry: multiarch support in apt
[16:17] <barry> rock on
[16:17] <cjwatson> oh, and alpha-1 next week, so expecting to be plugging away at that
[16:17] <mvo> but he also worked on general apt stuff, I uploaded apt into debian-experimental with some basic support recently
[16:17] <mvo> upgrades via lucid->maverick should work now too btw
[16:18] <mvo> via update-manager
[16:18] <mvo> and do-release-upgrade
[16:18] <barry> mvo: very cool, i will try that in a vm today
[16:18] <barry> mvo: what kind of stuff is he doing to apt?
[16:18] <ev> mvo: out of curiosity, are you having him write an Ubuntu spec and add work items to the foundations page of the tracker? I've asked Dmitrijs to do that on the theory that it will make him feel like more of a member of Foundations, as we're all working to get below the red line.
[16:18] <mvo> you need to set /etc/update-manager/release-upgrades to "normal" instead of lts
[16:18] <barry> mvo: right, thanks, i'd forgotten about that
[16:19] <mvo> ev: technically he is part of debian, we did a swap with debian for some organisational reason
[16:19] <ev> ahh
[16:19] <ev> fair enough :)
[16:19] <mvo> barry: yeah, its a common thing, I need to fix that so that its more obvious :/
[16:19] <mvo> ev: :)
[16:20] <barry> [TOPIC] Good news
[16:20] <MootBot> New Topic:  Good news
[16:20] <mvo> SoC!
[16:21] <ev> hear hear
[16:21] <barry> i guess the fact that prague is confirmed is good news too :)
[16:22] <barry> [TOPIC] AOB
[16:22] <MootBot> New Topic:  AOB
[16:23] <ev> Mumble!  Everyone jump on the bandwagon
[16:23] <ev> So far it's just me, Colin, and rarely Scott in the foundations room
[16:24]  * barry will try it this week
[16:24] <barry> but i think i will be lonely later in the day :)
[16:25] <cjwatson> specs
[16:25] <Keybuk> ev: the rarely scott is more of a factor that I've spent most of my time listening to uds tapes
[16:25] <cjwatson> two people have replied to my plea for data so far :)
[16:25] <cjwatson> which is good but I was hoping for a few more
[16:25] <Keybuk> and being interrupted by "evan was moved in from root by server" is irritating ;)
[16:25] <Keybuk> especially since Colin sits so far away from microphones that I have the volume up so loud, that when you move in from root, people down the road know about it
[16:25] <barry> Keybuk: any good sessions we might have missed that are worth a listen?
[16:25] <ev> Keybuk: we have the source code to Mumble, donchaknow
[16:26] <ev> comment that line out
[16:26] <cjwatson> if you haven't finished yet, please at least send me the list of specs you're working on drafting, so that (a) I can see which ones *nobody* is drafting, and (b) I can make sure they're all targeted to maverick so that they show up on our work items list
[16:26] <cjwatson> the sooner this gets done, the more accurate the start point on our work items graph can be
[16:26] <Keybuk> cjwatson: err, I apparently have no specs ;-)
[16:26] <cjwatson> ?
[16:27] <cjwatson> I thought there was foundations-m-finish-upstart at least
[16:27] <Keybuk> there's no spec for that though
[16:28] <Keybuk> and those I am putting together are on launchpad.net/upstart
[16:28] <Keybuk> which can't be targeted to maverick
[16:28] <cjwatson> well, fine, but telling me "zero" is better than not replying to my mail. :-)
[16:28] <Keybuk> (cause I have to pretend other distros are going to use upstart next cycle :p)
[16:28] <cjwatson> that way, at least I know
[16:28] <Keybuk> cjwatson: I'm telling you zero now ;)
[16:28] <cjwatson> ack
[16:28] <cjwatson> perhaps we can figure out a way of getting upstart specs onto the WI list
[16:29] <cjwatson> it really helps me to see what's going on for everyone
[16:29] <Keybuk> yes, I have on my todo to talk to pitti to get the work items included in that list
[16:29] <Keybuk> e.g. whether pitti can just include the upstart 0.10 milestone as a maverick one
[16:29] <cjwatson> if you're happy for that to be done, I can probably take care of it
[16:29] <Keybuk> oh, definitely happy for that
[16:30] <cjwatson> are all the specs you're planning on working on targeted for 0.10 already, then?
[16:30] <Keybuk> no
[16:30] <Keybuk> none of them exist yet
[16:30] <Keybuk> roadmap first, roadmap produces specs
[16:30] <cjwatson> ok
[16:30] <Keybuk> roadmap I intend to be finished with tomorrow/friday
[16:30] <cjwatson> tell me when you have something so that I have test cases? :-)
[16:30] <Keybuk> and then send that round people, to get feedback
[16:30] <Keybuk> while I write up the initial specs for those parts of the roadmap that are doable for maverick
[16:31] <Keybuk> kk
[16:31] <barry> question for y'all: in the future does it make more sense to just update the meeting wiki page with your activity reports yourself, or should we still send them into the meeting chair?
[16:31] <Keybuk> https://launchpad.net/upstart/+milestone/0.10.0
[16:31] <Keybuk> ^ is the milestone
[16:31] <cjwatson> ok
[16:32] <Keybuk> sorry, I just squeed myself with the 0.6.6 codename again
[16:33] <barry> oh well, anyway :)
[16:33] <cjwatson> barry: I don't mind either way
[16:33] <barry> [TOPIC] next week's chair
[16:33] <MootBot> New Topic:  next week's chair
[16:33] <cjwatson> as long as it gets done
[16:34] <barry> cjwatson: yeah, maybe it's better that the chair can ride herd
[16:34] <barry> any volunteers for next week?
[16:35]  * ev raises hand
[16:35] <barry> ev: thanks!
[16:35] <barry> and if there's nothing else, that's it!
[16:35] <barry> 5
[16:35] <barry> 4
[16:35] <barry> 3
[16:35] <barry> 2
[16:36] <barry> 1
[16:36] <barry> #endmeeting
[16:36] <MootBot> Meeting finished at 10:36.
[16:36] <ev> thanks!
[16:36] <barry> thanks everybody!
[16:36] <barry> (send those activity reports :)
[16:36] <mvo> thanks
[17:58]  * ara waves
[17:58]  * fader_ waves.
[17:59] <pedro_> hello!
[17:59] <sbeattie> hey!
[17:59] <Paddy_NI> Is there any documentation about what is typically covered by the Q&A team?
[18:00] <ara> Paddy_NI, qa.ubuntu.com will point you to the right place
[18:00] <hggdh> ~o~
[18:00] <Paddy_NI> Thank you
[18:00] <fader_> Paddy_NI: Not sure if you're looking for "Questions and Answers" or "Quality Assurance" -- this meeting is for the latter :)
[18:00] <thekorn> hey Q&A team
[18:00] <Paddy_NI> ah
[18:00] <Paddy_NI> :)
[18:01] <fader_> Though we're certainly happy to help with QA Q&A :)
[18:01] <ara> OK, let's get started
[18:01] <hggdh> hi thekorn
[18:01] <ara> #startmeeting
[18:01] <MootBot> Meeting started at 12:01. The chair is ara.
[18:01] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[18:01] <ara> Agenda, as usual, at https://wiki.ubuntu.com/QATeam/Meetings
[18:02] <ara> # SRU testing -- sbeattie (Steve Beattie)
[18:02] <ara> # Bug Day status -- pvillavi
[18:02] <ara> # Results of the meetings time poll - ara
[18:02] <ara> # Blueprints update -- all
[18:02] <ara> # Laptop Testing wiki cleanup - ara
[18:02] <ara> # Sound Card Compatibility Testing - awbancroft
[18:02] <ara> # Selection of new chair - ara
[18:02] <ara> [TOPIC] SRU testing -- sbeattie (Steve Beattie)
[18:02] <MootBot> New Topic:  SRU testing -- sbeattie (Steve Beattie)
[18:02] <sbeattie> SRU Activity report for the past week (since 2010-05-19):
[18:02] <sbeattie> * lucid: 20 new packages in -proposed (abiword, chromium-browser, exo, gnome-screensaver, gtk+2.0, gtkmm2.4, hamster-applet, librsvg, netbook-launcher, netbook-meta, openssh, pm-utils-powersave-policy, postgresql-8.4, pygtksourceview, python-apt, rhythmbox, telepathy-butterfly, totem, vinagre, virtuoso-opensource)
[18:02] <sbeattie>      and 11 packages pushed to -updates (apt, bareftp, edubuntu-artwork, glibmm2.4, jockey, pangomm, php5, rcmdr, software-center, unetbootin, xsane)
[18:02] <sbeattie> * karmic: 2 new packages in -proposed (postgresql-8.4, virtualbox-ose)
[18:02] <sbeattie>       and 1 package pushed to -updates (kdepimlibs)
[18:02] <sbeattie> * jaunty: 2 new packages in -proposed (postgresql-8.3, virtualbox-ose)
[18:02] <sbeattie>       and 2 packages pushed to -updates (sun-java6)
[18:02] <sbeattie> * hardy: 2 new packages in -proposed (apache2, postgresql-8.3)
[18:02] <sbeattie> * dapper: 1 new package in -proposed (postgresql-8.1)
[18:02] <sbeattie> Thanks to Wolfgang Kufner, Takkat, Charlie Kravetz (charlie-tca), Irihapeti, Dietmar, slumbergod, Andreas Wenning (a|wen), Leo, Filip Palm, Jens Langner, Jean-François Fortin Tami (nekohayo), areskz, Steffen Krumbholz, Pirouette Cacahuète, Thorsten Reinbold, Maciej Bęcławski (Hakkatuka), Jonathan Thomas (JontheEchidna), Numérigraphe, Hagen Fürstenau, Scott Kitterman (ScottK), Jan Schneider (yunosh), João Neves, and othe
[18:02] <sbeattie> rs for testing SRUs this week.
[18:03] <sbeattie> Nice to see the amount of SRUs for lucid calming down a bit.
[18:03] <ScottK> Don't worry.  Working on more.
[18:03] <hggdh> heh
[18:03] <pedro_> heh
[18:03] <sbeattie> ScottK: I'd never doubt you!
[18:03] <sbeattie> Plenty still out there for people to test: http://people.canonical.com/~ubuntu-archive/pending-sru.html
[18:03] <fader_> Job security ;)
[18:04] <sbeattie> (that's all I have unless there's any questions)
[18:04] <ara> OK, let's move on. Thanks sbeattie!
[18:05] <ara> sbeattie, before that, I have a question
[18:05] <ara> sbeattie, is there a place in the wiki where you publish this same report?
[18:05] <sbeattie> ara: no, but I can.
[18:06] <ara> well, I don't want to put more work on you, at least it is something people might be interested in
[18:06] <sbeattie> ara: any particular location you'd like it published?
[18:06] <ara> somewhere under https://wiki.ubuntu.com/StableReleaseUpdates ?
[18:07] <sbeattie> Okay, I thought perhaps under the QATeam somewhere, but that might work as well.
[18:07] <ara> sbeattie, yes, maybe under QATeam makes more sense and it is easier to find
[18:08] <ara> sbeattie, a link from SRU won't do any harm, though
[18:08] <hggdh> ideally, we should link to current/proposed off w.u.c/SRU
[18:08] <hggdh> and, of course, to thank-yous
[18:09]  * sbeattie takes an action item
[18:09] <hggdh> sbeattie: sorry for the additional work...
[18:09] <ara> [ACTION] sbeattie to create a wiki page of history of SRUs
[18:09] <MootBot> ACTION received:  sbeattie to create a wiki page of history of SRUs
[18:10] <ara> [TOPIC] Bug Day status -- pedro_
[18:10] <MootBot> New Topic:  Bug Day status -- pedro_
[18:10] <pedro_> On Thursday 20 we had a bug day based on Update Manager:
[18:10] <pedro_> https://wiki.ubuntu.com/UbuntuBugDay/20100520
[18:11] <pedro_> ~41 bugs were triage. Thanks a bunch to our bug day heroes:  txwikinger, micahg, kamusin, mistrynitesh, brunogirin, jibel, yofel, paulduf, odd-rationale, gregbair and effie-jayx
[18:11] <pedro_> you guys rock ;-)
[18:11] <pedro_> Tomorrow our bug day target will be the Epiphany Browser
[18:11] <pedro_> https://wiki.ubuntu.com/UbuntuBugDay/20100527
[18:12] <pedro_> There's plenty of bugs waiting to be triaged, so if you have some time and want to learn a bit more about bug triage join us, we'll be glad to help you to start
[18:12] <ara> pedro_, let's hope those bugs don't get triage to the epiphany package ;-)
[18:12] <pedro_> as always the bug day is going to happen on #ubuntu-bugs ;-)
[18:12] <pedro_> ara, lol, yeah hope that too ;-)
[18:13] <bdmurray> maybe looking at epiphany bugs and making sure they are not epiphany-browser bugs would be a good idea
[18:13] <pedro_> nibel already sent a notice to the bugsquad mailing list about that
[18:13] <hggdh> Nigel, you meant?
[18:14] <pedro_> bdmurray, good idea indeed, i'll put that in the wiki page
[18:15] <pedro_> that's all from here ara
[18:15] <qense> hello
[18:15] <ara> pedro_, cool, thanks!
[18:15] <ara> qense, hi :)
[18:15] <ara> [TOPIC] Results of the meetings time poll - ara
[18:15] <MootBot> New Topic:  Results of the meetings time poll - ara
[18:16] <ara> As you know, we conducted a poll to ask for a different time for this meeting to rotate every other week
[18:16] <ara> The most voted hour was 19:00 UTC, with 17 votes
[18:17] <qense> Which confirms this time is a very good one.
[18:17] <qense> wait
[18:17] <qense> CEST != UTC
[18:17] <ara> qense, we are at 17:00UTC ;-)
[18:17] <charlie-tca> they want it two hours later
[18:17] <qense> whoops
[18:17] <ara> From now on we will be rotating this meeting one week at 17:00 UTC, the following at 19:00 UTC
[18:17] <fader_> That makes it even worse for you, ara :/
[18:18] <ara> fader_, yes, but I have to accommodate to the rest of the ubuntu qa team!
[18:18] <ara> fader_, and it is every other week, I will survive (I hope)
[18:18] <fader_> :)
[18:18]  * fader_ should have stuffed the ballot box.
[18:19] <ara> the chair of the meeting (who also rotates) will send the reminder a couple of days before to the mailing list
[18:19] <sbeattie> ara: have we confirmed 1900 UTC is available?
[18:19] <ara> sbeattie, very good point, indeed
[18:19] <ara> sbeattie, we haven't!
[18:19]  * ara reads fridge.ubuntu.com
[18:20] <pedro_> fridge says Edubuntu Meeting at 1900 UTC on Wed
[18:20] <qense> aww
[18:20] <ara> that's unfortunate
[18:21] <ara> what do you guys recommend doing?
[18:21] <ara> stgraber, how often do you have edubuntu meetings? it is every week? every other week?
[18:21] <fader_> If it goes back to a vote again, I suggest that we have only available slots to vote on
[18:21] <fader_> Or we beat up stgraber and steal his slot ;)
[18:22] <charlie-tca> move it to 20:00 ?
[18:22] <qense> that was the second choice, wasn't it?
[18:22] <sbeattie> I guess I'd like to understand why so many people can't make the current timeslot but can make it 2-3 hours later? conflict with work?
[18:22] <charlie-tca> 2000 was not a choice. it went by two hour increments
[18:22] <sbeattie> (but it's probably better to ask on the mailing list)
[18:22] <ara> I guess it is a matter of work conflicts
[18:23] <ara> who can take the action to talk with stgraber and check how often they have meetings?
[18:23] <bdmurray> What is the advantage to having the meeting here?
[18:23] <qense> good question
[18:23] <ara> bdmurray, the bot?
[18:23] <qense> I mean, it's not like #ubuntu-quality is too busy to use.
[18:23] <sbeattie> or are most of the people that were available at 1900 also available for the current time?
[18:23] <bdmurray> bingo!
[18:24] <ara> so, options are:
[18:24] <ara> 1) revote again with only available slots
[18:25] <ara> 2) talk to stgraber and check if they have meetings every week or not
[18:25] <ara> 3) install a meeting bot in #ubuntu-quality and move the meeting there
[18:25] <ara> what do you guys think?
[18:25] <bdmurray> well I'd say 3 is plan B for 2
[18:26] <hggdh> +1 with Brian
[18:26] <qense> bdmurray, +1
[18:26] <hggdh> we go 2 and, if needed, 3
[18:26] <ara> +1
[18:26] <hggdh> will there be a vote (official)?
[18:27] <ara> hggdh, on what?
[18:27] <hggdh> new times ;-)
[18:27] <qense> this
[18:27] <hggdh> otherwise, I would say this is done
[18:27] <ara> I think we can move on, but who take the action on talking with stgraber?
[18:28] <hggdh> I will
[18:28] <ara> hggdh, thanks!
[18:28]  * hggdh thinks its time to go and really do something ;-)
[18:28] <ara> [ACTION] hggdh to talk with stgraber about Edubuntu meetings frequency
[18:28] <MootBot> ACTION received:  hggdh to talk with stgraber about Edubuntu meetings frequency
[18:29] <ara> [TOPIC] Blueprints update -- all
[18:29] <MootBot> New Topic:  Blueprints update -- all
[18:29] <ara> OK, anyone wants to give updates on their blueprints?
[18:29] <qense> pedro_: How are the responses from mentors and students going?
[18:29] <qense> Blueprint: qa-maverick-mentoring-program
[18:30] <pedro_> qense, just waiting an extra day for getting more responses, but so far so good
[18:30] <qense> pedro_: Many people wanting to stay?
[18:31] <pedro_> qense, yes, so far we only have 1 person who decided to step down and 1 update (ogasawara->JFo)
[18:31] <qense> ok
[18:31] <qense> good
[18:31] <pedro_> qense, i'll be sending the updates by the end of this week
[18:31] <qense> By the way, is everyone here familiar with the changes we decided for the Bug Squad's mentoring programme?
[18:31] <qense> pedro_: great, thanks
[18:32] <ara> qense, a brief summary will be nice :)
[18:32] <qense> the session at the UDS was only attended by hggd, pedro_, two other guys whose name I can't remember and I.
[18:32] <qense> ara: OK
[18:32] <qense> Well, the first thing we said was that it was clear the mentoring programme wasn't exactly working perfectly. We had some mentors on the list, and there were some students on that list as well, but no one was really doing much.
[18:33] <qense> Students wouldn't show up after someone would have accepted them, mentors rarely did accept students.
[18:33] <qense> We saw that it was needed to get some people that would do the assignment of students because otherwise it would not happen.
[18:34] <qense> We decided on a mentorship 'admins' group, consisting of hggdh, pedro_, charlie-tca and myself (for optimal timezone coverage), which would be reponsible for assigning students to mentors.
[18:34] <qense> It would then be up to the mentors to do the rest.
[18:34] <ara> qense, nice, it reminds me to the ubuntu-packaging-coordinators team
[18:34] <qense> They would also have to give a monthly status update during either one of the weekly Bug Squad meetings, or via the mailing list.
[18:35] <hggdh> BTW, we would still like to get an admin from the Asia/Pacific TZ, in order to cover all TZs
[18:35] <qense> good point from hggdh
[18:35] <qense> Now pedro_ has sent mails to all current students and mentors asking if they still want to get mentored or mentor and we're waiting for their response.
[18:35] <qense> Like pedro_ said we will wait for a bit longer and then update the wiki page and clean up.
[18:36] <qense> New, fresh start
[18:36] <qense> the wiki page should only containt he current mentors witht heir current, accepted students.
[18:36] <qense> THE END
[18:36] <ara> qense, :)
[18:36] <ara> qense, thanks!
[18:36] <qense> Any questions?
[18:36] <hggdh> qense, good summary, thank you
[18:36] <pedro_> qense, thanks for the summary ;-)
[18:36] <qense> you're welcome, thank you :)
[18:37] <ara> I will talk a bit about qa-maverick-improve-iso-tracker
[18:37] <ara> [LINK] https://blueprints.launchpad.net/ubuntu/+spec/qa-maverick-improve-iso-tracker
[18:37] <MootBot> LINK received:  https://blueprints.launchpad.net/ubuntu/+spec/qa-maverick-improve-iso-tracker
[18:37] <ara> we need to fix and improve the ISO tracker a bit in order to fill our requirements while we wait for the new "Results Tracker"
[18:38] <ara> I know, it is Drupal, it is PHP, it is ugly
[18:38] <ara> But... if you know how to code that ugly language called PHP and feel like contributing, let me know :)
[18:39] <fader_> Why all the PHP hate?  It's not like it's perl ;)
[18:39] <ara> Right now I have assigned all the tasks to myself, and I will be happy to reassign some of them :-)
[18:39]  * hggdh hides
[18:39] <ara> Write PHP! Help the ISO tracker! PHP is fun! :D
[18:39]  * txwikinger programs PHP everyday
[18:39]  * hggdh looks, full of hope
[18:40] <txwikinger> what do you guys need?
[18:40] <ara> txwikinger, you're hired!
[18:40] <ara> txwikinger, I'll send you an email with the details, and you decide :-)
[18:40] <txwikinger> ok. ara
[18:40] <fader_> ara: Some of them look pretty easy for even beginners at PHP, e.g. bug 578349
[18:41] <ara> fader_, yes
[18:41] <qense> Isn't there actually a trim() function?
[18:41] <ara> qense, yes, yes, you can get that one :P
[18:41] <fader_> Darn it, that was my secret weapon!
[18:42] <txwikinger> qense: yes
[18:42] <ara> any other blueprint?
[18:43] <ara> OK, moving on, then
[18:43] <ara> [TOPIC] Sound Card Compatibility Testing - awbancroft
[18:43] <MootBot> New Topic:  Sound Card Compatibility Testing - awbancroft
[18:43] <ara> mmm, it looks like awbancroft is not around
[18:44] <ara> I'll send him an email to see if wants to add the topic for next week's meeting
[18:44] <ara> [TOPIC] ara to send an email to awbancroft about Sound Card Compatibility Testing
[18:44] <MootBot> New Topic:  ara to send an email to awbancroft about Sound Card Compatibility Testing
[18:44] <ara> [ACTION]  ara to send an email to awbancroft about Sound Card Compatibility Testing
[18:44] <MootBot> ACTION received:   ara to send an email to awbancroft about Sound Card Compatibility Testing
[18:44] <ara> that's better :-)
[18:44] <qense> Otherwise we'd have to discuss that mail.
[18:44] <qense> here
[18:45] <ara> [TOPIC] Selection of new chair
[18:45] <MootBot> New Topic:  Selection of new chair
[18:45] <ara> So, who wants to be the chair of next meeting?
[18:45]  * ara sees how people are hiding
[18:46] <qense> I'll be on an island next week, without a computer.
[18:46] <qense> for real
[18:46] <sbeattie> ara: I can do it.
[18:46] <ara> sbeattie, thanks :-)
[18:47]  * hggdh unhides self
[18:47]  * charlie-tca unhides too
[18:47] <ara> OK, that was the agenda for today. Any other topics?
[18:47] <qense> ara: The laptop testing wiki thing was discussed before I remembered this meeting and joined the channel?
[18:47] <sbeattie> I assume for next week, we'll keep it at 1700 UTC, unless we get resolution on the dubuntu conflict?
[18:48] <sbeattie> err, edubuntu conflict?
[18:48] <hggdh> sbeattie: I think this is a good approach
[18:48] <ara> sbeattie, +1
[18:48] <qense> agreed
[18:48] <ara> qense, no, the person in charge of that work (primes2h) is not here
[18:48] <ara> qense, we will get back to that one in following meetings
[18:49] <qense> ok
[18:49] <ara> Anything else?
[18:49] <ara> going once...
[18:50] <ara> going twice...
[18:50] <ara> OK, I think we can finish the meeting
[18:50] <ara> #endmeeting
[18:50] <MootBot> Meeting finished at 12:50.
[18:50] <hggdh> thank you, ara
[18:50] <sbeattie> thanks ara!
[18:50] <ara> Thanks everyone!
[18:50] <qense> thank you ara!
[18:50] <fader_> Thanks all
[18:51] <bladernr__> thanks ara, that was a much larger meeting than I've seen previously
[18:51] <bladernr__> thanks all too
[20:04]  * stgraber waves
[20:05]  * bencrisford waves back
[20:06]  * highvoltage jumps in the channel and makes big waves
[20:07] <alkisg> Hi all
[20:07] <bencrisford> alkisg: hello :)
[20:08] <highvoltage> everyone feeling good?
[20:08] <bencrisford> the weather is getting brighter, and despite that im naturally happy today for some reason!  im feeling great! :)
[20:09] <alkisg> Yup, everything fine here
[20:09] <highvoltage> great.
[20:09] <highvoltage> let's jump right in
[20:09] <highvoltage> here are the blueprints from UDS:
[20:09] <highvoltage> https://blueprints.edge.launchpad.net/ubuntu/+spec/community-maverick-edubuntu-community
[20:09] <stgraber> a good > 30C outside here, /me loves AC
[20:09] <highvoltage> https://blueprints.edge.launchpad.net/ubuntu/+spec/foundations-maverick-edubuntu-ubiquity
[20:09] <highvoltage> https://blueprints.edge.launchpad.net/ubuntu/+spec/community-maverick-edubuntu-packages
[20:10] <highvoltage> last week I did some triaging on what specs actually need to be written from them
[20:10] <highvoltage> but I keep changing my mind and keep going into a panic for no good reason :)
[20:11] <highvoltage> I'm just going to past some of it here and perhaps we can discuss it
[20:11] <highvoltage> and- maybe we can get some more people involved in doing it
[20:11] <highvoltage>     *  NEEDS-SPEC: Edubuntu advocacy- Forums for teachers on website, Facebook group?, feed on website for teacher blogs, create mailing list for educators (discontinue ubuntu-education), some kind of forum for teachers to provide edu-tips
[20:11] <highvoltage>     * COUNCIL: Approve LP Team changes
[20:11] <highvoltage>     * NEEDS-SPEC: Edubuntu Stable PPA
[20:11] <highvoltage>     * NEEDS-SPEC: Edubuntu Menu Editor Improvements, get feedback from our users (guadalinex-edu menus) (mgariepy?)
[20:11] <highvoltage> so that's from the edubuntu-community blueprint
[20:12] <highvoltage> I'm not sure if we'd have to retro-actively make a new blueprint for each spec since you can only link one spec to a blueprint
[20:12] <highvoltage> (argh)
[20:12] <highvoltage> I'm thinking that we probably need more of a to-do list than specs for our community items
[20:13] <highvoltage> any thoughts?
[20:13] <sbalneav> Present
[20:13] <highvoltage> yay
[20:13] <stgraber> hey sbalneav
[20:13] <highvoltage> sbalneav: we missed you
[20:15] <highvoltage> *crickets.wav*
[20:15] <alkisg> highvoltage: we also need a wiki page for the live ltsp
[20:15] <alkisg> Lots of people asked for that
[20:15] <alkisg> And I really like the idea of the stable ppa
[20:16] <highvoltage> alkisg: I noticed, I answered some questions on some bugs about it and also the questions on the list.
[20:16] <alkisg> (and also an accompanying testing ppa)
[20:16] <sbalneav> Yeah, the live ltsp seems to work, but I've seen some issues with people not being able to INSTALL ltsp
[20:17] <sbalneav> from the dvd.  Do we know what's up with that?
[20:17] <highvoltage> so, we currently have a Roadmap page on the wiki that we could probably use more, should I make our community items to-do list items there?
[20:19] <highvoltage> sbalneav: we haven't received a bug report / list message about it yet
[20:19] <highvoltage> sbalneav: could you perhaps ellaborate on some of those issues?
[20:20] <sbalneav> I'll dig up the list messages I've seen.
[20:20] <highvoltage> ah, on the LTSP list?
[20:20] <sbalneav> yeah
[20:20] <sbalneav> I think that's where they were
[20:20] <highvoltage> I haven't been paying good attention there lately so I'll go look
[20:21] <highvoltage> I remember seeing one message there from someone who tried to start ltsp-live on two different interfaces, but iirc that was all
[20:21] <highvoltage> sbalneav: does LTSP upstream use LP for bugs or its own bug tracker?
[20:22] <highvoltage> (it uses LP, I know that, sorry my brain doesn't want to brain)
[20:22] <sbalneav> heh
[20:22] <sbalneav> My brain *never* brains.
[20:22] <sbalneav> so don't feel bad.
[20:23] <highvoltage> sbalneav: would be great to encourage them to file a bug on it if they want to, I get the LTSP bugmail at least
[20:24] <sbalneav> ok, will do.
[20:24] <sbalneav> anyone had a chance yet to dig into the updated xexit in my ppa?
[20:24] <highvoltage> ok, about those blueprints and specifications, I'll send a summary to the list then for feedback, doesn't seem like anyone wants to discuss it tonight :)
[20:26] <highvoltage> sbalneav: how does it work?
[20:26] <highvoltage> you say it's a lot lighter than the older tools that did the same thing?
[20:27] <sbalneav> right.
[20:27] <sbalneav> it's a small C program that basically installs an X onerror handler
[20:28] <sbalneav> as well as launch a thread to keep pinging the display.
[20:28] <sbalneav> when the display dissapears, it runs a script.
[20:28] <sbalneav> which just searches /etc/Xexit.d, and executes any scripts in there (run-parts type script).
[20:29] <sbalneav> I can log in with a thin client, yank the power cord, and all user processes dissapear in 15 seconds.
[20:29] <sbalneav> alkis was looking for something better than gnome-watchdog, so I coded this up.
[20:29] <stgraber> interesting, the ltsp-cluster accountmanager does the job for us, but it's clearly a nice thing for erveryone else ;)
[20:29] <highvoltage> oh cool, I like that you can put scripts in there
[20:30] <alkisg> sbalneav: it'd be nice to have this upstream, maybe as an lts.conf option...
[20:31] <stgraber> alkisg: that's to be run on the server side, so unless upstream changed it's ideas, it shouldn't be part of LTSP as we try not to require any additional component on the server side (other than SSH that's)
[20:31] <highvoltage> I was actually going to ask whether it's suitable for including in Edubuntu, but if it would go into upstream that would probably be simpler
[20:31] <sbalneav> alkisg: Well, the only reason I *WOULDN'T* want it as part of LTSP is that even on the console, gnome/kde leave "droppings" around when you log out.
[20:31] <sbalneav> so I'm thinking it might be handy as a standalone package, but I'm easy.
[20:31] <sbalneav> and cheap.
[20:32] <highvoltage> sbalneav: if you have some time over the next few weeks we could get it into universe
[20:32] <highvoltage> sbalneav: you've already had lots of packaging practise so it shouldn't take too long :)
[20:33] <highvoltage> stgraber: I guess something like xexit could fall under edubuntu-dev once it's in the archives? then sbalneav would be able to update it quite easily
[20:34] <alkisg> ...and we could backport it to the edubuntu stable ppa for lucid ;)
[20:34] <stgraber> I guess so
[20:34] <highvoltage> that would be a nice package for the stable ppa indeed
[20:37]  * Lns rushes in
[20:39] <highvoltage> sbalneav: I checked the ltsp list and couldn't find those messages, but if you do please pass them along
[20:40] <Lns> sbalneav: sounds like an awesome addition :) thank you! stgraber: how does the ltsp-cluster accountmanager differ in its operation from xexit?
[20:40]  * alkisg notes that it'd be nice if some of the cluster functionality could also work in single server environments...
[20:40] <highvoltage> sbalneav: the ltsp installer currently is quite simplistic, for the one that's going to be embedded in ubiquity we'd ideally want options to configure networking nicely and things like bridging and bonding. not 100% sure exactly how nice we'll get this for maverick, but I do think we can make some good progress at least
[20:45] <highvoltage> slow meeting tonight :)
[20:46] <bencrisford> yep
[20:46] <bencrisford> :)
[20:48] <highvoltage> well, is there anything else or shall we adjourne and continue anything else in #edubuntu?
[20:48] <Lns> what's wrong with adding functionality server-side for stuff like xexit? Sounds like a totally sane addition to me.
[20:48] <Lns> highvoltage: just that from me ;)
[20:49] <highvoltage> Lns: well, if adding it to upstream ltsp would break stuff like ltsp-cluster or other scripts and implementations, then it might not be a great idea :)
[20:50] <highvoltage> Lns: I suppose making it easy to install would be a good start and then we take it from there
[20:50] <bencrisford> highvoltage: I don't have anything, unless anyone has any ideas regarding marketing materials
[20:50] <Lns> oh. yeah :) that makes sense. Of course I'm sure if it's a separate package it can just do the whole remove-other-package-thingie that apt likes to do with conflicts
[20:51] <Lns> bencrisford: what specifically regarding marketing materials? WHat's the status on marketing campaign?
[20:51] <bencrisford> Lns: just general marketing stuff, because we dont have any, and I think its important that we put some out there
[20:51] <bencrisford> leaflets to locos, web buttons to people who will wear them on their site, and other stuff.. :)
[20:52] <Lns> I have some material from a while ago
[20:52] <Lns> i dunno if it'll help but I can show it to you
[20:52] <bencrisford> Lns: that would be awesome :)
[20:53] <bencrisford> there is a bzr branch for the edubuntu-advocacy materials for sharing marketing stuff
[20:53] <bencrisford> edubuntu advocacy team*
[20:53] <Lns> oh nice. well we can chat in #edubuntu about that
[20:54] <highvoltage> we also decided to use the ubuntu-education list for teachers, etc using ubuntu and edubuntu
[20:54] <highvoltage> the list used to be abandoned but Charles Profitt picked it up
[20:55] <Lns> honestly sounds like a lot of different places to go for such a small project...jmho!
[20:55] <Lns> do we need that many different facilities?
[20:56] <Lns> bencrisford: http://logicalnetworking.net/other/edubuntuposter.png is one thing I had made a while back
[20:56] <Lns> http://logicalnetworking.net/other/TuxInSchoolComputerLab.png - another one
[20:56] <highvoltage> Lns: it is, although the need for a platform for non-technical users has been strongly identified
[20:57] <Lns> highvoltage: platform meaning what, a listserv?
[20:57] <bencrisford> Lns: Loving the posters!  Nice work :)
[20:57] <alkisg> Lns, those are cool!
[20:57] <Lns> bencrisford: also, a shirt I have a few left of and could make more if people want them: http://logicalnetworking.net/other/school-oss-shirt-front.jpg  and http://logicalnetworking.net/other/school-oss-shirt-back.jpg
[20:57] <Lns> See, I'm good at the visionary stuff..not so good at the programming part ;)
[20:58] <bencrisford> those are cool! :)
[20:58] <highvoltage> Lns: listserv, web forums, facebook... it's going to take some experimenting. we basically have to use what educators use, there's a few suggestions that seem good so we'll have to use a bit of trial and error
[20:59] <Lns> highvoltage: as far as exposure, all of the above is a good idea :) facebook, youtube, even myspace (!!), twitter too
[20:59] <highvoltage> Lns: cute :)
[20:59] <Lns> besides the normal list/irc/etc
[20:59] <highvoltage> Lns: yeah videos are a great way to show off things
[20:59] <Lns> I have a t-shirt maker in my office building that does it for way cheap. So if you guys have suggestions or artwork you want on shirts, hit me up.
[21:00] <Lns> You guys have all seen the video i did for ltsp in education right?
[21:00] <bencrisford> Lns: nope
[21:00] <alkisg> Yup
[21:00] <Lns> it's not edubuntu specific, kinda a marketing-y thing for my company but it can be used for whatever. I tried to make it as non-LNS specific as possible
[21:00] <bencrisford> I love the youtube+twitter ideas :)!
[21:00] <Lns> k for those who haven't seen it: www.youtube.com/logicalnetworkingnet
[21:01] <Lns> it's the first/featured video on that chan
[21:01] <Lns> yeah - twitter would be great to put a feed on front edubuntu.org page
[21:01] <Lns> makes the site more "live"
[21:01] <highvoltage> well, that's it for this week's meeting time, thanks for attending!
[21:01] <Lns> thanks highvoltage et al.
[21:01] <alkisg> Thanks & bye all
[21:01] <highvoltage> Lns: the new site will have that, I'll have to put some more pressure on Hedgemadge, she's really great but has been way too busy recently
[21:02] <stgraber> thanks
[21:02] <highvoltage> Lns: and I kind of feel bad for having to put more pressure on her, but we really need to replace our old site
[21:03] <Lns> highvoltage: is she in the middle of it all?
[21:03] <bencrisford> Lns: love the video :)
[21:03] <Lns> bencrisford: hehe thanks
[21:03] <Lns> the guy who produced it actually used to work at google =)
[21:03] <Lns> one of the benefits of living near silicon valley
[21:04] <highvoltage> Lns: yep, she needs to tar up the db and some other files she has that's not in bzr
[21:04] <Lns> that's cool
[21:04] <Lns> ok i'm gonna hop on #edubuntu
[21:05] <bencrisford> as am I
[21:05] <bencrisford> :)
[21:05]  * highvoltage 3
[21:06] <bencrisford> highvoltage: you forgot the gong!
[21:08] <highvoltage> *GONG*
[21:10] <Lns> BWONG...love that china style percussion!