[14:04] <maco> meeting?
[14:04] <stgraber> bdrung, cody-somerville, persia, Laney: ping
[14:04] <Laney> \o
[14:06] <stgraber> hmm, let's hope someone else shows up
[14:09] <RoAkSoAx> o/
[14:09] <stgraber> hey RoAkSoAx. Waiting for another DMB member to show up so we have quorum.
[14:09] <RoAkSoAx> stgraber: alright!
[14:09] <RoAkSoAx> thanks
[14:10] <stgraber> (as we don't have any non-voting agenda item to discuss)
[14:10] <Laney> I'd like to annihilate all mention of universe-contributor and call it 'contributing developer' everywhere :-)
[14:10] <Laney> that is my one non-agenda wish
[14:11] <stgraber> Laney: about that, would there be any (known) problem with renaming the team?
[14:12] <Laney> not sure anything would depend on it
[14:12] <Laney> besides potentially documentation
[14:16] <ScottK> I'm not sure it's universally appropriate.
[14:17] <ScottK> For Kubuntu, Kubuntu Council will process people for Kubuntu (and transitively Ubuntu) membership based on packaging work.
[14:18] <Laney> people are still encouraged to approach the most specific council
[14:18] <Laney> universe contributor is misleading as that is not what we are looking for really
[14:19] <ScottK> As long as it's clear about most specific council, I think that's fine.
[14:30] <stgraber> hey geser!
[14:30]  * geser waves
[14:31] <stgraber> ok, we have quorum now, let's start
[14:31] <RoAkSoAx> YaY!!
[14:31] <stgraber> #startmeeting
[14:31] <MootBot> Meeting started at 08:31. The chair is stgraber.
[14:31] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[14:31] <stgraber> [TOPIC] PerPackageUploader Applications: Rosen Diankov
[14:31] <MootBot> New Topic:  PerPackageUploader Applications: Rosen Diankov
[14:32] <rdiankov> present!
[14:32] <stgraber> hi rdiankov
[14:32] <stgraber> can you introduce yourself quickly?
[14:32] <rdiankov> sure
[14:32] <rdiankov> i'm roboticist
[14:33] <rdiankov> in other words, working on AI problems involving perception and motion of machines
[14:33] <rdiankov> i'm also the developer of a openrave: the open robotics automation virtual environment
[14:33] <rdiankov> which is becoming very popular in the robotics community
[14:33] <rdiankov> because i'm primarily using ubuntu
[14:33] <rdiankov> and a lot of robotics guys are starting to use ubuntu
[14:34] <rdiankov> we would like to start offering these types of robotics packages
[14:34] <rdiankov> through the official venues
[14:34] <rdiankov> hence my application
[14:35] <rdiankov> there are also file format libraries like collada and assimp
[14:35] <rdiankov> which would be also great to get into ubuntu
[14:35] <geser> do any packages for openrave exist already?
[14:35] <stgraber> doh, geser was faster ;)
[14:36] <rdiankov> yes
[14:36] <rdiankov> https://launchpad.net/~openrave/+archive/release
[14:36] <rdiankov> i started a ppa
[14:36] <rdiankov> basically every ubuntu release cycle
[14:36] <stgraber> are any of these already in Ubuntu or Debian?
[14:36] <rdiankov> no
[14:37] <rdiankov> every ubuntu release cycle, it would be great if these packages are copied
[14:37] <rdiankov> and put into universe
[14:37] <rdiankov> or multiverse
[14:37] <rdiankov> because there are no dependencies on these packages
[14:38] <rdiankov> it shouldn't affect anything
[14:38] <stgraber> ok, the main problem here is that we can't give upload rights to packages that don't exist in Ubuntu. Once they are in the repository (through sponsoring by an existing ubuntu developer), we can then process applications for upload rights.
[14:39] <rdiankov> ok, how can we fine someone to sponsor them?
[14:39] <rdiankov> find*
[14:39] <stgraber> https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages is the process for new packages
[14:39] <stgraber> #ubuntu-motu usually has people around to help review the packages and once they are happy with them, upload them for you
[14:40] <rdiankov> file a bug report in launchpad?
[14:40] <stgraber> they then will be reviewed by the archive admins and once they are happy with them, they'll be in Ubuntu. When that's done, you can then request Per-Package-Upload rights to them.
[14:41] <stgraber> yep, you'll need a needs-packaging bug per package, your changelog entry will need to close that bug (LP:#xxxxxx)
[14:41] <rdiankov> ok, got it guys
[14:41] <rdiankov> thanks!
[14:42] <stgraber> no problem!
[14:42] <stgraber> hope to see you apply again soon!
[14:42] <stgraber> [TOPIC]
[14:42] <MootBot> New Topic:
[14:42] <rdiankov> of course!
[14:42] <stgraber> oops (copy/paste issue)
[14:42] <geser> and don't forget your sponsor to add endorsements to your application
[14:42] <stgraber> [TOPIC] Ubuntu Contributing Developer Applications: Ricardo Salveti
[14:42] <MootBot> New Topic:  Ubuntu Contributing Developer Applications: Ricardo Salveti
[14:43] <stgraber> hey rsalveti
[14:43] <rsalveti> hey!
[14:43] <rsalveti> I'm here today :-)
[14:43] <stgraber> hehe
[14:43] <stgraber> can you introduce yourself quickly?
[14:44] <rsalveti> Hi, I'm Ricardo Salveti, currently working mostly with Ubuntu on ARM. I'm deeply involved with Ubuntu development for about one year now, working helping maintaining x-loader, u-boot, omap kernel and some other cool packages for ARM :-)
[14:44] <rsalveti> I've being working with OSS for quite a while now, doing contributions in a large set of software, and as a distro developer I also worked for a while with OpenEmbedded and the debian based distro called Mamona (now basically dead).
[14:44] <rsalveti> Usually around #ubuntu-arm, trying to help people getting the most we can from our ARM images, by helping with bugfixing and adding hw support (kernel, x-loader, etc).
[14:45] <rsalveti> I applied for universe contributor but soon should also be applying for a dev role, like core-dev, just need to find time to prepare my application :-)
[14:46] <ScottK> rsalveti: How is your script for automatic FTBFS bug filing going?  I'm sure you recall our discussion on it?
[14:46] <Laney> oh, whoops, didn't noticed we'd started :P
[14:47] <rsalveti> ScottK: sure, I'm currently improving svammel to have a interactive step, so I can go over the FTBFS first before opening a bug
[14:47] <ScottK> That's good to hear.
[14:47] <rsalveti> I should be helping going over at least the FTBFS list for arm
[14:47] <rsalveti> only interested at the moment in arm specific build failures, as we can use more workforce from Linaro to help us fixing them
[14:50] <stgraber> in your "What I like least in Ubuntu", you mention our SRU process. I understand that the kernel team has a different SRU process (with a release every 3 weeks IIRC) but do you see a similar issue with non-kernel packages?
[14:51] <stgraber> In my experience, the SRU process improved a lot lately and I can usually get something fixed into -updates in a week (from getting the fix, uploading to -proposed, get it accepted, get it tested and then copied to -updates)
[14:51] <rsalveti> Yes, my feeling is that in general once a release is out, nobody actually cares a lot about them
[14:51] <rsalveti> so SRU ends up taking a lot of time
[14:51] <rsalveti> in the past (maverick) I had some issues with the kernel SRU in specific
[14:52] <rsalveti> that took almost 2 months to deliver the fix
[14:52] <rsalveti> and asking testing for more than one time, when they released another version that contained the fix
[14:53] <stgraber> was your (non-kernel) experience with a bug having a patch applied, taking long to get uploaded or in a case where the package got uploaded to -proposed and took a long time to get to -updates ?
[14:53] <rsalveti> my complain was both the time to get sponsored and also to hit -updates
[14:54] <rsalveti> I know it's a lot of work to keep the SRU in places, but sometimes we have issues that really affects the user
[14:54] <stgraber> was that before the patch pilot program got introduced?
[14:54] <stgraber> (trying to see if we're missing something on the sponsorship lists)
[14:55] <rsalveti> for bug 707794 (my latest work with an SRU) it took 10 days to get sponsored
[14:55] <rsalveti> against the pyside package
[14:55] <rsalveti> I belive this case is enough
[14:55] <rsalveti> I mean, the time it took
[14:56] <ScottK> Unfortunately that package takes forever to build on armel and not many potential sponsors have the hardware to test.
[14:56] <rsalveti> yeah, hopefully to get sorted with the panda build cluster
[14:57] <rsalveti> now one kernel example
[14:57] <rsalveti> bug 770679
[14:58] <rsalveti> pull request, and SRU request sent at May 18
[14:58] <rsalveti> it's fixed commited already
[14:58] <rsalveti> and it basically breaks support for beagle rev C
[14:58] <rsalveti> so at least for people using that hardware it's somehow critical
[14:59] <rsalveti> and the fix will only hits update in probably one month from now
[15:00] <rsalveti> but maybe something to bring directly with the kernel team :-)
[15:00] <stgraber> yeah, kernel SRUs tend to take a lot longer, not sure what can be done to improve the delay and still keep the same QA standards
[15:00] <stgraber> yep, if you have an idea of how to improve the delay, you probably should start a discussion on their ML or at next UDS
[15:00] <stgraber> anyway, any other question for rsalveti?
[15:00] <rsalveti> yup, will think better
[15:01] <Laney> none here
[15:01] <stgraber> maco, geser, Laney: ?
[15:01] <maco> no
[15:02] <geser> no
[15:02] <stgraber> [VOTE] Ubuntu Contributing Developer membership for Ricardo Salveti
[15:02] <MootBot> Please vote on:  Ubuntu Contributing Developer membership for Ricardo Salveti.
[15: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
[15:02] <MootBot> E.g. /msg MootBot +1 #ubuntu-meeting
[15:02] <Laney> +1
[15:02] <MootBot> +1 received from Laney. 1 for, 0 against. 0 have abstained. Count is now 1
[15:02] <stgraber> +1
[15:02] <MootBot> +1 received from stgraber. 2 for, 0 against. 0 have abstained. Count is now 2
[15:02] <geser> +1
[15:02] <MootBot> +1 received from geser. 3 for, 0 against. 0 have abstained. Count is now 3
[15:02] <maco> +1
[15:02] <MootBot> +1 received from maco. 4 for, 0 against. 0 have abstained. Count is now 4
[15:03] <stgraber> #endvote
[15:03] <stgraber> [ENDVOTE]
[15:03] <MootBot> Final result is 4 for, 0 against. 0 abstained. Total: 4
[15:03]  * stgraber just found MootBot's man page again :)
[15:03] <stgraber> congrats rsalveti!
[15:03] <Laney> \o/
[15:03] <rsalveti> thanks! should be back in some weeks for a dev role ;-)
[15:04] <rsalveti> we'll see :-)
[15:04] <stgraber> geser, maco, Laney: still going to be around for a few more minutes (so we can process RoAkSoAx's coredev application)?
[15:04] <maco> sure
[15:04] <Laney> yep if there's no conflict for the room
[15:04] <stgraber> according to the fridge, the room isn't used
[15:05] <stgraber> geser: also fine with you?
[15:05] <geser> yes, I've around 30 min
[15:05] <stgraber> cool
[15:05] <RoAkSoAx> YaY!
[15:05] <stgraber> [TOPIC] Ubuntu Core Developer Applications: RoAkSoAx
[15:05] <MootBot> New Topic:  Ubuntu Core Developer Applications: RoAkSoAx
[15:05] <RoAkSoAx> Hi All!
[15:05] <stgraber> hey RoAkSoAx!
[15:05] <RoAkSoAx> My name is Andres Rodriguez, I've been involved with the community for quite a while now. I started as a translator then moved to development. I've been a MOTU for almost two years now. Throughout my work as a MOTU I've done things from simple syncs/merges all the way to package/library splits (I've done MIR reports, SRU's, packaged from scratch, bug fixing, python transitions, FTBFS, etc, etc).
[15:05] <RoAkSoAx> Within packaging, python packaging is what I enjoy the most, though I don't really have any problems with working with any type of packages. There's always something new to learn.
[15:05] <RoAkSoAx> I'm also the upstream maintainer of PowerNap (in main) and TestDrive. I  also currently maintain the Ubuntu HA Cluster Stack which include several packages currently in Main, which I got into Main last release cycle after various attempts of doing so. Currently I also work (mainly) on server related stuff that has spawned doing some work accross varios Ubuntu Server packages, both as a community member, as lately for work.
[15:06] <RoAkSoAx> and that's pretty much about it
[15:07] <RoAkSoAx> s/as/and/
[15:07] <Laney> So you say that you dislike delays in sponsorship... do you plan on making this situation better by devoting some of your time to doing sponsoring? :-)
[15:07] <RoAkSoAx> Laney: sure! it is not that I dislike delays in sponsoring, but rather I believe we need to improve it
[15:07] <RoAkSoAx> (myself included)
[15:07] <RoAkSoAx> as sometimes I've found myself having packages sitting there for days
[15:08] <RoAkSoAx> sometimes resulting on some other developer doing the merge for e.g., not noticing there was a merge report already filed in
[15:08] <RoAkSoAx> so that's work lost
[15:08] <RoAkSoAx> but yes, I do believe we need to improve
[15:09] <RoAkSoAx> it has been hugelyu improved with patch pilot but sometimes some types of packages are not touched
[15:09] <RoAkSoAx> and I can't have my co-workers sponsor for me all the time
[15:09] <RoAkSoAx> as they also have other stuff to work on
[15:09] <RoAkSoAx> and yes, It is something that I also blame myself as I havent done much sponsoring in Universe
[15:09] <RoAkSoAx> which I'd like to change
[15:11] <Laney> urgh, my internet just froze — sorry
[15:11] <Laney> the patch pilot process was designed to avoid certain patches being repeatedly ignored
[15:12] <Laney> so if you're finding that happening then I suggest you speak to dholbach and/or rickspencer3 and try to get it sorted
[15:12] <RoAkSoAx> Laney: will do ;)
[15:14] <stgraber> also, were you aware of the ubuntu server packageset?
[15:14] <RoAkSoAx> stgraber: yes I am, though I know nonone's in it yet
[15:14] <stgraber> Dave Walker and Mathias Gug are in it
[15:15] <RoAkSoAx> stgraber: AFAIK I though Dave was core dev rather than in the server package set
[15:15] <RoAkSoAx> dunno about mathiaz
[15:15] <RoAkSoAx> but anyways, the reason why I went to core dev directly is that I'd also like to do some greater good than just ubuntu server packages
[15:15] <stgraber> yep, both of them also happen to be coredev ;)
[15:16] <RoAkSoAx> i know :)
[15:16] <RoAkSoAx> though, last time I spoke about it, no-one was in it yet :(
[15:17] <stgraber> yeah, helping with sponsoring/merging in main is definitely a good reason to apply for core-dev :) I was just wondering if that packageset was known at all and if we should try to get more people to apply for upload rights to it.
[15:18] <geser> a list of the available package set for which applicants can apply would probably help
[15:18] <RoAkSoAx> i think we do, though, IMHO we don't have as many contributors as other teams do, and that's probably why the packageset is not yet well known out there
[15:18] <RoAkSoAx> geser: indeed!
[15:18] <stgraber> http://paste.ubuntu.com/619968/ apparently
[15:18] <MootBot> LINK received:  http://paste.ubuntu.com/619968/ apparently
[15:19] <stgraber> ok, any other question for RoAkSoAx?
[15:20] <geser> no
[15:21] <stgraber> [VOTE] Ubuntu Core Developer membership for Andres Rodriguez
[15:21] <MootBot> Please vote on:  Ubuntu Core Developer membership for Andres Rodriguez.
[15:21] <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
[15:21] <MootBot> E.g. /msg MootBot +1 #ubuntu-meeting
[15:21]  * maco reads scrollback (sorry, was in bathroom)
[15:22] <stgraber> maco: ok, if you have any question before voting, just go ahead and ask
[15:23] <Laney> RoAkSoAx: Do you agree with your endorsers that there are no areas in which you could improve? ;-)
[15:23] <RoAkSoAx> Laney: I believe there's always area of improvement, as I said earlier, you never finish learning
[15:23] <RoAkSoAx> Laney: though I guess they referred to the technical skills required to be a core dev
[15:24] <maco> wow very thorough application
[15:24] <RoAkSoAx> but yeah, we wouldn't be in this if we wouldn't improve ourselves eventually
[15:24] <Laney> anyway
[15:24] <Laney> +1
[15:24] <MootBot> +1 received from Laney. 1 for, 0 against. 0 have abstained. Count is now 1
[15:24] <stgraber> +1
[15:24] <MootBot> +1 received from stgraber. 2 for, 0 against. 0 have abstained. Count is now 2
[15:24] <geser> +1
[15:24] <MootBot> +1 received from geser. 3 for, 0 against. 0 have abstained. Count is now 3
[15:25] <maco> +1
[15:25] <MootBot> +1 received from maco. 4 for, 0 against. 0 have abstained. Count is now 4
[15:25] <stgraber> [ENDVOTE]
[15:25] <MootBot> Final result is 4 for, 0 against. 0 abstained. Total: 4
[15:25] <stgraber> and one more core-dev!
[15:25] <stgraber> congrats RoAkSoAx!
[15:25] <RoAkSoAx> YaY!!!
[15:25] <RoAkSoAx> stgraber: thank you!
[15:25] <RoAkSoAx> Laney: geser maco thank you too guys!
[15:25] <RoAkSoAx> and thank you for taking the time to process this today
[15:26] <stgraber> [TOPIC] Chair for next meeting
[15:26] <MootBot> New Topic:  Chair for next meeting
[15:26] <stgraber> volunteers?
[15:27] <stgraber> apparently not :)
[15:28] <stgraber> [TOPIC] AOB
[15:28] <MootBot> New Topic:  AOB
[15:28] <stgraber> anything else?
[15:29] <maco> i suppose i could chair the next meeting, but ive never done it before
[15:29] <maco> there's a bot and it does some stuff....this much ive got
[15:29] <stgraber> I already added RoAkSoAx to core-dev and rsalveti to universe-contributors. Will quickly write the minutes now and figure out who I'm supposed to e-mail them too again :)
[15:29] <stgraber> [ACTION] maco to chair the next DMB meeting
[15:29] <MootBot> ACTION received:  maco to chair the next DMB meeting
[15:29] <stgraber> maco: https://wiki.ubuntu.com/ScribesTeam/MootBot
[15:30] <stgraber> maco: that's for the bot. Other than that, it's the usual, go through the agenda, copy/paste the notes in the team reports (https://wiki.ubuntu.com/TeamReports) and probably e-mail it to some list (not sure which one, will figure it out after the meeting and update our wiki page)
[15:31] <stgraber> #endmeeting
[15:31] <MootBot> Meeting finished at 09:31.
[15:31] <stgraber> thanks everyone for attending!
[15:31] <maco> stgraber: kk thanks
[15:31] <geser> stgraber: I usually look at the last minutes to see where to mail them :)
[15:32] <stgraber> geser: yep, sounds good. I'm probably going to put the post-meeting TODO at the end of the agenda so whoever chairs the meeting can just follow that.
[15:57]  * skaet waves
[15:57] <martins-gss> hi
[16:00] <skaet> #startmeeting
[16:00] <MootBot> Meeting started at 10:00. The chair is skaet.
[16:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[16:00] <skaet> SRU/LTS bi-weekly synch meeting.
[16:00] <skaet> .
[16:00] <skaet> Reminder, please follow the convention  of using ".." on a separate line when you've finished typing.    Also, If someone wants to comment on the last point, please "o/", so we know to wait.
[16:00] <skaet> [TOPIC] Release overview - skaet
[16:00] <MootBot> New Topic:  Release overview - skaet
[16:01] <skaet> Dapper Drake (6.06) Server EOL on June 1.   OEM is ok with cleanup of archive,  so will be working with teams to clean up the old packages and PPAs over next few weeks (and get back some space).
[16:01] <skaet> .
[16:01] <skaet> [LINK] https://wiki.ubuntu.com/Releases
[16:01] <skaet> .
[16:01] <skaet> 10.04.3 - July 21 - no negative feedback so moved.
[16:01] <MootBot> LINK received:  https://wiki.ubuntu.com/Releases
[16:01] <skaet> [LINK] https://wiki.ubuntu.com/LucidReleaseSchedule
[16:01] <MootBot> LINK received:  https://wiki.ubuntu.com/LucidReleaseSchedule
[16:01] <skaet> ..
[16:01] <ara> o/
[16:01] <skaet> go ara
[16:01] <ara> I have a question related to EOL
[16:01]  * vanhoof looks in
[16:01] <ara> we had set the date of EOL for Dapper
[16:02] <ara> for the end of June
[16:02] <ara> and we needed to change it last week to avoid certificates for 6.06 appearing in the site
[16:02] <skaet> EOL for Dapper was June 1
[16:02] <ara> I know
[16:02] <ara> my question is:
[16:02] <ara> are EOLs normally going to be at the beginning of the month?
[16:02] <ara> (rather the end of the month=
[16:03] <ScottK> It should relate to the release date.
[16:03] <skaet> EOLs are a fixed period of time after the release
[16:03] <skaet> date
[16:04] <skaet> I'm not sure where EOL for Dapper at end of June came from as a notion.
[16:04] <skaet> I'll look into it a bit offline
[16:04] <ara> OK, thanks
[16:05]  * skaet looks around for any other questions?
[16:05] <skaet> heh,  and since I just saw sconkin join...   will move on.
[16:06] <skaet> [TOPIC] Kernel SRU status - sconklin
[16:06] <MootBot> New Topic:  Kernel SRU status - sconklin
[16:06] <sconklin> we just published new kernels to -proposed for the major series (and to other pockets, but that's bee resolved I think)
[16:07] <sconklin> ec2 and backports for LTS will follow today or tomorrow
[16:07] <sconklin> and evrification will begin, a week later than we had hoped it would
[16:07] <sconklin> ..
[16:07] <skaet> Thanks sconklin.
[16:07] <skaet> What is the story with lucid kernel,  is that resolved and published to -proposed now?
[16:08]  * skaet may have missed something in her inbox....
[16:08] <pitti> the issue of having natty kernels in lucid/maverick-proposed should all be resolved now
[16:08] <pitti> see u-d-a@
[16:08] <sconklin> not sure what you're referrign too, but yes, there's a new Lucid that resolved past issues
[16:08] <pitti> https://lists.ubuntu.com/archives/ubuntu-devel-announce/2011-June/000854.html
[16:08] <skaet> thanks sconklin,   thats what I was wondering.
[16:08] <pitti> ah, that's something else then, sorry
[16:09] <skaet> thanks pitti,  yup, read that this morning.  :)
[16:09] <skaet> anyone else have questions for sconklin?
[16:09] <skaet> [TOPIC] General SRU status - pitti
[16:09] <MootBot> New Topic:  General SRU status - pitti
[16:10] <pitti> I'm currently wondering about the linux-lts-backport-natty in the PPA
[16:10] <pitti> sec, door bell
[16:10] <pitti> other than that, it's pretty much business as usual
[16:10] <sconklin> pitti, first, ignore it, it will be replaced by another today
[16:10] <pitti> we have some backlog in natty queue processing, I need some more hands with that
[16:11] <pitti> people are uploading SRUs like crazy :)
[16:11] <pitti> sconklin: ack
[16:11] <sconklin> second, tose build failures are for arch's which were being tested during development and not released for stable, so they can be ignored. I'm told that they should stop happening, i.e. the natty backport is not supposed to try to build for those archs
[16:11] <sconklin> ..
[16:12] <pitti> the non-usual SRU thing that will happen soon is the switch from firefox 4 to 5 in natty, which will require some coordination with a full language pack refresh
[16:12] <pitti> but that's pretty much understood
[16:12] <pitti> ..
[16:13] <skaet> thanks pitti.  :)
[16:13] <skaet> [TOPIC] QA status - jibel
[16:13] <MootBot> New Topic:  QA status - jibel
[16:13] <jibel> Packages published to -proposed, -updates and -security since last week
[16:13] <jibel> http://reports.qa.ubuntu.com/reports/sru/latest.html
[16:13] <MootBot> LINK received:  http://reports.qa.ubuntu.com/reports/sru/latest.html
[16:14] <jibel> Pending Ubuntu stable release updates
[16:14] <jibel> http://people.canonical.com/~ubuntu-archive/pending-sru.html
[16:14] <MootBot> LINK received:  http://people.canonical.com/~ubuntu-archive/pending-sru.html
[16:14] <jibel> There are currently 19 SRUs with Critical or High importance in -proposed waiting for verification
[16:14] <jibel> 2 Critical SRUs in Natty:
[16:14] <jibel>  * bug 778026 in Natty requires an Infra-red Remote Control
[16:14] <jibel>  * bug 778520
[16:14] <jibel> A couple of SRUs are targeted to 10.04.3
[16:14] <jibel>  * bug 777759 : See comment #1 for verification
[16:14] <jibel>  * bug 695842 : Requires specific Hardware (two CCISS disks and doing a RAID install on it)
[16:14] <jibel>  * 2 Wubi bugs: bug 610898, bug 742967 : Not sure of the status based on the comment in the report and I am not able to reproduce the original issue.
[16:15] <jibel>  * bug 687501 : Not sure of the status and if it can be promoted to lucid-updates
[16:15] <jibel>  * bug 783836 : requires a re-producable test case
[16:15] <jibel>  * bug 561750
[16:16] <jibel> ..
[16:16] <skaet> Thanks jibel,  :)
[16:16] <skaet> Will work with you offline to get a summary of the 10.04.3 targetted bugs, and get it circulated.
[16:16] <jibel> thanks
[16:18] <skaet> On that note of 10.04.3 - Does freeze a month before make sense,  or can we make it 3 weeks?  (am thinking we want to interlock with the new SRU cycle a bit better this time?)
[16:18] <skaet> sconklin, pitti,  ^^
[16:18] <pitti> my gut feeling is that 3 weeks are enough; didn't we do 3 weeks for .2 as well?
[16:18] <sconklin> this might be a good time to note that the kernel SRU calendar we have in google calendars all needs to be shifted a week later
[16:19] <skaet> pitti,  we did a month, but I think that 3 weeks is worth trying too.
[16:19] <skaet> sconklin,  ack.
[16:19] <sconklin> I don't know. The kernel generally freezes a week before everything else
[16:19] <bjf> skaet, we should talk to pgraner to see how he's going to be setup for supporting sru kernels
[16:20] <skaet> sconklin,  ok,  I'll be working on the interlock this week, and we can see how it all lines up.
[16:20] <sconklin> but generally the less freeze time the better
[16:20] <bjf> skaet, i'd like to see us decouple as soon as possible for him
[16:20] <sconklin> +1
[16:20] <skaet> bjf,  yes,  will do.
[16:20] <skaet> [TOPIC] HW certification - brendand
[16:20] <MootBot> New Topic:  HW certification - brendand
[16:21] <bjf> skaet, however, i recognize he has quite a load on his plate this dev cycle and not sure he'll have the resources
[16:21] <brendand> Not much from our side. We are preparing to start testing Lucid, Maverick and Natty kernels once the verification phase is done.
[16:21] <bjf> ..
[16:21] <brendand> sconklin, any reasons why the start of the testing phase could be later than next Monday?
[16:21] <brendand> ..
[16:22] <skaet> thanks brendand.  :)
[16:22] <skaet> sconklin?
[16:22] <sconklin> brendand: we are not expecting any delays. But our tracking bug dashboard is totally unusable this morning due to the problems this morning, and I don't know how many bugs require verification
[16:23] <sconklin> But I don't expect delays
[16:23] <sconklin> ..
[16:23] <brendand> thanks
[16:23] <skaet> brendand,  are there reports from the last cycle we can look at now?
[16:24] <brendand> skaet - http://people.canonical.com/~hwcert/sru-testing/current
[16:25] <brendand> skaet - but my understanding was these kernels were not getting published?
[16:25] <skaet> Thanks brendand.
[16:25]  * skaet will look at them, and do some cross correlation later. 
[16:26] <skaet> any other questions for brendand?
[16:26] <skaet> [TOPIC] Support priorities - martins-gss
[16:26] <MootBot> New Topic:  Support priorities - martins-gss
[16:26] <martins-gss> great
[16:26] <martins-gss> http://people.canonical.com/~pmatulis/martin/Support-status-june-6.html
[16:26] <MootBot> LINK received:  http://people.canonical.com/~pmatulis/martin/Support-status-june-6.html
[16:26] <martins-gss> this is the current support escalations that we have
[16:27] <martins-gss> the top three are the highest in priority at the moment
[16:27] <martins-gss> http://launchpad.net/bugs/695842
[16:27] <MootBot> LINK received:  http://launchpad.net/bugs/695842
[16:27] <martins-gss> ubottu
[16:28] <martins-gss> ubottu yes correct, next three, sorry
[16:28] <martins-gss> rails (Ubuntu)
[16:29] <martins-gss> skate this is a long list, what do you want covered for this meeting?
[16:29] <skaet> just the top 3 please,  so they're on the log
[16:29] <martins-gss> ok
[16:30] <martins-gss> http://launchpad.net/bugs/670571
[16:30] <MootBot> LINK received:  http://launchpad.net/bugs/670571
[16:30] <martins-gss> open, we have difficulty reproducing, this status shows as fixed, but is not
[16:31] <martins-gss> http://launchpad.net/bugs/688703
[16:31] <MootBot> LINK received:  http://launchpad.net/bugs/688703
[16:31] <martins-gss> open, high priority, need to work with developers and see if we can get hw vendor to provide equipment
[16:32] <martins-gss> those are the three that I have on high status
[16:33] <skaet> thanks martins-gss.    I'll work with you offline to figure out if we can get the statuses to match what you expect them to be.
[16:33] <martins-gss> ok great thanks
[16:33] <skaet> any one have questions for martins-gss ?
[16:33] <ScottK> Might be the other way around.
[16:33] <skaet> :)
[16:34] <martins-gss> I am good for now
[16:34] <skaet> [TOPIC] OEM priorities - vanhoof
[16:34] <MootBot> New Topic:  OEM priorities - vanhoof
[16:34] <vanhoof> skaet: two bugs: bug 790754 & bug 741825
[16:35] <vanhoof> skaet: both are posted, and awaiting review/ack
[16:35] <vanhoof> hopefully will make next natty SRU cycle
[16:35] <vanhoof> ..
[16:35] <skaet> thanks vanhoof.  :)
[16:35] <skaet> where are they posted
[16:35] <vanhoof> for kernel team review
[16:36] <skaet> coolio,  will leave it to sconklin and bjf then.  :)
[16:36] <vanhoof> cool
[16:36] <vanhoof> nothing else from me presently
[16:36] <skaet> any questions for vanhoof?
[16:36] <skaet> [TOPIC] New business, last chance for general questions? - all
[16:36] <MootBot> New Topic:  New business, last chance for general questions? - all
[16:36] <skaet> going once...
[16:37] <skaet> twice...
[16:37] <skaet> #endmeeting
[16:37] <MootBot> Meeting finished at 10:37.
[16:37] <skaet> thanks all.
[16:39] <jibel> Thanks for chairing skaet !
[16:40] <pitti> thanks skaet
[18:15] <jdstrand> hi!
[18:16] <kees> \o
[18:16]  * sbeattie waves
[18:16] <micahg> o/
[18:16] <jdstrand> #startmeeting
[18:16] <MootBot> Meeting started at 12:16. The chair is jdstrand.
[18:16] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[18:16] <jdstrand> The meeting agenda can be found at:
[18:16] <jdstrand> [LINK] https://wiki.ubuntu.com/SecurityTeam/Meeting
[18:16] <MootBot> LINK received:  https://wiki.ubuntu.com/SecurityTeam/Meeting
[18:16] <jdstrand> [TOPIC] Review of any previous action items
[18:16] <MootBot> New Topic:  Review of any previous action items
[18:16] <jdstrand> we actually don't have any. that is not an indication of a lack of work done :P
[18:17] <jdstrand> [TOPIC] Weekly stand-up report
[18:17] <MootBot> New Topic:  Weekly stand-up report
[18:17] <jdstrand> I'll go first
[18:17] <mdeslaur> hello
[18:17] <jdstrand> I was on triager last week, and am on community this week
[18:17] <jdstrand> I've got a qemu-kvm update I am working on
[18:18] <jdstrand> (which has involved writing test-qemu.py for qrt)
[18:18] <jdstrand> I hope to have that published by tomorrow
[18:19] <jdstrand> the server team has been waiting on me for the final libvirt merge (they did it, but there were various reviews/issues that I am looking at (not related to the work already done-- related to some upstream changes/bugs)
[18:19] <jdstrand> )
[18:20] <jdstrand> jjohansen and I plan to get together on dbus/apparmor (finally) and I hope to work on that a bit this week
[18:20] <jdstrand> finally, I have a pile of email I need to get through
[18:20] <jjohansen> yeah we are crazy
[18:20] <jdstrand> that's it from me
[18:20] <jdstrand> kees, you're up
[18:20] <kees> this week I'm in the happy place!
[18:21] <mdeslaur> \o/ :)
[18:21] <kees> I've got a double-patch pilot on thursday
[18:21] <jdstrand> eek
[18:21] <kees> (I skipped a patch pilot during uds, so I'm going to pull 8 hours thursday)
[18:21] <jdstrand> well, that day is gone :P
[18:21] <kees> I'm on vacation for a week starting friday
[18:21] <kees> yeah
[18:21] <sbeattie> (is that the not-so-happy place?)
[18:21] <kees> heheh
[18:21] <jdstrand> hehe
[18:22] <kees> I'm getting familiar with the new bug-based workflow for kernel SRU validation
[18:22] <kees> and will be continuing to work on USN correctly/building tools and LP/uct sync tools
[18:22] <kees> that's it from me
[18:23] <jdstrand> kees: if you have time, would you mind looking at the accountsservice and apg mirs (#785680, #785682)
[18:23] <jdstrand> kees: I think it is blocking the new gnome-control-center
[18:23] <jdstrand> kees: if not, we can have someone else do it
[18:23] <kees> okay
[18:23] <jdstrand> (seb128 requested it today)
[18:24] <jdstrand> I think apg will be pretty quick, fwiw
[18:24] <jdstrand> I don't know what accountservice is
[18:24] <jdstrand> kees: anyhoo, if you can't get to it, feel free to handoff to someone else
[18:24]  * kees nods
[18:25] <jdstrand> mdeslaur: you're up
[18:25] <mdeslaur> So, I just released subversion, and have a surprise flashplugin-nonfree update to do today
[18:25] <jdstrand> kees: oh, and thank you for looking at those :)
[18:25] <mdeslaur> after that, I'll be going down the list, and maybe doing some work items
[18:25] <mdeslaur> that's it from me!
[18:26] <mdeslaur> oh, I may look at nagios3
[18:27] <jdstrand> sbeattie: you're next
[18:27] <sbeattie> cool.
[18:27] <sbeattie> I'm in the happy place this week.
[18:27] <sbeattie> I have an embargoed update on my plate.
[18:28] <sbeattie> I'm also poking a bit at the dovecot qrt script after last weeks update; oneiric has dovecot 2.0.x which introduces some changes.
[18:29] <sbeattie> and am investigating a related issue with dovecot.
[18:29] <sbeattie> beyond that, I have some apparmor things I need to work on.
[18:29] <sbeattie> I think that's it for me.
[18:30] <jdstrand> micahg: you're up
[18:30] <micahg> still trying to figure out while I can't get the thunderbird regression to reliably fail, by EOD should know more
[18:31] <micahg> there's a chrome update for the new flash that we don't need
[18:31] <micahg> there should be a new chromium stable update this week or next based on the 6 week timeline
[18:32] <micahg> chrisccoulson proposed a plan for the natty update to Firefox 5, I will need to discuss that with him, that will be taking my time over the weekend and next week
[18:33] <micahg> Firefox 3.6.19 builds should be ready towards the end of the week, I'll get those uploaded when they're release to the beta channel
[18:33] <micahg> Thunderbird 3.1.11 same as Firefox 3.6.19
[18:34] <jdstrand> micahg: the tbird regression is the global menu thing?
[18:34] <micahg> jdstrand: yeah, that I can verify, I just have other problems with thunderbird in the VM which my be related to my "server" vm
[18:35] <micahg> but I don't remember having these issues when originally testing 3.1.10
[18:35] <chrisccoulson> one person has already reported the menu bug upstream to mozilla now btw
[18:36] <jdstrand> micahg: what do you think about just pushing that fix to the archive?
[18:36] <jdstrand> (istr that the fix was very small and easy to verify)
[18:37] <chrisccoulson> it's 1 line ;)
[18:37] <micahg> jdstrand: and just blame my vm setup for the test issues?
[18:38] <jdstrand> micahg: have you compared the test output from the previous builds to the current?
[18:38] <micahg> jdstrand: not yet, was going to do that today and if they matched, just push it out
[18:39] <jdstrand> sounds like a plan
[18:39] <jdstrand> micahg: anything else?
[18:39] <micahg> well, I have a short week this week, off wed/thu
[18:39] <jdstrand> ok
[18:39] <jdstrand> micahg: thanks
[18:39] <jdstrand> [TOPIC] Miscellaneous and Questions
[18:39] <MootBot> New Topic:  Miscellaneous and Questions
[18:39] <micahg> o/
[18:39] <micahg> not done...
[18:40] <jdstrand> ah
[18:40] <jdstrand> micahg: please go ahead
[18:41] <micahg> also, would like to get webkit 1.2.7 out before I get bogged down in the Firefox 5 migration, but have been having trouble getting through the CVEs, I think only a limited number were fixed in 1.2.6 and 1.2.7, so I'm going to look at the Debian CVE tracker today and see what they marked as fixed by these updates, and if it looks sane, upload based on that and try to push that out thursday night
[18:41] <micahg> ok, that's it :)
[18:42]  * jdstrand nods
[18:42] <jdstrand> I will not be taking off all of next week after all. but likely take of just monday
[18:42] <jdstrand> does anyone have any other questions or items to discuss?
[18:44] <jdstrand> #endmeeting
[18:44] <MootBot> Meeting finished at 12:44.
[18:44] <jdstrand> kees, mdeslaur, sbeattie, micahg: thanks!
[18:44] <sbeattie> jdstrand: thank you!
[18:44] <mdeslaur> thanks jdstrand!
[18:44] <micahg> thanks jdstrand
[18:45] <kees> thanks jdstrand!
[18:45] <jdstrand> sure thing!
[19:00] <total08> cxz
[19:01] <total08> Ïðèâåò