- OpenStack-I18n - lists.openstack.org

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

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

11 Nov '15

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 >> >

3 3

Re: [Openstack-i18n] I18n wiki page is translatable
by Ian Y. Choi 11 Nov '15

11 Nov '15

Thank you so much, Daisy and Akihiro! I also hope that everything runs so well. With many thanks, /Ian Ying Chun Guo wrote on 11/11/2015 4:09 PM: > > 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 > > >> > > > > > >

1 0

I18n wiki page is translatable
by Ying Chun Guo 10 Nov '15

10 Nov '15

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)

3 6

Granting access for a new translator for the finnish (finland) translation project
by Jori Kuusinen 10 Nov '15

10 Nov '15

Hi all i18n mailing list members, I registered myself for the finnish (finland) translation project page and would like to have myself granted as a contributor. As a global project owner, I think "Daisy" is in charge for granting access if I'm not mistaken. Looking forward to begin contributing for the project. With kind regards, J o r i

1 0

FYI: [openstack-dev] [release] new change management tools and processes for stable/liberty and mitaka
by KATO Tomoyuki 08 Nov '15

08 Nov '15

FYI. KATO Tomoyuki ---- As we discussed at the summit, the release management team is modifying our change management tracking tools and processes this cycle. This email is the official announcement of those changes, with more detail than we provided at the summit. In past cycles, we have used a combination of Launchpad milestone pages and our wiki to track changes in releases. We used to pull together release notes for stable point releases at the time of release. Most of that work fell to the stable maintenance and release teams. Similarly, the release managers worked with PTLs and release liaisons at each milestone checkpoint to update Launchpad to accurately reflect the work completed at each stage of development. It's a lot of work to fix up Launchpad and assemble the notes and make sure they are accurate, which has caused us to be a bottleneck for clear and complete communication at the time of the release. We have been looking for ways to reduce that effort for these tasks and eliminate the bottleneck for some time. This cycle, to address these problems for our ever-growing set of projects, the release management team is introducing a new tool for handling release notes as files in-tree, to allow us to simply and continuously build the release notes for stable branch point releases and milestones on the master branch. The idea is to use small YAML files, usually one per note or patch, to avoid merge conflicts on backports and then to compile those files in a deterministic way into a more readable document for readers. Files containing release notes can be including in patches directly, or you can create a separate patch with release notes if you want to document a feature than spans several patches. The tool is called Reno, and it currently supports ReStructuredText and Sphinx for converting note input files to HTML for publication. Reno is git branch-aware, so we can have separate release notes documents for each release series published together from the master build. The documentation for Reno, including design principles and basic usage instructions, is available at [1]. For now we are focusing on Sphinx integration so that release notes are published online. We will add setuptools integration in a future version of Reno so that the release notes can be built with the source distribution. As part of this rollout, I will also be updating the settings for the gerrit hook script so that when a patch with "Closes-Bug" in the commit message is merged the bug will be marked as "Fix Released" instead of "Fix Committeed" (since "Fix Committed" is not a closed state). When that work is done, I'll send another email to let PTLs know they can go through their existing bugs and change their status. We are ready to start rolling out Reno for use with Liberty stable branch releases and in master for the Mitaka release. We need the release liaisons to create and merge a few patches for each project between now and the Mitaka-1 milestone. 1. We need one patch to the master branch of the project to add the instructions for publishing the notes as part of the project sphinx documentation build. An example patch for Glance is in [2]. 2. We need another patch to the stable/liberty branch of the project to set up Reno and introduce the first release note for that series. An example patch for Glance is in [3]. 3. Each project needs to turn on the relevant jobs in project-config. An example patch using Glance is in [4]. New patches will need to be based on the change that adds the necessary template [5], until that lands. 4. Reno was not ready before the summit, so we started by using the wiki for release notes for the initial Liberty releases. We also need liaisons to convert those notes to reno YAML files in the stable/liberty branch of each project. Please use the topic "add-reno" for all patches so we can track adoption. Once those merge, project teams can stop using Launchpad for tracking completed work. We will still use Launchpad for bug reports, for now. If a team wants to continue using it for tracking blueprints, that's fine. If a team wants to use Launchpad for scheduling work to be done in the future, but not for release tracking, that is also fine. The release management team will no longer be reviewing or updating Launchpad as part of the release process. Thanks, Doug [1] http://docs.openstack.org/developer/reno/ [2] https://review.openstack.org/241323 [3] https://review.openstack.org/241322 [4] https://review.openstack.org/241344 [5] https://review.openstack.org/241343 __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

1 0

What's Up, Doc? 6 November 2015
by Lana Brindley 05 Nov '15

05 Nov '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone, Wow! What a great Summit! And isn't Tokyo a truly beautiful and amazing city? Thank you so much to the Japanese Stackers who hosted us, and to everyone who came along to the docs sessions and helped us hammer out a great plan for Mitaka. I'm very excited about this release! This week, I've been catching up with everything that happened during Summit, and also working on outreach tasks. Today, I recorded an interview with Foundation about the project, and I've also published a blog post on the same topic, which will be published soon. You might also like to check out the Superuser interview Anne and I did about the docs while we were in Tokyo: http://superuser.openstack.org/articles/openstack-documentation-why-it-s-im… == Progress towards Mitaka == 152 days to go! 77 bugs closed so far for this release. API Docs * The API docs are will be switched to swagger: http://specs.openstack.org/openstack/docs-specs/specs/liberty/api-site.html DocImpact * I've removed the WIP from this blueprint, and will be working on this from next week: 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 ** Thanks for all the offers of help on this one! Please contact the Config Ref Speciality team: https://wiki.openstack.org/wiki/Documentation/ConfigRef 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 Training * Labs ** https://blueprints.launchpad.net/openstack-manuals/+spec/training-labs * Guides ** Upstream University & 'core' component updates, EOL Upstream Wiki page. Document openstack-doc-tools * Need volunteers for this! Reorganise index page * The API docs have already moved off the front page * We need volunteers to look at the organisation of this page and to write one-sentence summaries of each book == Doc team meeting == Meetings will kick off again next week with the APAC meeting: APAC: Wednesday 11 November, 00:30:00 UTC US: Wednesday 18 November, 14: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/ iQEcBAEBCAAGBQJWPC4TAAoJELppzVb4+KUynpUH/30Y6pv7Zrse+YM1ki2pqLqi dp0f9RysJQkvXOA7OWy48kWLWXgMF0/hq1DIhrZ9AlsUCGOGC04/YVGNyaCAxMkx TTpyi6gJWl9Fiwbrc6k63MPx7OMFDcGu8KQow7tCBewH0jYngiJeP/mxIP6AnhBy SHVsZZ4OG99w/xZyUe8rVGkpXLFUfow8u0r4hCLlFGSUxLD3jz8ABp2HX7mf3ICi 0u1rgxD08lWSHPHRmhzUZ+kx7uW1ZY0UWiX1rsyTU690dsYbYeJSUcY+Saf2md52 eIGk7yevZaYczXvn9vo/rfwZCc4G5jyRFp55yR/BfD/2NVsjmt2vvguWTnDywEE= =Y0ik -----END PGP SIGNATURE-----

1 0

IRC meeting tomorrow
by Ying Chun Guo 04 Nov '15

04 Nov '15

1 0

mark as read-only policy
by KATO Tomoyuki 01 Nov '15

01 Nov '15

Hi Daisy, Today, I found some projects are translable at both master and stable-liberty branch. In my understand, only one branch should be translable. Just a example,I do not check all projects. * ironic * ceilometer Regards, KATO Tomoyuki

3 6

magnum-ui translation setup
by Andreas Jaeger 31 Oct '15

31 Oct '15

Steve and myself have been working on fixing the broken translation for magnum-ui. I didn't notice that it uses *two* pot files like horizon (one for python files, one for javascript) and uses as well a django and djangojs file and thus wrote these: https://review.openstack.org/#/c/240650/ https://review.openstack.org/#/c/240651/ Will these duplicated names - django in both horizon and magnum-ui - cause any problems in the running system? I doubt it since already horizon has *two* different django files but wanted to double check - and ask for review of the above. I think we need to use this setup for other dashboard related projects, so also for designate-dashboard. Reviews and comments are welcome, 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

1 0