- OpenStack-I18n - lists.openstack.org

empty PO-Revision-Date in tr_TR neutron log PO file
by Akihiro Motoki 19 May '16

19 May '16

Hi team, There was a report in #-i18n channel that tr_TR neutron PO file contains empty PO-Revision-Date [1]. Can anyone dig into the detail? In addition, there seems very few folks on the IRC channel. Is it a right contact point to the i18n team? Is it better to add some warning to our document to encourage to use the mailing list? Surprisingly, the above it the first conversation in #-i18n channel in May! [1] http://eavesdrop.openstack.org/irclogs/%23openstack-i18n/%23openstack-i18n.… Akihiro

1 0

i18n meeting in IRC meeting calendar looks wrong....
by Akihiro Motoki 19 May '16

19 May '16

OpenStack IRC meeting calendar says that we have a meeting today (19 May) at 0600UTC [1]. However, i18n team doc [2] says we will have a meeting today at 1300UTC, week 3 of May. This means a meeting slot described at [2] is NOT reserved. (Don't worry. The slot is not booked as of today.) I think the reason is because OpenStack IRC meeting scheduler does not support monthly meeting schedule. It only supports weekly or bi-weekly (based on a week number in a year). It is to reduce meeting time conflicts. I have no good solution but it is better to be solved. Just FYI. Akihiro [1] http://eavesdrop.openstack.org/calendars/i18N-team-meeting.ics [2] http://docs.openstack.org/developer/i18n/i18n_team_meeting.html

1 0

Re: [OpenStack-I18n] stackalytics translation stats API is broken????
by Kato, Tomoyuki 17 May '16

17 May '16

> which is Remo(a)rm.ht > > This should be also usable on OpenStack. > > Any other suggestions Hi Remo, As of now, we maintain the user list manually. So, we should add users to the list... I'll check the list, but anyone can submit a patch for addition. http://git.openstack.org/cgit/openstack/i18n/tree/tools/zanata/translation_… Next release of Zanata will support the feature to dump user list with email. Thanks, KATO Tomoyuki

2 1

Re: [OpenStack-I18n] stackalytics translation stats API is broken????
by Ian Y. Choi 16 May '16

16 May '16

Hello Remo! Your translation count on Stackalytics is zero? If then, I think [1] and [2] will help to solve your problem :) [1] http://lists.openstack.org/pipermail/openstack-dev/2016-February/087537.html [2] http://lists.openstack.org/pipermail/openstack-dev/2016-February/087659.html With many thanks, /Ian Remo Mattei wrote on 5/16/2016 2:22 AM: > The last 2 months I translated about 400 words but stack does not even show any. It will be great to get this fixed. > > Thanks > > Inviato da iPhone > >> Il giorno 15 mag 2016, alle ore 09:56, Ian Y. Choi <ianyrchoi(a)gmail.com> ha scritto: >> >> Hello, >> >> I might have found the problem. >> >> The problem is that there can be several 'Translated' results within a week, >> however, those results are saved with the same primary key. >> >> I have just proposed https://review.openstack.org/316460 . >> >> I am not sure whether 'date' field is used on other Stackalytics sources, >> but at least, generating the primary key for translation records on record_processor.py >> does not use 'savedDate' field, as Shengjing mentioned. >> If 'date' field is used on other Stackalytics sources, please tell me, then I will change the review :) >> >> >> With many thanks, >> >> /Ian >> >> >> SJ Zhu wrote on 5/16/2016 12:14 AM: >>>> On Sun, May 15, 2016 at 10:42 PM, Ian Y. Choi <ianyrchoi(a)gmail.com> wrote: >>>> I have a question, although it is not mainly related to wrong Stackalytics >>>> stats. >>>> >>>> I have found that API 'stats/user/%s/%s..%s' >>>> and API 'stats/project/%s/version/%s/contributor/%s/%s..%s' generate >>>> different results. >>>> >>>> For example, from Apr 1 2016 to today, my count is 34320 with the first API, >>>> but the send API generates 29490 for the same period. >>>> >>>> I do know why the two APIs generate different numbers. >>>> Can statistics numbers on user API and the sum of results from each project >>>> API be different? >>> Hi all, >>> >>> Previously Stackalytics uses API >>> 'stats/project/%s/version/%s/contributor/%s/%s..%s'. >>> But I change it to 'stats/user/%s/%s..%s' in >>> https://review.openstack.org/#/c/288871/ >>> >>> I may find the BUG but I have no time to fix it these days. So I hope >>> someone to help. >>> >>> Stackalytics will get the results every week. And >>> 'stats/user/%s/%s..%s' will return >>> everyday's count. However Stackalytics seems not to sum a week's work. >>> >>> To fix it, I think we can change the way how Stackalytics uses >>> Zanata's API. Based on >>> 'stats/user/%s/%s..%s' we can get 'savedDate'. So just use the >>> 'savedDate' to display >>> on Stackalytics. I haven't read the code carefully but I think the >>> change is possible. >>> What's more we can debug the wrong results on Stackalytics more conveniently. >>> >>> But there's another question. How can we fix the old results on Stackalytics? >> >> _______________________________________________ >> OpenStack-I18n mailing list >> OpenStack-I18n(a)lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n >> >> !DSPAM:5738aa786031686312732! >> >>

3 5

stackalytics translation stats API is broken????
by Akihiro Motoki 15 May '16

15 May '16

Hi, Does stackalytics translation stats API work? I translated 7827 words this month according to Zanata homepage, but stackalytics says just 251 words translated. I translated thousands of words at least 2 or 3 days ago, so I think it should be visible at stackalytics now. I wonder what happens in Stackalytics integration..... Does anyone know the status? Akihiro

5 5

What's Up, Doc? 13 May
by Lana Brindley 12 May '16

12 May '16

= 13 May 2016 = Hi everyone, Wow, what a busy week! I've been mainly focused on the Install Guide speciality team this week, with gathering interested participants, ensuring our specs are ready to be merged, and setting a new meeting time. I'm also pleased to say that our speciality team reports make a post-Summit comeback in this newsletter. Just another reminder that all projects should update their cross-project liaison for docs on the wiki here: https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation If you're one of the lucky people nominated by your PTL to be a docs CPL, then please do your very best to attend docs meetings in your favourite timezone to make sure we hear the voice of your project when we're making documentation decisions. Details of upcoming docs meetings are at the end of this newsletter every week. On a related note, it was refreshing to read the conversation from the US meeting this week, and the associated conversation on the mailing lists about developer contributions to documentation. We'd love to find out what it is that prevents you from contributing to the docs, and what the docs team can do to make things that little bit easier for you! Reach out to us either on the dev mailing list (with [docs] in the subject line), or on the docs mailing list at openstack-docs(a)lists.openstack.org. == Progress towards Newton == 145 days to go! Bugs closed so far: 71 Newton deliverables 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. The Ops and HA Guides now exist in openstack-manuals, and the old repos have now been set to read-only. We also have the first patch in for the Install Guide 'cookie cutter' template, which is a great start! == Speciality Team Reports == '''HA Guide: Bogdan Dobrelya''' No report this week. '''Install Guide: Lana Brindley''' New meeting time proposed: https://review.openstack.org/#/c/314831/ Still need to merge final spec: https://review.openstack.org/#/c/310588/ If you're interested in helping out, add your name here: https://wiki.openstack.org/wiki/Documentation/InstallGuide#Team_members '''Networking Guide: Edgar Magana''' We are planning to resume the meeting next week. '''Security Guide: Nathaniel Dillon''' Summit Recap: https://etherpad.openstack.org/p/austin-docs-workgroup-security Good conversations around API rate limiting, OSSN in-flight, SecGuide work being prep'd (Thanks to Luke Hinds for taking this on!) Added Doc reviewer (Thanks Shilla and welcome!) Will be focusing on Neutron security '''User Guides: Joseph Robinson''' No report this week. '''Ops Guide: Shilla Saebi''' Proposed architecture guide restructure: https://review.openstack.org/#/c/311998/ Ops guide session Etherpad from Austin: https://etherpad.openstack.org/p/AUS-ops-Docs-ops-guide OpsGuide reorg: https://etherpad.openstack.org/p/PAO-ops-ops-guide-fixing Newton Plans: Review content of both guides, and delete anything out of date Review architecture of both guides, and possibly combine Ops Guide in openstack-manuals repo Gather content from Ops internal documentation '''API Guide: Anne Gentle''' All but two services have someone working on landing a migration patch in the project's repo. Read: Status on bugs and migration http://lists.openstack.org/pipermail/openstack-docs/2016-May/008624.html Read: Summit session recap http://lists.openstack.org/pipermail/openstack-dev/2016-May/094472.html '''Config/CLI Ref: Tomoyuki Kato''' Discussing documenting auto generation of config options with Oslo team. Dropped keystone command-line client from CLI reference. Keystone CLI was removed in python-keystoneclient 3.0.0 release. '''Training labs: Pranav Salunke, Roger Luethi''' Working on adding new features like PXE boot. Stabilizing current release and backends. Figuring out the zip file generation and web site/page. Chaging the meeting time to more CET/CEST friendly time. '''Training Guides: Matjaz Pancur''' No report this week. '''Hypervisor Tuning Guide: Joe Topjian''' No report this week. '''UX/UI Guidelines: Michael Tullis, Stephen Ballard''' No report this week. == Site Stats == The interesting fact I'd like to share with you this week is that just over 25% of our viewers this month are new to the site. == Doc team meeting == Next meetings: The US meeting was held this week, you can read the minutes here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2016-05-11 Next meetings: APAC: Wednesday 18 May, 00:30 UTC US: Wednesday 25 May, 19: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 https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#13_May_2016 -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com

1 0

where are translated documents (master/stable-mitaka) published
by Akihiro Motoki 11 May '16

11 May '16

Hi, In Zanata, we have master and stable-mitaka versions for openstack-manuals. Where are these translated documents published? For Japanese install guide, I see only http://docs.openstack.org/draft/ja/install-guide-ubuntu/ and no http://docs.openstack.org/mitaka/ja/install-guide-ubuntu/ . Which zanata version (master or stable-mitaka) corresponds to http://docs.openstack.org/draft/ja/install-guide-ubuntu/ ? Akihiro

2 2

[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 06 May '16

06 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