/srv/irclogs.ubuntu.com/2013/06/17/#ubuntu-meeting.txt

=== marlinc is now known as marlinc|away
=== marlinc|away is now known as marlinc
=== Sarvatt is now known as Sarvatt_
=== Logan_ is now known as Guest912
smartboyhwNoskcaj10, I will review your testcase branches post-lunch.03:51
smartboyhwrather, post-piano lesson...03:52
=== Noskcaj10 is now known as Noskcaj
=== greyback is now known as greyback|lunch
=== greyback|lunch is now known as greyback
=== mmrazik_ is now known as mmrazik
=== mmrazik is now known as mmrazik|afk
=== mmrazik|afk is now known as mmrazik
=== mmrazik is now known as mmrazik|afk
=== dholbach_ is now known as dholbach
jjohansen\o16:32
tyhickshello16:32
mdeslaur\o16:32
jdstrandhi!16:32
jdstrand#startmeeting16:32
meetingologyMeeting started Mon Jun 17 16:32:56 2013 UTC.  The chair is jdstrand. Information about MeetBot at http://wiki.ubuntu.com/meetingology.16:32
meetingologyAvailable 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 #votesrequired16:32
jdstrandThe meeting agenda can be found at:16:32
jdstrand[LINK] https://wiki.ubuntu.com/SecurityTeam/Meeting16:32
jdstrand[TOPIC] Announcements16:33
=== meetingology changed the topic of #ubuntu-meeting to: Announcements
jdstrandStefan Bader (smb) provided debdiffs for precise-raring for xen. Your work is very much appreciated and will keep Ubuntu users secure. Thanks!16:33
jdstrand[TOPIC] Weekly stand-up report16:33
=== meetingology changed the topic of #ubuntu-meeting to: Weekly stand-up report
chrisccoulsonhi16:33
jdstrandI'll go first16:33
jdstrandI'm on triage this week16:34
jdstrandI will finish the preliminary install audit of the phablet image this week16:34
jdstrandI have some pending updates16:34
jdstrandand need to review sbeattie's deliverables for the month and plan for getting them finished since he is on holiday16:35
jdstrandmdeslaur: you're up16:35
mdeslaurI'm on community this week16:35
mdeslauram currently testing an embargoed issue16:35
mdeslaurand will write a test for libraw16:35
mdeslaurwill go down the list of updates after that16:36
mdeslaurthat's pretty much it16:36
mdeslauruh...who's usually after steve... tyhicks?16:36
tyhicksyep16:36
tyhicksI'm currently drafting an email to the apparmor list to push the dbus syntax discussions along16:37
tyhicksI hope that we can come to a decision on that and I can make the parser changes for that this week16:37
* sarnold dons asbestos ..16:38
jdstrandso16:39
jdstrandwith sbeattie out, I wonder if we can actually take a decision16:39
tyhicksI'll also be going through my todo list of trivial things that needs to be fixed/improved in the dbus and apparmor packages as we get closer to upstreaming those and sticking them in the archive16:39
tyhicksjdstrand: I expected more people to chime into your question on proposal 3 vs 416:39
jdstrandme too :\16:40
tyhicksjdstrand: but, I feel like there's still a lean towards 316:40
tyhickswhich is sbeattie's proposal16:40
tyhicksThat's it for me16:41
tyhicksjjohansen: you're up16:41
jdstrandbecause that didn't happen and steve is on vacation, I don't think we can take a decision and complete that work item16:41
jdstrandwait16:41
tyhicksah16:41
tyhickssorry16:41
jdstrandbefore we get to jjohansen16:41
jdstrandjjohansen: opinion? ^16:41
jjohansenjdstrand: well likely not, but we will see how things go. I don't think steve cares so much about 3 vs 416:42
jdstrandhuh, 4 seems so radically different I would think there would be an opinion16:42
jjohansenbut if we are leaning towards 3 and since it is his proposal modified, maybe16:43
jdstrandbut I don't want to stall out for weeks either16:43
jdstrandmy feeling is that as upstream, we shouldn't take the decision16:43
jjohansenjdstrand: don't worry I can throw enough fuel on the fire16:43
jdstrandjjohansen: I'm afraid of said fuel :P16:43
jdstrand my feeling is that as upstream, we shouldn't take the decision without steve16:44
jdstrandbut, for Ubuntu I think we should revise our stance on pushing a syntax that may change16:44
jjohansenI think that we will just have to push something that may change16:45
jjohansenbut lets get it to where it likely won't16:45
jdstrandin others words, let's get as far as we can on the syntax as we can without steve (like tyhicks said), then push that into the archive (or at least the ppa) so that these code bits are in before feature freeze and getting some testing16:45
tyhicksI think that makes sense16:46
jdstrandthen when he gets back, we can see what he objects to (if anything), then adjust before committing upstream. then after committing to upstream, do another upload to ubuntu16:46
tyhicksthat's reasonable16:47
jdstrandmdeslaur, jjohansen: what do you think?16:47
jjohansenjdstrand: I think its the only thing we can reasonable do given the circumstance16:48
mdeslaurI didn't follow what the issue was, so I have no current opinion16:48
jdstrandok, then let's plan on that16:48
jdstrandtyhicks: thanks16:48
jdstrandjjohansen: you're up16:48
jjohansenI'll be working on backporting apparmor for the phablet kernels, an email to push the syntax discussion along (or at least ignite the arguing again), hopefully release 2.8.2 and then back to working ipc16:48
jjohansens/working/working on/16:49
* jjohansen just wishes it was all working16:49
mdeslaur\o/ phablet kernels16:51
jjohansenthats it for me sarnold your up16:52
sarnoldI'm in my happy place this week, though I've got some leftover packages from community to finish: stunnel4 (I want another two manual tests before shipping) and ruby-openid (no idea how to test, asking ckuerst for ideas..)16:53
sarnoldthe patch for ruby-openid looked simpled enough, it's probably fine even without a test, but just 'it loads' is a little unsatisfying.16:54
sarnoldI'm looking forward t othrowing rocks at hornets's nests^W^W^W^W the upcoming dbus responses... I'm mostly happy with #3 but want to make sure that we're not missing something better.16:55
sarnoldI'm hopeful for some patch review from jjohansen or tyhicks this week, but if not, I'll pick up an update16:55
sarnoldI think that's it for me; chrisccoulson, you're up :)16:56
chrisccoulsonw00t16:56
chrisccoulsonso, last week we got a flash update, and i did some more work on our chromium API16:57
chrisccoulsoni've scheduled a meeting tomorrow afternoon to discuss that btw :)16:57
chrisccoulsoni shall be doing more work on that this week, and we'll likely get chromium published too (yay!)16:57
jdstrandsarnold: regarding options against #3-- not to worry, I'll be happy to shoot those down too16:57
jdstrandsarnold: :P (j/k ;)16:57
sarnoldjdstrand: woo :)16:57
* jdstrand hugs sarnold 16:58
sarnoldchrisccoulson: oh man, that's awesome. :)16:58
mdeslaurchrisccoulson: chromium updates! /me rubs his eyes16:58
chrisccoulsonalso, i'll get builds for next weeks firefox update before the end of the week16:58
* jdstrand hugs chrisccoulson too :)16:58
chrisccoulsonso it's going to be a fun end to the week ;)16:58
chrisccoulsonthanks :)16:58
chrisccoulsoni think that's me done16:58
jdstrand[TOPIC] Highlighted packages16:59
=== meetingology changed the topic of #ubuntu-meeting to: Highlighted packages
jdstrandThe 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:59
jdstrandSee 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:59
jdstrandhttp://people.canonical.com/~ubuntu-security/cve/pkg/lib3ds.html16:59
jdstrandhttp://people.canonical.com/~ubuntu-security/cve/pkg/tryton-server.html16:59
jdstrandhttp://people.canonical.com/~ubuntu-security/cve/pkg/libphp-jpgraph.html16:59
jdstrandhttp://people.canonical.com/~ubuntu-security/cve/pkg/osc.html16:59
jdstrandhttp://people.canonical.com/~ubuntu-security/cve/pkg/magics++.html17:00
jdstrand[TOPIC] Miscellaneous and Questions17:00
=== meetingology changed the topic of #ubuntu-meeting to: Miscellaneous and Questions
jdstrandDoes anyone have any other questions or items to discuss?17:00
jdstrandmdeslaur, tyhicks, jjohansen, sarnold, chrisccoulson: thanks!17:05
jdstrand#endmeeting17:05
=== 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
meetingologyMeeting ended Mon Jun 17 17:05:33 2013 UTC.17:05
meetingologyMinutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-06-17-16.32.moin.txt17:05
meetingologyMinutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-06-17-16.32.html17:05
sarnoldthanks jdstrand :)17:05
tyhicksthanks17:05
mdeslaurthanks jdstrand!17:05
jjohansenthanks jdstrand17:06
jdstrandsure thing :)17:07
bdrung!dmb-ping19:00
ubottubdrung, ScottK, Laney, micahg, barry, tumbleweed, stgraber: DMB ping19:00
* barry waves19:00
Laneylo19:00
tumbleweedhi19:00
tumbleweedwe have apologies from ScottK, so I guess I'm chair19:01
tumbleweed#startmeeting Ubuntu Developer Membership Board19:02
meetingologyMeeting started Mon Jun 17 19:02:03 2013 UTC.  The chair is tumbleweed. Information about MeetBot at http://wiki.ubuntu.com/meetingology.19:02
meetingologyAvailable 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 #votesrequired19:02
=== 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 | Ubuntu Developer Membership Board Meeting | Current topic:
tumbleweedcan someone else volunteer to chair if I have network trouble again / have to run off? I'll handle the minutes etc.19:02
* barry can19:02
tumbleweedthanks19:02
tumbleweed#chair barry19:02
meetingologyCurrent chairs: barry tumbleweed19:02
tumbleweed#topic Review of previous action items19:02
=== 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 | Ubuntu Developer Membership Board Meeting | Current topic: Review of previous action items
tumbleweedbarry to send outcome of sweetshark ppu vote19:03
barrydone19:03
tumbleweedeveryone read and amend http://pad.ubuntu.com/dmb-ppu-membership-proposal, and sign up for the implementation tasks19:03
tumbleweedLaney: care to drive this?19:03
Laneyrather micahg did if he's here19:03
tumbleweedah, of course19:03
* stgraber waves19:03
stgraber(sorry, just got out of another meeting, it's that kind of day...)19:04
Laney:(19:04
=== marlinc is now known as marlinc|away
Laneyok, seems not19:04
Laneyso I think we're all agreed on the principle19:04
Laneythat we shouldn't always require membership contributions19:05
Laneyerr wtf19:05
Laneymembership levels of involement from new developers19:05
Laneythe remaining questions are about precisely where we should set the new boundaries19:06
Laneylike:19:06
Laney - which, if any, packagesets should this apply to?19:06
Laney - should it be open to all PPU?19:06
Laneyand there's questions about how to design the application procedure (should considering membership be implicit?)19:07
barryLaney: i wonder if we can start small and just apply it to ppu and not package sets (although there may be some overlap, but ignore that for now)19:07
Laneyah, I think it's non-controversial enough that we can deal with it all at once19:07
Laneyand one thing I thought of is that we should probably say that all devs need to have signed the CoC I suppose19:08
* bdrung nods.19:08
tumbleweedour membership-monitoring thing already enforces CoC for all uploaders IIRC19:09
Laneyright, but that requirement is implicit because of membership19:09
Laneywe just need to say it19:09
stgraberbarry: I don't see much of a point to distinguish between PPU and packageset as the concerns at least for me are similar. e.g. I'd be oposed to give PPU to xserver-xorg to a non-member just as much as I'd to give xorg packageset rights to a non-member. Packagesets indeed are just a level of abstraction on top of PPU, so the two should be treated the same way.19:09
micahg-workI would think that CoC needs to apply to uploaders as well19:09
Laneyi don't think it's a controversial suggestion - the smallest tweak of the lot of them really ...19:09
Laneylet's take the packageset question19:10
micahg-workit's a standard for interaction with the community, not just a prerequisite for membership19:10
LaneyI saw we just treat packagesets as a convenience aggregating PPU together19:11
micahg-workwell, that's one type19:11
Laneybut there are 'flavour' packagesets which are somewhat different19:11
micahg-workright, that's the other19:11
tumbleweedand, package sets that consist of many (or entirely of) seeded packages19:12
micahg-workumm...well, I see that as one of the two other cases19:13
tumbleweedthey have a lot in common with flavour packagesets, without necessarily being flavour packagesets19:13
micahg-worktumbleweed, example pleasE?19:13
micahg-workflavor packagesets imply project level involvement19:13
tumbleweedcore was mentioned in the discussion earlier. xorg?19:13
stgrabercore, desktop-core, xorg, ubuntu-desktop, ubuntu-server, ...19:14
stgraberwe have a few of those19:14
micahg-workcore packageset isn't a packageset for these purposes IMHO, that would be core-dev19:14
LaneyI can't imagine entertaining an application for the first two19:14
Laneynot without other changes anyway19:14
micahg-workright19:14
micahg-workthe last 2 are flavors19:14
micahg-workxorg has seeded content, but that's aggregate PPU IMHO19:14
tumbleweedand we'd be unlikley to give a new person upload access to it. But conceputally, it probably doesn't require membership19:15
Laneyright19:15
barrywell, one way it could work is that the general rule is membership is not necessary for ppu.  then we have a black list of packages for which membership *is* required.  then if any of those packages appear in a package-set, the set is also blacklisted.  it means the level of check/control is at the package level19:16
Laneyhaha19:16
micahg-workI'm not sure about which problem we're trying to solve here19:16
bdrungwould having all main packages in the blacklist too restrict?19:17
Laneyyes19:17
tumbleweedmicahg-work: making it clear to applicants whether they need membership or not19:17
micahg-workIf we are trusting them with upload rights for these important packages, we're inherently trusting them not to break stuff19:17
micahg-worktumbleweed, no, I mean the issue of packagesets like xorg requiring membership19:17
tumbleweedyeah, agreed with you19:17
micahg-workhaving membership shouldn't improve that "trust" any19:18
LaneyRight, we're not lowering any technical requirements here19:18
Laneyso if they know everything they need to to upload then I don't see any need to require s&s on top of that19:18
micahg-workand if we're worried someone's going to break the archive during a milestone or what not, we probably shouldn't be giving them upload rights in the first place19:19
tumbleweedok, flavour packagesets?19:20
micahg-workflavor packagesets have project level scope IMHO and should require membership (in that we want flavors integrated into the main Ubuntu community and not islands amongst themselves)19:22
tumbleweedyeah, my feeling too19:22
Laneysame19:22
Laneyfor the same reason we'll continue requiring it for motu/core-dev19:22
tumbleweedcan we vote on this proposal, or is there anything else we need to hash out?19:22
bdrungwhich criteria do we want to use for requiring significant & sustainable contribution?19:22
micahg-workstgraber, how do you feel about all this?19:22
stgrabermicahg-work: still not too happy about opening the possiblity of the DMB granting upload rights to critical packages without requiring membership. I know that the current DMB probably is reasonable about it, but I'm not thrilled about the documented new process being that open.19:23
LaneyI guess I don't feel that membership is where concerns about individual developers are likely to be19:24
Laneyit's going to be at their technical judgement19:24
micahg-workright, that's how I feel as well19:25
stgraberwell, I personally tend to like people who have upload rights to packages installed by default on my system to have been around for at least a whole cycle19:25
tumbleweedI don't want non-member developers to be come a norm19:25
micahg-workstgraber, we can make being around a whole cycle a requirement without requiring membership (not requiring significant or sustained, just the time period)19:26
tumbleweedwould we be prepared to limit this to entirely non-main package (-set)s ?19:26
stgraberso I'm happy to grant non-member PPU to some upstream dev maintaining their package in universe, but I'd prefer to have the process restricted in a way that ensures that19:26
LaneyI think that any DMB the community has confidence in will be rigorous enough19:26
stgrabermicahg-work: then I think I'd be happy with that19:26
Laneywhat is 'being around'?19:27
Laneytime from first upload to application?19:27
micahg-workwe already require understanding of the release schedule for upload rights19:27
tumbleweedbeing around a whole cycle, but not a member doesn't sound like a common scenario19:27
Laneyindeed19:27
micahg-workLaney, well, either that or first contribution (bzr included)19:27
stgraberLaney: either first upload or testimonial from a current dev that the applicant has been anoying them for over 6 months19:27
micahg-workjust being exposed to the release process19:28
tumbleweedhow about if instead of requiring non-main, we added a sentence to the effect of: Upload rights to core (seeded) packages will require sustained experience in the project (usually meaning membership)?19:31
bdrung+119:31
* tumbleweed isn't convinced that membership from forums would make us happy about upload rights to xorg, though :P19:32
Laneyfine, but I don't see the point in singling packages out like that19:32
LaneyI'd rather make explicit that we'll require a level of trust that is appropriate for the packages in question19:32
micahg-worktumbleweed, right, that's the catch, you can get membership for a lot of different things19:32
Laneyso nethack not so much, binutils perhaps a bit more19:32
micahg-workLaney, I think that's fair19:33
Laneywhich is of course what happens already19:33
micahg-workright19:33
tumbleweedLaney: the level of trust expectation is already there19:33
tumbleweedlevel of trust doesn't mean experience of release process, which is what stgraber seems concerned about19:34
micahg-worktumbleweed, it does to some extent19:34
micahg-workespecially WRT seeded packages19:34
micahg-workit's one of the components19:34
Laneywell it doesn't say "you have to have been around for X months" indeed19:34
Laneybut the DMB has to convince itself19:34
* Laney shrugs19:35
micahg-workI'm fine with explicit vagueness if it solves the problem19:35
Laneyif this is what we need to move on then so be it19:35
tumbleweedclarity of our expectations would also be useful19:35
tumbleweedOK, so while we consider this. What's next19:35
tumbleweedmail final wording to TB for signoff?19:35
tumbleweedcan we get a final wording now? or this this meeting not going to do it for us?19:36
tumbleweedwe have an applicant to process, too19:36
Laneywording of what?19:36
Laneyan announcement?19:36
tumbleweedthe proposal, if we want their signoff19:37
LaneyI guess just edit the pad that I started already to reflect what we decide now19:37
tumbleweedok, I think we should move on now, we can revisit this later19:37
Laneythen ask the TB to ack/nack it at their meeting19:37
tumbleweedremaining action item:19:37
tumbleweedlaney to update DD-PPU process to say that any ubuntu-dev is eligible19:37
Laneyyeah sorry didn't do that yet19:38
tumbleweedok, carried19:38
Laneybut we got an applicant through it anyway19:38
Laneyso seems ok19:38
tumbleweed#topic Louis Bouchard's Contributing Developer application19:38
=== 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 | Ubuntu Developer Membership Board Meeting | Current topic: Louis Bouchard's Contributing Developer application
tumbleweedcaribou: hi19:38
caribouHello everyone19:38
cariboutumbleweed: o/19:38
tumbleweedcaribou: please introduce your application19:38
tumbleweedhttps://wiki.ubuntu.com/LouisBouchard19:38
caribouMy name is Louis Bouchard19:39
caribouI've been working on Ubuntu as my day job for a bit more than 2 years noew19:39
cariboubut started using ubuntu in 2006 with Edgy19:39
caribouI will not repeat what you can read on the Wiki page19:40
=== marlinc|away is now known as marlinc
=== marlinc is now known as Marlinc
caribouI come from the dark side of proprietary softwarea long long time ago19:40
tumbleweedheh19:40
caribouI involvment with Ubuntu is mainly around bug fixing, SRU etc19:40
caribouI also do some mentored packaging on the debian side of things19:41
tumbleweedgreat to hear19:41
caribouSince my involvment has been regularly increasing with Ubuntu, I thought it was appropriate to apply for UCD19:41
tumbleweedI'm afraid I have to run off in a minute, but hopefully barry can continue chairing the meeting for me19:42
tumbleweedcaribou: when do you expect to be applying for upload rigths?19:42
cariboumost of my involvment is around Foundation packages, with a bit of work on the kernel side19:42
caribouI want to get more exposure with merges and also participate in PlusOne to get more experience19:42
* barry takes a seat19:42
barrycaribou: have you scheduled your plus-one yet?19:43
caribouno, not yet. I will need some hand-holding in that direction19:43
cariboubut some of my colleagues have participated a few cycles already19:44
caribouso they can help19:44
barrycaribou: it's a great learning experience19:44
cariboubarry: that's what I heard, which triggered my interest19:44
cariboumerging is also something I'm curious about.19:44
caribouI see packaging from the debian side of things only right now19:45
caribouthough it's a rather small package19:45
caribouI also think that PlusOne will help me in may daily activities19:46
caribouanything else I can outline for you ?19:46
bdrungcaribou: i saw that makedumpfile is arch restricted. is that intentional?19:46
cariboubdrung: there seems to be some issues currently with the ARM side of things19:47
cariboubdrung: there is an open Debian bug about it that needs my attention19:47
cariboubdrung: aside from that, I think that there is one specific PPC patch laying around that might explain it19:48
bdrungcaribou: but shouldn't it work on all architectures (besides bugs)?19:48
caribouafaik makedumpfile do make some assumptions regarding specific architectures19:49
cariboubdrung: as it works in a kexec triggered kernel boot that is somewhat different from a regular boot environment19:49
bdrungah, okay19:50
cariboubdrung: that might come from debian's inheritance as well, since I don't think we do specific changes to the package on Ubuntu19:51
caribouI see it listed for amd64, i386, ia64 and powerpc only on Debian19:51
barrycaribou: thanks.  i think we're ready to vote19:52
barry#vote should caribou become an ubuntu contributing developer?19:52
meetingologyPlease vote on: should caribou become an ubuntu contributing developer?19:52
meetingologyPublic 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:52
bdrung+119:53
meetingology+1 received from bdrung19:53
barrytumbleweed extends a +119:53
barry+119:53
meetingology+1 received from barry19:53
Laney+119:53
stgraber+119:53
meetingology+1 received from Laney19:53
meetingology+1 received from stgraber19:53
micahg-work+119:53
meetingology+1 received from micahg-work19:53
barryand scottk is absent today, so19:54
barry#endvote19:54
meetingologyVoting ended on: should caribou become an ubuntu contributing developer?19:54
meetingologyVotes for:5 Votes against:0 Abstentions:019:54
meetingologyMotion carried19:54
barrycaribou: congratulations19:54
cariboubarry: & everyone else, thank you very much19:54
cariboulooking forward to see you again for the next step19:54
Laney\o/19:55
barrycaribou: indeed!  enjoy the +1 :)19:55
caribou& all the work in the meantime19:55
Laneyget on that sponsorin' train19:55
caribouLaney: will do19:55
barrywe have no more applicants today19:55
barry#topic AOB19:55
=== 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 | Ubuntu Developer Membership Board Meeting | Current topic: AOB
barryanything else folks want to bring up today?19:55
LaneyI don't know how we are carrying the PPU thing on19:56
barryLaney: i think we have to continue on the mailing list19:56
Laneyok19:57
barryif there's nothing else, i think we're done19:58
barry#endmeeting19:58
=== 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
meetingologyMeeting ended Mon Jun 17 19:58:38 2013 UTC.19:58
meetingologyMinutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-06-17-19.02.moin.txt19:58
meetingologyMinutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-06-17-19.02.html19:58
Laneythanks19:59
caribouthanks everyone & have a nice rest of the day20:00
stgraberthanks20:01
tumbleweedcaribou: congrats :)20:28
* ScottK wave belatedly.20:58
=== marlinc is now known as marlinc|away
=== marlinc|away is now known as marlinc
=== biostudent_ is now known as biostudent
=== biostudent_ is now known as biostudent

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!