- OpenStack-I18n - lists.openstack.org

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

09 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 06 Nov '15

06 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 01 Nov '15

01 Nov '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

I18n team meet up in Tokyo
by Ying Chun Guo 31 Oct '15

31 Oct '15

3 2

What's Up, Doc? 三鷹 Summit Edition
by Lana Brindley 30 Oct '15

30 Oct '15

Hi everyone, Welcome to the Summit edition of the docs newsletter! Docs have had a wonderfully productive week here in Tokyo, and we've now established a plan for Mitaka. This newsletter covers the more important announcements, and the main points we want to hit in the next release. Karin has kindly written up the summary of the Design Summit sessions here: https://etherpad.openstack.org/p/Mitaka-Docs-Meetup == Mitaka Goals == This is the list at the moment. There are more notes in the docs etherpads, and not everything has blueprints yet. * Switch API docs over to swagger http://specs.openstack.org/openstack/docs-specs/specs/liberty/api-site.html (???) * Implement new docimpact plan: https://blueprints.launchpad.net/openstack-manuals/+spec/review-docimpact * RST Conversions: ** Arch Guide: https://blueprints.launchpad.net/openstack-manuals/+spec/archguide-mitaka-r… ** Ops Guide: https://blueprints.launchpad.net/openstack-manuals/+spec/ops-guide-rst (pending O'Reilly conversation) ** Config Ref * Reorganisations: ** Arch Guide: https://blueprints.launchpad.net/openstack-manuals/+spec/archguide-mitaka-r… ** Ops Guide: https://blueprints.launchpad.net/openstack-manuals/+spec/improve-ops-guide ** User Guides: https://blueprints.launchpad.net/openstack-manuals/+spec/user-guides-reorga… * Training ** Labs: https://blueprints.launchpad.net/openstack-manuals/+spec/training-labs ** Guides: Upstream University & 'core' component updates, EOL Upstream Wiki page. * First App Guide: testing & improvements * Reorganise the index page * Document the openstack-doc-tools == Speciality Team Changes == More detail on the Speciality Team wiki page: https://wiki.openstack.org/wiki/Documentation/SpecialityTeams * Install Guide is now with Christian Berendt * HA Guide is now with Bogdan Dobrelya * Networking Guide is now with Edgar Magana * New Hypervisor Tuning Guide team with Joe Topjian あなたの東京ありがとう! Lana Lana Brindley Technical Writer Rackspace Cloud Builders Australia

1 0

dashboard translation check site
by KATO Tomoyuki 29 Oct '15

29 Oct '15

Hi, Elizabeth, Akihiro, Daisy Just a memorandum from the Summit session. We need share the operation process of Akihiro's personal dashboard translation check site before we prepare the our official check site. The check site is built with DevStack. Basic scripts for import and export tranlations are: https://github.com/amotoki/horizon-i18n-tools * need update from Transifex client to Zanata client Akihiro-san, please follow up and correct the details. Thanks, KATO Tomoyuki

2 1

Request to join local Translation in thai language.
by sawangpong muadphet 29 Oct '15

29 Oct '15

Dear Team My name is Sawangpong Muadphet from Thailand. I would like to join the Local Translation Teams for Thailand. I am contribute on Openstack promotion in Thailand for 2 yrs. I do training openstack also. But thai language is not in the openstack yet. I do hope that Thai people will have more opportunity in openstack my transfix account: sawangpongm Sincerely yours Sawangpong Muadphet CEO www.itbakery.net <http://www.itbakery.net/> Thailand

4 3

Call for Presentation Proposals for FUEL GILT Conference 2015!
by Rajesh Ranjan 24 Oct '15

24 Oct '15

FUEL GILT Conference is one of the largest events of FOSS language technology - Its challenges, solutions, best practices and its conventions. Due to some unavoidable reasons, we are a bit late in announcing CFP. We apologize for the same. We are late, but this time we have grand plan to celebrate the presence of our languages on new technology platform. Yes, we have a grand plan! Total three days for the event : 20,21 and 22 Nov 2015. So, save these dates on your calender! The host for the event and venue is - Tamil Virtual Academy (Erstwhile Tamil Virtual University), Anna University Campus, Gandhi Mandapam Road, Kottur, Chennai, Tamil Nadu. Thank you TVA. We are happy that, this time Mozilla Localisation Hackathon is being organised as a part of FUEL Gilt Conference 2015. We have FUEL Gilt Conference on 20th Nov and Mozilla l10n Hackthon on 21-22 Nov.However, the localization hackathon is open to the invited members only. If you are one of the localizers contributing to Mozilla, you may contact your locale leader to know more about it. This year Mozilla Corporation, Centre for Development of Advance Computing (C-DAC), Pune and Red Hat are the main organizers of the Conference. The event is being hosted at Tamil Virtual Academy and supported by Free Software Foundation Tamil Nadu. Thank you all for helping hand. Call for Presentation Proposal is open till Oct 31, 2015. Please send your proposal in required format mentioned on the page: http://fuelproject.org/gilt2015/index FUEL is growing only because of the support of volunteer communities world-wide and several well known organizations! The power of the event is the power of collaboration, the power of sharing, the power of volunteerism! Currently, More than 60 language communities are working with the FUEL Project. Since 2008, FUEL Project is consistently working with the different language communities to provide standard linguistic resources eg. Terminologies, style guides, assessment methods etc. to the world.Like last year, please collaborate and cooperate to make the event a huge success! For more details, please visit: http://fuelproject.org/gilt2015/index -- Rajesh Ranjan www.rajeshranjan.in @kajha <https://twitter.com/kajha> Developing a linguistic standard for language localization <http://www.livemint.com/Industry/zWJ1943VQmwABkZGmMTT2H/Developing-a-lingui…>

1 0