/srv/irclogs.ubuntu.com/2014/03/20/#ubuntu-meeting.txt

=== OutOfControl is now known as benonsoftware
=== vladk|offline is now known as vladk
=== vladk is now known as vladk|away
=== vladk|away 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
=== JoseeAntonioR is now known as jose
=== 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|away
=== vladk|away is now known as vladk
=== vladk is now known as vlad|lunch
=== vlad|lunch is now known as vladk|away
=== vladk|away is now known as vlad|lunch
=== vlad|lunch is now known as vladk|away
=== vladk|away is now known as vlad|lunch
=== vlad|lunch is now known as vlad|
=== vlad| is now known as vladk|offline
=== vladk|offline is now known as vladk
=== vladk is now known as vladk|offline
=== Joeb454_ is now known as Joeb454
bdmurrayI'm ready for a meeting15:02
cariboume too15:03
cjwatsonslangasek,barry,doko,jodh,stgraber,xnox: around?15:03
* barry waves15:03
cjwatsonno infinity here15:03
MooDooI'm just here, but I'll watch any way :D15:03
jodho/15:03
dokodid we move it?15:04
cjwatsondoko: I think google calendar did15:04
cjwatsondoko: it's the weeks of confusion due to eu/us daylight savings desync15:04
* stgraber waves15:04
dokoahh, ok15:04
barrycjwatson: should i file a bug to remove dst from trusty?15:05
cjwatsonbarry: I'd like it removed from the planet, personally15:05
barry+115:05
cjwatson#startmeeting15:05
meetingologyMeeting started Thu Mar 20 15:05:52 2014 UTC.  The chair is cjwatson. Information about MeetBot at http://wiki.ubuntu.com/meetingology.15:05
meetingologyAvailable commands: action commands idea info link nick15:05
cjwatson[TOPIC] Lightning round15:05
=== meetingology changed the topic of #ubuntu-meeting to: Lightning round
xnoxcjwatson: hey!15:06
cariboucjwatson: I would like to go first if you don't mind15:06
cariboucjwatson: I will need to leave the meeting in ~20min15:06
cjwatson$ echo caribou $(shuf -e barry doko stgraber jodh bdmurray slangasek cjwatson xnox infinity)15:06
cjwatsoncaribou bdmurray xnox barry infinity slangasek stgraber doko cjwatson jodh15:06
cjwatsonMooDoo: just a quick team standup, may not be very exciting I'm afraid :)15:07
cariboucjwatson: shall I proceed ?15:08
cjwatsonyes, please do15:08
caribouweekly highlights15:08
cjwatsonthe above was the ordering15:08
caribou* Tested backport of kdump-tools to Precise15:08
caribou* Picked up some Work Items for updates to the Server Guide15:08
caribou  - /etc/network/interfaces15:08
caribou  - uvtool15:08
caribou* Worked on various charms issues15:08
caribouDone15:08
bdmurrayworking with dames regarding moving the error tracker to prodstack15:08
bdmurrayworked on an apport branch to install specific package versions when retracing15:08
bdmurrayupdated integration-tests for the error tracker for testing prodstack15:08
bdmurraytest of phased-updater with prodstack version of errors15:09
bdmurrayattempted to get the error-tracker working with python-django 1.515:09
bdmurrayinvestigation into missing detailed stacktrace for a ubiquity crash (LP: #1267112)15:09
ubottuLaunchpad bug 1267112 in Daisy "errors indicates a retraced crash but isn't showing a stack trace" [High,Fix committed] https://launchpad.net/bugs/126711215:09
bdmurraypushed daisy code to log a traceback if setting up the retrace env fails15:09
bdmurraysubmitted RT to have daisy updated15:09
bdmurraymanually retraced the crash provided by jibel for bug 126711215:09
bdmurraysorted out why the ubiquity crashes are disappearing (bug 1267112)15:09
bdmurraytested submit.py changes in canonistack (looks good)15:09
bdmurraysubmitted merge proposal regarding python crash detection for daisy15:09
bdmurrayresolved an issue with the phased updater not stopping phased-updates due to a traceback15:09
bdmurrayuploaded a fix for ubuntu-release-upgrader bug 107102515:09
ubottubug 1071025 in ubuntu-release-upgrader (Ubuntu) "do-release-upgrade allows both -d and -p switches although neither takes effect" [Medium,Fix released] https://launchpad.net/bugs/107102515:09
bdmurrayreported and fixed ubuntu-release-upgrader bug 1289580 to improve crash report consolidation15:09
ubottubug 1289580 in ubuntu-release-upgrader (Ubuntu Saucy) "dist upgrade crash tracebacks include a tmpdir name" [High,Fix released] https://launchpad.net/bugs/128958015:09
bdmurrayoverrode blocked phasing of ubuntu-release-upgrader (new crashes are seen because of how duplicates are consolidated)15:09
bdmurrayreported ubuntu-release-upgrader bug 128960415:09
bdmurrayuploaded Saucy SRU for ubuntu-release-upgrader bugs 1289580 and bug 128960415:09
ubottubug 1289604 in ubuntu-release-upgrader (Ubuntu Saucy) "ubuntu-release-upgrader doesn't depend on python-apport" [High,Fix released] https://launchpad.net/bugs/128960415:09
bdmurrayuploaded ubuntu-release-upgrader change to include DistUpgradeVersion from the release-upgrader tarball in the Package line of apport crashes15:09
bdmurrayuploaded update-manager Precise SRU for bug 128958015:09
bdmurrayreported and fixed apt-clone bug 129058415:09
ubottubug 1290584 in apt-clone (Ubuntu) "apt-clone restore should have a use my mirror option" [Undecided,In progress] https://launchpad.net/bugs/129058415:09
bdmurrayuploaded fix for update-notifier bug 122700015:09
ubottubug 1227000 in The Ubuntu Power Consumption Project "update-notifier is polling every 5 seconds" [Undecided,New] https://launchpad.net/bugs/122700015:09
bdmurrayuploaded update-manager fix for bug 129082515:09
ubottubug 1290825 in update-manager (Ubuntu) "Upgrade using do-release-upgrade takes a long time to start because 'iptables -L' runs with DNS lookups enabled" [Medium,In progress] https://launchpad.net/bugs/129082515:10
bdmurrayinvestigation into update-manager test failures15:10
bdmurrayI could use some help with that last thing regarding update-manager test failures15:10
bdmurrayAnd the error tracker should be moving to prodstack today!15:10
cjwatsonfinally15:10
cjwatson:-)15:10
bdmurray⌁ done ⌁15:11
xnox\o/15:11
xnox* vUDS:15:11
xnox  - participated in the discussions, following up from that15:11
xnox* python2 / ap transition:15:11
xnox  - pending release of phablet-tools from silo15:11
xnox  - pending release of gallery-app click15:11
xnox  - pending release of calendar-app click15:11
xnox* x86-emulator:15:11
xnox  - uploaded bionic i686 toolchain15:11
xnox  - working on packaging changes in src:android to build x86 emulator images15:11
xnox* release:15:11
xnox  - worked on reviewing download pages / messaging on those for 14.04 release date15:11
xnox* qt5.2 transition:15:11
xnox  - helped unwinding / unblocking the transition and building arch-restricted packages15:11
xnox* probably other things I missed.15:12
xnoxTODO:15:12
xnox  * boost1.54 bugfix update15:12
xnox  * mdadm transition finalisation15:12
xnox..15:12
xnoxI am away next week, snowboarding.15:12
barryphone: gallery_app pkg_resources branch.  camera_app py3autopilot branch.  ci-train for landing system-image 2.2.  extensive testing.  had meeting on qa for system updates and worked on the system-image test plan.15:12
barrydebuntu: worked a bit on LP: #1220013 and  LP: #1272359.  LP: #1269898.  sponsored nose 1.3.1-1.  Python 3.4 and ensurepip.  LP: #1295153.15:12
barrydone15:12
ubottuLaunchpad bug 1220013 in python-apt (Ubuntu) "python-apt can SIGSEGV when encountering Packages stanzas with no Description field (was: update-apt-xapian-index crashed with SIGSEGV in File())" [High,Confirmed] https://launchpad.net/bugs/122001315:12
ubottuLaunchpad bug 1272359 in aptdaemon (Ubuntu Trusty) "Test suite fails in all versions of Python" [Undecided,New] https://launchpad.net/bugs/127235915:12
ubottuLaunchpad bug 1269898 in oneconf (Ubuntu Trusty) "The use of __file__ causes the tests to fail in Python 3.4" [High,Fix released] https://launchpad.net/bugs/126989815:12
ubottuLaunchpad bug 1295153 in python3.3 (Ubuntu) "[FFe] Remove Python 3.3 from Trusty" [Undecided,New] https://launchpad.net/bugs/129515315:12
cjwatsoninfinity and slangasek not here15:13
cjwatsonstgraber:15:13
stgraberLXC: New CI infrastructure, code reviews, ...15:13
stgraberlogind: Finished writing cgmanager integration patches, now blocked on the cgmanager MIR15:13
stgrabernetwork: Working on a bunch of fixes for ifupdown/ifenslave. Fixed a small bug in isc-dhcp.15:13
stgrabersystem-image: Renamed all channels to ubuntu-touch/<channel>15:13
stgraberother: reviewd OFED packages, vUDS, travel plans for Malta, couple of CI-Train landings15:13
stgraber(DONE)15:13
doko- came back from vacation without computer, wading through email ...15:14
doko- intend to work on ftbfs, toolchain updates, python3.4, python3.3 removal, and on the fallout of the two test rebuilds15:14
doko(done)15:14
cjwatsonpython3.3 removal sounds promising15:15
cjwatsonLast week: vUDS; landed libclick, followed by another landing to add interfaces for getting manifests and frameworks; worked on porting various bits of the phone stack to libclick for performance (1.4 seconds shaved off app startup, waiting to land).15:15
cjwatsonArchitecture porting assistance for the Qt 5.2 landing and fallout.  Bits of this continue.15:15
cjwatsonLanded new ubuntu-sdk-14.04-*-dev1 click frameworks.15:15
cjwatsonLanded a slew of "click chroot" improvements, so both 13.10 and 14.04 chroots should work now.15:15
cjwatsonWorking on getting ubuntu-sdk-libs-dev:armhf installable on other architectures.  Currently blocked on https://code.launchpad.net/~cjwatson/dee/multiarch/+merge/211463 and https://code.launchpad.net/~cjwatson/libaccounts-glib/multiarch/+merge/211468.15:15
cjwatsonHelping jodh out with upstart async-spawn work.15:15
cjwatson..15:15
jodh* vUDS.15:15
jodh* foundations-1305-upstart-work-items: Working with cjwatson on async15:15
jodh  issues.15:16
jodh* other: Initial reviewed of plymouth MP for xnox (still need to re-review).15:16
jodh15:16
cjwatson[TOPIC] AOB15:16
=== meetingology changed the topic of #ubuntu-meeting to: AOB
cjwatsonanything else people have for today?15:16
bdmurrayI'd appreciate it if someone else could have a look at t the update-manager test failures15:17
cjwatsonok, just current trunk?15:17
cjwatsonbeen a while since I looked at u-m15:17
bdmurrayyeah, its been failing since february it seems15:17
barrybdmurray: is there a bug?15:17
bdmurraybarry: I don't think so15:18
barrybdmurray: okay15:18
cjwatsonbdmurray: erm, remind me how to run the tests?15:18
bdmurrayxvfb-run nosetests3 --tests tests/test_update_list.py15:19
* barry grabs the branch15:19
cjwatsonoh, well if barry's keen ... :-)15:19
bdmurraynothing has changed in update-manager itself15:19
barrywell, i'll take a look :)15:20
cjwatsonmight be worth trying with saucy's python-apt, that seems like a plausible candidate15:20
barrybdmurray: FAILED (errors=1, failures=5)15:20
barryis that what you see?15:20
bdmurrayI did try it with python-apt 0.9.1ubuntu1 and it still failed15:21
bdmurraybarry: yes15:21
barrycool.  i'll poke at it more after lunch15:22
bdmurrayxnox: you said you'd updated app-install-data?15:22
bdmurraybarry: thanks!15:22
xnoxbdmurray: yes, I did.15:22
xnoxbdmurray: i didn't update "command-not-found" and I'm not sure how that is generated.15:22
xnoxshould I contact mvo about that?15:22
xnoxbdmurray: well the data used by command-not-found.15:22
bdmurrayxnox: I think so, but I'll check my notes too.15:23
xnoxbdmurray: well, it's before my time. And there was nothing substantial on the wiki.ubuntu.com (apart from original implementation blueprints / plannning)15:23
barryxnox: yes, i think you should contact mvo.  iirc, it's rather tricky to update that data15:24
cjwatsonxnox: mvo is back soon, so maybe it can wait a couple of weeks :)15:24
bdmurrayhttp://bignay.canonical.com/~mvo/command-not-found/15:24
bdmurraythat has recent data15:24
dokocjwatson, start of April?15:25
cjwatsonthink so15:25
xnoxbdmurray: oh, excellent! if that is still cron-running, i think i should be able to figure out how to update the package with data off there.15:26
xnoxbdmurray: the generating new data is what I was after ;-)15:26
bdmurrayxnox: pre-build.sh seems to call update-from-web.sh which gets data from there15:26
cjwatsonok, anything else?15:29
xnoxbdmurray: right, i think i need to reconcile lp:command-not-found, lp:~ubuntu-core-dev/command-not-found/ubuntu, lp:ubuntu/command-not-found, do pre-build.sh, generate new upload and upload. And then it should be all good. I'll work on doing that.15:29
bdmurrayxnox: thanks15:30
cjwatsonright, I think we're done, further command-not-found discussion -> #ubuntu-devel :)15:31
cjwatson#endmeeting15:31
=== 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 Mar 20 15:31:45 2014 UTC.15:31
meetingologyMinutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2014/ubuntu-meeting.2014-03-20-15.05.moin.txt15:31
cjwatsonthanks all15:31
barrythanks!15:31
jodhthanks!15:32
stgraberthanks!15:36
mhall119o/16:03
josemhall119: looks like DST corrections played on you :P16:55
mhall119jose: yes :(16:56
YokoZarHey, at least you got to lose an hour's sleep17:01
dholbachhey17:02
josehey YokoZar! long time no see!17:03
YokoZarHey there :)17:04
dholbachall rightie... who's here from CC and LoCo Council? :)17:04
josecoolbhavi will be joining us in 2mins, PabloRubianes and I are already here17:04
PabloRubianesLoCo Council o/17:04
dholbachwelcome welcome everyone! :)17:04
PabloRubianesthanks17:04
dholbach#startmeeting17:05
meetingologyMeeting started Thu Mar 20 17:05:08 2014 UTC.  The chair is dholbach. Information about MeetBot at http://wiki.ubuntu.com/meetingology.17:05
meetingologyAvailable commands: action commands idea info link nick17:05
dholbach#chairs YokoZar mhall11917:05
dholbachhum17:05
dholbach#chair YokoZar mhall11917:05
meetingologyCurrent chairs: YokoZar dholbach mhall11917:05
elfyhi17:05
dholbachaha!17:05
dholbach#chair elfy17:05
meetingologyCurrent chairs: YokoZar dholbach elfy mhall11917:05
josea wild elfy appeared!17:05
pleia2o/17:05
dholbach#topic Checking in with the Loco Council17:05
=== meetingology changed the topic of #ubuntu-meeting to: Checking in with the Loco Council
dholbach#chair pleia217:05
meetingologyCurrent chairs: YokoZar dholbach elfy mhall119 pleia217:05
dholbachPabloRubianes, jose: thanks a lot for joining us today17:06
dholbachHow are you doing? How is the LoCo Council doing right now?17:06
josehello hello :)17:06
PabloRubianeshello17:06
czajkowskialoha17:07
joseI think PabloRubianes should go, he's been there before I joined :)17:07
PabloRubianeswell here I go17:07
dholbachhey coolbhavi17:07
PabloRubianesI think that with the addition of the new members we had a new energy in the team17:07
coolbhavihey dholbach17:07
pleia2that's great17:08
elfyalways good to hear about new energy17:08
PabloRubianesmainly in the this period we had a LoCo Check in17:08
PabloRubianeswe contact all the LoCos listed in the loco portal17:09
PabloRubianesthis is something we want to do every 6 months cicle17:09
PabloRubianesis not part of the verified process just a "hello how are you? can we help in something?"17:10
YokoZarIt's a good idea ;)17:10
YokoZarAn inspired one, even17:10
elfyyep17:10
elfyis it doable though17:10
coolbhaviyes and the response was also quite good except few teams who failed to respond17:10
elfyit is then :)17:10
coolbhavieven after say a week17:10
PabloRubianeswe got in the past some feedback of not been as present as LoCos expected so this can help with this17:11
josehttp://lococouncil.ubuntu.com/2014/02/16/interim-report-on-2014-census-effort/ has an interim report published a month ago17:11
dholbachgreat... I could imagine that if you run something like this the first time, you get a few who don't respond17:11
czajkowskicoolbhavi: who did you contact was it the person listed on LP or LTP or how did you directly contact the team ?17:11
dholbachdid you mail the contacts of the loco or their mailing lists?17:11
dholbach:)17:11
dholbach#chair czajkowski17:11
meetingologyCurrent chairs: YokoZar czajkowski dholbach elfy mhall119 pleia217:11
josethe contacts directly, mostly we wanted to see if the contact was still active and how the team was doing17:11
PabloRubianesczajkowski: team contact17:11
coolbhaviczajkowski, we contacted the team contacts17:12
czajkowskidholbach: great minds :)17:12
joseI think that our main goal is to demonstrate teams and team contacts (who often have some questions) that there's people there to give a hand when needed, and we tried to achieve that with the check-ins17:12
dholbachthat's great17:12
* coolbhavi remembers the d-a-t reachout feedback cycle here 17:12
elfyseems a lot of loco's didn't respond then17:13
josethat was the main issue, yes17:13
dholbachI could imagine that in some cases you hit LoCos whose contacts got too busy, or where it might make sense to explain the distinction between "a contact" (somebody who can be contacted) and a "team leader" :)17:13
PabloRubianesdholbach: busy or not the contact anymore17:14
coolbhaviyes again few who responded said our loco team is not so active17:14
PabloRubianessometimes LoCo info gets outdated17:14
dholbachdid you have follow-up conversations with some of the teams? like the ones who said "yeah, we actually do need help"17:14
czajkowskijose: can I suggest mailing the teams directly as I know some contacts may not be the contact any more nad there could be others who running things17:14
joseczajkowski: that's actually a good idea, which is what actually happens in ubuntu-de, maybe we can try that with the teams that didn't respond17:15
czajkowskijose: +117:15
coolbhavidholbach, yes basically and the questions that we got were mostly on loco resources17:15
PabloRubianesand on LoCo activity17:16
PabloRubianesthe need of new members or members who want to organize is common17:16
joseabout that contact/team leader thing, we're trying to define it as usually the contact doesn't have contact with the team leader, and it's more useful to have team leaders as contact17:16
joses17:16
dholbachjose, I think that it'd be super helpful to get that message across17:17
josewould a blog post stating that sound good to you?17:17
dholbachyeah, that might be a good start :)17:18
elfyit would sound good to me too :)17:18
joseadded to our trello board :)17:18
pleia2so I'm not so sure about that17:18
PabloRubianesanother stuff we were working in17:19
josepleia2: about what?17:19
pleia2I like the contact is a delegated thing, if a leader doesn't want to do it they can tell someone else to be contact17:19
pleia2requiring leaders to take on specific responsibilities seems a bit odd17:19
pleia2making it more clear that contacts and leaders must communicate is good, but requiring leaders to handle that administrative thing... no so much17:19
elfypleia2: possibly so - but if the contact isn't contactable then I'd say that at the least a leader should be17:19
YokoZarDoes the loco council feel that the situation with Loco logistic support (CDs, etc) is better than in the past?17:20
coolbhavihow about getting the mails on the mailing list if available so that if members see it they would be able to respond?17:20
pleia2I'm happy to be a leader and contact, by my two co-leaders seem quite happy not to have to deal with that responsiblity17:20
elfypleia2: of the 156 teams contacted, the council only received responses from 53 teams would suggest that something needs to be looked at17:20
pleia2elfy: oh of course, I just don't like top down mandates of roles ;)17:20
mhall119ha, and now I'm late17:20
elfy:)17:20
pleia2contacts and leaders must work together, but I don't think they need to be the same people17:21
josepleia2: I think that what you're mentioning may work for some teams, but for others it doesn't, contacts are the ones that usually drop more quicker17:21
czajkowskiI think that you're right to try something new17:21
pleia2jose: that's kind of my point :) teams organize how they organize, mandating that a leader must be a contact also won't work for everyone, so why not just say that contacts and leaders must work together?17:22
dholbachpleia2, hum... that's at least how I understood the conversation earlier - that a team leader doesn't need to be the contact, but that we need somebody who's contactable17:22
joseYokoZar: I think we're good with it, communication with Canonical in those terms is good since I joined, and Michelle/Cezzaine have been super responsive to all our enquiries17:22
czajkowskiand see if something needs to be tweeked/changed slightly in order to get more feedback from the teams17:22
dholbach(or maybe I misunderstood the last parts of the conversation now)17:22
pleia2my concern really is just that we don't want to enforce structure on teams17:23
dholbachok17:23
elfypleia2: I would agree with that - it should be up to the loco and council - but to have a loco uncontactable doesn't work for anyone17:23
dholbach"have a contactable contact" sounds like a reasonable request to me ;-)17:23
pleia2I'd be annoyed if my team were required to all of a sudden make our trio of leaders contacts too17:23
pleia2dholbach: yeah17:24
mhall119when you say you want leaders to be contactable, what does that mean? that they subscribe to loco-contacts? That you (the LC) can sent them email directly?17:24
pleia2mhall119: they emailed all contacts directly, many didn't reply17:24
joseI'd say that when us (LC) email them directly they respond17:24
* pleia2 nods17:24
mhall119it seems to me that it's a judgement call, whether a particular message should go to just team contacts, or contacts *and* leaders17:25
mhall119for example, if it's to announce global jam, that's appropriate for just contacts, if it's for a team health check, that should be both contacts and leaders17:25
josein this case, which was about health, we tried to contact leaders without getting an answer from many of them17:26
joseglobal jam-like things are usually announced via the loco-contacts ML, so it goes to the contacts17:26
mhall119in that case, it sound like a separate issue from who is listed as a contact17:26
pleia2I never did like the name of the loco-contacts mailing list ;)17:26
pleia2should just be locoteams, everyone should subscribe17:27
pleia2(indeed, I tell people to subscribe all the time)17:27
* mhall119 isn't opposed to that, but sounds like it should be it's own topic17:27
pleia2yeah17:27
joseI think we need to further discuss how can we make team leaders contactable in case we need it, and still don't enforce structure on the teams17:28
* pleia2 nods17:28
mhall119yeah, leaders should always be responsive to direct emails from the LC17:28
mhall119IMO, that is one of the responsibilities of being a leader17:29
pleia2contact is the person who is the liason for 3rd party things (supplies from canonical, books from publishers)17:29
joseone thing that I saw was that when the LC directly contacted a team leader in a certain team, he didn't respond, but when he got an email from another team member saying to contact us he did respond17:29
pleia2and can reply to inqueries17:29
pleia2requiring that person to be a leader is... a different skillset :)17:30
josepleia2: +117:30
elfyI don't understand why there is an issue with a 'leader' being contactable17:30
joseelfy: it's just that some of them aren't, for unknown reasons17:31
pleia2elfy: there is a difference between "contact" and "contactable"17:31
elfyyea - I get that :)17:31
elfypleia2: agreed17:31
pleia2leaders should respond, certainly17:31
pleia2but "contact" is a specific role17:31
elfymmm17:31
joseso we're going to further discuss that and we'll report the results to the CC17:32
elfythanks jose17:32
pleia2thanks jose17:32
dholbachgreat - thanks a lot17:32
dholbachwhat has been keeping the LoCo Council busy in the last cycle?17:32
jose:)17:32
josewe've basically had some discussions about how things are moving17:33
josewe discuss everything on a Trello board and have a voting system there17:33
pleia2cool17:33
joseany LC member can propose an item to be discussed, and once it has 4 votes it's moved for discussion17:33
josewe've also set bug status definitions on the ubuntu-locoteams project (see https://wiki.ubuntu.com/LoCoCouncil/BugStatus)17:33
coolbhavidholbach, reverification rebranding and reachout  3R's basically and internal discussions.17:34
joseabout verification, we're using both the traditional meeting method, where the team leader attends the LC meeting set to be done on this channel and we check things, and our new bug/email method17:35
josea bug is created on the ubuntu-locoteams project for each (re-)verification to be done on the cycle, and with those bug statuses we've set we track the progress of the (re-)verification17:35
dholbachand that's working well?17:36
joseworks better than I expected, most leaders prefer to do it via email17:36
joseso how it works is, once they post the link to their verification application, we check it, and once the first vote is casted all LC members have 7 days to vote17:37
dholbachnice :)17:37
josein case not all votes have been casted within the first 7 days, then it only needs only +4 votes, which would make it positive even if the other 2 missing people voted -117:37
dholbachit's interesting to see which forms of organisation work well for which teams :)17:38
elfy:)17:38
joseI think it's basically because timezones suck :)17:38
elfyha ha ha17:38
dholbachthat makes a lot of sense :)17:38
* elfy likes the "votes have been casted within the first 7 day ..." thing and ponders 17:39
joseoh, and we're trying to encourage as many teams as possible to be verified so they can get their DVD pack from Canonical17:39
coolbhavidholbach, we call it a vote shot clock and as jose said  differing timezones are sometimes tough to handle17:39
dholbachyeah, I remember a few other boards having similar issues - mailing list threads going on forever, people forgetting to vote, etc17:40
josethe verification system allows this to be more efficient than approval as teams find it easier - we only check that the leader/contact have signed the CoC, that all resources are set up and follow the naming standards, and they're alive and have good health17:40
dholbachso this is interesting to see :)17:40
cprofittyes, this is good to see17:41
josehey, cprofitt!17:41
cprofitthello jose17:41
dholbachDid you get many direct enquiries from LoCos themselves? I think I recall this taking up the majority of time of the LC in the past.17:41
mhall119jose: are the verification requirements listed somewhere?17:41
josedholbach: not that much, what consumes most of our time is discussion as well as verifications and guiding people for a successful verification17:42
PabloRubianesAnother topic that we are working is the subteam thing17:42
josemhall119: we have https://wiki.ubuntu.com/LoCoCouncil/TeamVerificationGuidelines17:42
PabloRubianesczajkowski: might remember this17:42
mhall119thanks jose17:42
josesure17:42
joseoh, yep, the subteams issue17:43
PabloRubianeswe are trying to see which is the best solution for this17:43
PabloRubianesas some teams want to divide but we dont have resources for all17:43
PabloRubianesand some of the divisions could kill teams17:43
PabloRubianesand we have the fact that USA for example is divided17:44
cprofittthe issue of sub-teams is a complex one...17:44
PabloRubianescprofitt: yes it is17:44
PabloRubianesbut we want to have a conclusion to this topic soon to move forward this17:45
cprofittit becomes difficult to monitor teams as the number grows... but I do understand the desire to organize on a smaller geographic region17:45
PabloRubianescprofitt: I always believe the brazilian model is the best17:45
PabloRubianesone main team and subteams within the team17:46
PabloRubianesnot separate locos17:46
joseand it's only considered as one team, with a board, though17:46
cprofittPabloRubianes: just keep in mind there is no solution that everyone will be satisfied with ... you have to do what you feel is withing the capabilities of the community to handle and is healthy for the loco teams17:46
josecprofitt: +117:46
PabloRubianescprofitt: yes17:47
cprofittWhat I have always been concerned with is the splintering of teams due to personalities and not other factors17:47
PabloRubianescprofitt: we also care about the resources as DVDs and conf packs too17:47
josethat is something that should never happen, conflicts are to be resolved17:47
dholbachjose, the podcast you're doing on Saturday(?) - how many of them did you do before?17:48
josedholbach: 0, it's the first edition ever17:48
PabloRubianesdholbach: is a hangout17:48
dholbachah... yes, a hangout - right :)17:48
cprofittPabloRubianes: I think the resource issue can be dealt with regardless of how many teams / sub teams there are... but the question would be how much time would be necessary to manage it...17:48
dholbachnice :-)17:48
dholbachI'm looking forward to it17:48
josethat takes us to the next point, in our efforts to engage with the community we'll be having a monthly ubuntuonair show, the LoCo Teams update (http://lococouncil.ubuntu.com/2014/02/28/loco-teams-update-on-air/)17:49
cprofittNice, what do you plan on covering in these?17:49
josethe show is to be community-focused, so it's a show made by LoCo Teams for LoCo Teams, anyone can submit news17:49
josebasically what teams have been doing17:49
cprofittnice17:50
dholbachjose, I added a few small things to your notes :)17:50
josewe want to recognize the efforts of the loco community, and also use it to announce a couple things or give some advice in terms of event organizing17:50
josedholbach: cool, I'll check them in a while17:50
dholbachI think it's great - especially if you showcase great work which has been happening elsewhere17:51
josewe expect it to happen more frequently if needed (if teams send so many events we can't cover all of them doing a monthly 1h session)17:51
pleia2yeah, I'm really looking forward to the results from this :)17:52
josewe thought on a Saturday as most LoCo people are off-work that day17:52
elfythat all sounds like good stuff17:52
PabloRubianesyes having events in not working days is something we find important17:52
cprofittI think there are a lot of positive angles to it and look forward to seeing it in action17:53
dholbachIs there anything the CC could help with?17:53
josewell, if you guys can give us some input about the subteams thing that would be useful17:54
PabloRubianesyeap17:54
cprofittinput on sub-teams...17:55
dholbachI could imagine that that could result in a loooooooooooooooong discussion. :-)17:55
pleia2again17:55
cprofittI think you should look at both sides of that issue and determine the road blocks17:55
elfyagain for you pleia2 :p17:55
dholbachshall we take that offline or discuss in a hangout on air maybe?17:55
cprofittonce you have that list you could submit it to the CC for input17:55
pleia2elfy: there have been many threads about pros and cons on loco-contacts17:55
elfyI don't doubt it :)17:55
dholbachI'm done with questions... pleia2, cprofitt, elfy, czajkowski, mhall119, YokoZar: anything else from you?17:56
pleia2I'm good17:56
mhall119nothing from me17:56
cprofittnothing ele from me17:56
coolbhaviI recall the pains when czajkowski sergio chris n myself went through brainstorming on this when we started17:56
pleia2thanks everyone :)17:56
* mhall119 needs to get his team re-verified17:56
YokoZarI'm good, thank you guys :)17:56
elfynothing from me thanks17:56
josewell, if you have anything to say the team is completely open to suggestions, we want to make the loco experience better than ever :)17:56
dholbachgreat, thanks so much for your hard work on the LC17:57
coolbhaviyes thanks to all the CC members too :)17:57
dholbachhugs! :)17:57
mhall119thanks everyone17:57
dholbachand thanks for making time17:57
* jose hugs dholbach17:58
dholbach#topic Any other business...17:58
=== meetingology changed the topic of #ubuntu-meeting to: Any other business...
PabloRubianesno problem thanks for having us17:58
dholbach:-)17:58
dholbachDoes anyone have anything else to discuss?17:58
dholbachLooks like all's good.17:58
dholbachThanks everyone!17:58
dholbach#endmeeting17:58
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology
meetingologyMeeting ended Thu Mar 20 17:59:02 2014 UTC.17:59
meetingologyMinutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2014/ubuntu-meeting.2014-03-20-17.05.moin.txt17:59
elfythanks all17:59
joseenjoy the rest of your day, everyone :)17:59
coolbhavigood night all btw striking midnight here :)18:00
=== vladk|offline is now known as vladk
=== marrusl is now known as marrusl_afk
=== marrusl_afk is now known as marrusl
=== vladk is now known as vladk|offline

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