May 2016 - OpenStack-I18n - lists.openstack.org

[all][i18n] translation import: No more pot files in git trees
by Andreas Jaeger 07 May '16

07 May '16

Instead of storing the generated source translation files (*/locale/*.pot) in git and proposing them as part of the translation import, we publish these files now whenever we push to the translation server also to http://tarballs.openstack.org/translation-source/ Therefore, the source files are not needed in the git repositories anymore, the proposal bot will now - when it proposes translations - remove existing pot files. This will reduce the size of the imports significantly. Please import the translations with these removed pot files: https://review.openstack.org/#/q/status:open+topic:zanata/translations,n,z 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

2 1

pot files in git trees?
by Andreas Jaeger 07 May '16

07 May '16

Looking at the daily imports we do for our translations, a lot of that is importing pot files (translation source). Do we really need these for anything in the git trees? We've stopped importing those pot files which are not translated at all but import pot files that have translations and update them daily (only if there are real translations as well). I really wonder whether we need these pot files in our git repositories at all, Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter: 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

5 14

Re: [OpenStack-I18n] [OpenStack-docs] What's Up, Doc? 6 May 2016
by Matt Kassawara 07 May '16

07 May '16

One significant advantage of central documentation involves providing content in a single location with consistent structure or format that best serves the particular audience. Moving most or all documentation into project trees essentially eliminates this advantage, leaving our audiences with an impression that OpenStack consists of many loosely associated projects rather than a coherent cloud computing solution. However, as a contributor to a few other OpenStack projects who helps other developers contribute to central documentation, I can understand some of the frustrations with it. I prefer to resolve these frustrations and have some ideas that I intend to float in separate thread, but if you don't think that's possible, consider submitting a spec to change the primary purpose of the central documentation team to simply managing links to content in the project trees. On Fri, May 6, 2016 at 10:03 AM, Ildikó Váncsa <ildiko.vancsa(a)ericsson.com> wrote: > Hi Lana, > > Thanks for the summary, it's pretty good reading to catch up what happened > recently. > > I have one question, I might missed a few entries, so please point me to > the right document in this case. We had a docco session with the Telemetry > team and we agreed on moving back the documentation snippets, like for > instance the Install Guide, to the project trees is a really good step and > we're very supportive. In this sense I would like to ask about the plans > regarding the Admin guide. We have a chapter there, which is on one hand > outdated and on the other hand would be better to move under the project > trees as well. Is this plan/desire in line with your plans regarding that > document? > > Thanks, > /Ildikó > > > -----Original Message----- > > From: Lana Brindley [mailto:openstack@lanabrindley.com] > > Sent: May 06, 2016 08:13 > > To: enstack.org; OpenStack Development Mailing List; > openstack-i18n(a)lists.openstack.org > > Subject: What's Up, Doc? 6 May 2016 > > > > Hi everyone, > > > > I hope you all had a safe journey home from Summit, and are now fully > recovered from all the excitement (and jetlag)! I'm really > > pleased with the amount of progress we made this time around. We have a > definitive set of goals for Newton, and I'm confident that > > they're all moving us towards a much better docs suite overall. Of > course, the biggest and most important work we have to do is to get > > our Install Guide changes underway. I'm very excited to see the new > method for documenting OpenStack installation, and can't wait > > to see all our big tent projects contributing to docs in such a > meaningful way. Thank you to everyone (in the room and online) who > > contributed to the Install Guide discussion, and helped us move forward > on this important project. > > > > In other news, I've written a wrapup of the Austin design summit on my > blog, which you might be interested in: > > http://lanabrindley.com/2016/05/05/openstack-newton-summit-docs-wrapup/ > > > > == Progress towards Newton == > > > > 152 days to go! > > > > Bugs closed so far: 61 > > > > Because we have such a specific set of deliverables carved out for > Newton, I've made them their own wiki page: > > https://wiki.openstack.org/wiki/Documentation/NewtonDeliverables > > Feel free to add more detail and cross things off as they are achieved > throughout the release. I will also do my best to ensure it's kept > > up to date for each newsletter. > > > > One of the first tasks we've started work on after Summit is moving the > Ops and HA Guides out of their own repositories and into > > openstack-manuals. As a result, those repositories are now frozen, and > any work you want to do on those books should be in > > openstack-manuals. > > > > We are almost ready to publish the new RST version of the Ops Guide, > there's just a few cleanup edits going in now, so make sure you > > have the right book, in the right repo from now on. This was our very > last book remaining in DocBook XML, so the docs toolchain will > > be removing DocBook XML support. See spec > https://review.openstack.org/311698 for details. > > > > Another migration note is that the API reference content is moving from > api-site to project specific repositories and api-site is now > > frozen. For more detail, see Anne's email: > http://lists.openstack.org/pipermail/openstack-docs/2016-May/008536.html > > > > == Mitaka wrapup == > > > > We performed a Mitaka retrospective at Summit, notes are here: > https://etherpad.openstack.org/p/austin-docs-mitakaretro > > > > In particular, I'd like to call out our hard working tools team Andreas > and Christian, all our Speciality Team leads, and the Mitaka release > > managers Brian and Olga. Well done on a very successful release, > everyone :) > > > > Total bugs closed: 645 > > > > == Site Stats == > > > > Thanks to the lovely people at Foundation (thanks Allison!) I now have > access to more stats than I could possibly guess what to do > > with, and I'm hoping to be able to share some of these with you through > the newsletter. If there's something in particular you would > > like to see, then please let me know and I'll endeavour to record it > here! > > > > So far I can tell you that docs.openstack.org had 1.63M unique > pageviews in April, down slightly from 1.72M in March, and the average > > session duration is just over six minutes, looking at just under 4 pages > per session. > > > > == Doc team meeting == > > > > Next meetings: > > > > We'll be restarting the meeting series next week. > > > > Next meetings: > > US: Wednesday 11 April, 19:00 UTC > > APAC: Wednesday 18 April, 00:30 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 > > > > https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#6_May_2016 > > > > -- > > Lana Brindley > > Technical Writer > > Rackspace Cloud Builders Australia > > http://lanabrindley.com > > _______________________________________________ > OpenStack-docs mailing list > OpenStack-docs(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs >

1 0

What's Up, Doc? 6 May 2016
by Lana Brindley 06 May '16

06 May '16

Hi everyone, I hope you all had a safe journey home from Summit, and are now fully recovered from all the excitement (and jetlag)! I'm really pleased with the amount of progress we made this time around. We have a definitive set of goals for Newton, and I'm confident that they're all moving us towards a much better docs suite overall. Of course, the biggest and most important work we have to do is to get our Install Guide changes underway. I'm very excited to see the new method for documenting OpenStack installation, and can't wait to see all our big tent projects contributing to docs in such a meaningful way. Thank you to everyone (in the room and online) who contributed to the Install Guide discussion, and helped us move forward on this important project. In other news, I've written a wrapup of the Austin design summit on my blog, which you might be interested in: http://lanabrindley.com/2016/05/05/openstack-newton-summit-docs-wrapup/ == Progress towards Newton == 152 days to go! Bugs closed so far: 61 Because we have such a specific set of deliverables carved out for Newton, I've made them their own wiki page: https://wiki.openstack.org/wiki/Documentation/NewtonDeliverables Feel free to add more detail and cross things off as they are achieved throughout the release. I will also do my best to ensure it's kept up to date for each newsletter. One of the first tasks we've started work on after Summit is moving the Ops and HA Guides out of their own repositories and into openstack-manuals. As a result, those repositories are now frozen, and any work you want to do on those books should be in openstack-manuals. We are almost ready to publish the new RST version of the Ops Guide, there's just a few cleanup edits going in now, so make sure you have the right book, in the right repo from now on. This was our very last book remaining in DocBook XML, so the docs toolchain will be removing DocBook XML support. See spec https://review.openstack.org/311698 for details. Another migration note is that the API reference content is moving from api-site to project specific repositories and api-site is now frozen. For more detail, see Anne's email: http://lists.openstack.org/pipermail/openstack-docs/2016-May/008536.html == Mitaka wrapup == We performed a Mitaka retrospective at Summit, notes are here: https://etherpad.openstack.org/p/austin-docs-mitakaretro In particular, I'd like to call out our hard working tools team Andreas and Christian, all our Speciality Team leads, and the Mitaka release managers Brian and Olga. Well done on a very successful release, everyone :) Total bugs closed: 645 == Site Stats == Thanks to the lovely people at Foundation (thanks Allison!) I now have access to more stats than I could possibly guess what to do with, and I'm hoping to be able to share some of these with you through the newsletter. If there's something in particular you would like to see, then please let me know and I'll endeavour to record it here! So far I can tell you that docs.openstack.org had 1.63M unique pageviews in April, down slightly from 1.72M in March, and the average session duration is just over six minutes, looking at just under 4 pages per session. == Doc team meeting == Next meetings: We'll be restarting the meeting series next week. Next meetings: US: Wednesday 11 April, 19:00 UTC APAC: Wednesday 18 April, 00:30 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 https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#6_May_2016 -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com

1 0

Newton Design Summit summary
by Kato, Tomoyuki 05 May '16

05 May '16

Hi everyone, Here is Newton Design Summit I18n sessions summary. I18n Design Summit ------------------ * Thursday 2016-04-28 13:30 - 15:00 I18n workshop: translation processes and tools https://etherpad.openstack.org/p/austin-i18n-workshop * Friday 2016-04-29 9:00 -12:30 I18n Contributors meetup https://etherpad.openstack.org/p/austin-i18n-meetup Summary ------- * Newton cycle translation priority - Dashboard and plug-ins: require ALL with appropriate priority [TBD] - Documentation: install-guide, user-guide, api-quick-start - Glossary (not yet implemented) * I18n Guide revision - String freeze policy - How to translate release notes - How to archiving ATC, coordinators and core reviewers * Release notes translation - At now, we have translation resources at Zanata, which is named "releasenotes" at each project - Discussion with Doug Hellman, Release Management team PTL - publish to http://docs.openstack.org/<lang>/releasenotes/<project>/ - create each language index page, manually or automatically - each release note page doesn't contain language selector * Translation check site - patch review is under going. need review * Zanata upgrade - we need more time because it does not work fine * Automatic generation of ATC list - First, need to upgrade Zanata to version 3.9 or later * Glossary management - First, need to upgrade Zanata to version 3.9 or later - Need to decide management process, file formats, and so on * Improve Stackalytics - Add "translation review" count as new metrics - Update the stats daily, not weekly, as others * Docs translation publication - Simplify the maintainance process of traslated docs publication - Need to work with docs and infra team * Bug management - Email bug report to i18n ML when it is submitted * Transifex closure [Done] For more information, please see the Etherpad pages. -- KATO Tomoyuki

3 3

[i18n] Meeting reminder
by Kato, Tomoyuki 05 May '16

05 May '16

Hi team, This is a meeting reminder. I think it will be a short meeting, mainly for summit non-attendency. Kato

1 0

Create new language team called "Hinglish"
by Nitin Madhok 04 May '16

04 May '16

Hello, I’m Nitin Madhok working for Clemson University and currently contributing to various open source projects. I’m multi lingual and can read/write/speak the following languages: English(US) English(UK) French Hindi Hinglish Punjabi I want to create a language team called “Hinglish” (https://en.wikipedia.org/wiki/Hinglish <https://en.wikipedia.org/wiki/Hinglish>). My ID on Zanata is nmadhok -- Thanks, Nitin Madhok Clemson University

3 3

Fw: [OpenStack-docs] Freezing operations-guide repository
by KATO Tomoyuki 02 May '16

02 May '16

Hi team, Docs team decided to move operations guide into openstack-manuals repo. Also, XML DocBook is freezed, so we should not translate it. i.e. operations-guide/openstack-ops at Zanata. Stay tuned, the newer operations guide in RST format will appear at openstack-manuals project at Zanata, which will occur soon. KATO Tomoyuki ----------------------- Original Message ----------------------- Since we have now imported the RST ops-guide in openstack-manuals, let's freeze the operations-guide repository. We do not need to make any further edits there, any further updates should be done to the RST guide. I'm working on retiring the repository following the process documented at http://docs.openstack.org/infra/manual/drivers.html#retiring-a-project . Once this is done, the repository will be completely read-only. For that, I will propose a few final cleanup changes. So, let's do now: * Freeze repo - no more approvals for it (besides retiring). * Retire repository Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter: 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