Monday, 2018-11-19

*** tosky has quit IRC00:49
*** jamesmcarthur has joined #openstack-i18n00:59
*** jamesmcarthur has quit IRC01:04
*** jamesmcarthur has joined #openstack-i18n01:23
*** eumel8 has quit IRC01:49
*** jamesmcarthur has quit IRC02:16
*** jamesmcarthur has joined #openstack-i18n02:54
*** jamesmcarthur has quit IRC03:03
*** jamesmcarthur has joined #openstack-i18n04:59
*** adiantum has joined #openstack-i18n06:53
*** pcaruana has joined #openstack-i18n07:24
*** hberaud has joined #openstack-i18n07:56
*** adiantum has quit IRC08:16
*** eumel8 has joined #openstack-i18n08:16
*** adiantum has joined #openstack-i18n08:46
*** rsimai has joined #openstack-i18n08:48
*** tosky has joined #openstack-i18n08:50
*** jpich has joined #openstack-i18n09:17
*** adiantum has quit IRC09:24
*** adiantum has joined #openstack-i18n09:27
jpicheumel8: Happy to move back to a more formal type of meeting at last? :-)09:33
eumel8jpich: Office Hour didn't worked a expected, from my point of view09:36
jpicheumel8: I agree on your point about the empty sessions. It was good to give it a shot anyway :)09:37
eumel8jpich: Yeah, maybe we will get some downstream people now in09:37
jpichWe're reverting back to how it used to be so I'd expect it will be the same as before?09:38
eumel8jpich: that's a bit philosophical ;)09:57
eumel8btw: I've started a Blueprint for Zanata Replacement: https://blueprints.launchpad.net/openstack-i18n/+spec/renew-translation-platform09:58
*** adiantum has quit IRC10:04
*** adiantum has joined #openstack-i18n10:07
*** adiantum has quit IRC10:07
jpicheumel8: Ah, thank you for the link, I will follow. There was a lot of efforts internally to find a new home for it but that was before the IBM news, no updates since that. I'll let you know should I hear anything...10:15
eumel8jpich: ok, thanks for the update. I would stay with Zanata, but when the developer left, there is not the best future. So we should be prepared10:26
jpicheumel8: I agree. Your blueprint gives me a good stepping stone to start following up with people :)10:26
eumel8jpich: you're welcome. There were also a lot of Australian guys in Berlin and they had also some ideas10:27
eumel8beside Zanata10:28
jpicheumel8: In case that helps, those whre the results of the testing between Pootle and Zanata last time around (I don't recall if you were here), it was recorded it an etherpad http://lists.openstack.org/pipermail/openstack-i18n/2014-October/000828.html . Pootle had some issues with python tooling, it would be good to see if this has been resolved since it's on your list as well10:30
jpichAre the ideas you mention, the ones listed on the blueprint?10:32
eumel8jpich: yeah, I installed Pootle, which looks good but not perfect. It's Open Source.10:34
jpichYeah I understand it was the main other contender last time10:34
jpichhttps://etherpad.openstack.org/p/translation-tools-comparation10:34
eumel8jpich: the other idea should be  RedHat internal AI project, what I understood10:35
jpichHm... Ok I'm not familiar with that, that sounds a bit too generic to be used as a translation platform?10:35
eumel8jpich: it was with machine translation but I have no more details. The RedHat guys in the same building like Zanata guys working on it.10:37
eumel8but no glue if that will be Open Source or a new product10:37
jpicheumel8: Ok. It sounds more like a nice addition to a translation platform than something that knows how to handle po files TM etc to me but I really haven't heard about it :)10:38
jpichcommunity moved away from transifex because it was no longer open-source so mystery project probably won't make the list till it's clearer anyway. I'll poke at your list of links as well10:41
jpichThough I'm still hoping I get happy news to share and none of that is necessary, at some point :)10:42
eumel8jpich: yeah, thanks for the links so far :)10:54
jpich:)10:54
jpicheumel8: For your list, Mozilla has a translation platform as well though it seems to be mostly a one person project, pontoon https://pontoon.mozilla.org/ https://github.com/mozilla/pontoon/10:58
jpicheumel8: Also you might want to add a year beside the "previous activities" etherpad so it's clearer how out of date the info might be :)10:58
*** tosky has quit IRC11:03
*** tosky has joined #openstack-i18n11:06
eumel8jpich: done, thx11:17
jpichCool :)11:18
amotokiwhat is the difference between meeting and office hour?11:25
amotokiwe didn't change the meeting/office hour time and just moved the channel which the meetings are held.11:25
amotokiI support the idea of merging docs and i18n meetings into one hour11:26
jpichI think a stronger agenda and easier to cancel if there is no topic, to avoid people showing up and nothing happening for an hour?11:26
amotokiAh, nice point. office hours happen in project-specific channel, so it affects little for other projects.11:27
amotokiMy case is a bit different and completely due to my recent schedule. 7UTC means 4pm in Japan and it conflicts my weekly team meeting..  For the other timeslot (IIRC 10pm or 11pm in JST), I tend to schedule my party or meetup on Thu to avoid schedule conflicts.11:36
amotokieumel8: regarding the platform switch, we also need to clarify the behavior of branch merge around OpenStack release. When we switched to Zanata, we explored the Zanata behavior on how translations in a release branch will be able to be merged into the master branch.11:39
amotokieumel8: it could not be achieved from Zanata upstream developers to clarify the detail behavior.11:39
* jpich still crossing fingers a platform switch won't be necessary11:40
amotokiwe need to re-establish the whole process with the translation platform if we really switch it :(11:41
amotokiIn addition, it requires language coordinators to get familiar with the new process/behavior to answer questions from local translators. I am not sure how it can be done...11:43
-amotoki- doesn't think he can play such role in ja team at the moment11:44
eumel8amotoki: I know it's a lot of work for the platform change, but on the other hand we operate an un-maintained piece of software.11:51
jpichWhat we have works for now so there shouldn't be any immediate need for migrating. It's "just in case" investigating for now11:52
eumel8amotoki:  as jpich mentioned is team meeting a bit more official like  an office hour. Would 8:00 UTC fits for you? Might be a conflict for me in CEST11:53
eumel8the late hours we need for US docs team member but it shouldn't be too late from UTC11:53
eumel8jpich: yeah, "be prepared" and looking a bit forward to some future feature like MT11:54
amotokieumel8: unfortunately 800UTC does not work either. My i18n work is completely private, so most from working hours do not work for me.12:15
eumel8amotoki: the same for me. you can add more time proposal to the e-mail. But I wouldn't spend too much effort in that team meeting thing.12:19
amotokieumel8: Is a day other than Thu considered? I have late time meeting (around 11pm or 12pm) on Tue, Wed and Fri, so Thu is the day I avoid.12:21
amotokiI can follow meeting logs :)12:22
eumel8amotoki: understandable. They day is not fix, beside Mo, Tue, Wed, and Fri ;)12:27
eumel8ianychoi: question was last week during Summit: is that page still valid: https://wiki.openstack.org/wiki/Translations/Infrastructure ? Otherwise I would remove it + the parrent page. I think the content is on the I18n guide.13:36
*** openstackgerrit has joined #openstack-i18n13:51
openstackgerritMerged openstack/i18n master: Update infra URLs for Zanata scripts  https://review.openstack.org/61811313:51
openstackgerritFrank Kloeker proposed openstack/i18n master: Point PTL guide to the new openstack-discuss ML  https://review.openstack.org/61875714:09
ianychoieumel8, I already moved most content to I18n guide - How look my addition of a caution message on that wiki?16:07
*** pcaruana has quit IRC16:07
eumel8ianychoi: would be nice! I wasn't aware of this page16:08
ianychoiI have seen some better format on other OpenStack wiki pages but I simply copied & pasted a basic syntax from mediawiki site..16:08
ianychoiAnd I like idea on seeking new tools instead of Zanata, but I think we can ask to Zanata team. For example, zanata-users mailing list still works: https://www.redhat.com/archives/zanata-users/2018-November/date.html -> Carlos responds :)16:15
eumel8ianychoi: I know, talked to his colleagues in Berlin. But it's another department. There is no Zanata developement anymore and what I talked ealier the day: we should be prepared16:18
*** jamesmcarthur has quit IRC16:32
*** jamesmcarthur has joined #openstack-i18n16:32
*** itlinux has joined #openstack-i18n17:12
*** pcaruana has joined #openstack-i18n17:44
*** jamesmcarthur has quit IRC17:44
*** jpich has quit IRC17:49
*** jamesmcarthur has joined #openstack-i18n18:15
*** adiantum has joined #openstack-i18n19:33
*** adiantum has quit IRC19:53
*** adiantum has joined #openstack-i18n20:05
*** jamesmcarthur has quit IRC20:13
*** jamesmcarthur has joined #openstack-i18n20:13
*** jamesmcarthur has quit IRC21:02
*** jamesmcarthur has joined #openstack-i18n21:08
*** jamesmcarthur has quit IRC21:16
*** pcaruana has quit IRC21:51
*** adiantum has quit IRC21:52
*** dayou_ has joined #openstack-i18n22:37
*** dayou has quit IRC22:39
*** jamesmcarthur has joined #openstack-i18n23:16
*** jamesmcarthur has quit IRC23:21
*** jamesmcarthur has joined #openstack-i18n23:55

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