- OpenStack-I18n - lists.openstack.org

Re: [Openstack-i18n] stable-liberty version for openstack-manuals created in Zanata
by Andreas Jaeger 17 Nov '15

17 Nov '15

On 2015-11-17 10:49, Ying Chun Guo wrote: > Hi, Andreas > > I see stable/liberty is created in the repo of openstack-manuals, > and stable-liberty version is created for openstack-manuals project in > Zanata. > Thank you for handling these. > > Is the installation guide in the master branch keeping open for Mitaka > release? Yes. > So in order to translate Liberty installation guide, our translators should > go to stable-liberty and work there. Correct. > I have changed the link of openstack manuals in the home page > translation plan > to stable-liberty version. > Correct me if I'm wrong. Looks fine Andreas > Thank you. > Best regards > Ying Chun Guo (Daisy) > > ----- Forwarded by Ying Chun Guo/China/IBMon 2015/11/17 17:40----- > > Andreas Jaeger <aj(a)suse.com> wrote on 2015/11/16 23:44:58: > > > From: Andreas Jaeger <aj(a)suse.com> > > To: "openstack-docs(a)lists.openstack.org" > <openstack-docs(a)lists.openstack.org> > > Date: 2015/11/16 23:46 > > Subject: [OpenStack-docs] stable/liberty for openstack-manuals > > created - and frozen! > > > > Thanks to Spencer Krum (nibalicer) we now have a stable/liberty branch > > for openstack-manuals. > > > > I now need to setup the branch and ask for a freeze of stable/liberty > > until I have given the go ahead for the branch! I need to set it up and > > document all the steps ;) > > > > Merging of changes for master is fine but do not merge any for > liberty yet! > > > > Thanks > > Andreas > > -- > > Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi > > SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany > > GF: Felix Imendörffer, Jane Smithard, Graham Norton, > > HRB 21284 (AG Nürnberg) > > GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 > > > > > > _______________________________________________ > > OpenStack-docs mailing list > > OpenStack-docs(a)lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs > -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

1 0

stable-liberty version for openstack-manuals created in Zanata
by Ying Chun Guo 17 Nov '15

17 Nov '15

Hi, Andreas I see stable/liberty is created in the repo of openstack-manuals, and stable-liberty version is created for openstack-manuals project in Zanata. Thank you for handling these. Is the installation guide in the master branch keeping open for Mitaka release? So in order to translate Liberty installation guide, our translators should go to stable-liberty and work there. I have changed the link of openstack manuals in the home page translation plan to stable-liberty version. Correct me if I'm wrong. Thank you. Best regards Ying Chun Guo (Daisy) ----- Forwarded by Ying Chun Guo/China/IBM on 2015/11/17 17:40 ----- Andreas Jaeger <aj(a)suse.com> wrote on 2015/11/16 23:44:58: > From: Andreas Jaeger <aj(a)suse.com> > To: "openstack-docs(a)lists.openstack.org" <openstack-docs(a)lists.openstack.org> > Date: 2015/11/16 23:46 > Subject: [OpenStack-docs] stable/liberty for openstack-manuals > created - and frozen! > > Thanks to Spencer Krum (nibalicer) we now have a stable/liberty branch > for openstack-manuals. > > I now need to setup the branch and ask for a freeze of stable/liberty > until I have given the go ahead for the branch! I need to set it up and > document all the steps ;) > > Merging of changes for master is fine but do not merge any for liberty yet! > > Thanks > Andreas > -- > Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi > SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany > GF: Felix Imendörffer, Jane Smithard, Graham Norton, > HRB 21284 (AG Nürnberg) > GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 > > > _______________________________________________ > OpenStack-docs mailing list > OpenStack-docs(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs

1 0

Rename the language code of Punjabi
by Ying Chun Guo 16 Nov '15

16 Nov '15

Hello, According to previous discussion[1], it seems like pa-IN is meaningless. "Punjabi has two entirely different scripts i.e. Gurmukhi (ਪੈਂਤੀ) and Shahmukhi (اردو), while former is widely used in Indian side of Punjab aka Eastern Punjab the latter is used in Pakistani side of Punjab aka Western Punjab." The translations of pa-IN are mixing of two kinds of characters. So I think we should rename pa-IN to pa-Guru, in order to avoid confusing. I see Alam prefer to use "pa", not "pa-Guru". [2] But I think pa-Guru is more clear than pa. @Alam and Amandeep, correct me if I'm wrong. I have created a blueprint.[3] The work items include both the language team rename in Zanata and the folder rename in repo. Please review. Best regards Ying Chun Guo (Daisy) [1] http://lists.openstack.org/pipermail/openstack-i18n/2015-September/001358.h… [2] http://lists.openstack.org/pipermail/openstack-i18n/2015-September/001424.h… [3] https://blueprints.launchpad.net/openstack-i18n/+spec/rename-punjabi-code

2 2

Duplicated toctree of sidebar in translated install guides
by Akihiro Motoki 16 Nov '15

16 Nov '15

Hi, I noticed translated install guides have a toctree in the sidebar twice. The example is http://docs.openstack.org/draft/ja/install-guide-obs/ . I filed a bug at https://bugs.launchpad.net/openstack-manuals/+bug/1516079 . It is due to the change in https://review.openstack.org/#/c/237885/ and I think it is because index.rst has two toctree. We are doing a special handling in tools/build-install-guides-rst.sh when generating a non-translated install guide. Do we need a similar handling for translated install guides? The translated install guides are currently generated by doc-tools-check-languages and some infra jobs. I am not confident how they are involved. Any help would be appreciated. Thanks, Akihiro

3 2

How can i join Chinese (China) team？
by gaoxiao zhu 16 Nov '15

16 Nov '15

Hi all, I registered myself for the Chinese (China) translation project .I am looking forward to begin contributing for the project. What should I do? Best regards

2 1

Re: [Openstack-i18n] I18n wiki page is translatable
by Tom Fifield 14 Nov '15

14 Nov '15

On 13/11/15 14:00, Ying Chun Guo wrote: > Thank you, Akihiro. > It looks wonderful. > I think we could mark I18nTeam translatable now. > > Tom, please help. The page I18nTeam has been marked up for translation with 14 translation units. The page can now be translated. > Best regards > Ying Chun Guo (Daisy) > > > Akihiro Motoki <amotoki(a)gmail.com> wrote on 2015/11/12 23:06:14: > > > From: Akihiro Motoki <amotoki(a)gmail.com> > > To: Ying Chun Guo/China/IBM@IBMCN > > Cc: Tom Fifield <tom(a)openstack.org>, Openstack-i18n <openstack- > > i18n(a)lists.openstack.org> > > Date: 2015/11/12 23:06 > > Subject: Re: [Openstack-i18n] I18n wiki page is translatable > > > > Hi Daisy, > > > > I move all team wiki pages to I18nTeam/team/xxxxx. > > In addition, I created a page > https://wiki.openstack.org/wiki/I18nTeam/team > > which contains a list of language teams. > > > > Akihiro > > > > 2015-11-12 16:04 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > > > Thank you Tom. > > > Sorry for the trouble. > > > I will move all the team wiki pages to different links. > > > > > > Best regards > > > Ying Chun Guo (Daisy) > > > > > > > > > Tom Fifield <tom(a)openstack.org> wrote on 2015/11/12 07:43:39: > > > > > >> From: Tom Fifield <tom(a)openstack.org> > > >> To: Ying Chun Guo/China/IBM@IBMCN, Akihiro Motoki <amotoki(a)gmail.com> > > >> Cc: Openstack-i18n <openstack-i18n(a)lists.openstack.org> > > >> Date: 2015/11/12 07:43 > > > > > > > > >> Subject: Re: [Openstack-i18n] I18n wiki page is translatable > > >> > > >> Hi, > > >> > > >> Sorry, it took a while to work out how to disable the translations. > > >> That's been done now. > > >> > > >> > > >> Regards, > > >> > > >> > > >> Tom > > >> > > >> On 11/11/15 18:09, Ying Chun Guo wrote: > > >> > I think we need to disable the translation at first. > > >> > Then we could be able to move them. > > >> > I'm not able to move, same as you. > > >> > > > >> > Best regards > > >> > Ying Chun Guo (Daisy) > > >> > > > >> > > > >> > Akihiro Motoki <amotoki(a)gmail.com> wrote on 2015/11/11 14:40:43: > > >> > > > >> > > From: Akihiro Motoki <amotoki(a)gmail.com> > > >> > > To: Ying Chun Guo/China/IBM@IBMCN > > >> > > Cc: "Ian Y. Choi" <ianyrchoi(a)gmail.com>, Openstack-i18n > <openstack- > > >> > > i18n(a)lists.openstack.org> > > >> > > Date: 2015/11/11 15:05 > > >> > > Subject: Re: [Openstack-i18n] I18n wiki page is translatable > > >> > > > > >> > > Daisy, > > >> > > > > >> > > It sounds good to me, but normal users like me cannot move pages. > > >> > > I got Permission Error. Could you handle all moving of pages? > > >> > > > > >> > > > > >> > > 2015-11-11 15:05 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > > >> > > > Thank you for the explain Ian. > > >> > > > I think we could move the wiki pages for language teams to > > >> > > > /I18nTeam/team/<language-code>, > > >> > > > and then keep /I18nTeam/<language-code> for the translation > page of > > >> > > > I18nTeam. > > >> > > > > > >> > > > How do you think about it, Akihiro? > > >> > > > > > >> > > > Best regards > > >> > > > Ying Chun Guo (Daisy) > > >> > > > > > >> > > > > > >> > > > "Ian Y. Choi" <ianyrchoi(a)gmail.com> wrote on 2015/11/11 > 00:55:07: > > >> > > > > > >> > > >> From: "Ian Y. Choi" <ianyrchoi(a)gmail.com> > > >> > > >> To: Akihiro Motoki <amotoki(a)gmail.com>, Ying Chun > > >> > Guo/China/IBM@IBMCN > > >> > > >> Cc: Openstack-i18n <openstack-i18n(a)lists.openstack.org> > > >> > > >> Date: 2015/11/11 00:55 > > >> > > >> Subject: Re: [Openstack-i18n] I18n wiki page is translatable > > >> > > > > > >> > > > > > >> > > >> > > >> > > >> Hello Akihiro, > > >> > > >> > > >> > > >> Actually I suggested a translatable I18nTeam wiki page [1] for > > >> > Korean > > >> > > >> during last Tokyo Design Summit. > > >> > > >> After saying it, I found that there might be a problem in > Japanese > > >> > local > > >> > > >> team > > >> > > >> because Japanese language team already used /ja page, as you > > >> > mentioned and > > >> > > >> which would make conflict with translation functionality in > > >> > OpenStack > > >> > > >> wiki. > > >> > > >> > > >> > > >> Let me first say why Korean translation page for I18nTeam is > > >> > needed and > > >> > > >> how Korean translation team wants to use two wiki pages > > >> > separately: > > >> > > >> > > >> > > >> 1) https://wiki.openstack.org/wiki/I18nTeam/ko > > >> > > >> : To provide Korean guys with official I18nTeam introduction > > >> > wiki page > > >> > > >> : I think "Local Translation Teams" section is needed > because > > >> > this > > >> > > >> information is > > >> > > >> beneficial with the knowledge of the various language team > > >> > activities. > > >> > > >> > > >> > > >> 2) https://wiki.openstack.org/wiki/I18nTeam/team/ko_KR > > >> > > >> (I found that Daisy moved from .../ko_KR to .../team/ko_KR. > > >> > Thank you!) > > >> > > >> : To introduce Korean translation team with details and our > > >> > specific > > >> > > >> translation rules > > >> > > >> : Providing links for OpenStack I18n official > introduction wiki > > >> > page & > > >> > > >> its translation > > >> > > >> > > >> > > >> I would like to respect I18nTeam official wiki page, and this > > >> > > >> information is written in English. > > >> > > >> In my opinion, translating this page would more clearly > advertise > > >> > > >> OpenStack I18n overall activities to more Korean. > > >> > > >> > > >> > > >> This requirement and need might be different from various > local > > >> > > >> translation teams, I think, > > >> > > >> and I also would like to respect the ways Japanese team > used more > > >> > than 1 > > >> > > >> year. > > >> > > >> > > >> > > >> So I would like to suggest not to include "<languages />" > tag on > > >> > [1] . > > >> > > >> As you know, OpenStack Release Note wiki pages such as [2] > > >> > > >> contain "<languages />" tag and displays different language > > >> > translated > > >> > > >> pages on the top part. > > >> > > >> > > >> > > >> I think this suggestion would satisfy different needs from > various > > >> > > >> language translation teams. > > >> > > >> However, if https://wiki.openstack.org/wiki/I18nTeam page > includes > > >> > > >> "<languages />" tag, > > >> > > >> then it would not fit to not only Japanese translation > team, but > > >> > also > > >> > > >> other teams such as French, Polish and so on. > > >> > > >> For Korean translation team, our official page contains the > > >> > translated > > >> > > >> I18nTeam link so it would be okay. > > >> > > >> > > >> > > >> I am not sure, but Daisy might already think so Daisy only > moved > > >> > from > > >> > > >> .../ko_KR to .../team/ko_KR, and > > >> > > >> did not include "<languages />" tag on [1] :) > > >> > > >> > > >> > > >> This is just my suggestion not to conflict with your team > and to > > >> > > >> accomplish our team requirement, > > >> > > >> and I would like to listen Daisy's opinion and other > language > > >> > teams' > > >> > > >> opinions. > > >> > > >> > > >> > > >> [1] https://wiki.openstack.org/wiki/I18nTeam > > >> > > >> [2] https://wiki.openstack.org/wiki/ReleaseNotes/Liberty > > >> > > >> > > >> > > >> > > >> > > >> With many thanks, > > >> > > >> > > >> > > >> /Ian > > >> > > >> > > >> > > >> Akihiro Motoki wrote on 11/10/2015 8:48 PM: > > >> > > >> > In addition, Japanese team maintains the original > contents which > > >> > > >> > are differ from the English version of I18nTeam page. > > >> > > >> > Before enabling translation for I18nTeam, I would like > to see a > > >> > solution > > >> > > >> > for language specific content. > > >> > > >> > > > >> > > >> > > > >> > > >> > 2015-11-10 20:45 GMT+09:00 Akihiro Motoki > <amotoki(a)gmail.com>: > > >> > > >> >> I noticed the existing language team page cannot be edited. > > >> > > >> >> For example, > https://wiki.openstack.org/wiki/I18nTeam/ja exists > > >> > from > > >> > > >> >> more than one year ago. > > >> > > >> >> After this change, we can no longer edit the original page. > > >> > > >> >> What should we do? > > >> > > >> >> > > >> > > >> >> In addition, I18nTeam wiki page contains contents which > is not > > >> > > >> >> appropriate for translation, > > >> > > >> >> for example, "Local Translation Teams" section. > > >> > > >> >> As a local team coordinator, I don't like to display this > > >> > section in a > > >> > > >> >> translated version. > > >> > > >> >> > > >> > > >> >> Thanks, > > >> > > >> >> Akihiro > > >> > > >> >> > > >> > > >> >> 2015-11-10 18:11 GMT+09:00 Ying Chun Guo > <guoyingc(a)cn.ibm.com>: > > >> > > >> >>> Hi, > > >> > > >> >>> > > >> > > >> >>> As requested by Korean team, the wiki page of I18nTeam is > > >> > > >> translatable now. > > >> > > >> >>> If you want to translate this page into your own language, > > >> > > >> please go ahead. > > >> > > >> >>> Thank you. > > >> > > >> >>> > > >> > > >> >>> Best regards > > >> > > >> >>> Ying Chun Guo (Daisy) > > >> > > >> >>> > > >> > > >> >>> > > >> > > >> >>> _______________________________________________ > > >> > > >> >>> Openstack-i18n mailing list > > >> > > >> >>> Openstack-i18n(a)lists.openstack.org > > >> > > >> >>> > > >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n > > >> > > >> >>> > > >> > > >> > _______________________________________________ > > >> > > >> > Openstack-i18n mailing list > > >> > > >> > Openstack-i18n(a)lists.openstack.org > > >> > > >> > > > >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n > > >> > > >> > > >> > > >> -- > > >> > > >> /Ian > > >> > > >> > > >> > > > > > >> > > > > >> > > > >> > > > >> > > > >> > _______________________________________________ > > >> > Openstack-i18n mailing list > > >> > Openstack-i18n(a)lists.openstack.org > > >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n > > >> > > > >> > > > > > >

1 0

Re: [Openstack-i18n] I18n wiki page is translatable
by Akihiro Motoki 12 Nov '15

12 Nov '15

Hi Daisy, I move all team wiki pages to I18nTeam/team/xxxxx. In addition, I created a page https://wiki.openstack.org/wiki/I18nTeam/team which contains a list of language teams. Akihiro 2015-11-12 16:04 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > Thank you Tom. > Sorry for the trouble. > I will move all the team wiki pages to different links. > > Best regards > Ying Chun Guo (Daisy) > > > Tom Fifield <tom(a)openstack.org> wrote on 2015/11/12 07:43:39: > >> From: Tom Fifield <tom(a)openstack.org> >> To: Ying Chun Guo/China/IBM@IBMCN, Akihiro Motoki <amotoki(a)gmail.com> >> Cc: Openstack-i18n <openstack-i18n(a)lists.openstack.org> >> Date: 2015/11/12 07:43 > > >> Subject: Re: [Openstack-i18n] I18n wiki page is translatable >> >> Hi, >> >> Sorry, it took a while to work out how to disable the translations. >> That's been done now. >> >> >> Regards, >> >> >> Tom >> >> On 11/11/15 18:09, Ying Chun Guo wrote: >> > I think we need to disable the translation at first. >> > Then we could be able to move them. >> > I'm not able to move, same as you. >> > >> > Best regards >> > Ying Chun Guo (Daisy) >> > >> > >> > Akihiro Motoki <amotoki(a)gmail.com> wrote on 2015/11/11 14:40:43: >> > >> > > From: Akihiro Motoki <amotoki(a)gmail.com> >> > > To: Ying Chun Guo/China/IBM@IBMCN >> > > Cc: "Ian Y. Choi" <ianyrchoi(a)gmail.com>, Openstack-i18n <openstack- >> > > i18n(a)lists.openstack.org> >> > > Date: 2015/11/11 15:05 >> > > Subject: Re: [Openstack-i18n] I18n wiki page is translatable >> > > >> > > Daisy, >> > > >> > > It sounds good to me, but normal users like me cannot move pages. >> > > I got Permission Error. Could you handle all moving of pages? >> > > >> > > >> > > 2015-11-11 15:05 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: >> > > > Thank you for the explain Ian. >> > > > I think we could move the wiki pages for language teams to >> > > > /I18nTeam/team/<language-code>, >> > > > and then keep /I18nTeam/<language-code> for the translation page of >> > > > I18nTeam. >> > > > >> > > > How do you think about it, Akihiro? >> > > > >> > > > Best regards >> > > > Ying Chun Guo (Daisy) >> > > > >> > > > >> > > > "Ian Y. Choi" <ianyrchoi(a)gmail.com> wrote on 2015/11/11 00:55:07: >> > > > >> > > >> From: "Ian Y. Choi" <ianyrchoi(a)gmail.com> >> > > >> To: Akihiro Motoki <amotoki(a)gmail.com>, Ying Chun >> > Guo/China/IBM@IBMCN >> > > >> Cc: Openstack-i18n <openstack-i18n(a)lists.openstack.org> >> > > >> Date: 2015/11/11 00:55 >> > > >> Subject: Re: [Openstack-i18n] I18n wiki page is translatable >> > > > >> > > > >> > > >> >> > > >> Hello Akihiro, >> > > >> >> > > >> Actually I suggested a translatable I18nTeam wiki page [1] for >> > Korean >> > > >> during last Tokyo Design Summit. >> > > >> After saying it, I found that there might be a problem in Japanese >> > local >> > > >> team >> > > >> because Japanese language team already used /ja page, as you >> > mentioned and >> > > >> which would make conflict with translation functionality in >> > OpenStack >> > > >> wiki. >> > > >> >> > > >> Let me first say why Korean translation page for I18nTeam is >> > needed and >> > > >> how Korean translation team wants to use two wiki pages >> > separately: >> > > >> >> > > >> 1) https://wiki.openstack.org/wiki/I18nTeam/ko >> > > >> : To provide Korean guys with official I18nTeam introduction >> > wiki page >> > > >> : I think "Local Translation Teams" section is needed because >> > this >> > > >> information is >> > > >> beneficial with the knowledge of the various language team >> > activities. >> > > >> >> > > >> 2) https://wiki.openstack.org/wiki/I18nTeam/team/ko_KR >> > > >> (I found that Daisy moved from .../ko_KR to .../team/ko_KR. >> > Thank you!) >> > > >> : To introduce Korean translation team with details and our >> > specific >> > > >> translation rules >> > > >> : Providing links for OpenStack I18n official introduction wiki >> > page & >> > > >> its translation >> > > >> >> > > >> I would like to respect I18nTeam official wiki page, and this >> > > >> information is written in English. >> > > >> In my opinion, translating this page would more clearly advertise >> > > >> OpenStack I18n overall activities to more Korean. >> > > >> >> > > >> This requirement and need might be different from various local >> > > >> translation teams, I think, >> > > >> and I also would like to respect the ways Japanese team used more >> > than 1 >> > > >> year. >> > > >> >> > > >> So I would like to suggest not to include "<languages />" tag on >> > [1] . >> > > >> As you know, OpenStack Release Note wiki pages such as [2] >> > > >> contain "<languages />" tag and displays different language >> > translated >> > > >> pages on the top part. >> > > >> >> > > >> I think this suggestion would satisfy different needs from various >> > > >> language translation teams. >> > > >> However, if https://wiki.openstack.org/wiki/I18nTeam page includes >> > > >> "<languages />" tag, >> > > >> then it would not fit to not only Japanese translation team, but >> > also >> > > >> other teams such as French, Polish and so on. >> > > >> For Korean translation team, our official page contains the >> > translated >> > > >> I18nTeam link so it would be okay. >> > > >> >> > > >> I am not sure, but Daisy might already think so Daisy only moved >> > from >> > > >> .../ko_KR to .../team/ko_KR, and >> > > >> did not include "<languages />" tag on [1] :) >> > > >> >> > > >> This is just my suggestion not to conflict with your team and to >> > > >> accomplish our team requirement, >> > > >> and I would like to listen Daisy's opinion and other language >> > teams' >> > > >> opinions. >> > > >> >> > > >> [1] https://wiki.openstack.org/wiki/I18nTeam >> > > >> [2] https://wiki.openstack.org/wiki/ReleaseNotes/Liberty >> > > >> >> > > >> >> > > >> With many thanks, >> > > >> >> > > >> /Ian >> > > >> >> > > >> Akihiro Motoki wrote on 11/10/2015 8:48 PM: >> > > >> > In addition, Japanese team maintains the original contents which >> > > >> > are differ from the English version of I18nTeam page. >> > > >> > Before enabling translation for I18nTeam, I would like to see a >> > solution >> > > >> > for language specific content. >> > > >> > >> > > >> > >> > > >> > 2015-11-10 20:45 GMT+09:00 Akihiro Motoki <amotoki(a)gmail.com>: >> > > >> >> I noticed the existing language team page cannot be edited. >> > > >> >> For example, https://wiki.openstack.org/wiki/I18nTeam/ja exists >> > from >> > > >> >> more than one year ago. >> > > >> >> After this change, we can no longer edit the original page. >> > > >> >> What should we do? >> > > >> >> >> > > >> >> In addition, I18nTeam wiki page contains contents which is not >> > > >> >> appropriate for translation, >> > > >> >> for example, "Local Translation Teams" section. >> > > >> >> As a local team coordinator, I don't like to display this >> > section in a >> > > >> >> translated version. >> > > >> >> >> > > >> >> Thanks, >> > > >> >> Akihiro >> > > >> >> >> > > >> >> 2015-11-10 18:11 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: >> > > >> >>> Hi, >> > > >> >>> >> > > >> >>> As requested by Korean team, the wiki page of I18nTeam is >> > > >> translatable now. >> > > >> >>> If you want to translate this page into your own language, >> > > >> please go ahead. >> > > >> >>> Thank you. >> > > >> >>> >> > > >> >>> Best regards >> > > >> >>> Ying Chun Guo (Daisy) >> > > >> >>> >> > > >> >>> >> > > >> >>> _______________________________________________ >> > > >> >>> Openstack-i18n mailing list >> > > >> >>> Openstack-i18n(a)lists.openstack.org >> > > >> >>> >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n >> > > >> >>> >> > > >> > _______________________________________________ >> > > >> > Openstack-i18n mailing list >> > > >> > Openstack-i18n(a)lists.openstack.org >> > > >> > >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n >> > > >> >> > > >> -- >> > > >> /Ian >> > > >> >> > > > >> > > >> > >> > >> > >> > _______________________________________________ >> > Openstack-i18n mailing list >> > Openstack-i18n(a)lists.openstack.org >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n >> > >> >

2 1

What's Up, Doc? 13 November 2015
by Lana Brindley 12 Nov '15

12 Nov '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone, Well, things are starting to ramp up again after Summit. This week, I've spent some time catching up with other PTLs, and also worked on the DocImpact spec. I've also implemented my plan to get the Speciality Team leads to provide content on their projects individually, so many thanks to them for replying with so much great info! == Progress towards Mitaka == 145 days to go! 100 bugs closed so far for this release. DocImpact * I've updated the spec and made contact with Infra to nut out the finer technical details: https://blueprints.launchpad.net/openstack-manuals/+spec/review-docimpact RST Conversions * Arch Guide ** https://blueprints.launchpad.net/openstack-manuals/+spec/archguide-mitaka-r… ** Contact the Ops Guide Speciality team: https://wiki.openstack.org/wiki/Documentation/OpsGuide * Ops Guide ** https://blueprints.launchpad.net/openstack-manuals/+spec/ops-guide-rst ** Lana will reach out to O'Reilly to discuss the printed book before this work begins * Config Ref ** Contact the Config Ref Speciality team: https://wiki.openstack.org/wiki/Documentation/ConfigRef * Virtual Machine Image Guide ** https://blueprints.launchpad.net/openstack-manuals/+spec/image-guide-rst and https://review.openstack.org/#/c/244598/ Reorganisations * Arch Guide ** https://blueprints.launchpad.net/openstack-manuals/+spec/archguide-mitaka-r… ** Contact the Ops Guide Speciality team: https://wiki.openstack.org/wiki/Documentation/OpsGuide * User Guides ** https://blueprints.launchpad.net/openstack-manuals/+spec/user-guides-reorga… ** Contact the User Guide Speciality team: https://wiki.openstack.org/wiki/User_Guides Document openstack-doc-tools and reorganise index page * Thanks to Brian for volunteering to take this on! Horizon UX work * There's an interesting opportunity to improve the wording in Horizon, specifically around LBaaS, and also to develop a set of standards around the language used in the dashboard. If you're interested, let me know and I'll get you in contact with the right people. == Speciality Teams == '''HA Guide - Bogdan Dobrelya''' Created a poll to shift HA guide IRC meeting time (http://lists.openstack.org/pipermail/openstack-docs/2015-November/007830.ht…) Submitted a status for HA guide testing (http://lists.openstack.org/pipermail/openstack-docs/2015-October/007718.html) hoping to see more participants in testing. Trying to push few patches, and initiated related discussion: https://review.openstack.org/#/c/225418/ and https://review.openstack.org/235893. Thinking on how to effectively collaborate with Adam Spiers and his Openstack HA initiative (http://lists.openstack.org/pipermail/openstack-dev/2015-November/079127.html) to benefit HA guide project as well. '''Installation Guide - Christian Berendt''' Moved the team meeting from Google Hangout to IRC (online at http://eavesdrop.openstack.org/#Documentation_Install_Team_Meeting) we had our first team meeting on the IRC (http://eavesdrop.openstack.org/meetings/docinstallteam/2015/docinstallteam.…) we discussed the inclusion of hypervisor specific appendixes, no consensus at the moment, really good progress on the Debian install guide, zigo is doing a good job. '''Networking Guide - Edgar Magana''' We have a new spec for OVN: https://review.openstack.org/#/c/244367/ I am going to start pulling people into specific patches. '''Security Guide - Nathaniel Dillon''' We have added a new chapter on Manila and have completed the reworking of the case studies. '''User Guides - Joseph Robinson''' Our meeting format has changed from hangouts to IRC meetings, with the appropriate changes made to the meetbot script thanks to Brian. The mitaka specification: the priority at the moment is checking in with project docs liaisons to confirm what services are in scope, and then add a short statement to the specification outlining this scope. Responding to Cloud Admin Guide patches. Thanks to Andreas for the link. '''Ops and Arch Guides - Shilla Saebi''' The operations guide RST migration is on hold until we find out if we are going to move forward with docbook or RST. In the meantime we are looking to add content and update it. The architecture guide RST conversion is underway. The progress on chapters and pages can be checked via the wiki page: https://wiki.openstack.org/wiki/Documentation/Migrate '''API Docs - Anne Gentle''' Russell Sim plans to revise the templates for developer.openstack.org landing page to better match docs.openstack.org. We'll also map out a plan for fairy-slipper and the WADL migration. Spec to be updated soon. '''Config Ref - Gauvain Pocentek''' The initial structure for the Config Reference RST migration is up, the automation tools are ready to handle RST tables generation, and a couple pages have already been converted. We're waiting for the liberty branching to start pushing more converted pages. '''Training labs - Pranav Salunke''' Added Kilo support, still under review but in final stages (https://review.openstack.org/#/c/237061/) Halfway through adding KVM support, will probably need more time. Other small things like fixing readmes etc. Still pending to decide IRC meeting time. '''Training Guides - Matjaz Pancur''' Two new core reviewers: Kato Tomoyuki and Tim Freund. We also added a new policy for cores: current lead of Upstream training session (held before each Summit) is now part of the core team by function. '''Hyperviser Tuning Guide - Joe Topjian''' All data from the past etherpads have been compiled onto the wiki (https://wiki.openstack.org/wiki/Documentation/HypervisorTuningGuide) My goal right now is to translate the raw notes into something more readable. Once the page starts to resemble a readable guide, I'll try to rally others to join in. == Doc team meeting == We held the APAC docs meeting this week, you can read the minutes here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2015-11-11 Next meetings: US: Wednesday 18 November, 14:00 UTC APAC: Wednesday 25 November, 00:30:00 UTC Please go ahead and add any agenda items to the meeting page here: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_mee… - -- Keep on doc'ing! Lana - -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJWRWXhAAoJELppzVb4+KUyE5IH/AjYER1GXxR7IE0zz8uIsfqx rkgm7tJDz5uPZaJr5taXJFtZRiYomZKrZNQ+ijDSt770lUApunr5Q/gkQLrnIyBr GVZPmsmv8duj6vYYDgIlDNwfaE7BtsCE5Cqvcg+rE8+MpWwFp66I8/AcJ2g0Ez2I qQZ/mfsWfURAU2rZssBSh4sSl+t90C2TBRYPA2kH45zfyBXKxqXH5q1uFE9XFUwS BgiUUpFewnAZM+r+dR/efyN/brLUfmI0UkczrazAngq1HsytXBEhxgI7/LJ/xC29 ZA5R11eppGyS3y/6dUvBFVlVLrDm324DPNJD4ykU7eCRJbCUsd4rekD/08UXCeo= =K6gD -----END PGP SIGNATURE-----

1 0

I18n Guide publication
by KATO Tomoyuki 12 Nov '15

12 Nov '15

Hi team, We have published the I18n Guide [1]. The more contents are coming. Also, your contribution is very welcome, feel free to send a patch. For details, see the blueprint [2] and patch review requests [3]. [1] http://docs.openstack.org/developer/i18n/ [2] https://blueprints.launchpad.net/openstack-i18n/+spec/i18n-contributor-guide [3] https://review.openstack.org/#/q/status:open+project:openstack/i18n,n,z Thanks, KATO Tomoyuki

3 4

Terminologies in repo
by Ying Chun Guo 11 Nov '15

11 Nov '15

Hello, team I have submitted a patch to our repo for review, containing all the terminologies and translations we made. https://review.openstack.org/244031 I want to discuss about how to handle these assets we made. Currently, I use a google doc to store the terms and the translations. https://docs.google.com/spreadsheets/d/1BRizUNhDLl_6NtsGconFkxsKUqAmEEGum9I… I want to move these assets to our repo. My plan is to use pot and po files to store the terms and the translations. Then create a project named as "terminology" in Zanata, and create auto jobs to manage the synchronization between i18n repo and Zanata. So the process to update terms are: - If a people wants to add a new term to the terminology, submit a patch to i18n repo to change the original term.pot file. - If a people want to update a translation of a term, go to Zanata to update the translation. Let me know your thoughts to my design. Thank you. Best regards Ying Chun Guo (Daisy)

5 6