11:00:19 #startmeeting l10n 11:00:19 Meeting started Mon Dec 11 11:00:19 2017 UTC. The chair is jibec. Information about MeetBot at http://wiki.debian.org/MeetBot. 11:00:19 Useful Commands: #action #agreed #halp #info #idea #link #topic. 11:00:19 The meeting name has been set to 'l10n' 11:00:27 #chair jibec 11:00:27 Current chairs: jibec 11:00:34 hi.. 11:00:42 #chair jibec aabuke noriko pravins ljanda semanticdesign 11:00:42 Current chairs: aabuke jibec ljanda noriko pravins semanticdesign 11:00:53 #info Please remember numbers are tickets numbers in https://pagure.io/g11n/issues 11:01:03 #topic Flock feedback 11:01:07 #topic #38 Host Zanata in Fedora infrastructure 11:01:24 no news, as always, brian (bexelbie) can't find ressources 11:01:30 it isn't easy to host Zanata, I feel like we should close this goal as no improvments in 6 months. 11:01:56 next ? 11:02:03 #chair jibec aabuke noriko pravins ljanda semanticdesign suanand 11:02:03 Current chairs: aabuke jibec ljanda noriko pravins semanticdesign suanand 11:02:06 jibec: if we get any help from Zanata team, will that help? 11:02:22 though as you know, Alex mentioned last time they dont have a resource. 11:02:32 the first step is to find someone willing to host it, and a working java server 11:02:36 lets send them email and if no progress, good to close. 11:02:57 jibec: so requirement is more from people side, not from hardware resources, right? 11:03:18 I'm sure Zanata team will help, but if no one would like to be technical administrator 11:03:30 good point !! 11:03:41 * bexelbie is lurking 11:03:46 we are making progress 11:04:07 there is an IT ticket working for resources - if it doesn't come through we will pivot to Plan B with new infra and more community infra support 11:04:22 I am talking to Alex and others 11:04:37 It is just slow :( 11:04:39 no offense, but this means same status as november, isn't it? 11:05:11 yes 11:05:23 in part because part of the dependency chain had PTO :) 11:05:26 ok, thanks bexelbie, good luck with this... 11:05:28 and not offended 11:05:33 slight movement is not no movement 11:05:40 bexelbie, can you point the ticket? 11:05:41 but that is also not significant movement 11:05:42 please translate "PTO" ;) 11:05:57 noriko, the ticket in question is internal to IT inside of RH 11:06:01 PTO = vacation/holiday 11:06:08 thanks, next subject 11:06:13 #topic #39 Using Transtats to track out-of-schedule string change for F28 11:06:16 Okioki, kinda I knew it 11:06:27 suanand: would you like to talk about your work, 11:06:29 ? 11:06:37 jibec, just one point: included f28 in transtats.xyz 11:07:17 can you write an email to mailing list about what works now and how to use it for f28? 11:07:18 hello :) 11:07:19 some discussion around track out-of-schedule string change is happening here: https://github.com/transtats/transtats/issues/69 11:07:35 jibec, good point, I will 11:07:46 Hi, sorry for being late. 11:08:13 we need to find out how to help the F28 release with this new tool 11:08:20 hello :) 11:08:29 so, it's time to communicate about the current status :) 11:08:29 working on koji and stuffs to look into translation diffs more closely 11:08:33 Hi jonatoni abd rluzynski 11:08:49 Hi noriko ;) 11:09:14 next 11:09:20 #topic #40 The documentation system reboot & translation 11:09:31 Test with French language is undergoing, here is our tracking pad : https://pad.lqdn.fr/p/fedora-docs-internationalization-jibecfed 11:09:56 there is a little patch stuck in Brian's hands to finish this work 11:10:12 tests are good, only finalization step is stuck 11:10:56 bexelbie or bexelbie[m]: anything to add ? 11:11:49 once this patch is done, we'll have to figure out the publishing process and how to enable new languages (this isn't fully automated) 11:11:57 next? 11:12:12 #topic #32 T-shirts for active contributors of Translation group 11:12:23 t-shirts are printed, cards are not 11:12:54 ticket is here: https://pagure.io/design/issue/557 11:13:03 bexelbie: anything required from anyone of us here? 11:13:05 this is an outstandingly long task... 11:13:15 but we'll finish it someday :p 11:13:22 jibec: it involved multiple printing ;) 11:13:34 we will have more experience for the next time :P 11:13:56 yes, let's hope we'll improve ;) 11:14:07 but i am more happy for Card we are going to print, i will keep it on my Desk B-) 11:14:26 I just sent a new comment in the design ticket 11:14:36 let's hope it moves forward 11:14:37 * pravins checking 11:14:49 next subject 11:14:51 #topic #35 FAS group for L10N #37 FAS group cleanup 11:14:54 👍 11:15:04 still waiting for a script from infrastructure team 11:15:32 the cvsl10n management is just a pain, is badly designed, i'm the only one to do it for now 11:15:38 jibec: who suppose to write script? 11:16:09 https://pagure.io/fedora-infrastructure/issue/6320 11:16:23 kevin said : codeblock pingou or puiterwijk 11:17:18 if they draft something, I can improve it and use it often to have a sync between zanata and FAS, but for now... 11:17:44 next 11:17:47 #topic #43 Adding Filipino 11:18:06 aabuke: can you please tell us what is the status of your team? :) 11:18:38 jibec, i am coordinating with instructors and recruiting students to join us. 11:19:37 good, can you please translate one package so filipino is available for F28? 11:19:43 I will be ready by 2018, i found out that i was a member of transifex and voluteered for translation but I felt guilty that I joined fedora first... 11:19:47 I suggested media writer 11:20:04 Sure... 11:20:04 aabuke: I think that you can also translate on your own, you don't absolutely need to recruit other people if that's difficult. 11:20:28 +1 rluzynski 11:20:34 that's true, having a team is just making it easier 11:20:40 it isn't mandatory 11:20:46 rluzynsi: noted! 11:21:29 so, about blog post to promote this translation, do someone feel like drafting something? 11:22:17 * pravins appreciating aabuke efforts on Filipino language translations. 👍 11:22:42 am not a good writer, :) can anyone give me a sample promotions made by fedora ? it will help me get started... 11:23:05 pravins: thanks... 11:23:34 semanticdesign: do you feel like it? 11:23:57 i am sorry. no :) 11:24:03 haha, I had to try :p 11:24:17 ok, I'll draft it if nobody volonteers ;) 11:24:23 next year, i am planning to give out shirts to those who will help me... locally, 11:24:40 ok! good idea 11:24:49 ok, next subject? 11:25:06 do i need approval on the shirt prints? 11:25:16 f 11:25:35 haha, I suggest to first focus on your translation and communication and recruitment 11:25:45 then we'll help you with this tshirt thing 11:26:02 jibec: thank you! 11:26:02 we already have to finish our tshirt distribution, we may have some left you may reuse 11:26:15 on step at a time :) 11:26:40 Appreciate that one! :) 11:26:44 but to have tshirt you need money, which you request to concil, which is easy to say, but also takes time 11:26:56 #topic #45 cvsl10n - november followup 11:27:02 I removed request of FAS users 11:27:15 which are not in Zanata and did not answer my emails 11:27:29 there is nothing more here, next 11:27:53 jibec: excellent, happy you took action finally. 11:27:53 #topic #48 Fedora 28 translation sprint l10n 11:28:14 We should probably run a translation sprint for Fedora 28 :) -> https://fedoraproject.org/wiki/Releases/28/Schedule 11:28:31 2018-02-06 is software String Freeze 11:28:48 pravins, sorry for delayed response - we are missing a bunch of addresses 11:29:04 bexelbie: please wait for the end of the meeting 11:29:42 can we plan translation sprint for the week before string freeze? 11:30:03 jibec: good to start it 2 week before. 11:30:14 january 22th ? 11:30:37 👍 11:30:44 2018-02-20 is Change Checkpoint: Completion deadline (testable) and Branch Fedora 28 from Rawhide (Rawhide becomes future F29) 11:31:18 can we take this milestone as the beginning of our translation sprint? (and be part of the official communications) 11:31:35 jibec: shouldn't the translations be *after* the string freeze? 11:32:02 oups rluzynski, you're right 11:32:11 I meant 2018-03-06 Software Translation Deadline 11:32:28 OK, now it's correct. :) 11:32:38 same date but one month later, it was a mistake :p 11:33:13 so, what do you think about take the branching and change checkpoint as the beginning of our translation sprint? (and be part of the official communications) 11:35:16 well, let's do this as nobody says : it's a bad idea :p 11:35:25 ha ha. Why? 11:35:35 No no, I just don't understand the point. 11:35:36 2 weeks before string freeze is good idea :) 11:35:44 jibec: so you mean 2018-02-20? 11:36:17 yep, and I'll ask the Fedora Release Manager to includes this milestone in official communications 11:36:35 "this milestone"?? 11:36:41 that's Tuesday, is that OK? 11:37:44 otherwise looks good to me. Does not start immediately after the string freeze and does not end immediately before the translation deadline. 11:37:45 well, it's the Fedora rhythm that makes it a Tuesday, I don't see any problem with this 11:38:02 OK :) 11:38:31 by Milestone, I meant: the translation sprint start 11:39:05 got it !! 11:39:40 do someone feel like being the coordinator of this ticket? It means writing/communicating/drafting blog posts, etc. 11:40:30 I listed subtasks inside the ticket, but many may have to be added 11:40:49 ok, next subject, please answer the ticket 11:40:53 #topic #49 Red Hat now have a translation program manager (REHL, not Fedora) 11:41:23 ljanda: would you like to introduce yourself 11:41:25 ? 11:41:26 That looks to be my topic :-) 11:41:47 Hi everybody, hi noriko, my name is Ludek, I am the new l10n PgM for RHEL 11:42:18 The reason why I am here is that it seems to me that a link between RHEL and Fedora localization got broken 11:42:27 hi ljanda, welcome to Fedora l10n meeting !! 11:42:28 hi 11:42:35 hi 11:42:42 hi 11:42:49 hi, that's sounds exciting... 11:43:02 Hi all 11:43:35 My main worry is that our Japanese translations we do in-house can't be pushed to upstream in many cases 11:43:59 Sometimes packagers refuse them saying correctly that they should come through upstream 11:45:07 which is a good behavior, but we need to help to find out a solution :) 11:45:26 (I mean: upstream first) 11:45:47 ljanda: technically it is possible to apply patches downstream. Of course it's better to push upstream first. But if upstream refuses then you have no choice. 11:45:47 The solution is that RH japanese translator joins the community and contribute upstream. 11:46:03 noriko +1 11:46:34 noriko: it also what I told ljanda by email, we need people to interact with and be part of our teams so we work together 11:46:55 Patching downstream might have still a problem 11:47:08 We do apply translations downstream as patches, but there is a risk of regressions and lost translation work 11:47:33 Cz redhat claims it is opensource, and a package can dependent to other package which is fully opensource. 11:48:07 ljanda and noriko: of course I understand this may take time but my point is that it's possible. Difficult but possible. 11:48:30 well, no need to explain to Fedora contributors that upstream first is the general rule to follow 11:48:37 * noriko knew and reminded it hundreds times.... Last year... 11:49:12 At the same time I can't imagine our translators contributing to upstream - too busy and tight RHEL schedules 11:50:09 Can Fedora Japanese translators help to review and push these translation in Fedora Zanata at least? (off course i think depends on language maintainer) 11:50:10 ljanda: it seems to me that contributing upstream takes less time than maintaining downstream patches. 11:50:31 rluzynski: yeah, agree. Maintaining patches is tricky. 11:50:49 I agree too 11:50:53 well, let's close this subject for now 11:50:59 ljanda: please open a ticket on this matter 11:51:07 pravins: I'm afraid this is not about the packages which are in zanata. ljanda: are you talking about the packages in zanata or not in zanata? 11:51:09 so we can discuss it together 11:51:18 jibec: sure !! 11:51:23 ljanda, I recommend to identify the problem of the packagers side. 11:51:25 first 11:51:36 It can narrow down the path. 11:51:44 so, this ticket should includes the points rised by noriko, rluzynski and pravins 11:51:49 Sorry jibec yup 11:51:55 so 11:51:58 noriko: what do you mean to identify the problem of the packagers side"? 11:52:02 yeah, good to Copy paste from long as a start. 11:52:07 ljanda: please stop :) 11:52:14 jibec: okay 11:52:15 we still have a few subjects 11:53:18 first : I do invite L10N contributors to rise any question or problem they currently have related to the RHEL product 11:53:47 for example, I have no idea when are the release and when to translate, so I do not forward any information to the french translation team 11:54:02 again, please open a ticket, and feel free for any kind of question 11:54:09 next subject 11:54:13 #topic #50 The new Fedora wiki homepage needs translation 11:54:29 you may have release our wiki got "improved" 11:54:31 https://fedoraproject.org/wiki/Fedora_Project_Wiki 11:54:40 the design changed, and the first page 11:55:04 do someone feel like adding the translation box and communicating to translator to tell them how to contribute? 11:55:11 it's pretty simple to do :) 11:56:07 do we have a deadline for this? 11:56:12 nope 11:56:25 then I can help 11:56:27 and I will not do it and let it open for any newcomer :p 11:56:37 \o/ 11:56:41 hahah 11:56:55 thank you jonatoni 11:56:58 #topic Open floor 11:57:11 bexelbie: you had something to say about tshirts? 11:57:21 i can finance the shirt locally 11:57:30 bexelbie: these many members not replied to our emails : flavius, aurisc4, rzil, feonsu, ouesten, ricardopinto, lstemmle, tiansworld, mosquito, sujiniku, sewerx, evillagr, laskov, redandrei, ypoyarko 11:57:49 me, jonatoni|m jibec have tried multiple time but no response. :( 11:58:13 pravins, ok. Can you work with kjandova to let her know to make another attempt - we are almost done with the cards and then they go to jibec for signing then we mail 11:58:47 bexelbie: yeah, sure. jonatoni|m in that list, looks you have sent email to more members. 11:59:06 * bexelbie looks to kjandova - who is unfortunately in class right now 11:59:11 lets, cc in those email kjandova and try one more time. That will be easy. 11:59:19 yep sure 11:59:27 we should try to do direct emails to only them 11:59:34 maybe they filter and we tripped a filter 11:59:44 good, any other subject? 11:59:49 jibec: what i meant was I can shoulder the budget for local production of shirts which I can give to local contributors. Do i still need approval of the prints? 12:00:06 fedora logo? or anything? 12:00:13 bexelbie: we did direct email only, so this time we will keep kjandova in CC, so she can follow-up if required. :) 12:00:32 ahh, cool 12:00:43 if we are going to do new shirts 12:00:48 we have a new way to do this that is much easier 12:00:58 we have a company that will manage print runs. We send a coupon code to each person 12:01:08 they go to the vendor website and place an order for a free shirt that meets their needs 12:01:17 this way we just distribute codes and tell people when they need to order by 12:01:20 bexelbie: wow, thats great !! 12:01:21 everyone gets a high quality shirt 12:01:27 much easier :) 12:01:27 aabuke: we already have a tshirt design you may reuse 12:01:37 we can most likely also get them to slipstream a new card for us 12:01:38 bexelbie: what about aabuke question? ^^ 12:01:51 what is the context for aabuke question? 12:02:04 and if you pay for it, there is no request to write I assume, just open a ticket in g11n tracker so we can send you the appropriate link 12:02:12 * pravins leaving for now. Thanks jibec for hosting this very active meeting !! 12:02:16 with the tshirt design 12:02:25 thanks! 12:02:25 #topic Next meeting 12:02:26 i wanted to know if there is an interest in translating developer docs in general, parts that are not included in the official fedora documentation. what is the investment to transfer this stuff @zanata? it is next to git (for me as translator) an issue to find reviewers for this. it makes things more complicate. my personal impression 12:02:32 #topic Open floor 12:02:34 if we ar eprinting t-shirts, we should pay for them and ensure quality 12:02:38 I have a simple question related with my current open source contribution: does anybody have this issue in their native language that the dates are formatted incorrectly in Fedora because the month name should be in a genitive case (or any other special case) which is currently not supported? 12:02:53 okay, please stop all :) 12:02:57 tshirt subject is close 12:02:59 lol 12:03:05 semanticdesign question first 12:03:38 most of the time, dev content is not translated, as upstream don't feel the need to do it 12:03:56 the general rule for Fedora apps is the same, contributor tools are not translated for the same reason 12:03:59 * jonatoni needs to go. 12:04:16 this doesn't mean it is impossible, it just depends on the will of the upstream project 12:04:30 semanticdesign: does it answer? (need to close this meeting) 12:04:42 so this is more a finger exercise for me if they are not willing to publish translation 12:04:53 yep 12:04:59 okay answered 12:05:18 rluzynski's question now, do someone had the same issue? (I did not) 12:05:47 most probably the answer to my question is "nobody here" but just in case. So let's consider it answered. 12:05:53 ok 12:05:57 #topic Next meeting 12:06:03 I should do it in a month or so 12:06:20 please remember to stop by our mailing list or issue tracker and finish tasks :p 12:06:28 thank you everyone 12:06:31 #endmeeting