07:59:42 #startmeeting OpenStack I18n Meeting 07:59:43 Meeting started Thu Aug 7 07:59:42 2014 UTC and is due to finish in 60 minutes. The chair is Fdot. Information about MeetBot at http://wiki.debian.org/MeetBot. 07:59:44 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 07:59:46 The meeting name has been set to 'openstack_i18n_meeting' 07:59:49 w00t 08:00:14 Good morning/evening everybody :) 08:00:25 who is here ? 08:00:34 steff00 08:00:35 Morning! 08:00:41 good afternoon 08:00:45 hello Steff00 jpich :) 08:00:47 good afternoon =) 08:00:47 hello everybody 08:00:47 good afternoon 08:00:51 hello 08:01:16 Hello :) 08:01:23 :) 08:01:34 Daisy is in holiday today, so I am going to drive this meeting 08:01:41 the agenda is very light 08:01:56 we are going to speak about the Documents’ categorization 08:02:12 and we will take some time for an open discussion 08:02:26 is there any subjects you would like to add to the agenda ? 08:03:27 ok we will see during the open discussion :) 08:03:34 #topic Documents’ categorization 08:04:05 In a previous meeting we have started to discuss about categorize the translation projects 08:04:17 there is now too many projects in transifex 08:04:29 and some projects are changing too much 08:04:50 #link https://www.transifex.com/projects/p/openstack-manuals-i18n/resources/ 08:04:50 so for new translators it is difficult to see how to start 08:05:18 and they could be afraid about all the works 08:05:27 thanks fifieldt 08:05:47 so it could be interesting to categorize all the projects 08:05:55 and then defining priorities 08:06:09 we have started to discuss about this with Daisy 08:06:15 and we have 2 propositions : 08:06:25 #link https://wiki.openstack.org/wiki/I18nTeam/docs-translation 08:06:42 what do you think about this ? Any suggestion ? 08:08:08 looks pretty good, but not so much documents categorized 08:08:23 adiantum: it is just an example ;) 08:08:29 anyone want to quickly l;ook at : https://etherpad.openstack.org/p/i18n-manuals-classification ? 08:08:31 ok =) 08:08:34 we could attempt to classify them now 08:08:51 I didn't add every projects before being agree about the format :) 08:09:13 seems to be a good thing . Who will classify the docs ? 08:10:01 Steff00: every volunteers are welcome :) 08:10:44 so, I think stablity varies during the release cycle 08:10:57 for instance, install-guide is stable for about a 3-4 week period every cycle 08:11:05 so if we want to translate that, we should do it during that time 08:12:01 just a note, looks like we could use one heuristic - log translations is not very important, so all docs with type log could have low priopity 08:12:13 sorry for beeing late - any question you have on Documents that I can help with? 08:12:18 adiantum: agree :) 08:12:32 AJaeger: hello :) 08:12:52 AJaeger, see if you agree with the categorisations in https://etherpad.openstack.org/p/i18n-manuals-classification 08:13:02 * AJaeger checks 08:13:07 One important things a lot of contributors coming are not coming for only translating the documentation 08:13:31 they are also coming for translating services like Horizon 08:13:39 and how frequently changing common during release cycle? 08:14:12 so we have to add it into the list and priorization 08:14:28 yes, common is a problem 08:14:46 common is moving too much and it is too big 08:15:26 AJaeger, what do you think about moving the config tables out of common into config-reference 08:15:40 Fdot, but common includes a couple of files that need translation - like the preface and appendix 08:15:42 I don't think we really use them as 'common' 08:15:45 fifieldt, sure, we can do that. 08:16:02 I think to facilitate translation, common should be as small as possible 08:16:15 be aware that we download in general only files that have at least 75 % translations with two exceptions: glossary and common (8 % each) 08:16:27 fifieldt, propose a patch ;) 08:16:30 AJaeger: yes but 73,557 words :) 08:17:49 * AJaeger agrees with the classification on the etherpad and has commented on it 08:18:07 is it possible to move all the logs into one log common project ? 08:18:36 actually, it's true that many log messages come from oslo.common 08:19:06 Fdot, they come initially from oslo-incubation and the files get copied around 08:19:28 There is a danger though that different projects use different versions of oslo 08:19:34 With a couple of oslo libraries graduated now, we have a much better situation. 08:20:12 They are now in *one* location - lke olso.messaging or oslo.i18n. Projects just need to update and remove the old oslo-incubation code and require the library instead 08:20:27 My recommendation for now: Don't translate log message and wait a bit until this has settled... 08:20:46 AJaeger: ok 08:21:57 Etherpad is going to be usefull for completing the wiki page 08:21:59 thanks a lot 08:22:18 I am going to add all the informations and projects today 08:22:32 Fdot, one other thing to consider 08:22:40 is taking a stance like the documentation team did 08:22:48 that they wouldn't touch non-integrated projects 08:23:29 * AJaeger has setup the translation jobs for the projects in incubation. I can switch those off if desired... 08:23:48 fifieldt: which one for example ? 08:23:52 sahara, marconi, barbarican etc 08:23:58 designate, gantt 08:24:05 oh ok of course 08:24:16 given the limited resources in our team, and the scary number of projects, it might be a reasonable step to remove these first 08:24:30 it would reduce the number of untranslated projects in view 08:24:39 I am agree with you 08:25:20 And in our translating teams we should communicate more about the priority 08:25:43 and about the project we don't need to touch 08:25:50 yup, it's nice 08:25:52 like the documentation team 08:26:57 are we still all agree about the priorities during the past meeting : 08:27:16 api-quick-start 08:27:16 api-ref-guides 08:27:16 api-ref 08:27:16 image-guide 08:27:16 Horizon 08:28:37 Seems like a reasonble start - they are small 08:28:43 and not changing 08:29:05 and easy for new translators arriving on the project 08:29:44 sounds good 08:29:48 fifieldt, some of these projects will integrate in Juno, so we should have them. 08:29:50 and the config tables will be removed from common we will be able to add it into the list 08:30:23 * AJaeger does not agree with api-ref and api-ref-guides 08:30:35 AJaeger: why ? 08:30:42 those are small because they contain lots of WADL that is not translated! 08:30:42 I just checked, and the config tables are 27812 words 08:30:58 this is true 08:31:24 25% of the project ;) 08:31:43 they're so small though AJaeger 08:31:51 api-ref-guides is 211 words 08:32:08 api-ref is a bit bigger though 08:32:15 4151 words 08:32:41 let me check how large the generated manuals are... 08:32:44 AJaeger is right that they shouldn't be a "priority" in terms of usefulness, but they can serve a purpose of giving a sense of completeness for a team :) 08:32:57 AJaeger, 20k words for install guide for example 08:33:09 60k words for ops guide 08:34:37 api-ref produces html pages and includes the WADLS 08:36:12 complete api-ref-guides is 1402 pages - the 211 words is just misleading 08:36:34 api-ref-guides includes *lots* of other files, the 211 words are just the glue that ties it together. 08:36:40 Same with api-ref-guides 08:36:52 1402 PDF pages 08:37:04 AJaeger: It could be very interesting to be able to translate this content 08:37:22 because it has been done for end users / developers 08:37:38 Fdot, I don't think it's worth to translate the API - this is reference documentation. 08:37:55 Fdot, first you need to enhance the tools so that WADLs can be translated as well. 08:38:05 This is a not trivial 08:38:14 AJaeger: I know 08:38:35 is the move from transifex to an another tool is going to improve this ? 08:38:40 Sory, I have to leave again and if there are further questions, I can answer on the i18n mailing list 08:38:55 Fdot, not at all: We extract the po files with our own tools 08:39:07 AJaeger: no pb thanls a lot for your time 08:39:08 bye 08:39:10 AJaeger: ok :/ 08:40:04 thanks! 08:40:15 Is there anything somebody want to add to this topic ? 08:40:36 I think we've made good progress 08:40:46 fifieldt: i think too :) 08:41:09 #topic Free discussion 08:41:26 I have a question for fifieldt 08:41:43 do you know when is the string freeze for the documentation ? 08:41:43 ok? 08:42:00 erm, you mean when documentation "stops"? 08:42:04 yes 08:42:07 it doesn't 08:42:10 for juno of course :) 08:42:12 there is no string freeze for documentation 08:42:41 and for the others project ? 08:42:58 https://wiki.openstack.org/wiki/Juno_Release_Schedule 08:43:01 Sep 4 08:43:23 aka Juno-3 08:43:42 fifieldt: thanks a lot that's exactly what i was looking for :) 08:44:01 :) 08:44:22 :) 08:44:30 Any others questions ? :) 08:46:21 ok so let's close the meeting 08:46:36 thanks a lot everybody for this rich discussion :) 08:46:55 have a good day / night ! 08:47:08 thanks Fdot! 08:47:10 thank you =) 08:47:15 thanks 08:47:16 :Thanks 08:47:18 :) 08:47:34 #endmeeting