*** tosky has quit IRC | 01:32 | |
*** itlinux has quit IRC | 03:59 | |
*** epico has joined #openstack-i18n | 04:17 | |
*** eumel8 has joined #openstack-i18n | 05:09 | |
*** openstackgerrit has joined #openstack-i18n | 06:04 | |
openstackgerrit | OpenStack Proposal Bot proposed openstack/i18n master: Imported Translations from Zanata https://review.openstack.org/543171 | 06:04 |
---|---|---|
openstackgerrit | Merged openstack/i18n master: Imported Translations from Zanata https://review.openstack.org/543171 | 06:30 |
eumel8 | Queens sync jobs are now in place & action | 06:30 |
ianychoi | eumel8, great, thanks! | 07:34 |
eumel8 | ianychoi: I realized yesterday we missed to setup some jobs in pike, but for queens it should be clean now | 07:41 |
ianychoi | Oh some jobs were not synced between pike branch in repos and pike version in Zanata? | 07:42 |
eumel8 | ianychoi: in zanata 4 it would be better because the full workflow will be handled with API | 07:42 |
ianychoi | Oh very nice news :) | 07:43 |
ianychoi | Would u share some examples of such API? | 07:43 |
eumel8 | ianychoi: I focused on the Pike Group Dashboard in Zanata, so we have our priorities in place. But there are much more projects with a stable/pike branch | 07:44 |
eumel8 | like the oslo stuff, but I think we wouldn't translate this in branches | 07:44 |
ianychoi | eumel8, I18n team decided to have stable versions for only dashboard projects, and documents (openstack-manuals) previously but now just master for documents | 07:45 |
ianychoi | Does oslo have dashboard projects? | 07:46 |
ianychoi | Hmm, I have found that monasca-ui does not have pike branch. I will investigate in such reason shortly.. | 07:48 |
eumel8 | ianychoi: I know and I'm very happy that docs are now only in master ;) | 07:48 |
eumel8 | ianychoi: Here is an example for Zanata API: https://zanata.ci.cloudbees.com/job/zanata-api-site/site/zanata-common-api/rest-api-docs/resource_ProjectResource.html#resource_ProjectResource_put_PUT | 07:48 |
eumel8 | ianychoi: we tried this with current version (set branch read-only) and it doesn't worked | 07:49 |
eumel8 | ianychoi: I experienced with the project liaisons won't work nicely. I have now a small script in place, check for stable branches for all zanata projects on github and setup sync job proposals. | 07:52 |
eumel8 | ianychoi: and for the missing pike sync jobs I don't care so much. Focus on the future :-) | 07:54 |
ianychoi | eumel8, I am now first looking https://review.openstack.org/#/c/543040/ - how about deleting all ocata and queens job sync for server projects like nova, glance, celiometer, and so on? | 07:55 |
ianychoi | eumel8, I think some sync cleanups for ocata were not performed.. | 07:55 |
eumel8 | ianychoi: still 14 days left till EOL ocata ;) | 07:56 |
eumel8 | I have it in mind | 07:56 |
ianychoi | eumel8, also, the release model in monasca-ui is cycle-with-intermediary, not cycle-with-milestone - this is why I did not include stable in previous branches. | 07:57 |
ianychoi | eumel8, hmm, do you now have some time for discussing some criteria of defining stable branches and stable sync jobs? | 07:57 |
eumel8 | ianychoi: sure | 08:03 |
ianychoi | eumel8, thanks. I am starting to write in https://etherpad.openstack.org/p/i18n-tralation-project-targets-and-syncs | 08:10 |
ianychoi | eumel8, Oh you're right - sorry :) I have been a little bit confused with sync policies. | 08:24 |
*** epico has quit IRC | 08:46 | |
ianychoi | eumel8, I have a question on "monasca-ui". Can I ask when the project was added as translation priority? I am a little confused since it was not in translation priority in Pike period | 09:01 |
ianychoi | (Sorry if I forget some discussion results) | 09:01 |
ianychoi | Also, I am a little bit confused in some criteria of including translation-jobs-queens for a few projects which previously only had sync jobs for master - for example, openstack/zaqar: https://git.openstack.org/cgit/openstack-infra/project-config/tree/zuul.d/projects.yaml#n17550 | 09:04 |
eumel8 | ianychoi: dependly on the target branches. | 09:06 |
eumel8 | ianychoi: this could be automated - if there are stable branch in the source repo, setup stable branch in Zanata + sync job | 09:07 |
ianychoi | eumel8, automated way should be nice and I agree such automating. But it is not a good idea to have all corresponding stable versions in Zanata for stable branches in repos. For example, I don't think translators will do translation contribution for zaqar ... | 09:14 |
ianychoi | eumel8, as far as I know, the main purpose of having stable versions in Zanata is to patch translation bugs for stable branches. I18n team syncs translation projects only for projects when the projects had >75% translation. | 09:16 |
eumel8 | ianychoi: sure, it would be good to define exactly when we switch to stable branch and when we switch back. then we could automate the full workflow. | 09:26 |
eumel8 | https://docs.openstack.org/i18n/latest/release_management.html | 09:27 |
eumel8 | at point 7 it was also the question, why master branch is not read-only at this time | 09:27 |
ianychoi | eumel8, this is because master is also needed to be translated and to reflect changes in source strings in master. | 09:28 |
eumel8 | ianychoi: it confused people at this time | 09:30 |
ianychoi | eumel8, I understand such confusion and this is why "the master version on Zanata is still open for translations, but it is strongly suggested to work on a stable version." is described. Changing from master to stable-queens for example in https://translate.openstack.org/version-group/view/Queens-dashboard-translation and sharing this thing to mailing list would tell translators focusing in stable branches IMO | 09:31 |
eumel8 | ianychoi: happily zanata will merge both versions after that phase. Another problem is, you don't reach all translators with the mailing list. It would be nice if zanata has some kind of feature. | 09:36 |
ianychoi | eumel8, +1 :) | 09:39 |
ianychoi | eumel8, and FYI: http://lists.openstack.org/pipermail/openstack-i18n/2018-February/003192.html - I could ask u but I cleaned up and I found that I could also tell u cleaning up releasenotes in stable-queens versions :) | 09:40 |
eumel8 | ianychoi: yeah, more confusings ;) It will be not easy for the next PTL | 09:44 |
*** dayou has quit IRC | 09:46 | |
ianychoi | eumel8, next means.. Rocky or S-? | 09:46 |
*** dayou has joined #openstack-i18n | 09:52 | |
*** dayou has quit IRC | 09:52 | |
*** dayou has joined #openstack-i18n | 09:52 | |
eumel8 | ianychoi: Rocky is already gone ;) | 09:56 |
ianychoi | eumel8, haha but Rocky PTL has not officially started yet since it is Queens cycle now :) | 09:57 |
eumel8 | ianychoi: I heard that the same people are nominated :) | 09:59 |
eumel8 | ianychoi: btw - some hints for this: https://review.openstack.org/#/c/509297/ ? | 09:59 |
eumel8 | maybe it will discussed in Dublin | 10:00 |
ianychoi | eumel8, I told pkovar the last last Docs team meeting about this. In my opinion, PDF (and documentation translation support) needs to be added into https://governance.openstack.org/tc/reference/project-testing-interface.html document. | 10:18 |
ianychoi | I want to add to this document but do not have enough time to add some description into the document now.. | 10:19 |
ianychoi | eumel8, by the way, would u list of the target of documentation translation support from https://www.openstack.org/assets/openstack-map/openstack-map-v2017112.pdf ? | 10:21 |
ianychoi | All the documents mentioned in the map or are u considering some priorities in the map? | 10:22 |
eumel8 | ianychoi: I see. I would only clarify the status and take you out from the focus as long do you have no time. Maybe we'll make some progress during PTG | 10:25 |
ianychoi | :) | 10:52 |
ianychoi | eumel8, and can I ask u how you think how to support documentation translation? | 10:53 |
eumel8 | ianychoi: that's another zuul deep dive. I think there are something to adapt from openstack-manuals. | 10:58 |
eumel8 | https://github.com/openstack/openstack-manuals/blob/master/.zuul.yaml#L89 | 11:00 |
*** tosky has joined #openstack-i18n | 12:23 | |
openstackgerrit | Ian Y. Choi proposed openstack/i18n master: More generic exclusion in pot generation https://review.openstack.org/543220 | 13:10 |
*** eumel8 has quit IRC | 13:14 | |
openstackgerrit | Ian Y. Choi proposed openstack/i18n master: More generic exclusion in pot generation https://review.openstack.org/543220 | 13:23 |
openstackgerrit | Ian Y. Choi proposed openstack/i18n master: More generic exclusion in pot generation https://review.openstack.org/543220 | 13:31 |
*** ykatabam has joined #openstack-i18n | 14:48 | |
*** ykatabam has quit IRC | 14:49 | |
*** eumel8 has joined #openstack-i18n | 15:40 | |
*** eumel8 has quit IRC | 15:45 | |
*** eumel8 has joined #openstack-i18n | 17:19 | |
*** ykatabam has joined #openstack-i18n | 20:19 | |
*** itlinux has joined #openstack-i18n | 21:53 | |
*** rcernin has joined #openstack-i18n | 22:28 | |
*** itlinux has quit IRC | 22:40 | |
*** itlinux has joined #openstack-i18n | 23:22 | |
*** eumel8 has quit IRC | 23:24 | |
*** dayou has quit IRC | 23:54 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!