- OpenStack-I18n - lists.openstack.org

Lao Localization
by Saikeo Kavhanxay 26 Sep '16

26 Sep '16

Hi localization team, I am interested to localize OpenStack into my language. Currently Lao localization team is not available on OpenStack yet. I want to open it and start translate. Please suggest me how to localize OpenStack. Thank you. Best regards, Saikeo Network and System Engineer IT Dept., APB Laos [ccna_routerswitching_sm][jn_certified_associate_rgb]

4 10

Re: [OpenStack-I18n] [openstack-community] Chinese Ask OpenStack
by Ian Y. Choi 24 Sep '16

24 Sep '16

Hello Stefano! First of all, sorry for my late reply from your kind comment. (Recently I have been thinking a lot inside my brain, but most ideas are still in my head..) Thank you very much for sharing with much details. Although it has been less than 2 years since I participated in as a OpenStack Korean group organizer, I have seen lots of kind and enormous efforts and communications from you and Tom during my community activities. I really appreciate such great help and support, especially for non-English members from you and Tom, and also so many community members. I agree that ask.o.o is also an open source, and in my opinion, we, as community organizers and leaders, can encourage local developers and operators to more participate in building and maintaining ask.o.o for their languages. I really hope that more local communities will be vitalized through lots of interesting activities : not only local meetups, but also grouped development activities and more participation in OpenStack contribution including infra-side management. My actions for building Korean ask.o.o may be slow, since recently I applied to I18n Ocata PTL. but I would happily like to keep on investigating my time for building Korean ask.o.o steadily. And for I18n team, the cross-relationship with other official project teams is important, but encouraging more local language translator participation is also another significant aspect to make OpenStack ubiquitously accessible. I really want to find nice approaches how local translators will get more involved in translation with local community activities. If someone has a good idea on such perspective, feel free to kindly share opinions :) (So for this reason and FYI, I am copying my mail thread to openstack-i18n(a)lists.openstack.org) With many thanks, /Ian Stefano Maffulli wrote on 9/14/2016 3:48 PM: > On 09/11/2016 12:09 AM, Ian Y. Choi wrote: >> I am one of OpenStack Korea user group organizers. >> >> On the other hand, I really wanted to open ask.o.o for Korean >> (e.g., ask.openstack.org/ko/questions ) but I am not familiar how I can >> create or request this site. > I can elaborate on this topic, since I have followed the initial steps > of Ask OpenStack when it launched. That site exists partially because > StackExchange denied OpenStack to create something like ask.ubuntu.com > for us, and partially because I really wanted to have ask.openstack.org > in multiple languages. > > During my tenure as community manager, the Foundation sponsored the > improvement of the support for non-latin alphabets, with Chinese, > Japanese and Korean as first targets. > > But once we launched the site in Chinese, we realized that the way we > managed the site, we couldn't add more languages without increasing > dramatically the risk of breaking everything. The resources to fix the > situation were never enough to make a dramatic impact and therefore the > site has been making slow progress over the years, focusing on > stability, operational solidity and spam-prevention/fix. > > Despite having an extremely high ranking on search engines for common > openstack issues in English, ask.openstack.org never had enough > development resources to grow to the other languages. > >> So my general idea is to support more languages on ask.o.o, and >> encourage more OpenStack members to use ask.o.o globally. > I think this is still a very fair request but the answer can only be in > the Foundation or volunteers in the community, since the whole software > and infrastructure behind ask.openstack.org is open source. Languages > can be added and tested on the staging site quite easily... in theory at > least (the documentation is a bit sparse, with > http://askbot.org/doc/multilingual.html#multilingual and > http://askbot.org/doc/text-search.html#text-search being a starting > point)... but once you activate Korean language, then you'll have a > whole new site to manage... and I'm not sure what resources will be > available to fix bugs that inevitably will pop up. > > /stef > > _______________________________________________ > Community mailing list > Community(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/community

1 0

What's Up, Doc? 23 September
by Lana Brindley 23 Sep '16

23 Sep '16

Hi everyone, Newton goes out in just two weeks, and the release team and I have been busy working through release tasks in preparation. Don't forget that you can contact any of us (or just send mail to the docs mailing list) if you have any questions about the Newton docs release. I'm also pleased to announce that I have been returned as the documentation PTL for Ocata, which will be my fourth term. Thanks for all the support! == Progress towards Newton == 12 days to go! Bugs closed so far: 455 Release managers: Olena Logvinova and Alexandra Settle Release tasks are being tracked here: https://etherpad.openstack.org/p/NewtonRelease Install Guide testing is being tracked here: https://wiki.openstack.org/wiki/Documentation/NewtonDocTesting == The Road to Barcelona == * I have a draft schedule starting to take shape, which you can see here: https://etherpad.openstack.org/p/Ocata-DocsSessions I'll put this into Sched once the tool becomes available, and your early feedback is welcome. Additionally, if you're interested in moderating a session in Barcelona, please let me know. * By now, you should be well on the way to having your travel and accommodation booked for Barcelona. In case you're still working on it, though, there's travel information available on the Summit site here: https://www.openstack.org/summit/barcelona-2016/travel/ * Looking a little further forward, Foundation have now announced that the first Project Team Gathering (PTG) will be held in Atlanta, US, on Feb 20-24: http://www.openstack.org/ptg == Doc team meeting == Next meetings: The APAC meeting was skipped this week. Next meetings: US: Wednesday 28 September, 19:00 UTC APAC: Wednesday 5 October, 00:30 UTC These two meetings will be the final meetings before release day. 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 https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#23_September_2016 -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com

1 0

UNOFFICIAL horizon check site
by Akihiro Motoki 23 Sep '16

23 Sep '16

Hi, The official translation check site is not planned for Newton, so I set up an unofficial horizon translation check site for Japanese team. There is no reason not to share it to the community. URL: http://v157-7-133-23.myvps.jp/dashboard Username: 'demo' or 'admin' Password: b2949da771d1 * The site is updated manually and occasionally when I want to. * Only core services (+ Heat) are covered. No additional services are covered. * The site will be closed or switched to Ocata sometime after Newton release is shipped. No announcement is planned. * The site is sometimes used for development purpose. * This is a voluntary site. Do not ask me to update :) Akihiro

5 7

[Bug 1587221] [NEW] openstack-manuals stable-mitaka releasenotes on Zanata looks unnecessary
by Akihiro Motoki 20 Sep '16

20 Sep '16

Public bug reported: As we discussed at Austin, only the master version is required for release notes translation on Zanata. Zanata currently has openstack- manuals stable-mitaka releasenotes resource. It looks unnecessary. ** Affects: openstack-i18n Importance: Undecided Status: New ** Tags: infra -- You received this bug notification because you are a member of OpenStack I18n Core Team, which is subscribed to openstack i18n. https://bugs.launchpad.net/bugs/1587221 Title: openstack-manuals stable-mitaka releasenotes on Zanata looks unnecessary Status in openstack i18n: New Bug description: As we discussed at Austin, only the master version is required for release notes translation on Zanata. Zanata currently has openstack- manuals stable-mitaka releasenotes resource. It looks unnecessary. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1587221/+subscriptions

2 1

[Bug 1571100] Re: 技术因素 in OpenStack 架构设计指南 - 当前最新
by Ian Y. Choi 20 Sep '16

20 Sep '16

Hmm.. I cannot check "Won't fix". Instead, I will triage as "Opinion". ** Changed in: openstack-i18n Status: Confirmed => Opinion -- You received this bug notification because you are a member of OpenStack I18n Core Team, which is subscribed to openstack i18n. https://bugs.launchpad.net/bugs/1571100 Title: 技术因素 in OpenStack 架构设计指南 - 当前最新 Status in openstack i18n: Opinion Bug description: Error "Redia"是一个key-value存储系统 Redis是一个key-value存储系统 ----------------------------------- Built: 2015-11-24T07:19:53 00:00 git SHA: ed0b07948cdc10b7fb962ec8aba3c3cb299fe053 URL: http://docs.openstack.org/zh_CN/arch-design/content/technical-consideration… source File: file:/home/jenkins/workspace/openstack-manuals-tox-doc-publishlang/generated/zh_CN/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml xml:id: technical-considerations-general-purpose To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1571100/+subscriptions

1 0

[Bug 1535172] Re: Wrong typesetting in Chinese OpenStack Mitaka and master install doc
by Ian Y. Choi 20 Sep '16

20 Sep '16

Thanks a lot for your comment, Shengjing! ** Summary changed: - Wrong typesetting in Chinese OpenStack Liberty install doc + Wrong typesetting in Chinese OpenStack Mitaka and master install doc ** Changed in: openstack-i18n Status: Confirmed => Fix Released -- You received this bug notification because you are a member of OpenStack I18n Core Team, which is subscribed to openstack i18n. https://bugs.launchpad.net/bugs/1535172 Title: Wrong typesetting in Chinese OpenStack Mitaka and master install doc Status in openstack i18n: Fix Released Bug description: Extra underline in the doc. The translated link is http://docs.openstack.org/liberty/zh_CN/install-guide-rdo/glance-install.ht… The original doc link is http://docs.openstack.org/liberty/install-guide-rdo/glance-install.html The picture is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1535172/+subscriptions

1 0

[Bug 1608992] [NEW] [api-quick-start] Some old translated pages are still being seen
by Ian Y. Choi 20 Sep '16

20 Sep '16

Public bug reported: Previously, API quick start documentation was xml-based format (with maven build). Since all the API quick start content is written as RST format now, docs.openstack.org/api/quick-start/ url is redirected to current API quick start URL like http://developer.openstack.org/api-guide/quick-start/index.html . I have found some of current problems which can be interpreted as bugs: - Not all translated RST documentation is visible : Although current translation is ~100% in Chinese (zh_CN), http://docs.openstack.org/zh_CN/api/quick-start/content/index.html (xml based) is okay, but http://developer.openstack.org/zh_CN/api-guide/quick-start/ url is not working. - No redirection to rst based documentation : For example, when users enter the previous Japanese API quick-start using docs.openstack.org/ja/api/quick-start/ , the old page is still being seen. On the other hand, English docs.openstack.org/api/quick-start url is redirected to current API quick start URL like http://developer.openstack.org/api-guide/quick-start/index.html . - Even though translation progress seems to be good, there is no rst- based generated documentation for zh_CN (Chinese) and id (Indonesia) So, currently, my approach to address this bug is: 1) Identify which languages have good progress on api-quick-start translation 2) Include that those languages need to build 3) After checking the documentation result on public web pages, we need to add url redirection. ** Affects: openstack-api-site Importance: Undecided Assignee: Ian Y. Choi (ianychoi) Status: In Progress ** Affects: openstack-i18n Importance: Undecided Assignee: Ian Y. Choi (ianychoi) Status: New ** Also affects: openstack-api-site Importance: Undecided Status: New ** Changed in: openstack-api-site Assignee: (unassigned) => Ian Y. Choi (ianychoi) ** Changed in: openstack-i18n Assignee: (unassigned) => Ian Y. Choi (ianychoi) -- You received this bug notification because you are a member of OpenStack I18n Core Team, which is subscribed to openstack i18n. https://bugs.launchpad.net/bugs/1608992 Title: [api-quick-start] Some old translated pages are still being seen Status in openstack-api-site: In Progress Status in openstack i18n: New Bug description: Previously, API quick start documentation was xml-based format (with maven build). Since all the API quick start content is written as RST format now, docs.openstack.org/api/quick-start/ url is redirected to current API quick start URL like http://developer.openstack.org/api-guide/quick-start/index.html . I have found some of current problems which can be interpreted as bugs: - Not all translated RST documentation is visible : Although current translation is ~100% in Chinese (zh_CN), http://docs.openstack.org/zh_CN/api/quick-start/content/index.html (xml based) is okay, but http://developer.openstack.org/zh_CN/api-guide/quick-start/ url is not working. - No redirection to rst based documentation : For example, when users enter the previous Japanese API quick-start using docs.openstack.org/ja/api/quick-start/ , the old page is still being seen. On the other hand, English docs.openstack.org/api/quick-start url is redirected to current API quick start URL like http://developer.openstack.org/api-guide/quick-start/index.html . - Even though translation progress seems to be good, there is no rst- based generated documentation for zh_CN (Chinese) and id (Indonesia) So, currently, my approach to address this bug is: 1) Identify which languages have good progress on api-quick-start translation 2) Include that those languages need to build 3) After checking the documentation result on public web pages, we need to add url redirection. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-api-site/+bug/1608992/+subscriptions

1 3

What happens in openstack-manual on Zanata?
by Akihiro Motoki 20 Sep '16

20 Sep '16

Hi, I see many many 'common' in openstack-manual project on Zanata? https://translate.openstack.org/iteration/view/openstack-manuals/master/doc… 'common' in openstack-manuals are linked into individual guides and they are uploaded by accident. Is there any change around upstream_translation_update.sh ? Akihiro

4 3

First stable/newton branches created
by Andreas Jaeger 19 Sep '16

19 Sep '16

Could somebody please set up stable-newton branches for those projects that should get translations of them, please? With RC1 today, projects are creating stable/newton branches now, 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

4 14