- OpenStack-I18n - lists.openstack.org

Re: [OpenStack-I18n] [OpenStack-docs] stable/newton created, publishing frozen for now
by Ian Y. Choi 20 Nov '16

20 Nov '16

Hello, Andreas Jaeger wrote on 11/13/2016 3:52 AM: > On 11/12/2016 07:18 PM, Andreas Jaeger wrote: >> Clark just created a stable/newton branch. >> >> I'll create the changes now for both master and stable so that >> publishing is correct. >> >> Please do not approve any changes until those are in. >> >> I'll sent in a few minutes an email with links to those changes for >> review, > > The changes that need to merge are: > > https://review.openstack.org/396874 > https://review.openstack.org/396875 > > In addition: > * stable-newton needs to be created on zanata (i18n team) Zanata now has a stable-newton version for openstack-manuals, and this version can be seen in https://translate.openstack.org/project/view/openstack-manuals and https://translate.openstack.org/iteration/view/openstack-manuals/stable-new… . i18n team will translate backported guides (common, install-guide, networking-guide) in stable-newton instead of master for translation plan and priority during Ocata cycle. Thank you all kind help and communication, especially Andreas and Olena! With many thanks, /Ian > * import of newton translations: https://review.openstack.org/396876 > * Documentation for the above: https://review.openstack.org/396877 > > Please review everything and help updating these if I missed anything, > I really like to have this properly documented so that the release > managers can do it next time, > > Andreas

1 1

What's Up, Doc? 18 November
by Lana Brindley 18 Nov '16

18 Nov '16

Hi everyone, Welcome to Ocata! It was great to catch up with many of you in Barcelona, and always refreshing to see the energy around our little project and catch that enthusiasm all over again :) Of course, Ocata is a *very* short cycle, so we've deliberately cut down our deliverables list to ensure we can squeeze it all in. We have two main priorities this release: tidying up the new Install Guides index page, and a little bit of navel gazing in terms of social structures and procedures. More on that in this newsletter! == Progress towards Ocata == 96 days to go! Closed 77 bugs so far. Release tasks are being tracked here: https://wiki.openstack.org/wiki/Documentation/OcataDeliverables == The Road to PTG in Atlanta == Event info is available here: http://www.openstack.org/ptg Purchase tickets here: https://pikeptg.eventbrite.com/ Docs is a horizontal project, so our sessions will run across the Monday and Tuesday of the event. == Specs on review == * Ops/Arch Guides: https://review.openstack.org/#/c/392372/ [arch-design] Revise the Architecture Design Guide https://review.openstack.org/#/c/394261/ [ops-guide] Add project upgrade notes https://review.openstack.org/#/c/391786/ Proposed use case form * Training Labs: https://review.openstack.org/#/c/391548/ training-labs: Rewrite training-labs in python == Speciality Team Reports == We've made some structural changes to how Speciality Teams and our regular docs meeting work. Speciality teams will now meet no more than once monthly (most on an 'as needed' basis), and participants are instead encouraged to attend the main docs meeting to discuss work and report on progress. This is aiming to keep all the information about the work we're doing a little more centralised, and give newcomers a way to find out where they can best help. It also gives us a chance to find out where we can help each other, without going to a dozen meetings! * API: Anne Gentle Karen Bradshaw has been working on updates to the openstackdocstheme that would fix this bug: https://launchpad.net/bugs/1583623. The review is up at https://review.openstack.org/#/c/393890/ and getting input from the affected teams who have recognized the need because of errors building when you have multiple API versions with very similar calls, so you end up with identical headings. Launchpad bug 1583623 in openstack-doc-tools "os-api-ref: duplicate labels for selectors" [Low,In progress] - Assigned to Karen Bradshaw (kbhawkey) I've had a couple of inquiries on IRC about "where did the draft/swagger files go?" but to meet their stated end goals, those particular files wouldn't have worked any way due to inaccuracies in the content and incomplete content. See the 100 api-ref doc patches up for review at: https://review.openstack.org/#/q/status:open+file:api-ref. * Configuration Reference and CLI Reference: Tomoyuki Kato No report this week * High Availability Guide: Andrew Beekhof No report this week * Hypervisor Tuning Guide: Joe Topjian No report this week * Installation guides: Lana Brindley No major updates to the guides themselves, but we are planning updates to the landing page. We're also working on getting our first deployment guide landed there, with OpenStack Ansible. I've requested design resources from foundation, but haven't heard back yet, so if you have ideas/suggestions (or design skillz!) then please let me know. * Networking Guide: John Davidge A couple of new articles are close to merging: https://review.openstack.org/#/c/361776/ - VLAN Trunking and https://review.openstack.org/#/c/356013/ - Routed Provider Networks. Need to decide how best to track the work that's going on for https://blueprints.launchpad.net/openstack-manuals/+spec/use-openstack-comm…. Probably a google spreadsheet or etherpad with a list of all the network guide pages to be converted, and the person working on it would be best. That way we can hopefully avoid duplicating efforts. * Operations and Architecture Design guides: Darren Chan We're slowly making progress with the arch guide, and have cloudnull onboard to help. So the focus is completing the design chapter and migrating stuff from the ops guide. * Security Guide: Nathaniel Dillon No update this week. * Training Guides: Matjaz Pancur We changed our IRC meeting to every two weeks (on even weeks) on Tuesday at 1300 UTC in #openstack-meeting-3. There will be an article published about BCN Upstream training in OpenStack's Superuser magazine. BCN Upstream training retrospective https://etherpad.openstack.org/p/upstream-training-barcelona-retrospective * Training labs: Pranav Salunke, Roger Luethi We have the python port already under review, the spec is not done yet, but we hope to get them merged soonish and in the right order :) User guides: Joseph Robinson * This the current work on converting the legacy commands to OS commands: https://wiki.openstack.org/wiki/Documentation/ReorganizeUserGuides#Ocata_Ta…. Thanks to csatari and visnyei and allen, there's progress happening. I need to finish adding the files affected to the checklist, and then also start making changes. Apart from that, keeping track of any admin or user guide bugs is also a task. == Doc team meeting == We have re-started the docs team meetings, with a new cadence. Our first meeting was held today, with much success. Thank you to everyone who participated, either directly in IRC, or by making sure you sent me your updates ahead of schedule. Our next meeting will be on Thursday 1 December at 2100 UTC in #openstack-meeting-alt For more meeting details, including minutes and the agenda: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting -- Keep on doc'ing! Lana https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#18_November_2016 -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com

1 0

Adding Romanian Language Team
by Cristian Cira (KTH-PDC) 17 Nov '16

17 Nov '16

Dear all, I have recently decided to contribute to the translation of the OpenStack documentation to Romanian in my limited free time. I am a native Romanian currently working in Sweden at a HPC center. My English is proficient having studied and worked in USA for 5 years prior to moving here. Here is my LinkedIn <https://se.linkedin.com/in/cristian-cira-246b0933> account for some more details. My username on Zanata is *cira* Please let me know what are the next steps I have to take. Thank you, C *Cristian Cira,* PhD Application Expert in Code Optimization *PDC Center for High Performance Computing* KTH Royal Institute of Technology SE-100 44 Stockholm, Sweden *http://www.pdc.kth.se <http://www.pdc.kth.se>* Tel : +46 8 790 6309 Mob : +46 737 65 22 98

2 1

Re: [OpenStack-I18n] [openstack-dev] [i18n] [glance] ESL question 'shared' vs 'shareable'
by Ian Y. Choi 17 Nov '16

17 Nov '16

Hello devs, As a Korean translator, I also quite agree with the idea. Some images with "shared" state but actually not shared yet would be awkward, and "shareable" word would cover such context : those images can be shard but may not be shared yet (although the addition of "image members"is needed) or already shared. Hello translators, I am copying openstack-i18n(a)lists.openstack.org on this. Would you pleased think about this and share your thoughts? (Or please attend to the next i18n IRC meeting about in 9-10 hours and tell me.) With many thanks, /Ian Sean McGinnis wrote on 11/17/2016 1:44 AM: > On Wed, Nov 16, 2016 at 04:04:52PM +0000, Brian Rosmaita wrote: >> Hello Translators, >> >> We're having a discussion about a new image "visibility" value for Glance, >> and before we go too far, it would be helpful to know whether what we're >> worried about is going to matter for ESL people. >> >> Here's the situation: Since the Diablo release, Glance end users have had >> the ability to share images with other cloud users by adding "members" to >> the image. We call those "shared images". Previously, we haven't had a >> special "visibility" keyword for these, but we are introducing one now >> [0]. Here's the problem introduced by that change: >> >> (1) Members can only be added to an image if its current visibility value >> allows for it. We're going to make this an explicit visibility state that >> we ware proposing to call 'shared'. >> >> (2) An image with visibility == 'shared', however, isn't actually >> accessible to other users unless they are added as "image members". So >> it's going to be possible for a user to have some images with visibility >> == 'shared', but they aren't *really* shared with anyone yet. >> >> (3) For reasons outlined on [0], we're proposing to make this new >> visibility the default value in Glance. This will enable the current >> sharing workflow to work in a backward-compatible way. But some people >> are worried that users will panic when they see that their new images have >> visibility == 'shared' (even though no other users have access to such >> images until "image members" are added). >> >> (4) To address this, we're thinking that maybe the identifier for this >> kind of image visibility should be 'shareable'. >> >> Finally, here's my question. For an ESL person looking at these two >> identifiers (which, as identifiers, won't be translated): >> * shared >> * shareable >> >> Are the above so similar that the nuances of the discussion above would be >> lost anyway? In other words, are we just bikeshedding here, or is there a >> clear distinction? What I mean is, is the panic described above likely or >> unlikely to happen for an ESL person? >> >> thanks, >> brian > Good question. I think technically it would be shareable, which would > mean that it then able to be shared. > > Realistically though, in my opinion, calling it shared to denote that it > _can be_ shared is probably intuitive enough that there wouldn't be any > confusion about the naming. > > My 2 cents. > >> [0] https://review.openstack.org/#/c/396919/ >> >> >> __________________________________________________________________________ >> 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 > __________________________________________________________________________ > 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

Creating i18n-specs for I18n specifications
by Ian Y. Choi 09 Nov '16

09 Nov '16

Hello, Official OpenStack project teams can have specification repositories, and the specifications are published on: http://specs.openstack.org/ . As we decided on last Barcelona i18n contributor meetup (Please see number 2 part in Etherpad for more details: https://etherpad.openstack.org/p/barcelona-i18n-meetup ), I have just requested to create i18n-specs repository using the following patchsets - https://review.openstack.org/#/c/394680/ - https://review.openstack.org/#/c/394681/ Hope that more i18n activities will be documented with details and shared using this i18n-specs repo. I will notice again after i18n-specs repo will be landed successfully :) With many thanks, /Ian

3 3

Feedback is needed for I18n draft logo!
by Ian Y. Choi 09 Nov '16

09 Nov '16

Hello, On last July, i18n team decided *parrot* as i18n project mascot. OpenStack Foundation has a plan for all the official OpenStack teams to have logos based on mascots. Logos will be ready by the 1st Project Team Gathering on next February. Please see the attached figure for draft logo. The attached is a draft logo for i18n team to target Barcelona Summit for project teams to more discuss on logos. If you are interested in how illustrators worked, please refer a video: https://youtu.be/JmMTCWyY8Y4 . I18n team needs to return a feedback from the draft logo by Nov 11 (Fri) with a feedback form: http://tinyurl.com/OSmascot . Direct feedback to the URL is also fine, but please share feedback through i18n mailing list! (e.g., color, style, design, form, ...) The following is what I was received what we can expect through the logo: * A horizontal version of the logo, including your mascot, project name and the words "An OpenStack Community project" * A square(ish) version of the logo, including all of the above * A mascot-only version of the logo * Stickers for all project teams distributed at the PTG * One piece of swag that incorporates all project mascots, such as a deck of playing cards, distributed at the PTG * All digital files will be available through the website With many thanks, /Ian

5 6

I18n in BCN: I18n contributor meetup wrap up
by Ian Y. Choi 02 Nov '16

02 Nov '16

Hello! There were around total 20 participants for last I18n contributor meetup @Barcelona, including Daisy, Zanata team, Infrastructure team, Docs team, and Stackalytics team members! Thank you very much for such all kind and so active participation! Although there have been sort of time conflicts for some active translators and main contributors on other projects but who are helping i18n team a lot, we have met each other and discussed for better i18n. I think i18n team members have dealt various topics with so long time. If there was no time limit: 6pm, i18n members might have discussed much longer :) I am now transferring to go home and my final flight has been delayed about 3 hours, but thanks to such delay, I have briefly summarized now what have been discussed and what are results from I18n contributor meetup. Please see Etherpad: https://etherpad.openstack.org/p/barcelona-i18n-meetup , and "Discussed Topics and Results" (2nd) section. - Andreas Jaeger shortly visited due to his return flight and we agreed with translation job import and export criteria. I have briefly summarized in number *(1)*. - Ilya Shakhat, who is a Stackalytics core developer and maintainer, kindly participated in the meetup. If anyone is interested in Stackalytics with i18n statistics, please refer to number *(3)* for the details. - Although there is another infrastructure team meeting on the same time, Elizabeth K. Joseph and Clark Boylan came to I18n contributor meetup (thank you so much again!). Zanata upgrade *(4)* is what i18n team is really waiting for. Alex Eng and Patrick Huang from Zanata team gave some beneficial feedback (e.g., current Zanata version number and new version release plan) through IRC in real time. Moreover, I hope that some discussion of translation checksite *(5)* will yield more positive progress, although it seems that more discussion is needed. - Also, Lana from Docs team PTL visited to i18n contributor meetup, although she was leading Docs contributor meetup on the same time. Lana and me both agreed that more communication between two teams will make nice fruit *(6)*. - For i18n activities, we have differentiated and clarified the usage of web pages : Zanata dashboard, Wiki, i18n contributor guide, and so on *(2)*, and also finalizing Ocata translation plans is very important during Ocata Design Summit *(7)*! I will update Zanata dashboard according to the finalization. Because of some time restriction, some topics has not been discussed yet or just briefly mentioned. Let's also consider those topics gradually such as on the next IRC meeting. Some meetup participants took photos. Frank shared photos to Etherpad! I hope that other participants will share photos soon. Hope all to have a return flight safely. Again, thank you very much all! With many thanks, /Ian

4 5

Fwd: Feedback is needed for I18n draft logo!
by Cloud Suhartono 02 Nov '16

02 Nov '16

Hello, I just gave the OpenStack Project Mascot Feedback. Overall, our logo is good, even though, skill of parrots just follows what people say, and is not smart enough to present it. For notes, our project should presents clearly the documentation. /suh 2016-11-02 1:13 GMT+07:00 JF Taltavull <jftalta(a)gmail.com>: > Hello Ian, hello teammates, > > The draft logo looks good for me, though the black lines are a little bit > too bold, maybe... > > -JF > > On 30/10/2016 03:05, Ian Y. Choi wrote: > > Hello, > > On last July, i18n team decided *parrot* as i18n project mascot. > OpenStack Foundation has a plan for all the official OpenStack teams to > have logos > based on mascots. Logos will be ready by the 1st Project Team Gathering on > next February. > > Please see the attached figure for draft logo. > > The attached is a draft logo for i18n team to target Barcelona Summit for > project teams > to more discuss on logos. > If you are interested in how illustrators worked, please refer a video: > https://youtu.be/JmMTCWyY8Y4 . > > I18n team needs to return a feedback from the draft logo by Nov 11 (Fri) > with a feedback form: http://tinyurl.com/OSmascot . > > Direct feedback to the URL is also fine, but please share feedback through > i18n mailing list! > (e.g., color, style, design, form, ...) > > The following is what I was received what we can expect through the logo: > > * A horizontal version of the logo, including your mascot, project name > and the words "An OpenStack Community project" > * A square(ish) version of the logo, including all of the above > * A mascot-only version of the logo > * Stickers for all project teams distributed at the PTG > * One piece of swag that incorporates all project mascots, such as > a deck of playing cards, distributed at the PTG > * All digital files will be available through the website > > > > With many thanks, > > /Ian > > > _______________________________________________ > OpenStack-I18n mailing listOpenStack-I18n@lists.openstack.orghttp://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 > >

2 1

Re: [OpenStack-I18n] Feedback is needed for I18n draft logo!
by Kato, Tomoyuki 02 Nov '16

02 Nov '16

Hi Ian, I do like this mascot logo. KATO Tomoyuki > Hello, > > On last July, i18n team decided *parrot* as i18n project mascot. > OpenStack Foundation has a plan for all the official OpenStack teams to > have logos > based on mascots. Logos will be ready by the 1st Project Team Gathering > on next February. > > Please see the attached figure for draft logo. > > The attached is a draft logo for i18n team to target Barcelona Summit > for project teams > to more discuss on logos. > If you are interested in how illustrators worked, please refer a video: > https://youtu.be/JmMTCWyY8Y4 . > > I18n team needs to return a feedback from the draft logo by Nov 11 (Fri) > with a feedback form: http://tinyurl.com/OSmascot . > > Direct feedback to the URL is also fine, but please share feedback > through i18n mailing list! > (e.g., color, style, design, form, ...) > > The following is what I was received what we can expect through the logo: > > * A horizontal version of the logo, including your mascot, project > name and the words "An OpenStack Community project" > * A square(ish) version of the logo, including all of the above > * A mascot-only version of the logo > * Stickers for all project teams distributed at the PTG > * One piece of swag that incorporates all project mascots, such as > a deck of playing cards, distributed at the PTG > * All digital files will be available through the website > > > > With many thanks, > > /Ian

1 0

[Bug 1637900] [NEW] 创建域、项目、用户和角色 in Installation Guide
by woolenhy 31 Oct '16

31 Oct '16

Public bug reported: ----------------------------------- Release: 0.1 on 2016-10-30 16:22 SHA: 0aec93ae3cabb0ba77ca4a0a2498b5dcaf454984 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: http://docs.openstack.org/mitaka/zh_CN/install-guide-rdo/keystone-users.html The following are a problem? 创建域``default``： $ openstack domain create --description "Default Domain" default openstack: 'domain' is not an openstack command. See 'openstack --help'. Did you mean one of these? command list container create container delete container list container save container set container show container unset ** Affects: openstack-i18n Importance: Undecided Status: New ** Tags: install-guide -- 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/1637900 Title: 创建域、项目、用户和角色 in Installation Guide Status in openstack i18n: New Bug description: ----------------------------------- Release: 0.1 on 2016-10-30 16:22 SHA: 0aec93ae3cabb0ba77ca4a0a2498b5dcaf454984 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: http://docs.openstack.org/mitaka/zh_CN/install-guide-rdo/keystone-users.html The following are a problem? 创建域``default``： $ openstack domain create --description "Default Domain" default openstack: 'domain' is not an openstack command. See 'openstack --help'. Did you mean one of these? command list container create container delete container list container save container set container show container unset To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1637900/+subscriptions

1 1