=== cking_ is now known as cking
[13:51] <bdrung> !dmb-ping: meeting in ten minutes
[13:51] <ubottu> bdrung: I am only a bot, please don't think I'm intelligent :)
[13:51] <bdrung> !dmb-ping
[13:51] <ubottu> bdrung, cody-somerville, Laney, micahg, barry, tumbleweed, stgraber: DMB ping
[13:51] <bdrung> meeting in ten minutes
[13:51]  * barry pongs
[13:51] <cody-somerville> Sorry, won't be able to make today's meeting
[13:52] <barry> cody-somerville: np.  i think we'll have quorum anyway, if bdrung isn't a bot too :)
[13:52] <tumbleweed> hi
[13:53] <bdrung> barry: my circuits can't answer this question ;)
[13:53] <barry> oh noes, i've shorted out the bdrungbot
=== Guest52991 is now known as mfisch
[14:00] <barry> #startmeeting
[14:00] <meetingology> Meeting started Mon Jul 30 14:00:13 2012 UTC.  The chair is barry. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[14:00] <meetingology> 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
[14:00] <micahg> barry: starting a minute early? :)
=== mfisch is now known as Guest54314
[14:00] <barry> hello and welcome to this week's developer membership board meeting.  do we have quorum?
[14:00] <tumbleweed> micahg: your clock is off
[14:00] <barry> micahg: it's all relative :)
[14:01] <barry> micahg: is in a gravitational well
[14:01]  * micahg fires up the warp engines
[14:01] <barry> #link https://wiki.ubuntu.com/DeveloperMembershipBoard/Agenda
[14:02]  * stgraber waves
[14:02]  * bdrung waves mechanically.
[14:03] <barry> shall we wait a minute or two to see if Laney shows up?
[14:03] <Laney> soryr
[14:03] <Laney> i am here
[14:03] <Laney> just twiddling a bug, one sec
[14:03] <barry> yay!  welcome everyone
[14:03] <barry> #topic review of previous action items
=== meetingology changed the topic of #ubuntu-meeting to: review of previous action items
[14:04] <barry> micahg to document the zentyal packageset
[14:04] <barry>  
[14:04]  * micahg hides
[14:04] <barry> continued then :)
[14:04] <bdrung> micahg: should we dig out the last meeting logs? ;)
[14:04] <barry> micahg to start a discussion on dmb@ about whether PPU should confer membership
[14:05] <micahg> bdrung: no :)
[14:05] <barry> i think that one's done, right?
[14:05] <micahg> barry: that was done already
[14:05] <barry> as was this one: get consensus whether upload rights should confer membership
[14:05] <barry> ?
[14:05] <bdrung> did we got to a consensus?
[14:06] <micahg> no, beuno was supposed to start that discussion
[14:07] <ScottK> Isn't that backwards?
[14:07] <barry> micahg: does he know that?  i did a quick review of my thread on that to the dmb list and see nothing about beuno
[14:07] <ScottK> Membership has certain requirements and the question is if you can get upload rights if you don't meet those.
[14:07] <micahg> barry: I think that was part of the CC discussion we had about 3.5 weeks ago
[14:08] <barry> micahg: k.  so i should continue this item.  should i put bueno's name next to it?
[14:08] <tumbleweed> and one of us should take an action to prod him
[14:09] <micahg> barry: http://irclogs.ubuntu.com/2012/07/16/%23ubuntu-meeting.html#t19:11
[14:09] <bdrung> shouldn't we come to a proposed change to discuss with the CC?
[14:09] <Laney> ScottK: backwards how?
[14:09] <ScottK> How can giving upload rights confer membership?
[14:10] <ScottK> Membership has certain requirements and either you meet them or you don't.
[14:10] <barry> micahg: will you mind pinging him about it?
[14:10] <ScottK> The question is can you have upload rights if you aren't a member/don't meet requirements.
[14:10] <tumbleweed> membership of the ubuntu-dev LP group gives indirect membership of the ubuntu-members group
[14:10] <ScottK> Which is a bug.
[14:11] <micahg> barry: I suppose
[14:11] <Laney> that's what we're cosnidering.
[14:11] <ScottK> CC owns membership requirements, not DMB.
[14:11] <barry> micahg: thanks
[14:11] <micahg> scottK: depends who you ask :), that's the issue, we didn't come to a consensus before
[14:11] <Laney> and why we're asking a CC member to start this thread ...
[14:11] <tumbleweed> ScottK: which is why we took it to them
[14:11] <ScottK> Ah.
[14:12]  * barry will change the action item to just the ping; and we'll let beuno and the cc take it from there
[14:12] <tumbleweed> but in the past, we've kind of waived the "significant and sustained contributions" bit of the membership requirements, for some PPU applications
[14:12] <tumbleweed> anyway, probably best not to have this discussion here and now :)
[14:12] <ScottK> OK.
[14:12] <barry> #topic Review any packageset descriptions that have been received (micahg)
=== meetingology changed the topic of #ubuntu-meeting to: Review any packageset descriptions that have been received (micahg)
[14:13] <micahg> barry: carried, I'll try to get that rolling by the end of next month
[14:13] <barry> micahg: thanks
[14:13] <barry> #topic package sets
=== meetingology changed the topic of #ubuntu-meeting to: package sets
[14:13] <barry> anything new there?
[14:13]  * barry thinks not
[14:13] <micahg> no, no one applying
[14:14] <bdrung> no, that's why it hasn't any subpoints
[14:14] <barry> tumbleweed reminds me of one other action item not on the wiki page:
[14:14] <barry> extra action item review item: Any progress on the ubuntu developers woh haven't signed the CoC?
[14:16] <micahg> well, we get an update weekly now, but haven't yet contacted the members in question
[14:16] <tumbleweed> sounds like the answer there is action: micahg
[14:17] <barry> yep.  micahg let us know if you want to off load some of that
[14:17] <barry> #topic PerPackageUploader Applications
=== meetingology changed the topic of #ubuntu-meeting to: PerPackageUploader Applications
[14:17] <micahg> ok
[14:17] <barry> matttbe ping
[14:17]  * matttbe waves
[14:17] <matttbe> Hello evryone!
[14:18] <barry> matttbe: welcome.  you're applying for ppu in cairo-dock cairo-doc-plug-ins and latexila, right?  can you tell us something about yourself?
[14:18] <matttbe> yes. sure!
[14:18] <barry> #link https://wiki.ubuntu.com/matttbe/PerPackageUploaderApplication
[14:19] <matttbe> Firstly, I want to apology for my "not so good" English, I hope it's readable ;)
[14:19] <bdrung> matttbe: it was.
[14:19] <matttbe> So... I'm Matthieu Baerts, student at UCL (in Belgium -- and no, sorry but I can't send you any Belgian beers, you'll have to come here for the next FOSDEM meeting :P ).
[14:19] <tumbleweed> awww
[14:19] <matttbe> I'm also a member of the Cairo-Dock team and other projects which support Free Software
[14:20] <matttbe> (I'm a member of a LUG (LouviLug) and I joined the Louvain-li-Nux association which promotes Free Software through Ubuntu's installations, weekly supports to the community and event's organizations 2 years ago).
[14:20] <matttbe> I've been working on Cairo-Dock packages since September 2009 and on LaTeXila packages since March 2011.
[14:21] <matttbe> I want to apply for upload rights for Cairo-Dock and LaTeXila packages because I *think* I'm starting to "annoy" my sponsors with these 'simple' releases :) (and mainly because Andrew Starr-Bochicchio told me that it was maybe a good idea to have these rights to upload directly these packages in order to not lose time)
[14:22] <matttbe> I think that's it :) But feel free to ask me for other things :)
[14:22] <barry> matttbe: is there a cairo ppa and have you done any uploads to it?
[14:23] <bdrung> matttbe: you are involved with the upstream projects and i saw that new package version closes bunches of Launchpad bugs. do you collaborate with our direct upstream Debian?
[14:23] <Laney> There's some disagreement / difference with Debian that was supposed to get resolved IIRC
[14:23] <matttbe> sure!
[14:23] <matttbe> I'm a member of cairo-dock-team and I maintain these ppa: https://launchpad.net/~cairo-dock-team/+archive/ppa and https://launchpad.net/~cairo-dock-team/+archive/weekly
[14:24] <barry> s/cairo/cairo-dock/
[14:24] <matttbe> + repos for Debian on http://download.tuxfamily.org/glxdock/repository/
[14:25] <matttbe> In fact, we have some troubles with our Debian maintainers :-/
[14:25] <matttbe> We already report bugs to them but it's hard to change things
[14:25] <matttbe> (as you can see there: https://bugs.launchpad.net/ubuntu/+source/cairo-dock-plugins/+bug/657564 )
[14:25] <ubottu> Launchpad bug 657564 in cairo-dock-plugins (Ubuntu Oneiric) "Duplicated package with cairo-dock-plugins (coming from Debian)" [Undecided,Confirmed]
[14:26] <matttbe> They decided to split all our plugins but it's hard to maintain that (there are a few dependences), they also add useless dependences and made 1 or 2 wrong patches but now it's a bit better ;)
[14:27] <bdrung> matttbe: have you tried to join the Debian Cairo-dock Maintainers team and do your packaging work in their git repositories?
[14:27] <matttbe> yes, I did it but they don't want to have the same packages than what we have in Ubuntu
[14:28] <bdrung> matttbe: is there no way to come to a consensus?
[14:29] <micahg> matttbe: as long as they add the appropriate interdependencies and have a meta package to install all the plugins, what's the issue?
[14:29] <matttbe> I know that it's an annoying problem but with other members of Cairo-Dock team, we already tried. This is now better and I think we can say that there is no way to come to a consensus about these dependences
[14:30] <micahg> matttbe: can you give an example of a "useless dependency"?
[14:30] <matttbe> micahg: yes, now they have a meta package but no appropriate interdependencies (and if you install Cairo-Dock on Debian, it will install thunar-data, kde stuff, etc. which are just useless if you're using Gnome)
[14:32] <tumbleweed> have bugs been filed in debian about this?
[14:32] <matttbe> (cairo-dock package depends of cairo-dock-plugins meta package which depends of cairo-dock-xfce-integration-plug-in package which install thunar dependences)
[14:32] <matttbe> tumbleweed: yes of course
[14:34] <matttbe> tumbleweed:  on https://bugs.launchpad.net/ubuntu/+source/cairo-dock-plugins/+bug/657564 and there I think: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=493736
[14:34] <ubottu> Launchpad bug 657564 in cairo-dock-plugins (Ubuntu Oneiric) "Duplicated package with cairo-dock-plugins (coming from Debian)" [Undecided,Confirmed]
[14:34] <bdrung> matttbe: i can't see an open bug report for that in the BTS
[14:34] <ubottu> Debian bug 493736 in wnpp "ITP: cairo-dock -- An light eye-candy fully themable animated dock for any Linux desktop" [Wishlist,Fixed]
[14:34] <micahg> matttbe: actually, it seems the meta package isn't pulled in by the -plugins package
[14:34] <matttbe> (and also on our forums)
[14:35] <micahg> the integration meta I mean
[14:35] <matttbe> maybe I should re-open a new bug report...
[14:35] <micahg> matttbe: I think the issue has been solved
[14:35] <matttbe> micahg: oh, maybe, good news :)
[14:36] <barry> do we have any other questions for matttbe?
[14:36] <micahg> matttbe: have you considered levering the backports pocket to provide stable updates?
[14:36] <micahg> *leveraging
[14:37] <matttbe> micahg: except that now, it doesn't install any -integration plug-ins (for a better integration in Gnome, XFCE, KDE and other DE which use gvfs) :)
[14:38] <micahg> matttbe: right, you could suggest an alternate Recommends with a sane default maybe
[14:39] <matttbe> micahg: I don't understand your question, sorry. Did you mean that it can be good to backport stable update?
[14:39] <micahg> matttbe: yes, backports is enabled by default since oneiric
[14:40] <micahg> matttbe: you might want to look at the requestbackport tool in ubuntu-dev-tools in precise and later
[14:41] <matttbe> micahg: ok, thank you. I'll have a look to this tool
[14:42] <bdrung> matttbe: i recommend to look at the wrap-and-sort tool (in devscripts and ubuntu-dev-tools previously)
[14:42] <matttbe> bdrung: oh, nice tool (as many other but there are a lot of tools like that :) )
[14:43] <matttbe> thank you
[14:44] <bdrung> matttbe: i saw that indicator-applet 0.5.0-0ubuntu2 failed to build (https://launchpad.net/ubuntu/+source/indicator-applet/0.5.0-0ubuntu2). how could that happen and what are you doing to prevent this to happen in the future?
[14:46] <matttbe> bdrung: Yes, I thought that it was enough to only test the modification in the apport hook :)
[14:46] <matttbe> But next time, I'll build the new version with pbuilder
[14:47] <matttbe> bdrung: but I fixed the bug in the next version and report the problem to indicator-applet devs
[14:48] <bdrung> matttbe: better be save than sorry. the build failure was introduced by a glib change and not by you. that's why test building should be always done before uploading.
[14:49] <stgraber> matttbe: are you subscribed to ubuntu-devel-announce@lists.ubuntu.com and read it at least daily?
[14:49] <matttbe> stgraber: I'm subscribed recently :)
[14:51] <matttbe> (stgraber: I'll read it at least daily but currently I only received maximum one or two messages)
[14:51] <stgraber> yeah, it's very low trafic but very important messages
[14:52] <stgraber> so should be read pretty quickly after something new is posted to it (like the freeze announcements)
[14:52] <bdrung> matttbe: it's good to check that before doing an upload (e.g. for freeze notifications)
[14:53] <matttbe> bdrung: ok, I'll do that. (and I've also bookmarked this link: https://wiki.ubuntu.com/QuantalQuetzal/ReleaseSchedule )
[14:53] <barry> #voters barry bdrung Laney micahg tumbleweed stgraber cody-somerville
[14:53] <meetingology> Current voters: Laney barry bdrung cody-somerville micahg stgraber tumbleweed
[14:53] <barry> #vote grant matttbe ppu rights to cairo-dock cairo-dock-plug-ins latexila
[14:53] <meetingology> Please vote on: grant matttbe ppu rights to cairo-dock cairo-dock-plug-ins latexila
[14:53] <meetingology> 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)
[14:54] <tumbleweed> +1 [ and I'd like to see these packages eventually get in sync with debian ]
[14:54] <bdrung> +1 please work with the Debian maintainers to reduce the diff between Debian and Ubuntu
[14:54] <meetingology> +1 [ and I'd like to see these packages eventually get in sync with debian ] received from tumbleweed
[14:54] <meetingology> +1 please work with the Debian maintainers to reduce the diff between Debian and Ubuntu received from bdrung
[14:55] <barry> +1 i would also like to see you work toward an eventual sync w/debian
[14:55] <meetingology> +1 i would also like to see you work toward an eventual sync w/debian received from barry
[14:55] <stgraber> +1
[14:55] <meetingology> +1 received from stgraber
[14:55] <micahg> +0 good work overall, would like to see more integration with Debian (it seems all the issues have been addressed)
[14:55] <meetingology> +0 good work overall, would like to see more integration with Debian (it seems all the issues have been addressed) received from micahg
[14:55] <Laney> +0 sorry have been distracted
[14:55] <meetingology> +0 sorry have been distracted received from Laney
[14:56] <matttbe> tumbleweed, bdrung, barry: yes, you're right. I'll re-contact Cairo-Dock Debian team!
[14:56] <micahg> err...+1
[14:56] <matttbe> (BTW I see that I'm still a member of this team ^^ https://alioth.debian.org/projects/pkg-cairo-dock/ )
[14:57] <bdrung> matttbe: i recommend to work with them in their git repository and merge the Ubuntu changes step by step (starting with the easy bits)
[14:57] <matttbe> bdrung: ok, I'll try to do that!
[14:58] <micahg> +1
[14:58] <meetingology> +1 received from micahg
[14:58] <barry> #endvote
[14:58] <meetingology> Voting ended on: grant matttbe ppu rights to cairo-dock cairo-dock-plug-ins latexila
[14:58] <meetingology> Votes for:5 Votes against:0 Abstentions:1
[14:58] <meetingology> Motion carried
[14:58] <barry> matttbe: congratulations!
[14:58] <bdrung> matttbe: in most cases it is a pleasant experience to work with Debian Developers
[14:58] <matttbe> Thanks all!
[14:59] <matttbe> bdrung: yes, sure I also want to have "better" packages in Debian but... I'll try :)
[14:59] <matttbe> Also I've two tiny questions: about Ubuntu Membership and the previous discussions, should I do something more to have this membership?
[14:59] <barry> #topic Ubuntu Core Developer Applications
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Core Developer Applications
[14:59] <tumbleweed> you'll get automatic membership, as things stand ATM
[14:59] <matttbe> tumbleweed: ok, thank you :)
[15:00] <barry> tumbleweed: welcome! you are applying to ubuntu core developer.  do you want to introduce yourself? :)
[15:00] <micahg> matttbe: try to keep in mind, it might be possible to satisfy your wants/needs as well of those of the other Debian packagers
[15:00] <tumbleweed> barry: sure. I'll try and be quick, and we're already out of time
[15:00] <barry> thanks
[15:00] <tumbleweed> #link https://wiki.ubuntu.com/StefanoRivera/CoreDevApplication
[15:00] <tumbleweed> meh, meetingology doesn't like me
[15:00] <tumbleweed> anyway
[15:01] <tumbleweed> you had better all know me, I serve on this board :)
[15:01]  * barry thinks #links aren't working
[15:01] <tumbleweed> so, I mostly do universe stuff, but occasionally touch something that's in main
[15:02] <tumbleweed> I don't have many endorsements, because I've had no regular sponsors. The 2/3 of the bulk sponsors endorsed me
[15:02] <tumbleweed> the other sponsors all only sponsored one upload
[15:02] <tumbleweed> but back to core-dev: I'd appreciate not having to go through the sponsorship process to touch main packages
[15:03] <tumbleweed> I haven't had significant feedback from a sponsor in ages, and don't think I'm benefiting from not having direct upload rights
[15:03] <tumbleweed> ..
[15:03] <Laney> \o
[15:04] <Laney> Can we learn anything from the Debian release team on how to run freezes?
[15:04] <tumbleweed> lol
[15:04] <Laney> re your first point of hate
[15:04] <Laney> :-)
[15:04] <bkerensa> :s
[15:04] <tumbleweed> I think there are pople in debian who ignore the release team and upload big things to unstable, without coordination
[15:05] <tumbleweed> so, that point of hate probably applies there, too
[15:05] <Laney> For example they are almost completely opposed to us on their opinion of new packages; who's right there?
[15:05] <tumbleweed> I think they have a far higher workload than we do
[15:05] <tumbleweed> tehy review every diff, and prod maintainers with RC bugs continuously
[15:06] <tumbleweed> whereas we trust our developers to only fix bugs after FF
[15:06] <tumbleweed> I think our approach makes far more sense for our tight release cycle
[15:06] <bdrung> where there abuses of this trust?
[15:06] <tumbleweed> sure, there always are a few. but that's actually not a problem
[15:07] <tumbleweed> as long as everything doesn't blow up, it worked, right?
[15:07] <bdrung> the impact of the abuses are small enough to warrant a lightweight process?
[15:07] <tumbleweed> yeah, exactly
[15:08] <tumbleweed> we have a continuous stream of people coming and asking "what's the latest they can get their new shiny thing into the release" and the only sane answer is "it gets harder. try and do it before FF, but if you can't it's not the end of the world"
[15:08] <tumbleweed> new packages have a very hard time breaking everything
[15:08] <micahg> well, with backports on by default, that issue is less pressing
[15:09] <tumbleweed> sure, although I beleive we have yet to test that process
[15:09] <bdrung> is backport working well nowadays?
[15:10]  * tumbleweed isn't on the backports team, but from what I see, yes. Aside from our sbuild being ancient and not letting things B-D on backports
[15:10] <micahg> I think it's working much better than in the past, we're mainly blocked on human reviews, but I don't think they're excessive
[15:10] <bdrung> then i should try it again.
[15:10] <micahg> I think we're getting a lot more backport requests for precise which is good news
[15:11] <Laney> well, it's the best time for it
[15:11] <Laney> we've constructed the system to make it become increasingly painful as releases go on
[15:13] <tumbleweed> yes, but (re FFes) people still turn up very late in the cycle with things that *have to* go in
[15:13] <tumbleweed> some of them being common sense, but big diffs
[15:13] <micahg> yes, but the case of the FFes, people usually only want for that release, so backporting from the next dev release isn't much of an issue
[15:13] <barry> there's nothing like a freeze or rc to motivate people to finish their work <wink>
[15:13] <tumbleweed> and others a dependancy of the latest greatest thing that someone really wants in the release
[15:15] <tumbleweed> micahg: if you have to put a whole stack of important-stuff in backports because it didn't make FF, that will probably mean less users
[15:15] <tumbleweed> the big thing in the last cycle was MAAS, I don't think that could have happily ended up in backports, rather than release
[15:15] <tumbleweed> but I also wasn't involved in approving that :)
[15:17] <micahg> tumbleweed: does core-dev to you just mean being able to upload everywhere in the main archive?
[15:17] <tumbleweed> micahg: well, technically, of course it does
[15:17] <tumbleweed> but there are packages I wouldn't touch without very good reason to
[15:17] <ScottK> tumbleweed: It's not clear it was ready to be in the archive at all (at least technically)
[15:18] <tumbleweed> many of the core packages have someone that mostly looks after them. I'd coordinate with taht person, if at all possible
[15:18] <tumbleweed> (someone or some team)
[15:19] <tumbleweed> and I don't expect being a core-dev to make a major difference to what I work on, but it would allow me to scratch a few itches a little more easily
[15:19] <tumbleweed> ScottK: which wouldn't be unsuprising for something arriving at the last minute
[15:19] <tumbleweed> *suprising, even
[15:21] <micahg> tumbleweed: yes, but what about the non-technical side of core-dev :)
[15:22] <micahg> ah, you answered it
[15:22] <tumbleweed> not entirely
[15:23] <tumbleweed> non-technically, it also honours one as being someone who feels responsible for the entire archive, and takes a leading role in Ubuntu
=== Guest54314 is now known as mfisch
[15:23] <tumbleweed> I'd like to think that I do both of those things, even if it's a leading role in one corner of Ubuntu :)
[15:23] <barry> tumbleweed: ubuntu is a big room with lots of corners that need sweeping :)
[15:24] <barry> #vote grant tumbleweed ubuntu core dev membership
[15:24] <meetingology> Please vote on: grant tumbleweed ubuntu core dev membership
[15:24] <meetingology> 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)
[15:24] <stgraber> +1
[15:24] <meetingology> +1 received from stgraber
[15:24] <bdrung> +1
[15:24] <meetingology> +1 received from bdrung
[15:24] <barry> +1
[15:24] <meetingology> +1 received from barry
[15:24] <Laney> +1
[15:24] <meetingology> +1 received from Laney
[15:24] <tumbleweed> \o/
[15:24] <ScottK> tumbleweed: Congratulations.
[15:25] <tumbleweed> ScottK: thanks
[15:25] <Laney> \o/
[15:25] <bdrung> tumbleweed: congrats
[15:25] <barry> #endvote
[15:25] <meetingology> Voting ended on: grant tumbleweed ubuntu core dev membership
[15:25] <meetingology> Votes for:4 Votes against:0 Abstentions:0
[15:25] <meetingology> Motion carried
[15:25] <barry> tumbleweed: congratulations!
[15:25] <stgraber> didn't we miss micahg?
[15:26] <micahg> oh, sorry, got distracted, +1000 :)
[15:26] <tumbleweed> heh
[15:26] <barry> oh whoops.
[15:26] <stgraber> good ;)
[15:26] <stgraber> tumbleweed: congrats!
[15:26] <tumbleweed> thanks everyone
[15:26] <barry> #topic next meeting chair
=== meetingology changed the topic of #ubuntu-meeting to: next meeting chair
[15:26] <barry> bdrung is up next i believe
[15:27] <bdrung> barry: nope. i was last time.
[15:27] <barry> ah, then cody-somerville ?
[15:27] <bdrung> yes
[15:28] <barry> cool.
[15:28] <bdrung> he can't veto ;)
[15:28] <barry> #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
[15:28] <meetingology> Meeting ended Mon Jul 30 15:28:38 2012 UTC.
[15:28] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-07-30-14.00.moin.txt
[15:28] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-07-30-14.00.html
[15:28] <matttbe> (sorry, I was too slow to write my second question. Where can I ask this question?)
[15:28] <matttbe> Do you think that I can join Ubuntu Contributing Developers team? It's mainly to show to other Ubuntu devs that it's not my first package but I'm (still) not a MOTU so please have a look ;)
[15:28] <matttbe> (I saw that I should have demonstrated 'significant and sustained' contributions in the area of UbuntuDevelopment, but I don't know what that means :) )
[15:28] <barry> thanks everyone!
[15:29] <tumbleweed> matttbe: I'd think so, yes
[15:29] <tumbleweed> matttbe: however, most of the point of becoming a contributing developer is to get membrship through packaging
[15:30] <tumbleweed> which you've just got with your PPU rights
[15:30] <matttbe> tumbleweed: oh ok. Thank you for these details :)
[15:30] <tumbleweed> joining contributing developers wouldn't grant you anything at all. It'd just be an LP team tha you are part of
[15:30] <matttbe> ok
=== Quintasan_ is now known as Quintasan
=== shadeslayer is now known as shadeslayer_
=== shadeslayer_ is now known as shadeslayer
[18:02] <jjohansen> o/
[18:02] <jdstrand>  \o
[18:03] <jdstrand> #startmeeting
[18:03] <meetingology> Meeting started Mon Jul 30 18:03:05 2012 UTC.  The chair is jdstrand. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[18:03] <meetingology> 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
[18:03] <jdstrand> The meeting agenda can be found at:
[18:03] <jdstrand> [LINK] https://wiki.ubuntu.com/SecurityTeam/Meeting
[18:03] <jdstrand> [TOPIC] Announcements
=== meetingology changed the topic of #ubuntu-meeting to: Announcements
[18:03] <jdstrand> Thanks to bdrung for his help on security updates for the community supported vlc last week. Your work is very much appreciated and will keep Ubuntu users secure. Great job! :)
[18:03] <jdstrand> [TOPIC] Review of any previous action items
=== meetingology changed the topic of #ubuntu-meeting to: Review of any previous action items
[18:03] <jdstrand> actually, don't have any of those
[18:03] <jdstrand> [TOPIC] Weekly stand-up report
=== meetingology changed the topic of #ubuntu-meeting to: Weekly stand-up report
[18:04] <jdstrand> I'll go first
[18:04] <jdstrand> I'm in the happy place this week
[18:04] <jdstrand> I've got to finish up community work from last week
[18:04] <jdstrand> I've also been working almost exclusively on MIR audits
[18:05] <jdstrand> I have a couple/few left, but it is slow going cause I need a functional openstack and that has proved elusive on quantal
[18:05] <jdstrand> I should also get started on the hiring process for our open generalist position
[18:06] <jdstrand> once my audits are done, I hope to dig into my webkit maintenance investigation
[18:06] <jdstrand> and get back to my pending updates
[18:06] <jdstrand> mdeslaur: you're next
[18:09] <mdeslaur> whoops, sorry
[18:10] <mdeslaur> I'm working on nss updates
[18:10] <mdeslaur> and will pick something else from the list
[18:10] <mdeslaur> I'm also on triage this week
[18:10] <mdeslaur> that,s about it. sbeattie, you're up
[18:10] <sbeattie> I'm in the happy place this week.
[18:10] <sbeattie> I've got two embargoed issues on my plate
[18:11] <sbeattie> I've also got a openstack issue that I need to test.
[18:11] <sbeattie> Once I've cleared those, I'm planning to get back to the apparmor dbus stuff.
[18:11] <sbeattie> I may also pick up another one from the list.
[18:12] <sbeattie> That's it from me.
[18:12] <sbeattie> micahg: you're up
[18:13] <micahg> still working on webkit, will be taking back Mozilla pretesting from tyhicks, precise should be promoted to -updates/-security this week barring any issues (I haven't heard anyone scream yet)
[18:13] <micahg> I guess that's it for me
[18:13] <tyhicks> I'm handling community this week
[18:14] <tyhicks> I'm currently working on some upstream auditd patches to disable network listening support. They should go out to the list today.
[18:14] <jdstrand> micahg: what about the other releases? istr you saying those were going to hit this week
[18:15] <micahg> jdstrand: yeah, hoping to drop oneiric and natty into proposed this week, going a little slower than I'd hoped
[18:15] <jdstrand> micahg: but you've got a handle on it?
[18:15] <micahg> jdstrand: yeah
[18:15] <jdstrand> ok cool
[18:16] <jdstrand> tyhicks: did you manage to talk to upstream auditd about the network stuff?
[18:16] <tyhicks> jdstrand: No, but it is straight forward so I'd like to start the conversation with the patch set
[18:16] <jdstrand> I see
[18:16] <jdstrand> thanks
[18:16] <jdstrand> sorry for the interruption
[18:17] <tyhicks> jdstrand: There are a few existing examples of other features (such as GSSAPI) that get flicked on and off at build time. I followed them.
[18:17] <tyhicks> I have an eCryptfs pull request that I need to prepare and send to Linus. Shouldn't take long, just need to get to it.
[18:17] <tyhicks> Then my focus will be on updates
[18:17] <tyhicks> That's it for me
[18:18] <tyhicks> jjohansen: you're up
[18:18] <jjohansen> well I have some dbus patch fixes to finish up so sbeattie can finish getting a ppa together.
[18:19] <jjohansen> Hopefully I'll get some patch review feedback this week that I can roll in to the current patchset, and I have the locking update to finish off
[18:20] <jjohansen> oh and I suppose it will be back to the stacking work after that
[18:20] <jjohansen> jdstrand: back to you
[18:21] <sbeattie> jjohansen: yeah, sorry, I'm trying to get to reviewing those patches as well.
[18:21] <jdstrand> [TOPIC] Highlighted packages
=== meetingology changed the topic of #ubuntu-meeting to: Highlighted packages
[18:21] <jjohansen> sbeattie: heh I know :)
[18:21] <jdstrand> 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.
[18:21] <jdstrand> 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.
[18:21] <jdstrand> http://people.canonical.com/~ubuntu-security/cve/pkg/bcfg2.html
[18:21] <jdstrand> http://people.canonical.com/~ubuntu-security/cve/pkg/ax25-tools.html
[18:21] <jdstrand> http://people.canonical.com/~ubuntu-security/cve/pkg/mysql-gui-tools.html
[18:21] <jdstrand> http://people.canonical.com/~ubuntu-security/cve/pkg/libpar-perl.html
[18:21] <jdstrand> http://people.canonical.com/~ubuntu-security/cve/pkg/gksu-polkit.html
[18:22] <jdstrand> [TOPIC] Miscellaneous and Questions
=== meetingology changed the topic of #ubuntu-meeting to: Miscellaneous and Questions
[18:22] <jdstrand> There are a lot of merge opportunities for packages listed in http://people.canonical.com/~ubuntu-security/d2u/. Performing these updates is a great way to help Ubuntu and bolster your developer application.
[18:25] <jdstrand> mdeslaur, sbeattie, micahg, tyhicks, jjohansen: thanks!
[18:25] <jdstrand> #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
[18:25] <meetingology> Meeting ended Mon Jul 30 18:25:30 2012 UTC.
[18:25] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-07-30-18.03.moin.txt
[18:25] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-07-30-18.03.html
[18:25] <micahg> thanks jdstrand
[18:25] <tyhicks> thanks!
[18:25] <mdeslaur> thanks jdstrand!
[18:25] <sbeattie> jdstrand: thanks!
[18:25] <jjohansen> thanks jdstrand
[18:26] <jdstrand> np
=== LordOfTime is now known as Guest41633
[20:35] <uros1> Any member of council present, need some help here
[20:35] <soren> Which council?
[20:36] <uros1> LoCo
[20:36] <uros1> About ReApproval issue
[20:37] <pleia2> might be best to email loco-council@lists.ubuntu.com
[20:38] <uros1> ok tnx
[20:44] <bkerensa> uros1: or try #ubuntu-locoteams :D
[20:47] <czajkowski> uros1: I'm about if I can help
[20:47] <czajkowski> pm me if needed