=== 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 [15:02] I'm ready for a meeting [15:03] me too [15:03] slangasek,barry,doko,jodh,stgraber,xnox: around? [15:03] * barry waves [15:03] no infinity here [15:03] I'm just here, but I'll watch any way :D [15:03] o/ [15:04] did we move it? [15:04] doko: I think google calendar did [15:04] doko: it's the weeks of confusion due to eu/us daylight savings desync [15:04] * stgraber waves [15:04] ahh, ok [15:05] cjwatson: should i file a bug to remove dst from trusty? [15:05] barry: I'd like it removed from the planet, personally [15:05] +1 [15:05] #startmeeting [15:05] Meeting started Thu Mar 20 15:05:52 2014 UTC. The chair is cjwatson. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [15:05] Available commands: action commands idea info link nick [15:05] [TOPIC] Lightning round === meetingology changed the topic of #ubuntu-meeting to: Lightning round [15:06] cjwatson: hey! [15:06] cjwatson: I would like to go first if you don't mind [15:06] cjwatson: I will need to leave the meeting in ~20min [15:06] $ echo caribou $(shuf -e barry doko stgraber jodh bdmurray slangasek cjwatson xnox infinity) [15:06] caribou bdmurray xnox barry infinity slangasek stgraber doko cjwatson jodh [15:07] MooDoo: just a quick team standup, may not be very exciting I'm afraid :) [15:08] cjwatson: shall I proceed ? [15:08] yes, please do [15:08] weekly highlights [15:08] the above was the ordering [15:08] * Tested backport of kdump-tools to Precise [15:08] * Picked up some Work Items for updates to the Server Guide [15:08] - /etc/network/interfaces [15:08] - uvtool [15:08] * Worked on various charms issues [15:08] Done [15:08] working with dames regarding moving the error tracker to prodstack [15:08] worked on an apport branch to install specific package versions when retracing [15:08] updated integration-tests for the error tracker for testing prodstack [15:09] test of phased-updater with prodstack version of errors [15:09] attempted to get the error-tracker working with python-django 1.5 [15:09] investigation into missing detailed stacktrace for a ubiquity crash (LP: #1267112) [15:09] Launchpad bug 1267112 in Daisy "errors indicates a retraced crash but isn't showing a stack trace" [High,Fix committed] https://launchpad.net/bugs/1267112 [15:09] pushed daisy code to log a traceback if setting up the retrace env fails [15:09] submitted RT to have daisy updated [15:09] manually retraced the crash provided by jibel for bug 1267112 [15:09] sorted out why the ubiquity crashes are disappearing (bug 1267112) [15:09] tested submit.py changes in canonistack (looks good) [15:09] submitted merge proposal regarding python crash detection for daisy [15:09] resolved an issue with the phased updater not stopping phased-updates due to a traceback [15:09] uploaded a fix for ubuntu-release-upgrader bug 1071025 [15:09] bug 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/1071025 [15:09] reported and fixed ubuntu-release-upgrader bug 1289580 to improve crash report consolidation [15:09] bug 1289580 in ubuntu-release-upgrader (Ubuntu Saucy) "dist upgrade crash tracebacks include a tmpdir name" [High,Fix released] https://launchpad.net/bugs/1289580 [15:09] overrode blocked phasing of ubuntu-release-upgrader (new crashes are seen because of how duplicates are consolidated) [15:09] reported ubuntu-release-upgrader bug 1289604 [15:09] uploaded Saucy SRU for ubuntu-release-upgrader bugs 1289580 and bug 1289604 [15:09] bug 1289604 in ubuntu-release-upgrader (Ubuntu Saucy) "ubuntu-release-upgrader doesn't depend on python-apport" [High,Fix released] https://launchpad.net/bugs/1289604 [15:09] uploaded ubuntu-release-upgrader change to include DistUpgradeVersion from the release-upgrader tarball in the Package line of apport crashes [15:09] uploaded update-manager Precise SRU for bug 1289580 [15:09] reported and fixed apt-clone bug 1290584 [15:09] bug 1290584 in apt-clone (Ubuntu) "apt-clone restore should have a use my mirror option" [Undecided,In progress] https://launchpad.net/bugs/1290584 [15:09] uploaded fix for update-notifier bug 1227000 [15:09] bug 1227000 in The Ubuntu Power Consumption Project "update-notifier is polling every 5 seconds" [Undecided,New] https://launchpad.net/bugs/1227000 [15:09] uploaded update-manager fix for bug 1290825 [15:10] bug 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/1290825 [15:10] investigation into update-manager test failures [15:10] I could use some help with that last thing regarding update-manager test failures [15:10] And the error tracker should be moving to prodstack today! [15:10] finally [15:10] :-) [15:11] ⌁ done ⌁ [15:11] \o/ [15:11] * vUDS: [15:11] - participated in the discussions, following up from that [15:11] * python2 / ap transition: [15:11] - pending release of phablet-tools from silo [15:11] - pending release of gallery-app click [15:11] - pending release of calendar-app click [15:11] * x86-emulator: [15:11] - uploaded bionic i686 toolchain [15:11] - working on packaging changes in src:android to build x86 emulator images [15:11] * release: [15:11] - worked on reviewing download pages / messaging on those for 14.04 release date [15:11] * qt5.2 transition: [15:11] - helped unwinding / unblocking the transition and building arch-restricted packages [15:12] * probably other things I missed. [15:12] TODO: [15:12] * boost1.54 bugfix update [15:12] * mdadm transition finalisation [15:12] .. [15:12] I am away next week, snowboarding. [15:12] phone: 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] debuntu: 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] done [15:12] Launchpad 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/1220013 [15:12] Launchpad bug 1272359 in aptdaemon (Ubuntu Trusty) "Test suite fails in all versions of Python" [Undecided,New] https://launchpad.net/bugs/1272359 [15:12] Launchpad 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/1269898 [15:12] Launchpad bug 1295153 in python3.3 (Ubuntu) "[FFe] Remove Python 3.3 from Trusty" [Undecided,New] https://launchpad.net/bugs/1295153 [15:13] infinity and slangasek not here [15:13] stgraber: [15:13] LXC: New CI infrastructure, code reviews, ... [15:13] logind: Finished writing cgmanager integration patches, now blocked on the cgmanager MIR [15:13] network: Working on a bunch of fixes for ifupdown/ifenslave. Fixed a small bug in isc-dhcp. [15:13] system-image: Renamed all channels to ubuntu-touch/ [15:13] other: reviewd OFED packages, vUDS, travel plans for Malta, couple of CI-Train landings [15:13] (DONE) [15:14] - came back from vacation without computer, wading through email ... [15:14] - intend to work on ftbfs, toolchain updates, python3.4, python3.3 removal, and on the fallout of the two test rebuilds [15:14] (done) [15:15] python3.3 removal sounds promising [15:15] Last 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] Architecture porting assistance for the Qt 5.2 landing and fallout. Bits of this continue. [15:15] Landed new ubuntu-sdk-14.04-*-dev1 click frameworks. [15:15] Landed a slew of "click chroot" improvements, so both 13.10 and 14.04 chroots should work now. [15:15] Working 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] Helping jodh out with upstart async-spawn work. [15:15] .. [15:15] * vUDS. [15:15] * foundations-1305-upstart-work-items: Working with cjwatson on async [15:16] issues. [15:16] * other: Initial reviewed of plymouth MP for xnox (still need to re-review). [15:16] ⤤ [15:16] [TOPIC] AOB === meetingology changed the topic of #ubuntu-meeting to: AOB [15:16] anything else people have for today? [15:17] I'd appreciate it if someone else could have a look at t the update-manager test failures [15:17] ok, just current trunk? [15:17] been a while since I looked at u-m [15:17] yeah, its been failing since february it seems [15:17] bdmurray: is there a bug? [15:18] barry: I don't think so [15:18] bdmurray: okay [15:18] bdmurray: erm, remind me how to run the tests? [15:19] xvfb-run nosetests3 --tests tests/test_update_list.py [15:19] * barry grabs the branch [15:19] oh, well if barry's keen ... :-) [15:19] nothing has changed in update-manager itself [15:20] well, i'll take a look :) [15:20] might be worth trying with saucy's python-apt, that seems like a plausible candidate [15:20] bdmurray: FAILED (errors=1, failures=5) [15:20] is that what you see? [15:21] I did try it with python-apt 0.9.1ubuntu1 and it still failed [15:21] barry: yes [15:22] cool. i'll poke at it more after lunch [15:22] xnox: you said you'd updated app-install-data? [15:22] barry: thanks! [15:22] bdmurray: yes, I did. [15:22] bdmurray: i didn't update "command-not-found" and I'm not sure how that is generated. [15:22] should I contact mvo about that? [15:22] bdmurray: well the data used by command-not-found. [15:23] xnox: I think so, but I'll check my notes too. [15:23] bdmurray: well, it's before my time. And there was nothing substantial on the wiki.ubuntu.com (apart from original implementation blueprints / plannning) [15:24] xnox: yes, i think you should contact mvo. iirc, it's rather tricky to update that data [15:24] xnox: mvo is back soon, so maybe it can wait a couple of weeks :) [15:24] http://bignay.canonical.com/~mvo/command-not-found/ [15:24] that has recent data [15:25] cjwatson, start of April? [15:25] think so [15:26] bdmurray: 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] bdmurray: the generating new data is what I was after ;-) [15:26] xnox: pre-build.sh seems to call update-from-web.sh which gets data from there [15:29] ok, anything else? [15:29] bdmurray: 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:30] xnox: thanks [15:31] right, I think we're done, further command-not-found discussion -> #ubuntu-devel :) [15:31] #endmeeting === 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 [15:31] Meeting ended Thu Mar 20 15:31:45 2014 UTC. [15:31] Minutes: http://ubottu.com/meetingology/logs/ubuntu-meeting/2014/ubuntu-meeting.2014-03-20-15.05.moin.txt [15:31] thanks all [15:31] thanks! [15:32] thanks! [15:36] thanks! [16:03] o/ [16:55] mhall119: looks like DST corrections played on you :P [16:56] jose: yes :( [17:01] Hey, at least you got to lose an hour's sleep [17:02] hey [17:03] hey YokoZar! long time no see! [17:04] Hey there :) [17:04] all rightie... who's here from CC and LoCo Council? :) [17:04] coolbhavi will be joining us in 2mins, PabloRubianes and I are already here [17:04] LoCo Council o/ [17:04] welcome welcome everyone! :) [17:04] thanks [17:05] #startmeeting [17:05] Meeting started Thu Mar 20 17:05:08 2014 UTC. The chair is dholbach. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [17:05] Available commands: action commands idea info link nick [17:05] #chairs YokoZar mhall119 [17:05] hum [17:05] #chair YokoZar mhall119 [17:05] Current chairs: YokoZar dholbach mhall119 [17:05] hi [17:05] aha! [17:05] #chair elfy [17:05] Current chairs: YokoZar dholbach elfy mhall119 [17:05] a wild elfy appeared! [17:05] o/ [17:05] #topic Checking in with the Loco Council === meetingology changed the topic of #ubuntu-meeting to: Checking in with the Loco Council [17:05] #chair pleia2 [17:05] Current chairs: YokoZar dholbach elfy mhall119 pleia2 [17:06] PabloRubianes, jose: thanks a lot for joining us today [17:06] How are you doing? How is the LoCo Council doing right now? [17:06] hello hello :) [17:06] hello [17:07] aloha [17:07] I think PabloRubianes should go, he's been there before I joined :) [17:07] well here I go [17:07] hey coolbhavi [17:07] I think that with the addition of the new members we had a new energy in the team [17:07] hey dholbach [17:08] that's great [17:08] always good to hear about new energy [17:08] mainly in the this period we had a LoCo Check in [17:09] we contact all the LoCos listed in the loco portal [17:09] this is something we want to do every 6 months cicle [17:10] is not part of the verified process just a "hello how are you? can we help in something?" [17:10] It's a good idea ;) [17:10] An inspired one, even [17:10] yep [17:10] is it doable though [17:10] yes and the response was also quite good except few teams who failed to respond [17:10] it is then :) [17:10] even after say a week [17:11] we got in the past some feedback of not been as present as LoCos expected so this can help with this [17:11] http://lococouncil.ubuntu.com/2014/02/16/interim-report-on-2014-census-effort/ has an interim report published a month ago [17:11] great... I could imagine that if you run something like this the first time, you get a few who don't respond [17:11] coolbhavi: who did you contact was it the person listed on LP or LTP or how did you directly contact the team ? [17:11] did you mail the contacts of the loco or their mailing lists? [17:11] :) [17:11] #chair czajkowski [17:11] Current chairs: YokoZar czajkowski dholbach elfy mhall119 pleia2 [17:11] the contacts directly, mostly we wanted to see if the contact was still active and how the team was doing [17:11] czajkowski: team contact [17:12] czajkowski, we contacted the team contacts [17:12] dholbach: great minds :) [17:12] I 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-ins [17:12] that's great [17:12] * coolbhavi remembers the d-a-t reachout feedback cycle here [17:13] seems a lot of loco's didn't respond then [17:13] that was the main issue, yes [17:13] I 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:14] dholbach: busy or not the contact anymore [17:14] yes again few who responded said our loco team is not so active [17:14] sometimes LoCo info gets outdated [17:14] did you have follow-up conversations with some of the teams? like the ones who said "yeah, we actually do need help" [17:14] jose: 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 things [17:15] czajkowski: 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 respond [17:15] jose: +1 [17:15] dholbach, yes basically and the questions that we got were mostly on loco resources [17:16] and on LoCo activity [17:16] the need of new members or members who want to organize is common [17:16] about 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 contact [17:16] s [17:17] jose, I think that it'd be super helpful to get that message across [17:17] would a blog post stating that sound good to you? [17:18] yeah, that might be a good start :) [17:18] it would sound good to me too :) [17:18] added to our trello board :) [17:18] so I'm not so sure about that [17:19] another stuff we were working in [17:19] pleia2: about what? [17:19] I like the contact is a delegated thing, if a leader doesn't want to do it they can tell someone else to be contact [17:19] requiring leaders to take on specific responsibilities seems a bit odd [17:19] making it more clear that contacts and leaders must communicate is good, but requiring leaders to handle that administrative thing... no so much [17:19] pleia2: possibly so - but if the contact isn't contactable then I'd say that at the least a leader should be [17:20] Does the loco council feel that the situation with Loco logistic support (CDs, etc) is better than in the past? [17:20] how about getting the mails on the mailing list if available so that if members see it they would be able to respond? [17:20] I'm happy to be a leader and contact, by my two co-leaders seem quite happy not to have to deal with that responsiblity [17:20] pleia2: of the 156 teams contacted, the council only received responses from 53 teams would suggest that something needs to be looked at [17:20] elfy: oh of course, I just don't like top down mandates of roles ;) [17:20] ha, and now I'm late [17:20] :) [17:21] contacts and leaders must work together, but I don't think they need to be the same people [17:21] pleia2: 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 quicker [17:21] I think that you're right to try something new [17:22] jose: 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] pleia2, 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 contactable [17:22] YokoZar: 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 enquiries [17:22] and see if something needs to be tweeked/changed slightly in order to get more feedback from the teams [17:22] (or maybe I misunderstood the last parts of the conversation now) [17:23] my concern really is just that we don't want to enforce structure on teams [17:23] ok [17:23] pleia2: I would agree with that - it should be up to the loco and council - but to have a loco uncontactable doesn't work for anyone [17:23] "have a contactable contact" sounds like a reasonable request to me ;-) [17:23] I'd be annoyed if my team were required to all of a sudden make our trio of leaders contacts too [17:24] dholbach: yeah [17:24] when 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] mhall119: they emailed all contacts directly, many didn't reply [17:24] I'd say that when us (LC) email them directly they respond [17:24] * pleia2 nods [17:25] it seems to me that it's a judgement call, whether a particular message should go to just team contacts, or contacts *and* leaders [17:25] for 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 leaders [17:26] in this case, which was about health, we tried to contact leaders without getting an answer from many of them [17:26] global jam-like things are usually announced via the loco-contacts ML, so it goes to the contacts [17:26] in that case, it sound like a separate issue from who is listed as a contact [17:26] I never did like the name of the loco-contacts mailing list ;) [17:27] should just be locoteams, everyone should subscribe [17:27] (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 topic [17:27] yeah [17:28] I 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 teams [17:28] * pleia2 nods [17:28] yeah, leaders should always be responsive to direct emails from the LC [17:29] IMO, that is one of the responsibilities of being a leader [17:29] contact is the person who is the liason for 3rd party things (supplies from canonical, books from publishers) [17:29] one 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 respond [17:29] and can reply to inqueries [17:30] requiring that person to be a leader is... a different skillset :) [17:30] pleia2: +1 [17:30] I don't understand why there is an issue with a 'leader' being contactable [17:31] elfy: it's just that some of them aren't, for unknown reasons [17:31] elfy: there is a difference between "contact" and "contactable" [17:31] yea - I get that :) [17:31] pleia2: agreed [17:31] leaders should respond, certainly [17:31] but "contact" is a specific role [17:31] mmm [17:32] so we're going to further discuss that and we'll report the results to the CC [17:32] thanks jose [17:32] thanks jose [17:32] great - thanks a lot [17:32] what has been keeping the LoCo Council busy in the last cycle? [17:32] :) [17:33] we've basically had some discussions about how things are moving [17:33] we discuss everything on a Trello board and have a voting system there [17:33] cool [17:33] any LC member can propose an item to be discussed, and once it has 4 votes it's moved for discussion [17:33] we've also set bug status definitions on the ubuntu-locoteams project (see https://wiki.ubuntu.com/LoCoCouncil/BugStatus) [17:34] dholbach, reverification rebranding and reachout 3R's basically and internal discussions. [17:35] about 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 method [17:35] a 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-)verification [17:36] and that's working well? [17:36] works better than I expected, most leaders prefer to do it via email [17:37] so 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 vote [17:37] nice :) [17:37] in 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 -1 [17:38] it's interesting to see which forms of organisation work well for which teams :) [17:38] :) [17:38] I think it's basically because timezones suck :) [17:38] ha ha ha [17:38] that makes a lot of sense :) [17:39] * elfy likes the "votes have been casted within the first 7 day ..." thing and ponders [17:39] oh, and we're trying to encourage as many teams as possible to be verified so they can get their DVD pack from Canonical [17:39] dholbach, we call it a vote shot clock and as jose said differing timezones are sometimes tough to handle [17:40] yeah, I remember a few other boards having similar issues - mailing list threads going on forever, people forgetting to vote, etc [17:40] the 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 health [17:40] so this is interesting to see :) [17:41] yes, this is good to see [17:41] hey, cprofitt! [17:41] hello jose [17:41] Did 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] jose: are the verification requirements listed somewhere? [17:42] dholbach: not that much, what consumes most of our time is discussion as well as verifications and guiding people for a successful verification [17:42] Another topic that we are working is the subteam thing [17:42] mhall119: we have https://wiki.ubuntu.com/LoCoCouncil/TeamVerificationGuidelines [17:42] czajkowski: might remember this [17:42] thanks jose [17:42] sure [17:43] oh, yep, the subteams issue [17:43] we are trying to see which is the best solution for this [17:43] as some teams want to divide but we dont have resources for all [17:43] and some of the divisions could kill teams [17:44] and we have the fact that USA for example is divided [17:44] the issue of sub-teams is a complex one... [17:44] cprofitt: yes it is [17:45] but we want to have a conclusion to this topic soon to move forward this [17:45] it becomes difficult to monitor teams as the number grows... but I do understand the desire to organize on a smaller geographic region [17:45] cprofitt: I always believe the brazilian model is the best [17:46] one main team and subteams within the team [17:46] not separate locos [17:46] and it's only considered as one team, with a board, though [17:46] PabloRubianes: 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 teams [17:46] cprofitt: +1 [17:47] cprofitt: yes [17:47] What I have always been concerned with is the splintering of teams due to personalities and not other factors [17:47] cprofitt: we also care about the resources as DVDs and conf packs too [17:47] that is something that should never happen, conflicts are to be resolved [17:48] jose, the podcast you're doing on Saturday(?) - how many of them did you do before? [17:48] dholbach: 0, it's the first edition ever [17:48] dholbach: is a hangout [17:48] ah... yes, a hangout - right :) [17:48] PabloRubianes: 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] nice :-) [17:48] I'm looking forward to it [17:49] that 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] Nice, what do you plan on covering in these? [17:49] the show is to be community-focused, so it's a show made by LoCo Teams for LoCo Teams, anyone can submit news [17:49] basically what teams have been doing [17:50] nice [17:50] jose, I added a few small things to your notes :) [17:50] we 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 organizing [17:50] dholbach: cool, I'll check them in a while [17:51] I think it's great - especially if you showcase great work which has been happening elsewhere [17:51] we 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:52] yeah, I'm really looking forward to the results from this :) [17:52] we thought on a Saturday as most LoCo people are off-work that day [17:52] that all sounds like good stuff [17:52] yes having events in not working days is something we find important [17:53] I think there are a lot of positive angles to it and look forward to seeing it in action [17:53] Is there anything the CC could help with? [17:54] well, if you guys can give us some input about the subteams thing that would be useful [17:54] yeap [17:55] input on sub-teams... [17:55] I could imagine that that could result in a loooooooooooooooong discussion. :-) [17:55] again [17:55] I think you should look at both sides of that issue and determine the road blocks [17:55] again for you pleia2 :p [17:55] shall we take that offline or discuss in a hangout on air maybe? [17:55]