[00:20] bdmurray: ping === noy_ is now known as noy === doko__ is now known as doko === Mkaysi_ is now known as Mkaysi === Quintasan_ is now known as Quintasan === fader_ is now known as fader === cmagina-afk is now known as cmagina [17:05] hello [17:05] \o [17:06] * sbeattie waves [17:06] hello [17:07] let's get started [17:07] #startmeeting [17:07] Meeting started Mon Aug 15 17:07:09 2011 UTC. The chair is jdstrand. Information about MeetBot at http://wiki.ubuntu.com/AlanBell/mootbot. [17:07] Useful Commands: #topic #action #link #idea #voters #vote #chair #action #agreed #help #info #endmeeting. [17:07] The meeting agenda can be found at: [17:07] [LINK] https://wiki.ubuntu.com/SecurityTeam/Meeting [17:07] [TOPIC] Review of any previous action items === meetingology changed the topic of #ubuntu-meeting to: Review of any previous action items [17:07] TOPIC: Review of any previous action items [17:07] huh, that's new [17:07] yeah [17:07] meetingology: hello [17:07] jdstrand: Error: "hello" is not a valid command. [17:08] anyhoo [17:08] seems we don't have any ACTION items from last week, so moving on [17:08] [TOPIC] Weekly stand-up report === meetingology changed the topic of #ubuntu-meeting to: Weekly stand-up report [17:08] TOPIC: Weekly stand-up report [17:08] I'll go first [17:08] so, I am back after my tour of the southern US [17:09] as such, I am dealing with quite a bit of backlog (email, et al) [17:09] in addition to that, I have some dbus/apparmor stuff to get back to [17:09] (sorry I didn't get dbus uploaded before FF) [17:10] I saw a few Oneiric apparmor profile bugs come in, so I'll fix those [17:10] and then a bunch of archive admin catch-up [17:10] I may pick up an update, but have a feeling I will not get to it [17:10] that's it from me [17:10] kees: you're up [17:11] okay, I'm on triage [17:11] and since I didn't get much triage done last week, this week will have more! :) [17:11] the kernel bug sync tools are in good shape now; they implement everything apw and I have identified as needing to be implemented. [17:11] kees: nice! [17:12] but I'll continue to keep an eye on it for tweaks. after that, I seriously need to get a handle on my work items [17:12] the graphing stuff just keeps slipping [17:12] in other news, kvm is now PIE [17:12] why bother, nobody would waste their time writing a kvm exploit [17:13] bliss: your join and that comment were perfectly timed! [17:13] * bliss bows [17:13] anyway, that's it from me. mdeslaur is up! [17:13] re kvm> woohoo [17:13] hiya! [17:13] :) [17:13] when will ax25d be PIE? [17:13] * mdeslaur points troll finger at bliss [17:13] so, I justpublished two updates [17:14] and I _still_ have foomatic to test [17:14] I'm currently working on some new stuff for vm-new [17:14] and will also go down the list [17:14] that's it from me [17:14] sbeattie: you're up [17:14] (oh, did a ton of MIR work last week. there is still more to do...) [17:14] I'm still wading through email after having most of last week off. [17:15] I'm on community this week. [17:15] and I have two days of holiday at the end of this week. [17:15] I also need to untangle my work items and do more stuff on the apparmor front. [17:16] that's pretty much it for me. [17:16] micahg: over to you [17:16] should be publishing a long overdue webkit update today [17:16] \o/ [17:16] \o/ [17:16] on track to release Firefox and Thunderbird tomorrow with upstream [17:17] \o/ [17:17] micahg: awesome :) [17:17] when that's all done, the last chromium update broke html5 on maverick and natty, so I've held off on publishing [17:17] micahg: is upstream aware of it? [17:18] idk, I tried to ask in their support channel yesterday w/no response, will try later today [17:18] grr.. [17:18] weekend is understandable :) [17:19] later this week, I need to discuss with pitti about Maverick migrating to Firefox 6 w/the final langpack update [17:20] I'd like to have 6 go through proposed/updates, then 7 will go through -security [17:20] micahg: does that mean lucid will get firefox 6 soon? [17:20] jdstrand: not necessarily, I'm still waiting on upstream's plans for 3.6.x EOL [17:20] makes sense [17:21] though, since maverick and lucid have the same release, I wonder if it is worth the effort there [17:21] this is driven by the end of langpack updates for maverick which is needed for the rapid release migration [17:21] (ie, on maverick) [17:21] ah [17:22] so, that's it for me [17:22] thanks [17:22] [TOPIC] Highlighted packages === meetingology changed the topic of #ubuntu-meeting to: Highlighted packages [17:22] TOPIC: Highlighted packages [17:23] The Ubuntu Security team will highlight some community-supported packages that might be good candidates for updating and or triaging. If you would like to help Ubuntu and not sure where to start, this is a great way to do so. See https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures for details and if you have any questions, feel free to ask in #ubuntu-security. [17:23] http://people.canonical.com/~ubuntu-security/cve/pkg/kolab-cyrus-imapd.html [17:23] http://people.canonical.com/~ubuntu-security/cve/pkg/audacity.html [17:23] http://people.canonical.com/~ubuntu-security/cve/pkg/neon26.html [17:23] http://people.canonical.com/~ubuntu-security/cve/pkg/xymon.html [17:23] http://people.canonical.com/~ubuntu-security/cve/pkg/monkeysphere.html [17:23] [TOPIC] Miscellaneous and Questions === meetingology changed the topic of #ubuntu-meeting to: Miscellaneous and Questions [17:23] TOPIC: Miscellaneous and Questions [17:23] Does anyone have any other questions or items to discuss? [17:25] * bliss cheers for acceptance of patch that prevents missing setuid return code checks from being root holes [17:25] bliss: where? [17:25] oh, neat [17:25] where is that? [17:25] upstream kernel, let me find link [17:26] cool! [17:27] bliss: is this segoon's work? [17:27] yeah [17:27] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commit;h=72fa59970f8698023045ab0713d66f3f4f96945c [17:28] oh! excellent. [17:29] nice [17:29] rockin' [17:30] anything else? [17:30] i guess stealth will have to find a new vuln class to root android kernels with [17:30] heh [17:31] alrighty then [17:31] thanks everyone! [17:31] #endmeeting === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology is the new Mootbot https://wiki.ubuntu.com/AlanBell/mootbot [17:31] Meeting ended Mon Aug 15 17:31:57 2011 UTC. Information about MeetBot at http://wiki.ubuntu.com/AlanBell/mootbot . (v 0.1.4) [17:31] Minutes: http://ubottu.com/meetingology/logs/ubuntu-meeting/2011/ubuntu-meeting.2011-08-15-17.07.moin.txt [17:32] thanks jdstrand! [17:32] thanks guys, keep up the good work :-) [17:32] << ubuntu security cheerleader [17:32] \o/ [17:32] :) [17:34] thanks jdstrand! [18:23] jdstrand: bot and minutes work OK for you? [19:00] right, dmb? [19:00] Laney, I hope so. [19:00] We have had several apologies on email [19:01] but I hope that we can still meet and if necessary carry out any supplementary voting on list [19:01] Laney, +1 to that [19:01] :-) [19:01] geser: persia [19:02] * geser is here [19:03] 4am for persia so I'm doubting even he is awake at that hour [19:03] geser: shall we? [19:04] Laney: you mean do the questioning and vote per mail? [19:04] yes [19:05] sure, can you chair? [19:05] yep [19:06] #startmeeting [19:06] Meeting started Mon Aug 15 19:06:06 2011 UTC. The chair is Laney. Information about MeetBot at http://wiki.ubuntu.com/AlanBell/mootbot. [19:06] Useful Commands: #topic #action #link #idea #voters #vote #chair #action #agreed #help #info #endmeeting. [19:06] I think it's best to skip "Rename UCD/UUC to Ubuntu Development Members" until there are more people around to discuss it [19:07] it arose from a conversation on -devel about UCD being confusing [19:07] or we can bring it up on devel-permissions [19:08] iamfuzz smoser cnd: you ready? [19:08] * iamfuzz is ready [19:08] I am [19:08] I am ready [19:08] Laney: I agress to move it to the next meeting, a discussion about a more clear name could be done on devel-permissions and/or ubuntu-devel [19:08] ok great [19:08] alright, so we're going to do the 'interview' stage today and then defer voting to email [19:08] sounds good [19:08] since 3 members are away/travelling and 1 has resigned [19:09] (:() [19:09] :-( indeed [19:09] [topic] MOTU Application for Brian Thomason === meetingology changed the topic of #ubuntu-meeting to: MOTU Application for Brian Thomason [19:09] TOPIC: MOTU Application for Brian Thomason [19:09] hey iamfuzz :-) can you quickly introduce yourself? [19:09] Sure, I'm Brian Thomason, and I've been doing packaging work professionally for about 9 years [19:10] I started with Lindows/Linspire, and joined Canonical a little over 4 years ago [19:10] I've been doing work in Universe for about 2 years now [19:10] and currently maintain all packages in the Canonical partner repo, and all For Purchase apps in the software center, along with 5-10 packages in universe [19:11] and for the record, this is my second MOTU application [19:11] :-) [19:11] how do you think packaging for partner differs from packaging in the main archive? [19:11] quite differently in most cases [19:11] do you stick to the standard Ubuntu release cycle? [19:12] no, not at all [19:12] we are at the whim of the ISV in most cases [19:12] we transition packages starting at Beta 1, and attempt to have them all migrated before RC1 [19:12] iamfuzz: you mentioned in your wiki page that also some free software is in the partner archive. is there a reason why it's in the partner archive and not the main repository? [19:12] However, Partner is always open and doesn't have the concept of pockets, such as -updates or -security [19:13] geser, yes, the free software that resides there is Openbravo, Alfresco, and Jonas [19:13] These ship many binary jars [19:13] rather than using those provided in the archive or even compiling them from source at build time [19:13] ah, the usual java trouble [19:13] this has prevented their transition to universe [19:14] most vendors refuse to do so as they wish to certify one build, rather than, in their minds, an additonal "Ubuntu" build [19:14] do you think it would be beneficial for these projects to work out the problems to get themselves into debian / ubuntu? or would it be more trouble than it's worth? [19:14] with potential moving pieces (the JAR deps) [19:14] could they not go into multiverse? [19:14] * Laney finds this quite interesting [19:15] Laney, in the case of Alfesco, probably more trouble than it's worth [19:15] 100+ jars at last count [19:15] though as the Java library in Ubuntu grows, it becomes more feasible [19:15] for Openbravo, yes, they likely would benefit and we speak with them about this every 6 months but have not as of yet gotten the go ahead [19:15] as for Multiverse, it likely could [19:16] but they see no benefit there as it isn't enabled by default on most server installs either [19:16] I guess part of the problem is that jars don't have proper versioning (API/ABI) [19:16] and they enjoy the lax rules of Partner [19:16] as well as a commercial relationship [19:16] correct [19:16] indeed [19:16] as well as the fact that they patch many of them to their liking [19:17] what are the main differences between the partner repository and the main one? just the relaxed rules? [19:17] relaxed rules, no pockets, always open [19:17] and the only license criteria that need be met is a distribution agreement with Canonical [19:18] that being said, with the relaxed rules, we do our best to make the packages as presentable as possible [19:18] I suppose for upstreams it gives them a guarantee hat their software will become available [19:18] but it isn't always easy with the binary blobs of goodness we receive :-) [19:18] correct, and the warm and fuzzies that they are a "Partner" of Canonical [19:19] anyway, to Ubuntu Development. (my standard question) Have you worked with Debian at all? For example forwarding patches [19:19] yes, not a ton, but yes [19:19] :-) [19:20] I worked with Debian to fix the gstreamer-plugins-bad package to not improperly collide with our packages [19:20] I've reported many bugs [19:20] and submitted a patch to lintian once [19:20] am in the process of working on a lintian profile that affects Partner packages [19:20] ah, excellent [19:20] that's a good development in lintian upstream [19:20] I've also worked fairly closely with their java maintainer as he assists with our building of them for partner [19:23] finally from me, you mention problems with the release cycle's length as a weakness in Ubuntu [19:23] what do yo uthink could be done about that? [19:23] I'm not sure there can be much done [19:23] I commented on that only because I came from a distribution that released ~every 2 years [19:23] which gave ample time for thorough bug testing and the like === med_out is now known as medberry [19:24] emphasise the LTS releases more over the others? [19:24] and more importantly in my role, it affects ISV package migrations [19:24] the IBMs of the world are slow to move [19:24] Yes, in that realm we do [19:24] if it's a "server" related package, we almost insist on their following the LTS cycle [19:24] which has proven helpful [19:24] I'm sure you know well all of the possible upgrade paths that you have to support [19:24] but the desktop-oriented offerings obviously have to be transitioned each release [19:25] geser: any qs? [19:25] no, just want to mention that I like to see that many testimonials on iamfuzz's application [19:25] indeed, i had much help along the way [19:26] thanks to all 4 of my mentors :-) [19:26] yes, they are very strong [19:26] good work :-) [19:26] geser: shall we vote now or would you prefer all votes on email? [19:26] like you like, I send sent my +1 now or with mail [19:27] let's vote now, to save some email traffic [19:27] [vote] Brian Thomason to join MOTU [19:27] Please vote on: Brian Thomason to join MOTU [19:27] Public votes can be registered by saying +1, +0 or -1 in channel, (private votes don't work yet, but when they do it will be by messaging the channel followed by +1/-1/+0 to me) [19:27] +q [19:27] erm, what does that mean? [19:27] +1 [19:27] +1 received from Laney [19:27] question? [19:27] +1 [19:27] +1 received from geser [19:27] means I can't hit the 1 correctly :P [19:28] ;-) [19:28] [endvote] [19:28] Voting ended on: Brian Thomason to join MOTU [19:28] Votes for:2 Votes against:0 Abstentions:0 [19:28] Motion carried [19:28] thanks a lot iamfuzz, watch devel-permissions for more :> [19:28] thanks guys, I very much appreciate your taking the time for the interview despite lack of quorum [19:28] yeah, sorry about that … [19:28] it happens [19:28] I seem to be a bad omen too [19:28] has happened 4 times to me :-) [19:28] heh [19:29] people seem to be travelling a lot currently [19:29] ah well [19:29] that time of year [19:29] smoser: here? [19:29] here [19:29] \o/ [19:30] [topic] Ubuntu Core Developer Application for Scott Moser === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Core Developer Application for Scott Moser [19:30] TOPIC: Ubuntu Core Developer Application for Scott Moser [19:30] I'm Scott Moser, I've been contributing to Ubuntu development for the past 2 years. For the majority of that time, I've been the responsible party for creating and releasing the official Ubuntu Cloud Images (UEC), which are ready-to-run images targetted towards running in cloud platforms. I've had PPU upload rights for a few packages for about a year, and have had several sponsored uploads across main, universe and multiverse. [19:30] care to give us a quick introduction to yourself? [19:30] aha! [19:30] my application is at https://wiki.ubuntu.com/ScottMoser/DeveloperApplication [19:30] [link] https://wiki.ubuntu.com/ScottMoser/DeveloperApplication [19:30] ... [19:31] I notice that you're explicitly applying for server and MOTU as well. Any reason for that? (not that it's a problem :-) [19:31] That was on advice of Daviey, but primarily the ubuntu-server-dev team is interested in boosting numbers to it. [19:32] and its membership approval is delegated here. [19:32] so 2 birds, one stone. [19:32] fair. [19:35] am I being waited on ? I just want to make sure I'm not holding anything up. My introduction came before Laney asked for it above (just to make sure it was seen). [19:36] too much to read in too little time [19:36] smoser: sorry, connection dropped [19:36] It is my impression that Ubuntu's cloud offerings have been rather sucessful. Is this accurate? Have you been please with the way they ahve been received? :-) [19:37] we have strong reason to believe that our images on EC2 are amoung the most popular to run. [19:38] I would say that that is most definitely the largest success we've had. The other thing to point to for success as Ubuntu as a "cloud os" is in Openstack usage. [19:38] Ubuntu is OpenStacks' reference platform, and our cloud-images are expected to work there, and used by many. [19:38] do the Ubuntu package need many changes to also work in the cloud image properly? [19:39] my largest head-butting with Ubuntu has been over grub. [19:39] the images are interesting in that we include both grub2 and write/manage a /boot/grub/menu.lst [19:39] how much of an intersection is there between server and cloud? Is there ever a conflict there or are they complementary? [19:40] grub-pc is included so that they can work as a normal ubuntu installation, and we manage /boot/grub/menu.lst with grub-legacy-ec2 (which is read by the 'pv-grub' "bootloader" on eC2) [19:40] i think there is a fairly large intersection between "server" and "cloud" [19:40] both ubuntu cloud host and cloud guest really are just package set selections. [19:41] and the packages that are improtant there rely heavily on functionality that is common to many ubuntu flavors [19:42] from the image perspective, we try to ship something that can easily and rapidly be provisioned into something that does what the user wants. [19:42] I guess outside of the 'infrastructure' not much needs modifying [19:43] I dont think i follow that. [19:44] what did you mean by 'infrastructure' ? [19:45] I am using infrastructure to refer to the packages needed to manage your cloud host or guest [19:45] well, largely i have ot say "i don't know" to much of that. [19:46] we certainly hope that people find the Ubuntu packages that are available in the archive to "just work". [19:46] but we give them a nice base, and they're able to use whatever they want to accomplish their task. [19:46] geser: any q? [19:47] ie, I'm actually not aware if 5% or 95% use the mysql that is packaged. they *could* all install from a binary build. [19:47] :-) [19:49] Laney: ready to vote [19:49] ok [19:50] [vote] Scott Moser to join core-dev, server-dev, MOTU [19:50] Please vote on: Scott Moser to join core-dev, server-dev, MOTU [19:50] Public votes can be registered by saying +1, +0 or -1 in channel, (private votes don't work yet, but when they do it will be by messaging the channel followed by +1/-1/+0 to me) [19:50] +1 [19:50] +1 received from geser [19:51] +1 // nice endorsements, and importently a nod to Debian in the application. Please continue to push for upstreaming of work wherever possible (Debian Cloud?) [19:51] grr [19:51] AlanBell: ^ make that work please ♥ [19:51] +1 [19:51] +1 received from Laney [19:51] [endvote] [19:51] Voting ended on: Scott Moser to join core-dev, server-dev, MOTU [19:51] Votes for:2 Votes against:0 Abstentions:0 [19:51] Motion carried [19:51] smoser: we'll be in touch over email [19:51] thanks for turning up :-D [19:51] cnd: heya, you here? [19:52] yep [19:52] thanks. [19:52] [topic] Ubuntu Core Developer Application: Chase Douglas === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Core Developer Application: Chase Douglas [19:52] TOPIC: Ubuntu Core Developer Application: Chase Douglas [19:52] quick intro? :> [19:52] sure [19:53] I'm one of the developers of the uTouch multitouch and gesture stack in Ubuntu [19:53] like much of the desktop-experience team at Canonical, we do a bunch of upstream development [19:53] however, our team is a little unique [19:53] we enjoy ubuntu development too :) [19:53] so we end up maintaining our own packages [19:54] so we do all kinds of development [19:54] * Laney likes the sound of that [19:54] did you write the packaging for your software? [19:54] for most of it, yes [19:54] our team did [19:54] specifically, I have packaged utouch-qml, utouch-gesturetest, and I have maintained packaging for all our stuff [19:54] I also have touched many packages throughout the stack [19:55] I started in the kernel team before utouch [19:55] so I have been involved there [19:55] and I still write patches that go upstream and then trickle back into ubuntu [19:55] I see you maintain a package in Debian. Do you think that works well? [19:55] tbh, I don't know too much [19:55] I wrote the package [19:55] and I have stats that show many people use it [19:56] you haven't had the pleasure of a bug report yet? :-) [19:56] but after a few bug reports initially I haven't heard anything since [19:56] ah [19:56] so no news is good news I guess :) [19:56] well, that's a good sign [19:56] I also have worked with debian in other areas [19:56] it's not causing you much trouble [19:56] I helped merge changes into pm-utils [19:57] and I have worked with the ubuntu and debian x teams [19:57] is the utouch stuff going to go to debian? [19:57] I'm the author of extensive X patches in ubuntu that we are hoping to get upstream into x.org [19:57] has anyone expressed interest there? [19:57] where it will be slurped into all the distros [19:57] or any other distro, for that matter [19:57] yes, we have interest from debian, and gentoo, and pretty much everyone :) [19:57] right now we have a prototype multitouch XInput extension in our server [19:57] which has been a proving ground of sorts [19:58] and we hope to have it officially available from upstream by the time 12.04 LTS ships [19:58] so we don't have a huge patch to maintain there [19:58] that would be great [19:59] it would also expand the reach of utouch since it's dependent on the patches [19:59] which no one else really wants to ship in their distro [19:59] and I don't blame them :) [19:59] the stuff needs to get upstream [20:00] I see one of your endorsers is someone you have mentored! [20:00] yes [20:00] that is a bit unusual - how did you find that experience? [20:00] great! [20:00] something you'd like to carry on if you are approved? :-) [20:00] (perhaps by hanging out in #ubuntu-motu, yes yes yes?) [20:00] certainly, it's one of th reasons I am coming here [20:01] I find it hard to participate in things like patch pilot [20:01] there are things one can do without upload rights [20:01] but many more things can be done with them to move things along faster [20:01] one of the goals of patch pilot was to /not/ require upload rights [20:01] I'm not sure that's been a success then... [20:01] it's true that it doesn't require it [20:01] i'd be interested in working with ways to make the stints more productive if you don't think that has worked [20:01] but I feel I don't accomplish much without it [20:02] I like to take tasks and see them to completion [20:02] I find that helps me make sure things are done [20:02] the more things are handed off from one person to another, the less likely it will really reach the finish line [20:03] I agree the nature of the work would have to be rather different (not direct sponsorship), but I'm sure we can find ways for people to be helpful even if they can't do the eventual sponsorship [20:03] hmm...... [20:03] I suppose I shouldn't have been so negative when I said it's not been a success [20:03] I feel I can do more [20:03] and that's one reason I'm here [20:03] no no I kind of foresaw this as something that might happen when we were devising the scheme [20:03] I think the program is reasonable [20:04] it just works better with upload rights [20:04] I don't want non-uploaders to feel like they aren't helping [20:04] there are 2k patches in Ubuntu that need a guiding hand [20:04] I'm not sure I have any good ideas off the top of my head on how to fix that [20:04] for example there is that ^ scheme that I forgot the name of [20:04] operation cleansweep [20:04] operation cleansweep [20:05] anyway, let's speak with dholbach about this another time [20:05] sure [20:05] geser: q? [20:05] it's probably worth pulling barry or poolie or someone else from the bzr team into the discussion, since that was the inspiration for the patch pilot stuff [20:05] no [20:06] broder: indeed [20:06] it'll be the patch pilot first anniversary at florida this year, perhaps we can review it then [20:06] not that I know if I'll be there yet [20:08] cnd: finally, there is a DMB seat going if you are interested. Regarding the recent thread(s), I apologise for our failings and hope we can work to improve the process :-) [20:08] particularly, I'm concerned that you didn't feel able to apply before now and how we can fix that [20:08] Laney, heh, I've been thinking very long and hard about that, tbh [20:08]