| *** adiantum has quit IRC | 01:41 | |
| *** macjack has joined #openstack-i18n | 02:20 | |
| *** steveg_afk has joined #openstack-i18n | 02:30 | |
| *** amotoki has joined #openstack-i18n | 02:48 | |
| *** steveg_afk has quit IRC | 02:51 | |
| *** epico has joined #openstack-i18n | 03:10 | |
| *** epico has quit IRC | 04:16 | |
| *** epico has joined #openstack-i18n | 04:26 | |
| *** macjack has quit IRC | 05:04 | |
| *** iranzo has joined #openstack-i18n | 05:37 | |
| *** iranzo has joined #openstack-i18n | 05:37 | |
| *** chandankumar has joined #openstack-i18n | 06:02 | |
| *** ianychoi has quit IRC | 07:10 | |
| *** fifieldt has joined #openstack-i18n | 07:13 | |
| *** ianychoi has joined #openstack-i18n | 07:14 | |
| *** ygbo has joined #openstack-i18n | 08:00 | |
| *** Daisy has joined #openstack-i18n | 09:16 | |
| *** Daisy has quit IRC | 09:37 | |
| *** Daisy has joined #openstack-i18n | 09:37 | |
| *** Daisy_ has joined #openstack-i18n | 09:41 | |
| *** Daisy has quit IRC | 09:42 | |
| *** Daisy_ has quit IRC | 09:46 | |
| *** steveg_afk has joined #openstack-i18n | 09:50 | |
| *** steveg_afk has quit IRC | 10:21 | |
| *** adiantum has joined #openstack-i18n | 10:44 | |
| *** epico has quit IRC | 10:45 | |
| *** Nikolay_St has joined #openstack-i18n | 10:58 | |
| Nikolay_St | hi | 10:58 |
|---|---|---|
| Nikolay_St | does translations tools handle string formatting introduced in pep3101? | 10:59 |
| Nikolay_St | #link: https://www.python.org/dev/peps/pep-3101/ | 10:59 |
| *** doug-fish has joined #openstack-i18n | 11:31 | |
| *** chandankumar has quit IRC | 11:46 | |
| *** doug-fish has quit IRC | 12:08 | |
| *** doug-fish has joined #openstack-i18n | 12:10 | |
| *** iranzo has quit IRC | 12:21 | |
| *** iranzo has joined #openstack-i18n | 12:22 | |
| *** daemontool_ has quit IRC | 12:23 | |
| *** chandankumar has joined #openstack-i18n | 12:24 | |
| *** daemontool_ has joined #openstack-i18n | 12:42 | |
| *** amotoki has quit IRC | 12:54 | |
| Nikolay_St | so, does anybody know the answer for my question? | 13:02 |
| *** daemontool_ has quit IRC | 13:22 | |
| *** Daisy has joined #openstack-i18n | 13:29 | |
| *** johnthetubaguy has joined #openstack-i18n | 13:49 | |
| johnthetubaguy | Daisy: hi I just wanted to quickly check about the liberty string freeze | 13:50 |
| johnthetubaguy | Daisy: is now a good moment to chat about that? | 13:50 |
| Daisy | on a phone | 13:52 |
| johnthetubaguy | Daisy: no worries, I am just checking this release is the same as previous releases, re: https://wiki.openstack.org/wiki/StringFreeze | 13:53 |
| johnthetubaguy | its not urgent | 13:53 |
| johnthetubaguy | if you can ping me when you are free, that would be awesome | 13:53 |
| Daisy | ok | 13:54 |
| Daisy | johnthetubaguy: I'm done. | 13:54 |
| johnthetubaguy | Daisy: cool | 13:55 |
| Daisy | johnthetubaguy: which project are you working on ? | 13:55 |
| johnthetubaguy | Nova | 13:55 |
| Daisy | ok. | 13:55 |
| johnthetubaguy | so we are attempting to implement a string freeze | 13:55 |
| Daisy | I think, the string freeze is same with the last one. | 13:55 |
| johnthetubaguy | I am getting push back, so I just wanted to double check its still working for you all | 13:55 |
| johnthetubaguy | so we have moving all logs to debug, with a TODO to put them back to warning or error later | 13:56 |
| Daisy | There is not a string freeze date for all projects in this release, isn't it ? | 13:56 |
| johnthetubaguy | I guess, not | 13:56 |
| johnthetubaguy | we just picked liberty-3 as thats the usual pattern | 13:57 |
| Daisy | While I'm looking at the release schedule, there is only feature freeze, no "string freeze" | 13:57 |
| johnthetubaguy | yeah | 13:57 |
| johnthetubaguy | it never really got announced as such | 13:57 |
| johnthetubaguy | I was just going off what we did last time really: https://wiki.openstack.org/wiki/Kilo_Release_Schedule | 13:57 |
| Daisy | Following the last time works fine with us. | 13:58 |
| Daisy | Following the last time schedule works fine with us. | 13:58 |
| johnthetubaguy | so the question I am getting from the developers is... you make me move the logs to debug for the string freeze, would it not be better for users they get an untranslated log, rather than no log? | 13:59 |
| johnthetubaguy | I am curious what the folks in this channel think about that | 13:59 |
| Daisy | what do you mean ? | 13:59 |
| johnthetubaguy | so its more about when we do a bug fix | 13:59 |
| johnthetubaguy | and need to add a log message thats an error or warning to the admin | 14:00 |
| *** amotoki has joined #openstack-i18n | 14:00 | |
| johnthetubaguy | in string freeze, we are only allowed to add debug message (which are assumed to be turned off by default in production) | 14:00 |
| johnthetubaguy | so we are kind of hiding the error, which can be confusing to the user | 14:00 |
| Daisy | I prefer a untranslated log. | 14:00 |
| johnthetubaguy | possibly more confusing than having an untranslated string | 14:00 |
| johnthetubaguy | Daisy: yeah, I think I do too | 14:01 |
| Daisy | My suggestion is to "not use strict string freeze", there are "string freeze exceptions" | 14:01 |
| Daisy | there could be string freeze exceptions. | 14:01 |
| johnthetubaguy | the trouble is we have loads of bug fixes with string changes, so I don't really want to go through exceptions for those | 14:02 |
| johnthetubaguy | now API error strings, totally | 14:02 |
| johnthetubaguy | but I am wondering about logs | 14:02 |
| johnthetubaguy | now leaving them untranslated for now, seems like a good middle ground | 14:03 |
| johnthetubaguy | hmm, I should go check we have the tooling for this to work | 14:03 |
| Daisy | You plan to not mark them with _("") ? | 14:04 |
| johnthetubaguy | Daisy: we have _LW and _LI etc, but yeah I was thinking just leave that off | 14:04 |
| johnthetubaguy | Daisy: now that will mean we need a # noqa message so our tests pass | 14:05 |
| johnthetubaguy | Daisy: that should make it easy to go find them when we open master for mitaka, but I need to check that works properly first | 14:05 |
| Daisy | My suggestion is to use exceptions. If our translators don't have time to translate these exceptions, we leave them untranslated. | 14:05 |
| johnthetubaguy | Daisy: OK, so we add them, but you just ignore them if there is no time? | 14:06 |
| Daisy | I mean, use string freeze exceptions. If we don't have enough time to translate these strings coming from exceptions, we just leave them untranslated. | 14:06 |
| Daisy | Yes, exactly. | 14:06 |
| johnthetubaguy | Daisy: that sounds even better, thank you | 14:06 |
| johnthetubaguy | Daisy: do you want an email for every exception? I guess they would just show up in your tools OK? | 14:07 |
| Daisy | You are welcome. Thank you for discussing with me. | 14:07 |
| Daisy | I don't want exceptions for every email. | 14:07 |
| johnthetubaguy | Daisy: I figured not, that would keep us both busy just reading them all! | 14:07 |
| johnthetubaguy | Daisy: thanks for your help with that | 14:08 |
| Daisy | You are welcome. | 14:08 |
| Daisy | I could share the translation experiences with Horizon project. | 14:08 |
| Daisy | The translation schedule of Horizon project. | 14:08 |
| johnthetubaguy | Daisy: that would be interesting | 14:09 |
| Daisy | Horizon project don't have string freeze before RC1. We will start translation without string freeze. | 14:09 |
| johnthetubaguy | (I will add this to the cross project meeting agenda later, to share the ideas) | 14:09 |
| Daisy | RC1 is for codes, and RC2 is only for translations. | 14:09 |
| johnthetubaguy | sorry, what are codes? like string ids? | 14:10 |
| Daisy | So after RC1, there will be very strict "string freeze". Horizon will give us 10 days at least, for us to catch up with the unfinished translations. | 14:10 |
| Daisy | Sorry. RC1 is only for developers, and RC2 is only for translators. | 14:11 |
| johnthetubaguy | ah, no worries, I see | 14:11 |
| johnthetubaguy | so maybe this would be better way to put what we want... until RC1: soft freeze (try not to change things you don't really have to), after RC1: very strict hard freeze, with exception process | 14:13 |
| Daisy | Let me describe more clearly. Translators will start translation without string freeze, just after feature freeze, maybe. Then have a strict string freeze date, and give us 10 days (the longer, the better) to catch up with the updated strings before the final release. | 14:13 |
| johnthetubaguy | yeah, we can do that for Nova if that would work OK for you all? | 14:14 |
| Daisy | Let's try. I don't force translators to translate Nova. Horizon, the dashboard, is our top priority project. I think, I could try to include Nova in my translation plan for Liberty release. | 14:15 |
| johnthetubaguy | totally makes sense to focus on horizon | 14:16 |
| Daisy | I want to expend to other projects. | 14:16 |
| johnthetubaguy | yeah, let me know what we can do to help move that forward, but probably post liberty now | 14:17 |
| johnthetubaguy | I suspect we probably need to make sure the logs are all very separate from other things, etc | 14:17 |
| Daisy | what do you mean by other things? | 14:18 |
| johnthetubaguy | Daisy: I think its API error messages, although having said that, I am not sure we translated those properly, I need to dig into this more really | 14:19 |
| Daisy | ok. | 14:20 |
| johnthetubaguy | Daisy: I will try draft up the plan in our wiki, then let you review it, one second while I draft that | 14:20 |
| Daisy | I want to know Nova release schedule. When is your planned strict string freeze, and when is your final release. | 14:20 |
| Daisy | I care three time poings: 1. feature freeze, 2, strict string freeze, 3, final release | 14:21 |
| Daisy | After strict string freeze, exceptions are not welcomed. | 14:22 |
| johnthetubaguy | so feature freeze has happened, let me work out the other dates | 14:22 |
| johnthetubaguy | yeah, understood | 14:22 |
| Daisy | ok. Write email to me, or write to openstack-i18n, if I don't appear in IRC. | 14:23 |
| johnthetubaguy | Daisy: thank you, will get back to you ASAP | 14:24 |
| Daisy | Thank you. | 14:24 |
| *** steveg_afk has joined #openstack-i18n | 14:27 | |
| *** Daisy has quit IRC | 14:28 | |
| *** Daisy has joined #openstack-i18n | 14:28 | |
| *** Daisy has quit IRC | 14:33 | |
| johnthetubaguy | for other interested, here is my write up: https://wiki.openstack.org/wiki/Nova/Liberty_Release_Schedule#String_Freeze | 14:39 |
| *** clarkb has quit IRC | 14:42 | |
| *** clarkb has joined #openstack-i18n | 14:44 | |
| *** fifieldt has quit IRC | 15:00 | |
| *** chandankumar has quit IRC | 15:06 | |
| *** Daisy has joined #openstack-i18n | 15:06 | |
| *** Daisy has quit IRC | 15:31 | |
| *** Daisy has joined #openstack-i18n | 15:31 | |
| *** Daisy has quit IRC | 15:36 | |
| *** macjack has joined #openstack-i18n | 15:36 | |
| *** chandankumar has joined #openstack-i18n | 15:54 | |
| *** ygbo has quit IRC | 16:01 | |
| *** doug-fis_ has joined #openstack-i18n | 16:09 | |
| *** doug-fish has quit IRC | 16:09 | |
| *** doug-fis_ has quit IRC | 16:41 | |
| *** amotoki has quit IRC | 16:46 | |
| *** doug-fish has joined #openstack-i18n | 17:00 | |
| *** iranzo has quit IRC | 17:35 | |
| *** macjack has quit IRC | 17:39 | |
| *** Nikolay_St has quit IRC | 17:58 | |
| *** doug-fis_ has joined #openstack-i18n | 17:59 | |
| *** doug-fi__ has joined #openstack-i18n | 18:00 | |
| *** doug-fish has quit IRC | 18:01 | |
| *** doug-fis_ has quit IRC | 18:03 | |
| *** chandankumar has quit IRC | 18:35 | |
| *** doug-fi__ has quit IRC | 19:00 | |
| *** doug-fish has joined #openstack-i18n | 19:01 | |
| *** doug-fish has quit IRC | 19:01 | |
| *** doug-fish has joined #openstack-i18n | 19:02 | |
| *** doug-fish has quit IRC | 19:02 | |
| *** doug-fish has joined #openstack-i18n | 19:02 | |
| *** ianychoi has quit IRC | 19:33 | |
| *** ianychoi has joined #openstack-i18n | 19:33 | |
| *** steveg_afk has quit IRC | 20:13 | |
| *** steveg_afk has joined #openstack-i18n | 20:14 | |
| *** doug-fis_ has joined #openstack-i18n | 20:30 | |
| *** doug-fi__ has joined #openstack-i18n | 20:33 | |
| *** doug-fish has quit IRC | 20:34 | |
| *** doug-fis_ has quit IRC | 20:35 | |
| *** doug-fi__ has quit IRC | 20:37 | |
| *** steveg_afk has quit IRC | 20:55 | |
| *** doug-fish has joined #openstack-i18n | 21:23 | |
| *** doug-fish has quit IRC | 21:24 | |
| *** doug-fish has joined #openstack-i18n | 21:25 | |
| *** steveg_afk has joined #openstack-i18n | 21:28 | |
| *** doug-fish has quit IRC | 21:29 | |
| *** doug-fish has joined #openstack-i18n | 21:37 | |
| *** doug-fish has quit IRC | 22:00 | |
| *** Daisy has joined #openstack-i18n | 22:02 | |
| pleia2 | hi Daisy! | 22:07 |
| Daisy | pleia2: | 22:07 |
| Daisy | Yes. | 22:07 |
| Daisy | Migration starts ? | 22:07 |
| pleia2 | we have other folks working on this migration too, so I want to keep all chat in public :) | 22:07 |
| pleia2 | in 2 hours | 22:07 |
| Daisy | ok. understand. | 22:07 |
| Daisy | Could I write an email before the migration, letting translators know that migration starts ? | 22:07 |
| pleia2 | Daisy: yes, that makes sense | 22:08 |
| Daisy | Or maybe you make the annoucement. | 22:08 |
| Daisy | ok. | 22:08 |
| pleia2 | I can reply to your email later when it's complete and people can start using it | 22:08 |
| Daisy | OK. | 22:08 |
| Daisy | will write it now. | 22:08 |
| pleia2 | sounds good | 22:10 |
| Daisy | pleia2: email sent. I will go to make breakfast now. Talk to your later. | 22:44 |
| pleia2 | Daisy: enjoy :) | 22:44 |
| *** Daisy has quit IRC | 22:45 | |
| *** Daisy has joined #openstack-i18n | 22:45 | |
| *** Daisy has quit IRC | 22:49 | |
| *** steveg_afk has quit IRC | 23:01 | |
| *** steveg_afk has joined #openstack-i18n | 23:40 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!