[00:15] <Manuelbrs> alguien que brinde ayuda aqui?
[00:30] <kklimonda> !es | Manuelbrs
[00:31] <kklimonda> I wonder whether it's the right language.
[00:32] <Manuelbrs> gracias
[04:52] <Mosibe> Buenas
[11:02]  * persia peers about
[11:19]  * persia doesn't see prabhash, or anything else on the agenda, so figures the meeting must be cancelled
[14:06] <NCommander> #startmeeting
[14:06] <MootBot> Meeting started at 08:06. The chair is NCommander.
[14:06] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[14:07] <GrueMaster> Morning.
[14:07]  * NCommander forgot that this meeting was in the morning after a month in China
[14:07] <mpoirier_> o/
[14:07] <dyfet> *blink*
[14:07] <davidm> G'day NCommander
[14:08]  * NCommander swears
[14:08] <NCommander> I think the wiki page forgot to save
[14:08] <NCommander> give me a sec
[14:08] <ogra> hmm
[14:09] <NCommander> [topic] Action Item Review
[14:09] <MootBot> New Topic:  Action Item Review
[14:09] <ogra> you dont have the action items ...
[14:09] <NCommander> [topic] ogra to talk to rsalveti about the darn EDID spec, reassigning it and new workitems
[14:09] <MootBot> New Topic:  ogra to talk to rsalveti about the darn EDID spec, reassigning it and new workitems
[14:09] <ogra> done
[14:09] <rsalveti> working on it now :-)
[14:09] <NCommander> [topic] NCommander to clean up thumb2 assignments from http://qa.ubuntu.com/reports/team-assigned/canonical-mobile-assigned-bug-tasks.html which he definitely wont work on this cycle
[14:09] <MootBot> New Topic:  NCommander to clean up thumb2 assignments from http://qa.ubuntu.com/reports/team-assigned/canonical-mobile-assigned-bug-tasks.html which he definitely wont work on this cycle
[14:09] <NCommander> c/o
[14:09] <ogra> pfft
[14:10] <NCommander> [topic] ogra to clearify uboot-imx bugs with jcrigby
[14:10] <MootBot> New Topic:  ogra to clearify uboot-imx bugs with jcrigby
[14:10] <ogra> c/o
[14:10] <ogra> imx is really low prio
[14:10] <NCommander> [topic] ogra to update the title and generalize bug 628029
[14:10] <ogra> at least that part
[14:10] <MootBot> New Topic:  ogra to update the title and generalize bug 628029
[14:10] <ogra> whoops
[14:10] <ogra> c/o
[14:10] <NCommander> [topic] NCommander to talk to davidm about adding dove to https://wiki.ubuntu.com/MaverickMeerkat/ReleaseManifest
[14:11] <MootBot> New Topic:  NCommander to talk to davidm about adding dove to https://wiki.ubuntu.com/MaverickMeerkat/ReleaseManifest
[14:11] <NCommander> Done
[14:11]  * ogra applauds
[14:11] <NCommander> [TOPIC] Standing Items
[14:11] <MootBot> New Topic:  Standing Items
[14:11] <NCommander> http://people.canonical.com/~pitti/workitems/maverick/canonical-mobile.html
[14:11] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/maverick/canonical-mobile.html
[14:11] <NCommander> http://people.canonical.com/~pitti/workitems/maverick/canonical-mobile-ubuntu-10.10.html
[14:11] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/maverick/canonical-mobile-ubuntu-10.10.html
[14:12] <ogra> wohooo !
[14:12] <ogra> below trend
[14:13] <NCommander> yay
[14:13] <ogra> well, not in the overall one
[14:13] <ogra> but for 10.10
[14:13] <NCommander> [TOPIC] Kernel Status (cooloney, mpoirier, lag(
[14:13] <MootBot> New Topic:  Kernel Status (cooloney, mpoirier, lag(
[14:14] <mpoirier_> nothing to declare.
[14:14] <ogra> bug 605042 ... will screw us if we dont find a fix on imx51
[14:14] <persia> I thought that was fixed with the reversion to b18
[14:14] <ogra> persia, the buildd screwup ?
[14:14] <ogra> no
[14:15] <lag> I have
[14:15] <persia> Oh :(
[14:15] <ogra> the kernel on the buildds makes java segfault
[14:15] <lag> o/    When you're ready
[14:15] <ogra> which makes all packages using java binaries ftbfs
[14:15] <ogra> lag, go
[14:15] <lag>  * Marvel (mvl-dove)
[14:15] <lag>    * Nothing new this week
[14:15] <lag>  * Freescale (fsl-imx51)
[14:15] <lag>    * ON GOING : B605042: Java segfault on Freescale iMX5.1 Babbage board with Lucid - will try to bisect Lucid 2.6.31 kernel
[14:15] <lag>  * Texas Instruments (ti-omap)
[14:15] <lag>    * ON GOING : B591941 Original patch was not complete - Adrian Hunter should release the final patch this week.
[14:15] <lag>    * ON GOING : B608266 Fix submitted and accepted - still waiting for mobile team to test.
[14:15] <lag>    * ON GOING : B633227 ES2.0 board is unstable when highmem is enabled - backported a patch from upstream to solve memtester issue
[14:15] <lag>    * ON GOING : B628029 ES2.0 board does not boot with CONFIG_PM enabled
[14:15] <lag>    * NEW      : B622935 a patch has been written - author needs to send it upstream
[14:15] <lag>    * PATCH    : Lots of TI audio patches have now been applied - testing under way
[14:15] <lag>    * PATCH    : B563650 upstream patch was applied
[14:16] <lag>    * PATCH    : B477106 Lucid alpha-2 and earlier freeze upon suspend with sd card plugged in with some hardware
[14:16] <lag>    * PATCH    : B588243 upstream patch was applied
[14:16] <lag>    * FIXED    : B613855 omap3 beagle XM MMC card always comes up read-only
[14:16] <lag>    * FIXED    : B605488 scheduling while atomic: mmcqd/46/0x00000002
[14:16] <lag>    * FIXED    : B589624 omap flavour does not work on beagle XM board
[14:16] <lag>    * FIXED    : B605832 LG monitor behaving incorrectly when used in conjunction with the Panda board and HDMI
[14:16] <lag>    * FIXED    : B477106 Maverick alpha-2 and earlier freeze upon suspend with sd card plugged in with some hardware
[14:16] <lag>    * FIXED    : B592295 omapdss DISPC error: SYNC_LOST_DIGIT
[14:16] <lag>    * FIXED    : B628107 false alarm - first boot loaded unstable kernel
[14:16] <lag> ..
[14:16] <ogra> i see some weird display issues on omap4 at,
[14:16] <ogra> *atm
[14:16] <ogra> which are not easily reproducable
[14:16] <GrueMaster> I will be testing 608266 today.
[14:17] <rsalveti> ogra: like what?
[14:17] <ogra> screen goes black and i can only get it back when switching consoles
[14:17] <lag> Yeah, I have that
[14:17] <lag> Although, when I do switch consoles, I only have a display for a few seconds then that dies too
[14:17] <ogra> EEEK !
[14:18]  * ogra just looked at dmesg on his panda for the first time this week
[14:18] <ogra> [89357.432678] swapper: page allocation failure. order:3, mode:0x4020
[14:18] <ogra> *sigh*
[14:18] <ogra> lots of them
[14:18] <rsalveti> =\
[14:18] <ogra> gah, i thought that was gone
[14:19] <ogra> lag, it stays for me and i dont have anything display related in dmesg usually
[14:19] <GrueMaster> Is that today's image?
[14:19] <ogra> GrueMaster, yesterdays
[14:19] <rsalveti> but kernel should be the same
[14:19] <lag> ogra: Mine just went black :(
[14:19]  * ogra wishes dmesg would have proper timestamps
[14:20] <GrueMaster> I'm running 20100913 on ES2 and not seeing the page allocation failures.
[14:20] <ogra> i just did lots of apt-get stuff on the panda, i wonder if the page allocation stuff is related
[14:20] <ogra> but hard to tell without a proper timestamp
[14:20] <lag> Okay, it's staying now
[14:21] <lag> But there's no messages in dmesg
[14:21] <ogra> right
[14:21] <ogra> same for me
[14:21] <ogra> i wonder if userspace triggers some DPMS stuff that hangs until you switch consoles
[14:21] <lag> No, I have it
[14:21] <persia> Might be better to do the low-legel debugging discussion after the meeting...
[14:21] <ogra> persia, indeed
[14:21] <lag> It's the GFX_FIFO_UNDERFLOW again
[14:21] <lag> ack
[14:21] <ogra> lag, ah, i think i saw that
[14:21] <NCommander> can I move on?
[14:22] <lag> ..
[14:22] <ogra> NCommander, go
[14:22] <NCommander> [topic] QA Status (GrueMaster)
[14:22] <MootBot> New Topic:  QA Status (GrueMaster)
[14:23] <GrueMaster> Worked a bit on a script to generate a launchpad report with all open bugs.  WIP.
[14:23] <GrueMaster> Most of my testing is on apps atm.  Testing on all running systems as simultaneously as possible.
[14:24] <GrueMaster> I'm still getting some random, hard to reproduce bugs that don't generate enough debug output for the devs to work on.
[14:24]  * ogra looked at go-home-applet today
[14:25] <GrueMaster> I saw that, cool.
[14:25] <ogra> and found some work for our contractor :)
[14:25] <GrueMaster> Will it get fixed before release?
[14:25] <GrueMaster> We are weeks away.
[14:25] <ogra> GrueMaster, if you find bugs that are clearly -efl, feel free to assign to him (and notify me)
[14:25] <ogra> i'm working on a fix for go-home today
[14:25] <GrueMaster> I'll need his info.
[14:25] <ogra> not sure about efl
[14:25] <ogra> look at the bug :)
[14:26] <GrueMaster> Ok.
[14:26] <ogra> i assigned the efl part to him
[14:26] <ogra> and go-home to me
[14:26] <GrueMaster> Go-home looks like an easy fix.  porting the add-to-fav's may be a little more work.
[14:26] <GrueMaster> And not as critical.
[14:26] <ogra> i'm also going through the remaining jasper bugs today
[14:27] <GrueMaster> I also filed a low priority bug on go-home-applet wrt the version reported.
[14:27] <ogra> sadly our contractor is in a werid TZ
[14:27] <GrueMaster> aren't we all. :P
[14:27] <ogra> like US westcoast ... i think
[14:27] <ogra> :P
[14:28] <ogra> so i havent talked to him yet
[14:28] <GrueMaster> Erm, that is the pacific Standard timezone, thankyou.
[14:28] <NCommander> can I move on?
[14:28] <GrueMaster> go
[14:28] <ogra> ++
[14:28] <NCommander> [topic] ARM Porting/FTBFS status (NCommander, dyfet)
[14:28] <MootBot> New Topic:  ARM Porting/FTBFS status (NCommander, dyfet)
[14:29] <dyfet> Well, I am focused this morning on two packages, gcl and hdf5
[14:29] <ogra> great !
[14:29] <ogra> doko asked for them
[14:29] <dyfet> I am trying to reduce the hdf5 issue into a simple test case
[14:29] <NCommander> ubiquity remains dead on Dove
[14:30] <NCommander> (and armel in general I guess)
[14:30] <NCommander> Looking into that this week
[14:30] <dyfet> gcl I think may be an underlying toolchain bug
[14:30] <ogra> NCommander, dead as in FTBFS ?
[14:30] <NCommander> ogra: segfault
[14:31] <ogra> NCommander, note that ubiquity runs fine on omap
[14:31] <ogra> so must be either dove specific or partitioner issue
[14:31] <NCommander> ogra: ubiquity is running in oem-config mode, and not in full installation mode.
[14:31] <ogra> since we use everything but the partitioner on omap
[14:31] <NCommander> ogra: right. I'm working on it.
[14:31] <ogra> k
[14:31] <NCommander> We might just change to alternates for release if necessary if this proves difficult to fix (already discussed with davidm)
[14:32] <ogra> oem-config mode isnt much different to normal install mode
[14:32] <ogra> just adds the extra panel and supresses partitining
[14:32] <ogra> NCommander, why not preinstalled ?
[14:32] <ogra> would save us QA effort
[14:32] <NCommander> ogra: cause 1. preinstall images require hacks to livecd-rootfs.sh for each subarch 2. you actually want to install on Dove since it has both SATA, and FTL NAND
[14:32] <davidm> NCommander, I really don't want to use alternates
[14:33] <GrueMaster> Not much.  I actually have more infrastructure to support installs on dove.
[14:33] <ogra> NCommander, leave 2 to server installation ;)
[14:33] <GrueMaster> And the installer works on Dove A0.
[14:33] <GrueMaster> Just not on unsupported hw.
[14:33] <ogra> and 1) isnt really a big issue
[14:33] <NCommander> GrueMaster: it does? I thought it was segfaulting during installation
[14:33] <GrueMaster> That was fixed last week.
[14:33] <NCommander> GrueMaster: oh good. yeah, its known to do that on unsupported installation. I'm working with cjwatson to resolve it.
[14:33] <NCommander> GrueMaster: ah, I must have missed it in my bug mail
[14:34] <ogra> ah, so we talk about a non-issue ?
[14:34] <ogra> great
[14:34] <NCommander> ogra: it must have gotten fixed while I was in transit (I hadn't tested since Thursday)
[14:34] <GrueMaster> The last image available (20100910 I believe) installed fine yesterday.
[14:34] <NCommander> \o/
[14:34] <NCommander> execellent
[14:35] <ogra> 0910 ?
[14:35] <ogra> its 14th today
[14:35] <ogra> NCommander, can you check crontab and make sure dailies build ?
[14:35] <ogra> i think there was a big difference between tree and real crontab when i checked
[14:35] <NCommander> ogra: will do
[14:35] <ogra> just didnt have the time to fix it
[14:35] <GrueMaster> 20100909 is the latest (looking on cdimage now.
[14:35] <GrueMaster> )
[14:36] <NCommander> ogra: I *really* want to know who is changed it; I know I had the tree and the actual crontab in sync
[14:36] <ogra> yeah, seems like dailies dont happen
[14:36] <ogra> 0910 was a manual build i did
[14:36] <NCommander> [action] NCommander to smash antimony's crontab's with a big large golden brick
[14:36] <MootBot> ACTION received:  NCommander to smash antimony's crontab's with a big large golden brick
[14:36] <NCommander> [topic] Weekly Activity Reports (all)
[14:36] <MootBot> New Topic:  Weekly Activity Reports (all)
[14:36] <GrueMaster> Not seeing dailies for omap either.
[14:36] <GrueMaster> omap4 is ok.
[14:36] <ogra> [action] NCommander to put something fluffy aounrd the golden brick
[14:36] <NCommander> This topic is a request from davidm for us to do our activity reports here in the meeting
[14:37] <NCommander> (if I understood him right)
[14:37] <ogra> NCommander, yes, he asked me too to take care
[14:37] <NCommander> so I'll go first
[14:37] <NCommander> [topic] NCommander's status
[14:37] <MootBot> New Topic:  NCommander's status
[14:37] <ogra> NCommander, but to have them on the wiki
[14:37] <NCommander> oh
[14:37]  * NCommander coughs
[14:37] <NCommander> Ok
[14:37] <ogra> dont make the meeting longer
[14:37] <NCommander> [action] EVERYONE to put their status on the wiki
[14:37] <MootBot> ACTION received:  EVERYONE to put their status on the wiki
[14:37] <NCommander> [topic] AOB
[14:37] <MootBot> New Topic:  AOB
[14:38] <ogra> action me with hunting people down for them
[14:38] <ogra> did we have image status ?
[14:38] <NCommander> gah
[14:38] <rsalveti> there's a question regarding the opengl es powervr sgx driver
[14:38] <NCommander> [topic] CDimage Status
[14:38] <MootBot> New Topic:  CDimage Status
[14:38] <ogra> heh
[14:38] <rsalveti> for AOB
[14:38] <NCommander> (thanks ogra)
[14:38] <GrueMaster> Easier for me to add to wiki than to type it out at 6:40am.
[14:38] <ogra> we seem to have bad HW
[14:39] <ogra> acorn constantly fails
[14:39] <NCommander> ogra: yeah, the crontab looks like it got changed for beta and never reverted. I'm just going to save a copy and apply the tree (which is what we were using pre-beta)
[14:39] <ogra> usually only survives a day or two
[14:39] <ogra> NCommander, fine with me
[14:39]  * NCommander does a manual spin for Dove
[14:39] <ogra> i asked lamont to try to find out when exactly it fails ... (under load or during idling)
[14:40] <ogra> but we have no outcome there yet
[14:40] <NCommander> speaking of acorn
[14:40] <NCommander> Its dead
[14:40] <ogra> NCommander, yeah
[14:40] <NCommander> ssh: connect to host acorn.buildd port 22: No route to host
[14:40] <NCommander> :-/
[14:40] <ogra> you should have gotten mail about the failed omap build this morning
[14:40] <ogra> if thats emopty its a good indicator its dead
[14:40] <NCommander> ogra: I did.
[14:41] <NCommander> ogra: I hadn't looked at the email though in depth
[14:41] <GrueMaster> Last one I got was two days ago.
[14:41] <NCommander> [action] NCommander to change buildlive to send an email to lamont if acorn is down
[14:41] <MootBot> ACTION received:  NCommander to change buildlive to send an email to lamont if acorn is down
[14:41] <NCommander> :-)
[14:41] <ogra> mean !
[14:41] <ogra> i doubt he likes that
[14:41] <ogra> and he cant do much anyway
[14:41] <NCommander> ogra: well, if you have a better target ...
[14:41] <ogra> since it requires someone to drive over to the location and reboot it by hand
[14:42] <NCommander> ugh
[14:42] <NCommander> disregard then:-/
[14:42] <ogra> someone of the guys who drive over ;)
[14:42] <ogra> i mean, i'm sure lamont would like to know about it ... but effectively he will only trigger manual intervention
[14:43] <ogra> NCommander, ask in #is if they would like such a thing and to whom
[14:43] <NCommander> ogra: k
[14:43] <ogra> though it smells to me like we need to replace the board soon
[14:43] <ogra> its diening more often than it used to
[14:43] <ogra> and the OS is the same all over the place so its unlikely to be software
[14:44]  * NCommander wonders if the kernel team was allowed near it
[14:44] <ogra> heh
[14:44] <NCommander> I think that's everything
[14:44] <NCommander> [topic] AOB
[14:44] <MootBot> New Topic:  AOB
[14:44] <rsalveti> so, regarding the powervr sgx driver for omap3
[14:45] <rsalveti> latest version they changed the license
[14:45] <rsalveti> from export control to TSPA (no registration required)
[14:45] <ogra> sweet !
[14:45] <rsalveti> and from the license definition we're able to distribute it
[14:45] <ogra> does that mean we can pull it to multiverse ?
[14:45] <rsalveti> still restricted, but we can pull it
[14:45] <rsalveti> as they libraries are just binaries
[14:46] <rsalveti> don't know how we work with proprietary stuff
[14:46] <ogra> well, if its suitable for restricted/multiverse we should immediately upload it there
[14:46] <rsalveti> there are 2 pieces, one is the kernel part, that's GPL
[14:46] <ogra> and build our images with it
[14:46] <rsalveti> another is the libraries
[14:46] <rsalveti> I created a first version for the packages, and described the test howto at http://people.canonical.com/~rsalveti/maverick/sgx/HOWTOINSTALL.txt
[14:46] <ogra> if its not different to nvidia/fglrx we can use it
[14:47] <rsalveti> for now I'm separating the kernel part because we should discuss to understand where it should be integrated
[14:47] <rsalveti> ogra: guess it's the same
[14:47] <ogra> rsalveti, you shouldnt use m-a
[14:47] <ogra> use DKMS
[14:47] <rsalveti> http://www.flickr.com/photos/rsalveti/4989404974/
[14:47] <MootBot> LINK received:  http://www.flickr.com/photos/rsalveti/4989404974/
[14:47] <rsalveti> the driver running with beagle xM
[14:47] <ogra> if you could repack them with DKMS they can go in
[14:47] <persia> rsalveti, Could you post the license somewhere?
[14:47] <rsalveti> ogra: yep, saw that after using m-a
[14:48] <rsalveti> persia: sure
[14:48] <rsalveti> ogra: I can work on it
[14:48] <ogra> awesome !
[14:48] <rsalveti> ogra: then the libraries also need some more love
[14:48] <ogra> that would be a big step
[14:48] <rsalveti> as it'll conflict with mesa ones
[14:48] <ogra> like nividas
[14:48] <ogra> or fglrx
[14:49] <ogra> look at these packages
[14:49] <persia> No, it's not as bad as nvidia, but there's work to be done
[14:49] <ogra> they handle the mesa replacements somehow
[14:49] <rsalveti> persia: http://people.canonical.com/~rsalveti/maverick/sgx/TSPA.txt
[14:49] <rsalveti> ogra: yep, will check with these packages
[14:50] <rsalveti> and with asac, as I remember there was a proposal for opengles
[14:50] <ogra> cool, thanks a lot, thats so awesome
[14:50] <ogra> you really really rock !"
[14:50] <rsalveti> Object Code License.  For the Licensed Materials provided in object code format, TI hereby grants to you a limited, non-exclusive license to reproduce and use the Licensed Materials provided to you in object code format and to distribute an unlimited number of object or executable copies of such object code Licensed Materials.
[14:50] <ogra> all beer at UDS is on me !
[14:50] <GrueMaster> Very nice.  With those installed how well does unity work?
[14:50] <rsalveti> this is the piece that I like the most, from the license
[14:50] <ogra> GrueMaster, i think clutter still has issues
[14:50] <GrueMaster> Damn, I won't be there for free beer.
[14:51] <rsalveti> GrueMaster: still didn't check unity
[14:51] <rsalveti> but probably has issues
[14:51] <ogra> and i think we'll need an xserver for it long term ...
[14:51] <ogra> which doesnt exist at all afaik
[14:51] <rsalveti> persia: can you check the license later?
[14:51] <rsalveti> to see if I'm right on it
[14:52] <persia> rsalveti, that license looks OK, depending on the additional materials provided: stuff that falls afoul of the export restrictions, registration requirments, royalty requirements, etc. might have to be multiverse.  Other stuff could be universe.
[14:52] <rsalveti> cool
[14:52] <ogra> persia, well, main then
[14:52] <persia> I'm not authoritative, but I've read a lot of licenses, so there's probably at least an 80% chance the archive-admins would have a similar opinion.
[14:52] <ogra> if we can ship it we can add it to the images
[14:53] <persia> ogra, Doesn't matter really.
[14:53] <ogra> from an image guy POV it does :)
[14:53]  * persia adds "really get rid of the main/universe distinction" to the list of things to bring to UDS
[14:53] <persia> Not really, but sure :)
[14:53] <ogra> well, make it "on image/not on image" then :P
[14:54] <persia> Well, no, but never mind :)
[14:55] <ogra> rsalveti, what about the GPLed kernel bit, culd we get it in the tree ?
[14:55] <ogra> we wouldnt need m-a or DKMS then
[14:55] <rsalveti> ogra: I'd love if we could move to the tree
[14:56] <rsalveti> maybe to staging
[14:56] <ogra> lag, ^^^ ??
[14:56] <persia> lag, ?
[14:56] <ogra> rsalveti, even as sauce or under the ubuntu/ dir :)
[14:56] <rsalveti> ogra: could be
[14:56]  * ogra doesnt mind how ... as long as we can get it
[14:57] <rsalveti> lag: ?
[14:57] <ogra> or mpoirier_ ^^^
[14:57] <ogra> :)
[14:57] <rsalveti> that's why he uses lag as nick
[14:57] <ogra> yeah
[14:57] <mpoirier_> Yes, no problem.
[14:57] <ogra> there is a special meaning ... i always suspected that
[14:57] <lag> Sorry
[14:57] <mpoirier_> but again, I don't have a board to test.
[14:57] <rsalveti> mpoirier_: do you have a beagle?
[14:57] <ogra> mpoirier_, omap3 ?
[14:57] <rsalveti> normal beagle
[14:57] <mpoirier_> ok.
[14:58] <ogra> C4 or some such will do
[14:58] <ogra> we dont have these libs for omap4 yet
[14:58] <mpoirier_> omap3 - no problem.
[14:58] <rsalveti> mpoirier_: if you can work on it I'll send you the links
[14:58] <rsalveti> we can talk on #ubuntu-arm
[14:58] <mpoirier_> yes indeed, more more details.
[14:58] <NCommander> we're almost out of time, can I close the meeting?
[14:58] <rsalveti> no more topics from me
[14:59] <NCommander> #endmeeting
[14:59] <MootBot> Meeting finished at 08:59.
[15:20] <bilalakhtar> Keybuk: Howdy!
[15:20] <bilalakhtar> Keybuk: Is there some part of Upstart in which I can help?
[15:21] <Keybuk> which bit would you like to help with?
[15:21] <bilalakhtar> Keybuk: I am an intermediate developer, so would like to help out in developing some easy part
[15:21] <bilalakhtar> perhaps Upstart is made up of difficult code!
[15:22] <Keybuk> there aren't really many easy parts
[15:22] <Keybuk> there isn't much code, in fact
[15:22] <bilalakhtar> Upstart is small? o_O
[15:22] <Keybuk> yeah, 4000-odd lines of code
[15:23] <Keybuk> and a portion of those are auto-generated
[15:23] <bilalakhtar> okay, that's small-to-medium
[15:26] <Keybuk> what kind of projects do you work on at the moment?
[15:26] <bilalakhtar> Keybuk: Ubuntu (Of course!), Gwibber, The papercuts project
[15:26] <bilalakhtar> trivial parts!
[15:27] <Keybuk> what languages?
[15:28] <bilalakhtar> Keybuk: C mainly, then comes python and PHP
[15:28]  * BlackZ thinks this is not the right channel to talk about that
[15:29] <bilalakhtar> Keybuk: That;s all, I will look at a few upstart bugs to begin with, if I am able to fix 'em. Thanks!
[15:29] <bilalakhtar> BlackZ: okay
[15:30] <Keybuk> that's probably the best way to get started
[15:30] <Keybuk> take a look at some bugs and ask me how I'd fix them
[15:46] <AnAnt> Hello, I possibly won't be able to attend the DMB today, since something has come up at work. If I don't show up, then I'm sorry for that very short notice.
[16:00] <cjwatson> hi
[16:00] <bilalakhtar> hello there cjwatson !
[16:00] <angelabad> hi
[16:01] <cjwatson> geser,persia,stgraber,soren: ping
[16:01] <MichealH> Hi bilalakhtar , cjwatson
[16:01] <cjwatson> can't see Cody or Richard on IRC
[16:03] <geser> Hi
[16:04] <bilalakhtar> 'Hi' has replaced 'pong' nowadays
[16:04] <geser> pong :)
[16:04] <bilalakhtar> geser: :D
[16:05] <ari-tczew> poor attendance :(
[16:05] <czajkowski> cjwatson: don't know if you saw but anAnt gave apologies there at 15:45 for DMB today
[16:05] <cjwatson> I did
[16:06]  * bilalakhtar fears a repeat of 31st of august
[16:06] <ari-tczew> wake up
[16:06] <bilalakhtar> calm down, ari-tczew let us wait
[16:06] <cjwatson> lack of attendance is certainly beginning to irritate me.  we should switch to the new schedule next meeting
[16:07] <cjwatson> ari-tczew: (the people who see what you're saying are *already here*)
[16:07] <bilalakhtar> cjwatson: Monday 12:00 UTC?
[16:07] <ari-tczew> 12:00 UTC is very early date
[16:07] <bilalakhtar> ari-tczew: It will keep on rotating
[16:07] <cjwatson> the new schedule is alternating 12:00 UTC and 19:00 UTC on Mondays
[16:07] <MichealH> 12:00 = Cant do
[16:07] <cjwatson> no single time fits everyone
[16:08] <MichealH> cjwatson: Agreed
[16:08] <bilalakhtar> for me, almost every time fits. I am in the middle of the world :)
[16:08] <ari-tczew> <3 <3 <3 <3 <3
[16:08] <MichealH> bilalakhtar: Me too
[16:09]  * bilalakhtar wants ari-tczew to calm down
[16:09] <cjwatson> I've SMSed Soren
[16:09] <ari-tczew> bilalakhtar: I;m very relaxed, don't be afraid.
[16:09] <ari-tczew> just love sarcasm :P
[16:09] <MichealH> ari-tczew: Well, If you didnt notice, this place is for formal discussions :)
[16:09] <cjwatson> let me see if I can find Cody's and Emmet's numbers
[16:10] <bilalakhtar> I saw soren around 45 minute earlier on #launchpad
[16:11] <cjwatson> SMSed Cody
[16:12] <cjwatson> SMSed Emmet
[16:12] <cjwatson> Cody sends apologies
[16:13] <bilalakhtar> :(
[16:13] <ari-tczew> let's go drinking!
[16:13] <cjwatson> does anyone have Richard's or Stéphane's mobile numbers?
[16:14] <geser> cjwatson: didn't nixternal send recently an email with his number to the DMB list (in a reply for missing votes)?
[16:15] <cjwatson> good call.  I'll text him
[16:15]  * MichealH could help if needed
[16:16] <cjwatson> only if you have Stéphane's mobile number ...
[16:16] <czajkowski> MichealH: I think they're trying to actually get the DMB members here
[16:16] <cjwatson> other than that I've done the best I can
[16:17] <MichealH> czajkowski: Okay
[16:17] <bilalakhtar> Thanks cjohnston , let us hope your efforts do make a difference
[16:17] <bilalakhtar> argh
[16:17] <bilalakhtar> tab-fail
[16:17] <bilalakhtar> cjwatson: ^^
[16:17] <bilalakhtar> cjohnston: sorry, unping
[16:17] <MichealH> bilalakhtar: Let me gues... cj<tab>
[16:17] <MichealH> hehe
[16:18] <MichealH> Do cjw<tab>
[16:18]  * bilalakhtar goes for praying, will be back in 5 mins to see what's going on
[16:18] <cjwatson> assuming :-( that nobody else shows up, I propose we hold an extra meeting to try to catch up, so the schedule would be: Monday 20 Sep @ 1200 UTC, Monday 27 Sep @ 1900 UTC, Monday 11 Oct @ 1200 UTC, Monday 25 Oct @ 1900 UTC
[16:18] <cjwatson> and thenceforth every two weeks
[16:18] <cjwatson> any objection?
[16:19] <cjwatson> in the forlorn hope that we can actually get a quorum of board members to show
[16:19] <czajkowski> cjwatson: if you're the only board member present, tis your call :)
[16:19] <ari-tczew> get used to
[16:20] <cjwatson> geser is here too
[16:20] <czajkowski> ok 2
[16:20] <ari-tczew>  Monday 27 Sep @ 1900 UTC my date
[16:21] <MichealH> I can do 27@ 19:00
[16:21] <cjwatson> we could start with 1900 instead if that suits the people who've been waiting for ages
[16:21] <cjwatson> (i.e. 20 Sep @ 1900, 27 Sep @ 1200, 11 Oct @ 1900, ...)
[16:21] <MichealH> I can do 10:00 UTC, yeah
[16:21] <angelabad> I can  Monday 20 Sep @ 1200
[16:21] <ari-tczew> cjwatson: I would prefer 20th Sep 19:00
[16:21] <sconklin> I will show up at any time you choose
[16:22] <cjwatson> MichealH: I don't see you on https://wiki.ubuntu.com/DeveloperMembershipBoard/Agenda, are you applying?
[16:22] <ari-tczew> cjwatson: last time me and angelabad were not reviewed due to not quorum
[16:22] <MichealH> cjwatson: Im supporting bilalakhtar
[16:22] <cjwatson> angelabad,bilalakhtar: quick show of hands on preferred time on 20 Sep?
[16:22] <cjwatson> MichealH: ah
[16:22] <cjwatson> ari-tczew: I know :-(
[16:23] <angelabad> me last two times :-(
[16:23] <MichealH> cjwatson: I cant do 12:00 UTC (at school)
[16:23] <ari-tczew> angelabad: what do you think about 20th Sep 19:00 Utc?
[16:23] <MichealH> I can do 19:00 UTC though cjwatson
[16:23] <bilalakhtar> back
[16:23] <bilalakhtar> MichealH: please!
[16:24] <bilalakhtar> cjwatson: hmm, 19:00 UTC
[16:24] <MichealH> bilalakhtar: ?
[16:24] <angelabad> for at 20th the time isnt important
[16:24] <bilalakhtar> MichealH: Please don't bug DMB members for nothing, your opinion is not needed right now
[16:24] <ari-tczew> cjwatson: I don't want be demanding, but I guess that  next meeting should be planned for delayed people : me and angelabad
[16:24]  * bilalakhtar doesn't know why he is missed out
[16:25] <cjwatson> ari-tczew: certainly, the queue is in FIFO order
[16:25] <cjwatson> ari-tczew: you're first on the list followed by angelabad
[16:25] <bilalakhtar> then Jmos, then me
[16:25] <bilalakhtar> *Kmos
[16:26] <MichealH> So there is no meeting?
[16:26] <ari-tczew> MichealH: bingo
[16:26] <bilalakhtar> MichealH: :( not for now, some time later
[16:26] <MichealH> Okay...
[16:26] <ari-tczew> we just drinking coffe
[16:26]  * MichealH /aways
[16:26] <ari-tczew> cjwatson: are you agree with 20th Sep 19:00 UTC?
[16:27] <cjwatson> yes.
[16:27] <ari-tczew> angelabad: ^^
[16:27] <angelabad> its ok for me
[16:27] <ari-tczew> great!
[16:27] <MichealH> ari-tczew: Its okay for me
[16:27] <bilalakhtar> fine for me, though it might be a bit late in the night, but I accept it
[16:27] <ari-tczew> MichealH: nice, but where are you on Agenda wiki page?
[16:27] <cjwatson> sigh.  I think we have to give up on today.  I'm composing a mail to the DMB right now, and have set a calendar event for myself: barring objections, I'll send it to ubuntu-devel-announce on Thursday
[16:27] <MichealH> ari-tczew: Im supporting bilalakhtar
[16:28] <czajkowski> MichealH: then it really doesnt matter what time tbh, they are trying to sort a date out for candidates not supporters
[16:28] <MichealH> czajkowski: Okay
[16:28] <ari-tczew> czajkowski: hmm, are you also related to meeting?
[16:28] <cjwatson> geser said by mail that he may not be able to make it at 1200 generally, but can make 1900
[16:28] <czajkowski> ari-tczew: no
[16:28] <cjwatson> soren is fine with 1900
[16:28] <bilalakhtar> ari-tczew: czajkowski isn't, she is the leader of the loco-council
[16:28] <ari-tczew> cjwatson: great 1900 rulez
[16:29] <cjwatson> persia can't do 1900
[16:29] <bilalakhtar> persia was usually fine with this time, what's the matter now?
[16:29] <czajkowski> not leader, member.
[16:29] <cjwatson> and I will harass everyone else
[16:29] <cjwatson> bilalakhtar: 1900 is a pretty obnoxious time in Japan
[16:29] <ari-tczew> cjwatson: could you update wiki for date?
[16:29] <cjwatson> I will do
[16:29] <cjwatson> 1500 UTC is just "stay up late" kind of thing
[16:30] <bilalakhtar> soren might come on the channel soon, he is just away
[16:30] <bilalakhtar> AND he was here an hour ago
[16:30] <bilalakhtar> talking on #launchpad
[16:30] <cjwatson> that would still only give us three
[16:30] <ari-tczew> even so it's not quorum
[16:30] <bilalakhtar> 3 - 4 = -1
[16:33] <cjwatson> right, tetchy mail sent to dmb@
[16:33] <cjwatson> sorry
[16:33] <ari-tczew> cjwatson: maybe dmb should invite more members?
[16:33] <ari-tczew> I suggest people like ScottK or dholbach
[16:34] <cjwatson> we had a nomination pass recently, and will be starting an election for that soon
[16:35] <ari-tczew> aha
[16:36] <bilalakhtar> wah! I dropped a plan to go to the beach because of this meeting, and, *sad*
[16:37] <highvoltage> cjwatson: did you get stgraber's number?
[16:39] <cjwatson> highvoltage: yes
[16:39] <cjwatson> bilalakhtar: I'm sorry :(
[16:39] <bilalakhtar> cjwatson: ah, not your fault :)
[16:40] <ari-tczew> bilalakhtar: I suggest you to prepare some other work till next meeting
[16:40] <nixternal> argh, cjwatson sorry, I just got your message
[16:40] <cjwatson> yay for SMS, eh?
[16:40] <cjwatson> ok, well, we're really too late to start now even if (say) soren does show up
[16:40] <nixternal> no, I forgot to turn my phone on this morning :)
[16:41] <cjwatson> nixternal: see my mail to the board list, anyway
[16:41] <nixternal> roger that
[16:42] <bilalakhtar> cjwatson: Why are we late? What would stop you people from starting a meeting now for ari-tczew and angelabad , atleast?
[16:42] <cjwatson> true.  but we still only have three
[16:43] <angelabad> :(
[16:43] <cjwatson> if somebody else shows up, and candidates are still here, and the channel is free, and people haven't had to wander off (which I'll need to do in about an hour and a quarter), then we can do some review
[16:44]  * bilalakhtar hopes soren comes around and geser doesn't wander
[16:47] <angelabad> I can wait for one hour more or less
[16:47] <AnAnt> I'm here
[16:47] <highvoltage> cjwatson: didn't you get hold of stgraber?
[16:48] <bilalakhtar> AnAnt: The meeting hasn't started yet :(
[16:48] <AnAnt> oh
[16:48] <bilalakhtar> AnAnt: no quorum :((((((((((((((((((
[16:48] <cjwatson> highvoltage: I don't have his phone number, and he isn't responding on IRC.  He's often not available at this time anyway
[16:49] <highvoltage> cjwatson: ok, he's sitting right next to me (sorry I understood that you did)
[16:49] <maco> highvoltage: poke him?
[16:49] <highvoltage> cjwatson: he's poked, I'm not sure if it's too late though
[16:49] <cjwatson> geser: are you still around?
[16:49]  * stgraber waves
[16:49]  * geser is still around
[16:50] <AnAnt> so I made it
[16:50] <cjwatson> aha!  then we have quorum, however briefly
[16:50] <stgraber> sorry, Tuesday morning is always extremely busy ... we should really change meeting time
[16:50] <cjwatson> #startmeeting
[16:50] <MootBot> Meeting started at 10:50.  Meeting started! o_O
[16:53]  * cjwatson finishes reading
[16:53] <ari-tczew> Please ask if you have any doubts. I wouldn't leave understatements.
[16:54] <cjwatson> ok, so the general opinion I'm getting reading through comments from others on your wiki page is that people had got the impression in the past that you were rather impatient and there were some concerns about making sure that everyone was on the same page regarding freeze processes and the like, but that things seemed to be improving
[16:54] <cjwatson> as a MOTU, what would your focus over the next few weeks leading up to release be?
[16:55] <ari-tczew> cjwatson: I prefer to work on merges during development cycle.
[16:55] <ari-tczew> and till next development cycle I'd like fix security issues
[16:56] <cjwatson> can you just clarify what you mean by "development cycle" there, as a few people use that term in different ways?
[16:57] <ari-tczew> cjwatson: e.g. maverick May 2010 - Feature Freeze (13th Sep)
[16:57] <cjwatson> gotcha
[16:57] <cjwatson> there are great comments from the main security team members here
[16:57] <maco> cjwatson: about his understanding of freezes, he came to me before feature freeze for sponsorship to ensure he wouldnt be breaking freeze
[16:57] <cjwatson> what sort of state is universe security in at the moment?  I look at the raw data from time to time, but it doesn't really give the big picture
[16:57] <cjwatson> maco: thanks
[16:58] <cjwatson> (anyone else going to ask anything, or is it just me? :-) )
[16:58] <nixternal> I noted that as well. Seems all comments are fairly positive with a few showing a bit of concern
[16:58] <ari-tczew> cjwatson: I respect FF. do you mean Laney comment?
[16:59] <nixternal> ari-tczew: what are your plans from now until release? if you were granted MOTU, what would see out of you in the next couple of weeks?
[16:59] <cjwatson> ari-tczew: hm?  no, I meant the comments from Kees, Jamie, and Marc, which are all very positive
[16:59]  * stgraber switches to the n900, needs to be out of the office for a few minutes
[16:59] <cjwatson> nixternal: mm, I thought I asked that above :)
[16:59] <cjwatson> 16:54 <cjwatson> as a MOTU, what would your focus over the next few weeks leading up to release be?
[17:00] <nixternal> heh, I didn't see that one slip in
[17:00] <ari-tczew> nixternal: yes, I just answered this to cjwatson
[17:00] <ari-tczew> nixternal: http://paste.ubuntu.com/493711/
[17:01] <nixternal> ahh, fix security issues. yeah, think i could have done without the paste
[17:01] <nixternal> to early to read small fonts i guess
[17:01] <ari-tczew> I would assure that I will ask on #ubuntu-motu when I will be not sure.
[17:01] <nixternal> groovy
[17:02] <ari-tczew> package don't need merging in future - libpdfbox-java and ddd
[17:02] <ari-tczew> Looking on my comments, people see improve in my person and I'm going to better.
[17:03] <cjwatson> I think I'm ready to vote at this point; does anyone have further questions?
[17:03]  * geser has none
[17:03] <nixternal> none here
[17:03] <stgraber> nope
[17:04] <ari-tczew> ;o
[17:04] <cjwatson> [VOTE] Artur Rona for MOTU
[17:04] <MootBot> Please vote on:  Artur Rona for MOTU.
[17:04] <MootBot> Public votes can be registered by saying +1/-1/+0 in the channel, private votes by messaging the channel followed by +1/-1/+0  to MootBot
[17:04] <MootBot> E.g. /msg MootBot +1 #ubuntu-meeting
[17:04] <cjwatson> +1
[17:04] <MootBot> +1 received from cjwatson. 1 for, 0 against. 0 have abstained. Count is now 1
[17:04] <nixternal> +1
[17:04] <MootBot> +1 received from nixternal. 2 for, 0 against. 0 have abstained. Count is now 2
[17:04] <stgraber> +1
[17:04] <MootBot> +1 received from stgraber. 3 for, 0 against. 0 have abstained. Count is now 3
[17:04]  * bilalakhtar rocks on ari-tczew
[17:04] <geser> +1
[17:04] <MootBot> +1 received from geser. 4 for, 0 against. 0 have abstained. Count is now 4
[17:05] <ari-tczew> hoho!
[17:05] <bilalakhtar> Congrats ari-tczew !
[17:05] <cjwatson> [ENDVOTE]
[17:05] <MootBot> Final result is 4 for, 0 against. 0 abstained. Total: 4
[17:05] <cjwatson> ari-tczew: welcome, and thank you for your patience
[17:05] <nixternal> congrats and welcome ari-tczew \o/
[17:05] <ari-tczew> thanks everyone!
[17:05] <bilalakhtar> ari-tczew is a MOTU!
[17:06] <ari-tczew> bilalakhtar: calm down :P
[17:06] <cjwatson> (excuse me, firefox is being slow again)
[17:06]  * nixternal chuckles - chromium -dev is nice and fast :)
[17:07] <ari-tczew> very long way, but it;s gained :)
[17:07] <cjwatson> [TOPIC] Universe Contributor Application: Angel Abad
[17:07] <MootBot> New Topic:  Universe Contributor Application: Angel Abad
[17:07] <cjwatson> angelabad: still here?
[17:07] <angelabad> yes, im here
[17:08] <angelabad> any questions?
[17:08] <cjwatson> excuse me, my father just called, can somebody please drive for a bit?
[17:08] <bilalakhtar> angelabad: they're reading, wait for a few minutes
[17:08] <angelabad> ok, sorry
[17:08] <nixternal> nice endorsements, looks like good work all around
[17:09] <angelabad> nixternal, thanks!
[17:10] <cjwatson> this all looks pretty good.  you mention you're planning on doing sponsorship work; what skills do you feel you need to develop there?
[17:10] <nixternal> "I dont like very much that sometimes poorly tested software is included in Ubuntu distribution. Sometimes it is better to have stability that the latest version."   <- ahh, a breath of fresh air. my same exact thoughts, though I like to expand on that. I don't like when devs upload a crap package just to try and beat a freeze, or upload a package during the beginning of the cycle without much testing, therefor leading to a ton of blog
[17:11] <cjwatson> cut off at "ton of blog"
[17:12] <zkriesse> G'day...supporting my buddy bilalakhtar
[17:12] <nixternal> ...therefor leading to a ton of blog posts and tweets on how to get around the mess they created
[17:12] <angelabad> cjwatson, first gain more experience
[17:15] <angelabad> cjohnston, and second improve my English
[17:15] <angelabad> sorry cjwatson, and sorry for my lag
[17:16] <cjwatson> anyone have further questions?
[17:17]  * nixternal none
[17:17]  * geser none too
[17:17] <cjwatson> [VOTE] Angel Abad for Universe Contributor
[17:17] <MootBot> Please vote on:  Angel Abad for Universe Contributor.
[17:17] <MootBot> Public votes can be registered by saying +1/-1/+0 in the channel, private votes by messaging the channel followed by +1/-1/+0  to MootBot
[17:17] <MootBot> E.g. /msg MootBot +1 #ubuntu-meeting
[17:17] <cjwatson> (implies Ubuntu membership)
[17:17] <cjwatson> +1
[17:17] <MootBot> +1 received from cjwatson. 1 for, 0 against. 0 have abstained. Count is now 1
[17:18] <geser> +1
[17:18] <MootBot> +1 received from geser. 2 for, 0 against. 0 have abstained. Count is now 2
[17:18] <nixternal> +1
[17:18] <MootBot> +1 received from nixternal. 3 for, 0 against. 0 have abstained. Count is now 3
[17:18] <zkriesse> Can I vote?
[17:18] <bilalakhtar> zkriesse: no!
[17:18] <cjwatson> members of https://launchpad.net/~developer-membership-board may vote
[17:19] <stgraber> +1
[17:19] <MootBot> +1 received from stgraber. 4 for, 0 against. 0 have abstained. Count is now 4
[17:19] <nixternal> congrats and welcome angelabad \o/
[17:19] <stgraber> sorry, just got back in the office
[17:19] <bilalakhtar> Congrats angelabad !
[17:19] <angelabad> thanks a lot!
[17:20]  * bilalakhtar looks around for Kmos, but he isn't here
[17:20] <cjwatson> [ENDVOTE]
[17:20] <MootBot> Final result is 4 for, 0 against. 0 abstained. Total: 4
[17:20] <cjwatson> thanks angelabad, and keep it up :-)
[17:21] <cjwatson> let's move on to bilalakhtar then
[17:21] <angelabad> cjwatson, thanks!
[17:21]  * bilalakhtar climbs up the stage
[17:21] <cjwatson> [TOPIC] MOTU Application: Bilal Akhtar
[17:21] <MootBot> New Topic:  MOTU Application: Bilal Akhtar
[17:21] <geser> cjwatson: when looking at the agenda, can we finalize coolbhavi's application or are votes still missing?
[17:21] <ari-tczew> +1 for geser
[17:21] <cjwatson> geser: I think we can, how about I look at that when I'm preparing the minutes?
[17:21] <bilalakhtar> +1 for cjwatson
[17:22] <geser> cjwatson: sure, thanks
[17:22] <JamesMR> +7 for me
[17:22] <stgraber> yeah, back on a decent keyboard !
[17:23] <bilalakhtar> My recent sponsorships, as I have mentioned, have been very much flawless, so I applied for MOTU
[17:24] <bilalakhtar> I have been involved with the papercuts project as well, with kenvandine and seb128 sponsoring my changes
[17:24]  * cjwatson is still reading
[17:24] <geser> bilalakhtar: I see that you would like to see REVU in more use again: how do you plan do deal with the problem that people vanish after they got their package into the archive and leave the further maintainance to MOTU?
[17:25] <bilalakhtar> geser: If I become MOTU, I would continue to fix bugs in packages, upgrade it from upstream, etc
[17:25] <geser> bilalakhtar: for all packages you advocated on REVU?
[17:26] <bilalakhtar> geser: I would never leave a package alone. For example, package gnome-media-player in Ubuntu has one bug, which I am unable to understand. I asked the reporter for more info, pending
[17:26] <bilalakhtar> geser: I would subscribe to bug mail, add 'em to a list and keep updating/asking the uploader for upgrades
[17:27] <bilalakhtar> ''em' above refers to packages
[17:27] <geser> and if the uploader vanishes/doesn't respond?
[17:27] <bilalakhtar> geser: then do it myself
[17:27]  * geser is impressed
[17:27] <bilalakhtar> as I said, I usually don't leave some work alone. I have been involved with upstream development of my package gnome-media-player as well
[17:27] <cjwatson> so, hm.  I think you're the youngest applicant I remember reviewing.  It's really good to see people get seriously involved earlier.  How do you find that Ubuntu work ties in with things like school commitments?
[17:27] <bilalakhtar> I have upgraded 3 packages in all
[17:27] <AnAnt> brb
[17:28] <bilalakhtar> cjwatson: my vacations are going on, and I am a lot free
[17:28] <bilalakhtar> I keep spreading Ubuntu in my school a lot
[17:28] <bilalakhtar> My computer lab has 3 computers running Ubuntu
[17:28] <bilalakhtar> and
[17:28] <bilalakhtar> almost the whole of my class has Ubuntu CDs
[17:29] <bilalakhtar> I distributed it to them
[17:29] <bilalakhtar> I will take breaks from developing only during exams for 2-3 weeks, that's all
[17:29] <nixternal> ahh to be young and energetic again :D
[17:29] <AnAnt> back
[17:30] <maco> nixternal: maybe if you stopped tiring yourself out on that bike, old man
[17:30]  * maco runs
[17:30] <bilalakhtar> My schools will reopen after 2 weeks, but I will keep developing at full speed for atleast another month, upto 3-4 more months, then a 2 week break, then full speed again!
[17:30] <JamesMR> bilalakhtar: what about revising for exams?
[17:30] <bilalakhtar> JamesMR: I can manage it myself
[17:30] <JamesMR> you'd surely need more than 2-3 weeks o.o
[17:30] <nixternal> maco: I am starting to feel older and a hell of a lot grumpier, almost like ScottK grumpier :p
[17:30] <bilalakhtar> I know python/PHP/C/C++/Java
[17:30] <bilalakhtar> oops, add HTML/CSS to the list
[17:31] <bilalakhtar> so I know quite a lot early and I can maintain MOTU if I become one, for atleast 6 years
[17:31] <bilalakhtar> and I aim to become a canonical employee :D
[17:31] <nixternal> bilalakhtar: thanks for taking care of krename. i usually do it since i love that app to death, but was gone during that time period. I see the good ol' KUBUNTU POT file crap caught you, glad I am not the only one that has been bitten by it
[17:31]  * zkriesse would like to add something to bilalakhtar's list of contributions
[17:31] <bilalakhtar> thanks nixternal
[17:32] <bilalakhtar> Well
[17:32] <bilalakhtar> no package can be called crap
[17:32] <nixternal> bilalakhtar: also with that one, i am supposed to maintain it in debian but never get around to it, so if it needs updating in debian, you could always update there and try to sync locally. at least that is what I used to do
[17:32] <bilalakhtar> Packages are cool
[17:32] <cjwatson> could somebody paste the logs from after "<bilalakhtar> I will take breaks from developing only during exams for 2-3 weeks, that's all"?  I lost connectivity
[17:32] <bilalakhtar> nixternal: definitely
[17:32] <cjwatson> (by /msg)
[17:33] <bilalakhtar> Anyone here going to give the logs to cjwatson or should I do?
[17:33] <cjwatson> thanks, got it
[17:33] <bilalakhtar> ah
[17:33] <bilalakhtar> I keep learning things all the time
[17:33] <stgraber> cjwatson: done
[17:33] <bilalakhtar> and I still remember VB, my first language
[17:33] <ari-tczew> cjwatson: http://paste.ubuntu.com/493726/
[17:33]  * maco shudders
[17:34] <bilalakhtar> I have always obeyed the Freezes, I requested and got an FF a month ago, though I was not goin to be the uploader of the package
[17:34] <cjwatson> exams> can't begrudge you that, certainly.  I was just looking at ari-tczew's comment that he felt your application was requested too quickly; I can see it either way, you've been involved at least a few months now and certainly over the bare minimum.  How would you reply to his comment?
[17:34] <bilalakhtar> hmm
[17:34] <bilalakhtar> well
[17:35] <bilalakhtar> there was a LOT of time between my first proper upload in Ubuntu and the beginning of my packaging work
[17:35] <bilalakhtar> I began with being the PPA maintainer of gnome-media-player
[17:35] <MichealH> Can I add something for bilalakhtar
[17:35] <bilalakhtar> then tried getting it into Ubutnu
[17:35] <bilalakhtar> *ubuntu
[17:35] <cjwatson> MichealH: certainly
[17:35] <bilalakhtar> then someone on #ubuntu-motu advised me it wa too late in the lucid cycle to get it into Ubuntu, so I tried it for maverick, and got it in
[17:36] <bilalakhtar> I have 5 new packages pending an upload in Debian
[17:36] <MichealH> He has been the one getting me intrested in bugs and packaging and has been a inspiration to me. I would definanly like to see him get +1's all round
[17:36] <MichealH> Because he has helped me on my Packaging/MOTU/bug journeyu
[17:36] <bilalakhtar> And sponsors on Debian have pointed out a few packaging mistakes there a few months ago, with a shared lib called liboauth
[17:36] <bilalakhtar> packaging shared libs sure needs a lot of knowledge, which I learnt
[17:36] <bilalakhtar> and
[17:37] <seb128> bilalakhtar has been doing nice work on some desktop bugs
[17:37] <bilalakhtar> so I know a lot about packaging, thanks to pabs in Debian and package liboauth!
[17:37] <seb128> (just adding a comment, I'm in another meeting as well)
[17:37] <cjwatson> I'm still ridiculously careful with shared library packaging ;-)
[17:37] <bilalakhtar> cjwatson: :)
[17:37] <maco> i just hope someone else does it :P
[17:37] <zkriesse> My name is Zach zkriesse on IRC, some of you may know me from somewhere around the 'Buntu realm. Currently I'm the lead for the Ubuntu Youth Team which bilalakhtar has just recently joined, and he's offered to come up with some packaging/dev tutorials for the newer/younger users to Ubuntu...he's doing a great job and I'd love to see him around...
[17:37] <nixternal> well, you can't get any better endorsement than one from seb128 :)
[17:37] <bilalakhtar> Thanks seb128 a lot!!
[17:38] <bilalakhtar> yup
[17:38] <bilalakhtar> zkriesse: thanks for mentioning that
[17:38] <nixternal> "I am 14 years old.  :O
[17:38] <bilalakhtar> I hate KDE for using, but I like its apps
[17:38] <bilalakhtar> nixternal: ^^
[17:38] <nixternal> just a bit
[17:39] <bilalakhtar> I prefer the KDE apps more than the DE
[17:39] <nixternal> $5 and I will look past that one :D
[17:39] <ari-tczew> about my comment: It's only my view, not negative comment.
[17:39] <bilalakhtar> Kate, KOffice, Dolphin, etc
[17:39]  * nixternal has no more questions
[17:39] <bilalakhtar> And I like the Qt toolkit a lot
[17:39] <cjwatson> ari-tczew: understood, just thought it worth exploring
[17:39]  * MichealH disappears again
[17:40] <ari-tczew> I'd keep bilalakhtar in work to show perfect packaging level. :)
[17:40] <cjwatson> ok, anything else before we move to a vote?
[17:40] <cjwatson> thanks to the cheerleading fraternity ;-)
[17:41] <bilalakhtar> As I have been in my recent work, I will surely try to make sure each one of my upload is perfect
[17:41] <bilalakhtar> I have been testing maverick since alpha 2
[17:41] <ari-tczew> btw. before close this topic, what about coolbhavi's case?
[17:42] <cjwatson> e-mail majority on coolbhavi was +1 with a review in (some months, I haven't collated the information yet)
[17:42] <bilalakhtar> I have also (indirectly) fixed a (major) bug  in maverick, lemme check for the bug number
[17:42] <bilalakhtar> bug #626723
[17:42] <cjwatson> ah yes, I saw that one, that was a good catch
[17:42] <bilalakhtar> I found out the fix, poked zul  and he fixed it
[17:42] <cjwatson> [VOTE] Bilal Akhtar for MOTU
[17:42] <MootBot> Please vote on:  Bilal Akhtar for MOTU.
[17:42] <MootBot> Public votes can be registered by saying +1/-1/+0 in the channel, private votes by messaging the channel followed by +1/-1/+0  to MootBot
[17:42] <MootBot> E.g. /msg MootBot +1 #ubuntu-meeting
[17:42] <nixternal> +1
[17:42] <MootBot> +1 received from nixternal. 1 for, 0 against. 0 have abstained. Count is now 1
[17:43] <cjwatson> +1
[17:43] <MootBot> +1 received from cjwatson. 2 for, 0 against. 0 have abstained. Count is now 2
[17:43] <stgraber> +1
[17:43] <MootBot> +1 received from stgraber. 3 for, 0 against. 0 have abstained. Count is now 3
[17:43] <geser> +1
[17:43] <MootBot> +1 received from geser. 4 for, 0 against. 0 have abstained. Count is now 4
[17:44] <cjwatson> [ENDVOTE]
[17:44] <MootBot> Final result is 4 for, 0 against. 0 abstained. Total: 4
[17:44] <cjwatson> bilalakhtar: welcome!
[17:44] <bilalakhtar> cjwatson: Thanks
[17:44] <bilalakhtar> THanks all!
[17:44] <bilalakhtar> geser, cjwatson , stgraber , nixternal , seb128 : All thanks!
[17:44] <ari-tczew> congrats bilalakhtar
[17:44] <bilalakhtar> Thanks ari-tczew !!!
[17:45] <geser> IIRC bilalakhtar beats wgrant in becoming the youngest MOTU by 2 years :)
[17:45] <nixternal> congrats and welcome bilalakhtar \o/
[17:45] <seb128> bilalakhtar, well done
[17:45] <ari-tczew> bilalakhtar: don't making mistakes :P
[17:45] <bilalakhtar> Thanks all!
[17:45] <nixternal> geser: wgrant and nhandler
[17:45] <cjwatson> if bilalakhtar is anywhere near as productive as wgrant, I'll be happy
[17:45]  * bilalakhtar will try to be
[17:45] <nixternal> wgrant is productive? when he isn't complaining about LP :p  he knows I love um!
[17:46] <cjwatson> "Set new meeting time and rotation", we did that
[17:46] <ari-tczew> geser: how old was wgrant when he applicated to motu?
[17:46] <geser> 16
[17:46] <cjwatson> AnAnt: still here?
[17:46] <AnAnt> cjwatson: yes
[17:47] <cjwatson> [TOPIC] PPU Application (sl-modem): Ahmed El-Mahmoudy
[17:47] <MootBot> New Topic:  PPU Application (sl-modem): Ahmed El-Mahmoudy
[17:47] <cjwatson> (sorry, my IRC client is not going to be able to manage to produce your name in the correct script)
[17:47] <AnAnt> no problem
[17:48] <AnAnt> ok, so as I've mentioned I've been maintaining sl-modem on Debian since about 2 years
[17:48] <AnAnt> and I sync back to Ubuntu
[17:48] <geser> AnAnt: no plans for the future? nothing you dislike in Ubuntu?
[17:49] <nixternal> geser: i think those were covered when AnAnt went for contrib dev and motu :p
[17:49] <geser> ah, ok then
[17:49] <nixternal> haha, i was just messing. surely things have changed since then
[17:50] <cjwatson> Emmet's comment is a pretty good summary here, and generally I have no issues giving the person obviously most involved with a package (in Debian and Ubuntu) the ability to upload it
[17:50] <nixternal> same here
[17:50]  * nixternal has no ?'s
[17:51] <AnAnt> geser: MOTU app has it
[17:51] <cjwatson> [VOTE] Ahmed El-Mahmoudy for per-package upload (sl-modem)
[17:51] <MootBot> Please vote on:  Ahmed El-Mahmoudy for per-package upload (sl-modem).
[17:51] <MootBot> Public votes can be registered by saying +1/-1/+0 in the channel, private votes by messaging the channel followed by +1/-1/+0  to MootBot
[17:51] <MootBot> E.g. /msg MootBot +1 #ubuntu-meeting
[17:51]  * geser forgot that AnAnt is already a MOTU
[17:51] <nixternal> +1
[17:51] <MootBot> +1 received from nixternal. 1 for, 0 against. 0 have abstained. Count is now 1
[17:51] <geser> +1
[17:51] <MootBot> +1 received from geser. 2 for, 0 against. 0 have abstained. Count is now 2
[17:51] <cjwatson> (if moving to a vote isn't premature)
[17:52] <cjwatson> +1
[17:52] <MootBot> +1 received from cjwatson. 3 for, 0 against. 0 have abstained. Count is now 3
[17:52] <stgraber> +1
[17:52] <MootBot> +1 received from stgraber. 4 for, 0 against. 0 have abstained. Count is now 4
[17:52] <cjwatson> [ENDVOTE]
[17:52] <MootBot> Final result is 4 for, 0 against. 0 abstained. Total: 4
[17:52] <cjwatson> excellent
[17:52] <AnAnt> thanks
[17:52] <nixternal> that was easy </staple's button push>
[17:53] <cjwatson> [TOPIC] Kernel package set application: Steve Conklin
[17:53] <MootBot> New Topic:  Kernel package set application: Steve Conklin
[17:53] <cjwatson> I gather the kernel meeting is in here right after this, so they have a reason to wait ;-)
[17:53] <sconklin> ;-)
[17:53] <JFo> :)
[17:53] <bjf> cjohnston: ack
[17:54] <cjwatson> sconklin: hi
[17:54] <sconklin> good whatever
[17:54] <nixternal> yeah, this shouldn't be that hard of an application
[17:54] <nixternal> I've appointed Steve as the next stable release manager beginning with the Natty Narwhal UDS.
[17:54] <nixternal> That assignment implies the level of confidence that I have in Steve's abilities as I consider the
[17:54] <cjwatson> so, I know Steve, maybe somebody else can do most of the interrog^Wquestioning :)
[17:55] <nixternal> maintenance of our existing kernels to be extremely important.
[17:55] <nixternal> ^^ from Tim
[17:55] <nixternal> I think that sums everything up right there
[17:56] <smb> And being the current one I get bored of checking uploads for Steve, not finding an issue and then just signing things. :-P
[17:56] <sconklin> aw shucks
[17:56] <nixternal> I would love to ask "any plans for working outside the kernel?" but I know how demanding that work is, and honestly I would rather have you spending your time there than outside somewhere else. without that kernel us outside would have nothing to do :)
[17:57] <sconklin> Actually I have the debian packaging of d-rats (initial packaging done) and am going to bug my sponsor for an upload today . . .
[17:57] <nixternal> lol
[17:57] <sconklin> userspace amateur radio app
[17:58] <cjwatson> I shall have to nobble you at some point about the whole business of switching smoothly from a VESA mode to a KMS mode, which, er, isn't so smooth right now ... but perhaps this meeting isn't the right place
[17:58] <sconklin> http://www.ai4qr.com/debian/
[17:58] <MootBot> LINK received:  http://www.ai4qr.com/debian/
[17:58] <nixternal> "I could do a better job of communicating what I'm doing to the community in general. A lot of things I work on are interesting, but I seldom take the time to blog about them or to use other social media to talk about what I'm doing."
[17:58] <sconklin> for my packaging on that
[17:59] <nixternal> ^^ that takes getting used to. though I have done exactly that in the past, only to get burned out trying to do it all the time
[17:59] <nixternal> now I just use social media to bitch and moan :)
[17:59] <sconklin> and cjwatson, that's a pretty involved discussion
[17:59] <cjwatson> indeed
[17:59] <stgraber> just wondering, are there any plan on improving the documentation on the kernel packaging magic ?
[17:59] <maco> nixternal: hmm you *are* turning into scottk...
[17:59] <nixternal> ScottK only wishes his grumpiness was as cool as mine
[18:00] <nixternal> i love talking about him when he isn't around, so much fun!
[18:00] <stgraber> I had to do it a couple of times (for custom kernel when working with some colleage on lttng) and it's usually hard to find it and not always accurate (especially the abi-check part of it)
[18:00]  * nixternal has no ?'s
[18:00] <sconklin> stgraber: it's an ongoing project for the kernel team to improve the wiki pages. But that's an area that still needs a lot of improvement
[18:00] <sconklin> there have been a lot of wiki improvements for the kernel during the M cycle
[18:01] <shadeslayer> nixternal: i think hes just lurking around the corner to pounce on you :P
[18:01] <cjwatson> any further questions?
[18:01] <tgardner> cjwatson, shall we vote? we're running into the next meeting.
[18:01] <cjwatson> my thought exactly
[18:02] <cjwatson> [VOTE] Steve Conklin for ubuntu-kernel-uploaders
[18:02]  * nixternal none
[18:02] <MootBot> Please vote on:  Steve Conklin for ubuntu-kernel-uploaders.
[18:02] <MootBot> Public votes can be registered by saying +1/-1/+0 in the channel, private votes by messaging the channel followed by +1/-1/+0  to MootBot
[18:02] <MootBot> E.g. /msg MootBot +1 #ubuntu-meeting
[18:02] <nixternal> +1
[18:02] <MootBot> +1 received from nixternal. 1 for, 0 against. 0 have abstained. Count is now 1
[18:02] <tgardner> +1
[18:02] <MootBot> +1 received from tgardner. 2 for, 0 against. 0 have abstained. Count is now 2
[18:02] <geser> +1
[18:02] <MootBot> +1 received from geser. 3 for, 0 against. 0 have abstained. Count is now 3
[18:02] <cjwatson> +1
[18:02] <MootBot> +1 received from cjwatson. 4 for, 0 against. 0 have abstained. Count is now 4
[18:02] <cjwatson> [ENDVOTE]
[18:02] <MootBot> Final result is 4 for, 0 against. 0 abstained. Total: 4
[18:02] <cjwatson> and just in time, that's the agenda as clear as we can get it given who's here
[18:02] <cjwatson> thanks everyone for your continued patience
[18:02] <cjwatson> #endmeeting
[18:02] <MootBot> Meeting finished at 12:02.
[18:02] <sconklin> Thank you all
[18:02] <lag> \o/
[18:02] <JFo> congrats sconklin!
[18:02] <geser> hmm, is 3 now quorum for DMB?
[18:02] <lag> Woooooooooooooooooooo sconklin
[18:02] <JFo> heh
[18:02] <apw> congrats sconklin
[18:02] <tgardner> cjwatson, thanks for chairing
[18:02] <ogasawara> sconklin: \o/
[18:03] <kamal> congrats sconklin!
[18:03] <cking> ditto
[18:03] <stgraber> +1 (btw)
[18:03] <smb> Yay for sconklin
[18:03] <tgardner> bjf, ok, on with the next meeting....
[18:03] <cjwatson> geser: no?  we had 4
[18:03] <stgraber> geser: +1
[18:03] <bjf> #startmeeting
[18:03] <MootBot> Meeting started at 12:03. The chair is bjf.
[18:03] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[18:03] <stgraber> cjwatson: tgardner voted, not me ;)
[18:03] <cjwatson> *blink*
[18:03] <nixternal> cjwatson: tgardner voted, not stgraber :D
[18:03] <cjwatson> I didn't see that
[18:03] <nixternal> that was funny!!!
[18:03] <bjf> [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting
[18:03] <bjf> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick
[18:03] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/Meeting
[18:03] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick
[18:03] <cjwatson> my bad, but fortunately it worked out
[18:03] <geser> cjwatson: if you replace tgarnder's vote with stgraber's one than it matches
[18:04] <bjf> #
[18:04] <bjf> # NOTE: '..' indicates that you are finished with your input.
[18:04] <bjf> #
[18:04] <cjwatson> must make mootbot smarter
[18:04] <sconklin> tgardner: you troublemaker
[18:04] <stgraber> cjwatson: we need LP-team support in mootbot ;)
[18:04] <tgardner> all in ignorance, I assure you
[18:04] <cjwatson> yeah yeah ;-)
[18:04] <bjf> [TOPIC] ARM Status (lag)
[18:04] <MootBot> New Topic:  ARM Status (lag)
[18:04] <lag>  * Marvel (mvl-dove)
[18:04] <lag>    * Nothing new this week
[18:04] <lag>  * Freescale (fsl-imx51)
[18:04] <lag>    * ON GOING : B605042: Java segfault on Freescale iMX5.1 Babbage board with Lucid - will try to bisect Lucid 2.6.31 kernel
[18:04] <lag>  * Texas Instruments (ti-omap)
[18:04] <lag>    * ON GOING : B591941 Original patch was not complete - Adrian Hunter should release the final patch this week.
[18:04] <lag>    * ON GOING : B608266 Fix submitted and accepted - still waiting for mobile team to test.
[18:04] <lag>    * ON GOING : B633227 ES2.0 board is unstable when highmem is enabled - backported a patch from upstream to solve memtester issue
[18:04] <lag>    * ON GOING : B628029 ES2.0 board does not boot with CONFIG_PM enabled
[18:04] <lag>    * NEW      : B622935 a patch has been written - author needs to send it upstream
[18:04] <lag>    * PATCH    : Lots of TI audio patches have now been applied - testing under way
[18:04] <lag>    * PATCH    : B563650 upstream patch was applied
[18:04] <lag>    * PATCH    : B477106 Lucid alpha-2 and earlier freeze upon suspend with sd card plugged in with some hardware
[18:05] <lag>    * PATCH    : B588243 upstream patch was applied
[18:05] <lag>    * FIXED    : B613855 omap3 beagle XM MMC card always comes up read-only
[18:05] <lag>    * FIXED    : B605488 scheduling while atomic: mmcqd/46/0x00000002
[18:05] <lag>    * FIXED    : B589624 omap flavour does not work on beagle XM board
[18:05] <lag>    * FIXED    : B605832 LG monitor behaving incorrectly when used in conjunction with the Panda board and HDMI
[18:05] <lag>    * FIXED    : B477106 Maverick alpha-2 and earlier freeze upon suspend with sd card plugged in with some hardware
[18:05] <lag>    * FIXED    : B592295 omapdss DISPC error: SYNC_LOST_DIGIT
[18:05] <lag>    * FIXED    : B628107 false alarm - first boot loaded unstable kernel
[18:05] <lag> ..
[18:05] <tgardner> lag, is yuor memtest solved with the cache line patch?
[18:06] <lag> It's not mine, but I don't believe that it is
[18:06] <tgardner> ok
[18:06] <tgardner> ..
[18:06] <lag> ..
[18:06] <bjf> [TOPIC] Release Metrics: (JFo)
[18:06] <MootBot> New Topic:  Release Metrics: (JFo)
[18:06] <JFo> Release Meeting Bugs (12 bugs, 9 Blueprints)
[18:06] <JFo> [18:06] <JFo>  * 1 linux kernel bugs (no change)
[18:06] <JFo>  * 0 linux-fsl-imx51 bugs (down 1)
[18:06] <JFo>  * 0 linux-ec2 bugs (no change)
[18:06] <JFo>  * 0 linux-mvl-dove bugs (no change)
[18:06] <JFo>  * 0 linux-ti-omap bugs (no change)
[18:06] <JFo>  * 0 linux-meta-ti-omap bug (no change)
[18:06] <JFo> [18:06] <JFo>  * 7 linux kernel bugs (down 5)
[18:06] <JFo>  * 1 linux-fsl-imx51 bugs (down 1)
[18:06] <JFo>  * 1 linux-ec2 bugs (no change)
[18:06] <JFo>  * 3 linux-mvl-dove bugs (no change)
[18:06] <JFo>  * 1 linux-ti-omap bugs (no change)
[18:06] <JFo>  * 0 linux-meta-ti-omap bug (no change)
[18:07] <JFo> [18:07] <JFo>  * 13 blueprints (Including HWE Blueprints)
[18:07] <JFo> [18:07] <JFo>  * [[https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.has_patch=on | Bugs with Patches]]
[18:07] <JFo>  * [[http://qa.ubuntu.com/reports/ogasawara/csv-stats/bugs-with-patches/linux/ | Breakdown by status]]
[18:07] <JFo> ..
[18:07] <bjf> [TOPIC] Blueprint: kernel-maverick-bug-handling (JFo)
[18:07] <bjf> [LINK] https://blueprints.edge.launchpad.net/ubuntu/+spec/kernel-maverick-bug-handling
[18:07] <MootBot> New Topic:  Blueprint: kernel-maverick-bug-handling (JFo)
[18:07] <MootBot> LINK received:  https://blueprints.edge.launchpad.net/ubuntu/+spec/kernel-maverick-bug-handling
[18:08] <JFo> nothing to report. I have been slack in my updates on it
[18:08] <JFo> will work it the rest of this week
[18:08] <JFo> ..
[18:08] <bjf> [TOPIC] Blueprint: kernel-maverick-bios-test-automation (cking)
[18:08] <bjf> [LINK] https://blueprints.edge.launchpad.net/ubuntu/+spec/kernel-maverick-bios-test-automation
[18:08] <MootBot> New Topic:  Blueprint: kernel-maverick-bios-test-automation (cking)
[18:08] <MootBot> LINK received:  https://blueprints.edge.launchpad.net/ubuntu/+spec/kernel-maverick-bios-test-automation
[18:08] <cking> Changes this week to fwts:
[18:08] <cking> * Updated USB boot image tests to use the ncurses based dialog interface
[18:08] <cking> * natty branch:
[18:08] <cking>     mtrr: test for SYSCFG[MtrrFixDramModEn], more intelligent mtrr testing
[18:08] <cking>     klog + acpi tests: check for single MADT
[18:08] <cking>     pci: check for _CRS PCI host bridge configuration
[18:08] <cking>     acpidump: annotated dump of ERST, SLIT, SRAT, SBST, ECDT, CPEP, BERT,
[18:08] <cking>         DSDT, SSDT, RSDT, XSDT
[18:08] <cking>     lib: hexdump
[18:08] <cking>     bios: romdump (dump BIOS + option ROMs)
[18:08] <cking>     framework: add --show-progress-dialog option for dialog tool
[18:08] <cking> ..
[18:09] <ogasawara> from a blueprint point of view, the fwts looks finished
[18:09] <bjf> this is dealing with a maverick blueprint but the status is natty related
[18:09] <bjf> ogasawara: ack
[18:09] <cking> oh, yes.
[18:09] <cking> it's finished for maverick
[18:09] <JFo> great work cking
[18:09] <ogasawara> bjf, cking: we can probably drop this from the weekly agenda
[18:09] <JFo> you inspire me
[18:09] <bjf> i'll drop this
[18:09] <cking> good idea
[18:09] <bjf> [TOPIC] Status: Maverick (ogasawara)
[18:09] <MootBot> New Topic:  Status: Maverick (ogasawara)
[18:10] <ogasawara> We've uploaded a new Maverick kernel, 2.6.35-21.31.  This was to resolve linux-libc-dev ti-omap4 version conflicts which prevented any armel uploads.
[18:10] <ogasawara> Kernel Freeze is this Thurs Sept 16th.  After Kernel Freeze, we transition to our SRU policy.  I plan to upload our final Maverick kernel Sept 17th.  There is little to no room for uploading any kernels beyond the 17th as the archive will freeze in preparation for Mavrick's 10.10 Release Candidate.  Any patches which have any hope of landing the the 10.10 Maverick kernel need to be submitted and garnered the appropriate
[18:10] <ogasawara> Ack's prior to the 16th.
[18:10] <ogasawara> We are again nearing being above the trend line for our overall burn down chart.  We need to start closing out all remaining open work items.
[18:10] <ogasawara> JFo, sconklin, apw, tgardner, jjohansen, smb: It appears you have open work items.  Please review if your work item(s) can be marked as DONE or POSTPONED, else get er done.
[18:10] <JFo> yep, will do
[18:10] <ogasawara> [LINK] http://people.canonical.com/~pitti/workitems/maverick/canonical-kernel-team.html
[18:10] <ogasawara> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick#Milestone ubuntu-10.10
[18:10] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/maverick/canonical-kernel-team.html
[18:10] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick#Milestone ubuntu-10.10
[18:11] <jjohansen> ogasawara: done, just waiting for security to sign off
[18:11] <smb> ack
[18:11]  * tgardner likes POSTPONED
[18:11] <ogasawara> ..
[18:11] <sconklin> wilco
[18:11] <bjf> [TOPIC] Security & bugfix kernels - Karmic/Jaunty/Intrepid/Hardy/Others (smb)
[18:11] <MootBot> New Topic:  Security & bugfix kernels - Karmic/Jaunty/Intrepid/Hardy/Others (smb)
[18:11] <smb> ||                   || Upd./Sec.     || Proposed      || TiP || Verified    ||
[18:12] <smb> || Dapper: Kernel    || 2.6.15-55.87  ||               ||     ||             ||
[18:12] <smb> || Hardy:  Kernel    || 2.6.24-28.77  || (pending)     ||     ||             ||
[18:12] <smb> || Jaunty: Kernel    || 2.6.28-19.64  ||               ||     ||             ||
[18:12] <smb> || Karmic: Kernel    || 2.6.31-22.63  || 2.6.31-22.64  ||  21 ||  0/ 4       ||
[18:12] <smb> || =       mvl-dove  || 2.6.31-214.30 || 2.6.31-214.31 ||  21 ||  0/ 4       ||
[18:12] <smb> || =       fsl-imx51 || 2.6.31-112.28 ||               ||     ||             ||
[18:12] <smb> || =       ec2       || 2.6.31-307.17 || 2.6.31-307.18 ||  21 ||  0/ 4       ||
[18:12] <smb> || Lucid:  Kernel    || 2.6.32-24.42  || 2.6.32-25.43  ||  13 ||  1/25 (+ 1) ||
[18:12] <smb> || =       LBM       || 2.6.32-24.17  || 2.6.32-25.22  ||  13 ||  0/ 4       ||
[18:12] <smb> || =       mvl-dove  || 2.6.32-209.25 || (pending)     ||     ||             ||
[18:12] <smb> || =       fsl-imx51 || 2.6.31-608.19 ||               ||     ||             ||
[18:12] <smb> || =       ti-omap   || 2.6.33-502.10 ||               ||     ||             ||
[18:12] <smb> || =       ec2       || 2.6.32-308.15 ||               ||     ||             ||
[18:12] <smb>  * There are very little to no verifications coming in for the Karmic and Lucid
[18:12] <smb>    proposed kernels. It looks like we need to start our own bug(them)-squad.
[18:12] <smb>  * Accepting packages into proposed also faces some delays as pitti was on
[18:12] <smb>    holiday and it feels like there is no real backup there.
[18:12] <smb>  * Karmic-fsl-imx51 sounds like being dead to me. We should probably make an
[18:12] <smb>    official announcement that we won't do any security updates on it anymore
[18:12] <smb>    and see whether anybody cries.
[18:12] <smb> ..
[18:13] <bjf> [TOPIC] Incoming Bugs: Regressions (JFo)
[18:13] <MootBot> New Topic:  Incoming Bugs: Regressions (JFo)
[18:13] <ogasawara> smb: if karmic-fsl-imx51 is indeed dead, that might automatically knock off one of your work items :)
[18:13] <smb> ogasawara, indeed. :)
[18:14] <JFo> 533 Maverick Bugs (up 85)
[18:14] <JFo> 1036 Lucid Bugs (up 39)
[18:14] <JFo> Current regression stats (broken down by release):
[18:14] <JFo> [18:14] <JFo>   * 272 maverick bugs (up 47)
[18:14] <JFo>   * 170 lucid bugs (up 4: to be converted to regression-release)
[18:14] <JFo> [18:14] <JFo>   * 47 lucid bugs (down 2)
[18:14] <JFo>   * 7 karmic bugs (no change)
[18:14] <JFo>   * 4 jaunty bugs (no change)
[18:14] <JFo>   * 0 hardy bugs (no change)
[18:14] <JFo> [18:14] <JFo>   * 181 lucid bugs (up 4)
[18:14] <JFo>   * 37 karmic bugs (no change)
[18:14] <JFo>   * 18 jaunty bugs (no change)
[18:14] <JFo>   * 3 hardy bugs (no change)
[18:14] <JFo> [18:14] <JFo>   * 7 lucid bugs (no change)
[18:14] <JFo>   * 1 karmic bug (no change)
[18:14] <JFo> We are in the stage now where we are getting almost 90 bugs a week for Maverick
[18:14] <JFo> ..
[18:14] <ogasawara> JFo: any updates about regression-potential tag going away?
[18:15] <JFo> ogasawara, yes, I need to take the regression potential tag out of the apport hok soon
[18:15] <JFo> hook*
[18:15] <JFo> will discuss with you after this
[18:15] <ogasawara> ack
[18:15] <JFo> other than that, I have an update on it coming up
[18:15] <JFo> in the triage bit. :)
[18:15] <JFo> ..
[18:16] <bjf> [TOPIC] Incoming Bugs: Bug day report (JFo)
[18:16] <MootBot> New Topic:  Incoming Bugs: Bug day report (JFo)
[18:16] <JFo> Next week's bug day will focus on the bugs with patches. We will be reviewing them to ensure that the attached is in fact a patch.
[18:16] <JFo> There will be a bug day by the community team to help us address the regression-potential and regression-proposed bugs per
[18:16] <JFo> our latest conversation on the subject. I don't have date/time information as yet, but I will provide that as I have it.
[18:16] <JFo> We will continue to have the Team Bug Day to address the Top 50 list as half days on Friday and Monday.
[18:16] <JFo> Reviewers, please take a look at your needs-review lists and help us keep the process moving.
[18:16] <JFo> Please also take ownership of your bugs as you work them so we can get them fixed or otherwise off the list.
[18:16] <JFo> There are several subsystems owned by all that need to be reviewed for inclusion in our top 50 list.
[18:16] <JFo> ..
[18:17] <tgardner> JFo, remember we'll all be in Taipei next Monday
[18:17] <bjf> JFo: many folks are going to be in taipei does that change your plans
[18:17] <bjf> ?
[18:17] <JFo> ah yes
[18:17] <JFo> yes, it does
[18:17] <JFo> so I'll postpone the bug day till the week after
[18:17]  * JFo makes a note
[18:18] <bjf> [TOPIC] Triage Status (JFo)
[18:18] <MootBot> New Topic:  Triage Status (JFo)
[18:18] <JFo> The Kernel Triage Summit was a success. I am thankful to all of you who were able to make yourselves available for the sessions. Thanks to sconklin, diwic, apw and ogasawara for holding the sessions. I'll be blogging about the event and making the transcripts and survey available to those who were unable to attend.
[18:19] <sconklin> Thanks JFO, I thought we got good participation
[18:19] <JFo> any input you'd like to make on the Summit?
[18:19] <JFo> sconklin, I did too
[18:19] <JFo> I was well pleased
[18:19] <apw> just that we should touch those people who attended and showed interest again
[18:19] <JFo> I agree
[18:19] <apw> to follow up with them, and get their feedback individually
[18:19] <apw> ..
[18:19] <JFo> I'll be going though the transcript to see who was involved and get back with them
[18:19] <ogasawara> and we should follow up that the info dispersed lands in a wiki page somewhere
[18:19] <JFo> yes
[18:20] <apw> there was some very good audio info in there we must not lose ..
[18:20] <JFo> I think that is the most important bit here
[18:20] <JFo> apw, definitely agree
[18:20] <JFo> ..
[18:21] <bjf> [TOPIC] Open Discussion or Questions: Raise your hand to be recognized (o/)
[18:21] <MootBot> New Topic:  Open Discussion or Questions: Raise your hand to be recognized (o/)
[18:21] <JFo> o/
[18:21] <kstailey> HPET + PAT = Oops (affects many systems) see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/563481/comments/34
[18:21] <bjf> JFo: go
[18:21] <JFo> As we will be in Taipei next week, I'd like to see about doing the bug chat on Thursday or friday if you all agree
[18:21] <JFo> .
[18:22] <JFo> since we have not had one for a few weeks
[18:22] <tgardner> JFo, get it on the calendar
[18:22] <JFo> will do
[18:22] <apw> JFo, works for me
[18:22] <JFo> apw, ack
[18:22] <smb> should work for me as well
[18:22] <JFo> ogasawara, sconklin smb that good for you guys?
[18:22] <JFo> smb, ack
[18:22] <ogasawara> JFo: should work for me
[18:22] <JFo> ogasawara, ack
[18:23] <JFo> ok, I'll schedule it up
[18:23] <sconklin> should work for me
[18:23] <JFo> rather Thursday than friday
[18:23] <JFo> sconklin, ack
[18:23] <JFo> ..
[18:23] <smb> JFo, sounds good
[18:23] <smb> ..
[18:23] <bjf> anything else?
[18:23] <kstailey> o/
[18:23] <bjf> kstailey: go
[18:23] <kstailey> HPET + PAT = Oops (affects many systems) see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/563481/comments/34
[18:23] <kstailey> please help test, thanks
[18:23] <kstailey> ..
[18:24] <ogasawara> kstailey: which release?
[18:24] <kstailey> > Jaunty
[18:24] <kstailey> in the past PAT was not enabled
[18:24] <ogasawara> kstailey: I assume there is a patch to fix it?  and if so is it upstream?
[18:25]  * apw wonders how long jaunty has for support remaining
[18:25] <tgardner> about a month
[18:25] <smb> not very long
[18:25] <kstailey> Karmic and Lucid
[18:25] <kstailey> ">" as in "greater than
[18:25] <kstailey> as in when PAT code was thrust upon the world
[18:25] <apw> yeah finally twigged that about 2s too late, ignore me pls
[18:26] <kstailey> go search on: ubunut nopat
[18:26] <kstailey> to see the impact
[18:27] <kstailey> er, ubuntu
[18:27] <apw> if there is an upstream patch then could you send the patch on to kernel-team@ list, then it'll get on the list for consideration
[18:27] <kstailey> try https://patchwork.kernel.org/patch/120327/
[18:27] <kstailey> no warrantees
[18:28] <bjf> anything else?
[18:28] <bjf> thanks everyone
[18:28] <bjf> #endmeeting
[18:28] <MootBot> Meeting finished at 12:28.
[18:28] <kamal> thanks bjf
[18:28] <JFo> thanks bjf
[18:28] <cking> thanks bjf
[18:28] <bjf> before everyone leaves!!!!
[18:29] <bjf> should we have a meeting at all next week?
[18:29]  * smb waits
[18:29] <JFo> kstailey, let's discuss what is needed to get this in front of the team in #ubuntu-kernel?
[18:29] <bjf> i'm thinking not
[18:29] <smb> +1
[18:29] <JFo> +1
[18:29] <tgardner> I'm thinking it'll be in the middle of my night
[18:29] <ogasawara> +1
[18:29] <bjf> are those votes for a meeting or against a meeting?
[18:29] <tgardner> its 0129 in Taipei right now
[18:30] <JFo> against
[18:30] <ogasawara> +1 for not having the meeting
[18:30] <cking> ditto
[18:30] <smb> against having one
[18:30] <bjf> ok, no meeting next week
[18:30] <bjf> that's all, thanks again
[18:30] <apw> bjf thanks
[18:30] <JFo> thanks bjf :)
[18:31] <apw> kstailey, do come join us on #ubuntu-kernel
[18:52] <zul> heylo
[18:52] <smoser> \0
[18:54] <Daviey> o/
[18:55] <mathiaz> /\~o/\_-+
[18:56] <hggdh> ~ô~
[18:58] <zul> .--. ..-.. ...
[18:59] <ttx> o-^-o
[18:59] <jiboumans> o/
[19:00] <hallyn> \o
[19:00] <sommer> o//
[19:00] <jiboumans> #startmeeting
[19:00] <MootBot> Meeting started at 13:00. The chair is jiboumans.
[19:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[19:00] <SpamapS> ._-=o/
[19:00]  * SpamapS is on fire
[19:00] <jiboumans> [TOPIC] Review ACTION points from previous meeting
[19:00] <MootBot> New Topic:  Review ACTION points from previous meeting
[19:00] <jiboumans> i'll be your scribe/chair for the day
[19:00] <kirkland> howdy
[19:00] <jiboumans> Daviey to contact upstream eucalyptus, regarding issues that seem to be blocked.
[19:00] <Daviey> done.. but a new issue arisen
[19:01] <jiboumans> do tell
[19:01] <Daviey> Hmm
[19:01] <Daviey> currently we are seeing a meta data service failure
[19:02] <Daviey> upstream have been notified by myself qand hggdh
[19:02] <Daviey> I have a trivial patch that seems to restore functinaility
[19:02] <Daviey> but really want upstream to dicuss it
[19:02] <jiboumans> ok, that's bug 637659
[19:02] <jiboumans> gotcha
[19:02] <Daviey> yes!
[19:02] <jiboumans> alright, let's move on then
[19:02] <jiboumans> jjohansen to follow up on bug 574910 with the current direction
[19:03] <jjohansen> jiboumans: added some comments, I haven't nailed down any specific load averages
[19:03] <jiboumans> so what are we doing right now?
[19:04] <jjohansen> jiboumans: basically we need to search down every problem that could be causing high load averages
[19:04] <jjohansen> there are a few known already
[19:04] <jjohansen> the write back patches are in proposed.
[19:05] <jjohansen> The high number of wakeups, is not properly address and last I saw still being examined upstream
[19:05] <jjohansen> but there is something else going on too, and I haven't been able to replicate
[19:06] <jiboumans> understood
[19:06] <jiboumans> moving on: jjohansen and smoser to report on bug 613083 bug 606373 and next meeting
[19:07] <jiboumans> kernel upgrade in the cloud bugs
[19:07] <jjohansen> 613083 has progress but we are not sure when the fix will hit
[19:07] <smoser> Amazon is looking into it.  Last i was aware, there were 2 bugs, one of them fixed on their side.  They indicated that no changes would be necessary in our kernels.
[19:07] <jiboumans> are tehy both on amazon?
[19:07] <jjohansen> yes
[19:07] <smoser> yes
[19:08] <jjohansen> 606373 I thought I had a working fix, but smoser is reporting it doesn't work for him and we haven't had a chance to compare yet
[19:08] <jiboumans> ok, so best we can do is track and provide information i suppose
[19:08] <smoser> bug 606373
[19:09] <smoser> jiboumans, yes. for 613083, we should have nothing to do.  I have reasonable confidence that it will be fixed.
[19:09] <jiboumans> sounds like we've done what we can from our side
[19:09] <jiboumans> moving on
[19:09] <jiboumans> sommer and mathiaz to sync up regarding puppet server guide
[19:10] <mathiaz> jiboumans: I haven't had to review the puppet section
[19:10] <mathiaz> jiboumans: it seems that it landed though
[19:10] <sommer> it's pretty simple so shouldn't take too long :)
[19:10] <mathiaz> sommer: ok - I'll give it a look
[19:10] <sommer> mathiaz: thanks I appreciate it
[19:10] <jiboumans> [ACTION] mathias to review puppet server guide entry
[19:10] <MootBot> ACTION received:  mathias to review puppet server guide entry
[19:11] <jiboumans> RoAkSoAx to email ubuntu server mailing list with update of cluster stack progress
[19:11] <RoAkSoAx> o/
[19:12]  * jiboumans waits for roaksoax
[19:12] <RoAkSoAx> well unfortunately I didn't email because we've been working on getting the packages done and I wanted to provide an update after the work was done given that right after last meeting we received further input on our issues that kinda helped us on see how to resolves our issues
[19:13] <jiboumans> roaksoax: so what's the current status?
[19:13]  * jiboumans also notes it's finalfreeze on thursday
[19:13] <RoAkSoAx> jiboumans: packages should be in shape to hit main before final freeze. ivoks has to do a final upload with the fixes
[19:14] <RoAkSoAx> final fixes
[19:14] <RoAkSoAx> hoefully for today
[19:14] <jiboumans> [ACTION] roaksoax to announce updated cluster packages when they land, ETA before finalfreeze
[19:14] <MootBot> ACTION received:  roaksoax to announce updated cluster packages when they land, ETA before finalfreeze
[19:14] <ttx> RoAkSoAx: on the release front it's tracked through bug 635884
[19:14] <RoAkSoAx> indeed
[19:14] <jiboumans> [TOPIC] Maverick develoment
[19:14] <MootBot> New Topic:  Maverick develoment
[19:15] <jiboumans> all quiet on the western front; most development items are now around process, documentation, etc. most of our time is spent on testing, bug fixing & stabilization
[19:15] <jiboumans> work item tracker looks all good from here and no real items left on the critical path
[19:15] <jiboumans> i'll hand over to ttx for the release critical issues
[19:15] <SpamapS> jiboumans: burnup is fixed btw. ;)
[19:15] <ttx> https://wiki.ubuntu.com/ServerTeam/MaverickReleaseStatus is almost up to date, smoser sneakily fixed bug 623609 15 minutes before the meeting
[19:15] <jiboumans> spamaps++
[19:16] <smoser> it was fixed monday. silly launchpad just didn't know it.
[19:16] <ttx> right, is silly LP fixed now ?
[19:16] <ttx> silly LP did not close the bugs automatically anymore.
[19:17] <ttx> on Daviey's plate we have:
[19:17] <Daviey> :(
[19:17] <ttx> Bug 617053
[19:17] <ttx> Bug 637659
[19:17] <ttx> I think both are clsoe to get a fix
[19:17] <Daviey> (both would benefit from upstream reading)
[19:17] <ttx> 2 new bugs have been assigned to JamesPage, I'll review and sponsor the proposed fixes
[19:18] <Daviey> both seem to be fixed in bzr.. but waiting for them
[19:18] <ttx> the redhat-cluster one we already mentioned
[19:18] <ttx> that leaves Bug 632696, I'll sync with jdstrand later today
[19:19] <ttx> On the Other Critical/High Maverick bugs list, the only one with concern is, I think;
[19:19] <ttx> Bug 582963
[19:19] <jdstrand> ttx: hallyn mentioned he is tracking that down more since only he can reproduce it atm
[19:19] <ttx> jdstrand: ok
[19:19] <hallyn> i think it needs to be 'invalid' again, haven't reproduced it since
[19:20]  * hallyn wonders if there's an fd leak...
[19:20] <ttx> that passphrase bug is slightly complex since it's an interaction/plymouth thing, and we broke things last time we tried to fix it
[19:21] <ttx> zul: could you ask someone more knowledgeable on upstart how we could fix that, and if it's safe to do before release ?
[19:21] <zul> ttx: ack
[19:21] <cjwatson> ttx: LP fix is in progress, but in the meantime bugs need to be closed manually
[19:21] <jdstrand> hallyn: it wouldn't be the first time
[19:21] <ttx> cjwatson: thx for the update
[19:21] <ttx> Bug 628055 - i'll reproduce it before throwing it to Daviey again
[19:22] <ttx> Once you are done with those, please feel free to pick bugs in the last list
[19:22] <ttx> we haven't had that many extra bugs fixed over the last week :)
[19:22] <jiboumans> ttx: are we ready to move on?
[19:22] <ttx> yes
[19:23] <jiboumans> [TOPIC] Weekly Updates & Questions for the QA Team (hggdh)
[19:23] <MootBot> New Topic:  Weekly Updates & Questions for the QA Team (hggdh)
[19:23] <hggdh> life is good, with Eucalyptus swallowing all my time ;-)
[19:23] <hggdh> apart from that -- expect an email to -devel describing the changes we want to make on the regression-* tags
[19:24]  * SpamapS likes the simplification
[19:24] <hggdh> we propose to drop regression-potential, since it is pretty much only giving us more work
[19:24] <hggdh> but details later
[19:25]  * hggdh is done
[19:25]  * jiboumans waits 5 more seconds for questions
[19:25] <jiboumans> [TOPIC] Weekly Updates & Questions for the Kernel Team (jjohansen)
[19:25] <MootBot> New Topic:  Weekly Updates & Questions for the Kernel Team (jjohansen)
[19:25] <jiboumans> looks like we covered the first two already
[19:25] <jiboumans> but not yet: Bug 621175 - -virtual kernel contains too many modules
[19:26] <jjohansen> should be fixed
[19:26] <ttx> jjohansen: was reopened recently, was it re-fixed ?
[19:26] <smoser> its reported to be re-fixed.
[19:26] <jjohansen> ah no, I hadn't noticed
[19:26] <smoser> a permissions on a maintainance script that would do the module filtering
[19:27] <jjohansen> I'll check, and if it is still broken refix
[19:27] <jiboumans> jjohansen: anything else from the kernel front?
[19:27] <jjohansen> yeah, just a sec
[19:28] <jjohansen> Bug #634316
[19:28] <jjohansen> I am planning on recommending this patch unless anyone has issues with it
[19:28] <jiboumans> ebs performance on ubuntu is something that's been lamented before
[19:29] <jiboumans> so if we have a fix, that'd be a good thing
[19:29] <jiboumans> jjohansen: can we get that one on lucid?
[19:29] <jjohansen> well it does come with risk as it hasn't been well tested by us
[19:29] <jjohansen> no
[19:30] <jiboumans> smoser: do we have ebs/fs regression tests for amis?
[19:30] <jjohansen> its against the pv-ops driver not the full xen
[19:30] <smoser> we test ebs boot and general worked-ness.
[19:30] <smoser> not extensive disk test, though
[19:31] <jiboumans> i'd like to give it a shot jjohansen
[19:31] <jjohansen> okay, I will submit today
[19:33] <jiboumans> anything else from kernel?
[19:33] <jjohansen> not atm
[19:34] <jiboumans> thanks jjohansen
[19:34] <jiboumans> [TOPIC] Weekly Updates & Questions for the Documentation Team (sommer)
[19:34] <MootBot> New Topic:  Weekly Updates & Questions for the Documentation Team (sommer)
[19:36] <jiboumans> no updates from sommer?
[19:36] <sommer> things are good
[19:36] <sommer> string freeze is in effect, and I feel good about the maverick guide :-)
[19:36] <jiboumans> sommer: ok, all sections (bar the puppet one) are getting review?
[19:36] <jiboumans> excellent
[19:37] <jiboumans> no kim0, so skipping 'Weekly Updates & Questions for the Ubuntu Community Team (kim0)'
[19:37] <mathiaz> jiboumans: puppet review has actually been done :)
[19:37] <jiboumans> mathiaz++
[19:37] <jiboumans> multitasker
[19:37] <sommer> heh, just had that typed, thanks all for your help and feedback
[19:37] <SpamapS> jiboumans: maybe we should remove that section from the agenda.. thats about 4 meetings in a row with no attendance by kim0.
[19:37] <jiboumans> spamaps: point.. action for me to follow up with him
[19:37] <ttx> multitasker, or kernel questions skipper :P
[19:37] <jiboumans> [ACTION] jib to check with kim0 if he can attend meetings regularly ro not
[19:37] <MootBot> ACTION received:  jib to check with kim0 if he can attend meetings regularly ro not
[19:38] <jiboumans> alright
[19:38] <jiboumans> [TOPIC] Open discussion
[19:38] <MootBot> New Topic:  Open discussion
[19:38] <mathiaz> o/
[19:38] <mathiaz> one of the remaining item on the hadoop spec is whether the hadoop package currently in maverick should be dropped from the archive
[19:39] <mathiaz> I've focused on testing the cloudera packages from archive.cloudera.com
[19:39] <mathiaz> and the hadoop packages currently in maverick are not feature complete
[19:39] <mathiaz> I'd like to get your input on whether it makes sense to drop the current hadoop packages from maverick?
[19:39] <jiboumans> as the debian maintainer also not recommended them for production use, i'd be inclined to not have them show up
[19:39] <ttx> mathiaz: makes sense to drop the universe hadoop packages, but only if the cloudera ones can easily be found
[19:40] <SpamapS> mathiaz: we should collaborate on a session at UDS for this, I think we need to formalize the conduits, and put a policy in place for this exact sort of thing.
[19:40] <ttx> I'm not sure making hadoop disappear will help anyone. Removing it to make the others more easily found, yes
[19:40] <mathiaz> ttx: well - it's complicated to define "easily found"
[19:40] <ttx> mathiaz: I think we defined it as "apt-cache search finds it"
[19:40] <jiboumans> mathiaz: place holder package?
[19:41] <jiboumans> our 'hadoop' instead of debians
[19:41] <ttx> jiboumans: wasn't that your definition ?
[19:41] <jiboumans> ttx: yeah, that's my goal
[19:41] <jiboumans> but right now, the 'hadoop' in maverick is not one the maintainer even recommends you install
[19:41] <SpamapS> +1 for having something in apt-cache search that shows hadoop
[19:41] <mathiaz> would a place holder package be accepted given the current release cycle?
[19:41] <SpamapS> -1 for having it be broken
[19:41] <mathiaz> it would be a new empty package
[19:42] <mathiaz> ttx: should I discuss that with the release team
[19:42] <mathiaz> ttx: ?
[19:42] <Daviey> pursue FFe :)
[19:42] <SpamapS> postinst would be  'echo Please see http://xxx for info on running hadoop'
[19:42] <ttx> mathiaz: yes, we cna discuss that with skaet
[19:43] <ttx> mathiaz: I'm not sure what's the less worse solution here
[19:43] <Daviey> "less worse" :)
[19:43] <ttx> I'm just unconvinced by the "remove package" solution
[19:43] <mathiaz> ttx: ok - we shoudl discuss that with the release team then
[19:43] <SpamapS> Daviey: its more better than less worser
[19:43] <ttx> mathiaz: pick a moment when I'm around
[19:43] <mathiaz> ttx: remove + placeholder package would work for you?
[19:44] <ttx> mathiaz: yes
[19:44] <jiboumans> as would for me
[19:44] <mathiaz> ok - great
[19:44] <mathiaz> that's all for me
[19:44] <jiboumans> any other topics?
[19:44] <SpamapS> one
[19:44] <SpamapS> Related to that
[19:44] <ttx> SpamapS: if that's not too orthogonal with the effort you want to push for next cycle
[19:44] <SpamapS> I have stopped updating the Cassandra Ubuntu PPA that I created
[19:44] <SpamapS> There has been zero interest from the community.
[19:45]  * ttx mentions there has been zero interest from upstream in the Terracotta PPA, fwiw
[19:45] <SpamapS> i think until we have packages *in the release* that help you find the conduit/ppa/whatever .. the community will continue to google for it, find upstream's instructions, and ignore any packaging options
[19:46] <SpamapS> Unless we want to attack SEO for "Cassandra Ubuntu" or "Terracotta Ubuntu", then yes, the empty package w/ a pointer to our current status for whatever package we're addressing there, is probably the way to go.
[19:47] <SpamapS> My only reluctance would be if it has any reverse dependencies
[19:47] <ttx> SpamapS: one single package pointing to all of them, or one per project ?
[19:47] <SpamapS> As they'll break horribly.
[19:47] <SpamapS> ttx: one per project.
[19:47] <ttx> SpamapS: ok, then mathiaz's empty package can be reused in Natty
[19:47] <jiboumans> i think this is something we can take off line
[19:48] <SpamapS> Agreed
[19:48] <jiboumans> any other topics?
[19:48] <SpamapS> but suffice to say, the cassandra ubuntu PPA is dead unless somebody picks it up.
[19:48] <jiboumans> going once...
[19:48] <ttx> SpamapS: didn't you sign with your blood to maintain it forever ?
[19:48] <mathiaz> SpamapS: you may wanna delete it then
[19:48] <jiboumans> [TOPIC] Announce next meeting date and time
[19:48] <MootBot> New Topic:  Announce next meeting date and time
[19:48] <jiboumans> Tuesday 2010-09-21 at 1800 UTC - #ubuntu-meeting
[19:49] <jiboumans> #endmeeting
[19:49] <MootBot> Meeting finished at 13:49.
[19:49] <SpamapS> mathiaz: I'll email the cassandra users list before doing that.
[19:49] <ttx> SpamapS: I'd keep it and advertise it with whatever empty-package solution we find for natty
[19:49] <ttx> maybe it will gain momentum...