=== noy_ is now known as noy === doko_ is now known as doko === jjohansen is now known as jj-afk === Ursinha is now known as Ursinha-brb === wendar is now known as allison === allison is now known as wendar === Ursinha-brb is now known as Ursinha === wendar is now known as allison === UndiFineD is now known as hajour1 === jj-afk is now known as jjohansen === allison is now known as wendar [18:05] hi! [18:06] hello! [18:06] hey [18:07] #startmeeting [18:07] Meeting started at 12:07. The chair is jdstrand. [18:07] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [18:07] [LINK] https://wiki.ubuntu.com/SecurityTeam/Meeting [18:07] LINK received: https://wiki.ubuntu.com/SecurityTeam/Meeting [18:07] [TOPIC] Review of any previous action items [18:07] New Topic: Review of any previous action items [18:07] \o [18:07] there are none from our last meeting [18:07] [TOPIC] Weekly stand-up report [18:07] New Topic: Weekly stand-up report [18:07] I'll go first [18:08] I have a pending update [18:08] a lot of email to get through (still behind) [18:08] I've got another training session this week [18:08] I need to prepare for the rally [18:08] and (finally, for real) talk with jjohansen about dbus/apparmor [18:09] * jdstrand hugs jjohansen [18:09] that's it from me [18:09] hehe [18:09] kees: you're up (and welcome back!) [18:10] thanks! [18:10] well, I will be catching up for a while. I'm also on triage, and will be continuing to review some of the kernel CVE states with apw [18:10] things are in good shape overall, though. lots of stuff in pending. :) [18:11] that's it from me. [18:12] mdeslaur: you're up [18:12] my turn? [18:12] hehe [18:12] So, I'm off thursday and friday [18:12] kees: re pending> that's great news. I know everyone has been working hard on that [18:13] :) [18:13] until then, I plan on figuring out how to test the logrotate updates I've prepared [18:13] and will continue going down the list of CVEs [18:13] that's it from me [18:14] sbeattie: you're up [18:14] I'm on community this week. [18:15] I have an issue to followup with upstream on re: last week's openjdk update [18:15] I also have 2 embargoed issues that I'm working on. [18:16] and I need to spend a bit of time prepping for the rally. [18:16] That's it for me. [18:16] micahg: you're next [18:16] I have Mozilla updates this week (hopefully going out tomorrow) including the Firefox 5 transition in Natty [18:17] I expect a chromium update this week since it's been a while [18:17] then webkitgtk 1.2.7 time permitting [18:17] I think that's it === hajour1 is now known as UndiFineD [18:18] cool [18:18] [TOPIC] Miscellaneous and Questions [18:18] New Topic: Miscellaneous and Questions [18:19] as micahg mentioned, he is doing a mozilla 5.0 transition in natty this week. it would be good if all of us could be running the new firefox packages in -proposed (I mention -proposed cause there are langpacks in -proposed hat aren't in the ubuntu-mozilla-security ppa) [18:20] I started testing this morning, and it seems solid [18:20] I think sbeattie has been running it for a while [18:20] anyhoo, feel free to test :) [18:20] cool, will do [18:20] (thanks for that sbeattie) [18:20] yeah been running it since last weekend, I got it through -proposed. [18:20] err s/weekend/week/ [18:21] one thing that I noticed over the weekend was arkose (http://www.stgraber.org/2011/06/14/app-containing-on-the-modern-linux-desktop/) which is stgraber's lxc work [18:23] it sounds interesting and I'd like for our team to talk with stgraber and wendar next week tolearn more about it, see how it can work with apparmor, and what we as apparmor upstream can learn or take from his approach. also to see how this might tie into ARB [18:23] I don't expect any new work items per se, but maybe info sharing and inspiration [18:24] mdeslaur: I noticed that you marked the apparmor profiles wiki page as 'done'. where is that? [18:25] jdstrand: http://wiki.apparmor.net/index.php/Main_Page#Profiles [18:26] mdeslaur: cool-- do you have a plan on when you are going to announce it? [18:26] jdstrand: nope [18:26] mdeslaur: would it be worthwhile talking about that next week? [18:27] I was debating whether it should be on a standalone page, so the url will be better once I add it to the user space tools [18:27] jdstrand: I can add it to the schedule if you'd like [18:27] mdeslaur: thanks. +1 for standalone page, but we can discuss more next week [18:28] jdstrand: added to schedule [18:28] cool [18:28] mdeslaur: I'm imagining as things flesh out, a standalone page will be needed, but for now it's sufficient. [18:28] that's it from me for now [18:28] sbeattie: well, I'd like to get a URL that will stay the same for the user space tools [18:28] does anyone have any other questions or items to discuss? [18:29] oh, I forgot to mention I'll be going through applicants this week [18:30] alrighty then [18:30] kees, mdeslaur, sbeattie, micahg, jjohansen: thanks! [18:30] #endmeeting [18:30] thanks [18:30] Meeting finished at 12:30. [18:30] thanks jdstrand [18:31] woo, thanks! [20:01] persia, Laney, bdrung: ping? [20:01] o/ [20:01] pong :) [20:03] stgraber: thanks for the pointer btw [20:03] o/ [20:03] np [20:03] o/ everyone [20:03] need 4 for quorum right? [20:03] yep [20:04] cody-somerville: ping [20:04] hi all [20:04] thanks. i cant remember all the members of both boards im on :) [20:04] maco: poked geser in -devel [20:05] Laney said he wouldn't be around, hopefully one of the others will show up [20:05] I'm here. [20:05] yeah! [20:07] #startmeeting [20:07] Meeting started at 14:07. The chair is maco. [20:07] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [20:07] Welcome to the Developer Membership Board meeting [20:08] Agenda is here: [20:08] [link] https://wiki.ubuntu.com/DeveloperMembershipBoard/Agenda [20:08] LINK received: https://wiki.ubuntu.com/DeveloperMembershipBoard/Agenda [20:08] oh good, it doesnt mind lowercase [20:08] [topic] James Page's application for Server package set [20:08] New Topic: James Page's application for Server package set [20:08] Hi All [20:09] details of my app are here : https://wiki.ubuntu.com/JamesPage/ServerDeveloperApplication [20:09] [link] https://wiki.ubuntu.com/JamesPage/ServerDeveloperApplication [20:09] LINK received: https://wiki.ubuntu.com/JamesPage/ServerDeveloperApplication [20:09] Want to introduce yourself a bit? [20:10] OK; so I've been contributing to Ubuntu as a member of the Ubuntu Server team since September last year [20:10] (shortly before I started to work for Canonical) [20:10] jamespage: i see java in there. are you interested in Eclipse? ;) [20:10] As a reminder, here's the server package set: http://paste.ubuntu.com/629984/ [20:10] stgraber, kudos [20:11] a bdrung points out quite a bit about java in my app; and this is my background before I started contributing to Ubuntu [20:11] stgraber: would be nice if this was exposed in LP's UI :-/ [20:11] (and yes I am interested in eclipse) [20:11] stgraber: ant1.7 is in there, but not ant? [20:11] bdrung: apparently :) some packagesets are weird. You'll also note that tomcat isn't in there... [20:12] jamespage: we need more manpower for eclipse. feel free to join #debian-java on OFTC and/or #eclipse-linux on freenode after the meeting if you are interested [20:12] bdrung: ack - I'll drop by [20:13] maco: indeed. At the moment you need to use edit_acl.py from lp:~ubuntu-archive/ubuntu-archive-tools/trunk/ unless someone added it somewhere on LP and I missed it :) [20:13] stgraber: why is gimp in there? [20:13] bdrung: oh, fun :) no idea [20:13] bdrung: I guess we may want to poke cjwatson to get that package set cleaned up a bit :) [20:14] bdrung: and make sure whatever jamespage needs is in there (if it's in the ubuntu-server scope) [20:14] I asked once about gimp already as I spotted it too [20:14] it's autogenerated [20:14] I'm not going to do single-package cleanups [20:14] IIRC it is correct but I don't remember the reason, might be a (build-)dependency [20:15] afk for a few minutes (there is a bothersome interrupt) [20:15] gimp will be there for (build-)dependency closure reasons [20:15] stgraber: yeah i know, but for example i was trying to find a list of all the package sets (and i thought someone had pastebinned it at an earlier meeting but couldnt find it), and a page to point people to "pick the one that fits" rather than "get this script and do a thing" (which i couldnt get it to do anyway)... [20:15] so although my core competency is Java; I have worked extensively with non-Java technology on Linux as well [20:15] jamespage, Are most of the uploads that have been sponsored for you thus far been just bug fixes? [20:16] cjwatson: is there any documentation on how the package sets are currently autogenerated? (or the scripts used for that) [20:16] cody-somerville: yes they have; you should see more new packages from me this cycle whilst I work to get jenkins into the archive [20:16] in particular, one of the gimp libraries is a build-dependency of gutenprint, which is supported as part of print-server [20:16] stgraber: just mailing list stuff really [20:17] I did do one new package last cycle to support the server team effort packaging cobbler [20:17] jamespage, How familiar are you with versioning of SRU packages? [20:17] s/packages/uploads/ [20:18] cody-somerville: so I have done a few SRU's; I followed the versioning advice as advised in the documented process [20:18] i.e. .X version ontop of the release version [20:18] * bdrung is back. [20:19] there are a few examples with links on my application [20:20] jamespage, If you were doing an SRU to upload a number of bug fixes from the development focus, how might you version an upload to several older releases? Feel free to create and describe an entirely imaginary situation that demonstrate your strong understanding. [20:21] jamespage, and for kicks, assume that two of the releases you wish to perform an SRU for have the same version of the package. [20:22] so I would identify the latest point release in each of the older releases (including the ones which have the same version of the package) [20:23] prepare a updated packages based on the branch for each release; using the currentpointrelease+1 increment on the version number and identifying the -proposed pocket for the release [20:24] * jamespage takes a second to thing about the instances with the same version [20:25] so as I've never actually come across this situation the first thing I would do is seek guidance [20:26] however I would have thought that I would need to prepare point release updates for each instance (again marking for -proposed); unless its possible to prepare it once and then sync to the second release with the same version of the package [20:26] you need to prepare an update for each instance [20:27] I thought so; I was not aware of any such sync process [20:27] what's the problem in this case? can you imagine a solution? [20:28] additional question: which version would you use for SRUing 1.2-3? [20:30] so the issue I could see with the releases with the same version would be around the updates not getting through to proposed at the same time; I could see that this could create some odd versioning issues say if 1.2-3ubuntu1.1 got into an earlier release prior to it hitting a later release [20:31] I would probably look to ensure that the verification process followed made sure that these drop's hit at the same/similar time into -updates [20:32] jamespage, You wouldn't be able to upload the same version to the later release. It would be rejected. [20:32] are you familiar with how archive.ubuntu.com works? specifically /pool? if so, you should see the problem in what you just said :) [20:33] right; so using the same release number in both of the updates create a conflict hence the rejection [20:33] yep [20:33] stgraber: its not an area I have alot of experience in [20:34] so how would you work around that limitation? to have the same update hit two versions of ubuntu while avoiding the version conflict and without breaking dist-upgrade to the next relesae? [20:34] *release [20:35] so understanding that constraint I would use a lower point release number in the earlier release [20:36] if the base version was 1.2-3ubuntu1 I would use say 1.2-3ubuntu1.1.1 in the earlier version [20:36] and 1.2-3ubuntu1.2.1 in the later version to avoid the versioning conflict [20:37] jamespage, what if the version after has 1.2-3ubuntu1.2 already? [20:37] infact you could use the release numbers to good effect here [20:37] (s/version/next release/ [20:38] 1.2-3ubuntu1.2.10.04 and 1.2-3ubuntu1.2.10.10 say [20:38] bingo [20:38] well, move the .2 to the end, but yeah [20:38] right - gotcha [20:38] jamespage: which version would you use for SRUing 1.2-3? [20:39] and then that can be increments as required [20:39] 1.2-3ubuntu0.1 [20:39] XubuntuY.10.04.1 and XubuntuY.10.10.1 is how https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging shows [20:39] (bookmark that link, btw, very handy) [20:39] or in the instance of dual versions ubuntu0.10.04.1 and ubuntu0.10.10.1 [20:40] i always forget the layout of the security changelog entry [20:40] Alternatively, I think I've seen the use of tilde and the release codename + X [20:40] maco- thanks for the link [20:40] cody-somerville: that's for backports, i believe [20:40] (that hangs of the SRU page right?) [20:40] hopefully the sru page links to it... [20:41] yes it does - just checked [20:41] maco, I think I've seen similar notation be used when there are already 'point releases' so you can't just shift the the numbers around [20:41] cody-somerville: also, it'll create a problem when we loop from z back to a [20:41] maco, if the upstream versions has never changed, yes :P [20:42] cody-somerville: between z and a it might not, assuming we don't go into a new charset :P [20:42] using the year won't lead to problem for my generation (2100) [20:43] jamespage, Do you collaborate and interact frequently with community developers at all? [20:45] cody-somerville: so I do hang out on ubuntu-server and ubuntu-devel; although I would have to admit that my interaction with community developer in Ubuntu has not been large [20:45] on Java related packaging stuff I have had more interaction with the debian-java team [20:47] done with questions yet? [20:47] No further questions from me. [20:47] yes [20:47] I would like to add that James Page does indeed rock. His recent NEW packages which i sponsored into Oneiric were faultless. Sailed through the queue. He is pushing his work into Debian concurrently. He is a good cookie. [20:48] * stgraber is ready to vote [20:48] [vote] James Page's server package set application [20:48] Please vote on: James Page's server package set application. [20:48] 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 [20:48] E.g. /msg MootBot +1 #ubuntu-meeting [20:48] +1 [20:48] +1 received from maco. 1 for, 0 against. 0 have abstained. Count is now 1 [20:48] (Also noticed him working with various upstreams to get them to resolve licencing issues.) [20:48] +1 (likes the Debian involvement) [20:48] +1 received from bdrung. 2 for, 0 against. 0 have abstained. Count is now 2 [20:49] +1 [20:49] +1 received from stgraber. 3 for, 0 against. 0 have abstained. Count is now 3 [20:50] cody-somerville, geser? [20:50] +1 [20:50] +1 received from cody-somerville. 4 for, 0 against. 0 have abstained. Count is now 4 [20:50] +1 [20:50] +1 received from geser. 5 for, 0 against. 0 have abstained. Count is now 5 [20:50] [endvote] [20:50] Final result is 5 for, 0 against. 0 abstained. Total: 5 [20:50] congrats jamespage! [20:50] jamespage: congrats [20:51] \o/ [20:51] thankyou! [20:51] [topic] Marc Cluet's Contributing Developer application [20:51] New Topic: Marc Cluet's Contributing Developer application [20:51] hi everyone [20:51] my application is here https://wiki.ubuntu.com/MarcCluet/UbuntuContributingDeveloper [20:51] [link] https://wiki.ubuntu.com/MarcCluet/UbuntuContributingDeveloper [20:51] LINK received: https://wiki.ubuntu.com/MarcCluet/UbuntuContributingDeveloper [20:52] lynxman: please introduce yourself [20:52] I'm Marc Cluet, I'm working for Canonical in Corporate Services [20:52] With negronjl we form the Systems Integration team [20:53] Our goal is to integrate into Ubuntu new solutions for servers both cloud and metal based [20:53] Right now our main project is Orchestra [20:53] This has allowed me to collaborate both with the communities surrounding puppet and mcollective and at the same time Puppet Labs [20:54] I've also registered patches and pushed new versions for mcollective and rabbitmq plugins [20:54] (all through sponsorization) [20:54] Right now finishing the last details to get also mcollective-plugins in the Oneiric archive [20:55] My collaborations are mainly with the Ubuntu Server team [20:55] In you "What I like least in Ubuntu" section, you mention the review process. Do you think the patch pilot program is helping improve that or are we still missing something? [20:56] *your [20:56] stgraber: It does help, I do still think that the big problem is not enough man hours to review all the packages in the queue [20:57] stgraber: To help with that process I've also subscribed to ~ubuntu-sponsors to get better reviews of my work and learn faster, trying to commit as few errors as it can be [20:57] i see only one package appearing on https://launchpad.net/~lynxman/+uploaded-packages - do you have pointers to the bugs that were sponsored? [20:58] bdrung: Let me look for them, one sec [20:59] https://launchpad.net/ubuntu/+source/rabbitmq-stomp/2.4.1+hg20110525-0ubuntu1 [20:59] DEBEMAIL mismatch :( [21:00] bdrung: https://launchpad.net/ubuntu/+source/mcollective/1.2.0-0ubuntu1 was completely done on my own, with sponsorship from zul [21:01] lynxman: it fails to build. how can you ensure that this won't happen again? [21:02] bdrung: I always build all my new packages first locally then on a PPA, run through Lintian checks to make sure all is good [21:02] bdrung: once the packages pass all the checks I submit them for sponsoring [21:02] lynxman: you should go to https://launchpad.net/~marc-cluet and request to merge the two accounts so all your work does actually show under your account. [21:02] how do you build it locally? with debuild? [21:02] bdrung: I used to use dpkg-buildpackage but now I'm using debuild that runs lintian at the end [21:03] Ampelbein: thank you for pointing that out, I'll make sure to ask for the account merge :) [21:04] lynxman: i recommend to use pbuilder / sbuild or similar before the upload (or instead of using a PPA). this gives a minimal chroot similar to the official builders [21:04] bdrung: I'm also using pbuilder or sbuild for a clean chroot, learning all the tools of the trade [21:04] bdrung: jinx :) [21:05] what's your relation to Debian? [21:06] lynxman, Do you collaborate and interact frequently with community developers at all? [21:06] bdrung: I had no relation with debian before except personal friendships with some of the debian packagers, i also did run some serves on debian and submitted bug reports [21:08] cody-somerville: I do specially when I'm creating packages for the software that the community is based around, this has been the case with mcollective in special [21:09] cody-somerville: I hang regularly in the #mcollective channel, submit bugs upstream and help other developers and users to smooth their experience of mcollective in Ubuntu [21:09] cody-somerville: I also hang both in #ubuntu-server and #ubuntu-devel regularly [21:09] lynxman, So mostly upstream collaboration? [21:09] cody-somerville: yes [21:10] cody-somerville: I do want to try to push the rabbitmq plugins to Debian as well since there's no maintainer for them right now [21:10] lynxman: what do you think about getting packages into Debian first and getting changes into Debian? [21:10] lynxman, Do you have any examples of collaboration with Ubuntu MOTU, Ubuntu Core Developers, or Debian Developers that you're proud of and can share with us? [21:10] cody-somerville: yes, I've had interaction with smoser adding features to cloud-init [21:11] cody-somerville: also collaborated very closely with zul, kirkland and Daviey for both mcollective and rabbitmq plugins [21:11] lynxman, Was that work you did as part of your job? [21:12] (if it was, its not a strike against you - I'm just curious). [21:12] cody-somerville: part of it was, but I also submitted more useful features or patches that were out of my project requirements [21:12] cody-somerville: specially for the mcollective-provisioner, I've been collaborating very closely with RI Pienaar (Volcane on Freenode) on that piece of code on my free time [21:13] cody-somerville: I also want to get the rabbitmq plugins in Debian so mcollective can work well in debian (and replace activemq with rabbitmq there) [21:13] cody-somerville: so I expect my work in Ubuntu making mcollective work smoothly to benefit Debian too [21:14] i have no more questions [21:14] * stgraber is ready to vote [21:14] cody-somerville: all of this is extra curricular to my work, which is just to integrate mcollective into Orchestra and Ubuntu [21:15] everyone else ready to vote? [21:15] [vote] Marc Cluet for contributing developer [21:15] Please vote on: Marc Cluet for contributing developer. [21:15] 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 [21:15] E.g. /msg MootBot +1 #ubuntu-meeting [21:17] +1 [21:17] +1 received from maco. 1 for, 0 against. 0 have abstained. Count is now 1 [21:17] everybody waiting for someone else to go first? [21:17] +1 for ubuntu-contributor [21:17] +1 received from bdrung. 2 for, 0 against. 0 have abstained. Count is now 2 [21:17] +1 (sorry got distracted) [21:17] +1 received from stgraber. 3 for, 0 against. 0 have abstained. Count is now 3 [21:17] -1 - Although on the right path, I don't think lynxman meets the minimum standards per current precedent for contributing developer. [21:17] -1 received from cody-somerville. 3 for, 1 against. 0 have abstained. Count is now 2 [21:17] +0 [21:17] Abstention received from geser. 3 for, 1 against. 1 have abstained. Count is now 2 [21:18] [endvote] [21:18] Final result is 3 for, 1 against. 1 abstained. Total: 2 [21:19] cody-somerville: "minimum standards per current precedent for contributing developer"?...really? lol [21:20] split vote...how do these work again? [21:20] i remember one meeting ending in a debate on how split votes go [21:20] (a few years ago) [21:20] where are these current precedents? are they objectively documented? [21:20] maco: IIRC he needs 4 +1s. (but that's really IIRC :)) [21:21] stgraber: based on what ratio? [21:21] 4 out of 7 is enough [21:21] => more than 50% [21:21] stgraber: yeah the debate i remember was "does it need to come out positive or does it need to come out to quorum-number-of-+1-votes?" [21:21] Daviey: DMB has 7 members [21:21] there's only 5 votes [21:21] 3 out of 5 is 60% [21:22] hmm? didn't it used to work that someone needs a final 'score' of +4? [21:22] * micahg thought the requirement was +4, but that just comes from an outsider observer [21:22] I also remember us asking the members who couldn't make it to vote on the mailing-list [21:22] wow, this uncertainity is quite unfair to put on a potential contributing developer who is clearly waiting on the edge of his seat. [21:22] highvoltage: that sounds reasonable, when 7 sitting council members actually attend and vote [21:23] quorum-number-of-+1-votes is stronger than positive [21:23] +3 -1 = +2, positive, no? [21:23] IIRC, the other DMB members where asked to vote per email [21:24] The vote can be taken to mailing list to ask the other members to vote. If they both +1 then the applicant is accepted AFAICT. [21:24] cody-somerville: thatd work [21:24] one +1 would be enough [21:24] kirkland: the debate is whether that's enough. majority of quorum v. majority of board [21:25] when this came up in '08 or '09, i remember crimsun mentioning how the MC handled it, but its been long enough ive forgotten again [21:25] bdrung, How so? That would only bring the vote to +3. +4 is required. [21:26] cody-somerville: that would bring us to 4x +1 and 1x -1 [21:26] 4x +1 is enough even if 3x -1 are there, isn't it? [21:27] bdrung, -1 cancels out one of the +1s as we've discussed and agreed before IIRC. [21:27] cody-somerville: but then you still end up with the majority of the entire board having voted +1 [21:27] we need to write down how this works [21:27] maco: I think it's sad that a fraction of the board shows up for the meeting that candidates clearly work toward and prepare for [21:28] kirkland: quorum is 4. we'd never have a meeting if all 7 had to be free every time, especially with timezones [21:29] kirkland: you should replace board members who stay away for two consecutive meetings without apologies! [21:29] maco: and a single down vote can take a candidate down [21:29] maco, I move that we take this discussion to the mailing list. We can more easily bring up prior discussion + votes there. [21:29] *sigh* [21:29] maco: particularly when that downvote is quite predictably linked to @canonical.com addresses [21:29] geser: Would you like to expand on your +0? [21:29] ~/win 3 [21:30] kirkland: i dont think there's any sort of pattern to suggest that @canonical folks are "predictably" downvoted [21:30] [action] Conclude Marc Cluet's vote on Permissions mailing list [21:30] ACTION received: Conclude Marc Cluet's vote on Permissions mailing list [21:31] thank you guys for your time, I'll keep an eye on the mailing list traffic for the final vote [21:31] [action] Figure out majority-of-quorum versus majority-of-board and document it somewhere [21:31] ACTION received: Figure out majority-of-quorum versus majority-of-board and document it somewhere [21:31] and now that it's been an hour and a half... [21:31] #endmeeting [21:31] Meeting finished at 15:31. [21:31] thanks! [21:31] sad. [21:32] https://wiki.ubuntu.com/DeveloperMembershipBoard/Logs is not up-to-date [21:32] I still think we should get persia and Laney to vote on lynxman's application [21:33] bdrung: how so? (still waiting for wiki to load :)) [21:33] oh, right, forgot to add a link to the minutes of last meeting ... why do we have to update so many pages? [21:33] the latest entry is 2011-05-09 [21:33] I already added our last meeting to the team reports... [21:34] we need some tools doing all the annoying stuff [21:34] +1 [21:34] Daviey: sure, mostly the short time of contributions (and the few sponsored uploads, but I just see that through the account merging some more uploads appeared), so my vote would be +0.5 (I'm still on the edge) [21:34] stgraber: i'm emailing the Permissions list right now so persia and Laney can vote [21:34] kirkland: please keep in mind the DMB is staffed by volunteers and people try their best to attend [21:34] geser: Thanks. Appreciated. [21:35] bdrung: updated [21:35] maco: thanks [21:36] found a +3 vote in http://irclogs.ubuntu.com/2011/01/31/%23ubuntu-meeting.html#t19:16 [21:36] which was continued via email [21:36] stgraber: I started the log page because I needed several time to look up something in a log of a previous meeting and had to count backwards to find the date of a previous meeting to be able to find the log in irclogs.u.c [21:37] geser: ok, I just wasn't aware of it :) I'm adding it to the post-meeting todolist so hopefully we won't forget about it [21:37] that's if the wiki finally lets me edit the DMB agenda page ... [21:39] email sent [21:39] ok, updated post-meeting todolist === tremolux_ is now known as tremolux === AlanChicken is now known as AlanBell === Ursinha` is now known as Ursinha === Ursinha is now known as Guest75959 === fader_` is now known as fader_ === Guest75959 is now known as Ursinha === Ursinha is now known as Guest67245 === Guest67245 is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha [23:59] I find the second guessing and sideline sniping to be rather disappointing.