/srv/irclogs.ubuntu.com/2014/05/15/#ubuntu-meeting.txt

=== Ursinha is now known as Ursinha-afk
=== Ursinha-afk is now known as Ursinha
=== vladk|offline is now known as vladk
=== vladk is now known as vladk|offline
=== vladk|offline is now known as vladk
=== vladk is now known as vladk|offline
=== vladk|offline is now known as vladk
=== vladk is now known as vladk|offline
=== psivaa is now known as psivaa-afk
=== greyback is now known as greyback|food
=== vladk|offline is now known as vladk
=== doko_ is now known as doko
=== greyback|food is now known as greyback
=== psivaa-afk is now known as psivaa
=== vladk is now known as vladk|offline
=== vladk|offline is now known as vladk
* xnox goes to grab a coffee14:54
* slangasek waves15:00
mhall119hello15:00
* mvo waves as well15:00
* barry wavers15:00
jodho/15:01
slangasek#startmeeting15:01
meetingologyMeeting started Thu May 15 15:01:48 2014 UTC.  The chair is slangasek. Information about MeetBot at http://wiki.ubuntu.com/meetingology.15:01
meetingologyAvailable commands: action commands idea info link nick15:01
slangasek[TOPIC] lightning round15:01
=== meetingology changed the topic of #ubuntu-meeting to: lightning round
slangasek$ echo $(shuf -e barry doko stgraber jodh bdmurray slangasek cjwatson xnox caribou infinity mvo)15:01
slangasekbarry caribou bdmurray stgraber infinity mvo jodh doko xnox slangasek cjwatson15:01
barry\o/15:02
barrymostly working on debian bug #732703.  i have a full working stack, discussed with debian pythonistas on various forums, and ready to be applied and uploaded.  currently writing some documentation, and then will release new debian packages for DPMT maintained packages, with bugs and diffs for non-team maintained packages.  should have all this finished today, modulo interacting with maintainers and nmus.15:02
ubottuDebian bug 732703 in python3.4 "python3.4: cannot create a virtualenv" [Normal,Open] http://bugs.debian.org/73270315:02
barryother: patch piloted. debian bug #744300 + SRU'd to trusty.  LP: #1317660.  scripttest 1.3-1.  python-pip 1.5.5-1.15:02
ubottuDebian bug 744300 in pexpect "missing dependency on dh-python" [Wishlist,Fixed] http://bugs.debian.org/74430015:02
ubottuLaunchpad bug 1317660 in pexpect (Ubuntu) "[SRU] Bug: AttributeError: 'error' object has no attribute 'errno'" [High,In progress] https://launchpad.net/bugs/131766015:02
barrymeet with q/a folks re: system-image testing for utopic.  need to get nose2-conv packages in debian (debian bug #740195) so that i can capture coverage output for q/a dashboard.15:02
ubottuDebian bug 740195 in wnpp "ITP: nose2-cov -- A coverage plugin for the nose2 Python testing framework." [Wishlist,Open] http://bugs.debian.org/74019515:02
barrytodo: triage and planning utopic work for system-image.15:02
barrydone15:02
caribou* makedumpfile 1.5.6 now published in Debian unstable15:02
caribou* Worked on adding remote kernel dump functionality to Debian/Ubuntu. Now working with SSH & NFS15:02
caribou* Worked on Bug 1313602 now waiting for merge proposal15:02
caribou* Started initial work for PPU application to the DMB15:02
ubottubug 1313602 in nova-cloud-controller (Juju Charms Collection) "Nova-cloud-controller charms failed to sync ssh keys between compute nodes" [Undecided,In progress] https://launchpad.net/bugs/131360215:03
cariboudone15:03
bdmurrayresearch into successfully retried retaces by the error tracker15:03
bdmurrayresearch into indicator-sound retracing failures15:03
bdmurrayupdated the daisy retracer to be more informative when failing to retrace15:03
bdmurrayirc discussion regarding RecoverableProblem duplicate signatures15:03
bdmurrayreported apport bug 1319099 regarding whoopsie-upload-all not uploading RecoverableProblems15:03
ubottubug 1319099 in apport (Ubuntu) "whoopsie-upload-all does not upload RecoverableProblem reports" [High,Fix committed] https://launchpad.net/bugs/131909915:03
bdmurrayreported apport bug 1319477 regarding whoopsie-upload-all waiting period15:04
ubottubug 1319477 in apport (Ubuntu) "whoopsie-upload-all waits for crash files to upload that have failed to upload" [High,New] https://launchpad.net/bugs/131947715:04
bdmurrayreplied to mailing list thread regarding the error tracker15:04
bdmurrayresearch into phased-update of nautilus (manually set to 100%)15:04
bdmurrayhelped infinity tracker down errors made by the phased updater15:04
bdmurraytesting of whoopsie on the nexus 415:04
bdmurrayreported bug 1319213 regarding android dual boot and files in /var/crash/15:04
ubottubug 1319213 in android (Ubuntu) "keeping user data keeps files in /var/crash which makes little sense" [Undecided,New] https://launchpad.net/bugs/131921315:04
bdmurraysubmitted apport merge proposal fixing bug 131684115:04
ubottubug 1316841 in Daisy "apportcheckresume does not create a duplicate signature" [Medium,Triaged] https://launchpad.net/bugs/131684115:04
bdmurraysubmitted merge proposal with fixes for bugs 1319099, 131676315:04
bdmurraySRU verification of bug 1277706 (failed?)15:04
bdmurraySRU verification of apport upload to trusty-proposed15:04
ubottubug 1316763 in apport (Ubuntu Trusty) "bucketing of recoverable problems is done poorly" [Medium,Triaged] https://launchpad.net/bugs/131676315:04
ubottubug 1277706 in ubiquity (Ubuntu Precise) "ubiquity in precise-updates, doesn't have tight enough dependency on python-apt leading to crashers" [High,Fix committed] https://launchpad.net/bugs/127770615:04
bdmurrayuploaded apport fix for bug 123543615:04
ubottubug 1235436 in apport (Ubuntu) "/etc/init/apport-noui.conf is non-functional on the phone" [Critical,Fix released] https://launchpad.net/bugs/123543615:04
bdmurraybug bot modifications for mythbuntu installer bug, flightgear upgrade failure15:04
bdmurrayadded 13.10 iso verification code to the bug bot15:04
bdmurrayran bug bot against ubiquity bugs for 13.10 isos15:04
bdmurrayupdated pMRE report for vlc, sent email to tech board15:04
bdmurraypatch pilot15:04
bdmurray✔ done15:04
slangasekstgraber is off today, so presumably not reporting despite being in the channel15:05
slangaseklooks like mvo is next15:06
mvoShorter week, 2*0.5 days off15:06
mvoDid:15:06
mvo- click: bug triage, create some feature/bugfix branches, ride the CI train for the first time (yeah!)15:06
mvo- hwe-eol: work on corner cases in detection script15:06
mvo- merges: look at some old-merges15:06
mvo- misc: explore unity8 in the desktop15:06
mvo- apt: work on abi-break branch, bugfix/ensure-optional-targets, bugfix/update-progress-reporting, bugfix for robustness on corrupted Translation-$lang files15:06
mvoTodo:15:06
mvo- hwe eol15:06
mvo- sprint preparing15:06
mvo(done)15:06
mvoslangasek: no infinity today?15:06
jodh* foundations-1305-upstart-work-items:15:06
slangasekmvo: I've pinged him, but he's not in the channel so go ahead15:06
jodh  - cgroup+async support:15:06
jodh    - wrote a new test to ensure jobs not auto-started until cgmanager available.15:06
jodh    - Fixed a async re-exec issue.15:06
jodh    - Currently working on another re-exec issue whilst15:06
jodh* other:15:07
jodh  - Out tomorrow and Monday.15:07
jodh15:07
jodhOops! '- Currently working on another re-exec issue whilst working with xnox on async branch re-jiggling' :)15:08
doko- work on GCC warning regressions PR 61106 and 6112615:08
doko- work on GCC 4.8.3 updates before the upstream release15:08
doko- fix gnat link issues on AArch6415:08
doko- openjdk-8 packaging15:08
doko(done)15:08
xnox* upstart/async:15:08
xnox - completing refactoring async branch15:08
xnox - all/most code is merged into lp:upstart/async staging branch15:08
xnox - everything is synchronous in that branch at the moment, next15:08
xnox starting flipping to async process-by-process15:08
xnox* gcc-4.9:15:08
xnox - trianged / sent patches for 10 FTBFS bugs15:08
xnox* python2/autopilot:15:08
xnox  - DONE autopilot1.5 has landed15:08
xnox  - TODO camera, gallery, sudoku apps declare py3 compat in their15:08
xnox  trunks, but not on the images yet.15:08
xnox  - TODO make python2-autopilot depend on python2-evdev.15:08
xnox* insserv/systemd:15:09
xnox  - ongoing in-distro init systems improvements, e.g. UPSTART_SESSION15:09
xnox  in the environment should no longer affect package15:09
xnox  configuration/installation. Progressing with pitti/vorlon to enable insserv.15:09
xnox* was off mon-wed15:09
xnox..15:09
slangasek * short week, out sick this past Monday15:09
slangasek * Java engineer hired, starts Monday15:09
slangasek * prepping for Malta15:09
slangasek * discussing UEFI on arm64 with the hyperscale and server teams15:09
slangasek * TODO:15:09
slangasek  * look at systemd integration with nfs-utils and rpcbind (Debian bug #622394)15:09
ubottuDebian bug 622394 in nfs-common "nfs-common: breaks systemd - dependency cycle in require-start leads to removal of critical jobs" [Normal,Open] http://bugs.debian.org/62239415:09
slangasek  * more malta prep15:09
slangasek(done)15:09
barryxnox: image #29 is still pulling in py2.15:09
cjwatsonlivefs in LP:15:09
cjwatson - Worked on a scheme to pass additional arguments through.  I've uploaded the livecd-rootfs part of this, although I'm holding off on my Launchpad code for now since it probably wants separate review and isn't needed for the initial deployment.15:09
cjwatson - Finished writing browser tests and pushed https://code.launchpad.net/~cjwatson/launchpad/livefs-browser/+merge/219505.15:10
cjwatson - Got initial cdimage code working.15:10
cjwatson - Did a successful end-to-end ubuntu-touch build with local cdimage and Launchpad instances!15:10
cjwatson - Released and got webops to deploy launchpad-buildd bug fixes.15:10
xnoxbarry: correct, as it should.15:10
cjwatsonA few merges.  Synced r-base, which unblocked a pile of stuff.15:10
cjwatsonReviewed some of Michael's click changes, although he is currently outpacing me.  Helped with some CI Train handling.15:10
slangasekxnox: why did you send patches for the gcc-4.9 bugs instead of NMUing? :)15:10
cjwatsonFixed libfreehand/ppc64el FTBFS.15:10
cjwatsonTo do before Malta: finish cdimage/Launchpad integration; experiment with autopilot on x86 emulator; respond to any LP review feedback; sort through some more of Michael's click branches15:10
cjwatson..15:10
xnoxslangasek: because they ain't yet RC. And i've been told off about 0-day NMU for "good" reasons, when it's "not RC yet".15:11
barryxnox: hmm. didn't the ap changes to remove py2 land in #29?15:11
slangasekxnox: ah, well, that's what delayed NMUs are for, then.. .but ok :)15:11
xnoxslangasek: joined Debian GNOME team to do "team uploads" of my pending patches. Most of gcc-ftbfs are not team managed packages =(15:11
slangasekxnox: python2> what do we need to do to drive this to completion?  how do we get these apps from trunk to image?15:11
xnoxslangasek: i was expecting for that to just happen whilst i was away. but it didn't.15:12
xnoxslangasek: will poke people about it.15:12
slangasekok, cool15:12
ogra_note that i just dropped the thos python2 packages in touch15:12
xnoxbarry: so in autopilot-touch metapackage, i still explicitely hold on to py2, because i can only drop that once all clicks on the image correctly declare their py3 alignment.15:13
ogra_(test image is building right now)15:13
ogra_*the two15:13
slangasekogra_: so you're breaking the click apps that are still missing their py3 declarations?15:13
ogra_python2-autopilot and python2-evdev15:13
ogra_slangasek, i had three independed people ping me to drop these two packages today15:13
barrymaybe we can talk about this after the meeting?15:13
xnoxogra_: you will fail autopackage tests in gallery-app, sudoku-app and camera-app. As well as breaking all the deb based python2 autopackage tests.15:14
ogra_which i now did15:14
xnoxogra_: well, you should talk to TIL first.15:14
ogra_robru even with high urgency15:14
ogra_referring to barry15:14
slangasekok, deep topic, let's take this out of the meeting :)15:14
* ogra_ is in meetings for the next 2h and then gone 15:14
slangasekbut we definitely should not be pulling python2 off the images before the click packages are all resolved per https://blueprints.launchpad.net/ubuntu/+spec/core-1311-python3-roadmap15:15
slangasek[TOPIC] AOB15:16
=== meetingology changed the topic of #ubuntu-meeting to: AOB
slangasekanything else here?15:17
slangasekeveryone ready for the sprint?15:17
* mvo nods15:18
dokoGCC bug squashing tomorrow and Saturday!15:18
slangasekreminder to put sprint agenda items on https://wiki.canonical.com/UbuntuEngineering/Sprints/ClientSprint-May2014/Foundations please15:19
dokoyep15:19
slangasekok then15:20
slangasekshort meeting - thanks all, now let's get the python sorted on the phone images :015:21
slangasek#endmeeting15:21
=== 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 Thu May 15 15:21:55 2014 UTC.15:21
meetingologyMinutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2014/ubuntu-meeting.2014-05-15-15.01.moin.txt15:21
mvothanks15:21
jodhthanks!15:21
barrythanks!15:21
caribouthanks15:21
valoriehi pen17:00
pleia2o/17:00
s-foxo/17:00
pleia2#startmeeting Community Council17:00
meetingologyMeeting started Thu May 15 17:01:09 2014 UTC.  The chair is pleia2. Information about MeetBot at http://wiki.ubuntu.com/meetingology.17:00
meetingologyAvailable commands: action commands idea info link nick17:00
=== 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 | Community Council Meeting | Current topic:
* pleia2 rounds up usual suspects17:00
mhall119o/17:01
s-foxo/17:01
valoriehi lyz, michael17:01
elfyo/17:01
pleia2#chair elfy cprofitt dholbach czajkowski17:01
meetingologyCurrent chairs: cprofitt czajkowski dholbach elfy pleia217:01
PendulumHiya :)17:01
dholbachhiza17:01
pleia2#chair mhall11917:01
meetingologyCurrent chairs: cprofitt czajkowski dholbach elfy mhall119 pleia217:01
pleia2there we go17:01
pleia2https://wiki.ubuntu.com/CommunityCouncilAgenda17:02
mhall119oh, that was unexpected17:02
mhall119oh, we're all chair, ok then17:02
mhall119who's up first?17:03
pleia2so first up on our agenda is Membership Board17:03
pleia2#topic Membership Board catch up17:03
=== 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 | Community Council Meeting | Current topic: Membership Board catch up
pleia2I see Pendulum and s-fox here from the board, anyone else?17:03
PendulumIdleOne might be coming (I've just poked him to check)17:04
mhall119good to see you again Pendulum, haven't chatted with you in a long time :)17:04
dholbachhow have things been going on the Membership Board? :)17:05
s-foxGenerally okay, few items we'd like to go over with the cc though17:05
PendulumIn general things have been pretty good.17:05
pleia2shall we talk about quorum?17:05
cjohnstonoh hi17:05
mhall119yeah, quorum seemed to be the biggest obstacle17:06
s-foxsure,  okay17:06
mhall119that is, membeship meeting without enough people to actually vote on the applicants17:06
PendulumIn general, I think that's been improving.17:07
cjohnstonI don't think that's the issue.. I think the issue is how many votes are required for an approval17:07
s-foxit has been improving, but we're finding it hard to decide if someone is approved or not.17:07
mhall119cjohnston: that's really dependent on how many people are there to vote though17:07
dholbachsome of us were chatting a bit about it since you last brought it up, and I can't remember who brought up the idea, but one approach we talked about was that we could ask applicants to hand in their application earlier (let's say a few days), so members of the board who can't make it could send in their vote by mail17:07
s-foxfor example if everyone votes +0 and then someone goes +1 it is technically approved.17:07
s-foxit just doesn't look right with the lack of support17:08
dholbachanother idea was that if there weren't enough members of the board around to make a decision during the meeting, the vote could be taken to mail17:08
dholbach... which is what the DMB has been doing17:08
cjohnstonIf we do the voting by mail, we might as well not have meetings and just do all voting by mail17:08
PendulumWe have been moving applications when there isn't quorum to e-mail17:08
dholbachthe advantage of both ideas is that we wouldn't get into voting arithmetics :)17:08
mhall119so let's tackle these one at a time, quorum first then what technically consitutes approval17:08
mhall119Pendulum: so the voting and discussions continue over email after the meeting?17:08
dholbachcjohnston, I disagree - it's always worth having a chat and resolving questions which might be not answered on the wiki17:09
Pendulummhall119: If there isn't quorum it does17:09
pleia2cjohnston: no, DMB still has public meetings so people can apply in public and everything is recorded17:09
cjohnstondholbach: in that case, the people who have already voted have voted without those answers17:09
mhall119Pendulum: out of the number of times the discussion and voting went to email, how often was a final vote taken?17:09
dholbachcjohnston, some might already know that person, etc17:09
cjohnstonIt could sway my vote, but was never given the opportunity to sway someone elses vote17:10
pleia2cjohnston: afaik on list voting happens after the meeting17:10
elfypleia2: +117:10
cjohnstonpleia2: that wasn't dholbach's suggestion17:10
Pendulummhall119: I think we have had final votes on all of them. Very few in those situations have been rejected17:10
mhall119ok, so that's been effective then, that's good to hear17:10
PendulumWe do have some meetings where a member who isn't going to make it has let us know in advance either on IRC or the mailing list what their vote would be.17:10
PendulumWe also, I think, have really mostly been making qorum17:11
mhall119cjohnston: dholbach was suggesting votes via email as a fallback when you can't attend the meeting, not at the preferred method17:11
dholbachmhall119, thanks for clarifying this17:11
mhall119and it sounds like that's already been happening17:11
s-foxThings have improved a lot in recent meetings, especially with regards to voting on the mailing list in advance if you are likely to be able to unattend17:12
pleia2so it sounds like quorum typically isn't the issue, mostly it's a numbers thing, if quorum to hold a meeting is 4 does three +1s and one -1 equal approval17:12
IdleOnehere17:12
PendulumMy impression is that it's the 12:00 UTC board that is having more problem, but that may just be due to my being on that board :) (the members who never show on that board are among those expiring at the end of the month)17:12
Pendulumpleia2: exactly17:12
mhall119so do we need to officially endorse email votes as a fallback, or can we just say "carry on" with doing it?17:12
cjohnston"ask applicants to hand in their application earlier (let's say a few days), so members of the board who can't make it could send in their vote by mail"  what is the point of turning them in earlier if the voting doesn't start until later?17:12
cjohnstonmhall119: ^17:12
elfycjohnston: so people have longer time to read them17:12
pleia2cjohnston: I read that as voting by mail after the meeting, not before17:13
cjohnstonthen they don't need to turn them in earlier.17:13
mhall119cjohnston: shouldn't applicants already submit their application early enough for board members to review before the meeting?17:13
cjohnstonI believe there already is a requirement17:13
elfycurrently it's 24 hours on the wiki17:13
pleia2so they have time to read app, read meeting, send in vote; I think the only time there would be an exception is if they know something specific about the applicant that would make them reject them regardless17:13
mhall119so then there's no change to what's happening, just making what's happening officially approved17:13
Pendulumthat sounds good to me :)17:14
s-foxi do a review roughly 3 or 4 days before the meeting in my own time.  i have been known to be a slow reader and also be sure i understand the applicant17:14
mhall119pleia2: or when they would approve them regardless17:14
pleia2mhall119: yeah17:14
pleia2anyway, quorum17:14
pleia2my impression was always that it was 4 to hold a meeting, then a majority of those folks had to +117:15
mhall119a majority had to vote +1, or the the final tally had to be >= +1?17:15
cjohnstonWe all agree on the 4.. it's the latter part as mhall119 says17:15
pleia2majority had to vote +117:15
IdleOneso +3-1 would be approved?17:15
mhall119or a minimum of 4 +1's regardless of final tally17:16
pleia2but when I was on the board it wasn't usually an issue because we had a back channel where we typically came to a consensus17:16
pleia2if someone felt really strongly about a -1, we all took that pretty seriously17:16
cjohnstonwe end up with +0 and +1 normally in this situation17:16
PendulumIn most cases we do come to consensus17:16
mhall119cjohnston: is that because of a lot of +0s, or because of a balance of +1 and -1?17:16
s-foxUnless I am mistaken we had an applicant who was technically approved on the 22:00 UTC meeting but we were concerned by lack of +1's from the board and went to the mailing list.  Can any of the board remember who it was?17:16
cjohnstonso is 2 +0's and 2 +1's approved?17:17
cjohnstons-fox: are you refereing to the Canonical employee?17:17
pleia2cjohnston: a majority of 4 would mean 3 :)17:17
IdleOneWe do have a back channel. The question in my mind is do we need a majority in favor regardless of the number of voting members. or do we need a minimum of positive votes17:17
mhall119if the rule is "majority of votes are +1" then 4 votes would require 3 +1s17:17
s-foxNo cjohnston , i think it was after that.17:17
cjohnstonpleia2: I understand majority.. but that wasn't the only thing thrown out17:17
sabdflhi folks, sorry to be late17:17
pleia2welcome sabdfl17:17
s-foxhello17:18
mhall119it seems there was some confusion as to what the actual rule on approval was17:18
mhall119hi sabdfl17:18
shadeslayerhiya, sorry I was late17:18
elfyhi shadeslayer sabdfl17:18
cjohnstonmhall119: correct. and that's what we need defined17:18
mhall119pleia2: so the rule is "majority of votes are +1", regardless of final tally, and a quorom of 4, is that correct?17:18
pleia2mhall119: that's always been my understanding17:18
mhall119so 3 or more +1s, depending on how many votes are cast17:19
elfythat would make sense to me17:19
s-foxThe bot does give a verdict for us, but sometimes it just feels wrong.17:19
mhall119then we should put this in writing somewhere17:19
s-foxCan the bot be reworked?17:19
IdleOneyes it can17:19
pleia2I think the bot does math, becasue that's how some teams do it17:19
IdleOne!meetingology17:19
ubottumeetingology is a bot that runs !meetings and produces minutes - information at https://wiki.ubuntu.com/meetingology17:19
meetingologyubottu: Error: "is" is not a valid command.17:19
mhall119lol17:20
mhall119bot fight17:20
dholbachok... shall we talk about the nominations as well?17:20
mhall119can we tell meeting-ology about the decisions so far recarding quorum and approval rules?17:20
mhall119so it's in the minutes17:21
Pendulummhall119: it says there's a way to tell it a minimum number of +1s to pass17:21
mhall119Pendulum: the bot does?17:21
elfyPendulum: per session?17:21
mhall119ah, yes, # votesrequired, nice17:21
IdleOnethe bot has a command to set #requiredvotes17:21
mhall119Pendulum: you just have to know how many votes will be cast ahead of time and calculate the majority value17:22
cjohnstonso I just want to be clear.. to be approved it is 1/2 of the voters +1, correct?17:22
cjohnstonmhall119: ^17:22
IdleOnethat is not the issue though, what we would like defined is what that number is17:22
mhall119cjohnston: 50%+117:22
cjohnstonack17:22
s-foxcan this be tested with the bot?17:22
=== vladk is now known as vladk|offline
pleia2s-fox: yep, #meetingology is the playground for that17:22
mhall119does anybody mind if I tell the bot about what's been agreed to so far about getting quorum via email votes when it's not achieved in the meeting?17:23
pleia2mhall119: please do17:23
mhall119#agreed when quorum is not reached in a meeting, votes can continue via email until quorum is reached17:23
* mhall119 assumes the bot got that17:24
pleia2yeah, it doesn't echo anymore17:24
mhall119now, on that note, does voting via email automatically stop when quorum is reached?17:24
s-foxWould you like us to test and come back to the CC, or is this something you will be looking into yourself ?17:24
pleia2mhall119: I'd say so17:24
mhall119pleia2: that wouldn't allow everybody to vote then17:24
pleia2mhall119: nope, it's as it's always been17:24
IdleOneWe can set a time limit for email voting17:25
IdleOne1 week?17:25
elfyIdleOne: that works for me17:25
mhall119if there are 3 people at the meeting, there is no quorum, so it goes to email, then the very next person to vote would end the voting17:25
pleia2I like seeing folks walk away from a meeting with an answer, not wait on email voting unless there is an issue17:25
dholbachagreed17:25
elfypleia2: that's ideal - but not what always happens17:26
mhall119dholbach: agreed to which?17:26
dholbachmhall119, sorry, what pleia2 said before17:26
pleia2elfy: hence "unless there isan issue" :)17:26
mhall119pleia2: I think we're all on the same page there, the preference is to have quorum at the meeting and give people a yes or no answer then and there17:26
mhall119the question now is how to handle where there isn't quorum at the meeting17:26
elfythen it goes to e-mail17:27
pleia2I think typically the meeting isn't held if there isn't quorum, or they grab CC members to fill in17:27
mhall119if there are, say, 3 board members who are absent and it goes to email, do we wait for all 3 to vote or do we end voting as soon as quorum is reached and the others don't get a chance?17:27
dholbachspeaking of going to email: shall we move some of the discussion to mail? I'm just raising this because we're meeting up with the kubuntu folks today as well17:27
IdleOnemhall119: I think the best thing is to set a time limit on the email voting. Those members who get the vote in on time get counted.17:28
pleia2IdleOne: but only if there isn't quorum at the meeting, right?17:28
Pendulumpleia2: correct17:28
elfymhall119: if it goes to e-mail I see no reason why not just wait the week as IdleOne suggests and use all the votes17:28
IdleOnecorrect17:28
pleia2wfm17:28
elfyand me17:29
dholbachcool :)17:29
IdleOneif there is quorum (4 voting members) at the meeting there is no need for email votes17:29
pleia2great17:29
mhall119#agreed if voting goes to email for quorum, board members will be given a deadline of one week to cast their vote17:29
mhall119can I note down the approval rule as agreed to?17:30
mhall119"majority of votes cast must be +1"?17:30
IdleOneplease do17:30
pleia2so the other thing with membership boards should be pretty quick - we don't have enough applicants for the spaces available on the boards17:30
dholbachit looks like we're lacking some nominations for the 12UTC meetings, so it probably might make sense to extend the time on the board for the expiring members and have another call for help? maybe ask the EMEA people on the loco contacts list?17:30
* pleia2 nods17:30
mhall119#agreed applicants are approved when a majority of votes cast are +1, regardless of the final total, as long as quorum is reached17:30
PendulumQuite honestly, only 1 of the expiring members on 12UTC has shown up for meetings for at least a year17:31
pleia2:\17:31
dholbachPendulum, is the time popular among applicants?17:31
pleia2that time zone region has always been tough to staff17:31
s-foxI tried to stimulate getting this resolved by changing the time.  It was generally not received well and people were saying they would struggle even more.17:32
PendulumPart of what happened is that most of the 12UTC board is actually people on the East Coast of the US. So moving it earlier makes it more difficult for us, but moving it later means that the A/O folks can't make it17:33
mhall119is it worth having a 12UTC board then?17:33
PendulumMy impression was that when we had 3 boards and that one met at 10UTC, there was even more trouble reaching quorum than we have at 12UTC17:34
mhall119if it's difficult for the board, surely it's difficult for applicants too17:34
s-foxIt is a shame that time is in the middle of the working day in europe.17:34
PendulumWe do get applicants who would not be able to make 22UTC17:34
elfymhall119: I think that it's more that it's difficult to get the board there rather than applicants from what I've seen17:34
Pendulumexactly17:35
pleia2mhall119: we want more APAC applicants, I fear removing the board spot would make it harder for them and prepetuate the imbalance17:35
s-foxWe have never had a problem with applicants. the list is usually well populated17:35
elfys-fox: thanks17:35
s-foxthe problem is the board voting.17:35
PendulumI do think we've gotten better with getting quorum for 12UTC17:35
mhall119and is that because it's in the middle of their work day and they can't attend?17:35
mhall119or too early in the morning/late at night to attend?17:36
dholbachcan we try to mail locos in those regions?17:36
Pendulummhall119: it's more because it's either really early or really late. I don't think there's anyone from EMEA on that board17:36
pleia2dholbach: that's what I'm thinking17:36
dholbachok... I'll send a mail to the CC and membership board to organise this17:37
PendulumI'm not actually sure if there are many, if any, EMEA folks on either board these days.17:37
Pendulumdholbach: thank you :)17:37
pleia2dholbach: thanks :)17:37
s-foxI would look to get myself put  on that board, except it conflicts with my work day17:37
mhall119is there anything else for membership boards, before we run out of time to sync with kubuntu folks?17:37
valoriethank you, mhall11917:38
s-foxPendulum,  i think this is the time to mention the renewals17:38
Pendulummhall119: That's it :)17:38
pleia2#agreed extend nomination period for membership boards so we can reach out to locos to find more for 1200 slot17:38
s-foxlol17:38
dholbachI'd like to thanks everyone on the Membership Boards for their hard working and stepping in when other board members couldn't make it. It's fun to get to chat with aspiring Ubuntu members, but it's also hard to make a decision. So thanks a lot everyone! :)17:38
pleia2#topic Kubuntu catch up17:39
=== 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 | Community Council Meeting | Current topic: Kubuntu catch up
yofelo/17:39
valorie\o/17:39
valoriehi folks, we took notes in advance of this meeting: https://wiki.kubuntu.org/Kubuntu/CCmeeting17:40
dholbachhello everyone!17:40
mhall119yay notes!17:40
valoriehowever I can put in the items one at a time so they are here in the backlog17:40
valoriefirst, thank you for asking to catch up with us17:40
valorieit's lovely to meet with y'all17:40
valorieso, since we last met, we've encountered some issues. Summing up:17:41
shadeslayerheya17:41
valorieSince last year, the threats of legal action against Mint and other derivative distributions have upset our community. We were disappointed in the reaction of the CC -- it seemed to us that the CC was just doing as Canonical directed, rather than work with Mint to bring them into the community.17:41
valoriecomments?17:42
mhall119first I'd like to say that the CC intesely discussed this for months trying to A) understand it and B) come to consensus on it17:42
valoriewe don't expect a change, frankly17:43
valoriebut we're disappointed about that17:43
mhall119it's a complex issue that has little to do with technology or community, and a lot to do with vague legal precedence and laws17:43
valoriefrom our pov, legal issues never had to come into it, if a friendly hand had been extended17:44
mhall119extended to whom?17:44
valoriethe mint community17:44
mhall119I believe the Mint community is statisfied with what was offered and how it was offered17:44
valoriecool17:44
mhall119we never heard anything from them, despite multiple requests for their input on the subject17:45
valorieI don't want to bang on about this, but as far as we know, their first contact was vague legal threats17:45
mhall119speaking personally, I requested advice on this subject for Qimo and was given a similar trademark usage license from Canonical17:45
valorierather than friendliness17:45
shadeslayerI'm still quite fuzzy on how this works for ubuntu derivatives btw, does this mean trademarks are enforcable on packages just because the version has the string "ubuntu" in it?17:46
mhall119valorie: we know there were many contacts, and again we never heard anything back from the mint community on it17:46
pleia2we don't have control over what Canonical legal did, we didn't even know about this until after and thats when we attempted many times to make friendly contact17:46
valoriewell, you are already rather friendly with ubuntu and canonical michael!17:46
mhall119shadeslayer: no, it's much more complex and legally than that17:46
pleia2we really did the best we could, for months, it was agonizing17:46
mhall119valorie: doesn't matter to the legal team :)17:46
shadeslayeror does this only extend to art assets and code specifically from Canonical which can be mis interpreted as being representative of the ubuntu trademark17:46
valoriepleia2: yeah, we realize that17:46
shadeslayermhall119: oh my :(17:47
valorieanyway, water under the bridge17:47
mhall119the tl;dr of the whole story is that Mint was on questionable legal grounds with what they were doing, and the license offered to them firmed that up for them17:47
valorieOK. next item: We continue to feel apprehension over Wayland/Mir situation, which has brought the Ubuntu brand into controversy, and has caused a lot of bad feelings from our upstream. We hope for peace and technical excellence.17:48
shadeslayermhall119: okay, does this also extend to other ubuntu derivatives?17:48
shadeslayeror was it something specific to Mint17:48
pleia2we can make our input known to Canonical, and they do typically respond to us, but at the end of the day Canonical owns the trademarks and handles the legal team17:48
valoriesorry, shadeslayer17:48
pleia2shadeslayer: as mhall119 said, his distro also approached legal and got a similar agreement offer17:48
mhall119shadeslayer: it depends on whether what they are doing falls under an existing license grant or not17:48
shadeslayerso anyone who doesn't sign the license grant could potentially face legal action?17:49
mhall119for Qimo, because we weren't just a remix of packages in the archives, we didn't get the existing grant that covered the archives17:49
dholbachvalorie, are there specific technical points right now which are seen as problematic right now and should be raised anywhere?17:49
valorieoh, technical -- you are asking the wrong person17:49
shadeslayeror am I mis interpreting :)17:49
mhall119shadeslayer: Canonical isn't sueing people over this, we're giving them a cheap or free license that guarntees that we can't sue them over it17:49
valorieright now, things are OK17:49
valorieMir isn't released17:49
dholbachvalorie, or anything concrete which needs to be resolved right now?17:49
shadeslayermhall119: roger17:49
valoriedholbach: as I understand it, as long as there is a libwayland17:50
sabdflshadeslayer, yes, it does, which is why we have the remix framework to support people doing pretty much what they want17:50
sabdflin other words, we went to a lot of trouble to enable freedom of remixing, both legally and in practice with supporting tools, processes and resources17:50
valoriewe'll be fine17:50
mhall119IIRC, there was some technical concerns about how we would support both Mir and Wayland compositors on the same system, especially if Mir was also running as a system-level-compositor17:50
ScottKThe technical point re Mir is really about Wayland support.17:51
shadeslayerre Mir situation, I think the big concerns are patching things like mesa, drivers and how difficult/easy will it be for Kubuntu and KDE to use wayland since that's what our upstream is pushing for17:51
mhall119with the move to SystemD and logind, I'm not sure if we're still going to have a system-level compositor or not, but that's out of scope for this meeting anyway17:51
valorieyes, I can only speak for the community concerns17:51
ScottKIf Wayland doesn't work well, we're in trouble.17:51
shadeslayerright ^^17:51
valorieI don't like the tone of the controversy17:52
dholbachin any case we'd be happy to help bring people to a table together to resolve these technical issues and find solutions17:52
mhall119ScottK: so is the concern over the amount of support and QA we'll give Wayland?17:52
valorieand it has made things touchy with our upstream people17:52
sabdflwe have very pointedly not been going around threatening people with legal action17:52
sabdflhowever, we also would not be serving the community interest by failing to point out the rules of the community itself17:52
sabdflwe all feel good when the GPL is enforced, that depends on amongst other things respect for laws and rights17:52
mhall119as far as I know, there's nothing to stop KDE and Kubuntu from using a Wayland compositor on Ubuntu17:53
ScottKAnd the degree to which distro patches for Mir support hurt Wayland or upstream willingness to consider issues on our platform.17:53
valoriethat sounds good, and I'm hoping for the best17:53
mhall119ScottK: distro patches to what?17:53
dholbachScottK, are there current technical issues you're aware of? or is this about potential issues in the future?17:54
ScottKMesa etc.17:54
sabdflScottK, you can count on us to go beyond even reasonable lengths to accommodate alternative views of the world17:54
ScottKPotential.17:54
mhall119ScottK: so what exactly is the concern, than an upstream will refuse Mir patches, and they refuse to support KDE on a system that carries those patches?17:54
sabdflin other words, we are not going to prejudice something on Wayland just because we like Mir17:55
dholbachI think I speak for us all, that if there's ever a concrete issue regarding, the CC will be happy to help bring the right people together to find a solution17:56
sabdflwe have always managed to cross these bridges between the people who cared and were willing to do the work17:56
yofeldholbach: it's mostly that we would like people to be aware that no matter how well mir shold be integrated at least we'll need a system where mir stays out of the way, and the next CC/Kubuntu meeting will likely be after the time where issues might pop up17:56
mhall119yeah, I think we can firmly state that both Mir and Wayland should be fully supported in Ubuntu, and if for any reason they are not then action should be taken (by the CC or others as appropriate) to correct that17:57
mhall119ScottK: so, tl;dr, Wayland compositors will not be treated like second-class citizens in Ubuntu17:57
dholbachyofel, if you are that concerned about a specific future issue, we should probably discuss it at the next UDS17:57
sabdflmhall119, modulo that you can't bind others to do the work, you could reasonably say it would be anti-social to BLOCK someone doing the work17:57
dholbachsorry, UOS17:57
dholbachwhich is just in a few weeks17:57
ScottKIt's s challenge for Kubuntu because we've always leveraged Canonical work on the display stack and it's going to get harder for us to an unknown degree.  That's good to hear.17:57
mhall119sabdfl: yes, and also we can encourage people do help do the work17:57
valoriewhich brings me to our next point: we are missing our face-to-face UDS meetings with the rest of the Ubuntu community. Last year and again this year we've arranged a Kubuntu meeting at the KDE yearly meeting, Akademy. Last year we met in Bilbao, this year it will be held in Brno, in the Czech Republic. However, we really miss being able to touch base with the rest of the Ubuntu community.17:58
dholbach10th – 12th June 201417:58
mhall119valorie: I think we all miss that17:58
sabdflvalorie, we miss you too!17:58
valorieBrno is beautiful, I hear.....17:58
valorie:-)17:58
sabdfl:)17:58
czajkowskivalorie: as is everyone also :)17:59
sabdfli'll be called to another commitment shortly, here's an update on the legal front17:59
shadeslayerofcourse, open invitation to anyone who wants to come and help kubuntu btw ;)17:59
yofeldholbach: ok, thanks, we'll try to bring things up there too so it's not forgotten :)17:59
czajkowskiCzech should be nice :)17:59
dholbachyofel, rock and roll! :)17:59
sabdflwe've worked through our public trademark, copyright and patent policy with SFLC17:59
sabdflwe will make some clarifications based on their advice17:59
shadeslayersabdfl: sounds excellent :D17:59
shadeslayermuch appreciated18:00
yofelthat'll be great :)18:00
valorieok, on to the present18:00
sabdflthe exact position of who can assert what is not simplistic - it varies a lot based on package, license, toolchain, jurisdiction18:00
valorieWe have our own webserver now, at Kubuntu.co.uk. Kubuntu.org will be moved there soon.18:00
valoriewe hope18:00
valoriestill in the moving and testing phase18:00
sabdflwhen folks have made sweeping assertions about "what can be claimed" they are quite obviously not aware of that complexity18:01
shadeslayersabdfl: I think that's primarily because things were quite vague in the beginning18:01
sabdflthe net position is this: if you are making a binary derivative of Ubuntu, including lots / most of the packages and pointing to Ubuntu repo's, you do in practice need to have an agreement with Canonical18:01
ScottKPeople also get can and should mixed up.18:02
sabdflwe have made a "public agreement" in the form of the remix guidelines18:02
mhall119valorie: will you be able to migrate your wiki docs to the new server?18:02
sabdflthat says "join the project and work in the archive and you can pretty much do what you want just call it a remix"18:02
sabdflthat's got good social karma - participate and benefit18:02
valoriemhall119: we're now using the KDE wikis to develop our user docs, and some community wiki pages. Moin moin is just not reliable. We've gained some more translations this way for the documentation. We ran out of people who were experts in Docbook, which is why we started using the MM wiki. http://userbase.kde.org/Kubuntu is for writing; when docs are done they are moved to the website.18:03
sabdflMint took the view that they did not have to contribute, breaking the social contract18:03
valoriethat's what we did for Trusty and it worked ~pretty well18:03
mhall119ok18:03
shadeslayerre moin moin not being reliable, this is what I get when I tried to login today : http://imgur.com/Mcpajig18:03
sabdflit's important for us to be clear that this is not acceptable, for me, or hopefully for anybody else too18:03
valoriemoinmoin just got harder and harder to use18:04
mhall119shadeslayer: ew, openid errors, that's not good18:04
mhall119shadeslayer: did you file a bug?18:04
valoriewhich is what we used for saucy18:04
shadeslayermhall119: not yet, I just got it when I tried to use it after a long time today :P18:04
czajkowskisabdfl: thank you for the clarification18:04
dholbachshadeslayer, valorie: it might be worth raising this in #canonical-sysadmin as well18:04
valorieyes, we've filed some tickets with them18:05
shadeslayermhall119: But it's just a pain to use with all it's timeouts and what not, the KDE MediaWiki instances is such a breeze to use :)18:05
ScottKsabfl: Will you define what contribute means?18:05
sabdflnonetheless, we didn't exactly beat Mint over the head with a lawyer, we asked them to sign an agreement that would enable them to keep doing what they do without contributing, though it did limit commercial activity18:05
ScottKI think it shouldn't be just about packages.18:05
shadeslayermhall119: which is primarily we now house documentation and policies there18:05
sabdflScottK, upload to the archive, build from there18:05
ScottKWe had one derivative sponsor a sprint.18:06
mhall119ScottK: mint has a lot of packages that don't get submitted to the archives, and changes to packages without those changes being submitted to the archive18:06
czajkowskivalorie: shadeslayer can we  follow what sabdfl is sayig right now and come back to wiki in a moment18:06
sabdfland ScottK we have traditionally been generous in interpreting that, because sometimes you can't strictly build from the archive even if you are generally contributing / uploading there18:06
czajkowskiit's getting lost in the conversation18:06
shadeslayerok18:06
sabdflMint is not doing this. There have been a fewother MUCH BIGGER companies that tried to do the same thing18:06
ScottKRight.  I'm not too worried about Mint per se.18:06
sabdflok18:06
sabdfli am sure we'll work something out with Mint18:07
ScottKWe have a derivative that wanted 12.04 plus current KDE.18:07
mhall119ScottK: it's impossible to make one blanket statement when there are so many ways for derivatives to operate, we cover the specifics we can clearly define (pure remixes) and take others on a case-by-case basis (Mint and Qimo)18:07
ScottKCan't do that in the archive.18:07
sabdflbut it would help if there were a wider appreciation for the fact that Mint are fundamentally outside our social constructs18:08
ScottKIt'd be nice if that kind of derivation were clearly allowed.18:08
mhall119ScottK: again though, "that kind" isn't a specific enough definition to give a license grant to18:09
sabdflScottK, we do allow for it in practice, we've never even raised an issue with folks doing an external build of stuff the way you describe18:09
sabdflespecially if "current KDE" is in a PPA or the main archive18:09
sabdflin other words, if other members of the community can benefit from it18:09
sabdflok, have been called away18:09
mhall119ScottK: the question isn't "what is allowed", it's "what is covered under an existing grant"18:09
ScottKAgreed, but absent that understanding the discussion about Mint concerns others.18:09
elfysabdfl: thanks :)18:10
sabdflcheers18:10
dholbachI will need to rush out now as well. Thanks a lot everyone!18:10
mhall119ScottK: there was a fair amount of fear-mongering around that issue too, nobody was up in arms about Qimo needing a similar grant :)18:10
mhall119we're 10 minutes over time, is there anything else before we wrap up?18:10
valoriewell, Peppermint is for sale; you don't sell Qimo18:10
valorieyes, I was trying to finish....18:11
mhall119valorie: depends on how much you're offering :)18:11
valoriefinal present point: We are wondering about the state of donations. On the donations page, a report is promised, but we've not seen one, and none are linked to. http://community.ubuntu.com/help-information/funding/18:11
czajkowskivalorie: pleia2 has asked Jono for this18:11
czajkowskiwe'll ask him again for it.18:12
mhall119as have I, and I will ask him again18:12
valorieso far, when we've asked for funding, we've gotten it18:12
jonomy apologies, I will get this out this week18:12
shadeslayer^^ Thanks alot for that18:12
czajkowskia lot of people are asking about it so it would be good for once and for all to get a post out about it18:12
mhall119thank you jono!18:12
shadeslayer\o/18:12
valorieso this isn't a complaint, just an ask for a report18:12
czajkowskijono: thank you!18:12
jonoterribly sorry for the delay18:12
valoriecool18:12
czajkowskijono: no worries we understand18:12
jonothanks18:12
shadeslayeryep :)18:12
czajkowskivalorie: I'm glad to hear though people use it18:12
valorieas for the future: Discussing how to handle KDE's new Frameworks and Plasma Next. In 14.10 we'll be rather conservative, and offer the newest stuff being released this summer in PPA. We may be able to spin an ISO of this software; we are still pondering our best path forward.18:12
elfyjono: thanks - with my Xubuntu hat on too ;)18:12
czajkowskiit seems some people still don't know about it existing18:12
shadeslayerczajkowski: it's been immensly useful18:12
jonoelfy, :-)18:12
mhall119valorie: bringing that back around, if anybody in the Kubunu community needs sponsorship to attend Akademy to represent Kubuntu, they can apply for that18:13
valorieI've done so!18:13
valorie\o/18:13
mhall119valorie: "newest stuff" being KDE stuff or Qt stuff?18:13
valorieboth18:14
shadeslayerespecially seeing how plasma next and frameworks will have short cadence cycles to get things stabalized initially, we'll have to figure out how that plays with the Ubuntu archive policy18:14
mhall119are Kubuntu and the SDK teams talking to each other to sync up on Qt dependencies?18:14
valoriewe're sort of doing this one step at a time18:14
valoriemhall119: I think ScottK just wrote about that18:14
shadeslayermhall119: we are working with the ubuntu team in general, ScottK sent an email to discuss having 5.3 in Utopic18:14
mhall119ok18:14
ScottKmhall119: Not very effectively so far.18:15
mhall119the SDK in particular should be involved in that discussion too18:15
ScottKWe'll see how it goes18:15
ScottKWe had a session last UDS.18:15
mhall119ScottK: let me know if you need me to grease any wheels there18:15
czajkowskiScottK: is there any way we can help imrprove that ?18:15
mhall119the SDK team just *loves* hearing me ask for more things :)18:15
ScottKSomeone answer the mail I sent to u-devel (although I didn't check today if someone already did).18:16
yofelI haven't seen one either18:17
shadeslayernot that I'm aware of ^^18:17
mhall119also, FWIW, I made a website to combine Qt API docs with Ubuntu UI Toolkit API docs: https://launchpad.net/ubuntu-api-website which the KDE and/or Kubuntu projects are welcome to use if they want to do something similar18:17
elfyScottK: I've not seen a reply to the mail18:18
ScottKWe'd use the upstream Qt5 docs.18:18
shadeslayermhall119: fwiw one of my colleague's who's working on plasma components is quite impressed with Ubuntu's Qt components, so kudos for that :)18:18
mhall119shadeslayer: I saw on G+ :)18:19
shadeslayer;)18:19
mhall119even had the performance metrics widget ported18:19
valoriemhall119: you might follow the frameworks folks after awhile -- they may save you some work18:19
shadeslayeryep18:19
ScottKBut it doesn't help the FOSS ecosystem until it's upstream.18:19
ScottKGotta go.18:19
mhall119ok, is that a wrap then?18:20
* valorie needs to go as well18:20
valoriethank again for asking us to catch up18:20
mhall119thanks everyone18:20
valoriethanks, I mean18:20
yofelpretty much all from us for now18:20
mhall119and keep up the fantastic work18:20
pleia2thanks for bringing up these issues in such an organized way, hooray for wiki prep :)18:20
yofelthanks everyone for the time18:20
valorie:-)18:20
shadeslayercheers :), have a fun evening18:20
mhall119you can always ping us anytime if one of these issues need more immediate attention from us18:20
elfythanks everyone :)18:21
pleia2#topic Any other business18:21
=== 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 | Community Council Meeting | Current topic: Any other business
mhall119or email rather, that would be better18:21
pleia2real quick, anything else?18:21
mhall119not from me18:21
elfynor me18:21
pleia2ok, thanks everyone :)18:21
pleia2#endmeeting18:21
=== 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 Thu May 15 18:22:10 2014 UTC.18:21
meetingologyMinutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2014/ubuntu-meeting.2014-05-15-17.01.moin.txt18:21
mhall119dang, doesn't look like my #agreed did anything18:23
=== Ursinha is now known as Ursinha-afk
=== Ursinha-afk is now known as Ursinha
=== broder_ is now known as broder

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