=== freeflying_away is now known as freeflying === freeflying is now known as freeflying_away === mapreri_ is now known as mapreri === freeflying_away is now known as freeflying === doko_ is now known as doko === AlanChicken is now known as alanbell === alanbell is now known as AlanBell === freeflying is now known as freeflying_away === greyback is now known as greyback|food === greyback|food is now known as greyback === Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha === mhall119_ is now known as mhall119 [16:32] \o [16:32] hi! [16:32] #startmeeting [16:32] Meeting started Mon Sep 30 16:32:42 2013 UTC. The chair is jdstrand_. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [16:32] Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired [16:32] The meeting agenda can be found at: [16:32] [LINK] https://wiki.ubuntu.com/SecurityTeam/Meeting [16:32] [TOPIC] Weekly stand-up report === meetingology changed the topic of #ubuntu-meeting to: Weekly stand-up report [16:32] I'll go first [16:33] I'm in the happy place this week [16:34] you do indeed look happy [16:34] I'm working on an apaprmor-easyprof-ubuntu upload which should finish out all the policy/reserved vs common policy groups/etc. I'm waiting for bug #1231863 to be fixed before uploading [16:34] bug 1231863 in ubuntu-ui-toolkit (Ubuntu Saucy) "Local Sqlite databases are still created/stored in incorrect location" [Critical,Triaged] https://launchpad.net/bugs/1231863 [16:34] heh [16:34] I also am doing stuff with appstore reviews this week-- various updates for recent changes [16:35] including working with SDK team on filing path bugs against apps now that they are fixed [16:35] "now that they are fixed" referes to the path bugs being fixed in the sdk [16:35] \o/ [16:36] but apps are now broken-- so I am going to enumerate them [16:36] also continue various followups on https://bugs.launchpad.net/bugs/+bugs?field.tag=application-confinement bugs [16:36] I have some patch piloting to do [16:37] and think there is a decent chance I might pick up an update this week [16:37] * jdstrand_ crosses fingers [16:37] mdeslaur: you're up [16:37] I'm on triage this week [16:37] I have a short week as I'm off thursday and friday [16:37] I'm about to push out a few USNs [16:37] and I have a bunch more in our PPA that are in the testing phase [16:38] I may get to a couple more before thursday [16:38] that's about it [16:38] sbeattie: you're up [16:38] I'm on apparmor again this week, trying to offload work from jjohansen [16:39] I'm poking at the very early ipc prototype kernel he got me, now that I finally got it booting :/ [16:39] I also need to followup with jdstrand on the hardware apparmor policy proposal he had made earlier. [16:40] and I need to track down why the parser commits broke both my jenkins build and the daily apparmor ppa builds [16:40] uh oh [16:40] I think it's the newly added dependency on libapparmor for the parser build [16:41] (but we don't need to solve that here) [16:41] I think that's it for me; tyhicks, you're up [16:41] oh, yeah likely, sorry [16:41] I'm testing dbus, apparmor, and evince uploads that fix several bugs [16:41] One of the fixes in dbus-daemon looks like it may affect some of the dbus policy in apparmor-easyprof-ubuntu, so I'll need to coordinate w/ jdstrand [16:41] Then I've got an embargoed issue to work on [16:41] Then I've got one more dbus bug to fix (bug #1229280) [16:42] bug 1229280 in dbus (Ubuntu) "Eavesdroppers confined with AppArmor can see all method_return and error messages" [High,Triaged] https://launchpad.net/bugs/1229280 [16:42] I think that's it for me [16:43] jjohansen: you're up [16:44] I'll be working on more apparmor IPC mediation this week [16:45] hrmm I think that is about it for me sarnold your up [16:45] jjohansen, oh, i've been looking at your earlier ping [16:46] I'm not sure sarnold is here yet. chrisccoulson feel free to go ahead [16:46] (hello :) [16:46] jjohansen, http://hg.mozilla.org/releases/comm-esr24/rev/16e20df57d08 is what removed the ability to set the Follow-Up header [16:46] anyway [16:47] chrisccoulson: thanks for looking [16:47] this week, i'll hopefully be getting back to my oxide bug / feature list :) [16:47] sarnold: ah, didn't see you come in :) [16:47] jdstrand_: heh, that was me coming in :) sorry. [16:47] no need to be sorry [16:47] we've got pretty good test coverage for the actual API now, although i'm still adding bits (and fixing bugs as I find them) [16:47] i think that's me done [16:48] chrisccoulson: any progress on the nss ftbfs? [16:48] although I guess it's a little late now to get it in saucy [16:49] mdeslaur, oh, i need to get back to that. sorry. i've got my pandaboard all set up here again now so I've got a bit more flexibility with the test environment [16:49] chrisccoulson: cool, thanks [16:49] i planned to roll back some of the recent updates to see when it fails. the main suspects are gcc, binutils and eglibc, which were all updated since the last time it worked [16:51] * mdeslaur rolls dice [16:51] gcc! [16:51] heh [16:51] mdeslaur, it doesn't matter which one it is. they're all doko's packages anyway :) [16:51] that's why i picked them out as suspects ;) [16:52] (just kidding btw) [16:52] heh [16:52] chrisccoulson: did you have more to report? [16:52] hehe [16:53] jdstrand_, no, i'm done [16:53] sarnold: you're up [16:53] I'm on community this week, and have two more MIR audits to finish up, MIR and open-vm-tools; I would very much like to do both of them this week, but Mir is a large and complicated codebase, I may not make enough progress to finish both this week. [16:53] s/MIR and/Mir and/ [16:54] at least the unity-system-compositor was written in idiomatic c++11, which isn't one of my strong languages, so the going was slower than I'd like. [16:54] but hey I'm getting to learn c++11 while I'm at it, and that's fun. :) [16:55] I think that's it for me, jdstrand_ back to you [16:55] :) [16:55] sarnold: you've been redefining the word "fun" again, haven't you? :) [16:55] * jdstrand_ hugs sarnold [16:55] sarnold, want to port chromium to c++11? [16:55] sarnold: when you're done, can you teach me those bits of c++11? [16:56] mdeslaur: he overloaded the fun operator. [16:56] return True; [16:56] mdeslaur: lol :) yes, just operator_fun() { ... } and away you go! [16:56] chrisccoulson: nothanks :) [16:56] heh [16:56] [TOPIC] Highlighted packages === meetingology changed the topic of #ubuntu-meeting to: Highlighted packages [16:57] i really want to be able to use final and override [16:57] http://people.canonical.com/~ubuntu-security/cve/pkg/argyll.html [16:57] http://people.canonical.com/~ubuntu-security/cve/pkg/passenger.html [16:57] http://people.canonical.com/~ubuntu-security/cve/pkg/gridengine.html [16:57] http://people.canonical.com/~ubuntu-security/cve/pkg/salt.html [16:57] http://people.canonical.com/~ubuntu-security/cve/pkg/openswan.html [16:57] 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. [16:57] See https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures for details and if you have any questions, feel free to ask in #ubuntu-security. To find out other ways of helping out, please see https://wiki.ubuntu.com/SecurityTeam/GettingInvolved. [16:57] [TOPIC] Miscellaneous and Questions === meetingology changed the topic of #ubuntu-meeting to: Miscellaneous and Questions [16:57] Does anyone have any other questions or items to discuss? [17:07] mdeslaur, sbeattie, tyhicks, jjohansen, sarnold, ChrisCoulson: thanks [17:07] #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 documentation: https://wiki.ubuntu.com/meetingology [17:07] Meeting ended Mon Sep 30 17:07:54 2013 UTC. [17:07] Minutes (wiki): http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-09-30-16.32.moin.txt [17:07] Minutes (html): http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-09-30-16.32.html [17:07] thanks jdstrand_ [17:07] thanks jdstrand_ :) === jdstrand_ is now known as jdstrand [17:07] thanks jdstrand! [17:08] jdstrand: thanks! === psivaa is now known as psivaa-afk [19:58] stgraber, soren, kees, cjwatson: meeting in 2 mins? [19:58] yep, I'll be there [19:59] Here [20:01] cjwatson chaired last time AFAICS, so kees today? [20:01] and as he seems absent, I guess it's my turn [20:02] #startmeeting [20:02] Meeting started Mon Sep 30 20:02:39 2013 UTC. The chair is pitti. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [20:02] Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired [20:02] pitti, hi [20:02] hey mdz, how are you? [20:02] busy! :-) [20:03] #topic action review === meetingology changed the topic of #ubuntu-meeting to: action review [20:03] do we have quorum today? [20:03] Martin Pitt to contact Mark Shuttleworth to organise nominations and elections [20:03] done [20:03] mdz: 4 members, so yes [20:03] ah great [20:03] kees still wanted to review MREs, no visible progress there [20:03] re nominations [20:04] #topic TB elections === meetingology changed the topic of #ubuntu-meeting to: TB elections [20:04] I guess the plan is to renew just those members who haven't declared an intent to stand down? [20:04] o/ [20:04] oh, hey kees [20:04] as in, temporarily extend terms pending elections [20:04] yeah, so no progress on MRE review. still need to gather bug details. it is not trivial :) [20:04] cjwatson: I actually meant it "extend membership of the whole board for a month" [20:04] cjwatson: but if you want to leave now, that's fine too [20:05] I'm just concerned that suddenly nobody of us would have tb powers any more, which makes some things difficult [20:05] (cleaning up MPs and similar) [20:05] just wondering if I get to stop turning up to Monday evening meetings ... ;-) [20:05] cleaning up MPs - I think core-dev can do that now [20:05] given that ~ubuntu-branches > ~ubuntu-core-dev [20:05] cjwatson: well, you can :) [20:06] cjwatson: oh, good [20:06] I agree that the TB slots in Launchpad shouldn't be left unstaffed [20:06] I got infinity to add me to ~launchpad-buildd-admins, though, so I think that's the main TB power I use routinely [20:06] do we need to have offset terms for the incoming folks? [20:06] If there are others, I would be interested to discover them :-) [20:07] kees: Seems unnecessary [20:08] ok, other than that I guess we need to wait on sabdfl's reply on a candidate list now, and the actual elections [20:08] #topic Requiring TB members to be Ubuntu core developers === meetingology changed the topic of #ubuntu-meeting to: Requiring TB members to be Ubuntu core developers [20:09] just as some people already said by mail, I generally agree that TB members *should* be core devs [20:09] o/ [20:09] but I'm not even sure whether we can even instantiate that requirement [20:09] Sorry I'm late. [20:09] given that ultimately sabdfl decides on the nominations [20:09] My feeling on this is that it can be left up to the good sense of the electorate, given (a) a reasonable slate of nominees and (b) a secret ballot so that there's no undue pressure [20:09] why should this be different than any other board? [20:10] we could, as a TB, give him a recommendation to consider core-devs only [20:10] micahg-work: how do you mean? [20:10] I agree that it's a reasonable default, but I can easily imagine exceptions, and indeed some were suggested [20:10] no other board is "core dev only" [20:10] why not making it a requirement, and then if it needs to be violated, that can be discussed at the time. [20:10] cjwatson: I did a milestone cleanup last week which IIRC requires TB privileges so we're good for a bit [20:10] well, to have prerequisites in terms of who can serve [20:11] stgraber: Yeah, that and I suspect that I may run into something with packagesets but we'll see [20:11] even the CC has a public nominations period [20:11] cjwatson: oh yeah, good point, that's one TB-related right I use quite a bit [20:11] micahg-work: I think we can have recommendations and/or requirements [20:11] (for those that aren't DMB owned) [20:11] stgraber: It might be ~ubuntu-archive. I'll find out [20:11] sorry [20:11] it just feels odd to me that an existing board can restrict its own successors [20:11] getting 2 topics crossed here [20:12] What I mean is, I think we can have core-dev as a soft requirement / recomendation, without having to make it a rule and then argue about violations [20:12] micahg-work: that's fine, your's is the current one [20:12] no, I meant I was bringing up 2 topics :) [20:12] let's focus on the core dev issue first [20:12] pitti: heh, British constitutional principle [20:13] so, maybe I should ask the CC to make it a requirement if the TB doesn't feel it has the right to do so [20:13] by the same reason we coudl decide that members must only be "pitti", "cjwatson", "kees", and so on [20:13] I still haven't understoo the motivation, to be honest. [20:13] micahg-work: In my case, it's not that I don't think the TB has the right, it's that I think it shouldn't make it a hard rule [20:13] micahg-work: Furthermore, the CC does not have authority over the TB [20:13] but still, if there's a very active MOTU with a good technical understanding and he gets a majority of ubuntu dev's trust, why not [20:13] I thought the CC has some authority as the ultimate community governance structure [20:13] The governance structure has the CC and TB at the same level, under sabdfl [20:14] If sabdfl and the everyone who can vote wants someone to be in the TB who isn't a core-dev... Why not? [20:14] I was there when it was written [20:14] ok, I guess that's good to know then [20:14] This is news to me, too. I thought CC>TB. [20:14] also, if someone is a very active, say ~ubuntu-desktopper [20:14] soren: Right, this is my "set general principle but let the electorate decide" preferred approach [20:14] cjwatson, I recall sabdfl remembering differently and/or wanting to change that, a while back [20:14] (we have package sets now) [20:15] cjwatson: Right. That's what I tried to express in my e-mail as well, but you managed it much more eloquently :) [20:15] mdz: Well, if so, I don't think http://www.ubuntu.com/about/about-ubuntu/governance implies that right now ... [20:16] (And I think it would be unfortunate) [20:17] cjwatson, I agree [20:17] micahg-work: under the circumstances (no majority for a requirement, and doubts that we even have the ability to make it a requirement), would you settle for the TB giving this as a reocmmendation to sabdfl? [20:17] at least on the former. I should probably be neutral on the latter [20:18] FWIW, the current set of nominees being tossed around in private mail doesn't include any non-core-devs, I believe; I don't know if sabdfl has other ideas [20:18] pitti, if that's the best I can get, I guess I"ll take it [20:18] but I was very concerned with the last election [20:18] it seemed to be too close for comfort [20:18] right, and admittedly I used ~core-dev/+members as input for my own recommendations [20:18] micahg-work: Was it really a problem, given that the electorate made its feelings clear? [20:19] * soren tries to recall the last election.. [20:19] cjwatson, I don't want it to get to a point where it is a problem [20:19] I'm in favor of fewer rules where guidelines and judgment suffice [20:20] The non-dev candidates in the last election placed 10th and 13th [20:20] I don't recall exactly who was core-dev at the time but I think all the top 9 were [20:20] oh, hrm, I thought one placed 7th [20:20] if I"m misremembering, I guess it might be a non-issue after all [20:20] micahg-work: No, history from LP is clear that that wasn't the case [20:20] http://www.cs.cornell.edu/w8/~andru/cgi-perl/civs/results.pl?id=E_3896e483ca548c95 if anyone else wants to data-mine [20:21] ok, must have been thinking of something else then [20:21] Looks like all of 1-9, 11, 12 were core-dev at the top [20:21] then, I guess the recommendation will suffice [20:21] *time [20:21] * soren doesn't recall whether Clint was core-dev at the time, tbh. [20:21] I'm pretty sure he was [20:22] soren: He was, by a few months [20:22] https://launchpad.net/~ubuntu-core-dev/+members has joining dates [20:22] cjwatson: Are those trustworthy? It used to show the date when someone applied for membership, not when they were approved. [20:23] Bah. It doesn't matter. [20:23] I'n not certain. Could check, but not within meeting time :-) [20:23] ok, I think that suffices then, thank you all [20:24] soren: In Clint's case, -devel-announce archives confirm that it was approval date [20:24] so is everyone ok with an explicit recommendation about core-dev to sabdfl? [20:24] +1 [20:24] or any new/other discussion aspects? [20:24] +1 [20:25] soren, kees, mdz: opinions? [20:25] +0 [20:25] (mdz is actually an interesting case as he voluntarily stepped out of core-dev) [20:25] I'll support the consensus [20:26] +1 [20:26] and collective wisdom via vote should do the rest :) [20:26] I think it's worth asking the question, it would be unusual I agree [20:26] +1 [20:27] unusual> Yes, I'm definitely in favour of it as a default and as a (strong) recommendation, just have qualms about it as a hard requirement [20:27] +1 [20:28] ack, thanks [20:28] #topic Provisional MRE Request For KDE Telepathy === meetingology changed the topic of #ubuntu-meeting to: Provisional MRE Request For KDE Telepathy [20:28] (via email) [20:29] this seems rather obvious to me really, as these are now under the KDE microrelease policy [20:29] and don't influence other flavours [20:29] yeah [20:30] any objections? [20:30] Nope. [20:30] nope; I'm for it. [20:30] ack, so granted (will do bureaucracy after meeting) [20:31] #topic ML scan === meetingology changed the topic of #ubuntu-meeting to: ML scan [20:31] Oh, I thought I'd replied to that by mail [20:31] nothign else that I can see [20:31] I agree, the MRE looks like an easy signoff [20:31] https://bugs.launchpad.net/ubuntu-community/+bugs?field.assignee=techboard -> zarro [20:31] #topic Select a chair for the next meeting === meetingology changed the topic of #ubuntu-meeting to: Select a chair for the next meeting [20:31] kees: would you do the honors? [20:31] kees: (as it would have been your turn today) [20:32] yup! [20:32] sorry about being late :( [20:32] np [20:32] #topic AOB === meetingology changed the topic of #ubuntu-meeting to: AOB [20:32] o/ [20:32] micahg-work: go ahead [20:33] so, I was wondering why there was no public call for nominations for the TB this time around, ISTR one happening last time [20:35] I'm not sure whether there is a final nomination list already, so far Mark just asked for some recommendations from the current TB [20:35] right, I saw that [20:35] The nomination process is running rather behind, of course [20:35] I think partly because Mark was on holiday [20:36] ok, ISTR dholbach gathering nominations [20:36] https://lists.ubuntu.com/archives/ubuntu-devel-announce/2011-September/000895.html [20:38] I'll forward that question to Mark, CC'ing the list (need to write him anyway for the core-dev recommendation) [20:38] the CC just had a public call for nominations as well: https://lists.ubuntu.com/archives/community-announce/2013-September/000013.html [20:39] I think it'd be a good idea, although bearing in mind that we're late [20:40] AOB 2? [20:40] going once.. [20:40] twice.. [20:41] #endmeetnig [20:41] #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 documentation: https://wiki.ubuntu.com/meetingology [20:41] Meeting ended Mon Sep 30 20:41:21 2013 UTC. [20:41] Minutes (wiki): http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-09-30-20.02.moin.txt [20:41] Minutes (html): http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-09-30-20.02.html [20:41] thanks everyone! [20:41] thanks pitti [20:41] * cjwatson waves [20:41] thanks pitti! [20:41] thanks! [21:09] ok, all mopped up I think [21:09] good night [21:57] Could a tech board member check the emails requiring moderation on their list. It did not make the meeting and does not appear on the web based list archive. Thanks.