/srv/irclogs.ubuntu.com/2015/09/03/#ubuntu-meeting.txt

=== zukeprime is now known as rayq
=== kickinz1 is now known as kickinz1|lunch
barrymumble seems unhappy15:01
infinityI was just going to say.15:01
slangasekalas15:01
* slangasek waves15:01
bdmurrayworks for me15:01
* barry renames it grumble15:01
slangasekyeah, it's working here15:01
cyphermoxworks here15:01
barrybdmurray: rejects password15:01
infinityYeah, reject for me too.15:02
cariboubarry: here too15:02
tdaitxnot working here, bad password it says15:02
slangasekhmm15:02
infinityOh, SSO is down.15:02
tdaitxyeah15:02
slangasekoh?15:02
barryi guess it only hates some of us15:02
cyphermoxthen it just went down15:02
slangasekor some of us already had valid tokens?  because I connected after barry said it wasn't working15:03
barryslangasek: that could be15:03
slangasekI guess if it's an SSO problem, other chat solutions are also out at the moment ;)15:03
barryi'm connecting on a different box15:03
slangasekwell, first thing's first15:04
slangasek#startmeeting15:04
meetingologyMeeting started Thu Sep  3 15:04:03 2015 UTC.  The chair is slangasek. Information about MeetBot at http://wiki.ubuntu.com/meetingology.15:04
meetingologyAvailable commands: action commands idea info link nick15:04
slangasek[TOPIC] Lightning round15:04
=== meetingology changed the topic of #ubuntu-meeting to: Lightning round
slangasek$ echo $(shuf -e barry doko bdmurray slangasek caribou infinity sil2100 robru cyphermox pitti tdaitx)15:04
slangasektdaitx doko infinity slangasek robru sil2100 caribou barry pitti bdmurray cyphermox15:04
tdaitxhurray!15:04
tdaitxCurrent15:04
tdaitx- Fixed FTBFS in bluez-tools (LP: #1489661, Debian #797128); forwarded fix upstream (accepted)15:04
tdaitx- Fixed FTBFS in bluez-tools (LP: #1490204, Debian #797356); fowarded fix upstream (accepted)15:04
tdaitx- Fixed FTBFS in opencsg (LP: #1490091); no debian backport, debian does not use opengles2 for qt4-x1115:04
tdaitx- Fixed FTBFS in jruby (LP: #1490323)15:04
tdaitx- Fixed FTBFS in openscad (LP: #1489992)15:04
tdaitx- Updated libjoda-time-java from 2.7 to 2.8.2 (LP: #1491530, Debian #797842)15:04
ubottuLaunchpad bug 1489661 in bluez-tools (Ubuntu) "bluez-tools FTBFS on wily-proposed due to AM_LDFLAGS misuse" [Undecided,Fix released] https://launchpad.net/bugs/148966115:04
tdaitx- Investigating JRuby FTBFS due to failing spec tests (LP: #1491526); seems like many are due to build environment setup (eg. non-existing $HOME); local chroot has 2 failures and 2 errors, lp build has 21 failures and 13 errors15:04
ubottuDebian bug 797128 in bluez-tools "bluez-tools FTBFS on wily-proposed due LDFLAGS misuse" [Important,Fixed] http://bugs.debian.org/79712815:04
tdaitx- Investigating openscad FTBFS on armhf (LP: #1491553, Debian #797816); there are lots of failures in LP and Debian due to conflicting declaration between GL and ES2 (search for "khronos_ssize_t gl3.h"); any reason not to define "khronos_ssize_t" as "ptrdiff_t" instead of "signed long int"?15:04
ubottuLaunchpad bug 1490204 in bluez-tools (Ubuntu) "bluez-tools FTBFS on wily-proposed in 64-bit archs due to implicit pointer conversion" [Undecided,Fix released] https://launchpad.net/bugs/149020415:04
tdaitx- Setting up JCK 7 to run localy for trusty15:04
tdaitxNext week15:04
ubottuDebian bug 797356 in bluez-tools "bluez-tools FTBFS in 64-bit archs due to implicit pointer conversion" [Important,Fixed] http://bugs.debian.org/79735615:05
tdaitx- Guarantee that local JCK 7 tests are running fine for trusty, then move those to canonistack15:05
ubottuLaunchpad bug 1490091 in opencsg (Ubuntu) "opencsg 1.4.0-1 FTBFS on armhf" [Undecided,Fix released] https://launchpad.net/bugs/149009115:05
tdaitx- Additional tests for JDK6 TLS 1.1 and JDK7 TLS 1.2 backports, need to reproduce user report as I might have a regression in JDK 7 (LP: #1482924)15:05
tdaitx- Setup and use umt schroots, check if that setup is closer to15:05
tdaitxWaiting/On hold15:05
ubottuLaunchpad bug 1490323 in jruby (Ubuntu) "jruby FTBFS due to missing libjzlib-java dependency" [Undecided,Fix released] https://launchpad.net/bugs/149032315:05
tdaitx- Reviews by OpenJDK project of the TLS backports for JDK6 and JDK 7 still requires OCA clearance15:05
tdaitx(done)15:05
ubottuLaunchpad bug 1489992 in openscad (Debian) "openscad ftbfs in wily" [Unknown,New] https://launchpad.net/bugs/148999215:05
ubottuLaunchpad bug 1491530 in libjoda-time-java (Debian) "Update libjoda-time-java to 2.8.2 to fix timezone" [Unknown,New] https://launchpad.net/bugs/149153015:05
ubottuDebian bug 797842 in libjoda-time-java "libjoda-time-java: Update libjoda-time-java to 2.8.2 to fix timezone" [Wishlist,Open] http://bugs.debian.org/79784215:05
ubottuLaunchpad bug 1491526 in jruby (Ubuntu) "jruby FTBFS when running mspec tests" [Undecided,New] https://launchpad.net/bugs/149152615:05
ubottuLaunchpad bug 1491553 in openscad (Ubuntu) "openscad FTBFS in armhf due to conflict declaration of headers gl3.h and glew.h" [Undecided,New] https://launchpad.net/bugs/149155315:05
ubottuDebian bug 797816 in openscad "openscad FTBFS in armhf due to conflict declaration of headers gl3.h and glew.h" [Important,Open] http://bugs.debian.org/79781615:05
ubottuLaunchpad bug 1482924 in openjdk-7 (Ubuntu) "Regressions due to USN-2696-1" [Undecided,New] https://launchpad.net/bugs/148292415:05
doko- GCC: build for POWER8, two backports for regressions on ARM32 and ppc64el, branch updates, package libstdc++fs.a15:05
doko- openjdk-7 update15:05
doko- gdal & friends transition15:05
doko- boost1.58 transition, removed boost1.55, and old icu15:05
doko- again, helped kubuntu with transitions. now all migrated15:05
doko- cleared NBS15:05
doko- almost cleared update_output.txt15:05
doko- tracked down cyclicy dependencies in java packages (gradle, groovy2, stringtemplate4, one more) and asked for manual builds15:05
doko- updated java related, which were behind in debian15:05
doko- llvm-3.7 final, still ftbfs on i386 and powerpc15:05
doko- some python3.5 related fixes15:05
doko- integrated some pending openjdk-8 patches15:05
doko(done)15:05
infinity[ Short week, due to illness ]15:05
infinity- Kernel SRU work15:05
infinity- NEW reviews15:05
infinity- General SRU/AA work15:05
infinity- Infrastructure work15:05
infinity- Discussions and planning for s390x bootstrap15:05
infinity- More glibc 2.22 work, expect upload Fri/Mon15:05
infinity(done)15:06
slangasek * follow through on g++5 transitions, mostly reverting library name changes that Debian has opted not to take15:06
slangasek * code review of ci-train code for new jenkins job security model15:06
slangasek * ramping up for the s390x port15:06
slangasek * working with dannf on getting edk2 buildable for arm64 with gcc515:06
slangasek(done)15:06
slangasekrobru:15:06
robrulp:cupstream2distro15:06
robru - set PPA description to show silo configuration15:06
robru - include tests in code coverage report, revealing some unused test helpers I've now deleted15:06
robru - Define an 'install' target in the makefile which installs needed deps, so that they're no longer defined in 3 different places (s-jenkins -ci and -autolanding jobs, plus charm)15:06
robru - Eliminate honor system allowing trainguards to spoof core devs during silo publication15:06
robru - better error messages for some failure conditions15:06
robru - workaround some lazr/lplib bugs15:06
robru - instead of using bot name in debian/changelog, use request creator's name15:06
robrulp:bileto15:06
robru - add some new API endpoints to ease common use cases15:06
robru - merge dashboard into requests page, dropping a ton of redundancy15:06
robru - Unify 3 disparate dependency definitions into one central location in the Makefile in trunk.15:06
robru - redirect to the newly created request when creating new requests, and dim the submit button when submitting, should alleviate users creating lots of duplicate records15:06
robru - initial db migrations, adding some columns and changing some column types as necessary15:06
robru - fix URL linkifier regex to not break when URL ends with punctuation15:06
robrulp:canonical-mojo-specs15:07
robru - new upgrade spec dramatically simplifying production rollout procedure15:07
robruMad Max game15:07
robru - Cleared Chumbucket's territory15:07
robru - cleared a decent area of Jeet's territory15:07
robru(fin)15:07
barryrobru: was that last bit just to see if we're paying attention? :)15:07
robrubarry: ;-)15:07
tdaitxwell, it did get my attention15:08
caribousil2100 doesn't seem here15:08
robruvacation15:08
caribouk then my turn15:08
slangasektdaitx: package builds shouldn't rely on $HOME being set fwiw; if something wants to write to $HOME during the build, create a scratch directory inside the package build tree and set the env var to point there15:08
caribouBugfix:15:08
caribou - lucid -> precise -> trusty upgrade issue15:09
caribou   * Unbootable system after upgrade (LP: #1491894)15:09
ubottuLaunchpad bug 1491894 in grub2 (Ubuntu) "lucid to precise to trusty upgrade may leave system unbootable" [Undecided,New] https://launchpad.net/bugs/149189415:09
caribouMerges:15:09
caribou - rsyslog merge : spent most of the time on merging 8.1215:09
caribou   then fixing FTBS. rsyslog 8.12.0-1 is now available15:09
caribouInvestigate Core Dev application15:09
caribou☑Done15:09
barrypy35 transition ongoing15:09
barrydh-python syncpackage testing (pyqt5, mock, mako);15:09
barrymain+flavor ftbfs analysis (see ppa-status script);15:09
slangaseksil2100 is on vacation yes15:09
barryfiling bugs, fixing bugs where possible, detailed ftbfs analysis (sometimes due to deps several levels deep), contacting upstreams, status reports.15:09
barrypython-pykmip w/o python3-enum34 (removed from archive).  python-zeroconf 0.17.2-1.  deja-dup 34.0-1ubuntu3 (succeeds in archive, fails in ppa due to libunity ftbfs).  chatting w/zyga re: checkbox ftbfs.  LP: #1491162.  autopilot ftbfs (succeeds in archive, fails in ppa due to testtools).  six 1.9.0-5.15:09
ubottuLaunchpad bug 1491162 in six (Ubuntu) "FTBFS in Wily" [Undecided,Invalid] https://launchpad.net/bugs/149116215:09
barrywill be sending detailed summary to ubuntu-devel later today15:09
barry--done--15:09
slangasekpitti has a conflict this afternoon but sent me his status15:10
slangasekapport:15:10
tdaitxslangasek, do you recall any package that does that? I would like to take a look and replicate it15:10
slangasek- several bug fixes/optimizations requested by bdmurray (#1487174, #1485773, etc.)15:10
slangasek- stop requiring apt lists to make origin check work with system-images (#1489410)15:10
slangasekautopkgtest:15:10
slangasek- Spent way too much time trying to find a non-hackish solution to detect and clean up leaked background processes which cause eternal hangs (hello deja-dup tests!) (#1488359)15:10
slangasek- various bug fixes and stabilization from daily test watching15:10
slangasek- enable britney/cloud testing for precise (mostly for kernel/dkms)15:11
slangasek- Implement autopkgtest/worker/britney changes for running DKMS tests against multiple kernels15:11
slangasek- Finish documentation: https://wiki.ubuntu.com/ProposedMigration/AutopkgtestInfrastructure15:11
slangaseksystemd:15:11
slangasek - resumed working on networkd integration, have if-up.d/if-post-down.d/ support working now (in review)15:11
slangasek - package 225, various bug fixes15:11
slangasekmisc:15:11
slangasek - fix various package test regressions to unblock stuff in -proposed15:11
slangasek - clean up and generalize SRU policy for new LTS features, send proposals to TB15:11
slangasek - big catch-up on bug triage15:11
slangasek(done)15:11
infinitytdaitx: If a testsuite actually relies on $HOME in a way that's a pain to patch out, you can just mkdir foo && HOME=foo ./testsuite15:11
barrytdaitx: tox used to but doesn't need to any more.  you might find a solution in its older vcs history15:11
infinitytdaitx: But I generally view that as an upstream bug worth fixing.15:11
slangasektdaitx: not offhand no, but what infinity said15:11
slangasekbeing sure to also remove foo/ in the clean target then15:12
bdmurrayinvestigation into gtk+3.0 trusty crash rate increase and bucket not updating15:12
bdmurrayfound and resolved an issue with how crash reports that have previous failures to retrace are bucketed15:12
bdmurraywrote code to bucket unbucketed OOPSes15:12
bdmurraysubmitted RT regarding allocating retracers to the failed queues15:12
bdmurraymodification of daisy-retracer charm to support retracing the failed queue15:12
bdmurrayworked with webops to sort out status of retracer for the failed queue15:12
bdmurrayreview list of core files currently in swift so we can remove Utopic crashes15:12
bdmurrayrebuilt test crashes for current package versions15:12
bdmurrayuploaded fix for ubiquity package hook in apport to W15:12
bdmurraytalked to pitti about LP: #1485787 and LP: #148577315:12
ubottuLaunchpad bug 1485787 in apport (Ubuntu Vivid) "package_hook does not include package version" [High,Fix committed] https://launchpad.net/bugs/148578715:12
bdmurrayinvestigation into apport not adding origin information to foreign packages15:12
ubottuLaunchpad bug 1485787 in apport (Ubuntu Vivid) "duplicate for #1485773 package_hook does not include package version" [High,Fix committed] https://launchpad.net/bugs/148578715:12
bdmurrayfixed an issue with the bug bot OOPSing when tagging ubiquity bugs15:12
bdmurraySRU review of python-neutronclient fixing a regression in V -updates15:12
bdmurraySRU verification of T, V fix for LP: #148578715:12
bdmurrayreview of patch for software-properties LP: #138105015:12
ubottuLaunchpad bug 1381050 in software-properties (Ubuntu) ""Import Key File" fails when the path of the file has special characters" [Medium,In progress] https://launchpad.net/bugs/138105015:12
bdmurray✔ done15:13
infinity(mumble is back)15:13
cyphermox - debugging of NM autopkgtests15:13
cyphermox - sponsored/reviewed some ubiquity-slideshow MPs15:13
cyphermox - updated doxia15:13
cyphermox - sponsored golang, dh-golang15:13
cyphermox - working on ubiquity update, fixing new PEP8 errors15:13
cyphermox - skiboot (opal-prd) update and SRU15:13
cyphermox - fixing util-linux 'lscpu -p' bug on ppc64el (bug 1427995)15:13
cyphermox - debugging more parted/multipath issues: bug 147390315:13
ubottubug 1427995 in util-linux (Ubuntu Trusty) "lscpu -p is showing wrong values for Node component" [High,Fix committed] https://launchpad.net/bugs/142799515:13
cyphermox - testing ubiquity timezone map update for Pyonyang time15:13
ubottubug 1473903 in parted (Ubuntu) "parted will generate two devices when adding one partition on mpath device" [High,Triaged] https://launchpad.net/bugs/147390315:13
cyphermox - preparing rrdtool FFE for sync.15:13
cyphermoxrobru: personally, I'm still more partial to playing Minecraft in my free time, don't know about Mad MAx...15:13
cyphermox(done)15:13
tdaitxinfinity, slangasek, barry thanks, I will check if the jruby folks can update their test15:13
robrucyphermox: ;-)15:14
slangasekany questions over status?15:15
infinitytdaitx: It's widely considered very poor practice in the free software world for a build to ever leave its build tree, so shouldn't be a hard sell upstream.15:15
tdaitxinfinity, indeed, but right now I'm not sure if the mspec tests is something they own or just got from somewhere else15:16
cyphermoxno questions from me15:16
slangasektdaitx: either way, worst case is they should be able to do the same HOME= trick upstream :)15:17
slangasek[TOPIC] AOB15:17
=== meetingology changed the topic of #ubuntu-meeting to: AOB
slangasekanything else today?15:17
barrymonday is a usa holiday15:17
slangaseko yes15:17
cyphermoxMonday is a holiday in Canada too15:17
caribouas surprizing as it may seem, it is *not* a holiday in France15:17
tdaitxwut? it is a holiday in Brazil as well15:18
infinitycaribou: The French would have to work before it would make sense to observe Labour Day.15:18
dokohttp://qa.ubuntuwire.com/ftbfs/15:18
slangasekinfinity: they already celebrated it in May, be impressed that they're not taking it twice15:19
dokoat least in main, there is some stuff belonging to foundations ...15:19
barryso, summer ends in may in france?15:19
cyphermoxdoko: I'll fix up curl today.15:19
slangasekhttp://qa.ubuntuwire.com/ftbfs/#core specifically, I believe?15:19
cyphermox(not ftbfs, but you know what I mean)15:19
dokocurl isn't on this list ;p15:19
slangasekdoko: or is there something other than those that you wanted to draw attention to?15:19
cyphermoxnot yet!15:20
cyphermox:)15:20
infinitycyphermox: You mean the curl-udeb thing?15:20
cyphermoxyeah15:20
barryi'll look in to python-*15:20
infinitycyphermox: I think fixing maas is the right answer.15:20
dokoplus: http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-ppc64el-20150902-wily.html  (note these are not ppc64el only)15:20
cyphermoxinfinity: it is15:20
infinitycyphermox: Given that curl-udeb was empty before it was dropped, so they can't possibly have been using it. :P15:20
cyphermoxoh, it was?15:20
infinityYeah.  That's why it was dropped.15:20
infinityIt was clearly broken for several releases.15:20
cyphermoxheh15:20
infinityWith not a single person complaining.15:20
infinityWhich is a fair sign no one was using it.15:20
barryhahahaha dep-wait on pypy*15:21
dokobarry, look first at the pypy MIR, then these will clear up ;-P15:21
dokodh-exec15:21
cyphermoxinfinity: it's not a very much used feature, it's mostly just enrolling maas devices via the ISO15:21
dokorpm15:21
cyphermoxI'll ask harder if we can just drop that altogether...15:21
dokosssd?15:21
infinitycyphermox: Oh, the "enlist in MaaS" bootloader option on the server CD?15:21
dokolibpod-readme-perl15:22
infinitycyphermox: If that actually relied on curl-udeb, they haven't tested it in years...15:22
cyphermoxinfinity: well, it's maas-enlist-udeb that requires curl-udeb15:22
slangasekdoko: heh, rpm shows up as part of the ubuntu-desktop package set, not core15:22
infinitydoko: sssd is RAOF's.15:22
cyphermoxthe only thing I could think of to use that was the enlist in MAAS option from the CD15:22
dokoand a lot of perl stuff here: http://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg15:22
infinitycyphermox: Your logic is sound, but they supposedly test that feature.  So, could need more investigating.15:23
cyphermoxeasy enough to test anyway15:23
infinityOh look, another java/maven explosion.15:23
infinityWhy, java, why?15:23
infinitydoko: The majority of those perl modules can probably get hand-waved in with a minimal review and subscriber, but I guess we should file a big bug and go through the motions.15:24
slangasektdaitx, robru: http://qa.ubuntuwire.com/ftbfs/#core should be driven to zero for release, can you take a look at these and see which ones you can help with?  (feel free to ask any of the core-devs if you have questions)15:24
robruslangasek: sure15:25
tdaitxslangasek, sure15:25
dokoinfinity, likely, but maybe check as well if they are maintained by the perl team15:26
cyphermoxinfinity: http://paste.ubuntu.com/12263705/ don't think they were testing it, otherwise it magically worked without that for some reason15:26
infinitydoko: Yeah.  Most probably are, they have most of CPAN packaged. :P15:26
cyphermox(that's from debian-cd)15:26
dokojava is known, and ruby is known too, wanted somebody to look at rails; how we can avoid it15:26
infinitycyphermox: Well, it may well be that maas-enlist-udeb doesn't actually need curl-udeb.15:27
infinityI'll pick up the firefox FTBFS, I'm sick of arguing with people about it.15:27
* pitti rentre -- qu'est-ce que j'ai perdu ? :-)15:29
slangasekpitti: un peu de ceci, un peu de c'là15:30
infinityin 25015:30
slangasekpitti: we're just about wrapped here, can you join mumble?15:30
infinity...15:30
pittiI'm in15:30
slangasekI think we're done here then15:34
slangasekunless there's anything else15:34
slangasek#endmeeting15:35
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology
meetingologyMeeting ended Thu Sep  3 15:35:54 2015 UTC.15:35
meetingologyMinutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2015/ubuntu-meeting.2015-09-03-15.04.moin.txt15:35
dholbachhello hello17:00
czajkowskiAloha17:00
czajkowskiwelcome to this weeks CC17:00
czajkowskifeels like a bit of a game show!17:00
dholbach#startmeeting17:00
meetingologyMeeting started Thu Sep  3 17:00:47 2015 UTC.  The chair is dholbach. Information about MeetBot at http://wiki.ubuntu.com/meetingology.17:00
meetingologyAvailable commands: action commands idea info link nick17:00
dholbach#chair czajkowski mhall119 pleia217:00
meetingologyCurrent chairs: czajkowski dholbach mhall119 pleia217:00
pleia2o/17:00
dholbachDo we have folks from the IRC Council and Canonical Community team here?17:01
pleia2#link https://wiki.ubuntu.com/CommunityCouncilAgenda17:01
pleia2^^ agenda17:02
balloonso/17:02
pleia2I don't think anyone sent a reminder to the IRC Council17:03
dholbachok, let's start with the community team then and I'll try to ping the IRC Council folks17:03
hggdhpleia2: a reminder was sent17:04
pleia2hggdh: oh good :)17:04
czajkowskidholbach: balloons mhall119 so life on the community team17:04
czajkowskiis dpm around17:04
dholbachthanks hggdh!17:04
hggdhbtw, hi all, long time and all that17:05
pleia2hggdh: welcome :)17:05
popeyo/17:05
czajkowskipopey: howdy17:05
dholbach#topic Catching up with the Canonical Community team17:05
=== meetingology changed the topic of #ubuntu-meeting to: Catching up with the Canonical Community team
popeyI have some opinions :)17:05
balloonsso, there's some things I wanted to bring up, but they are mostly based on popey's thoughts. I'll let him speak first if he wishes17:06
popeynah, knock yourself out17:06
czajkowskiballoons: do tell, but please don't injure you're self17:06
czajkowski:)17:06
dholbachhaha17:06
balloons:-) Ok, my first thought was bringing up how we deal with contributions. It's the second half of the lifecycle for contributing. We spend time and effort encouraging folks to contribute, but once they do, we sometimes falter17:07
* dholbach has opinions on that subject too :)17:08
balloonsThere are both good examples and bad examples of this. For instance, we do wonderfully on the core apps projects, while we have patches sitting waiting in other places17:08
dholbachyeah... I just raised the subject with the engineering managers for Ubuntu again - sponsoring and patch review for stuff going into the distro sort of went a bit on the backburner for many and patches had been piling up again17:09
balloonsI would be curious how we might be able to close this gap a bit better. Is there something collectively we could do and/or encourage the community to do to insure we are good stewards of people's contributions?17:09
popeyyeah17:09
dholbachI haven't checked other queues (NEW, SRU, +1 maintenance, MIR, etc.), but I can imagine that these might require more attention too17:10
popeyI had a ranty email from a community contributor recently who was annoyed that his merge proposals took a long time to be reviewed17:10
dholbachme too17:10
balloonsis it something we can empower the community collectively to do? AKA, are there not enough people to review the work?17:10
czajkowskipopey: how long was long?17:10
popeycould be days to weeks17:11
czajkowskiand is there way we can get more eyeballs on stuff in a more fun way to do it, as I know folks are busy but it's also a necessity17:11
popeyOne issue is many canonical people work closely on irc, and are happy to ping eachother17:11
dholbachthe patch pilot programme was supposed to guarantee that everyone within the distro team with upload rights had 4h/month (or one hour per week) to help out17:11
popeyJoe: "Hey, bob, can you review that merge on your project?"17:11
popeyBob: "Sure, I'll get to it in a bit"17:11
popeyjob done17:11
dpmo/17:11
popeycommunity person contributes and it looks like it disappears into a black hole17:11
popeyI am guilty of this too, not pointing fingers at others.17:12
dholbachI hope that we can get more energy into this again17:12
* dpm and mhall119 I were having a really interesting call with the Mycroft folks17:12
czajkowskipopey: aye I think at times the IRC ping often doesnt help folks not on irc17:12
czajkowskiwho may be working17:12
dholbachand some of the engineering managers are discussing the subject right now17:12
czajkowskiand taking things to a public mailing list to show how easy it is to get feedback ina constructive manner17:12
popeyczajkowski: indeed, and not knowing that people are approachable17:13
popeyczajkowski: and some people actually _not_ being approachable17:13
czajkowskipopey: exactly17:13
dholbachyeah, you can't say on a wiki page "ping popey to get your patch reviewed and included" :)17:13
czajkowskinail on the head :)17:13
popey(e.g. berating someone for pinging them which disturbs them, contributors should ask in public so as not to disturb individuals)17:13
dholbachthat's why we had current patch pilots in the topic in #u-devel17:13
popeyexactly!17:13
czajkowskiIt may be better to encoureage people when they see people being pinged on irc, to suggest can we move this to the ML so others can see how it's done17:14
czajkowskipopey: balloons dholbach which ml would this go to ?17:15
dholbacha request for a review of a patch?17:15
czajkowskidevel- devel-discuss, elsewhere?17:15
czajkowskidholbach: aye17:15
dholbachboth should work17:15
popeynot sure17:15
dholbachI hope that with support from management we can at least have Canonical engineers help out more regularly again17:15
czajkowskicould we try for the next few weeks to push to -devel-discuss - I know moderation can be an issue ?17:16
dholbachI'd leave the mailing list as last resort for the urgent cases17:16
popeyyeah17:16
dholbachwe shouldn't ask people to mail the mailing list for everything17:16
popeyirc is way easier / faster17:16
popeybut we shouldn't have to go round poking people17:16
balloonsI would also like to think about a way to monitor this and be proactive on our end a bit. Especially since things are backlogged now17:16
popeypeople who are upstream for a project should act like one17:17
czajkowskipopey: hmm but what about the people who want to contribute that aren't on IRC17:17
balloonsI would rather see us gently nudging upstreams to be more receptive. An MP should be enough to get the contact going17:17
dholbachhttp://reqorts.qa.ubuntu.com/reports/1glance-sponsoring/17:17
dholbachif you click on "year"17:17
dholbachyou can see that the last call for help seems to have done something17:18
balloonsyea, you can see when you issue the calls :-)17:18
popeyczajkowski: why arent they on irc? everyone is on irc.17:18
czajkowskipopey: that whole work thing :)17:18
czajkowskidholbach: nods17:18
dholbachpopey, there are upstream developers and debian folks and others who just want to do a drive by contribiution17:19
* hggdh respectully disagrees from popey17:19
popeyit was somewhat tongue in cheek17:19
* hggdh removes disagreement17:19
popeydholbach: i agree, and we should pick those up and not let them languish17:19
dholbachyep, agreed17:19
czajkowskiok17:19
czajkowskiso you mentioned other issues?17:19
czajkowskiwhat are they ?17:19
dholbachmaybe we can review in a couple of weeks again and see if the recent discussions helped change something17:20
dholbachballoons, popey: was your point mostly just about sponsoring?17:20
popeymine wasnt17:20
dholbachok, then I'll get out of the way now :)17:20
popeymine was a cultural change, more of an observation17:20
dpmI think it's about MPs and upstreams too17:20
czajkowskipopey: do tell17:21
popeyAre we done with the other topic though?17:21
balloonsmy point was about us collectively encouraging a better culture in our upstreams as well. But the boots on the ground work from dholbach is part of it17:21
czajkowskiballoons: cool can we try encouraging more people to review over the next few weeks17:21
dholbachI wonder if most developers in an upstream project are signed up for mails about new MPs...17:21
czajkowskisee if it makes a difference and if not lets come back and see if we need to take to ML or what we need to do17:22
balloonsyes, and given the changes to LP, we should encourage people to review filtering. I'm guiltly of this. I filtered out those mails17:22
balloonsbecause it was hard to get the right mix without getting overwhelemd17:22
balloonsthe lp team just redid this (I for instance often miss important mails, like renewing in a team)17:23
dholbachmaybe it'd be good to write up best-practices "how to be a good upstream" with a few paragraphs on "how to set up your project in LP"?17:23
popeyyeah, me too17:23
popeymy gmail has thousands of mails, this is why i rely on web pages with lists of things to do17:23
balloons+1, dholbach. That's the action I'd like to see, and I think we could do17:23
popeyrather than email17:23
czajkowskidholbach: brilliant idea17:24
dholbachI'm not sure if that'd solve all problems - you still need to do your reviews17:24
czajkowskidholbach: I see a to do AI for you then :)17:24
dholbachbut it could be a first good step17:24
dholbachczajkowski, erm....... I'm convinced :)17:24
dholbachbut yeah, I can have a look around and see what the current LP docs offer17:25
dholbachand bring that up for renewed discussion17:25
czajkowskinods17:25
dholbachhappy to do that17:25
czajkowskilovely jubbly thanks17:25
czajkowskipopey: so back over to you.17:25
popeyokay17:25
popeythis is an observation about our team, and not an opinion or conclusion17:26
popeySince jono left things have been a bit different.17:26
popeySo when things went "wrong" outside canonical jono would typically swoop in wearing a cape and write a blog post17:26
czajkowskinod17:26
czajkowskis17:26
popeywe tend not to do that now17:27
popeywe don't have as quite a public figure as jono17:27
popeythe role changed17:27
czajkowskiIt did17:28
popeythe result of this (IMO) is that sometimes a long time goes between adverse things happening and us responding17:28
popeysome would say thats actually a good thing17:28
popeybecause we're not knee-jerk responding17:28
popeybut taking more time and considering things rather than jumping on the PR train and writing rapid replies17:28
czajkowskipopey: I think the other thing that has happened, in that some on the team are a lot more vocal online and then get picked up as the "canonical community manager said X" but dont add the name to the role and that adds confusion, at least imo17:29
popeymy observation is that this means we (more) often go "silent" on the community about particular topics17:29
popeyI don't know how I feel about this, whether it's good or bad, whether it's seen as good or bad from outside.17:29
czajkowskiso I think taking a step back17:29
balloonsI would agree folks are a bit more gunshy on joining a topic, which leads to the banter being set for the community by others17:29
popeyI just see it more often now than in the past17:29
czajkowskitaking time to respond is a good thing17:29
czajkowskiI'm just worried that being too slow to reply leads to too much fud and not enough clearning things up in a manner I guess we're used to17:30
czajkowskiit can feel cut off and not knowing what's going on  - unless you pop on irc and ask :)17:30
czajkowskiso for me and I've said this , not having one focal main manager had been confusing especially on topics like you've just raised popey .17:31
dholbachmh, I'm not sure17:31
czajkowskipopey: part of me feels others are waiting for someone else to step in and reply and that leave it down to one or not at all.17:31
balloonsI think it's good in the sense, we are mindful about what we say. However, we are ending up being reactionary in conversations and being dragged into side conversations17:31
dholbachI mean many of us have been around for ages in the project and their voice should have relevance too17:31
czajkowskiballoons: +117:32
dholbachwhatever their job title is17:32
hggdh+117:32
dholbachand by that I don't just mean members of our team in Canonical17:32
dholbachand I don't think that relying on a single person to respond to all online discussions via blog will scale - but I have to admit that I often feel "too busy" to write a long blog post responding to whatever the discussion of the day is17:33
dholbachand I know I could blog more17:33
balloonsyes, the downside of having a single mouthpiece is all other voices have a tendency to be silent17:33
dpmI think the takeaway is also that we should all blog more, not only in reaction to a particular topic, and I am to blame on that too17:34
hggdhjono is one of a kind. But he is not here anymore. You cannot expect to keep on with his style, pretty much only he could. But you can keep on as a group17:35
czajkowskihggdh: true17:35
czajkowskiand we all have to find our own voice17:35
czajkowskiand our own way of doing things17:35
dholbachjust a quick note: the CC also is meeting the IRC Council today ... can we maybe make a list of subjects we still want to talk about?17:35
dholbachit looks like we need way more time to get through all of this, or am I wrong?17:36
czajkowskibut as popey pointed out culture changes means what we're used to is not what's happening so it was more of a discussion17:36
hggdhyes. And be vocal on it. And try to present a coherent, consistent view17:36
czajkowskiI will say that having dpm post the community team updates is brilliant!17:36
czajkowskiplease do keep that up :D  I love to read it17:36
dpmthanks17:36
czajkowskiI would also love to see more blogging of what the Community team is doing as I know I personally idle in the irc channel and can see you guys are busy17:36
dpmI've not been keeping up after travels and holidays too17:36
hggdhdpm: BTW, never said it -- thank you for the updates.17:36
czajkowskibut I'm sure others would love to see a day in the life a community team member17:37
balloonssummertime has taken a bit of a toll on things17:37
dpmso when the next sprint is over expect a new update17:37
dholbachif we have more to talk about, we could have a hangout on air and take more time to get through the issues together17:37
dholbachkind of a pre-UOS u-community-team get-together :)17:37
czajkowskidholbach: blog perhaps ?17:37
dholbachczajkowski, sorry I meant subjects popey and others wanted to bring up now17:37
czajkowskidholbach: ahh gotcha17:37
dpmbtw, so we've got ~20 mins left?17:38
czajkowskidpm: aye17:38
* hggdh warms hands17:38
czajkowskiI know dpm had a topic to bring up17:38
dpmindeed17:38
dholbachczajkowski, dpm: right, but we're also still meeting up with the IRC Council17:38
dholbachbut sure... bring it up - it looks like the meeting will run over today anyway17:39
dpmI think I don't need the whole 20 mins17:39
dpmI want to introduce the topic and follow up in the next few days anyway17:39
dpmin any case...17:39
dpm... this is a follow-up of a discussion we had at the Community Leadership Summit17:40
* balloons feels anticipation building17:40
dpmlol17:40
czajkowskidpm: no pressure17:40
dholbachthe suspense is killing me :)17:40
dpm...17:40
dpm...17:40
dpmj/k17:40
dpmso, we talked about more effective ways for teams/locos/individuals to meet up and get visibility and more attendees to their physical meetings17:41
dpmWhile we have the LoCo portal for event organization17:41
dpmit seems not all teams use it and also that it's a very Ubuntu-specific thing17:42
dpmso we don't get all the discoverability we could get17:42
czajkowskinods, it's a nice home for all the info on teams when you're searching about a loco.17:42
czajkowskidpm: that's also true17:42
=== greyback_ is now known as greyback|eod
dpmindeed, and to be clear, this is not about changing the LoCo portal17:43
dpmhowever, since we created the LP, things have changed17:43
dpmOne of the nice things about CLS was to get feedback from other open source communities17:43
balloonsso really this is about engaging folks where they already are?17:44
dpmon the infrastructure/tools they use17:44
dpmfor events17:44
dpmone of the ones that came up was meetup.com17:44
dpmI know for example czajkowski uses it over at CouchBase17:44
czajkowskinods this is true I do.17:44
czajkowskiand that was someting that came up at CLS, was more and more groups using meet up.17:45
czajkowskiand how best we could tie it into LTP17:45
dpmand I got convinced it could be a good thing to try17:45
* dpm nods17:45
czajkowskiso I think it's a good idea, and I'd love to see loco teams embrace it17:46
czajkowskiand if they don't want to also, that's equally fine,17:46
czajkowskiI think opt in would be good, looping in the LC into the discussion and dpm the funds for this will come via the community fund or canonical ?17:46
dpmThe thing that I particularly attracts me to it is that it opens the door to other open source communities that are using it to more easily see the Ubuntu events, so that we'd be no longer in our Ubuntu bubble17:46
dpmBy all means17:46
dpmI think this is a discussion that needs to happen with the CC17:47
dpmerr LC17:47
czajkowskinods i think it would open more doors for other groups to learn about ubuntu17:47
* mhall119 is here now17:47
czajkowskiand I think it's a postive step in understanding how our community is changing and adapting to it17:47
czajkowskidpm: so we do have a lmited CC here :)17:48
dholbach:)17:48
dpm:-)17:48
dholbachI haven't used meetup much yet, but I think it's worth a try17:48
czajkowskiI think the best thing as a stepping stone would be meet with the LC and involve them in this discussion if not done so already17:48
czajkowskimeet wtih meet up and then trial it with some teams17:48
dpmyeah17:49
czajkowskiand I'd love to see this plan being blogged so others can see how you guys are working with the community and loco teams17:49
balloonsI think opening ourselves up a bit more is a good thing. Things have changed and are changing. It would be best if we could empower those using other platforms to take ownership of them also. In other words, I don't want us to try and be all things to all people17:49
czajkowski:)17:49
czajkowskiand I think you can play with the API and intergrate it into the LTP17:49
czajkowskiso you could still have visibilty under one location17:49
czajkowskibut that's a dev issue :)17:49
dpmI will take an action to put together a doc to drive the discussion with the LC17:50
czajkowskibrilliant17:50
dholbachnice17:51
czajkowskidpm: will the community team be at CLS  Europe in case folks at ubuntu want to meet up with the team ?17:51
dpmWe're not planning to atm17:52
dpmBut will look into it17:52
czajkowskidpm: another action item :)17:52
balloonshttp://clsxeurope.com/ looks like it's the end of October17:52
dpm:)17:52
dpmah, it's a CLSx event17:52
czajkowskiwould be great to see the team at CLS and maybe this is something we could get some of the Ubuntu loco teams to come to and take part in ?17:52
* dholbach is at UbuConDE at the time17:53
dpmyeah, it's right on that date17:53
balloons^^ indeed, that would be the focus17:53
dpmI'm at UbuConDE as well17:53
* mhall119 will be sitting around here in Florida17:53
dpmBut perhaps we can send others who didn't make it to the last CLS17:53
czajkowskidpm: guess you need to get the team to Texas next year :)17:54
dpm:)17:54
czajkowskiright are there any other topics before we wrap up17:54
dholbachhum........17:54
dholbachthe IRC Council?17:54
czajkowskipopey: dholbach balloons dpm any other issues?17:54
hggdhyes?17:54
mhall119yes, sponsoring community leaders to go to CLS Europe would be ieal17:54
Pici\o17:54
czajkowskidholbach: you can run that bit of the meeting I need to run for a train :)17:54
dpmI'm good for today17:54
balloonssame, we've taken enough time for now17:55
dholbachthanks a lot everyone17:55
dholbachlet's move on then :)17:55
dpmo/17:55
dholbach#topic Catching up with the IRC Council17:55
=== meetingology changed the topic of #ubuntu-meeting to: Catching up with the IRC Council
dholbachsorry for keeping you waiting for so long17:55
dholbachhow are things?17:55
dholbachhow are you doing?17:56
Piciquiet.17:56
dholbachoh?17:56
hggdhtoo quiet, methinks17:56
dholbachI wouldn't have expected that answer from the fast-world-of-IRC :)17:56
mhall119bad quiet or good quiet?17:56
hggdhsince the election we have not had much done. We will be holding a IRC meeting next week, off the schedule to try to catch up17:57
dholbachbut the irc world is as busy as always, right?17:57
PiciWell, we had some issues with the server that ubottu and co was hosted on, so that was a bit frantic, but we've gotten things back together now.17:58
mhall119Pici: are there any outstanding issues now that the CC might help with?17:58
Picimhall119: I don't think so.17:58
hggdhI do not think so17:58
dholbachwho is mostly taking care of the bots these days?17:58
hggdhpici17:59
PiciI am.17:59
dholbachjust you?17:59
hggdhhe is the only one, I think with the necessary access. Which is good, otherwise we would have lost the bots for a bit longer17:59
mhall119is there a way to share that access, so it's not all on Pici?17:59
dholbachoh yeah... I have full trust in Pici - I was just asking if anyone else was helping out :)18:00
hggdhso do I :-)18:00
mhall119it's not a question of trust, I trust Pici too, but he should have a backup who can take over for him when he needs it18:01
PiciNo one else is helping at the moment, but I'd need to get something setup so that others could easily admin that part of the server in case I'm away.18:01
PiciJust a weekend project I should put in my to-do list.18:01
mhall119Pici: is this server yours or something Canonical-hosted?18:01
dholbachnice :)18:01
Picimhall119: its a small Linode instance I'm running.18:01
dholbachand speaking of helping out... are there enough folks helping out generally as ops and helpers?18:02
mhall119Pici: the community donations fund could be used to reimburse you for the cost of running it, just a reminder18:02
* Pici notes18:03
hggdhthe meeting next week should take care of most of the pending applications. -ops, though, probably needs a bit more of coverage18:03
PiciI think we had one or two applications for that, if not we can just hand it out to folks.18:04
dholbachbrilliant18:04
dholbachthanks a lot for taking care of that18:04
dholbachhow is morale generally among helpers and ops?18:04
dholbachI know that was a concern in the past18:04
hggdhhaven't heard of many complaints lately; I would venture it is better than it was before18:05
Pici*I* think that our operators are a lot better now. Things in general have calmed down a lot, not as many serial-trolls pushing their buttons lately.18:05
hggdhPici: good explanation. +118:06
mhall119that's good tohear18:06
dholbachphew18:06
dholbachI'm super happy to hear that :)18:06
hggdhso are we :-)18:06
dholbachit's not just the trolls, but also always a matter of how the atmosphere in the team is18:06
dholbachso it looks like you're doing something right :)18:07
* hggdh wonders about that...18:07
dholbachmh?18:07
hggdhI think the atmosphere got less polluted, not really what we did (for the most part I, for example, did not really do much)18:08
dholbachoh... I meant you as a whole team18:08
mhall119hggdh: leadership can do a lot to clean up the atmosphere without doing anything directly, just by setting the example18:08
dholbachatmosphere is something everyone contributes to :)18:08
hggdhindeed18:09
mhall119alright, we've used up our allotted time in this channel18:09
hggdhbut, apart from that things look good.18:09
mhall119anything else you guys want to bring up?18:09
hggdhnope, we are good.18:09
dholbachsorry again for keeping you waiting earlier :)18:09
* dholbach hugs you all18:09
mhall119thanks hggdh and Pici18:10
* hggdh hugs all18:10
dholbachthanks a lot for keeping #ubuntu-* so well organised!18:10
mhall119yes, +1 what dholbach said18:10
mhall119any other topics for the CC?18:10
mhall119from anybody18:10
* dholbach doesn't18:10
* mhall119 either18:11
dholbachhave a great rest of your day everyone - dinner is waiting for me :)18:11
mhall119thanks everyone18:11
dholbachthanks!18:11
dholbach#endmeeting18:11
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology
meetingologyMeeting ended Thu Sep  3 18:11:32 2015 UTC.18:11
meetingologyMinutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2015/ubuntu-meeting.2015-09-03-17.00.moin.txt18:11
Kiloshmm...19:55
elacheche_aniswillcooke, is here.. You're ready?19:55
willcookeelacheche_anis, hey, yup19:55
wxlwell in that case…19:55
Kiloshi willcooke19:56
wxl#startmeeting 20 UTC Membership Board Meeting19:56
meetingologyMeeting started Thu Sep  3 19:56:12 2015 UTC.  The chair is wxl. Information about MeetBot at http://wiki.ubuntu.com/meetingology.19:56
meetingologyAvailable commands: action commands idea info link nick19:56
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | 20 UTC Membership Board Meeting | Current topic:
willcookehi Kilos19:56
wxlHello and welcome to the Membership Board meeting!19:56
wxlThe wiki page for the Review Board is available here https://wiki.ubuntu.com/Membership/Boards. We will attempt to get through all of the applicants that have added themselves to that list before today's meeting.19:56
Kiloshi everyone19:56
wxlIf we are unable to make it through the entire list due to time constraints, then at the next meeting we will pick up where we left off. The format for the meeting is as follows: We will go through the list of applicants one by one, by date of application (FIFO).19:56
wxlEach applicant should introduce themselves (1-5 sentences) and provide links to their Ubuntu Wiki page. After the introduction the members of the Membership Review Board will review the pages and, if needed, ask the applicant further questions.19:56
wxlDuring this time it is encouraged for other members of the community to show their support for the applicant. Do not be alarmed if the members of the Membership Review Board are quiet during this time; they are most likely reading wiki/launchpad/forum/other pages and deciding how they are going to vote.19:57
wxl#topic willcooke19:57
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | 20 UTC Membership Board Meeting | Current topic: willcooke
wxlwillcooke:  please introduce yourself to the board, and share a link to your LP and wiki19:57
toddyhi everybody19:58
Kiloshgi toddy19:58
=== JanC_ is now known as JanC
Kiloshi as well19:58
willcookeHello board!  I've been using Ubuntu for about 10 years.  I started out supporting users on the forums and IRC, and then eventually managed to bad myself a job at Canonical.  I've done a few different jobs here but for the last year or so I've been managing the Ubuntu Desktop team.19:58
willcookeI'm a big supported of Open Source and Open Hardware.  In my spare time I like making electronic gizmos do things they weren't designed to do.19:59
willcookeLP: https://launchpad.net/~willcooke19:59
willcookeWiki: https://wiki.ubuntu.com/WillCooke20:00
wxlExcellent! Any questions for willcooke? ? Any supporters here?20:00
elacheche_anisWelcome willcooke :)20:00
elacheche_anisActually I have a question20:00
elacheche_aniswillcooke, I have no comments on you Wiki or LP :) I just love to know why you're applying for the Ubuntu Membership.. :)20:00
Kiloswillcooke  why did you take so long to apply?20:01
willcookeheh, yeah, I kept meaning to apply, but I assumed that I hadn't really done enough to warrant it.  Most of my Canonical work was kinda behind the scenes20:02
willcookebut then when I joined the desktop team people were always telling me to get on with it20:02
wxlinteresting. did you discuss that idea with anyone at all, willcooke ?20:02
willcookeso I finally did get round to it.20:03
willcookeSo popey was quite clear that I should apply and he convinced me that I had actually done enough to warrant it20:03
wxlexcellent20:03
willcookeplus rickspencer320:03
wxlgood job popey !20:03
popeynamedropper ;)20:03
willcookelolz20:04
Kiloshaha20:04
wxlhahahahah20:04
Kiloshi popey20:04
wxlany other questions or shoall we move on to voting?20:04
wxls/oa/a//20:04
toddywillcooke: do you involve in the loco in London?20:04
hggdhno questions from me. the testimonials are more than enough20:04
Kilosagreed20:04
popeythe UK loco is mostly idle20:04
willcooketoddy, not really.  I dont get down to the office so much.20:04
willcookewe "organised" a release party for 15.0420:05
willcookewhich was basically "let's go to the pub"20:05
ahoneybunlol20:05
hggdhorganised enough, I would say20:05
toddywillcooke: how many people was there?20:05
willcooketoddy, not including the desktop team, about 820:06
willcookewith the desktop team, about 2020:06
toddynice20:06
elacheche_anisloool willcooke x)20:06
dokowillcooke, what do you know about plus1 maintenance?20:06
willcookedoko, nothing20:06
willcookedoko, what is it?20:07
wxl#voters ahoneybun popey hggdh Kilos toddy elacheche_anis wxl20:08
meetingologyCurrent voters: Kilos ahoneybun elacheche_anis hggdh popey toddy wxl20:08
hggdh+1 finally, welcome20:08
wxlso i guess i'm ready to go vote if that's it?20:08
hggdhbah, jumped the gun20:08
elacheche_anisAm ready too :)20:08
Kilosditto20:08
ahoneybunI'm good to go20:08
willcookedoko, ah:  https://wiki.ubuntu.com/PlusOneMaintenanceTeam20:08
elacheche_anis+1 Keep the good work the the desktop :)20:08
wxloops hold on elacheche_anis :)20:08
popey+120:08
wxl#votesrequired 420:09
meetingologyvotes now need 4 to be passed20:09
wxlok NOW VOTE20:09
Kilos+1 keep going20:09
popey+120:09
wxl+1 hardware hackerz unite!20:09
wxloh20:09
wxlderp20:09
wxli'm new at this :/20:09
toddywe need a question20:09
elacheche_anis:D20:09
wxl#vote for willcooke's membership20:09
meetingologyPlease vote on: for willcooke's membership20:09
meetingologyPublic votes can be registered by saying +1, +0 or -1 in channel, (for private voting, private message me with 'vote +1/-1/+0 #channelname)20:09
elacheche_anisTake your time w:)20:09
hggdhah20:09
elacheche_anis+1 Keep the good work the the desktop :)20:09
meetingology+1 Keep the good work the the desktop :) received from elacheche_anis20:09
ahoneybun+120:09
meetingology+1 received from ahoneybun20:09
hggdhbah, jumped the gun20:09
popeyhah20:09
hggdh+1 finally, welcome20:09
meetingology+1 finally, welcome received from hggdh20:09
popey+120:09
meetingology+1 received from popey20:09
wxl+1 hardware hackerz unite!20:09
meetingology+1 hardware hackerz unite! received from wxl20:09
toddy+120:09
meetingology+1 received from toddy20:09
Kilos+120:09
meetingology+1 received from Kilos20:09
wxlokey dokey then20:10
wxl#endvote20:10
meetingologyVoting ended on: for willcooke's membership20:10
meetingologyVotes for:7 Votes against:0 Abstentions:020:10
meetingologyMotion carried20:10
willcooke\o/20:10
wxljeez you seem to have passed with flying colors willcooke :)20:10
wxlcongrats!20:10
ahoneybunnice one willcooke20:10
Kiloswelcome onboard willcooke20:10
willcookethanks very much everyone!20:10
Kiloswell done20:10
* elacheche_anis need to mention that willcooke already got +2 from 2 board members via the ML :)20:10
wxlthank you for all the hard work, both whilst getting paid and otherwise willcooke :)20:10
hggdhwillcooke: welcome in. Now you can look popey in the eyes and say "there. Happy?"20:10
wxlgood point elacheche_anis20:10
elacheche_anisCongrats willcooke :) Welcome aboard :)20:11
Na3iLcongrats willcooke :)20:11
Kiloshehe20:11
willcookethanks everyone20:11
wxllooks like that's about it20:11
wxlanyone else have anything else?20:11
popeynot from me20:11
willcookeI've been encouraging others to apply, so hopefully there will be more next month20:12
Kilosty for chairing wxl20:12
Kiloscool20:12
ahoneybunthanks wxl20:12
wxlthank you willcooke ! please let us know if you need further help20:12
willcookecheers wxl20:12
wxlcheers!20:12
* willcooke -> dinner time20:12
wxl#endmeeting20:12
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds: Please leave swords by the door | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendars | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology
meetingologyMeeting ended Thu Sep  3 20:12:41 2015 UTC.20:12
meetingologyMinutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2015/ubuntu-meeting.2015-09-03-19.56.moin.txt20:12
wxlwin item move 320:12
wxloops20:12
elacheche_aniswillcooke, just a quick question you can answer later.. Do you LOVE unity?! :D20:13
willcookeelacheche_anis, yes.  I love it.  It just works for me.20:13
* ahoneybun <3 Plasma20:13
elacheche_anis:D Happy to know that willcooke :D20:14
* elacheche_anis <3 awesome wm & mate :D20:14
Kilosthanks everyone20:15

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