/srv/irclogs.ubuntu.com/2013/09/19/#ubuntu-meeting.txt

=== freeflying is now known as freeflying_away
=== freeflying_away is now known as freeflying
=== freeflying is now known as freeflying_away
=== freeflying_away is now known as freeflying
ghostcubehttp://www.youtube.com/watch?v=A9b9bxUyK0o  xD07:50
=== freeflying is now known as freeflying_away
=== doko_ is now known as doko
=== freeflying_away is now known as freeflying
=== freeflying is now known as freeflying_away
=== freeflying_away is now known as freeflying
akerbeltzam I too late for the l10n  session?16:25
=== akerbeltz_ is now known as akerbeltz
dholbachakerbeltz, nope, the meeting will start in 13m16:47
akerbeltzthanx, i miscalculated UTC to GMT it turns out16:47
pleia2#startmeeting17:00
=== akerbeltz_ is now known as akerbeltz
dholbacho/17:00
pleia2#chair dholbach czajkowski beuno17:00
meetingologyMeeting started Thu Sep 19 17:00:35 2013 UTC.  The chair is pleia2. Information about MeetBot at http://wiki.ubuntu.com/meetingology.17:00
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:00
meetingologyCurrent chairs: beuno czajkowski dholbach pleia217:00
hanniehello CC17:00
beunohello hello!17:00
pleia2welcome to the Community Council meeting :)17:00
czajkowskialoha17:00
pleia2#chair Gwaihir17:01
meetingologyCurrent chairs: Gwaihir beuno czajkowski dholbach pleia217:01
akerbeltzhi17:01
dholbachso it seems we have people from the translations community here! *\o/*17:01
pleia2#link https://wiki.ubuntu.com/CommunityCouncilAgenda17:01
pleia2^^ Agenda17:01
pleia2#topic Translations Community Check-in17:01
=== meetingology changed the topic of #ubuntu-meeting to: Translations Community Check-in
pleia2so with these check-ins we just see how the team is doing, if there are any issues that we can help with, etc17:02
dholbachwelcome hannie and akerbeltz - anyone else here from the translations community?17:02
hanniethanks for the welcome17:02
Geochrdholbach, Hi from Greek team17:03
dholbachhow are you doing? how are things in the translations world? :)17:03
dholbachwelcome Geochr!17:03
hannieWell, we can start translating now (freeze). Most of the messages are translated alreaddy17:03
hannie*already17:04
pleia2yay freeze day \o/17:04
dholbachdo you have good communication channels to most of the teams? (like: are they all on the mailing list and so on?)17:05
hannieThere is a mailing list for translators which we use frequently. It works well.17:05
hannieAll translation team members can communicate via this mailing list17:06
hannieubuntu-translators@lists.ubuntu.com17:06
dholbachgreat, so all the team should know about the freeze date and everything17:07
dholbachI think I remember language pack creation from our last meeting to having been a bit of a problem - is that still the case?17:08
hannieI haven' t mentioned the freeze on the translators list. Perhaps I should do so17:08
pleia2hannie: probably a good idea :)17:09
dholbachyeah, a "ready? set? go!" message might help :-)17:09
hanniedholbach, I offered my help with the language pack updates17:09
hannieBut Milo Casagrande, who offered to help me get on the way, has not contacted me yet17:09
pleia2that's Gwaihir17:10
akerbeltzpleia2 told me it's ok to just bring up any issues - we (GunChleoc and me) had some specific problems with the Gaelic localization (rogue translator) but I think they have wider implications. At the moment there seems to be no efficient way of dealing with rogue translators globally on Launchapd and there is also no way of purging really bad translations17:10
pleia2Gwaihir: can you follow up with hannie?17:10
dholbachakerbeltz, did you talk to other teams to find out how they dealt with similar issues in the past?17:11
akerbeltzyes17:11
hannieah, those nicks :)17:11
Gwaihirpleia2, hannie, I will, and I need to chase the other person who offered help, since I didn't hear from him17:11
hannieGwaihir, ok, I will wait and see...17:11
akerbeltzmostly they suggested managing the issue via teams but the problem is that there are projects/packages on Launchpad which are *outside* the main Ubuntu files (such as Linux Mint). This left us in the position of having to chase the owners of individual projects17:12
akerbeltzwhich is problematic as they, on the whole, cannot tell if a translator is good or bad in his or her language17:12
akerbeltzit also costs a LOT of time17:12
dholbachakerbeltz, were you able to reach out to the translator to try to integrate them better into the team?17:13
hannieakerbeltz, I saw that this rogue translator has withdrawn from Launchpad17:14
akerbeltzI have been trying to (very diplomatically initially) talk to the guy in question for over a year now but in a nutshell, he though he was the beezneez and eventually I had to be more clear about the quality implications. at that point he resigned from the Ubuntu team for gd. But sadly he then started picking on projects that are not "covered" by that team17:14
akerbeltzyes he has now left but for the future, I think there ought to be a better process of handling rogue translators globally. I'm sure we are not the only locale in danger of those17:15
hannieI think the best option is to make a team moderate or restricted17:15
hannieWhen a team is open, anyone can have their translations accepted immediately17:16
akerbeltzbut that does not seem to work globally17:16
GunChleocThe proble is that we're not talking about problems in a team here, we're talking about somebody goind off on a rampage across a whole language. There are mutilpe teams on Launchpad17:16
czajkowski+117:17
Geochrakerbeltz, Try to contact with the owner of the project17:17
GunChleocAnd of course a team leader will gladly accept somebody to start a new localization not knowing if the person is any good17:17
hannieGunChleoc, the problem is that Linux Mint is an open team17:17
czajkowskiit can be difficult as you do want people to be involved17:17
czajkowskiis there possibly a way to mentor soeone17:17
czajkowski*someone17:17
GunChleocOh, I see. It proves my point though17:17
GunChleocWhen somebody refuses mentorship, no.17:18
czajkowskisee if they've done some transalations and then let them translate more17:18
akerbeltzYes but that means that once you spot a rogue, you then have to chase him across all projects, that costs a lot of time and in most cases, the project owners cannot tell good from bad17:18
GunChleocIt's easy when you have a bog language like, say, German with over 1000 contributors, there are enough people to know about quality and so forth. In a small language, things are more difficult17:19
akerbeltzsome translators are so bad mentoring is not an option, we're not talking debates about a comma or a typo here or there, we're talking barely fluent people17:19
czajkowskiakerbeltz: that is up to the owners of the project imo. I saw many mails when I worked in launchpad of people not likeing translations and it's difficult to police17:19
hannieczajkowski, or the LoCo perhaps?17:21
akerbeltzbut that causes serious quality issues down the line - if you owned a project and there were two Gaelic translators arguing that the other party is producing bad stuff, how could you judge? and if you just step back and say "you sort it out" then in the end the end user suffers because they get gibberish on screen. which does not help the image of Ubuntu/Linux17:21
Geochrakerbeltz, A solution is to create a team (not open) and to contact with the owner of the project to change the translation permissions into the "official" translationteam17:21
akerbeltzwe tried that17:21
akerbeltzthe rogue then came back with a whole lot of aggro17:22
akerbeltzand the owner then change it back to "open" because he (rightly) said he could not judge17:22
dholbachI think that or similar stories have happened across quite some teams17:22
akerbeltzi'm sure it has17:23
akerbeltzwhich is why I wanted to raise it17:23
Geochrif the owner change the permission, then if someone is out of the team, he is not able to review messages17:23
Geochralways hiw messages will be as suggetions17:24
Geochrhis*17:24
GunChleocThis is actually the really big problem we had with him, that he kept marking bad translations as reviewed17:24
hannieGeochr, not when the team is open17:24
czajkowskiGunChleoc: so I used to see a lot of that in a similar manner on launchpad answers17:24
Geochrhannie, you are right17:24
akerbeltzit was open. then I contacted the owner and he restricted the project. fine. the rogue then came back and argued. the owner then said he could not judge and set it to open. There are a LOT of projects across Launchpad. If we have to argue with *each* that will cost us SO much time we might as well not bother17:25
Geochrthiw is the first i have write17:25
czajkowskithe best bet there is to email them and say there are issues here and expain why it's not working, if it continues then perhaps look at having them not in the team especially if it leads to more work down the line17:25
GunChleocAnd it also puts the project leaders into an impossible situation17:25
dholbachthe general approach I've witnessed across teams has almost always been to reach out to the person, sometimes through somebody in their loco team or city group or somehow near them or by the phone or skype (this has worked well in many cases) to get them to live up to the team's standards17:25
czajkowskidholbach: +117:26
GunChleocThe problem is that our language is too smal to have another person mediate17:26
hanniedholbach, I agree that the loco team could act as a judge17:26
GunChleocThere are 3 of us only for the entire language across all open source projects under the sun. akerbeltz, me and the rogue17:26
Geochr+1 hannie17:26
GunChleocSo, who's the loco team that could mediate?17:27
hannieIs there a Scottish loco team?17:27
akerbeltz_dholbach, that again only works for big languages. GunChleoc and me are the only localizers (on the whole) working for Scottish Gaelic. There is no loco team or city group.17:27
czajkowskihannie: no it falls under UK as it's not language specific17:28
dholbachakerbeltz: does somebody live near to the guy who did the translations?17:28
akerbeltz_all we have is his handle, no idea who he is or where he lives17:29
=== akerbeltz_ is now known as akerbeltz
dholbachah, I thought you were in touch with him somehow17:29
akerbeltzemail17:29
dholbachso in a couple of cases I offered to have a chat on skype or somewhere else, maybe that'd work, but it seems he left the team already17:29
GunChleocYes, e-mail only. akerbeltz is the one who did the direct communication with him17:29
dholbachso that'd probably be a suggestion for the next time you run into a similar issue17:30
akerbeltzdo you know how many junk translations he submitted until he got annoyed enough to leave? and what if the next guy won't leave?17:30
akerbeltzwe will be proofreading after someone else's priorities forever rather than work out priorities for the locale and getting it right the first time17:31
GunChleocMaybe there should be an established process to handle such cases17:31
akerbeltzor a global Launchpad team for each locale17:31
GunChleocWe will still have to chase him on Transifex as well - not looking forward to that17:31
GunChleocA global team is a good idea17:31
akerbeltz(sorry my internet keeps dropping out, rainy day in Glasgow)17:32
GunChleocWe could have a global team for access rights, and then people could still join individual teams for the projetcs they wish to translate17:32
czajkowskiakerbeltz: have you brought up any of these suggestions onto the launchpad translations mailing list ?17:33
dholbachakerbeltz, I can't guarantee you that having a chat on the phone or skype will resolve all problems every single time17:33
dholbachakerbeltz, it's just my experience that some personal contact often helped, and that mistakes or misunderstandings could be cleared up quicker17:33
akerbeltzyes, silence from any known admins, other team leaders suggesting team with restricted settings but that clearly doesn't work globally, I also posted a question17:33
dholbachbut I'm not going to try to convince you - it was a suggestion17:33
akerbeltzit wasn't personal, honestly, I can forward you the emails. it was purely based on 15 years of experience in the translation industry17:34
GunChleocThe problem is that our rogue is actiny deply offended, and people in that state won't listen. So, it would have to come from a "neutral" party17:35
czajkowskiakerbeltz: it can be tricky to have a industry background when working in a community setting, the two often need to work harder togeteher to get done as people have different opinions and ideas.17:35
* hannie has to leave in a minute. Success in solving this problem17:35
GunChleocthanks Hannie17:36
dholbachhannie, any other items you wanted to bring up in the meeting?17:36
czajkowskihttps://launchpad.net/~launchpad-translators17:36
hannieNo, just the language packs updates17:36
czajkowskiI think it might be good to bring up some of the ideas on this list17:36
hannieSee you all17:36
dholbachhannie, perfect, thanks a bunch17:36
akerbeltzczaj, I agree, Launchapd is not the only project I'm working with. But there is a fundamental level of language skill you need before you can translate *anyt*thing even vaguely useful and some folk just don't have that17:36
akerbeltzsee you hannie17:36
akerbeltzit was, honest to [insert preferred invocation] at the "all you base are belong to us" level17:37
czajkowskiakerbeltz: I understand, but at the same time we in the ubuntu community do try and find ways for people to contribute in non code like ways so for some translations is key. we all just need to work together and it can be a bit harder with a language barrier.17:37
dholbachakerbeltz, right - we've seen the same in support forums, in Ubuntu development, in QA and many other parts of the community... you often have people who are very excited, sometimes very young, sometimes you have a language barrier or a different temper or whatever it may be - it can be difficult17:38
akerbeltzyes, I offered that too. In fact, I didn't even ask him to quit - all I asked for initially was to pause so we could catch up proofreading. No luck. I offered he could help in face to face workshops, no interest.17:38
dholbachakerbeltz, so GunChleoc suggested a neutral party, you suggested a global team - did you bring up those ideas on the translators list?17:39
akerbeltzyes, ringing silence17:39
akerbeltzexcept from fellow team leaders who suggested things along the lines of restricting permissions17:40
dholbachI'm not an expert when it comes to Launchpad's translations permissions, so I'm afraid I can't comment on that.17:41
dholbachMaybe it'd be worth reaching out to teams who had similar issues again and see if you can get them to reply to the mail.17:41
akerbeltzand how would I find them? and what would I propose?17:42
dholbachI thought somebody said earlier that other teams had had the same issues in the translations space17:42
dholbachin any case I'd probably try again to revive the mailing list thread17:42
akerbeltzyes, all from biiig languages who have enough people to set up teams for everything17:42
akerbeltzsurely the quality of localization must be important to the project? sure, the code makes it tick but the point of contact with the user is the UI - if that brings up gibberish, the user won't care how wonderful the code is.17:43
pleia2I don't think anyone said it wasn't important, it's just a tricky problem to solve17:45
dholbachtrust me, I do understand the importance of translations - unfortunately I just can't comment on Launchpad permissions or on the proposal as I'm not very much involved in the translations space17:46
pleia2akerbeltz: can you forward your email to the translations list to community-council@lists.ubuntu.com and we can follow up to see if we can find some launchpad folks with some more ideas?17:46
dholbachpleia2, yes - good idea17:46
akerbeltzok17:47
dholbachthanks17:47
GunChleocWe might have to changee the permission system for a global solution17:47
dholbachdo we have any other issues anyone wanted to bring up from the translations community?17:47
akerbeltzI will draft something with GunChleoc17:47
dholbachwe still have the membership board up in the queue - anyone from the board in here?17:47
pleia2chilicuil: you here?17:48
GunChleocLaunchpad translators decides who can found a global language team, then the global language team can vet new translators, who then can join projects.17:48
Geochrdholbach, what is going with ubuntu translation stats?17:48
dholbachGeochr, hannie would probably have been a good person to ask17:48
dholbachI'm afraid I don't know - if there are issues with it, it might also be worth raising it on the team mailing list17:49
pleia2IdleOne? Pendulum_? cjohnston? hggdh?17:49
PabloRubianespleia2: now is time to the membership board?17:49
pleia2should update https://wiki.ubuntu.com/Membership/Boards/SittingMembers some expired17:49
pleia2PabloRubianes: yes17:49
PabloRubianesI am here17:49
PabloRubianes:)17:49
pleia2#topic Membership Board Check-in17:49
=== meetingology changed the topic of #ubuntu-meeting to: Membership Board Check-in
dholbachI'd like to thank all the translators for the great work they've been doing. Keep up the good work!17:49
akerbeltzok, thanks folks, see youse17:50
pleia2PabloRubianes: happy birthday :)17:50
pleia2and welcome!17:51
GeochrAlso i awant to say for a bug that affects all the translations problems17:51
IdleOnehalf here17:51
PabloRubianespleia2: thanks!17:51
chilicuilhi there17:51
pleia2Geochr: if any changes are made, we'll be sure to coordinate that properly with the translations community17:51
GeochrI have reported but it has been marked as low priority17:51
chilicuilcongrats PabloRubianes, today is my birthday too =D17:51
dholbachcongratulations chilicuil!17:51
pleia2chilicuil: neat, happy birthday to you too!17:51
pleia2mine is 10 days away :)17:52
PabloRubianeschilicuil: hehehe so happy birthday too :D17:52
Geochrhttps://bugs.launchpad.net/launchpad/+bug/97597017:52
ubottuUbuntu bug 975970 in Launchpad itself "Messages reviewed in translator mode if you don't check manually "Someone should review this translation"" [Low,Triaged]17:52
chilicuilPabloRubianes, pleia2 =P17:52
pleia2Geochr: good to know, thanks17:52
pleia2we're approaching an hour for this meeting, so we should move on to the membership board17:52
chilicuildholbach: n_n17:52
czajkowskiGeochr: re the LP bug, LP is in maintenance mode and bugs taged low really may not get done without community involvment as LP is down to two people.17:53
pleia2anyone from the membership board have comments about how things are going? any issues? happy stories? things we can help with?17:53
czajkowskipleia2: happy Birthday!17:53
czajkowskiPabloRubianes: Happy Birthday17:53
PabloRubianesczajkowski: thanks!!!17:53
PabloRubianespleia2: I think we are doing fine, we have a regular amount of applicants17:54
Geochrczajkowski, what do you suggest ?17:54
czajkowskiGeochr: we have to move to the other board as running low on time sorry17:54
czajkowskiPabloRubianes: do you guys have enough people on the board to make the meetings?17:54
PabloRubianesczajkowski: we always get at least 417:55
PabloRubianesin the 22UTC17:55
Geochrok thanks, i hope to be that soon17:55
chilicuilwe had some issues with an asian team who tried to get the membership in bulk, language barriers, we started discussing ways to improve the situation however we've not decided anything yet17:56
PabloRubianesthe only problem we had lately was17:56
czajkowskichilicuil: membership in bulk is new to me :)17:56
czajkowskiwhat happened?17:57
PabloRubianeswe got almost all the myanmar team17:57
PabloRubianesapplying as 117:57
pleia2they had identical pages because they all contributed to the same events17:57
pleia2so it was really hard to tell who did what17:57
czajkowskiah I see17:57
PabloRubianespleia2: the problem was not just the events17:58
chilicuilwe had 10~ applicants from the same loco team, many of them had very similar input in its wiki pages, it seems it was because of a language barrier that they couldn't personalize his pages, and communication wasn't great in the meeting neither17:58
PabloRubianesevents, testimonials17:58
* pleia2 nods17:58
PabloRubianesand the language barrier got them angry17:58
PabloRubianeson top of all the time zone was a mess too17:59
PabloRubianesfor them was like 5am17:59
IdleOneIt was frustrating for all involved17:59
czajkowskinods17:59
czajkowskiin siutations like that would doing it via email be of use17:59
czajkowskitimezones are tricky17:59
PabloRubianesczajkowski: they had the other board18:00
PabloRubianesbut I email them before the meeting about that18:00
czajkowskinods ok18:00
IdleOneThat is what happened. We gave them some instructions on improving their personal wiki pages and took the vote to email.18:00
PabloRubianesbut after the got angry i got "Ohh I wait until 5am and I don't get elected?"18:00
pleia2sounds like one of those unusual situations that won't really come up often and you handed it well18:01
PabloRubianesthay*18:01
PabloRubianesthey*18:01
IdleOneit still turned out that most were not approved and some got upset...18:01
czajkowskipleia2: indeed18:01
IdleOnepleia2: yes, it isn't something I think will happened too often. Was certainly a test for both the board and the applicants18:02
PabloRubianesI think they still didnot understand what happend18:02
PabloRubianesIdleOne: +118:02
IdleOneAll in all I think the Membership board (12-22UTC) are doing good. I think we may need to step up on our team reports. I am guilty of not doing them myself :/18:04
czajkowskianything the CC can help with folks?18:05
pleia2I think the most important thing is getting the announcement emails out, more than team reports18:05
pleia2so if you want to focus on something, I'd suggest there :)18:05
IdleOneNothing I can think of, the meeting seem to run smooth. I think our main thing is the paper work after. I think the we have been good about the emails being done. PabloRubianes chilicuil ?18:06
chilicuilthe wiki page could take some love too, when people go to https://wiki.ubuntu.com/Membership they should feel inspired18:06
pleia2haven't seen an announcement for the last meeting yet18:06
PabloRubianesI agree with IdleOne18:06
chilicuileverything else seems ok to me18:06
czajkowskiexcellent18:07
dholbachgood work!18:07
IdleOnepleia2: I'll remind the 1200 folks about it.18:07
pleia2thanks :)18:07
czajkowskiThank you for all your hard work!18:07
pleia2and thanks for joining us here at the meeting18:08
dholbachhave a great rest of your day everyone!18:09
dholbachchilicuil, PabloRubianes: enjoy your birthdays! :)18:09
IdleOnethank you.18:09
PabloRubianesdholbach: thanks18:09
PabloRubianesOne more thing18:09
PabloRubianesto the CC18:09
PabloRubianesI've just send you the LoCo Council applications18:09
dholbachyep, saw the mail18:10
PabloRubianes:)18:10
IdleOneoh, +1 PabloRubianes for LoCo council18:10
pleia2#topic Any other business18:10
dholbachI'll have a look at it tomorrow18:10
dholbachdoes anyone else have any other agenda items or things you wanted to bring up?18:10
pleia2now that the LoCo Council call is wrapped up, we'll be sending out the Community Council restaffing call within the next day or so18:10
pleia2(we expire in mid october)18:10
=== meetingology changed the topic of #ubuntu-meeting to: Any other business
* pleia2 gives meetingology some more internets18:11
dholbach:-)18:12
pleia2oh!18:12
pleia2dholbach: how do we make a change to http://www.ubuntu.com/about/about-ubuntu/governance ?18:12
pleia2the first paragraph under CC confuses me a bit and doesn't seem accurate18:12
pleia2"It is the Community Council that approves the creation of a new team or project, along with team leader appointments."18:12
pleia2we don't strictly do that18:12
dholbachpleia2, for now just file a bug, but I still have work item from UDS to find a few folks who would like to be co-editors of the page18:13
dholbachhttps://bugs.launchpad.net/ubuntu-community-website/+filebug18:13
pleia2dholbach: this is on ubuntu.com18:14
pleia2not community18:14
pleia2maybe https://bugs.launchpad.net/ubuntu-website/+filebug ?18:14
dholbachoh sorry18:14
dholbachhttps://bugs.launchpad.net/ubuntu-website-content/+filebug18:14
pleia2ah ok18:14
pleia2thanks, I'll do that18:15
pleia2and sub the cc to the bug18:15
dholbachcool18:15
* pleia2 peers at trello real quick18:15
pleia2ah, we had a volunteer go through our planet config18:16
pleia2still need to review his feedback18:16
pleia2I'll dig up that mail and follow up soon18:16
pleia2ok, I guess we'll wrap this up then :)18:17
* dholbach hugs pleia218:17
pleia2thanks everyone18:17
dholbachthanks a  bunch!18:17
pleia2#endmeeting18:17
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology
meetingologyMeeting ended Thu Sep 19 18:17:53 2013 UTC.18:17
meetingologyMinutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-09-19-17.00.moin.txt18:17
meetingologyMinutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-09-19-17.00.html18:17
dholbachall right... dinner time!18:17
dholbachsee you :)18:17
=== PaulW2U_ is now known as PaulW2U
=== Ursinha is now known as Ursinha-afk
=== ampelbein_ is now known as Ampelbein
=== jpierre03_ is now known as jpierre03
=== freeflying is now known as freeflying_away
=== freeflying_away is now known as freeflying
=== Pendulum_ is now known as Pendulum
=== freeflying is now known as freeflying_away

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