| *** Daisy has joined #openstack-i18n | 01:28 | |
| *** epico has joined #openstack-i18n | 02:05 | |
| *** epico has quit IRC | 02:08 | |
| *** Daisy has quit IRC | 03:32 | |
| *** ykatabam has quit IRC | 04:01 | |
| *** ykatabam has joined #openstack-i18n | 04:34 | |
| *** Daisy has joined #openstack-i18n | 05:10 | |
| *** epico has joined #openstack-i18n | 05:19 | |
| *** chandankumar has joined #openstack-i18n | 05:34 | |
| *** ykatabam has quit IRC | 05:54 | |
| *** Daisy has quit IRC | 06:01 | |
| *** iranzo has joined #openstack-i18n | 06:36 | |
| *** ykatabam has joined #openstack-i18n | 06:53 | |
| *** ykatabam1 has joined #openstack-i18n | 07:40 | |
| *** Daisy has joined #openstack-i18n | 07:40 | |
| *** DuncanT has quit IRC | 07:41 | |
| *** ykatabam has quit IRC | 07:42 | |
| *** ykatabam1 has quit IRC | 07:45 | |
| *** ykatabam has joined #openstack-i18n | 07:45 | |
| *** chandankumar has quit IRC | 07:59 | |
| *** Daisy has quit IRC | 08:09 | |
| *** ygbo has joined #openstack-i18n | 08:17 | |
| *** DuncanT has joined #openstack-i18n | 08:18 | |
| *** mariantb has joined #openstack-i18n | 09:36 | |
| *** mariantb has quit IRC | 09:49 | |
| *** chandankumar has joined #openstack-i18n | 09:58 | |
| *** epico has quit IRC | 10:05 | |
| *** doug-fish has joined #openstack-i18n | 11:09 | |
| *** ykatabam has left #openstack-i18n | 12:22 | |
| *** doug-fish has quit IRC | 12:23 | |
| *** doug-fish has joined #openstack-i18n | 12:25 | |
| *** doug-fish has quit IRC | 12:30 | |
| *** doug-fish has joined #openstack-i18n | 12:45 | |
| *** chandankumar has quit IRC | 13:05 | |
| *** Daisy has joined #openstack-i18n | 13:42 | |
| *** doug-fis_ has joined #openstack-i18n | 13:47 | |
| *** doug-fish has quit IRC | 13:50 | |
| *** doug-fish has joined #openstack-i18n | 13:51 | |
| *** doug-fis_ has quit IRC | 13:52 | |
| *** amotoki has joined #openstack-i18n | 13:53 | |
| *** doug-fish has quit IRC | 14:14 | |
| *** doug-fish has joined #openstack-i18n | 14:15 | |
| amotoki | doug-fish: ping | 15:00 |
|---|---|---|
| doug-fish | hi amotoki | 15:01 |
| amotoki | doug-fish: hi. As you may already know, it seems some IBM translations were uploaded into master branches. | 15:01 |
| amotoki | doug-fish: have you already been aware of it? | 15:01 |
| doug-fish | amotoki: no - that's actually a surprise and concern to me | 15:02 |
| doug-fish | do you know of a specific instance? | 15:02 |
| amotoki | doug-fish: I just checked neutron translation and the master branch was changed too. | 15:02 |
| *** doug-fish has quit IRC | 15:03 | |
| *** doug-fish has joined #openstack-i18n | 15:03 | |
| amotoki | doug-fish: if you go to https://translate.openstack.org/iteration/view/nova/master/languages/ja, the progress of "nova" suddenly become up to 90%. it was under 50% a few days ago. | 15:04 |
| doug-fish | amotoki: sorry back in 5 minutes I have to change to a different location | 15:04 |
| *** doug-fish has quit IRC | 15:04 | |
| amotoki | doug-fish: no worries. | 15:05 |
| *** doug-fish has joined #openstack-i18n | 15:05 | |
| *** doug-fish has quit IRC | 15:06 | |
| *** doug-fish has joined #openstack-i18n | 15:06 | |
| Daisy | amotoki, doug-fish: it's a kind of copy. I still don't know who triggered the copy. | 15:08 |
| Daisy | If you look into the history, it is said: | 15:08 |
| Daisy | Copy translation: translation copied from project 'neutron', version 'ibm-translation-for-review', document 'neutron', author 'Lucas Palm' | 15:08 |
| amotoki | Daisy: I see it too. Copy translation: translation copied from project 'nova', version 'ibm-translation-for-review', document 'nova', author 'Tom Cocozzello' | 15:09 |
| Daisy | Who copied ? | 15:09 |
| Daisy | That's my question. | 15:09 |
| Daisy | While I did test in the test server, I didn't meet with this situation. | 15:09 |
| amotoki | Daisy: automatically or manually? | 15:09 |
| Daisy | I don't know | 15:10 |
| amotoki | Daisy: trying to check the timestamp | 15:10 |
| Daisy | If you look into the test server: Copy translation: translation copied from project 'neutron', version 'ibm-translation-for-review', document 'neutron', author 'Lucas Palm' | 15:10 |
| Daisy | sorry | 15:10 |
| Daisy | if you look into the test server: https://translate-dev.openstack.org/project/view/nova | 15:10 |
| Daisy | master percentage is far less that IBM versions. | 15:11 |
| Daisy | percentage of master is far less than IBM versions. | 15:11 |
| Daisy | If auto copy happened in test server, the percentage will be similiar. | 15:11 |
| Daisy | So I doubt in production server, it's a manually copy. | 15:12 |
| Daisy | My question is who has the right to execute "copy" action | 15:13 |
| amotoki | I checked more than 10 strings in Japanese nova tranasltions in master. All of them has the same minute 22:53 2015/09/15.. | 15:14 |
| amotoki | My one concern on unreviewed translating server side in Liberty is https://bugs.launchpad.net/horizon/+bug/1406333 | 15:15 |
| openstack | Launchpad bug 1406333 in OpenStack Dashboard (Horizon) "LOG messages localized, shouldn't be" [High,In progress] - Assigned to Sam Betts (sambetts) | 15:15 |
| amotoki | it is not a new topic but if we have a good progress in server side projects, more operators may hit this problem. | 15:15 |
| doug-fish | amotoki: could you share an example id of the Japanese nova translations with timestamp 22:53 2015/09/15? | 15:16 |
| Daisy | Doug's team didn't contribute log messages. | 15:17 |
| doug-fish | Daisy: yes, that's true | 15:17 |
| doug-fish | however, we don't really have any way to stop a tnanslator from doing that | 15:17 |
| doug-fish | it would be nice if a review were required before such a string even got into Horizon | 15:18 |
| Daisy | another possible reason is that the configuration is different in test server and production server. | 15:18 |
| amotoki | where can I get ID? | 15:18 |
| doug-fish | I mean the english string that the translation is based on | 15:19 |
| doug-fish | the source | 15:19 |
| amotoki | doug-fish: ah.. I just found Resource ID by clicking a star mark around source string. | 15:20 |
| amotoki | doug-fish: some examples from nova: 72b170951c472e7d3b3864a0f46ba88c a703a40925ee1d49a0c737412c4adffd 05baa14831e7c22c55903109b02bb436 | 15:21 |
| amotoki | doug-fish: if you need a right to access japanese translations, please let me know. | 15:21 |
| doug-fish | amotoki: I can view them now - thanks! | 15:21 |
| doug-fish | and it's probably best if I don't have access to actually translate! | 15:22 |
| doug-fish | Now I'm looking at the Japanese translation of "Insufficient compute resources: %(reason)s." which is resource-id 72b170951c472e7d3b3864a0f46ba88c ... | 15:23 |
| doug-fish | I'm not sure how to view the history of that translation | 15:23 |
| doug-fish | amotoki: Daisy can you share how to view the history? | 15:24 |
| amotoki | to view a history, can see an icon of a clock around translated string? | 15:24 |
| doug-fish | I don't see that icon | 15:25 |
| doug-fish | perhaps I have to be a member of the language team to see it? | 15:25 |
| doug-fish | oh I know - let me look for that in another language | 15:25 |
| Daisy | I think I know. | 15:25 |
| doug-fish | yes - I can see the clock icon for languages of which I am a translator | 15:26 |
| Daisy | amotoki: I wonder if you could check in Jenkins, when the auto jobs executed to upload pot files ? | 15:27 |
| doug-fish | pleia2: have you been asked about this or following the discussion? | 15:27 |
| doug-fish | Daisy: amotoki, stepping back a little ... does this seem to be a problem with only the ja nova translation? or have other languages and projects been affected as well? | 15:28 |
| amotoki | Daisy: what do you mean? | 15:28 |
| Daisy | From the help document, it is said that: This process is repeated for each text flow in the uploaded document. | 15:28 |
| Daisy | I wonder if a new upload pot action trigged the copy. | 15:28 |
| Daisy | http://docs.zanata.org/en/latest/user-guide/translation-reuse/copy-trans/ | 15:29 |
| Daisy | Copy Trans usually runs automatically when a document is uploaded using the cli-client. | 15:29 |
| Daisy | You can also run Copy Trans manually against a project version. | 15:29 |
| amotoki | doug-fish: it is not limited to ja nova. see https://review.openstack.org/#/c/225557/ for neutron (for all langs) | 15:29 |
| Daisy | The Copy Trans Options for the project are used in this case. | 15:29 |
| Daisy | Not limited to project and langauges. | 15:30 |
| Daisy | If Don't Copy is selected for all conditions, a string must have matching content, a matching ID, be from the same project, and be from a document with the same name and path, otherwise it will not be reused | 15:32 |
| Daisy | The current settings in Zanata is "Don't Copy is selected for all conditions" | 15:32 |
| Daisy | So when a new pot file is uploaded, a string with matching content, matching ID, from a same project, from a same document, is copied. | 15:33 |
| doug-fish | I'm confused about why we are seeing this different behavior on the production and development servers | 15:34 |
| doug-fish | Daisy: are you saying you think the settings are different for production? | 15:34 |
| Daisy | because there is no auto jobs running for test server. | 15:34 |
| doug-fish | *thinking* | 15:35 |
| Daisy | doug-fish: No, the settings are same. The differences are the auto jobs. Auto jobs are for the production server. | 15:35 |
| Daisy | Auto jobs will use CLI to upload pot files to production server, but there is no such jobs for the test server. | 15:35 |
| doug-fish | Daisy: did you say there was a specific auto job you were suspicious of? | 15:36 |
| doug-fish | I'm not aware of one that should affect this | 15:36 |
| Daisy | there are a serials of jobs in Jenkins to update pot files in the production server automatically when the pot files are changed in the code repo. | 15:37 |
| amotoki | doug-fish: what Daisy is talking about is a job to upload a new pot file using CLI. | 15:37 |
| Daisy | a new version of pot | 15:37 |
| amotoki | thanks for the correction. | 15:37 |
| doug-fish | right - I understand that part | 15:37 |
| doug-fish | but it's not clear to me that connection between upload an updated POT and merging in translations from a separate Zanata branch | 15:38 |
| Daisy | how do we roll back ? I don't have any ideas in mind. | 15:40 |
| Daisy | I have a wood head now. | 15:40 |
| doug-fish | :-) I've never heard that expression before, but I completely understand it! | 15:41 |
| doug-fish | Tom and Lucas probably have copies of the PO files that existed before we did the upload | 15:41 |
| Daisy | I think it has no relationship with Tom and Lucas. | 15:42 |
| amotoki | i have no good idea too. | 15:42 |
| Daisy | They get the latest po files, adding IBM translations when it's empty. | 15:43 |
| Daisy | And then upload to a separate branch. | 15:43 |
| Daisy | I didn't know uploading pot file will cause the copy action. | 15:43 |
| doug-fish | Daisy: right - I think we are all surprised by that | 15:43 |
| doug-fish | what would have happened if there were multiple proposed branches | 15:44 |
| amotoki | Daisy: we all are surprised | 15:44 |
| Daisy | no, updating pot file by CLI | 15:44 |
| amotoki | I think Zanata has an assumption that a same string can be used for all branches, and branches tend to have different source strings. | 15:44 |
| amotoki | it is mainly for different source branches in upstream projects: master, stable/xxxx in openstack. | 15:45 |
| amotoki | I think there are two possible options: (1) to just keep the current situation and encourage language team to review master branch, or | 15:46 |
| doug-fish | oooh - so what you are saying is that when the automatic jobs uploaded the POT files using the command line, Zanata took translations from all of the branches as updates? | 15:46 |
| amotoki | (2) to revert transaltions of a few days ago (we can extract some older versions of translations from git) | 15:47 |
| Daisy | doug-fish: you get it. | 15:47 |
| Daisy | amotoki: (2) how to revert ? | 15:48 |
| doug-fish | amotoki: I have the impression that the Japanese translations were the least well received | 15:48 |
| doug-fish | (2) is why I mentioned Tom and Lucas - I think they will have PO files from the community sitting around from when they started the update process | 15:48 |
| amotoki | doug-fish: it is just an example. I don't want to talk about only a specific language. | 15:49 |
| amotoki | Daisy: we can extract an older version of translations from openstack project git repo and upload PO files to Zanata manually. | 15:49 |
| amotoki | Daisy: it is what in my mind for option (2). I am not sure it works or not. | 15:50 |
| amotoki | because we may lose some translations. | 15:50 |
| Daisy | yes, that's the risk. | 15:50 |
| Daisy | and, manually...I don't like manually uploading po files. | 15:51 |
| Daisy | to 9 projects and 10 langauges. | 15:52 |
| Daisy | I think I prefer (1) | 15:53 |
| Daisy | If we want to recover, surely we could recover, either from the old version of po files, or manually reject TOm and Lucas translations. | 15:54 |
| Daisy | The question is whether it is valuable. Tom and Lucas translations are only to fill the blanks, and no log messages. | 15:55 |
| amotoki | I am okay with option (1). Improving existing translations is easier than translating from scratch. | 15:56 |
| Daisy | Thank you for the support, amotoki. It's a hard situation for me. | 15:56 |
| Daisy | I didn't expect that would happen. | 15:57 |
| amotoki | Daisy: thanks for your hard work on Zanata migration. it is not your fault of course. thanks anyway. | 15:57 |
| Daisy | So I will write to ML, explain the situation, and ask them to review master branch. | 15:58 |
| Daisy | If some coordinators don't like the translations at all, I could manually recover for them. | 15:58 |
| amotoki | Daisy: thanks for coming announce. | 15:59 |
| *** AJaeger has joined #openstack-i18n | 16:01 | |
| *** rsimai is now known as rsimai_away | 16:02 | |
| doug-fish | Daisy: amotoki thanks for your hard work and diligence in sorting this out | 16:03 |
| amotoki | Daisy: doug-fish: question on how each language team can communicate with IBM translators. I think each lang team need to discuss translation guidelines or some other topics. | 16:04 |
| *** ygbo has quit IRC | 16:04 | |
| amotoki | I hope some more information is provided on the i18n list. | 16:05 |
| clarkb | Daisy: I will update my changes based on your feedback and hope to have them merged this week well ahead of the october deadline. Also if we really need to we can do a manual push | 16:10 |
| Daisy | Thank you, clarkb. | 16:10 |
| Daisy | :) | 16:10 |
| Daisy | clarkb: did you notice IBM translations were copied into master version automatically ? | 16:11 |
| clarkb | I hadn't, still catching up on email | 16:11 |
| Daisy | ok... | 16:11 |
| Daisy | The Copy Trans is trigged by the uploading pot files by CLI. | 16:12 |
| clarkb | So even though we pushed to a different version because the source strings are identical Zanata copied them over? | 16:12 |
| clarkb | that sounds like a good optimization but maybe should be off by default? | 16:12 |
| clarkb | Daisy: have we asked Zanata about that yet? | 16:13 |
| Daisy | what do you mean ? | 16:13 |
| clarkb | have we asked them if that behavior is configurable or do we know if it is? | 16:13 |
| clarkb | I am just thinking that it may be a good idea to not have it copy translations by default if the source strings are identical since in theory different versions could have different glossaries and terms and conventions | 16:14 |
| Daisy | I read their help, I think we are not configure it. Currently, we have configured "not copy" to all the situations. | 16:14 |
| Daisy | a way to avoid "copy" is to mark the uploading translations for review in "fuzzy" | 16:15 |
| Daisy | But I don't know how to force the contributors to mark their translations as "fuzzy". So I don't think it's a good idea. | 16:15 |
| clarkb | I see the link you posted now, reading it to catch up | 16:15 |
| doug-fish | Daisy: I have a separate question for you (I hope you don't mind 2 discussions at the same time!) ... do you expect the nova translations are complete now? | 16:16 |
| Daisy | I agree disable copy by default is a right action. | 16:16 |
| AJaeger | clark, Daisy: Let's discuss with Zanata developers, please. | 16:17 |
| clarkb | Daisy: so right now we are set to "Don't Copy" for all the criteria? | 16:17 |
| Daisy | clarkb: Yes, we did. | 16:17 |
| doug-fish | I think they are planning an rc1 this week and don't expect further release canidates | 16:17 |
| doug-fish | no I'm not sure how they'd receive any nova translations that happen after Thursday | 16:17 |
| clarkb | Daisy: maybe what Zanata needs is another criteria that is "From different Versions" that we can set to Don't Copy | 16:17 |
| AJaeger | doug-fish: translations got imported today | 16:17 |
| Daisy | doug-fish: what do you mean ? I think there will be a rc for translations importing. | 16:17 |
| clarkb | Daisy: do you think that would solve the problem? | 16:17 |
| Daisy | clarkb: Yes, clarkb. | 16:18 |
| clarkb | Daisy: do you want to file that featuer request or should I? but we should do that so that in the future we can avoid this problem | 16:18 |
| Daisy | I could do that, clarkb. | 16:18 |
| clarkb | as for how to deal with this right now, I am not entirely sure. You can probably work off of the diffs to determine what cleanup needs to happen | 16:18 |
| clarkb | AJaeger: ^ doyou have ideas on that? | 16:19 |
| *** chandankumar has joined #openstack-i18n | 16:19 | |
| clarkb | Daisy: also maybe a featuer to turn off the automatic copy trans run and make it manual only? | 16:19 |
| AJaeger | clarkb: I have no ideas ;( StevenK might but he's not around. | 16:19 |
| Daisy | clarkb: I plan to ask translators to review in master branch. It could easily find IBM contributions by some search criteria. | 16:20 |
| doug-fish | Daisy: I mean the Horizon team will have an rc1 this week just like Nova - but the Horizon team expect to have an rc2 with translations in it - I'm not sure our nova friends are planning on that ... johnthetubaguy maybe you know? | 16:20 |
| AJaeger | Daisy: The nice thing is that copy-trans merged in the IBM translations without overwriting the others. | 16:21 |
| Daisy | doug-fish: I know johnthetubaguy. I have close work with him. He understand. | 16:21 |
| clarkb | AJaeger: ya it only looks to copy for untranslated items | 16:21 |
| AJaeger | The bad thing is: No review was done and no good way to track it... | 16:21 |
| clarkb | http://docs.zanata.org/en/latest/user-guide/translation-reuse/copy-trans/ is the doc Daisy linked on the email thread | 16:21 |
| doug-fish | Daisy: johnthetubaguy this was a surprised to some of my nova coworkers. As long as there is a plan to handle this I have no further concerns. | 16:22 |
| johnthetubaguy | sorry, which bit was a surprise? | 16:22 |
| Daisy | AJaeger: The worse thing for me, is that the process for contributing translations in batch is broken. Currently, the tool set cannot suport the process well. | 16:22 |
| doug-fish | johnthetubaguy: the surprise is that translations for nova will be arriving after your rc1 | 16:23 |
| doug-fish | so hopefully the rc2 will not be a surprise | 16:23 |
| johnthetubaguy | oh, thats fine | 16:23 |
| clarkb | cutting an RC for translations should be very low risk | 16:24 |
| johnthetubaguy | let me add more to the meeting notes for the next meeting | 16:24 |
| doug-fish | johnthetubaguy: perfect! thanks! | 16:24 |
| johnthetubaguy | doug-fish: no problem, added it here: https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting | 16:25 |
| johnthetubaguy | doug-fish: I thought that was covered in the ML post about the string freeze, but its easy to miss, so happy to shout a few more places about that :) | 16:26 |
| AJaeger | clarkb: zanata-cli has the option --copy-trans which we can set to false to disable the copy-trans | 16:26 |
| AJaeger | doug-fish: The translations have been imported for nova already! | 16:27 |
| clarkb | AJaeger: we can enforce that in our jobs easily but harder to enforce for other people pushing docs up | 16:27 |
| clarkb | AJaeger: in this case I think just pushing the proposed translations to a new version would trigger copy trans? | 16:27 |
| AJaeger | clarkb: indeed | 16:27 |
| clarkb | AJaeger: probably a good thing to do in our jobs anyways and maybe that is why they run long? | 16:28 |
| AJaeger | clarkb: I think it works when uploading of *source* files. | 16:28 |
| clarkb | AJaeger: were you still planning on pushing patches for the upstream job condensing? | 16:28 |
| AJaeger | Translators would not upload source files, that's only the tools | 16:28 |
| clarkb | AJaeger: oh is it just source files? | 16:28 |
| clarkb | in that case we should definitel add that to our jobs | 16:29 |
| AJaeger | clarkb: my guess - not completely sure. | 16:29 |
| clarkb | AJaeger: "Copy Trans usually runs automatically when a document is uploaded using the cli-client." is what the doc says | 16:29 |
| clarkb | so thats not super clear but seems to leave the door open to other files | 16:29 |
| AJaeger | clarkb: yeah ;( | 16:29 |
| AJaeger | clarkb: Just send https://review.openstack.org/226398 | 16:29 |
| AJaeger | ". The Copy Trans Options for the project are used in this case. " | 16:29 |
| clarkb | AJaeger: woot thanks | 16:29 |
| AJaeger | What copy trans options can we configure? | 16:30 |
| clarkb | AJaeger: the list is at http://docs.zanata.org/en/latest/user-guide/translation-reuse/copy-trans/ and all are set to Don't Copy already according to Daisy | 16:30 |
| clarkb | the problem is that there is no way to say "don't copy if this comes from a different version" which I think is a good idea | 16:31 |
| AJaeger | https://translate.openstack.org/project/view/ceilometer/settings/translation has these options... | 16:31 |
| AJaeger | clarkb: indeed. | 16:31 |
| Daisy | AJaeger: If Don't Copy is selected for all conditions, a string must have matching content, a matching ID, be from the same project, and be from a document with the same name and path, otherwise it will not be reused. | 16:31 |
| clarkb | Daisy: and in the case of kilo -> liberty or multiple liberty versions many strings will match all those criteria | 16:32 |
| Daisy | clarkb: Yes, in a same project, it's easily to match these criteria. | 16:32 |
| AJaeger | clarkb: should we push https://review.openstack.org/225966 in and then add the disable-copy-trans option? | 16:33 |
| doug-fish | *steps away for a quick lunch* | 16:33 |
| AJaeger | Daisy, clarkb: But what's the proper way forward? I would assume it's really beneficial if strings get copied directly. | 16:34 |
| AJaeger | That speeds up translation work, doesn't it? And gives consistency. | 16:34 |
| clarkb | AJaeger: I think the way forward is to only do manual copy trans | 16:34 |
| clarkb | at least until we are better equipped to deal with it? | 16:34 |
| Daisy | Agree, clarkb. | 16:34 |
| AJaeger | clarkb, Daisy: Why don't we want it in any case? | 16:35 |
| clarkb | AJaeger: but I agree copying where it makes sense is a huge time saver | 16:35 |
| clarkb | AJaeger: I think because multiple versions can have completely different conventions and terminology | 16:35 |
| AJaeger | If I translate a string in heat,wouldn't it be cool if the same string appears in ceilometer and get's translated the same there automatically? | 16:35 |
| clarkb | AJaeger: so you don't want to inadverdently mix in different terminology and conventions? but I defer to the translators here | 16:35 |
| AJaeger | clarkb: I don't. | 16:35 |
| AJaeger | clarkb: We can switch off copy-trans for now but this is something that indeed the whole team needs to discuss some more. | 16:36 |
| Daisy | AJaeger: The situation you described could be blocked by our current settings. We have set "not copy" on project mismatch. | 16:36 |
| AJaeger | Daisy: I know. I just wonder what would be best for us. The IBM situation is one problem... | 16:36 |
| AJaeger | Need to read my kids a good-night story, will be back later... | 16:37 |
| Daisy | Actually, I think the biggest issue in Zanata is that it treat approved translation and translated translation same. | 16:37 |
| Daisy | ok, AJaeger. After writing a email, I will go to sleep then. | 16:38 |
| AJaeger | good night, Daisy! | 16:38 |
| AJaeger | clarkb: what about https://review.openstack.org/225966? Shall we ask fungi for review? | 16:38 |
| AJaeger | clarkb: ah, pleia2 just approved it. | 16:39 |
| * AJaeger now really needs to step out | 16:39 | |
| pleia2 | o/ | 16:39 |
| clarkb | AJaeger: good night, enjoy | 16:40 |
| * clarkb has recently discovered the joys of reading to his children before bed | 16:41 | |
| AJaeger | clarkb: I'll be back - it's sleep time for Daisy ;) | 16:41 |
| AJaeger | clarkb: glad to hear | 16:42 |
| AJaeger | clarkb: The copy trans from the IBM branch explains why upstream jobs took ages this morning - see my email from 12 hours ago... | 16:56 |
| clarkb | AJaeger: ya so I Think we can disable it in the jobs for now to avoid that | 16:57 |
| clarkb | then work on a plan to enable it in a way that makes sense. Maybe we trigger it out of bad? | 16:57 |
| clarkb | er out of band | 16:57 |
| AJaeger | clarkb: https://review.openstack.org/226427 to disable it... | 16:59 |
| AJaeger | clarkb: let's wait for Daisy's email and discussion on what's the best way to do it. | 16:59 |
| clarkb | pleia2: ^ want to review that really quickly? | 17:00 |
| pleia2 | sure | 17:00 |
| AJaeger | clarkb: The IBM translations had many new strings, that's why it took so long this morning (28 minutes in one case). Normally copy-trans should be really quick... | 17:00 |
| pleia2 | oh yes, good | 17:00 |
| Daisy | You want to discuss: how to disable the auto copy ? | 17:01 |
| pleia2 | btw, I'm out of the office tomorrow (another holiday, but then no more holidays!) | 17:01 |
| Daisy | AJaeger: You want to discuss what's the best way to disable the auto copy? | 17:02 |
| AJaeger | Daisy: no, I want to discuss whether translators want the auto copy at all. | 17:04 |
| AJaeger | And then we can discuss how to implement it | 17:04 |
| Daisy | ok. Got it. | 17:04 |
| AJaeger | Daisy: We disabled the autocopy for now at upload with my change. We can always revert or change. | 17:04 |
| AJaeger | But at least the band-aid is in in case further IBM translations get uploaded ;) | 17:04 |
| Daisy | Great, the autocopy could be disabled by scripts ? That's a wonderful way. | 17:05 |
| Daisy | Thank you, clarkb and AJaeger. | 17:05 |
| clarkb | Daisy: if anyone else pushes docs that way they will alos need to set the flag | 17:06 |
| Daisy | AJaeger: do you want to initiate a mail thread in i18n ? or you want me to do that ? If me, I will do it tomorrow. | 17:06 |
| clarkb | Daisy: so this just disables it for when our jenkins jobs run (which should be the majority) | 17:06 |
| AJaeger | Daisy: I can write it... | 17:06 |
| Daisy | Thank you, AJaeger. It's 1am for me. My head is not clear. :) | 17:07 |
| Daisy | Got it, clarkb. | 17:07 |
| AJaeger | clarkb, pleia2: Updated the consolidation of translation proposal scripts: https://review.openstack.org/226398 , this should be fine now to go in. | 17:09 |
| clarkb | AJaeger: cool will review | 17:09 |
| *** Daisy has quit IRC | 17:31 | |
| *** Daisy has joined #openstack-i18n | 17:32 | |
| *** Daisy has quit IRC | 17:36 | |
| pleia2 | AJaeger: thanks, lgtm | 17:42 |
| AJaeger | pleia2: thanks for the review | 17:50 |
| pleia2 | AJaeger: great email | 17:50 |
| AJaeger | clarkb, pleia2: Just summarized the situation. Please review whether I missed anything. | 17:50 |
| AJaeger | pleia2: Glad to hear! | 17:50 |
| pleia2 | :) | 17:50 |
| *** chandankumar has quit IRC | 17:52 | |
| AJaeger | clarkb, pleia2: copy-trans disable worked, see https://jenkins.openstack.org/job/python-magnumclient-upstream-translation-update/35/console | 17:54 |
| *** chandankumar has joined #openstack-i18n | 17:55 | |
| AJaeger | There's no "Copy Trans" in the logs anymore | 17:55 |
| pleia2 | \o/ | 17:55 |
| *** chandankumar has quit IRC | 18:08 | |
| *** adiantum has joined #openstack-i18n | 18:12 | |
| *** cduch has joined #openstack-i18n | 18:36 | |
| cduch | hi | 18:36 |
| AJaeger | n'abend, cduch ! | 18:38 |
| cduch | :-) | 18:38 |
| cduch | AJaeger, ich steh grad auf dem Schlauch bei ein paar Übersetzungen. | 18:39 |
| cduch | AJaeger, was ist ein "shard"? Aus welchem Kontext kommt das? Ich würde es auf deutsch auch erstmal als "Shard" bezeichen. | 18:40 |
| AJaeger | cduch: tja, sind nur noch die schwierigen übrig ;( | 18:40 |
| AJaeger | cduch: welches project? | 18:40 |
| cduch | horizon | 18:40 |
| cduch | und puppy | 18:40 |
| cduch | also "puppy" ist der zweite Begriff mit dem ich nichts anfangen kann | 18:41 |
| AJaeger | cduch: lass mich mal greppen und suchen... | 18:41 |
| cduch | ist vermutlich auch eher ein Eigenbegriff und Übersetzung eher schlecht | 18:41 |
| AJaeger | "Sell Puppy"? | 18:41 |
| cduch | ja | 18:41 |
| cduch | genau | 18:41 |
| AJaeger | # Translators: test code, don't really have to translate | 18:42 |
| cduch | ok ... | 18:42 |
| cduch | ich wunderte mich schon | 18:42 |
| AJaeger | siehe http://git.openstack.org/cgit/openstack/horizon/tree/horizon/test/test_dashboards/dogs/puppies/tables.py | 18:43 |
| AJaeger | Shard finde ich gerade nicht | 18:43 |
| doug-fish | Translating puppy for Horizon probably isn't all that imporant | 18:43 |
| doug-fish | it is in sample code | 18:43 |
| AJaeger | indeed dough-fish - thanks | 18:44 |
| doug-fish | And it really means a young dog | 18:44 |
| doug-fish | :-) | 18:44 |
| doug-fish | sure np | 18:44 |
| AJaeger | cduch: yeah, welpen if you want | 18:44 |
| AJaeger | cduch: found shard, wrong checkout ... | 18:44 |
| cduch | sure, but I'Ve asked myself if there is a new project called something with dogs :-) | 18:45 |
| doug-fish | I'm sure it seems strange out of context | 18:45 |
| doug-fish | But you must have seen cats/kittens as well? | 18:45 |
| doug-fish | Apparently Horizon people love pets! | 18:46 |
| AJaeger | cduch: shard comes from trove and I found "Support for MongoDB Clustering (v1) which provides a basic clustering framework and implements support for a MongoDB shards with shards being three member replica-sets. There will be one query router and one config server" | 18:47 |
| cduch | AJaeger: ah! ok. | 18:47 |
| AJaeger | cduch: I guess leaving it as Shard might be ok. "Glasschere" or "Scherbe" sounds strange. | 18:48 |
| cduch | AJaeger: then we will keep the word "shard" because it is used in this context | 18:48 |
| cduch | AJaeger, yes, I'agree | 18:48 |
| cduch | I'm a little late with my translation work ... you guys allready did a lot of work | 18:50 |
| AJaeger | cduch, rsimai_away: If I should update the German glossary, please tell me ;) | 18:50 |
| cduch | AJaeger, I allready did | 18:50 |
| AJaeger | cduch: you can? Great, didn't know how permissions were set | 18:50 |
| cduch | AJaeger, https://wiki.openstack.org/wiki/German_Translation_Dictionary#Terminologie | 18:50 |
| cduch | maybe the change is not online right now. ready for approval | 18:50 |
| AJaeger | cduch: no, there's aglossary in translate.openstack.org, haven't seen it? | 18:50 |
| cduch | ah, then we should point to the new one | 18:51 |
| AJaeger | wow, horizon is 100 % translated to German! Great! | 18:51 |
| cduch | yes, I did around 100 translations and 500 reviews in the last hour | 18:52 |
| cduch | is there a key for the thumbs up/down function in the reviewing process in zanata? I didn't found it | 18:53 |
| AJaeger | cduch: you did more than I did ;) | 18:54 |
| * AJaeger worked mainly on infrastructure | 18:54 | |
| cduch | AJaeger: sadly to say but, translation is really ungrateful work | 18:55 |
| AJaeger | cduch: don't know about the key, hope others do... | 18:55 |
| cduch | AJaeger: in my experience, there are not a lot people/customers who really think they need a german translation for horizon | 18:56 |
| cduch | AJaeger: instead, they have more interest in translated documentation like operating guide etc. | 18:57 |
| cduch | but the translation of documentations is a lot more complex then single words / phrases | 18:59 |
| AJaeger | cduch: I haven't done docs translations... | 19:00 |
| cduch | AJaeger: me neither. But I've written a lot of docs in german about OpenStack in the past | 19:01 |
| AJaeger | ah... | 19:02 |
| AJaeger | cduch: time for infra meeting - gute nacht! | 19:03 |
| cduch | AJaeger: n8 | 19:03 |
| *** iranzo has quit IRC | 19:17 | |
| *** cduch has quit IRC | 19:31 | |
| *** adiantum has quit IRC | 20:22 | |
| *** AJaeger has quit IRC | 20:35 | |
| *** doug-fish has quit IRC | 20:39 | |
| *** ykatabam has joined #openstack-i18n | 22:17 | |
| *** neillc has quit IRC | 22:18 | |
| *** neillc has joined #openstack-i18n | 22:18 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!