| *** jamesmcarthur has quit IRC | 00:42 | |
| *** jamesmcarthur has joined #openstack-i18n | 01:03 | |
| *** jamesmcarthur has quit IRC | 01:12 | |
| *** jamesmcarthur has joined #openstack-i18n | 01:13 | |
| *** jamesmcarthur has quit IRC | 01:13 | |
| *** jamesmcarthur has joined #openstack-i18n | 02:38 | |
| *** jamesmcarthur has quit IRC | 02:43 | |
| *** jamesmcarthur has joined #openstack-i18n | 03:02 | |
| *** jamesmcarthur has quit IRC | 03:24 | |
| *** jamesmcarthur has joined #openstack-i18n | 03:49 | |
| *** jamesmcarthur has quit IRC | 04:07 | |
| *** pcaruana has joined #openstack-i18n | 06:14 | |
| *** rsimai has joined #openstack-i18n | 06:38 | |
| *** pcaruana has quit IRC | 07:09 | |
| *** ykatabam has left #openstack-i18n | 07:11 | |
| *** rcernin has quit IRC | 07:17 | |
| *** pcaruana has joined #openstack-i18n | 07:28 | |
| *** pcaruana is now known as pcaruana|elisa| | 07:30 | |
| *** Guest95483 has joined #openstack-i18n | 07:30 | |
| *** tosky has joined #openstack-i18n | 07:36 | |
| *** jamesmcarthur has joined #openstack-i18n | 12:48 | |
| *** jamesmcarthur has quit IRC | 13:14 | |
| *** jamesmcarthur has joined #openstack-i18n | 13:14 | |
| *** jamesmcarthur has quit IRC | 13:17 | |
| *** jamesmcarthur has joined #openstack-i18n | 13:39 | |
| *** jamesmcarthur has quit IRC | 13:40 | |
| *** jamesmcarthur has joined #openstack-i18n | 13:40 | |
| amotoki | eumel8: ianychoi: how do you think we can move https://review.openstack.org/#/c/606151/ forward? | 14:06 |
|---|---|---|
| amotoki | if we publish python package from the i18n repo, it is better to have a better test coverage. | 14:06 |
| amotoki | otherwise, cross-repo thing makes situation more complicated. | 14:07 |
| amotoki | previously I tried to set up 'openstack-i18n' package so that python tools in the i18n repo can be tested (i.e. can be importable). the effort was stopped and I have no plan on this. | 14:08 |
| eumel8 | Hi amotoki. Yeah, first of all write a blueprint or a user story, fix the issues in the proposal, adjust tox.ini in project repos, check Zuul job if it's working. | 14:08 |
| eumel8 | Unfortunatelly I'm running out of time, every day. | 14:08 |
| amotoki | eumel8: i think the key point is how we can prevent regression whcih affect cross projects by changes in the i18n repo. | 14:09 |
| eumel8 | amotoki: you mean a new repo? This sounds also better to me | 14:09 |
| amotoki | eumel8: no | 14:09 |
| amotoki | eumel8: I don't mean a new repo. What I mention is to how to achieve good test coverages. | 14:10 |
| eumel8 | I'm not so familar with building python packages, so this was my first shot | 14:10 |
| eumel8 | ah, ok | 14:10 |
| amotoki | eumel8: in my understanding, what you would like to do is to provide i18n-tools-build-lang for all i18n-ed documents. right? | 14:11 |
| amotoki | eumel8: I am not sure preparing a python package is the right way or not. | 14:11 |
| eumel8 | right, a central maintained script, distributed to build jobs in project repos | 14:12 |
| eumel8 | amotoki: Ideas was the easy installation with tox as a depend package | 14:12 |
| amotoki | if so, http://git.openstack.org/cgit/openstack/openstack-doc-tools/tree/ might be a better place. | 14:13 |
| amotoki | the i18n repo focuses on providing information on i18n so far. | 14:14 |
| amotoki | providing a python package is a bit different. it requires releases. | 14:14 |
| amotoki | I don't know whether openstack-doc-tools is still maintained or not, but it looks like a simpler way to me. | 14:14 |
| amotoki | I also would like not to add more burden to i18n-core. | 14:15 |
| eumel8 | amotoki: I was there but AJaeger mentioned it's only for openstack-manuals and not project docs (https://review.openstack.org/#/c/604568/) | 14:15 |
| amotoki | i18n-core are not expected to be familiar with openstack CI processes, even though they are familiar with i18n/l10n. | 14:16 |
| amotoki | eumel8: so, a new repo i18n-tools sounds better to me. | 14:17 |
| amotoki | with new cores | 14:17 |
| eumel8 | amotoki: I would like to have the full logic in the project repos, but building language docs is more then an one-liner as you know. So there are only few changes in an initial script, but there are changes. And you are right, it needs releases. | 14:18 |
| amotoki | if we go to that route, I would suggest to move python scripts under tools/ in the i18n repo to importable python paths and provides console scripts via setup.cfg. | 14:21 |
| *** openstackgerrit has joined #openstack-i18n | 14:26 | |
| openstackgerrit | Merged openstack/i18n-specs master: fix tox python3 overrides https://review.openstack.org/606638 | 14:26 |
| eumel8 | amotoki: mhm, I'm not sure. tox was the prefered way to use in the future. So the i18n-tools repo with that package include the build script installed and called by tox should be the better solution | 14:28 |
| amotoki | eumel8: tox is a tool to handle multiple python virtual envs efficiently. setup.cfg and tox are separate things | 14:32 |
| amotoki | once the goal and vision are clear, I can help the effort but if we need a discussion on the direction on i18n documents I cannot have enough time to join the discussion. | 14:34 |
| eumel8 | yes, thats the problem. I have to write the vision first | 14:35 |
| ianychoi | (I am now reading conversation) | 14:40 |
| eumel8 | better not ;) | 14:41 |
| ianychoi | amotoki, I am on the part of placing into i18n repo. http://eavesdrop.openstack.org/irclogs/%23openstack-i18n/%23openstack-i18n.2018-09-28.log.html#t2018-09-28T15:41:09 would summarize where to place scripts for that purpose. | 14:42 |
| ianychoi | "1) placing within Docs team 2) placing within Infra team and 3) placing within I18n team" | 14:43 |
| ianychoi | Either among three ways give some pressure to different team(s) | 14:44 |
| ianychoi | Currently, although me and eumel8 are still not familiar too much with Python packaging and other stuff, I am sure that i18n-cores (at least we three) are the best to know how to implement those things. | 14:45 |
| amotoki | ianychoi: I have a concern on including it in the i18n repo. are i18n cores expected to be familiar with the infra stuffs like this? | 14:45 |
| ianychoi | Since we would like to drive this implementation, I think i18n repo would be good. | 14:45 |
| amotoki | i am familiar with python packaging and release things (as my hat of neutron/osc/horizon core) but I still have a doubt on the i18n team can cover this. | 14:46 |
| ianychoi | amotoki, how about having "i18n-tool-core" then? | 14:47 |
| amotoki | ianychoi: I am okay with it (though I am not sure I would like to be a member) | 14:48 |
| ianychoi | amotoki, I don't want to make additional pressure to you. I think you have full of your current many core-ownership.. | 14:49 |
| eumel8 | I would like to have amotoki definitly in :) | 14:51 |
| amotoki | ianychoi: it is part of joke :) my point is that it is important to clarify what are expected in a specific core team. | 14:51 |
| amotoki | ianychoi: I believe mixing roles/expectations is not a good idea. | 14:51 |
| eumel8 | but with an own repo we are more independendly | 14:52 |
| amotoki | we already have such experiences when i18n cores review zanata interaction tools | 14:52 |
| eumel8 | ianychoi: ok, how to proceed with the description of the vision. i18n spec, launchpad/blueprint or new story on storyboard? | 14:53 |
| tosky | I'm not part of this process, but given that we are trying to migrate away from launchpad, I would suggest to use storyboard directoy or specs.openstack.org if this project uses it already | 14:55 |
| *** pcaruana|elisa| has quit IRC | 14:56 | |
| eumel8 | tosky: we're very virgin: https://github.com/openstack/i18n-specs/tree/master/specs | 14:56 |
| tosky | but the infrastructure is ready :) | 14:57 |
| *** pcaruana|elisa| has joined #openstack-i18n | 14:57 | |
| eumel8 | ++ ;) | 14:59 |
| ianychoi | I18n team currently mixes with core-ship and language coordinator-ship. During last discussion on AUC criteria for I18n team, we might be able to incorporate language coordinator from AUC perspective. | 15:02 |
| ianychoi | (that's just my brief thought brought out from last discussion during PTG) | 15:03 |
| ianychoi | Solving such mix-problem would be good idea to make I18n healthier. | 15:04 |
| ianychoi | eumel8, for team vision, from my remembrance, Docs team discussed during PTG. I think discussing team mission statement via mailing list would be first step: https://governance.openstack.org/tc/reference/projects/i18n.html#mission | 15:06 |
| ianychoi | eumel8, for i18n-spec, I still be on part of encouraging the repo, but I am okay to remove the repo if you and other cores think that it does not fit with the team. | 15:07 |
| eumel8 | ianychoi: no, I mean especially what amotoki mentioned - moving forward with project doc translation. | 15:07 |
| *** pcaruana|elisa| has quit IRC | 15:08 | |
| *** pcaruana has joined #openstack-i18n | 15:08 | |
| eumel8 | ianychoi: I can use it for the first time but if we assign tasks later, then storyboard would be a better choice. | 15:08 |
| ianychoi | Aha.. eumel8 would you create an Etherpad for this goal? | 15:08 |
| eumel8 | but I'm not sure - end the end it's only one task to bring this package in | 15:08 |
| ianychoi | I think Storyboard vs. LP needs more discussion in the team. | 15:08 |
| eumel8 | yeah, etherpad is already a good idea | 15:09 |
| ianychoi | eumel8, amotoki: for diving into specific core parts, do you have some brief idea? Seems that we don't have any specific idea right now so we can start to think about it. I agree with amotoki - clarifying roles and sharing details are solutions to go forward. | 15:14 |
| eumel8 | ok | 15:15 |
| ianychoi | tosky, I agree with current migration direction from LP to Storyboard, and during last PTG, I discussed with Storyboard team how to internationalize Storyboard. One of issues I18n team may need to think is how "different language team culture" can reflect into Storyboard. | 15:15 |
| ianychoi | I think I18n-ing Storyboard, and creating specific stories for language teams may address such issues. | 15:16 |
| amotoki | ianychoi: eumel8: I have no good idea to recruiting new members on tooling/infra part of the i18n team. | 15:25 |
| amotoki | ianychoi: eumel8: we so far recruited members who are active in translations but it turns out to me that we expect different roles to them. Hosting i18n tools more would encourage this expection. this is the reason I raised it here. | 15:25 |
| amotoki | perhaps we need to recruit folks who work on infra/CI stuffs to the team (i18n-tool core? not sure) | 15:26 |
| *** rsimai has quit IRC | 15:27 | |
| *** pcaruana has quit IRC | 15:31 | |
| eumel8 | I would expect a minimized part of work for i18n tooling. | 15:33 |
| *** openstackgerrit has quit IRC | 16:24 | |
| *** tosky has quit IRC | 17:18 | |
| *** jamesmcarthur has quit IRC | 17:19 | |
| *** jamesmcarthur has joined #openstack-i18n | 17:26 | |
| *** jamesmcarthur has quit IRC | 18:34 | |
| *** jamesmcarthur has joined #openstack-i18n | 23:10 | |
| *** jamesmcarthur has quit IRC | 23:15 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!