/srv/irclogs.ubuntu.com/2014/10/21/#ubuntu-meeting.txt

=== jasonjang is now known as jason_tmp
=== wendar_ is now known as wendar
=== ubott2 is now known as ubottu
=== kickinz1 is now known as kickinz1|afk
=== kickinz1|afk is now known as kickinz1
=== freeflying__ is now known as freeflying
=== Trevinho_ is now known as Trevinho
rbasako/16:00
gnuoyo/16:00
argeso/16:00
rbasak#startmeeting ubuntu-server-team16:00
meetingologyMeeting started Tue Oct 21 16:00:36 2014 UTC.  The chair is rbasak. Information about MeetBot at http://wiki.ubuntu.com/meetingology.16:00
meetingologyAvailable commands: action commands idea info link nick16:00
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | ubuntu-server-team Meeting | Current topic:
kickinz1\o16:00
rbasakI see no action points from the last meeting.16:00
rbasak#topic Utopic Development16:00
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | ubuntu-server-team Meeting | Current topic: Utopic Development
rbasakRelease in two days! Are we ready?16:01
caribourbasak: shouldn't it be Vivid now ;-) ?16:01
rbasakVivid isn't open for development yet :-P16:01
rbasak#subtopic Release Bugs16:01
rbasak#link http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-u-tracking-bug-tasks.html#ubuntu-server16:01
rharpero/16:02
jamespage\o16:03
lutostago/16:03
rbasakI think the High and Critical bugs in this list are already being taken care of.16:03
matsubarao/16:03
rbasakIt looks unlikely that the rest are going to be fixed at this stage of the cycle.16:03
rbasak#subtopic Blueprints16:03
rbasak#link http://status.ubuntu.com/ubuntu-u/group/topic-u-server.html16:03
rbasak#link https://blueprints.launchpad.net/ubuntu/+spec/topic-u-server16:03
rbasakCan everyone update their blueprints?16:04
rbasakI see a fair bit left here still.16:04
rbasakPresumably these are already done or won't make it?16:04
rbasak#topic Server & Cloud Bugs (caribou)16: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: Server & Cloud Bugs (caribou)
rbasakcaribou: over to you16:04
caribourbasak: nothing particular; working on automating kdump-tool testing16:05
rbasakOK, thanks!16:05
rbasak#topic Weekly Updates & Questions for the QA Team (psivaa)16: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: Weekly Updates & Questions for the QA Team (psivaa)
rbasakpsivaa_: around?16:05
psivaa_rbasak: not much of an update from us16:06
rbasakOK. Any questions for psivaa_?16:06
rbasak#topic Weekly Updates & Questions for the Kernel Team (smb, sforshee, arges)16:06
=== 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, sforshee, arges)
smbNothing from here.16:06
rbasak#topic Ubuntu Server Team Events16:06
=== 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
coreycbo/16:07
rbasakOpenStack Summit is coming up of course.16:07
rbasakAnything else?16:07
rbasakDiscuss EOLing qemu machine types (and legacy roms) (hallyn, rharper)16:07
rbasakhallyn can't make it, so deferring this until the next meeting.16:07
rbasak#topic Open Discussion16:07
=== 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
rbasakDoes anything have anything they'd like to raise?16:08
rharperrbasak: I'm here if you wanted to discuss the EOLing a bit16:08
rbasakSure.16:08
rbasakIs there a decision we need to make here?16:08
rharperso background, https://wiki.ubuntu.com/QemuPTMigration16:09
rharperthere is a decision w.r.t how long/how far to care the the legacy machine types from previous LTS releases w.r.t do we support live migration from an instance on an old LTS to current release16:09
rharperthere is on-going maint. w.r.t keeping roms around , as well as handling any of the potential issues w.r.t qemu machine imcompatibility  between releases.16:10
rbasakCan I suggest that this goes to an appropriate mailing list?16:10
rharperfrom trusty onward, qemu has a ubuntu_release named machine which will help disambiguate it from the defaults in qemu16:10
rharperrbasak: indeed16:10
rbasakIt sounds like there are some complicated implications here, and we should make sure that stakeholders have an opportunity to comment.16:11
coreycbrharper, and maybe to an openstack mailing list16:11
rharperrbasak: additionally coreycb brought up that this hits openstack upgrades with folks doing a precise -> trusty upgrade16:11
rbasakcoreycb: +116:11
rbasakThanks for summarising the issue.16:12
rharpersure16:12
coreycbrharper, upgrades to trusty that are entirely on precise too16:12
rbasakShall we leave this for now then, and take it to an ML?16:12
rharperI think that's best16:12
rbasakAny other topics for Open Discussion?16:12
coreycbs/trusty/icehoue above16:12
rbasak#topic Announce next meeting date, time and chair16:12
=== 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, time and chair
coreycbicehouse16:12
rbasakThe next meeting will be on Tue Oct 28 16:00:00 UTC 2014.16:13
rbasakhallyn will chair.16:13
rbasakI don't think there's anything on that will clash with that, right?16:13
gnuoyNorwich beer festival16:13
rbasak:-)16:13
caribouhaloween ?16:14
rbasak"Apologies for my absense, I was drinking beer"16:14
rbasak#endmeeting16:14
=== 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 Oct 21 16:14:37 2014 UTC.16:14
meetingologyMinutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2014/ubuntu-meeting.2014-10-21-16.00.moin.txt16:14
gnuoythanks rbasak16:14
kickinz1thanks, rbasak16:14
rharperrbasak: thanks!16:14
caribourbasak: thanks!16:14
matsubaraThanks rbasak16:15
=== jason_tmp is now known as jasonjang
med_rbasak, thanks for scrollback!16:32
YoBoYbonsoir19:49
skellatYoBoY: Bonsoir comrade19:49
YoBoY:)19:49
IdrogNbonsoir19:50
cm-tbonsoir :)19:55
SergioMenesesYoBoY, \o19:55
YoBoYhi SergioMeneses :)19:56
SergioMeneseshi YoBoY ! how you been?19:57
YoBoYtired and busy :) and you ?19:57
costalesHi!19:57
Cytheriahello guys !19:59
SergioMenesesYoBoY, like you! jejeje19:59
cm-theya !19:59
PabloRubianeshi YoBoY19:59
skellatAre we ready to begin the meeting?19:59
PabloRubianesyes19:59
skellat#startmeeting Regular LoCo Council Meeting for October 201419:59
meetingologyMeeting started Tue Oct 21 20:00:07 2014 UTC.  The chair is skellat. Information about MeetBot at http://wiki.ubuntu.com/meetingology.19:59
meetingologyAvailable commands: action commands idea info link nick19:59
=== 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 | Regular LoCo Council Meeting for October 2014 | Current topic:
skellat#topic Opening Business20:00
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Regular LoCo Council Meeting for October 2014 | Current topic: Opening Business
skellat#subtopic Listing of Sitting Members of LoCo Council20:00
skellat#info For the avoidance of uncertainty and doubt, it is necessary to list the members of the council who are presently serving active terms.20:00
skellat#info Marcos Costales, term expiring 2015-04-1620:00
skellat#info José Antonio Rey, term expiring 2015-10-0420:00
skellat#info Pablo Rubianes, term expiring 2015-04-1620:00
skellat#info Sergio Meneses, term expiring 2015-10-0420:00
skellat#info Stephen Michael Kellat, term expiring 2015-10-0420:00
skellat#info There is currently one vacant seat on LoCo Council20:00
skellat#subtopic Roll Call20:00
skellatAt this point we need to proceed with a roll call of LoCo Council members.20:00
skellatA quorum to transact business during today's meeting is 3.20:00
skellatDuring the following vote members of the council should vote "+1" to indicate their presence.20:00
skellat#voters PabloRubianes SergioMeneses skellat jose costales20:00
meetingologyCurrent voters: PabloRubianes SergioMeneses costales jose skellat20:00
skellat#vote LoCo Council Roll Call (All Members Present To Vote In Favor To Register Attendance)20:00
meetingologyPlease vote on: LoCo Council Roll Call (All Members Present To Vote In Favor To Register Attendance)20:00
meetingologyPublic votes can be registered by saying +1, +0 or -1 in channel, (for private voting, private message me with 'vote +1/-1/+0 #channelname)20:00
skellat+120:00
meetingology+1 received from skellat20:00
PabloRubianes+120:01
meetingology+1 received from PabloRubianes20:01
SergioMeneses+120:01
meetingology+1 received from SergioMeneses20:01
costales+120:01
meetingology+1 received from costales20:01
skellatAre there any other members of LoCo Council wishing to indicate their attendance?20:02
skellat#endvote20:02
meetingologyVoting ended on: LoCo Council Roll Call (All Members Present To Vote In Favor To Register Attendance)20:02
meetingologyVotes for:4 Votes against:0 Abstentions:020:02
meetingologyMotion carried20:02
skellat#topic Re-Verification: France20:02
skellatBefore today is a re-verification application from the team in France.  I will call upon the team's representative to speak to their application briefly.  Members of the Council will, of course, have questions to ask as we discuss the matter.20:02
skellatThe application is available for viewing on the wiki infrastructure. -- https://wiki.ubuntu.com/FrenchTeam/ReVerificationApplication20:02
=== 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 | Regular LoCo Council Meeting for October 2014 | Current topic: Re-Verification: France
skellatWho is here to speak for the LoCo of France?20:03
IdrogNyes20:03
cm-tIdrogN: will talk for us20:03
skellatGreetings IdrogN20:03
costalesHi IdrogN! |o/20:03
skellatTell us a bit about what is happening in France20:03
IdrogNpleased to meet you all20:04
skellatThank you20:04
IdrogNFirst, let me introduce myself, i'm David, the new head of Ubuntu-Fr board (we are a "legal" association)20:05
cm-tmister president :)20:05
IdrogNcm-t & yoboy, who are also here, are members of the board too20:05
cm-thi20:06
IdrogNShall we proceed to the lecture?20:06
skellatCertainly20:06
IdrogNYou can find our application there: https://wiki.ubuntu.com/FrenchTeam/ReVerificationApplication201420:07
olivebonsoir20:07
IdrogN(olive is also a member of the board)20:07
cm-t(and maybe since the begining of ubuntu-fr if I am not false)20:08
IdrogNSo, as you know, we organise a lot of events. The most important ones are the release party and the Paris Ubuntu Parties20:08
olivemaybe, maybe20:08
PabloRubianesreally nice application20:09
cm-toups, i forgot to remove the "we need you",  i remove it asap20:09
IdrogNWe are currently organising the next Ubuntu Party which will be hosted at la Cité des Sciences by mid-november and that occupies us a lot20:09
cm-t(done, no more ads "we need you")20:10
PabloRubianesAre you having any problem we can help in?20:10
IdrogNNext week, there will be the release party for the 14.10. During thisrelease party, we will meet to organise the next Ubuntu Party (UP) and train the volunteers20:11
YoBoY(this saturday more exactly)20:12
IdrogN@Pablo: for the next UP ?20:12
meetingologyIdrogN: Error: "Pablo:" is not a valid command.20:12
IdrogNPablo: for the next UP?20:12
PabloRubianesIdrogN: I mean in the team20:12
IdrogNPablo : everything seems to be quite ok20:13
SergioMenesesawesome guys!20:14
skellatWhat are your plans for 2015?20:14
IdrogNAs usual, 2 UP (15.4 & 15.10), several meetings & meet-ups with local teams & other association from the Free Software ecosystem20:15
skellatExcellent20:15
costalesYou're in a lot of social networks :)) Which of them is working better for you?20:15
IdrogNMore webcafés in more festivals20:15
IdrogNtwitter mostly20:16
IdrogNfor 2015, we can add that we will try to develop the association by recruiting more volunteers and using new tools to be more efficient20:17
skellatExcellent.20:17
PabloRubianesIdrogN: great!20:17
skellatFellow Council members, are we ready to vote?20:17
PabloRubianesyes20:17
costalesYes20:17
skellat#vote That the re-verification application of France be approved and that the period of verification be extended for a period of two years from this date.20:17
meetingologyPlease vote on: That the re-verification application of France be approved and that the period of verification be extended for a period of two years from this date.20:17
meetingologyPublic votes can be registered by saying +1, +0 or -1 in channel, (for private voting, private message me with 'vote +1/-1/+0 #channelname)20:17
PabloRubianes+1 great work20:17
meetingology+1 great work received from PabloRubianes20:17
costales+1 This is one of the best applications I've ever seen. Really an awesome work, team! Thanks!!20:18
meetingology+1 This is one of the best applications I've ever seen. Really an awesome work, team! Thanks!! received from costales20:18
SergioMeneses+1 congrats :D20:18
meetingology+1 congrats :D received from SergioMeneses20:18
skellat+1 an excellent example to be followed20:18
meetingology+1 an excellent example to be followed received from skellat20:18
skellat#endvote20:18
meetingologyVoting ended on: That the re-verification application of France be approved and that the period of verification be extended for a period of two years from this date.20:18
meetingologyVotes for:4 Votes against:0 Abstentions:020:18
meetingologyMotion carried20:18
IdrogNthank you20:18
PabloRubianeskeep the great work French Team20:18
YoBoYthanks you everyone for your support :)20:18
skellatCongratulations to the French team.  We'll be updating things on Launchpad after this meeting concludes.20:18
costalesCongrats team!20:18
cm-tthanks dear loco council <3, and thank to our new president to lead our lecture :')20:18
skellat#topic Update on open cases before the LoCo Council20:19
=== 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 | Regular LoCo Council Meeting for October 2014 | Current topic: Update on open cases before the LoCo Council
skellatMay I have permission to put in the record a list of our pending verification and re-verification proceedings?20:19
IdrogNmerci à l'équipe :)20:19
cm-t^^20:19
PabloRubianesskellat: yes20:20
skellat#agreed That information may be placed in the meeting record as to the list of pending LoCo Council proceedings.20:20
skellat#info LoCo Council presently has before it pending verification and re-verification proceedings for the following LoCo Teams: Mauritius, Finland, Netherlands, Peru, Russia, Serbia.20:20
skellat#topic The loco-contacts thread "Our teams reject the new LoCo Council policy"20:20
=== 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 | Regular LoCo Council Meeting for October 2014 | Current topic: The loco-contacts thread "Our teams reject the new LoCo Council policy"
skellatThere are many things relevant to the most recent thread on loco-contacts.20:20
skellatI will bring up that, in parallel to this, Daniel holbach discussed on ubuntu-community-team various thoughts about recognizing and incorporating non-LoCo groups. -- https://lists.ubuntu.com/archives/ubuntu-community-team/2014-October/000044.html20:20
skellatThe original start to this thread is available for reading and the thread did generate some rancor and heated discussion. -- https://lists.ubuntu.com/archives/loco-contacts/2014-October/006791.html20:20
skellatThe new SubLoCo policy is what caused much of the concern in this thread. -- http://lococouncil.ubuntu.com/2014/09/16/new-subloco-policy/20:20
skellatI don't want to discuss this for too long.20:20
skellatIs there anything we can add here today other than taking note of what Mr. Holbach is doing?20:21
PabloRubianesI think that the new policy is clear as it is20:22
SergioMeneseseverything is there!20:22
PabloRubianesand have the proper workarounds20:22
nhainesI recommend that the LoCo Council carefully consider how they represent policies in response to queries on the mailing list.20:22
felipexilFrom my point of view, the "exceptions" are not clear, but I don't want to open the discussion here20:22
skellatOkay20:23
olivethx20:23
nhainesFor instance, it was insinuated that independant status for LoCo teams of autonomous subregions would be somewhat of an uphill battle.20:23
nhainesAnd then later insinuated that it would probably be a rote overview.20:24
costalesGood point nhaines20:24
nhainesAnd skellat, you asked that conversation stop on the mailing list because this meeting was the only proper venue, and now you're saying that you don't want to spend much time on it.20:24
skellatnhaines: Coming up on the agenda will be consideration of requests from the Galician and Asturian teams.20:25
nhainesIt's clear from the actual announced policy that a great deal of thought was put into the general guidelines.20:25
nhainesSo when questions about hypothetical (or not so hypothetical) situations are met with mixed messages, that creates a lack of confidence.20:25
PabloRubianeslet me clear some points here20:25
skellatnhaines: I do want to ensure we reach the Galician and Asturian requests before 2100 UTC20:26
skellatThat is all20:26
rwwIf there wasn't public discussion of this policy before it was established, that probably would have helped decrease confusion. Something to bear in mind for the future.20:27
PabloRubianesI don't see the confusion20:27
skellatAh20:27
skellatPart of that is bringing Debian paradigms into Ubuntu20:27
rwwPabloRubianes: I think that regardless of the correctness of various emails on loco-contacts@, it's blatantly obvious that some people were confused.20:28
PabloRubianesif a team don't want to a subteam they can ask to be an independent loco20:28
nhainesI think the confusion is that the policy (presumably) was designed to address existing LoCos who wanted "official" subteams, and the policy was designed to be an operating guidelines for those teams.20:28
rwwNow, personally I'm fine with the policy, but as a LoCo leader, I'd prefer that future policy not come out of nowhere from a public point of view. Hence, prior discussion.20:28
costalesPabloRubianes, "if a team don't want to a subteam they can ask to be an independent loco". Could we append that to the policy?20:29
PabloRubianesnhaines: the last 2 sentences of the policy are clearly address for teams who don't want to be sublocos20:29
skellat"In the event what is considered a sub-team wants to be considered a LoCo, it will need to present a request to the LoCo Council."20:29
skellatWe have two of those requests coming up later in this meeting to address.20:29
PabloRubianescostales: the policy states "In the event what is considered a sub-team wants to be considered a LoCo, it will need to present a request to the LoCo Council."20:30
PabloRubianesthats the same!20:30
costalesI didn't read in the last days20:30
SergioMenesesI don't know if we are missing something but I don't get the point, I saw everything cover with the new policy20:30
costales;) sorry20:30
nhainesYes, but the fact that alarmed LoCo teams were told "read the policy" instead of being reassured is disappointing.20:30
felipexilPabloRubianes: the policy is not clear for a group of people, so even in the case it is clear for you, it is obvious that there is a problem20:30
xuacuI think that exixting LoCos were quite confused about being demoted fron LoCo to SubLoCo ;)20:31
felipexilas nhaines said, the problem is that the policy was written from a point of view that is not reflected in the policy itsefl20:31
costalesGood point xuacu20:31
PabloRubianesxuacu: the problem is some existent locos where out of the old policy too20:31
felipexilthere is a lack of context, and the "policy" is going to be interpreted without that point of view20:31
PabloRubianeswe made the new policy to contemplate them and have every loco on the same page20:32
nhainesSo once again, my advice is that the Council carefully consider the response to alarmed community members.  "RTFM" is something the Ubuntu project was founded to eliminate.20:32
PabloRubianesnhaines: none made RTFM20:32
nhainesI would be happy to provide links after the meeting.20:32
skellatNo, nhaines, please provide them in the record20:33
PabloRubianesyes20:33
SergioMenesessure20:33
nhainesIs the LoCo Council willing to delay the Galacian and Asturian requests while I cross-reference my email with the web archives?20:33
PabloRubianesnhaines:yes20:34
costaleshttps://lists.ubuntu.com/archives/loco-contacts/2014-October/006802.html20:34
nhainesThen I will do my best to be prompt.20:34
costalesJosé Antonio Rey: "Please, read the whole policy." Unique phrase20:34
costalesfor me it's a RTFM20:34
nhainescostales: agreed.20:34
PabloRubianesthat's not20:34
xuacucostales: +120:34
PabloRubianesthey where reading the first part20:35
PabloRubianesthe end of the policy is where the independent locos are allow20:35
PabloRubianesthe last 2 sentences20:35
felipexilPabloRubianes... How can you know what the other people were reading?20:35
costalesI didn't like too this: The LoCo Council isn't listen their teams/users20:35
nhaines"Please read the whole policy" and "read the fucking manual" are functionally identical.20:36
costalesIf the users/teams like change something, we have to listen them :)20:36
nhainesfelipexil: it's pretty clear he didn't read the entire policy, but that's no excuse not to clarify.20:36
PabloRubianesfelipexil: because as costales just did they where asking for something the policy states20:36
rwwI think "is the policy okay" and "were there issues with the way discussion proceeded before and after the announcement of the policy" are two different topics.20:36
rwwnhaines is quite clearly talking about the latter. Defending the policy is not addressing that.20:37
nhainesYes, the policy seems quite reasonable to me.  A codification of current best practice.20:37
costalesI think we have a lot of teams and it's impossible a rule for all of them :)20:38
skellatAnd that is where internal debate among LoCo Council members filtered outward and one person's opposition to a majority vote brings us to today's discussion20:39
rwwamongst other issues, such as lack of prior communication, handling of the ensuing thread after announcement, etc. etc.20:40
nhainesWhich one person opposed which majority vote and how did that lead to this discussion today?20:40
xuacuskellat: you can't avoid this kind of discussion sooner or later :)20:40
PabloRubianeswait a sec20:41
PabloRubianeslets get another angle of this20:41
PabloRubianesxuacu: for example20:41
PabloRubianeswhat do you think is wrong with the policy?20:41
felipexilAnd... I would like to point out that the sentence "In the event what is considered a sub-team wants to be considered a LoCo, it will need to present a request to the LoCo Council." is not clear at all20:41
felipexil"what is considered a sub-team" should be defined20:42
felipexil(at least, it is not clear for me)20:42
skellatOkay20:42
xuacuPablo: just the point felixepil brings up20:42
nhainesfelipexil: it does seem to indicate that an autonomous region would need to become a subteam to the existing team before asking for consideration.20:42
felipexilnhaines: +120:43
felipexiland, the two first sentences of the policy make this difficult20:43
SergioMenesesok let me see if I get the point, you want to have 2 official subteams in the same city, right? ( by instance )20:43
felipexilEach team will be a country (or state in the United States). We will call this a ‘LoCo’. Each LoCo can have sub-teams. This sub-teams will be created at the will and need of each LoCo.20:43
costalesSergioMeneses, Nobody talked about cities ;)20:44
xuacuand that begs the next question: could a subLoCo be denied to become a LoCO?20:44
SergioMenesescostales, city or state or region20:44
costalesSergioMeneses, It's not the same for us20:44
PabloRubianesxuacu: it depends on the case20:44
xuacuand where are the guidelines to be accepted or rejected?20:45
felipexilAccording to the two first sentences of the policy, only countries can be LoCo, and sub-teams will be created only at "the will and need of that LoCo", and it seems that to be promoted to a "LoCo", it is necessary to be a sub-LoCo. T20:46
PabloRubianesfelipexil: that was the old policy20:46
PabloRubianesjust that20:46
PabloRubianesso ubuntu-cat or ubuntu-ast were outside the policy20:46
nhainesThere was also a question about how a theoretical Basque LoCo would represent the Basque population found in the US.  https://lists.ubuntu.com/archives/loco-contacts/2014-October/006847.html20:47
nhainesI would in turn ask how the Ohio LoCo is representing the interests of the Ohioan population outside of Ohio.20:47
nhainesBut this seems to indicate a predisposition to rejecting autonomous regions looking to become independent LoCos.20:47
costalesGood point too: The Basque LoCo would be in 2 countries20:48
nhainescostales: a cultural identity with a unique language that happens to straddle two countries that came long later.20:48
PabloRubianesnhaines costales with that view all the latin america would be one 1 loco20:49
felipexilPabloRubianes: I copied the text from the new policy...20:49
PabloRubianesfelipexil: the old policy was just "one country one loco"20:49
felipexilPabloRubianes: yes, but the exception is not clear20:50
PabloRubianesnow we added the rest to let provinces or cities have their loco if they don't want to be part of the national loco20:50
felipexilPabloRubianes: it is not clear who is a "what is considered a sub-team"20:50
PabloRubianesfelipexil: any team that is not a country loco20:51
SergioMenesesfelipexil, a group of people20:51
PabloRubianesyes20:51
felipexilPabloRubianes: SergioMeneses: could that not be clarified in the policy?20:51
nhainesI rather like the language "In the event that what is or would be considered a sub-team wants to be considered a LoCo".20:52
felipexilPabloRubianes: SergioMeneses: (remove the "not" in my previous sentence)20:52
costalesPabloRubianes, then, we are treating a team without country as >>> "Sub" << this is bad in itself.20:52
nhainesThe problem is that the new policy immediately states "LoCos not meeting the criteria of country/state teams will be denied verification."20:52
PabloRubianesfelipexil: it could be20:53
PabloRubianesbut there's the fact that the only country that have locos working as independent at the moment is spain20:54
PabloRubianesbut if you feel more confortable with that we can clarified this20:54
costalesI'd like to hear to Quebec, Brittany...20:55
costalesNo all people read the mail list20:55
rwwI could point out the United States, but I expect that would just be pedantry ;)20:55
PabloRubianesrww: USA was the only exception when Locos where created20:56
PabloRubianesand I think is not fare to have different rules for them20:56
skellatrww: And the USA is definitely an exception as it a dual system of sovereigns.20:56
rwwPabloRubianes: I'm aware of the history involved, probably more than you are. I was pointing out a slight inaccuracy in your comment.20:56
PabloRubianesbut the new policy give the same posibility to the rest of the world20:57
nhainesThat the LoCo Council knew that Spain had independant LoCos and was still completely unprepared to address their concerns is a little disappointing.20:57
rww(my concerns, again, don't rest with the policy but the way it was communicated, hence me not really talking right now)20:57
skellatRight now I don't want to disappoint the Galician and Asturian teams but we're approaching 2057 UTC20:57
skellatDo they have representatives present to make their requests?20:58
felipexilskellat: /me from the Galician Team20:58
rwwskellat: remaining unaddressed concerns should go where? List, next meeting...?20:58
xuacuFor Asturian Loco, varela or me20:58
* ivarela too, for Asturian20:58
skellatrww: We will return to that matter in a few minutes20:59
rwwskellat: thank you20:59
skellat#topic Requests from the Galician and Asturian teams20:59
=== 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 | Regular LoCo Council Meeting for October 2014 | Current topic: Requests from the Galician and Asturian teams
skellatNow that the Galician and Asturian representatives are present, we can proceed.20:59
skellatThe policy, in its essentials, does not stipulate what the request should look like.20:59
felipexilThere was a lot of confussion in the mailing list. It was stated that existing LoCos will remain as indendent LoCos21:00
felipexilI would like to confirm this21:00
skellatfelipexil: We will address that later under "Any Other Business".  Right now it is out of order.21:00
PabloRubianesfelipexil: this is your request to be independent loco21:01
felipexilPabloRubianes: yes21:01
skellatRepresentatives of the teams, for the purposes of today's meeting, need merely make the following request: "That the XX Team be considered an independent LoCo team notwithstanding representing less than a country"21:01
skellatWith the name of the team substitute for XX21:01
ivarelayes21:02
skellatWould the representatives of the teams please state their formal requests?21:02
ivarelaI think it's the same case for both. The two groups have cultures, languages ​​and history that allows us to work at the same level as a LoCo with state21:03
skellatxuacu, do you make the same request?21:03
felipexilWe (the Galician team) make the same request21:04
xuacuI'm waiting for ivarela to do it, I could do on his behalf if he's not present21:04
skellatFellow Council members, the requests have been made.  Are you ready to vote on each item so as to dispose of the requests?21:04
costalesskellat, I'll no vote this time, because these teams are like brothers for me :)21:05
PabloRubianesok, can I ask why you don't want to be part of the Spain Team?21:05
ivarelaWhere do you live PabloRubianes ?21:05
PabloRubianesUruguay21:05
ivarelaDo you feel you are argentinian?21:06
ivarelaThat's the same.21:06
PabloRubianesno21:06
PabloRubianesyou are in the same country21:06
xuacuAsturian LoCo has it's own workflow. Despite our excellent relationships with es-LoCo we want to keep things as they are now21:06
felipexilPabloRubianes: the Galician team is organized around our "culture", specially by our language21:06
felipexilwe want to collaborate with all the teams21:06
felipexiland very specially with the teams in the Iberian Peninsula21:07
PabloRubianesfelipexil: I respect that, and I know that you have your language21:07
ivarelaanyway, culture and language is not the same. And we will not go back.21:07
PabloRubianesok21:07
ivarelatebanpb, Llumex03 and dangerouspiper can say exactly the same21:08
Llumex03Yep21:08
PabloRubianeslets vote then21:09
dangerouspiper+121:09
xuacuof course, our collaboration with es-LoCo will go on as usual, but as independent teams21:09
skellatThere will be two separate votes21:09
skellat#vote That the Galician Team, pursuant to their request this day, be considered an independent LoCo team notwithstanding representing less than a country.21:09
meetingologyPlease vote on: That the Galician Team, pursuant to their request this day, be considered an independent LoCo team notwithstanding representing less than a country.21:09
meetingologyPublic votes can be registered by saying +1, +0 or -1 in channel, (for private voting, private message me with 'vote +1/-1/+0 #channelname)21:09
skellat+121:09
meetingology+1 received from skellat21:09
PabloRubianes+121:09
meetingology+1 received from PabloRubianes21:09
SergioMeneses021:10
meetingology0 received from SergioMeneses21:10
skellat#endvote21:10
meetingologyVoting ended on: That the Galician Team, pursuant to their request this day, be considered an independent LoCo team notwithstanding representing less than a country.21:10
meetingologyVotes for:2 Votes against:0 Abstentions:121:10
meetingologyMotion carried21:10
skellat#vote That the Asturian Team, pursuant to their request this day, be considered an independent LoCo Team notwithstanding representing less than a country.21:10
meetingologyPlease vote on: That the Asturian Team, pursuant to their request this day, be considered an independent LoCo Team notwithstanding representing less than a country.21:10
meetingologyPublic votes can be registered by saying +1, +0 or -1 in channel, (for private voting, private message me with 'vote +1/-1/+0 #channelname)21:10
skellat+121:10
meetingology+1 received from skellat21:10
PabloRubianes+121:10
meetingology+1 received from PabloRubianes21:10
SergioMeneses021:11
meetingology0 received from SergioMeneses21:11
skellat#endvote21:11
meetingologyVoting ended on: That the Asturian Team, pursuant to their request this day, be considered an independent LoCo Team notwithstanding representing less than a country.21:11
meetingologyVotes for:2 Votes against:0 Abstentions:121:11
meetingologyMotion carried21:11
skellat#info Marcos Costales, in his capacity as leader of Ubuntu Spain and as a member of LoCo Council, stood aside from both votes.21:12
skellatThe requests are granted.  The Asturian team is reminded that re-verification is still due at the deadline specified on Launchpad.21:13
felipexilThanks!21:13
skellat#topic Any Other Business21:13
=== 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 | Regular LoCo Council Meeting for October 2014 | Current topic: Any Other Business
skellatWhat other business is there before the LoCo Council at this time?  It is presently 2113 UTC.21:13
xuacuThank you all for hearing us21:13
skellatxuacu: If you had written to us as asked prior we could have disposed of this even more quickly.21:14
nhainesWhat is the preferred forum for exception requests?21:14
ivarelaThank you very much21:14
ivarelafelipexil, gracies home!!21:14
skellatnhaines: We're still debating that internally.  This is the first time we've approached such since the policy was adopted so most of it was handled in a pro forma fashion.21:14
skellatIf we had been written to, the turnaround would possibly have been quicker.  We only hold one IRC meeting per month.21:15
skellatWhen in doubt, write to us.21:15
skellatWe try to not let things get hung up due to the calendar if we can avoid it.21:16
nhainesSo provisionally, the preferred form of contact is via email to the LoCo Council?21:16
skellatFor now, yes.21:16
skellat#info Those who have requests of the LoCo Council are advised to write to it at loco-council@lists.ubuntu.com for assistance.21:17
skellatrww: Do you wish to continue discussion of your matter?  We're unfortunately not quorate at this point as Sergio and Pablo had to depart.21:18
rwwsorry, work matter. yes.21:18
xuacustill, it's very likely that things goes out of control21:18
skellatOkay21:19
rwwso as I mentioned earlier, I was concerned (and I think nhaines was?) about the communication surrounding this policy21:19
nhainesrww: that is an accurate representation of my concern.21:19
skellatBad situations make for bad policy.21:19
xuacuI've found this issue already in a bad state21:19
rwwFor example, as I mentioned earlier, I didn't see public discussion of it beforehand, which I think is something that could be improved in the future.21:19
skellatMay I tell some of the back story?21:19
rwwsure :)21:20
skellatOkay21:20
skellatFirst the Catalan team came up for re-verification21:20
skellatUnder one country, one LoCo we said they didn't fit as they're still part of Spain21:20
skellatYes, they're trying hard to have a separatist referendum but for now they're still part of Spain21:20
skellatThe Catalan team didn't like that so they took the matter up with Community Council21:21
skellatAfter a long and not so happy meeting between both bodies, LoCo Council was tasked with trying to find a way to adapt what had existed prior to accommodate the Catalan situation21:21
nhainesWhy was it so important to disband the verified, fully-functional Catalan team?21:21
xuacunhaines: I second your question21:22
skellatnhaines: We were trying to clean up what we had in terms of policies and exceptions (written, unwritten, and some partially forgotten) to bring it into a coherent whole21:22
skellatThis was also prior to the Scottish independence vote failing21:22
skellatAfter multiple rounds of LoCo Council deadlocking on trying to adapt policy so that forgotten understandings, barely documented exceptions, and the like could be cleaned up...21:23
skellat...we voted via CIVS.21:23
skellatBy majority vote we adopted what we had.21:23
skellatThis stretched on for about 3 months.21:24
skellatWe finally submitted the policy to Community Council to see if they felt it would help ameliorate the situation that arose with respect to the Catalan team, they were okay with it, and we then resolved the Catalan matter.21:24
skellatThere were a couple different versions we voted on and this one was the one we felt would be flexible enough to accommodate the future.21:25
skellatAs to the US, the exceptions for the individual states stay because of the unique system of dual sovereignties in play especially considering every Governor has their own army (## State National Guard) as well as the federal forces.21:26
rwwI think discussing the US fully would probably not be productive, so unless someone objects we can probably set that aside :)21:27
rww(US sovereignty is... a fun topic)21:27
nhainesNot the consideration that a US LoCo with 50 team leads and almost no geographical continuity would be completely unproductive?21:27
skellatrww: LoCo Council spent a week going round and round about it and there was a "red team" discussion of creating a single US LoCo undertaken.21:28
nhainesActually I like rww's better.21:28
tebanpbI have a question then. What about countries without their own army? :s21:28
rwwSo yeah. Communication. I understand (and now more fully understand) that it was a difficult situation, and that bringing it up for public discussion was in some ways problematic.21:29
skellattebanpb: :-) That was just one example of dual sovereignties in the US system.21:29
skellatrww: Yeah, you could say that.21:29
skellatDoes it need work?  Probably.21:29
elfyo/21:29
skellatelfy: Hello comrade21:29
rwwHowever, as someone who part-manages a LoCo that occasionally threatens to try to be two LoCos, I would have appreciated *something* on loco-contacts@, even if it were just "we're pondering the one-LoCo-one-state policy, if you have input email the LoCo Council off-list"21:29
tebanpbBut sovereignty is a political concept which is defined differently in each country21:30
rwwI mean, it's water under the bridge now, but please consider that for future issues :)21:30
nhainestebanpb: this is why the guidelines allow for exceptions on an individual basis.21:30
tebanpbAs a matter of fact I don't get why we are getting so much into these politic issues :s21:30
rwwAnd I've said my piece, so back to the others for their comments I guess.21:30
costalestebanpb, all it's politic21:30
skellatrww: We're all fairly exhausted from the Utopic Unicorn cycle getting the issues of the Iberian Peninsula settled.21:31
costalestebanpb, our society and live21:31
costales;)21:31
dangerouspiperskellat you konw that in Spain is a system with dual sovereignties?21:31
tebanpbI mean institutional politics21:31
tebanpbdangerouspiper is right about that21:32
skellatOkay, does anybody else have anything else to raise before the LoCo Council at this time?21:32
costalesdangerouspiper,  I tried to explain to the Council21:32
tebanpband we could end discussing about what sovereignty means, it's pointless21:32
skellatNothing being heard, this meeting is concluded.  Thank you all for your participation.21:33
costalesI think is not a political issue, it's a cultural/language issue21:33
skellat#endmeeting21: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
meetingologyMeeting ended Tue Oct 21 21:33:47 2014 UTC.21:33
meetingologyMinutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2014/ubuntu-meeting.2014-10-21-20.00.moin.txt21:33
costalesthanks a lot skellat for be our chairman :)21:33
skellatYour welcome.21:33
skellats/Your welcome/You are welcome/21:34
costalesxD21:34
costalessed rules!21:34
nhainesxuacu, ivarela, felipexil: congratulations.  :)21:34
costalesbye bye!21:34
xuacuNigth everyone and thank you again :)21:34
felipexil skellat: I'm a bit late, but I think the policy should be clarified21:34
felipexiljust in case other teams are in our situation21:34
felipexilnhaines: thanks!21:34
xuacubye!21:35
ivarelanhaines, thanks to you21:35
felipexilthanks xuacu, ivarela!21:35
nhainesYour result is what I thought the policy should allow, and I'm happy it worked out that way.  I hope that this helps to relieve some of the concerns of the community.21:35
ivarelafelipexil, gracies home!21:35
nhainescostales: can't get enough of us?  :)21:36
=== IdleOne is now known as Guest88208

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