[01:00] <cprofitt> #startmeeting
[01:00] <MootBot> Meeting started at 19:00. The chair is cprofitt.
[01:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[01:00] <cprofitt> welcome to the Ubuntu Community Learning Project Meeting
[01:00] <pleia2> thanks cprofitt :)
[01:00] <pleia2> let me fix up the Agenda real quick
[01:01] <cprofitt> k
[01:01] <pleia2> there we go :)
[01:02] <sagaci> [TOPIC]
[01:02] <cprofitt> [TOPIC] Publicty by pleia2
[01:02] <MootBot> New Topic:  Publicty by pleia2
[01:02] <pleia2> so far doctormo and I have blogged about it, which was picked up in UWN \o/
[01:03] <pleia2> have had a lot of traffic in the channel the past few days :)
[01:03] <cprofitt> that is good... what are we looking for with publicity right now
[01:03] <pleia2> so I want to make sure we're all prepared to handle this, but I want to keep the momentum going
[01:04] <pleia2> blogging and sharing stuff with loco teams will work the best, I think
[01:04] <cprofitt> yes...
[01:04] <pleia2> any other thoughts?
[01:04] <cprofitt> How are we coming on course development?
[01:05] <pleia2> that's the next topic :)
[01:05] <pleia2> we have two started
[01:05] <cprofitt> [TOPIC] Course Development
[01:05] <MootBot> New Topic:  Course Development
[01:05] <pleia2> so doctormo has been working on his sysadmin stuff
[01:05] <sagaci> which two
[01:05] <cprofitt> Cool. Do you still need help?
[01:05] <pleia2> they are all linked here; https://wiki.ubuntu.com/Learning/SystemAdminTopics
[01:05] <cprofitt> sagaci, we actually have some sample courses on the site already too
[01:06] <bodhi_zazen> sorry I am late
[01:06] <pleia2> cprofitt: we need tons of help :)
[01:06] <pleia2> more writers, more reviewers are always helpful, more experts
[01:06] <cprofitt> I agree...
[01:06] <pleia2> but doctormo's start on the sysadmin stuff is realy great
[01:06] <bodhi_zazen> I think a how to moodle would be good =)
[01:06] <cprofitt> Do we need to take doctormo's stuff and convert to Moodle
[01:07] <pleia2> nothing is in moodle yet, so that nede to be taken care of
[01:07] <cprofitt> bodhi_zazen, have you looked at the how-to I uploaded?
[01:07] <pleia2> cprofitt: yeah
[01:07] <bodhi_zazen> no, but I shall
[01:07] <pleia2> the current plan is to use bzr for course development (doctormo posted info on the list on friday)
[01:07] <pleia2> and then use moodle for course deployment
[01:08] <cprofitt> that was one of the first courses I uploaded
[01:08] <pleia2> [LINK] https://lists.ubuntu.com/archives/ubuntu-learning/2009-August/000017.html
[01:08] <MootBot> LINK received:  https://lists.ubuntu.com/archives/ubuntu-learning/2009-August/000017.html
[01:08] <cprofitt> will the bzr have moodle course files or some other format?
[01:08] <bodhi_zazen> bzr can be hard for people to use =)
[01:08] <pleia2> for now, other format
[01:08] <pleia2> bodhi_zazen: there are some good how-tos on the ubuntu wiki
[01:09] <bodhi_zazen> yea, I have helped a few people with those
[01:09] <pleia2> it's pretty straight forward after a few minutes of trying to figure it out, and you can always view the stuff via the web interface
[01:09] <pleia2> it's just committers of material who will need to know how to use it really
[01:10] <pleia2> so doctormo is on sysadmin stuff, I've been tasked with beginning the Desktop stuff - which doctormo gave me an outline for
[01:10] <pleia2> planning on having this first section done aug 31st
[01:10] <cprofitt> nice...
[01:10] <cprofitt> I think those are some big first steps...
[01:11] <cprofitt> are you guys leveraging any external materials?
[01:11] <pleia2> yeah, if you look at the sysadmin page you can see some links already exist: https://wiki.ubuntu.com/Learning/SystemAdminTopics
[01:11] <pleia2> fleshing that out more would be *great*
[01:11] <pleia2> and I think that's where we should put our focus
[01:11] <cprofitt> so the sysadmin topics...
[01:12] <pleia2> so when the course writer comes along they just need to reference those materials already linked to write the course
[01:12] <cprofitt> are each of the bullet points a course?
[01:12] <pleia2> loosely
[01:12] <pleia2> it is a work in progress
[01:12] <cprofitt> I envision the courses being able to link back out to these materials too...
[01:12] <pleia2> once you get rolling with development you might find out there isn't enough material for each course, or too much
[01:12] <bodhi_zazen> I like that outline
[01:12] <cprofitt> no need to 'cut-n-paste' content
[01:12] <cprofitt> make 'reading' assignments
[01:12] <bodhi_zazen> I should throw up a similar outline. lol
[01:12] <pleia2> yeah
[01:13] <cprofitt> then IRC, Screen, or other activities for people to apply the reading
[01:13] <pleia2> bodhi_zazen: maybe you can continue to develop this one?
[01:13] <bodhi_zazen> Yea, I can add to some of those topics
[01:13] <bodhi_zazen> I am working on an intro to Ubuntu
[01:13] <pleia2> https://wiki.ubuntu.com/Learning/UbuntuDesktopTopics is the one I'm working on now
[01:13] <bodhi_zazen> how to get an iso, etc
[01:13] <pleia2> bodhi_zazen: ok, we'll have to collaborate then :) doctormo gave me that task too
[01:14] <bodhi_zazen> the differences between desktop and alternate
[01:14] <pleia2> I'll get you the log of what we outlined for the first desktop course
[01:14] <bodhi_zazen> I am planning to pull in pages from the wiki
[01:15] <bodhi_zazen> LTS versions, how to partition, etc
[01:15] <pleia2> I'm putting my desktop work up on bzr and will be editing that wiki page, so we don't duplicate work
[01:15] <bodhi_zazen> basic stuff we all take for granted yet many windows uses have no clue
[01:15] <pleia2> yeah, sounds like we're on the same track ;)
[01:15] <cprofitt> it does... very sorry I am not able to write courses right now
[01:16] <cprofitt> I feel like a laggard
[01:16] <bodhi_zazen> pleia2: should I wait for your wiki page
[01:16] <pleia2> bodhi_zazen: can you flesh out the UbuntuDesktopTopics page with links and further outline ideas you have?
[01:16] <pleia2> no need to wait, I'm using: https://wiki.ubuntu.com/Learning/UbuntuDesktopTopics
[01:16] <pleia2> so as long as we both update it with our progress and touch base in IRC, we should be good
[01:16] <cprofitt> Nice outline plars
[01:16] <cprofitt> pleia2,
[01:16] <cprofitt> gah
[01:17] <cprofitt> sorry for the ping plars
[01:17] <bodhi_zazen> yea, I will add
[01:17] <cprofitt> I will try to add some things too...
[01:17] <cprofitt> I am slowly gaining enough wisdom that I might be able to pass it along
[01:18] <cprofitt> Where are we going to put topics like VirtualBox, UFW, etc
[01:18] <bodhi_zazen> UFW => sys admin
[01:18] <bodhi_zazen> unless we want a security section
[01:18] <cprofitt> I noticed it was not in sys admin...
[01:18] <cprofitt> so was curious
[01:18] <bodhi_zazen> VBox , well we would need a virtualization section, IMO
[01:18] <bodhi_zazen> Virtualization becomes very complex fast
[01:19] <cprofitt> so we would need a section beyond those currently on the page?
[01:19] <bodhi_zazen> NAT, bridged, sharing files, etc
[01:19] <cprofitt> or would it fit in 'use'
[01:19] <pleia2> bodhi_zazen: I just updated the wiki, but this is the log from when doctormo outlined the intro class he teaches: http://irclogs.ubuntu.com/2009/08/14/%23ubuntu-learning.html
[01:19] <pleia2> also discusses how he goes about course development
[01:19] <cprofitt> pleia2, I have to say you guys are doing a very good job
[01:19] <pleia2> cprofitt: thanks :) it's really all doctormo so far
[01:20] <cprofitt> well... doctormo deserves a huge thank you
[01:20] <cprofitt> [AGREED] doctormo deserves a big thank you
[01:20] <MootBot> AGREED received:  doctormo deserves a big thank you
[01:20] <pleia2> absolutely :)
[01:20] <pleia2> hehe
[01:20] <bodhi_zazen> +1
[01:20] <cprofitt> any other topics for you bodhi_zazen ?
[01:20] <bodhi_zazen> That is a long page
[01:21] <bodhi_zazen> No, was thinking we should clean up the team structure page ;)
[01:21] <pleia2> so I think what we want to do is encourage people to add links to the topic pages if they want to pitch in resources-wise, easy way to help out
[01:21] <bodhi_zazen> I can probably look at that
[01:21] <cprofitt> [TOPIC] Team Structure page cleanup
[01:21] <pleia2> cool
[01:21] <MootBot> New Topic:  Team Structure page cleanup
[01:22] <cprofitt> I agree bodhi_zazen I think we need to clean it up and make it be the structure not the discussion
[01:22] <cprofitt> do you have time to take that on?
[01:22] <bodhi_zazen> yes
[01:22] <cprofitt> I would appreciate that ... and I am sure everyone else will as well
[01:22] <pleia2> yeah, thanks bodhi_zazen :)
[01:22] <cprofitt> my crunch time at work is now through end of October
[01:23] <cprofitt> so my spare time is < 0
[01:23] <bodhi_zazen> I think it is a matter of merging my initial comments, with doctormo
[01:23] <bodhi_zazen> and I it is not clear what is up I will ask =)
[01:23]  * cprofitt nods
[01:23] <pleia2> sounds good!
[01:23] <cprofitt> [AGREED] bodhi_zazen to clean up structure page
[01:23] <MootBot> AGREED received:  bodhi_zazen to clean up structure page
[01:24] <cprofitt> any other topics?
[01:25] <pleia2> I'm done
[01:25] <cprofitt> bodhi_zazen, ?
[01:26] <bodhi_zazen> not I
[01:26] <cprofitt> #endmeeting
[01:26] <MootBot> Meeting finished at 19:26.
[01:26] <cprofitt> thanks for coming to the meeting everyone... we can retire to our regular bat cave for informal discussions
[01:26] <pleia2> thanks everyone!
[11:03] <popey> cc meeting?
[11:03] <popey> fridge calendar says yes, lack of people here says no
[11:17] <james_w> popey: 45 minutes
[11:18] <james_w> seems the timezone of the event in the fridge calendar is wrong
[11:19] <popey> ta
[12:02] <dholbach> Unfortunately the CC meeting is not going to happen because we can't get quorum, seems like nobody updated the Fridge. Sorry.
[14:01]  * ogra waits patiently
[14:01]  * StevenK shores patiently
[14:01]  * bjf waves
[14:05] <plars> meeting happening?
[14:05] <bjf> better happen soon or i'm back to bed
[14:07] <ogra> NCommander missing ...
[14:09] <plars> he will be joining shortly
[14:10] <ogra> twiddle twiddle ...
[14:11]  * GrueMaster is here.
[14:11] <paulliu> orz
[14:11] <dyfet> here also
[14:13] <NCommander> Ugh, morning
[14:13] <NCommander> #startmeeting
[14:13] <MootBot> Meeting started at 08:13. The chair is NCommander.
[14:13] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[14:16]  * NCommander pokes StevenK ogra lool GrueMaster plars 
[14:17] <plars> we're here
[14:17] <paulliu> hi
[14:17]  * GrueMaster pokes back.
[14:17] <NCommander> ok
[14:17] <bjf> NCommander, poke youself, lets go
[14:17] <NCommander> [topic] Action Item Review
[14:17] <MootBot> New Topic:  Action Item Review
[14:17]  * StevenK shores
[14:17] <ogra> no agenda link ?
[14:18] <NCommander> ogra, I forgot to create a new page
[14:18] <ogra> hmm, k
[14:18]  * NCommander is not on his A game this week
[14:18] <ogra> so move on
[14:18]  * GrueMaster mumbles "this week?"
[14:18] <bjf> just bag the meeting
[14:18] <NCommander> [topic] NCommander to investigate https://bugs.launchpad.net/ubuntu/+source/vnc4/+bug/338148 (co)
[14:18] <MootBot> New Topic:  NCommander to investigate https://bugs.launchpad.net/ubuntu/+source/vnc4/+bug/338148 (co)
[14:18] <NCommander> c/o
[14:19] <NCommander> [topic] GrueMaster to retest on i386 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/337809
[14:19] <MootBot> New Topic:  GrueMaster to retest on i386 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/337809
[14:19] <GrueMaster> co
[14:19] <ogra> does that even still occur ?
[14:20] <GrueMaster> Hardware to reproduce is not currently set up.
[14:20] <NCommander> [topic] Specification status
[14:20] <MootBot> New Topic:  Specification status
[14:20] <NCommander> [topic] ogra's status
[14:20] <MootBot> New Topic:  ogra's status
[14:20] <ogra> ??
[14:20] <ogra> http://people.canonical.com/~lool/mobile-status.html is supposed to be our blueprint status overview of the future, it relies on everyone having the status field in the blueprints up to date ahead of the meeting ... seems lool didnt set up a cronjob to update the page though so we might need to go through that
[14:20] <MootBot> LINK received:  http://people.canonical.com/~lool/mobile-status.html is supposed to be our blueprint status overview of the future, it relies on everyone having the status field in the blueprints up to date ahead of the meeting ... seems lool didnt set up a cronjob to update the page though so we might need to go through that
[14:20] <ogra> manually
[14:21] <ogra> i though lool showed that to you at the sprint
[14:21] <NCommander> ogra, right, but I thought we were still going to go over status individually regardless
[14:21] <NCommander> ogra, we did that last week
[14:21] <ogra> yes, last week was supposed to e the last time, but fine
[14:21] <GrueMaster> Looks like it is updating fine.
[14:21] <plars> I think the idea was just to see if there was anything currently blocking anyone
[14:21]  * ogra wonders why he took the effort to updae the statuses 
[14:22] <plars> otherwise, read the status page
[14:22] <NCommander> Ok ...
[14:22] <ogra> GrueMaster, it doesnt reflect todays status for any of mine
[14:22] <ogra> anyway
[14:22] <ogra> freescale-desktop: Waiting on manoao replacement (IS) to build functional squashfs images
[14:22] <plars> yeah, page doesn't seem to be updated :(
[14:23] <ogra> manoao is borked and cant produce uasable squashfes atm, IS is in the process to replace it, they got 10 new boards for buildds and imagebuilders
[14:23] <ogra> until its back we cant roll any images ...
[14:23] <ogra> offline-installer-gui: Trying to find a fix for the missing sched_getaffinity() syscall in qemu-arm-static to make mono packages installable in armel chroots
[14:24] <ogra> oh, and for freescale-desktop: rtg is in the process of renaming the kernel packages as discussed ....
[14:24] <ogra> all from me
[14:24] <NCommander> [topic] plars's specifications
[14:24] <MootBot> New Topic:  plars's specifications
[14:25] <plars> UNR testing: added some more testcases to checkbox
[14:25] <plars> going to see about getting them integrated into daily testing in the lab
[14:25] <plars> cr3 said he needs to make some minor changes but thinks they can do it
[14:25] <plars> ARM testing, not much progress, need builds, and hardware
[14:26] <plars> screen size/resolution testsuite: good progress this week
[14:26] <plars> added support for editboxes and comboboxes and several new tests
[14:26] <plars> found bugs already with it!
[14:26] <plars> done
[14:26] <NCommander> [topic] dyfet's specifications
[14:26] <MootBot> New Topic:  dyfet's specifications
[14:27] <dyfet> Well...the lxde seed was completed, and in doing so provoked a minor war over what really should be in the seed in the public mailing list :)
[14:28] <ogra> did it settle ?
[14:28] <dyfet> Kinda...or should I say, more correctly, a "vigorous discussion"? ;)
[14:29] <dyfet> Nobody has offered any actual changes...
[14:29] <NCommander> [topic] StevenK's status
[14:29] <MootBot> New Topic:  StevenK's status
[14:29] <ogra> and his specs :)
[14:30] <NCommander> ^spec
[14:30] <StevenK> Wubi has had some changes commited that might make it work, I'll be testing tomorrow
[14:32] <NCommander> Er, is lool still on holiday before I ask his status?
[14:32] <ogra> yes until tomorrow
[14:32] <ogra> look at your team cal
[14:32] <NCommander> I don't have it up at the moment
[14:32] <NCommander> Thanks
[14:32] <NCommander> [topic] NCommander's specs
[14:32] <MootBot> New Topic:  NCommander's specs
[14:33] <NCommander> mobile-karmic-marvell-desktop: Uh, made quite a bit of progress
[14:33] <ogra> the kernel team is waiting for a design doc
[14:33] <ogra> they need to know what deps the packages need for uboot
[14:33] <NCommander> Its going to be standard flash-kernel
[14:33] <ogra> no, surely not
[14:33] <NCommander> Ugh, I didn't know they were dep-wait on that
[14:34] <ogra> kernel packages are sitting in NEW since 24h
[14:34] <ogra> flash-kernel is used if you flash mtd (or in special cases SD) devices
[14:35] <ogra> does your design require the kernel or initramfs to sit in mtd ?
[14:35] <ogra> (or in a special SD partition thats not accessible)
[14:35] <NCommander> ogra, its been used to create and install u-boot packages before. I can dump what I was going to put there into the postinst
[14:35] <ogra> i dont think thats proper
[14:36] <ogra> the kernel can build uboot bompliant uImage itself in the package
[14:36] <ogra> *compliant
[14:36] <ogra> no need for anything special
[14:36] <NCommander> I can change gears then, and provide them w/ a postinst, thats pretty easy.
[14:36] <ogra> please document your design somewhere
[14:36] <NCommander> ogra, I did, its on the internal wiki
[14:36] <ogra> *before* making up any postinst stuff
[14:36] <ogra> *in your spec*
[14:37] <ogra> thats why you have a spec
[14:37] <NCommander> I'll fix that after the end of thi smeeting
[14:37] <ogra> https://wiki.ubuntu.com/Specs/KarmicMarvellDesktop is the spec
[14:37] <NCommander> Anyway, I finished my changed to d-cd yesterday and over the weekend.
[14:38] <ogra> please put a detailed design description how the images are laid out in there
[14:38] <ogra> so others can look it up
[14:38] <NCommander> ogra, I wrote it, I just put it in the wrong place, I'll move it
[14:38] <ogra> ok
[14:38] <ogra> just that the kernel team knows whats needed for the packaging
[14:39] <ogra> and others know what to expect
[14:39] <NCommander> I'll have my bazaar branches posted later today I hope with my changes, and the boot info moved to the public wiki
[14:39] <ogra> will you shepherd the kernel packages through NEW once the naming is correct ?
[14:39] <NCommander> ogra, er, I'm not an archive admin ...
[14:40] <ogra> shepherd doesnt mean you review them yourself
[14:40]  * NCommander is unfamiliar with the term
[14:40] <ogra> have a look at the naming, poke an archive admin
[14:40]  * ogra sighs
[14:40] <ogra> (only poke an admin if the naming is fine indeed)
[14:41]  * NCommander nods
[14:41] <ogra> and make sure they go through binary new too after they built
[14:41] <ogra> and test them
[14:41] <ogra> etc
[14:41] <NCommander> Alright, no progress on mobile-arm-softbootloader
[14:42] <NCommander> [topic] GrueMaster's specs
[14:42] <MootBot> New Topic:  GrueMaster's specs
[14:42] <NCommander> ^status
[14:42] <GrueMaster> LSB Testing continued as normal.  No new issues.
[14:42] <GrueMaster> Currently testing Ubuntu Moblin edition (Ubuntu Moblin Remix) for Moblin compliance.  Will need to test against Moblin directly to establish a baseline.
[14:42] <GrueMaster> mobile-unr-karmic-applications:
[14:42] <GrueMaster> Work needs to be done by StevenK.  Empathy is seeded now so I updated the status.  Still need gwibber changes and size reduction changes.
[14:42] <GrueMaster> That is all.
[14:42] <StevenK> gwibber is done
[14:42] <NCommander> [topic] paulliu's specs
[14:42] <MootBot> New Topic:  paulliu's specs
[14:42] <StevenK> Size reduction, I'm waiting on you.
[14:43] <paulliu> resolution: slow progress. But the rest things are easy. I'm putting my efforts to moblin things.
[14:43] <paulliu> moblin: drafting. Need someone review the spec.
[14:44] <paulliu> Also I need sync/merging from Debian for 2 packages. librest and webkit.
[14:44] <GrueMaster> StevenK: Yes, I know.  Will have a list by end of the week.
[14:44] <paulliu> That's all.
[14:45] <NCommander> Did I get everyone?
[14:46] <NCommander> [topic] Any other business
[14:46] <MootBot> New Topic:  Any other business
[14:46] <ogra> as i mentioned before yesterday 10 new armel buildds arrived
[14:46] <ogra> davidm carried them by hand to the DC :)
[14:47] <NCommander> \o/
[14:47] <GrueMaster> cool.  Does that mean we'll have an image soon?
[14:47] <ogra> they will have to be set up by IS
[14:47] <ogra> not sure what the status on that is
[14:47] <ogra> i know lool worked on the images for them so they might wait for him to return from holiday before starting to get his instructions
[14:48] <ogra> given that they will likely use USB disks they will be slower than the current ones though
[14:48] <ogra> which means we need to be even more cautious to not fall behind
[14:49] <ogra> but that should finally enable us to build armv6+vfp
[14:49] <ogra> (which in turn will trigger a full archive rebuild)
[14:49] <ogra> and likely show new build issues in some packages
[14:50] <ogra> so please help out on the FTBFS list if you can :)
[14:50] <ogra> (after the machines are in place)
[14:50] <ogra> thats it from me
[14:51] <NCommander> ogra, writeup of my current boot proposal moved to the external wiki
[14:51] <NCommander> anyone got anything else?
[14:52] <NCommander> guess not
[14:52] <NCommander> #endmeeting
[14:52] <MootBot> Meeting finished at 08:52.
[14:52]  * GrueMaster goes back to bed for a few hours.
[15:59] <kirkland> o/
[15:59] <Sam-I-Am> mornings
[15:59] <Daviey> hey \o
[15:59] <jmdault> good morning
[16:00] <Daviey> (afternoon) :)
[16:00] <jmdault> good timezone ;-)
[16:00] <ttx> o/
[16:00]  * mathiaz waves
[16:00] <foolano> o/
[16:00] <mathiaz> let's get the server team meeting started
[16:00] <Daviey> hurray
[16:01] <mathiaz> #startmeeting
[16:01] <MootBot> Meeting started at 10:01. The chair is mathiaz.
[16:01] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[16:01] <mathiaz> Today's agenda: https://wiki.ubuntu.com/ServerTeam/Meeting
[16:01] <mathiaz> last week minutes: https://wiki.ubuntu.com/MeetingLogs/Server/20090811
[16:02] <mathiaz> [TOPIC] Asterisk
[16:02] <MootBot> New Topic:  Asterisk
[16:02] <mathiaz> what's the state of pwlib?
[16:02] <nijaba> o/
[16:02] <mathiaz> it seems that pwlib was the last blocker to get asterisk 1.6 in ubuntu
[16:02] <Daviey> mathiaz: no change from me here, since last meeting.
[16:02] <jmdault> pwlib is ok
[16:02] <jmdault> https://launchpad.net/~jmdault/+archive/ppa
[16:03] <Daviey> jmdault: so you rebuilt pwlib aswell?
[16:03] <Daviey> as in, the one in the archive is not good?
[16:03] <jmdault> Daviey: the one in the archive is missing the -dev
[16:03] <Daviey> isn't it -develop in the archive?
[16:04] <mathiaz> jmdault: which package from the ppa should be pushed to karmic?
[16:04] <Daviey> mathiaz: the pwlib :)
[16:04] <jmdault> mathiaz: all packages =)
[16:04] <Daviey> jmdault: http://packages.ubuntu.com/karmic/libpt-1.10.10-develop
[16:05] <jmdault> Daviey: it didn't seem to match the BuildRequires
[16:05] <Daviey> true.
[16:05] <mathiaz> jmdault: ok - next step is to ask for sponsorship then
[16:05] <jmdault> Debian changed the way the pwlib/libpt package is done
[16:05] <mathiaz> jmdault: I'd suggest to prioritize the package as this is a long list
[16:05] <jmdault> mathiaz: I have 2 core devs at the office
[16:05] <jmdault> =)
[16:06] <mathiaz> jmdault: are all the packages required?
[16:06] <Daviey> jmdault: it's my understanding that they want to move as much as possible away from pwlib.
[16:06] <mathiaz> jmdault: core-dev -> great.
[16:06] <jmdault> mathiaz: the most important packages are pwlib and openh323
[16:06] <mathiaz> jmdault: so you know how the process works
[16:06] <jmdault> mathiaz: as they're the building blocks
[16:06] <mathiaz> jmdault: ok - so I'd suggest to start by these
[16:06] <zul> hi
[16:06] <mathiaz> jmdault: and move down the list by priority order
[16:07] <Daviey> jmdault: superb.
[16:07] <mathiaz> anything else to add on this topic?
[16:07] <Daviey> pwlib -> openh323 -> dahdi* -> asterisk* IMP
[16:07] <Daviey> IMO*
[16:07] <jmdault> Daviey: yes
[16:07] <jmdault> mathiaz: there's one thing to add
[16:08] <jmdault> mathiaz: Asterisk 1.6 does not support fax as it used to do
[16:08] <mathiaz> [ACTION] jmdault to ask sponsorship for pwlib -> openh323 -> dahdi* -> asterisk* packages
[16:08] <MootBot> ACTION received:  jmdault to ask sponsorship for pwlib -> openh323 -> dahdi* -> asterisk* packages
[16:08] <jmdault>  asterisk-app-fax will need to be removed from the repo
[16:08] <jmdault> it's been deprecated since 2007
[16:08] <mathiaz> jmdault: are there any plans to replace it upstream?
[16:09] <Daviey> openh323 rebuild will require rebuild of other packages, inc Ekiga i believe.. but that is the core devs problem not the server team :)
[16:09] <jmdault> mathiaz: Asterisk 1.6 has a bundled fax send and receive function
[16:09] <mathiaz> jmdault: deprecated -> replaced by something else?
[16:09] <Daviey> Digium have a non-free fax app now.. don't they
[16:09] <Daviey> ?
[16:09] <jmdault> mathiaz: however, the trend is to use iaxmodem + hylafax
[16:09] <Daviey> ^^ /me does this.. not the cleanest..
[16:10] <jmdault> also, the asterisk-addons package is not in Debian right now
[16:10] <jmdault> only in svn
[16:10] <jmdault> so I took the version from svn
[16:10] <mathiaz> jmdault: so there is a functional equivalent to asterisk-app-fax?
[16:10] <jmdault> mathiaz: yes, asterisk 1.6 provides its own app_fax
[16:11] <mathiaz> jmdault: ok - asterisk-app-fax can be dropped from the archive as there is functional replacement available in karmic
[16:11] <mathiaz> ok - anything else to add on this topic?
[16:11] <jmdault> nope
[16:11] <mathiaz> great - let's move on then
[16:12] <mathiaz> [TOPIC] Update Ebox to 1.3
[16:12] <MootBot> New Topic:  Update Ebox to 1.3
[16:12] <mathiaz> what's the state of ebox 1.3?
[16:12] <mathiaz> foolano: zul: ^^
[16:12] <foolano> packages are already in the PPA, and I have also attached the diff to the lp bugs
[16:12] <zul> its on my plate for this afternoon
[16:13] <foolano> :)
[16:13] <mathiaz> ok - seems like everything is on track.
[16:13] <foolano> btw, there's a new dependency that i uploaded to revu and to debian
[16:13] <mathiaz> Feature Freeze is next week - so plan accordingly
[16:13] <foolano> it made it to the debian archive before, so i dunno what i should do with it
[16:13] <mathiaz> foolano: I've read your email to ubuntu-server about slapd and will reply to it later today
[16:14] <zul> foolano: just sync it then
[16:14] <foolano> mathiaz: thx :)
[16:14] <mathiaz> foolano: if the package is already in the debian archive you can ask for a sync
[16:14] <foolano> ok :)
[16:14] <mathiaz> foolano: but it needs to get passed the NEW queue
[16:14] <mathiaz> foolano: the Debian NEW queue
[16:14] <foolano> mathiaz: it has already passed the NEW queue
[16:15] <mathiaz> foolano: ok - then a Sync request is the next step
[16:15] <foolano> cool
[16:15] <mathiaz> [ACTION] zul to review ebox 1.3 packages
[16:15] <MootBot> ACTION received:  zul to review ebox 1.3 packages
[16:15] <mathiaz> anything else to add on this topic?
[16:15] <foolano> nope
[16:15] <mathiaz> great - let's move on
[16:16] <mathiaz> that's all from last week minutes
[16:16] <mathiaz> anything else to add wrt last week meeting?
[16:17] <Daviey> hmm
[16:17] <Daviey> ubuntu-server-tips
[16:18] <Daviey> mathiaz: may i?
[16:18] <mathiaz> Daviey: I'll get to this one later
[16:18] <Daviey> ok.
[16:18] <mathiaz> ok - let's move on.
[16:18] <mathiaz> [TOPIC] SRU weekly review
[16:18] <MootBot> New Topic:  SRU weekly review
[16:18] <ttx> yay
[16:18] <zul> yay...
[16:19] <mathiaz> As announced in the agenda I've put up one more list online
[16:19] <Daviey> \o/
[16:19]  * zul suggests #382136
[16:19] <mathiaz> http://people.canonical.com/~mathiaz/fix-released-bugs.ubuntu-server.2009-08-17.html
[16:19] <MootBot> LINK received:  http://people.canonical.com/~mathiaz/fix-released-bugs.ubuntu-server.2009-08-17.html
[16:19] <mathiaz> these bugs have been fixed last week
[16:19] <mathiaz> which are SRU worthy?
[16:19] <mathiaz> which *one* are SRU worthy?
[16:20] <zul> bug #382136 the samba one
[16:20]  * ttx suggests to remove open-iscsi from the "server packages" list, since Foundations takes care of it
[16:20] <mathiaz> ttx: ok.
[16:20] <Daviey> ttx: although isscsi is IMO a "server" thing.. so it would be good for us to help, prod and poke where we can, surely?
[16:20] <ttx> ack on 382136, it's already accepted
[16:23] <ttx> Daviey: I'm not sure we are in the right position to make decisions for that package, like for example SRU acceptations
[16:23] <mathiaz> ttx: ubuntu-server removed from the open-iscsi bug contact
[16:23] <Daviey> ttx: sure.
[16:23] <ttx> that doesn't prevent us from helping triaging there :)
[16:23] <mathiaz> ttx: and thus open-iscsi won't show up on the lists anymore
[16:24] <mathiaz> how about bug 57974?
[16:25] <mathiaz> zul: how did that bug got fix released?
[16:25] <Daviey> Does   Bug #358723:
[16:25] <Daviey> This report is public edit
[16:25] <Daviey> need an SRU?
[16:26] <zul> mathias: looking at the mailing list archives and the bug is 3 years old as well
[16:26] <ttx> Daviey: sounds like an easy workaround, and the bug is quite specific
[16:26] <mathiaz> Daviey: would it fit any of the criteria of https://wiki.ubuntu.com/StableReleaseUpdates?
[16:26] <mathiaz> zul: upstream mailing list archive?
[16:27] <zul> mathiaz: correct
[16:27] <Daviey> mathiaz: probably not.
[16:27] <mathiaz> zul: and having a bug 3 years old doesn't mean that it must be fixed
[16:27] <ttx> heh
[16:27] <mathiaz> zul: I'd suggest to try to add a reason why the bug is fixed released
[16:28] <zul> mathiaz: tracking down the fix might be a bit harder as well
[16:28] <mathiaz> ok - anything else from the list?
[16:28] <zul> mathiaz: sure
[16:28] <ttx> I'm not sure bug 254687 should be fix-released
[16:28] <ttx> "What i did is copy and paste users twice in user_list file and it worked" sounds like there is still a bug there
[16:29] <ttx> A "low" one, granted, with an easy workaround...
[16:29] <ttx> or do I miss something ?
[16:29]  * mathiaz agrees
[16:30] <ttx> zul: if you agree, reopen that one.
[16:30] <zul> k
[16:30] <ttx> mathiaz: nothing else in that list I guess
[16:30] <mathiaz> ok - let's move on then
[16:30] <mathiaz> to the next list
[16:30] <mathiaz> http://people.canonical.com/~mathiaz/nominated-bugs.ubuntu-server.2009-08-17.html
[16:30] <MootBot> LINK received:  http://people.canonical.com/~mathiaz/nominated-bugs.ubuntu-server.2009-08-17.html
[16:31] <mathiaz> ^^ these are the bugs that are nominated for each release
[16:31] <mathiaz> we should either accept or decline every one of them
[16:31] <mathiaz> which one should be accepted?
[16:31] <ttx> I would obviously accept bug 379748, I nominated it :)
[16:32] <ttx> I'd also accept bug 272060
[16:32] <Daviey> well the ones marked with CVE are possibly worthy..
[16:32] <mathiaz> ttx: accepted
[16:33] <ttx> Daviey: they are uisually already fixed
[16:33] <ttx> just need some cleanups
[16:33] <ttx> I'd accept bug 253743
[16:34] <ttx> that's all for me
[16:34] <mathiaz> ttx: hm - how would it fit under the SRU criteria?
[16:35] <mathiaz> ttx: it's a new feature AFAICT
[16:35] <Daviey> I do wonder if 253743 is worth fixing for hardy.. Surely there is a worthy work-around if that bug is a year old?
[16:35] <ttx> mathiaz: agreed. Decline it.
[16:35] <MsMaco> i would assume the workaround is ps
[16:36] <mathiaz> ok - anything else worth accepting on the nominated list?
[16:36] <mathiaz> if not, all the remaining bugs should be marked declined
[16:36] <mathiaz> if not, all the remaining bugs should be declined
[16:36] <Daviey> 282876 ?
[16:37] <mathiaz> bug 282876
[16:37] <ttx> I will go through the list and accept/fix-released the ones that happen to be already fixed
[16:37] <zul> the via padlock ones should probably be denied
[16:37] <mathiaz> [ACTION] ttx to go throught the list of nominated bugs and decline them
[16:37] <MootBot> ACTION received:  ttx to go throught the list of nominated bugs and decline them
[16:37] <Sam-I-Am> how do segfault-type bugs get handled?  i have one that belongs to dhcp3, but isn't being worked on...
[16:38] <ttx> mathiaz: I'll leave the dubious ones for more fun next week.
[16:38] <mathiaz> zul: done
[16:38] <mdz> Sam-I-Am, they generally need to be checked for private information and then made public before most developers can see them
[16:38] <nijaba> Sam-I-Am: on a server package?  bug # please?
[16:38] <Sam-I-Am> 358589
[16:38] <Daviey> bug 358589
[16:39] <mdz> oh, it isn't a crash report
[16:39] <mathiaz> allright - that's all for the Weekly SRU review
[16:39] <mathiaz> anything else to add?
[16:39] <mathiaz> next week we'll add one more list to review
[16:40] <mathiaz> which the list of accepted bugs and see how things are working there
[16:40] <Sam-I-Am> mdz: should that kind of bug become a crash report?
[16:40] <mathiaz> FYI the whole SRU process is described in the Knowledge base: https://wiki.ubuntu.com/ServerTeam/KnowledgeBase#SRU%20resources
[16:41] <Sam-I-Am> thx
[16:41] <mathiaz> anything else to add on this topic?
[16:42] <mathiaz> let's move on then
[16:42] <mathiaz> [TOPIC] libmysqlclient-dev transition
[16:42] <MootBot> New Topic:  libmysqlclient-dev transition
[16:42] <mathiaz> soren: ^^
[16:42] <soren> Yes.
[16:43] <mathiaz> well - I've uploaded a new version of MySQL 5.1 to karmic
[16:43] <mathiaz> and it was promoted to main yesterday
[16:43] <mathiaz> there are a bunch of packages that need to have their dependencies updated in main: libmysqclient15-dev -> libmysqlclient-dev
[16:44] <soren> Right. As a result, packages in main that depend on libmysqlclien15-dev will fail to build, so they need to be updated. There's ~10 packages affected by this, afaics.
[16:44] <mathiaz> soren: yes - I've already uploaded a third of them
[16:44] <soren> mathiaz: Ah, yes, so I see :)
[16:44] <mathiaz> A bunch of them are kde/qt related - I'll ask Riddell about it
[16:44] <mathiaz> and I'll do the rest
[16:45] <mathiaz> soren: anything else to add?
[16:45] <soren> Not really. I was just thinking maybe someone else wanted to do it.
[16:45] <soren> It's not very sexy, but it's always rewarding to see a package with your name on it get uploaded :)
[16:46] <zul> what about the packages in universe i forget what about those?
[16:46] <mathiaz> zul: MySQL 5.0 is still universe for karmic
[16:46] <mathiaz> getting rid of 5.0 is a goal for the next release cycle
[16:46] <zul> k
[16:47] <mathiaz> debian is also transitioning from 5.0 to 5.1
[16:47] <mathiaz> so we should get all the benefits in the next cycle
[16:47] <zul> and the packages in universe that have the dependency on libmsqlclient-dev15?
[16:47] <soren> zul: It's still in universe, so they're fine.
[16:47] <zul> gotcha
[16:48] <mathiaz> zul: and the dependency should be updated in Debian
[16:48] <mathiaz> zul: while the transition to 5.1 is going on there.
[16:48] <mathiaz> anything other questions/comments on this topic?
[16:48] <zul> nope
[16:49] <mathiaz> ok - let's move on.
[16:49] <mathiaz> [TOPIC] Server tips : implementation
[16:49] <MootBot> New Topic:  Server tips : implementation
[16:49] <mathiaz> Daviey: ^^?
[16:49] <Daviey> ah ha!
[16:49] <Daviey> Okay, i wrote an update on the ML.. did everyone catch that?
[16:50] <nijaba> yep
[16:50] <Daviey> great.. So i wanted to quickly talk about process.. I'm not sure it's a good long term plan for just me to approve and commit tips
[16:50] <Daviey> We currently have 32 tips committed.. and translations are doing much better.
[16:50] <nijaba> one remark: I think that some of the tips you approve go well beyond 160 chararcters
[16:51] <Daviey> nijaba: yeah.. i noted this.. it's not a *huge* problem in itself, as if we want to limit to 160 chars, we can poll fortune to only return short (160 ones)
[16:51] <Daviey> 160 wasn't an random figure :)
[16:51] <Daviey> a*
[16:52] <mathiaz> Daviey: IIRC one the proposal was to do a review before an upload
[16:52] <nijaba> Daviey: agreed.  Other than that, I have reviewed while translating, and all seem to abide to the rules on https://wiki.ubuntu.com/server-tips
[16:52] <Daviey> mathiaz: That is great, but how.. Does the weekly meeting really have time to cover any tips from that week?
[16:52] <mathiaz> Daviey: so you can commit new tips and we can review all of them on a monthly basis before preparing an upload
[16:52] <Daviey> makes sense.
[16:53] <mathiaz> Daviey: sending a monthly email to the mailing list seems a good option
[16:53] <Daviey> Would anybody else like to help confirm / committing them?
[16:53] <nijaba> Daviey: I volunteer
[16:53] <Daviey> hurray o/
[16:53] <mathiaz> great - anything else to add on this topic?
[16:53] <Daviey> One thing.
[16:54] <Daviey> I was waiting on better translations and more tips before requesting inclusion in archives
[16:54] <Daviey> How many tips should the target be, before doing this?
[16:54] <mathiaz> Daviey: well - FeatureFreeze is next week
[16:54] <nijaba> Daviey: I don't think volume should count, mostly quality
[16:54] <Daviey> so should we get it in, then bump with more tips?
[16:54] <mathiaz> Daviey: so that's the timeline for Karmic
[16:55] <nijaba> Daviey: so please, go ahead
[16:55] <Daviey> wilco.
[16:55] <Daviey> erm, is the plan still to have it as part of update-motd?
[16:55] <Daviey> In which case, we are looking at main, right?
[16:55] <mathiaz> Daviey: first universe
[16:56] <nijaba> Daviey: yep, kirkland was supposed to give us a one line to drop in update-motd.d
[16:56] <kirkland> nijaba: sure, you want that now?
[16:56] <Daviey> nijaba: well the script to retrieve a locale tip seems to work. so should be easy for kirkland.
[16:56] <mathiaz> we're running out of time
[16:56] <nijaba> kirkland: yep, that would be nice so that Daviey can include it in the package
[16:56] <mathiaz> so I'd suggest to differ this discussion to #ubuntu-server
[16:56] <kirkland> nijaba: i'll get with Daviey later today
[16:56] <mathiaz> anything else to add?
[16:56] <Daviey> ok.
[16:56] <nijaba> kirkland: thanks
[16:58] <mathiaz> anything else to add?
[16:58] <Daviey> EOF
[16:58] <nealmcb> :)
[16:58] <nijaba> Ctrl-D
[16:58] <mathiaz> [TOPIC] Agree on next meeting date and time
[16:58] <MootBot> New Topic:  Agree on next meeting date and time
[16:59] <mathiaz> next week - same place, same time?
[16:59] <Daviey> sounds good.
[16:59] <ttx> yes
[16:59] <mathiaz> And don't forget that Feature Freeze is around the corner
[16:59] <nijaba> I'll be off next week, but I'll read the meeting notes :)
[16:59] <jmdault> mathiaz: sounds good
[16:59] <Sam-I-Am> mathiaz: one thing... did you get my email about some patches to the build mechanism for openldap?
[17:00] <Sam-I-Am> mathiaz: not even sure it made it to the list
[17:00] <mathiaz> Sam-I-Am: I don't think so. Let's take this to #ubuntu-server
[17:00] <Sam-I-Am> sure
[17:00] <mathiaz> see you all next week, same place, same time.
[17:00] <mathiaz> #endmeeting
[17:00] <MootBot> Meeting finished at 11:00.
[17:00] <Daviey> thanks mathiaz
[17:01] <nijaba> thank you mathiaz
[17:31] <dhillon-v101> hi everyone, I thought this was supposed to be the kernel team meeting
[17:32] <ogra> in 30min
[17:32] <iulian> dhillon-v101: 17:00 UTC.
[17:33] <iulian> So yeah, in 30 minutes.
[17:33] <dhillon-v101> iulian: I am really sorry to bother you guys
[17:34] <iulian> No worries.
[17:36] <dhillon-v101> iulian: You have a unique name :)
[17:37] <iulian> Of course.
[17:38] <dhillon-v101> iulian: where are you from? I am from India
[17:38] <iulian> I'm currently living in Romania.
[17:39] <dhillon-v101> iulian: Cool that's a nice place
[17:55] <bjf> smb, that "vacation" feeling didn't last long did it?
[17:56] <smb> bjf, Hehe, it seldomly does, does it? :)
[17:59] <cking> here we go
[18:00]  * smb activates attention circuits
[18:00]  * apw fades in
[18:00] <cking> Roll Call
[18:00] <apw> o/
[18:00]  * rtg waves
[18:00]  * lieb waves
[18:00]  * ogasawara waves
[18:00]  * pgraner is here
[18:00]  * sconklin here!
[18:00] <dhillon-v101> hi everyone
[18:00]  * smb \o
[18:00]  * bjf is ready
[18:00] <cking> OK...
[18:00]  * jjohansen1 waves
[18:00] <cking> #startmeeting
[18:00] <MootBot> Meeting started at 12:00. The chair is cking.
[18:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[18:00] <cking> [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting
[18:00] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/Meeting
[18:00] <cking> [TOPIC] Open Action Items: (apw) check up on drbd status in dkms package and kernel
[18:00] <MootBot> New Topic:  Open Action Items: (apw) check up on drbd status in dkms package and kernel
[18:00] <apw> dammit thats still outstanding
[18:01] <dhillon-v101> topic
[18:01] <cking> any progress?
[18:01] <dhillon-v101> I am a bit new to this meeting  thing can you guys help
[18:01] <cking> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Karmic
[18:01] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Karmic
[18:01] <cking> [TOPIC] Karmic Release Status: Bugs (Release Meeting Bugs / RC Milestoned Bugs / Release Targeted Bugs)
[18:01] <MootBot> New Topic:  Karmic Release Status: Bugs (Release Meeting Bugs / RC Milestoned Bugs / Release Targeted Bugs)
[18:01] <apw> cking, no none, i've added it to my todo for tomomrrow ...
[18:01] <bjf> dhillon-v101, sit back and watch a bit, you'll get the hang of it
[18:02] <ogasawara> Release Meeting Bugs (2 bugs) - https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Karmic
[18:02] <ogasawara> RC Milestoned Bugs Alpha 4 (0 bugs) - https://bugs.launchpad.net/ubuntu/karmic/+bugs?field.milestone=12712
[18:02] <ogasawara> Release Targeted Bugs (10 bugs) - https://bugs.edge.launchpad.net/ubuntu/karmic/+source/linux
[18:02] <dhillon-v101> bjf: alright thanks
[18:02] <jjohansen1> dhillon-v101: also look at the first link its contains the agenda
[18:02] <cking> thanks ogasawara
[18:02] <cking> [TOPIC] Karmic Release Status: Milestoned Features
[18:02] <MootBot> New Topic:  Karmic Release Status: Milestoned Features
[18:02] <ogasawara> Milestoned Features - https://launchpad.net/ubuntu/+milestone/karmic-alpha-4
[18:02] <sconklin> dhillon-v101: cking is moderating, and using the mootbot to keep meeting notes
[18:03] <dhillon-v101> sconklin: alright thanks
[18:03] <cking> [TOPIC] Blueprints: kernel-karmic-hwdb-workshop (ogasawara)
[18:03] <MootBot> New Topic:  Blueprints: kernel-karmic-hwdb-workshop (ogasawara)
[18:03] <ogasawara> cking: nothing new to add for this
[18:03] <cking> TOPIC] Blueprints: kernel-karmic-kms (apw)
[18:03] <dhillon-v101> cking: hi how are you
[18:03] <apw> nothing much going on there.  just more testing
[18:03] <cking> anything notworthy?
[18:04] <apw> nothing significant this week no
[18:04] <cking> [TOPIC] Blueprints: kernel-karmic-new-kernel-on-lts (rtg)
[18:04] <MootBot> New Topic:  Blueprints: kernel-karmic-new-kernel-on-lts (rtg)
[18:04] <rtg> I've done a bit more on it since last week. I think I'll rework the build before uploading, but I've tested it
[18:04] <rtg> on a number of server boxes. Its seems as ready as it ever will, though I do need to get the AppArmor user space
[18:04] <rtg> application updated.
[18:04] <rtg> Talked to kees about AA, he says its SRU'able.
[18:04] <pgraner> rtg: this is likely going to be a big one for 10.04
[18:04] <apw> rtg will we just update AA wholesale ?
[18:04] <apw> or somehow do it as a backport only?
[18:05] <rtg> pgraner, yep
[18:05] <pgraner> rtg: we need to meet and discuss the supportability
[18:05] <rtg> I've been exploring the issues with other teams
[18:05] <amitk> rtg: what about other userspace bits?
[18:05] <rtg> seems that AA is the biggest support problem
[18:05] <pgraner> rtg: good to hear, we can add that to the agend for the Oct sprint
[18:05] <cking> ok.. moving on then
[18:05] <rtg> if you ignore desktop issues, then all seems to be fine.
[18:05]  * pgraner kicks jjohansen1 
[18:06] <jjohansen1> amitk: it is the userspace bits that need updating
[18:06] <amitk> akc
[18:06] <amitk> *ack
[18:06] <cking> [TOPIC] Blueprints: kernel-karmic-review-of-non-upstreamed-code (smb)
[18:06] <MootBot> New Topic:  Blueprints: kernel-karmic-review-of-non-upstreamed-code (smb)
[18:06] <smb> I believe I updated the page on the sprint but since then no change. But nearly done.
[18:06] <cking> ok, see what happens for next week
[18:07] <cking> [TOPIC] Blueprints: kernel-karmic-android (coolony)
[18:07] <MootBot> New Topic:  Blueprints: kernel-karmic-android (coolony)
[18:07] <apw> that is mostly pending our decision to rip everything which is commented out
[18:07] <cking> anyone able to input for coolony?
[18:07] <apw> i think this one is still on hold pending resource
[18:07] <cking> ok
[18:07] <cking> [TOPIC] Blueprints: kernel-karmic-suspend-resume  (manjo)
[18:07] <MootBot> New Topic:  Blueprints: kernel-karmic-suspend-resume  (manjo)
[18:07] <pgraner> cking: we can drop it, I've deferred
[18:08] <cking> manjo sends apologies, he's travelling today
[18:08]  * pgraner can't type fast enough
[18:08] <cking> I will slooow down. Sorry
[18:08] <pgraner> cking: back up for a sec
[18:08] <cking> back to where?
[18:08] <pgraner> cking: android is off the table for 9.10, since we have turned  on Bender that should work for anyone wanting to try it
[18:08] <pgraner> cking: with our kernel, much like OEM did for the demo
[18:09] <rtg> pgraner, isn't Bender a cartoon character?
[18:09] <apw> binder?
[18:09] <pgraner> rtg: typo
[18:09] <rtg> ah
[18:09] <smb> rtg, Futurama
[18:09] <pgraner> rtg: trying to type to fast
[18:09] <rtg> adult swim :)
[18:09] <cking> *sigh*
[18:09] <cking> [TOPIC] Other Release Tasks: AppArmour (jjohansen)
[18:09] <MootBot> New Topic:  Other Release Tasks: AppArmour (jjohansen)
[18:09] <jjohansen1> lp #359338 - ecryptfs, is wip part 1 should be done today
[18:10] <apw> iiuc that means we have a viable automatic work around once we have part 1
[18:10] <jjohansen1> I have also fixed several other bugs that security team have brought up
[18:10] <cking> ok - so parts 2..N still coming along for 359338
[18:10] <jjohansen1> with part 1 the security team can update the policy enough to make it work
[18:10] <jjohansen1> I can't see part2 or 3 hitting in Karmic
[18:11] <apw> so that takes the sting out of the bug for both ecryptfs and aufs use?
[18:11] <jjohansen1> but part1 is sufficeint for current policy
[18:11] <jjohansen1> yes
[18:11] <apw> good news, thankis
[18:11] <cking> great. moving on then
[18:11] <jjohansen1> it works because of how we mount them
[18:11] <cking> [TOPIC] Other Release Tasks: ARM-Freescale (amitk, bjf)
[18:11] <MootBot> New Topic:  Other Release Tasks: ARM-Freescale (amitk, bjf)
[18:11] <rtg> I'm working on rebasing fsl-imx51 against 2.6.31-rc6 along with new debian build infrastructure.
[18:11] <bjf> I've reapplied all FSL patches (including the latest ER9-SP) on Jaunty and issued a pull reques
[18:11] <bjf> t.
[18:11] <bjf> Also applied the latest 9 patches from the Marvell tree to the Karmic tree and issued a pull request.
[18:11] <bjf> Will be reviewing the dove config next.
[18:12] <amitk> I've been mostly testing the initial imx51 builds and fixing the ethernet driver for the babbage board
[18:12] <cking> anything else?
[18:12] <amitk> Working through the specs of the ethernet chip now
[18:12] <amitk> over
[18:12] <cking> [TOPIC] Other Release Tasks: Karmic General Status (rtg, apw)
[18:12] <MootBot> New Topic:  Other Release Tasks: Karmic General Status (rtg, apw)
[18:13]  * cking prods rtg, apw..
[18:13] <rtg> apw, I've been focused on arm this week. What have you been doing for Karmic?
[18:13] <apw> most of the work going on here is on regression-potential's we have on our lists
[18:14] <apw> mostly confirming they are fixed by the updates to -rc6
[18:14] <rtg> cking,  uploaded -rc6 rebase
[18:14] <apw> most of the developement effort is in support of the new arm branches in the main tree
[18:15] <cking> painful progress, but required
[18:15] <apw> as one would hope the rate of change both in our side, and in linus' tree is slowing
[18:15] <cking> ok, anymore?
[18:15] <apw> nothign herre
[18:15] <cking> [TOPIC] Security & bugfix kernels - Jaunty/Intrepid/Hardy/Others (smb)
[18:15] <MootBot> New Topic:  Security & bugfix kernels - Jaunty/Intrepid/Hardy/Others (smb)
[18:15] <smb> * Dapper:   2.6.15-54.78 (security, new security release in progress)
[18:15] <smb> * Hardy:    2.6.24-24.57 (security, new security release in progress)
[18:15] <smb>             2.6.24-24.58 (proposed, starved in accept queue)
[18:15] <smb>             Will re-upload proposed after security updates
[18:15] <smb> * Intrepid: 2.6.27-14.37 (security, new security release in progress)
[18:15] <smb>             2.6.27-14.38 (proposed+security)[20] with 8/24 verifications
[18:15] <smb>             [replacement ready to include security]
[18:15] <smb> * Jaunty:   2.6.28-15.48 (updates, new security release in progress)
[18:15] <smb>             \o/ big proposed update made it into updates!
[18:15] <smb> The security packages are just now in the oven and should be baked soon.
[18:15] <smb> Replacement for Intrepid proposed is in place to be accepted.
[18:16]  * apw points out the jaunty update ... finally that biggy with the stable update made it into -updates
[18:16] <cking> thanks smb
[18:16] <smb> Yeah, this helps a lot
[18:16] <cking> [TOPIC] Netbook Trees: status (sconklin)
[18:16] <MootBot> New Topic:  Netbook Trees: status (sconklin)
[18:17] <sconklin> The Jaunty LBM was branched for netbook last week (by apw). That's about it.
[18:17] <apw> we are also trying to solidify process for direct uploads to the trees
[18:17] <sconklin> right
[18:17] <cking> any idea of any patches coming down the pipe?
[18:17] <apw> as we will have some new security uploads soon for jaunty at least
[18:18] <cking> thanks..
[18:18] <cking> [TOPIC] Incoming Bugs: Regressions (ogasawara)
[18:18] <apw> we are hoping for clarification on the karmic patch stack
[18:18] <MootBot> New Topic:  Incoming Bugs: Regressions (ogasawara)
[18:18] <ogasawara> There was 1 kernel config regression but it's been resolved by Luke.
[18:18] <ogasawara> I'd also note a few others seems to have been resolved with -rc6
[18:18] <cking> still too early to see if rc6 introduces any more regressions?
[18:19] <apw> yeah we don't have that big a testing base as yet
[18:19] <ogasawara> cking: I've been monitoring and have seen maybe 1 or 2 get tagged as regressions
[18:19] <apw> as we near beta it is increasing as is the regression count
[18:19] <cking> moving on..
[18:19] <cking> [TOPIC] Incoming Bugs: Bug day report (ogasawara)
[18:19] <MootBot> New Topic:  Incoming Bugs: Bug day report (ogasawara)
[18:19] <ogasawara> Off to a slow start, but current progress can be seen at:
[18:19] <ogasawara> http://qa.ubuntu.com/reports/ogasawara/kernel-bugday/20090818.html
[18:19] <MootBot> LINK received:  http://qa.ubuntu.com/reports/ogasawara/kernel-bugday/20090818.html
[18:20] <cking> any community input?
[18:20] <apw> yeah not had a chance to look at mine as yet, hoping to get to them tommorrow
[18:20] <ogasawara> cking: not yet :(
[18:21] <cking> thanks ogasawara
[18:21] <cking> [TOPIC] Open discussion or Questions: Anyone have anything?
[18:21] <MootBot> New Topic:  Open discussion or Questions: Anyone have anything?
[18:21] <apw> dhillon-v101, have anything
[18:21] <dhillon-v101> yah I wanted to know more about how I can help
[18:21] <james_w> o/
[18:22] <ogasawara> dhillon-v101: I'd be more than happy to get you started
[18:22] <apw> sounds good, if you are interesting in how you can help i recon thats a discussion for over on #ubuntu-kernel, we always are keen for help
[18:22] <dhillon-v101> thanks bjf told me you would help me out
[18:22] <pgraner> Reminder for the community the Ubuntu Kernel Team will be at Atlanta LinuxFest doing various things... talks, driver hacking session and karmic hw testing
[18:22] <pgraner> Its on 19 Sep http://atlantalinuxfest.org
[18:22] <ogasawara> dhillon-v101: jump on #ubuntu-kernel after the meeting and we'll talk more
[18:23] <dhillon-v101> ogasawara: thank you very much
[18:23] <cking> great
[18:23] <cking> Anything else?
[18:23] <pgraner> For the team if you have a blog get the word out
[18:23] <amitk> james_w had a question
[18:23] <james_w> apw: I've definitely seen a drop in interactive performance under I/O load again since the heydey of early karmic, any chance we could get back to that point?
[18:23] <james_w> I know you had an idea about which patches were credited with that improvement
[18:24] <apw> james_w, the only one i found to be outstanding in the mix was the -rc which had
[18:24] <apw> broken load average
[18:24] <james_w> oh
[18:24] <apw> i am still not finding it as bad as jaunty, but not as good as that was
[18:24] <james_w> I agree
[18:24] <apw> i suspect there is an intereaction there
[18:25] <apw> i haven't had a chance to investigate more than that
[18:25] <cking> perhaps filing a bug to raise it's profile and keep this one tracked?
[18:25] <james_w> I can do that, though it won't be a very informed report
[18:26] <apw> i think there is one, searching for 'heavy i/o load' i think
[18:26] <cking> right.. any other open questions...
[18:27] <cking> [TOPIC] Next Meeting Chair: Manoj Iyer
[18:27] <MootBot> New Topic:  Next Meeting Chair: Manoj Iyer
[18:27] <apw> heh, as he is off, he didn't complain ... ship it :)
[18:27] <rtg> all opposed?
[18:27] <james_w> bug 131094?
[18:27] <apw> james_w, sounds about right
[18:28] <james_w> subscribed, thanks
[18:28] <cking> Manoj it is
[18:28] <cking> Think that's all
[18:28] <cking> 5
[18:28] <cking> 4
[18:28] <apw> 1
[18:28] <cking> 0!
[18:28] <cking> #endmeeting
[18:28] <MootBot> Meeting finished at 12:28.
[18:28] <smb> what happended to 3 and 2 ?
[18:28] <apw> i optimised them out
[18:28] <cking> apw expedited me
[18:28] <lieb> bye
[18:29] <apw> cking, thanks!
[18:29] <cking> thanks everyone
[18:29] <smb> cking, +1
[18:29]  * apw gives cking a dholbach style hug
[18:29] <amitk> bye
[18:29] <cking> cheers. That's my first meeting - not so bad after all
[20:02] <JanC> who's here for the loco council meeting?
[20:02] <popey> o/
[20:02]  * sbc listens in
[20:02] <JanC> juliux: ping?
[20:03] <effie_jayx> o/
[20:03] <Flare183> JanC: I am.
[20:04] <juliux> half here
[20:04] <juliux> i am haveing a phone conference atm
[20:05] <JanC> there isn't much on the agenda (no approvals), but I think effie_jayx was going to say something about the loco directory ?
[20:05] <effie_jayx> pk
[20:06] <effie_jayx> just to give a quick update and answer a few q's on the LoCo Directory and how it will be integrated to the way team data i handled
[20:07] <effie_jayx> rigght now the frist reelase is coded, iut has been reviewed by folks at canonical
[20:07] <effie_jayx> and we are just waiting for it to be put online. according to jono it should be another week or so.
[20:08] <effie_jayx> the loco directory will replase the Big LoCo team list that has served us as a way to find the relevant info for teams
[20:10] <effie_jayx> we are still defining de details for release 0.2, and it seems we will be adding more features soon
[20:10] <effie_jayx> if you want to keep uip with the latest info on the directory the pleace to check is https://wiki.ubuntu.com/LoCoDirectory
[20:11] <effie_jayx> and I am happy to answer some q's from the Council if you have any
[20:12] <JanC> and questions from other people who follow the meeting are welcome too I guess  ツ
[20:12] <effie_jayx> exactly
[20:12] <effie_jayx> thanks
[20:12] <effie_jayx> any questions at all?
[20:13] <greg-g> yes: how awesome with the loco directory be?
[20:13] <jacob> is there a (public) running instance of this somewhere to preview without having to branch & install?
[20:13] <greg-g> s/with/will/
[20:13] <popey> :)
[20:13] <Daviey> greg-g: Really AWESOME.
[20:13] <effie_jayx> greg-g, initially it just replaces the funtionality of the big list
[20:13] <greg-g> Daviey: awesome. thanks!
[20:13] <greg-g> effie_jayx: awesome.
[20:13] <effie_jayx> it does provide launchpad integration
[20:13] <effie_jayx> for date
[20:14] <effie_jayx> data
[20:14]  * greg-g appologizes, he seems to have caught something from jcastro
[20:14] <Daviey> effie_jayx: read only, i assume?
[20:14] <popey> Daviey: yes, we maintain a list of non-approved and approved locos in launchpad
[20:14] <effie_jayx> Daviey, it only takes names and other important data from the already created team in launchpad
[20:14] <popey> data is plucked from that
[20:14] <effie_jayx> it does so throuigh the launchpad api
[20:15] <effie_jayx> so the integration with launchpad makes it really usefull
[20:16] <effie_jayx> we are hoping to have more features that can cmplement the social part that laucnhpad can't cover
[20:16] <effie_jayx> like knowing wehat events each teams has
[20:16] <effie_jayx> and maybe sharing pics there
[20:17] <effie_jayx> blueprints are always welcome
[20:17]  * Daviey did start making a locomap that i intended to merge with the project.
[20:18] <effie_jayx> I am working on the xml file as we speak
[20:18] <effie_jayx> ;)
[20:18] <Daviey> effie_jayx: the stuff i did was based on json output.
[20:19] <effie_jayx> ahhh
[20:19] <effie_jayx> even more vcariants
[20:19] <effie_jayx> :D
[20:19] <Daviey> http://locomap.daviey.com/
[20:19] <effie_jayx> we already have 2 proposals for maps and we are intereted in checking more out
[20:19] <effie_jayx> the mopre diversity the better
[20:19] <Daviey> i pulled in data before there was a loco team, so i had to add teams manually
[20:19] <effie_jayx> well
[20:21] <effie_jayx> looks awesome
[20:22] <effie_jayx> if ther is anything we can do to ease the pain let us know
[20:22] <effie_jayx> a bug report with any data output perhaps
[20:22] <Daviey> well i haven't touched that code for 4 months.. i showed it to jono and well.. stayed there :)
[20:22] <effie_jayx> looks cool
[20:23] <effie_jayx> well maybe we can keep in touch about this and see how we can make it grab data from the django app itself
[20:23] <effie_jayx> I am already doing this for a drupal integration effort
[20:23] <Daviey> ^^ that is a django app, so should be pretty trival
[20:24] <effie_jayx> fantastic
[20:24] <Daviey> i've got my own database scheme pulling in data from lp, but shouldn't be too much effort to pull that out.
[20:25] <effie_jayx> Daviey, we did that as well
[20:26] <effie_jayx> any more questions?
[20:26] <popey> none here
[20:26] <effie_jayx> great
[20:26] <popey> thanks for the update effie_jayx
[20:26] <effie_jayx> I am done :D
[20:26] <effie_jayx> no problem
[20:27] <popey> short meeting :)
[20:27] <effie_jayx> lovely meeting
[20:27] <JanC> someone has another question?
[20:28] <JanC> (not about the loco directory I mean)
[20:28] <effie_jayx> I have another thing to mention
[20:29] <effie_jayx> not related to the loco directory
[20:29] <effie_jayx> mmm it seems better for a loco team meeting
[20:31] <effie_jayx> nevermind
[20:31] <effie_jayx> JanC, adjourn?
[20:31] <JanC> well, if nobody has anything more to say or ask, we can close the meeting I suppose  :-)
[20:32] <JanC> thanks everybody
[20:33] <effie_jayx> thanks JanC popey
[20:33] <popey> np