Friday, 2015-11-06

*** _ianychoi_ is now known as ianychoi00:13
*** Daisy has joined #openstack-i18n01:17
*** Daisy has quit IRC01:19
*** Daisy has joined #openstack-i18n01:20
*** Daisy has quit IRC01:28
*** Daisy has joined #openstack-i18n01:34
*** Daisy has quit IRC01:39
*** Daisy has joined #openstack-i18n02:02
*** Daisy has quit IRC02:09
*** Daisy has joined #openstack-i18n02:09
*** Daisy has quit IRC02:14
*** Daisy has joined #openstack-i18n02:28
*** Daisy has quit IRC02:42
*** Daisy has joined #openstack-i18n03:04
*** Daisy has quit IRC03:08
*** Daisy has joined #openstack-i18n03:32
*** Daisy has quit IRC03:37
*** Daisy has joined #openstack-i18n03:54
*** Daisy has quit IRC03:57
*** suanand has joined #openstack-i18n04:43
*** amotoki has joined #openstack-i18n04:51
*** ykatabam has quit IRC05:42
*** openstackgerrit has quit IRC06:31
*** openstackgerrit has joined #openstack-i18n06:32
*** david-lyle has joined #openstack-i18n06:40
*** david-lyle has quit IRC06:45
*** katomo has joined #openstack-i18n07:10
katomoHi, amotoki. I'm in meeting, so maybe late response :)07:11
amotokikatomo: you don't need to rush. let me ping after your meeting is over.07:12
katomothanks, see you later07:13
amotokikatomo: I think there are several points to be considered about the i18n document.07:13
katomoagree07:13
amotoki (1) a single document or multiple documents07:13
amotoki(2) document translation handling (we can leverage docs tool chain) -- do we want to translate 'i18n document' itself?07:14
amotoki(3) document style checking like niceness (I think it is useful)07:14
amotokiany other points?07:14
katomolanguage specific contents07:15
katomomaybe (2)'07:15
amotokiit's related to (2) but I think a different topic.07:16
katomoyes07:16
amotoki(4) allow to have language specific contents07:16
katomomay affect (1) : become multiple documents?07:17
katomoyes (4)07:17
katomolet's split topic07:17
amotokisure. re: (4), we can use a separate top directory I think.07:18
katomothat's all at now from my thought07:18
katomoah07:19
katomo(5) publish location07:19
katomohttp://docs.openstack.org/developer/i18n ? okay?07:20
amotokii have one minor thing: (6) infra config: do we follow most project jobs (pep8, doc, pytho27) or doc jobs (checknicesss, checkbuild, ....)07:20
katomoIf okay, not so hard. If no, a little hard.07:21
amotokiRe: (5), developer/i18n looks a good start. as you say, it is easy.07:21
katomoyeah (6)07:21
katomoyes07:22
amotokiyes on what?07:22
amotokion (5)?07:22
katomoRe: (5), yes07:22
amotokiokay, we agree to use http://docs.openstack.org/developer/i18n for the initial content location.07:23
katomookay07:23
katomoI'll update the blueprint07:25
amotokire (6) what do you think?07:25
katomouseful07:26
katomoi think we should add them07:26
katomodocs job is useful to me07:27
amotokiI am not sure we maintain scripts in our repo, so a need for python27 job would be low.07:28
katomocan we add both?07:28
amotokiyes if we can have anything, but we cannot use usual template in zuul/jbb.07:29
katomohmm07:29
amotokion the other hand, docs jos have various jobs but only checknicess and checkbuild have actual jobs and all of the rest are empty jobs.07:30
amotokilet me check on zuul/jjb template later07:30
katomothanks.07:31
katomoi need to be familiar with them, too07:31
amotokithis is an example of security guide https://review.openstack.org/#/c/242308/07:31
amotokiit looks good to me now.07:32
amotokiwe can change our test easily, so it looks good to start with doc jobs (checkniceness and checkbuild).07:33
*** adiantum has joined #openstack-i18n07:33
amotokikatomo: regarding (2), in my understanding, the current doc tool chain supports a siglle document. right?07:34
amotokibecause it uses sphinx-build inside.07:35
*** Daisy has joined #openstack-i18n07:36
katomoyes, but07:36
katomoloop call from outside07:36
katomohttps://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc-tools-check-languages.conf07:38
katomocontrolled by this definition07:38
amotokithanks for clarfication.07:39
amotokiI think a single document is a good start (as long as we can leverage the doc tool chain).07:39
katomoagree07:40
amotokiwith a single document, we don't need to worry about if this content fit this document or i should create a new doc.07:40
amotokilet me summarize what we discuss so far:07:41
amotoki(1) a single document or multiple documents -- a single document looks better07:42
amotoki(2) document translation handling -- we can use the doc tool chain if we want to have07:42
amotoki(3) document style checking like niceness -- looks useful: checknicenss and checkbuild07:43
amotoki(4) allow to have language specific contents -- we can use a separate top directory in i18n repo. (perhaps we can update doc tool chain if want)07:44
amotoki(5) publish location -- http://docs.openstack.org/developer/i18n is a good start because the current infra tool chain support this location07:45
amotoki(6) infra config -- docs jobs looks suitable at the moment07:45
katomookay07:47
katomothanks to summarize07:48
katomoHello Daisy07:50
katomohere?07:50
DaisyHi, there07:50
katomo^^ please take a look at summary by amotoki07:50
katomodiscussion about i18n guide07:50
DaisyReading07:50
Daisyabout (2), the doc tool chain is for translation only ?07:51
katomono, doc tool chain is useful for (3)07:52
Daisykatomo: I really don't like copy the doc tool chain to i18n repo. If there are other choices to refer to, I will not agree to copy.07:52
katomohm07:53
katomowhy?07:53
DaisyBecause it's a kind of duplicate.07:53
amotokithe doc tool chain I proposed contains only three file.07:53
amotokione is for translation and the other two are just a wrapper of sphinx.07:54
Daisyand has no relationship with i18n, except i18n doc building.07:54
amotokifor (3), openstack-doc-tool comes from doctool and we don't need to have a copy.07:54
amotokiDaisy: so perhaps we can drop build-rst.sh and build-all-rst.sh07:55
amotokiDaisy: generatepot-rst.sh can be simplified but I haven't investigated it yet.07:56
amotokiit can be deferred later.07:56
amotokiin the initial commit we don't need to support translation :-)07:57
Daisyamotoki: my opinion is to keep necessary files only.07:57
Daisyi18n repo is not a document repo.07:57
amotokiDaisy: agree.07:58
DaisyThank you, amotoki.07:58
amotokibtw, do we want to support translation for the doc in i18n repo?07:59
amotokis/the doc/the doc and others?07:59
DaisyI hope so.07:59
DaisyI don't see others till now.07:59
amotokiso, what are our conclusion? i18n repo is not a document repo. hopefully we support translation for the contents of i18n repo.08:02
amotokiwhat should tox env and job names be?08:02
Daisytox is for testing ?08:02
Daisywhat are jobs for ?08:02
amotokijenkins jobs to check styling, check document build or check something...08:03
katomoDaisy, amotoki, so sorry, I'm offline at once. I should understand the situation and your requirements.08:04
Daisyi18n repo is not a document repo. It is used for i18n related assets. "how to contribute" could be regarded as a developer document for a code project. So treat it similar as doc folder under Neutron.08:04
DaisyOf course, we are i18n team. I hope our own document could be translated.08:05
*** katomo has quit IRC08:05
DaisyI see the document build command in tox.ini under Neutron.08:08
amotokiyes. i know08:08
amotokiwe can follow it because we agree that we should a single document (doc/source/)08:09
DaisyThat's better, because it looks simple.08:09
Daisyas (4), maybe not a separate top folder under i18n repo.08:11
DaisyLet me think08:11
Daisyunder i18n repo, we have doc and tools.08:11
DaisyUnder doc, we have our rst files, and "locale" folder to contain the translated pot and po files.08:11
DaisyI think Neutron doc doesn't support translation.08:11
*** katomo has joined #openstack-i18n08:12
*** ykatabam has joined #openstack-i18n08:12
DaisyI hope documentation team could have a way to refer to their tools other than copying codes directly.08:13
Daisyother than copying their source codes directly.08:13
amotokiDaisy: most tools from the docs team are maintained in doctool repo and it is published as doctool in PyPI.08:13
amotokiDaisy: but there are some exceptions because it is specific to a repo structure.08:14
Daisyok.08:15
DaisyCould we follow the repo structure ? Maybe you could give me a sample of the repo structure ?08:15
Daisylike manuals ?08:15
Daisyor like ha-guide ?08:18
amotokiAccording to our dicsussion so far, it seems better to me to follow the structure of non-doc repo. thought?08:19
Daisyi'm looking at the structure of ha-guide.08:19
katomodoc/source ?08:19
Daisyamotoki: I like to follow the structure of non-doc repo.08:19
amotokikatomo: yes, doc/source.08:20
katomomanuals and ha-guide repos are a little complex to support multi docs.08:20
katomoDaisy: agree to non-doc repo.08:21
Daisythank you, katomo08:21
DaisyIf we have multiple documents for i18n, maybe we could ask for a i18n-doc repo separately08:21
Daisyin the future, I mean, if we have multiple documents for i18n, we could ask for a i18n-doc repo.08:22
DaisyBut for now, keep things simple, till we grow mature。08:22
katomosounds good idea08:22
amotokiagree.08:23
amotokilet's start with simple.08:23
katomoyes :)08:24
katomoI'll update the patch08:25
*** katomo has quit IRC08:35
*** Daisy has quit IRC08:38
*** Daisy has joined #openstack-i18n08:38
*** openstackstatus has quit IRC08:42
*** Daisy has quit IRC08:43
*** Daisy has joined #openstack-i18n08:52
*** Daisy has quit IRC08:54
*** ygbo has joined #openstack-i18n08:56
*** rsimai_away is now known as rsimai08:58
*** ykatabam has left #openstack-i18n09:15
openstackgerritKATO Tomoyuki proposed openstack/i18n: Create I18n Contributor Guide configuration  https://review.openstack.org/24110309:16
*** Besnik has joined #openstack-i18n09:35
*** Besnik has left #openstack-i18n09:40
*** epico has joined #openstack-i18n10:02
*** epico has quit IRC10:31
*** Daisy has joined #openstack-i18n10:37
*** Daisy has quit IRC10:41
*** ykatabam has joined #openstack-i18n11:51
*** ykatabam has left #openstack-i18n11:55
*** Daisy has joined #openstack-i18n12:13
*** Daisy has quit IRC12:14
*** ykatabam has joined #openstack-i18n12:38
*** suanand has quit IRC12:54
*** amotoki has quit IRC15:19
*** ygbo has quit IRC16:18
*** ygbo has joined #openstack-i18n16:20
*** rsimai has quit IRC16:36
*** adiantum has quit IRC17:00
*** ygbo has quit IRC17:49
*** Besnik has joined #openstack-i18n18:55
*** Besnik has left #openstack-i18n18:56
*** openstackstatus has joined #openstack-i18n19:35
*** ChanServ sets mode: +v openstackstatus19:35
-openstackstatus- NOTICE: Gerrit will be offline at 20:00-20:15 UTC today (starting 20 minutes from now) for scheduled project rename maintenance19:40
-openstackstatus- NOTICE: Gerrit is offline until 20:15 UTC today for scheduled project rename maintenance20:02
*** ChanServ changes topic to "Gerrit is offline until 20:15 UTC today for scheduled project rename maintenance"20:02
*** ChanServ changes topic to "OpenStack goes multilingual! | I18n & L10n channel"20:36
*** openstackgerrit has quit IRC21:01
*** openstackgerrit has joined #openstack-i18n21:02
*** doug-fish has quit IRC22:40
*** ykatabam has quit IRC23:46

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!