/srv/irclogs.ubuntu.com/2013/01/15/#ubuntu-meeting.txt

=== Seeker`_ is now known as Seeker
=== WaVeR` is now known as WaVeR
=== yofel_ is now known as yofel
=== Tonio_ is now known as Tonio_aw
=== trijntje_ is now known as trijntje
=== doko_ is now known as doko
=== Sweetsha1k is now known as Sweetshark
=== rsalveti_ is now known as rsalveti
=== Ursinha_ is now known as Ursinha
=== zequence_ is now known as zequence
Davieyo/16:00
SergioMenesesDaviey, \o16:00
arosalesHello16:01
Davieyanyone else?16:01
arosaleslooks like rbasak joined the party :-)16:01
DavieyUrsinha, shall we?16:02
UrsinhaDaviey, sure16:02
* Ursinha looks desperately for the links16:02
arosalesUrsinha: one sec16:03
arosalesI think jimbaker is on the list to drive16:03
* arosales giving him a ping16:03
Davieyarosales: He is slacking off16:04
Ursinhaokay, I found the links :)16:04
Ursinha#startmeeting ubuntu-server-team16:04
meetingologyMeeting started Tue Jan 15 16:04:42 2013 UTC.  The chair is Ursinha. Information about MeetBot at http://wiki.ubuntu.com/meetingology.16:04
meetingologyAvailable commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired16:04
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | ubuntu-server-team Meeting | Current topic:
arosalesUrsinha: ya, sorry are you available to chair16:04
arosalesthank you :-)16:04
Ursinha#topic Review ACTION points from previous meeting16:05
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | ubuntu-server-team Meeting | Current topic: Review ACTION points from previous meeting
Ursinhaarosales, is the wiki page updated?16:05
arosalesI don't think m_3 updated from the last meeting minutes . . .16:05
arosales:-(16:05
* Ursinha looks for the minutes16:05
arosaleshttps://wiki.ubuntu.com/ServerTeam/Meeting16:05
arosalesDaviey: is deprecating http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-r-tracking-bug-tasks.html#server in progress?16:06
Davieyno16:06
arosalessorry, I got that wrong16:07
arosaleswe are moving to http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-r-tracking-bug-tasks.html#server16:07
Davieynothat is done16:07
arosalesis deprecate http://reqorts.qa.ubuntu.com/reports/ubuntu-server/release-bugs.html done?16:07
Davieyyes16:07
arosalesthanks16:07
arosalesIRC commands were updated16:07
* arosales is still looking into status tracker is not picking up servercloud area16:08
Ursinhaarosales, okay, I thought that page was outdated, was looking for the logs16:08
arosales#action arosales to investigate why status tracker is not picking up all servercloud area BPs16:08
meetingologyACTION: arosales to investigate why status tracker is not picking up all servercloud area BPs16:08
arosalesUrsinha: it is a little behind, sorry about that16:08
arosalesI was just going to run through those real quick as I had some context16:08
Ursinhasure, go ahead :)16:08
arosalesjamespage, smoser: BP approval look good?16:08
smoseri think we should call that shipped. if you have a BP that is not approved at this point, please raise that with myself, Daviey or james_w16:09
smoseror even jamespage16:09
smoser(sorry james_w)16:09
arosalesthanks smoser16:09
arosalesUrsinha: all yours. I think that covers the action items from last week.16:09
Ursinhaall right, moving on16:09
Ursinha#topic Raring Development16:09
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | ubuntu-server-team Meeting | Current topic: Raring Development
Ursinhahttp://reports.qa.ubuntu.com/reports/ubuntu-server/release-bugs.html16:10
Ursinhahttp://reports.qa.ubuntu.com/reports/rls-mgr/rls-r-tracking-bug-tasks.html#server16:10
Ursinhahttp://status.ubuntu.com/ubuntu-quantal/group/topic-raring-servercloud-overview.html16:10
Ursinhaall links, I guess16:10
Daviey^ 40416:10
Ursinhahm, must fix wiki link16:11
Ursinhahttp://status.ubuntu.com/ubuntu-raring/group/topic-raring-servercloud-overview.html16:12
arosalesah needs raring16:12
Ursinhaah, obvious :)16:12
Ursinhathis last link is okay, go ahead :)16:12
* arosales looking at essentials that are in the red16:13
arosaleszul: you feel ok with https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-openstack-grizzly16:13
Davieyhttps://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-seeded-qa-workflow needs to be re-scoped, most likely16:14
zularosales: yep16:14
Davieyarosales: zul isn't here right now.. That blueprint looks in a worse state than it is.  The progress is actually good16:14
Davieyoh, zul is here16:14
arosaleszul: ok, thanks16:14
zulDaviey: barely16:14
* zul is on medication16:15
arosalesI think jamespage is driving https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-seeded-qa-workflow correct?16:15
Daviey#ACTION zul, go and rest16:15
meetingologyACTION: zul, go and rest16:15
arosales:-) lol16:15
Davieyarosales: he was.. i think we need to re-asses16:15
arosaleshttps://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-juju-charm-testing is behiind16:16
Davieyhttps://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-mysql <-- roaksoax, i believe you are taking a hunk of that.. can you update the BP please16:16
arosalesI'll follow up with jim baker16:16
Davieysmoser: https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-openstack-ubuntu-images might want a little love, can you take a gander at that at somepoint?16:17
* roaksoax looks16:17
smoseryes, Daviey16:17
DavieyThanks16:17
roaksoaxDaviey: nope not taking any WI of mysql BP16:18
roaksoaxthe ha stuff is in the HA BP16:18
DavieyInfact, i have a feeling that many (myself included) are behind on keeping the NBP status updated.. We should all take a check before next meeting16:18
Daviey#ACTION All, check status of assigned Work Items and refresh if necessary16:18
meetingologyACTION: All, check status of assigned Work Items and refresh if necessary16:18
arosales+116:18
Davieyroaksoax: Hmm, you made a mysql drbd charm?16:19
roaksoaxDaviey: i modified the charm to support DRBD16:19
Davieyso, shal we mark that BP dead.. and track in your HA BP?16:19
roaksoaxDaviey: yeah i'm tracking HA for MySQL in the HA BP16:19
Daviey(I assume clint won't work on that now?)16:20
Davieyok, lets kill it for now16:20
Davieythanks16:20
Daviey..16:20
DavieyI think we are good to move on?16:20
UrsinhaDaviey, are you reviewing bugs as well?16:20
DavieyUrsinha: I think you will do a better job than me ;)16:21
UrsinhaDaviey, hehe, I'd have to take a better look, I'll poke you later if I find something for you :)16:23
Davieywilco!16:23
UrsinhaDaviey, but I'd take a look at the critical bugs (we have three) and see if anything can be done there16:24
Davieyi'm afraid i need to pop out for 15 mins, another engagement..16:25
UrsinhaI'll move on16:25
Ursinha#topic Ubuntu Server Team Events16:25
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | ubuntu-server-team Meeting | Current topic: Ubuntu Server Team Events
Ursinhaany events coming soon?16:25
DavieyFOSDEM 2nd/3rd Feb, Brussels - Belgium16:25
arosalesScale 11x is end of Feb16:25
Davieyattending: Myself, jamespage & rbasak16:25
Ursinharight16:26
arosalesUrsinha: that seems to be it atm16:26
Ursinhaokay16:27
Ursinha#topic Weekly Updates & Questions for the QA Team (hggdh)16:27
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | ubuntu-server-team Meeting | Current topic: Weekly Updates & Questions for the QA Team (hggdh)
Ursinhahggdh, olá :)16:27
hggdhUrsinha: alo16:27
hggdhanything for us from the server team?16:27
UrsinhaDaviey, arosales, ^16:28
arosaleshggdh: nothing from me16:28
hggdhfrom the daily testing, raring-server-ec2 is yellow all over with some red dots :-)16:29
hggdhso it looks like flu with petechiae16:29
arosaleshggdh: :-)16:29
Ursinhahehe16:29
hggdhapart from that, life is good16:30
hggdh..16:30
UrsinhaI'll move on then16:30
Ursinhathanks hggdh16:30
Ursinha#topic Weekly Updates & Questions for the Kernel Team (smb)16:30
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | ubuntu-server-team Meeting | Current topic: Weekly Updates & Questions for the Kernel Team (smb)
Ursinhasmb isn't here, it seems16:31
Ursinhado we have anything for him?16:31
UrsinhaI'll take that as a no16:31
Ursinha#topic Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak)16: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 | ubuntu-server-team Meeting | Current topic: Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak)
rbasakNothing new to report. Any questions for me?16:31
Ursinhaguess not :) thanks rbasak16:33
Ursinha#topic Open Discussion16:33
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | ubuntu-server-team Meeting | Current topic: Open Discussion
Ursinhaanything else you feel like discussing?16:33
Ursinhaokay16:33
Ursinha#topic Announce next meeting date and time16:33
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | ubuntu-server-team Meeting | Current topic: Announce next meeting date and time
Ursinhanext meeting will be on Tuesday, Jan 22th at 16:00 UTC in #ubuntu-meeting16:34
arosalesUrsinha: thanks for chairing16:34
arosales:-)16:34
Ursinhaand according to the wiki page, rbasak is the next chair16:34
Ursinhacheers everyone!16:34
Ursinha#endmeeting16:34
=== 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 Tue Jan 15 16:34:39 2013 UTC.16:34
meetingologyMinutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-01-15-16.04.moin.txt16:34
meetingologyMinutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-01-15-16.04.html16:34
roaksoaxy/win close16:34
m_3arosales: my bad... I was just cutting/pasting from the meeting guide... closed it at the end of the meeting16:41
Davieythanks Ursinha16:42
arosalesm_3: fyi https://wiki.ubuntu.com/ServerTeam/KnowledgeBase#Team_policy gives instructions on actions post meeting16:42
UrsinhaDaviey, it was my pleasure :)16:43
arosalesI think we all in server need a refresher on those steps, I am guilty too16:43
m_3ack16:43
jsalisbury#startmeeting17:01
jsalisbury##17:01
jsalisbury## This is the Ubuntu Kernel Team weekly status meeting.17:01
jsalisbury##17:01
jsalisbury[LINK] https://wiki.ubuntu.com/KernelTeam/Meeting17:01
meetingologyMeeting started Tue Jan 15 17:01:15 2013 UTC.  The chair is jsalisbury. Information about MeetBot at http://wiki.ubuntu.com/meetingology.17:01
meetingologyAvailable commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired17:01
jsalisbury[LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/raring17:01
jsalisbury# Meeting Etiquette17:01
jsalisbury#17:01
jsalisbury# NOTE: '..' indicates that you are finished with your input.17:01
jsalisbury#       'o/' indicates you have something to add (please wait until you are recognized)17:01
jsalisburyRoll Call for Ubuntu Kernel Weekly Status Meeting17:01
argeso/17:01
ppisatio/17:01
ckingo/17:01
hertono/17:01
henrixo/17:01
rtgo/17:01
sconklino/17:01
jsalisbury[TOPIC] ARM Status (ppisati)17:01
=== meetingology changed the topic of #ubuntu-meeting to: ARM Status (ppisati)
ppisatiR/master: still working on multiplatform support: omap3/4 boots, i'm working on adding imx6 support now17:02
ppisati..17:02
jsalisbury[TOPIC] Release Metrics and Incoming Bugs (jsalisbury)17:02
=== meetingology changed the topic of #ubuntu-meeting to: Release Metrics and Incoming Bugs (jsalisbury)
jsalisburyRelease metrics and incoming bug data can be reviewed at the following link:17:02
jsalisbury[LINK] http://people.canonical.com/~kernel/reports/kt-meeting.txt17:02
jsalisbury..17:02
jsalisburyI'll post the updates for ogasawara17:02
jsalisbury[TOPIC] Milestone Targeted Work Items (ogasawara)17:02
=== meetingology changed the topic of #ubuntu-meeting to: Milestone Targeted Work Items (ogasawara)
jsalisbury[LINK] https://launchpad.net/~canonical-kernel-distro-team/+upcomingwork17:02
jsalisbury|| apw         || hardware-r-kernel-config-review       || 9 work items ||17:02
jsalisbury||             || hardware-r-delta-review               || 4 work items ||17:02
jsalisbury||             || hardware-r-arm-kernel-maintenance     || 2 work items ||17:02
jsalisbury||             || hardware-r-kernel-misc                || 4 work items ||17:02
jsalisbury||             || foundations-r-x32-planning            || 2 work items ||17:02
jsalisbury||             || desktop-r-clean-old-kernels           || 1 work item  ||17:02
jsalisbury|| ogasawara   || hardware-r-kernel-config-review       || 2 work items ||17:02
jsalisbury|| ppisati     || hardware-r-kernel-config-review       || 1 work item  ||17:02
jsalisbury||             || hardware-r-kernel-version-and-flavors || 2 work items ||17:03
jsalisbury||             || hardware-r-delta-review               || 1 work item  ||17:03
jsalisbury|| sconklin    || hardware-r-arm-power-measurement      || 3 work items ||17:03
jsalisbury|| rtg         || hardware-r-delta-review               || 1 work item  ||17:03
jsalisbury..17:03
jsalisbury[TOPIC] Status: Raring Development Kernel (ogasawara)17:03
=== meetingology changed the topic of #ubuntu-meeting to: Status: Raring Development Kernel (ogasawara)
jsalisburyWe have rebased the Raring kernel to the latest v3.8-rc3 upstream17:03
jsalisburykernel and uploaded last week.  Please test and let us know your17:03
jsalisburyresults.17:03
jsalisburyI also want to note that the 12.04.2 point release date has been moved17:03
jsalisburyout by 2 weeks to Thurs Feb 14:17:03
jsalisburyhttps://lists.ubuntu.com/archives/ubuntu-devel-announce/2013-January/001003.html17:03
jsalisburyImportant upcoming dates:17:03
jsalisbury * Raring:17:03
jsalisbury  * Fri Jan 18 - 13.04 Month 3 Milestone (3 days)17:03
jsalisbury  * Mon Feb 18 - 13.04 Month 4 Milestone (~5 weeks)17:03
jsalisbury * Precise:17:03
jsalisbury  * Thu Feb 14 - 12.04.2 Release (~4 weeks)17:03
jsalisbury..17:03
jsalisbury[TOPIC] Status: CVE's (henrix)17:03
=== meetingology changed the topic of #ubuntu-meeting to: Status: CVE's (henrix)
henrixCurrently we have 34 CVEs on our radar, with 0 CVEs added and 3 CVEs retired this week.17:03
henrixSee the CVE matrix for the current list:17:04
henrix[LINK] http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html17:04
henrixOverall the backlog has decreased slightly this week:17:04
henrix[LINK] http://people.canonical.com/~kernel/status/cve-metrics.txt17:04
henrix[LINK] http://people.canonical.com/~kernel/cve/pkg/CVE-linux.txt17:04
henrix..17:04
jsalisbury[TOPIC] Status: Stable, Security, and Bugfix Kernel Updates - Quantal/Precise/Oneiric/Lucid/Hardy (bjf/herton/henrix)17:04
=== meetingology changed the topic of #ubuntu-meeting to: Status: Stable, Security, and Bugfix Kernel Updates - Quantal/Precise/Oneiric/Lucid/Hardy (bjf/herton/henrix)
henrixHere is the status for the main kernels, until today (January 08):17:04
henrix * Hardy - Nothing in this cycle17:04
henrix * Lucid - In -updates; 1 CVE; (2 commits)17:04
henrix * Oneiric - In -updates; 2 CVEs; 4 upstream stable release(s); (78 commits)17:04
henrix * Precise - In Testing; 3 CVEs; 1 upstream stable release(s); (104 commits)17:04
henrix * Quantal - In Testing; 3 CVEs; 1 upstream stable release(s); (254 commits)17:04
henrixCurrent opened tracking bugs details:17:04
henrix * http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html17:04
henrixFor SRUs, SRU report is a good source of information:17:04
henrix * http://people.canonical.com/~kernel/reports/sru-report.html17:04
henrixFuture stable cadence cycles:17:04
henrix * https://wiki.ubuntu.com/RaringRingtail/ReleaseInterlock17:04
henrix..17:04
bjfThe kernel SRU cadence cycle that was to start this week has been canceled. The kernels in -proposed will be used for the 12.04.2 release.17:04
bjf..17:05
jsalisbury[TOPIC] Open Discussion or Questions? Raise your hand to be recognized (o/)17:05
=== meetingology changed the topic of #ubuntu-meeting to: Open Discussion or Questions? Raise your hand to be recognized (o/)
jsalisburyThanks everyone17:05
jsalisbury#endmeeting17:05
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology
meetingologyMeeting ended Tue Jan 15 17:05:51 2013 UTC.17:05
meetingologyMinutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-01-15-17.01.moin.txt17:05
meetingologyMinutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-01-15-17.01.html17:05
ckingthanks jsalisbury17:05
sconklinthanks17:06
=== hggdh is now known as hggdh_AFK
=== Ursinha is now known as Ursinha-afk
=== Ursinha-afk is now known as Ursinha
czajkowskihuats: itnet7 SergioMeneses ping21:01
huatsczajkowski: Hello dear21:01
czajkowskijust waiting on the others to start21:02
SergioMenesesczajkowski, hey hey21:02
czajkowskianyone seen effie?21:03
SergioMenesesczajkowski, no I dont21:03
czajkowski:/21:03
czajkowskilets start in case itnet7 is being held up at work.21:04
SergioMeneseshe is lost, I guess21:04
czajkowski#startmeeting21:04
meetingologyMeeting started Tue Jan 15 21:04:15 2013 UTC.  The chair is czajkowski. Information about MeetBot at http://wiki.ubuntu.com/meetingology.21:04
meetingologyAvailable commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired21:04
=== czajkowski changed the topic of #ubuntu-meeting to: catch up wth the loco council
czajkowskiso we don't have anything on our agenda21:04
czajkowskibut seeing as we're here lets just catch up21:04
SergioMeneseshttps://wiki.ubuntu.com/LoCoCouncil/Agenda21:04
czajkowskiSergioMeneses: we;re doing that team via bug no ?21:05
SergioMenesesonly the Ubuntu Iranian team, but they want to work on the bug21:05
SergioMenesesyes czajkowski21:05
czajkowskigrand21:05
=== czajkowski changed the topic of #ubuntu-meeting to: Alternative word to - Approved - for loco teams
czajkowskiso I've seen this come up on various blog posts in comments21:06
czajkowskihow people feel unmotivated due to them not being an Approved locoo and how really that word doesnt really help motvate people in getting more involved21:06
czajkowskiwhat I'd like to do is look at if there is an alternative and see if could be used21:07
czajkowskisometimes words in english don't always translate so clearly in other languages21:07
SergioMenesessure, like free21:07
czajkowskiso I just want to see if this is possible and it also may not be. But if we don't discuss it then well we'll never know21:08
czajkowskiso some alternaives that kinda spring to mind are21:08
czajkowskiSponsored loco - downsides would people may assume un approved locos would lose hosting, email etc as they are not sponsored, when they would be21:08
czajkowskiif anyone has any ideas please feel free to jump in21:09
SergioMenesesI was thinking on "official" or "sponsored"21:09
czajkowskiI do like offical as that is a clear word and is less black and white21:09
BobJonkman2Hi, I'm Bob Jonkman from the Canadian Team, which has recently lost its "approved" status.21:09
czajkowskiverified would also be a good one21:09
czajkowskiBobJonkman2: hi there21:09
czajkowskiREviewed would also be good21:10
SergioMenesesand Bhavani said Sponsored or Authorised21:10
czajkowskiso they are reviewed by the council21:10
czajkowskiAuthroised sounds a bit severe imo, but again that's just me21:10
SergioMenesessure21:10
czajkowskiand I'm trying to find a way to sum what up approved is, but also make it sound less harsh21:10
czajkowskihuats: any ideas21:10
SergioMenesesit is a strong word21:11
czajkowskiBobJonkman2: any ideas there?21:11
BobJonkman2loss of approval has caused some agitation amongst team members.  There is some feeling that we're not allowed to gather and have events focused on Ubuntu without approval.  A different word would be welcome21:11
huatshonnestly I have thought about that and approved is the best word for me21:11
czajkowskiBobJonkman2: why do people feel that way, we have many teams who don't have the approved status and all have events21:11
czajkowskihuats: nods21:11
huatsI don't llike sponsored nor authorised (team can exists without being approved)21:12
czajkowskiAgain, just like to point out, nothing is set in stone. it's jsut stuff I've seen and heard from many people and discussion is good.21:12
czajkowskihuats: nods21:12
BobJonkman2It's the word, "Approved".  Without "approval" the sense is that activities are disapproved21:12
czajkowskiwhat I had in my head Loco teams ( unapproved) and reviewed loco teams (approved)21:12
czajkowskitaking away the unapproved and approved words21:13
czajkowskiso all teams are locoteams21:13
czajkowskibut one of which has been reviewed by the council21:13
czajkowskiso seems offical21:13
czajkowskibut also less harsh21:13
czajkowskithoughts?21:13
czajkowskiBobJonkman2: never heard that but interesting to think about21:13
BobJonkman2The only direct benefit the Canadian Team sees to an "Approved" status is that Canonical provides branded Ubuntu disks (which are very welcome, and show proprietary software users that Ubuntu is not just some fly-by-night thing)21:14
czajkowskinods21:14
huatsI might try the word 'official' but nothing besides that21:14
BobJonkman2So perhaps a new word might focus on the benefits a Team receives.  "Sponsored" seems to work for that21:14
SergioMeneseshuats, +121:15
SergioMenesesBobJonkman2, huats czajkowski I think "official" would be better for this21:15
czajkowskiBobJonkman2: how would differenciate between sponsored and unsponsored then21:15
SergioMenesesimho21:15
huatsBobJonkman2: I think there is something on what we can try to work : some teams (I am aware of ubuntu-fr and ubuntu-de) have agreement with Canonical to be able to sell ubuntu branded goodies21:15
huatsI have been asked in the past by Jono to provide him that "agreement" so that he can work out on extending it to the rest of "approved" loco teams21:16
czajkowskiSo my only concern then would be for "unapproved" locos how seeing the word Sponsored and Offical not beside their team21:16
BobJonkman2From the Team members' perspective, the only thing we get out of "Approval" (or Sponsorship) is disks, which we give away gratis to anyone who is interested21:16
czajkowskiand also the word Offical means what ?21:17
czajkowskiany team not approved is not an offical team21:17
czajkowskiI susupect our inboxes would explode in outrage21:17
czajkowskiBobJonkman2: makes a difference in conference packs also21:17
czajkowskiwhich many teams use more so than CDs tbh21:17
huatsthis could be a real benefit to inform team that selling an ubuntu goodies without being approved is a copyright violation (and this is something people in FOSS are really looking carefully)21:17
pleia2there are sometimes also publishers who use approved/non-approved as criteria for giving out books (the official ubuntu book only went to approved teams)21:17
czajkowskialso little known fact. Not many teams request the CD allocation each cycle21:18
pleia2so it's not even just canonical21:18
BobJonkman2czajkowski: True, but most members don't see the conference packs21:18
BobJonkman2and since the decline of Ontario Linuxfest 2 years ago we haven't had need of a conference pack21:18
czajkowskiBobJonkman2: my experience is the other way in fact21:18
czajkowskibut nice to hear another side of things21:18
czajkowskiwell like I say nothing is fixed in stone, this is useful information and we'll follow up with a blog post and posting to the loco contacts list for wider discussion21:19
BobJonkman2czajkowski: That most members don't see the conference pack may be because the Canadian Team covers a large geographic region.21:19
czajkowski#action czajkowski write blog post and post to lococontacts on the subject21:20
meetingologyACTION: czajkowski write blog post and post to lococontacts on the subject21:20
czajkowski#topic Reviewed Large Geographic counteries for locoteam structure.21:20
=== meetingology changed the topic of #ubuntu-meeting to: Reviewed Large Geographic counteries for locoteam structure.
BobJonkman2But smaller geographic regions would reduce active membership to a small handful in each region21:20
czajkowskiSo BobJonkman2 this may be of interest to your team21:20
czajkowskiThis has come up time and time again over the last year or so21:21
BobJonkman2:) That's one of the reasons I'm here21:21
czajkowskiWe have counteries such as India, Australia, Canada and Brazil21:21
czajkowskiall of which are massive georgaphic regions and it's not possible to be loco in that sense21:21
czajkowskiwhat we would propse is to break them up into state/provence like USA has done21:22
czajkowskiand there can be locos that way21:22
czajkowskithe reason we would like to do this now rather than in 1+years is to put in place measures to help teams from the ground up, but also helps plan and better allocate resouces when planning eg. Canonical DVDs21:23
BobJonkman2For the Canadian Team, a good geographic area is maybe 100km across.  Even members in a provincial team would be separated by hundreds of km21:23
czajkowskiwe've had this request in a number of times now from India and we've had to keep putting it off as we don't have the requirements in place.21:23
czajkowskiBobJonkman2: the same goes for many countereies and even states in the USA21:23
czajkowskiwhat would also benefit is that the LTP would be able to have a section in the team page for a CITY contact21:24
czajkowskithis merge has been ready for a long time as it was discussed at least 2 UDSs ago21:24
BobJonkman2+1 for City contacts21:24
czajkowskiBrazil loco have already broken their team up into sub teams a long time ago , this would just help for making it offical21:24
czajkowskibut if we don't set the standard up now, then it all becomes rather messy and has a knock on effect on other things, then such as Approved/offical locos21:25
czajkowskiwhat do folks think?21:25
SergioMenesesbut it doesnt work for all teams, russia said no21:25
BobJonkman2In Canadian Team IRC meetings the consensus is that provincial teams won't make much difference to members; our team groups are city-based21:26
czajkowskiBobJonkman2: right but in a provence you could have a city contact but not a city loco. this has been discussed at length at UDS and it was said no a city loco would not happen.21:26
BobJonkman2If Canada is split into provincial teams most members still would not meet face-to-face, and we'd probably continue to meet in IRC on a Canada-wide basis anyway.21:27
BobJonkman2So, splitting into provincial teams would create bureaucratic and administrative overhead that accomplishes nothing.21:28
czajkowskior it could help the team21:28
czajkowskithe USA has a USA mentor team21:28
czajkowskiwe should try and be more encouraing about new ideas21:28
czajkowskirather than saying it wont work tbh21:29
BobJonkman2We're working on our Canadian Re-approval application now, and it's been difficult to get members working together in anything larger than a City.  Most of the discussion takes place during the Kitchener and Waterloo Ubuntu Hours, face-to-face21:30
czajkowskiBobJonkman2: you may not understand my point, break ing up teams into provence/state may encourage others to step up and if they dn't that's fine, but the standard is put in place21:31
czajkowskiand the option is there for the future21:31
BobJonkman2True, more teams would mean more involvement from people as local contacts21:32
czajkowskiyes exactly21:32
czajkowskias a person living the other side of canada may not be interested in an event in that area21:32
czajkowskibut may be interested in running on in their provence21:33
czajkowskilets try adn support the idea and work out the logistics as we move forward21:33
czajkowskithis idea has hit roadblocks from people for the last 18 months21:33
SergioMenesesanyways this is a sensible topic and we need a lot of ideas and commentaries21:33
czajkowskiyet we keep getting requests on a monthly basis for help in this area21:33
czajkowskiso I suspect we'll A) blog B) mail loco contacts and the teams we have in mind21:34
czajkowskiover the coming week(s)21:34
czajkowskibut it would be nice to get the ball rolling21:34
SergioMenesesczajkowski, I think is the best21:35
czajkowskiso for example there are 10 provences in Canada21:35
BobJonkman2A team leader may run an event in her City, but as each province is about 1000km wide having provincial LoCos doesn't make much difference to having a country LoCo21:35
czajkowskiyou could have 10 locoteams there rather than one large country one21:35
czajkowskisurely this makes more sense21:35
BobJonkman2We have about 300 members, spread out over more than 5000 km; most of them are in Ontario. A Saskatchewan LoCo may have only one or two members...21:37
czajkowskiso my georgaphy of Canada is a bit sketchy apologies, but you'd have ubutu-ca-on for Ontario loco and a city contact on the LTP for Toronto21:37
czajkowskiif I have my provence and city right there21:37
czajkowskiBobJonkman2: true but at least the two there would have the option and feel empowered to have a loco in their back ice skating rink! :)21:38
* czajkowski has a mate there, it's very cold!21:38
czajkowskibut they should have the option there to have their own loco21:38
czajkowskiequally they can mail the mothership the candian team for advice and help and that team could mentor people21:38
BobJonkman2In Vancouver there is a city-based (unapproved) LoCo, that seems to work well for them.21:39
SergioMeneseslike a meta team21:39
BobJonkman2But Toronto, with a population of about 5,000,000 doesn't even have Ubuntu Hours.21:39
czajkowskiBobJonkman2: each team is so different on their events21:39
czajkowskiand like I said city contact was discussed at UDS and it was said No it would not happen, at best the LTP would be edited to allow for a city contact.21:40
SergioMenesesBobJonkman2, but what can we do in that case?21:40
czajkowskianwyasy this was just to give an idea of what the council are working on21:40
BobJonkman2If Canada should be split into provincial LoCos we would like to keep the country-wide mailing list, IRC channel &c. because of the sparse membership.21:40
czajkowskiBobJonkman2: thats not a problem this could be worked out n the future21:41
czajkowskiit's not being decided this second21:41
BobJonkman2czajkowski: I understand.21:41
czajkowski#topic AOB21:41
=== meetingology changed the topic of #ubuntu-meeting to: AOB
czajkowskihuats: SergioMeneses any other comments21:41
czajkowskior AOB21:42
SergioMenesesnot from me21:42
huatsI don't know what means AOB21:42
huats:)21:42
czajkowskiany other business21:42
czajkowski:)21:42
huatsnot else21:43
czajkowskiokie doke21:43
czajkowski#endmeeting21:43
=== 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 Tue Jan 15 21:43:17 2013 UTC.21:43
meetingologyMinutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-01-15-21.04.moin.txt21:43
meetingologyMinutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-01-15-21.04.html21:43
czajkowskiSergioMeneses: huats thanks for coming21:43
czajkowskiBobJonkman2: thanks for taking part21:43
SergioMenesesthank to you czajkowski21:43
BobJonkman2czajkowski: Thanx for having me!21:43
czajkowskiit's an open meeting BobJonkman2 anyone and everyone is welcome21:43
czajkowskiwe dont always have such a free meeting21:44
czajkowskiit's nice :)21:44
BobJonkman2If anything is to be done about LoCos, I'd like to know how to engage more people.  300 people in Ubuntu-ca out in an entire country is pretty abysmal.21:45
czajkowskiBobJonkman2: it's not really21:47
czajkowskigiven peoples lives jobs and other stuff goig on21:47
czajkowski*going on21:47
czajkowski300 is a lot still21:47

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