- OpenStack-I18n - lists.openstack.org

What's Up, Doc? 19 Feb 2016
by Lana Brindley 19 Feb '16

19 Feb '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone, This week I've been focusing on general housekeeping duties as we prepare to rush headlong into the release. I've cleaned up the blueprints list, and also been burning through the oldest bugs in our queue. I'm very pleased to report that the overall number of bugs has reduced dramatically in the past month or two, and the number of untriaged bugs is holding steady at a much lower rate than previously. I think this probably has a lot to do with the DocImpact changes we made at the beginning of the year, so it's very gratifying to see some solid improvement starting to filter through. In other news, thanks to all those people who helped us with locating pre-release packages for the Install Guide. Please feel free to begin testing! The more people we have testing, the better and more accurate our docs will be, which helps everyone. == Progress towards Mitaka == 47 days to go! 417 bugs closed so far for this release. There is a global bug smash event coming up March 7-9 to try and hit as many Mitaka bugs as possible. You can join an in-person group near you, or participate remotely. There are still plenty of docs bugs that can be attended to. Details here: https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka Docs Testing * Volunteers required! * https://wiki.openstack.org/wiki/Documentation/MitakaDocTesting RST Conversions * All planned RST conversions are now complete! Reorganisations * Arch Guide: really needs a last minute push to get this complete before Mitaka. If you can help out, it would be greatly appreciated! ** 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 DocImpact * Is now complete == The Road to Austin == * ATC passes are going out now, so keep an eye on your inbox for your discount code if you haven't received yours yet. * Talk voting is now closed * You should be starting to think about booking travel and accommodation soon! If you need a visa to travel to the United States, there's more info here: https://www.openstack.org/summit/austin-2016/austin-and-travel/#visa == Speciality Teams == '''HA Guide - Bogdan Dobrelya''' No update this week. '''Installation Guide - Matt Kassawara''' Testing Mitaka milestone 3 using RDO packages and submitting patches for review. Lead of the install guide changed from Christian Berendt to Matt Kassawara. '''Networking Guide - Edgar Magana''' No update this week. '''Security Guide - Nathaniel Dillon''' No update this week. '''User Guides - Joseph Robinson''' The new User Guide team meetings are a success. We now have more contributors, and are discussing doc editing, new content, and Information Architecture of the User Guides. '''Ops and Arch Guides - Shilla Saebi''' Architecture guide reorganization is underway. We have a drafts repo in openstack-manuals, feel free to ping Shilla or Darren Chan if you are interested in helping out. Considering doing a swarm or work session at the summit in Austin for the Arch guide. Operations guide RST migration pending - conversations still happening to see which route we'll take. Still deciding if the ops guide should have another revision or edition, see ML e-mails. Call for volunteers email went out to the ops and docs ML from Devon Boatwright. We are looking for help! There is a global OpenStack bug smash scheduled for the Mitaka release in March. Details can be found here: https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka We're looking for people to specifically help with the Architecture Guide, which is currently going through a reorganization. Here is the link for more details: https://wiki.openstack.org/wiki/Architecture_Design_Guide_work_items If you are interested in helping out, more detail s can be found about our team and our meetings here: https://wiki.openstack.org/wiki/Documentation/OpsGuide '''API Docs - Anne Gentle''' http://lists.openstack.org/pipermail/openstack-docs/2016-February/008286.ht… Swagger files now available at http://developer.openstack.org/draft/swagger/ '''Config Ref - Gauvain Pocentek''' No update this week. '''Training labs - Pranav Salunke, Roger Luethi''' Fixing various things in training-labs cluster for VirtualBox and KVM backends. Improving workflow, configuration and making the library scripts nicer. Adding training-labs landing page (WIP). Summit related work. Some minor improvements. '''Training Guides - Matjaz Pancur''' No update this week. '''Hypervisor Tuning Guide - Joe Topjian''' No update this week. '''UX/UI Docs Guidelines - Linette Williams''' Enhancement to UI content guidelines underway. Expect a new review shortly that covers icons and text formatting. If interested or have questions, contact Linette or Piet Kruithof. == 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-02-14 Next meetings: APAC: Wednesday 24 February, 00:30 UTC US: Wednesday 2 March, 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… Note that there is currently discussion about moving the US meeting to 20:00 UTC. A patch is open to change this, with ongoing discussion about finding a meeting room: https://review.openstack.org/#/c/271361/ - -- Keep on doc'ing! Lana https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#19_February_2016 - -- 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/ iQEcBAEBCAAGBQJWxpUQAAoJELppzVb4+KUyM5IIAKXT4U1SDq8K1+3u41qchjRe tXx3DCHp+O70krBFP+b6xaYXsuIwd6G4iroUXtl0RodlNAxdBjFf82fnpTlt/sz9 tjlST4nt/Z93shaA5b0AkOzEKJhoHCyH0ucq2GCQ81P5mEM3ZkFOYsEjdQjckPhu fc8yvbgjo1Dvxjk6/bEV6c1hroEqLVrzhpd9jstefA/1ATTCg3hR/IWQ9cXscMn0 8qutBYibhFcXzcCVj4/aafjUH+1punMgGeb2KcjrmA0z345WcmS4+IWR4NZrCiMg WWEKbFT8MvGuLEU79KNs+cZBWA+TQnlD2d1fsuCHFKU/eqFeyPmc3P/tI9YM7Jo= =2AkG -----END PGP SIGNATURE-----

1 0

Re: [Openstack-i18n] [stable][i18n] What is the backport policy on i18n changes?
by Kato, Tomoyuki 18 Feb '16

18 Feb '16

> hmm, I think the policy should depends on projects. > For projects which don't have active translations, I think it's OK to backport. > For projects which have active translations, "Exception procedure" of StringFreeze could help. > Translators need to be notified for the changes. > > If you don't know whether the project has active translations or not, > "Exception procedure" can help, anyway. +1 KATO Tomoyuki > Best regards > Ying Chun Guo (Daisy) > > > Matt Riedemann <mriedem(a)linux.vnet.ibm.com> wrote on 2016/02/18 08:16:26: > > > From: Matt Riedemann <mriedem(a)linux.vnet.ibm.com> > > To: "OpenStack Development Mailing List (not for usage questions)" > > <openstack-dev(a)lists.openstack.org>, openstack-i18n(a)lists.openstack.org > > Date: 2016/02/18 08:18 > > Subject: [Openstack-i18n] [stable][i18n] What is the backport policy > > on i18n changes? > > > > I don't think we have an official policy for stable backports with > > respect to translatable string changes. > > > > I'm looking at a release request for ironic-inspector on stable/liberty > > [1] and one of the changes in that has translatable string changes to > > user-facing error messages [2]. > > > > mrunge brought up this issue in the stable team meeting this week also > > since Horizon has to be extra careful about backporting changes with > > translatable string changes. > > > > I think on the server side, if they are changes that just go in the > > logs, it's not a huge issue. But for user facing changes, should we > > treat those like StringFreeze [3]? Or only if the stable branches for > > the given project aren't getting translation updates? I know the server > > projects (at least nova) is still get translation updates on > > stable/liberty so if we do backport changes with translatable string > > updates, they aren't getting updated in stable. I don't see anything > > like that happening for ironic-inspector on stable/liberty though. > > > > Thoughts? > > > > [1] https://review.openstack.org/#/c/279515/ > > [2] https://review.openstack.org/#/c/279071/1/ironic_inspector/process.py > > [3] https://wiki.openstack.org/wiki/StringFreeze

1 0

[stable][i18n] What is the backport policy on i18n changes?
by Matt Riedemann 18 Feb '16

18 Feb '16

I don't think we have an official policy for stable backports with respect to translatable string changes. I'm looking at a release request for ironic-inspector on stable/liberty [1] and one of the changes in that has translatable string changes to user-facing error messages [2]. mrunge brought up this issue in the stable team meeting this week also since Horizon has to be extra careful about backporting changes with translatable string changes. I think on the server side, if they are changes that just go in the logs, it's not a huge issue. But for user facing changes, should we treat those like StringFreeze [3]? Or only if the stable branches for the given project aren't getting translation updates? I know the server projects (at least nova) is still get translation updates on stable/liberty so if we do backport changes with translatable string updates, they aren't getting updated in stable. I don't see anything like that happening for ironic-inspector on stable/liberty though. Thoughts? [1] https://review.openstack.org/#/c/279515/ [2] https://review.openstack.org/#/c/279071/1/ironic_inspector/process.py [3] https://wiki.openstack.org/wiki/StringFreeze -- Thanks, Matt Riedemann

3 2

IRC meeting today
by Ying Chun Guo 18 Feb '16

18 Feb '16

Hi, team We will have IRC meeting today at UTC 1300 in #openstack-meeting. The agenda in my mind are: * Follow up with translation check website * Get ready for Mitaka translation * Open discussions If you have more topics, feel free to add. Best regards Ying Chun Guo (Daisy)

1 0

Zanata 3.8 available
by Carlos Munoz 15 Feb '16

15 Feb '16

Hi All, Just a heads-up that Zanata 3.8.2 has been released and is ready for installation (See: https://github.com/zanata/zanata-server/releases) Please let us know if you want to do the upgrade and need any assistance. Regards, Carlos -- Carlos A. Muñoz Software Engineering Supervisor Globalization Red Hat

6 8

What's Up Doc? 12 Feb 2016
by Lana Brindley 12 Feb '16

12 Feb '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone, This week has been all about the Install Guide. We're locating pre-release packages now so we can begin testing in about two weeks' time. Please consider being a tester for this release. Even if you've never done it before, it's a great way to improve your OpenStack knowledge, and the more people we have testing, the better and more accurate our docs will be, which helps everyone. We're also starting to see a little more action in the lead up to the Austin Summit. ATC passes are going out, and the talk sessions are now open for voting: https://www.openstack.org/summit/austin-2016/vote-for-speakers/ == Progress towards Mitaka == 54 days to go! 389 bugs closed so far for this release. Docs Testing * Volunteers required! * https://wiki.openstack.org/wiki/Documentation/MitakaDocTesting RST Conversions * All planned RST conversions are now complete! Reorganisations * Arch Guide: really needs a last minute push to get this complete before Mitaka. If you can help out, it would be greatly appreciated! ** 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 DocImpact * Is now complete == The Road to Austin == * ATC passes are going out now, so keep an eye on your inbox for your discount code if you haven't received yours yet. * Don't forget to vote on your favourite talks: https://www.openstack.org/summit/austin-2016/vote-for-speakers/ == Speciality Teams == '''HA Guide - Bogdan Dobrelya''' Minor updates to the corosync/pacemaker, rabbitmq clusters setup guides '''Installation Guide - Christian Berendt''' Mitaka Installation guide changes spec: https://review.openstack.org/#/c/274231/ Testing beginning, require packages: https://wiki.openstack.org/wiki/Documentation/MitakaDocTesting '''Networking Guide - Edgar Magana''' Move the IRC meeting agenda to etherpad: https://etherpad.openstack.org/p/docnetworkingteam-agenda. Important Commits: DSCP addition to advanced qos guide: https://review.openstack.org/#/c/273638/ Add networking guide to Contributors Section: https://review.openstack.org/#/c/278330/ Last IRC Meeting Notes: http://eavesdrop.openstack.org/meetings/networking_guide/2016/networking_gu… '''Security Guide - Nathaniel Dillon''' Continuing bugfixes and beginning Networking review (thanks to all Neutron contributors!) '''User Guides - Joseph Robinson''' Held First US/EU Meeting, which was 1 and a 1/2 hours before the APAC meeting (Need to reserve the meeting time). Discussed Reorg- High Priority step - moving Dashboard content from the Admin Guide to the Cloud Admin Dashboard Chapter. '''Ops and Arch Guides - Shilla Saebi''' Architecture guide reorganization is underway. We have a drafts repo in openstack-manuals, feel free to ping Shilla or Darren Chan if you are interested in helping out. Considering doing a swarm or work session at the summit in Austin for the Arch guide. Operations guide RST migration pending - conversations still happening to see which route we'll take. Still deciding if the ops guide should have another revision or edition, see ML emails. '''API Docs - Anne Gentle''' No update this week. '''Config Ref - Gauvain Pocentek''' No update this week. '''Training labs - Pranav Salunke, Roger Luethi''' We reviewed and merged several patches: bug fixes, refactoring and some code to help with debugging. '''Training Guides - Matjaz Pancur''' No update this week. '''Hypervisor Tuning Guide - Joe Topjian''' No update this week. '''UX/UI Docs Guidelines - Linette Williams''' No update this week. == Doc team meeting == Next meetings: The APAC meeting was held this week, you can read the minutes here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2016-02-10 Next meetings: US: Wednesday 17 February, 14:00 UTC APAC: Wednesday 24 February, 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… Note that there is currently discussion about moving the US meeting to 20:00 UTC. A patch is open to change this, with ongoing discussion about finding a meeting room: https://review.openstack.org/#/c/271361/ - -- Keep on doc'ing! Lana https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#12_February_2016 - -- 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/ iQEcBAEBCAAGBQJWvWWOAAoJELppzVb4+KUyadwIAIzWAp7pJChEUmd6joi4GHig OLuvC3nsD6NnjW4qtK6OHdPklZQ6nN8JgNGhbnbBWhmO6/Pk4ulk4TUl5ENtYPxJ hCzQ3OKcgrj+Edb08mk7ck0uCXDQCnopDQfphNFVTObRWw6dpEBbWQBiy0zy0rsX rbp9P+TBOpbPHRgVoI/IvLps/lnlzYQM5QX+kBq0EdG6lG3jU1jDz6Lc3s8onZUV kim0xvw8Kq+l8ziJaf5UZ62ybKJeg/quhffvblVU0iU20m1sNpK6ockjR5miIJWt pSFgE1O4/AERn5/8lH72Nzm+2BuLYoxN749luRHU3agoewFxNdvpch0V7IdSv5c= =gytH -----END PGP SIGNATURE-----

1 0

French install guides for Liberty
by KATO Tomoyuki 10 Feb '16

10 Feb '16

Hi team, French team has good progress on install guides for Liberty translation. Nice work, French team! http://docs.openstack.org/liberty/fr/install-guide-obs/ http://docs.openstack.org/liberty/fr/install-guide-rdo/ http://docs.openstack.org/liberty/fr/install-guide-ubuntu/ Also, the guides will be linked from http://docs.openstack.org/draft/draft-index.html soon. At now, we have many translated docs as draft. If you think ready to publish, feel free to move them into public web pages. Regards, KATO Tomoyuki

1 0

bug squashing
by Kato, Tomoyuki 10 Feb '16

10 Feb '16

Hi team, We have 10 open bugs at now! 6 bugs looks like simplified-chinese traslation bugs. If you have time, please take a look at: https://bugs.launchpad.net/openstack-i18n/ Regards, KATO Tomoyuki

1 0

zh_CN Install Guide for Liberty broken
by Andreas Jaeger 08 Feb '16

08 Feb '16

Looking at today's import, I see for zh_CN lots of warnings - but none for other languages: http://logs.openstack.org/35/271735/1/check/gate-openstack-manuals-tox-chec… These warnings indicate a wrong breakage of the sphinx syntax. Could the zh_CN team look at these, please? 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

3 2

[Bug 1542487] extraneous spaces in some files in Glance translations
by Kato, Tomoyuki 08 Feb '16

08 Feb '16

Hi Italian team, Korean team Please take a look at the bug report. > -----Original Message----- > Public bug reported: > > Left comments in the files on this review: > https://review.openstack.org/#/c/276056/2 > > The two files affected are: > * glance/locale/it/LC_MESSAGES/glance.po > * glance/locale/ko_KR/LC_MESSAGES/glance.po > > ** Affects: openstack-i18n > Importance: Undecided > Status: New > > -- > Title: > extraneous spaces in some files in Glance translations > > Status in openstack i18n: > New > > Bug description: > Left comments in the files on this review: > https://review.openstack.org/#/c/276056/2 > > The two files affected are: > * glance/locale/it/LC_MESSAGES/glance.po > * glance/locale/ko_KR/LC_MESSAGES/glance.po

1 0

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

06 Feb '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone, A busy week here in docs, with today marking only two months left until Mitaka goes out. I've been working on the DocImpact script, the core team review, and a whole lot of general chasing things up and tidying around the place. I also note that the Installation Guide team is busy ramping up for Mitaka, so watch this space for your opportunity to jump into testing for that very soon. Next week, I'll be cleaning up the blueprints, and also starting to get in touch with our packaging contacts to get ready for release. == Progress towards Mitaka == 60 days to go! 382 bugs closed so far for this release. RST Conversions * All planned RST conversions are now complete! Reorganisations * Arch Guide: really needs a last minute push to get this complete before Mitaka. If you can help out, it would be greatly appreciated! ** 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 DocImpact * The implementation plan for the DocImpact script changed after we received feedback from Infra and Nova. Now, *all* projects (including the five 'defcore' projects) default to opening DocImpact bugs in their own bug queues. This change was proposed in https://review.openstack.org/#/c/276065/ and merged yesterday, very quickly! Projects will now be able to determine for themselves how they would like to use the DocImpact script within their own groups, and hopefully the quality of bug reporting to docs will improve dramatically as a result of this. I'd like to thank all the PTLs, cross-project liaisons, project core team members, and especially the Infra and Nova teams for their assistance and patience while we worked through this knotty problem. I'm happy to be able to report that, as of today, this project is now complete. == Speciality Teams == '''HA Guide - Bogdan Dobrelya''' No update this week. '''Installation Guide - Christian Berendt''' Mitaka Installation guide changes spec: https://review.openstack.org/#/c/274231/ '''Networking Guide - Edgar Magana''' No update this week. '''Security Guide - Nathaniel Dillon''' RST bug fixes and cleaning up of lingering migration issues. Looking for Neutron reviewers to see what is still accurate and what needs to be updated, please ping Nathaniel. Looking to setup PDF creation job. '''User Guides - Joseph Robinson''' An action item from last meeting was addressed this week - working with new User Guide team members to continue reorganisation edits. Plans for an earlier, US+EU meeting, which would roll into an APAC meeting on Wednesday/Thursday fortnightly meeting times are in place. '''Ops and Arch Guides - Shilla Saebi''' Architecture guide reorganization is underway. We have a drafts repo in openstack-manuals, feel free to ping Shilla or Darren Chan if you are interested in helping out. Considering doing a swarm or work session at the summit in Austin for the Arch guide. Operations guide RST migration pending - conversations still happening to see which route we'll take. Still deciding if the ops guide should have another revision or edition, see ML emails. '''API Docs - Anne Gentle''' Continuing to work on builds of Swagger plus RST. '''Config Ref - Gauvain Pocentek''' No update this week. '''Training labs - Pranav Salunke, Roger Luethi''' Liberty support has been merged. The new default for training-labs clusters is the Liberty release. '''Training Guides - Matjaz Pancur''' Removal of redundant Jenkins jobs (gate-training-guides-tox-slides) and tox targets. Upstream training archives (http://docs.openstack.org/upstream-training/upstream-archives.html) are now separated from the main landing page. '''Hypervisor Tuning Guide - Joe Topjian''' No update this week. '''UX/UI Docs Guidelines - Linette Williams''' Collaboration between the UX project and Doc project. The first UI text guidelines are live: http://docs.openstack.org/contributor-guide/ui-text-guidelines.html. Enhancements to guidelines in progress - specifically related to icons and text formatting. Text reviews are ongoing for new UI prototypes, as applicable. If interested in helping with UI panel reviews or with UI text guidelines, feel free to ping Linette or Piet Kruithof. == 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-01-20 Next meetings: APAC: Wednesday 10 February, 00:30 UTC US: Wednesday 17 February, 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… Note that there is currently discussion about moving the US meeting to 20:00 UTC. A patch is open to change this, with ongoing discussion about finding a meeting room: https://review.openstack.org/#/c/271361/ - -- Keep on doc'ing! Lana https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#6_February_2016 - -- 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/ iQEcBAEBCAAGBQJWtXI/AAoJELppzVb4+KUy1j8IAJ+g5ZbNQuvDCJsznis2EgfX TDMxpovMVwULypjuQdqLT7K6C/uy/4dZbKSlG7vsENnE/dzJngn52P5DriFN3CV0 YjJQ+c7iTzOaiI4choz2sdoaKOYvLIdwDSg89FpS+AE3QF0e3FnjqCtLnRJJAZhN eBg1EaTIeQO9Hz4VWs6QBIMZPsYB7icONy9V08IKDu5HyRm5HFJy73g1Wp+Nrrlv cE5PyBnARBES4bBocxENBy1w7/Pl1exnZXS7M/gadAsJGXBt/k77Ec+6wgY4BmaL XWMyjYGb+LEkdebcKf+kEZ+88eEJlTteSZgvr4B8PdDoB2b3kNUVG3tAuW3/q3g= =fQ5W -----END PGP SIGNATURE-----

1 0

Translators' statistic data and ATC
by Ying Chun Guo 03 Feb '16

03 Feb '16

4 6

Re: [Openstack-i18n] Translators' statistic data and ATC
by KATO Tomoyuki 03 Feb '16

03 Feb '16

> I didn't say NO to both. > The first is yes, the second is no. Sorry, Daisy. I misread the discussion. > For list of contributors for a project version, the rest API will be > available in 3.8 release. Thanks, Alex. KATO Tomoyuki

1 0

IRC meeting tomorrow
by Ying Chun Guo 03 Feb '16

03 Feb '16

1 0

Disabling translation import of django-openstack-auth and designate-dashboard
by Akihiro Motoki 02 Feb '16

02 Feb '16

Hi team, We would like to disable automatic translation imports for __Liberty__ version of django-openstack-auth and designate-dashboard. The background and reasons are described below. I hope there is no objections :-) Thought? [Background] Andreas and I are now working on improvements of translation setup [1] and horizon plugin translation setups. The change made is incompatible with liberty version of these projects only. To keep the infra scripts simple, we would like to disable these. [Status] * designate-dashboard translation setup in Liberty is broken and translation does not work, so I believe there is no impact. * django-openstack-auth is well translated. We can stop translations. We can still propose translation fix by manual. Thanks, Akihiro [1] http://specs.openstack.org/openstack-infra/infra-specs/specs/translation_se…

3 2

Re: [Openstack-i18n] Do we need a slot of i18n translation test meeting?
by Akihiro Motoki 02 Feb '16

02 Feb '16

I sent a patch to drop it. https://review.openstack.org/#/c/275045/ Akihiro 2016-02-02 15:01 GMT+09:00 Ying Chun Guo <guoyingc(a)cn.ibm.com>: > OK. > Thank you for reminding. > > Best regards > Ying Chun Guo (Daisy) > > > Akihiro Motoki <amotoki(a)gmail.com> wrote on 2016/02/02 13:34:43: > >> From: Akihiro Motoki <amotoki(a)gmail.com> >> To: "openstack-i18n(a)lists.openstack.org" >> <Openstack-i18n(a)lists.openstack.org> >> Date: 2016/02/02 13:36 >> Subject: [Openstack-i18n] Do we need a slot of i18n translation test >> meeting? > >> >> Hi, >> >> Can we release the meeting slot reserved for i18n translation test >> meeting [1]? >> According to the meeting log [2], only one meeting was held and seems >> unnecessary. >> >> [1] http://eavesdrop.openstack.org/#I18N_Translation_test_meeting >> [2] >> http://eavesdrop.openstack.org/meetings/openstack_i18n_test_meeting/2015/ >> >> Thanks, >> Akihiro >> >> _______________________________________________ >> Openstack-i18n mailing list >> Openstack-i18n(a)lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n >> >

1 0

Do we need a slot of i18n translation test meeting?
by Akihiro Motoki 02 Feb '16

02 Feb '16

Hi, Can we release the meeting slot reserved for i18n translation test meeting [1]? According to the meeting log [2], only one meeting was held and seems unnecessary. [1] http://eavesdrop.openstack.org/#I18N_Translation_test_meeting [2] http://eavesdrop.openstack.org/meetings/openstack_i18n_test_meeting/2015/ Thanks, Akihiro

2 1

I18n midcycle virtual sprint
by Ying Chun Guo 01 Feb '16

01 Feb '16

Hello, team In the last IRC meeting, we decided to run a midcycle virtual sprint at UTC 1330 on January 29th. For more details please go to https://wiki.openstack.org/wiki/VirtualSprints. The sprint is planned in an weekend. We welcome any people who are interested to join. Best regards Ying Chun Guo (Daisy)

3 3

i18n repo: invalid pot files
by Andreas Jaeger 30 Jan '16

30 Jan '16

funning msgfmt --check-format on the i18n repo gives a couple of violations, please check these. Exact command used: find . -type f -regex '.*\.pot?' -print0 | xargs -0 -n 1 msgfmt --check-format -o /dev/null ./i18n/i18n/locale/it/LC_MESSAGES/i18n.po:309: duplicate message definition... ./i18n/i18n/locale/it/LC_MESSAGES/i18n.po:210: ...this is the location of the first definition msgfmt: found 1 fatal error ./i18n/i18n/locale/fr/LC_MESSAGES/i18n.po:309: duplicate message definition... ./i18n/i18n/locale/fr/LC_MESSAGES/i18n.po:210: ...this is the location of the first definition msgfmt: found 1 fatal error ./i18n/i18n/locale/de/LC_MESSAGES/i18n.po:311: duplicate message definition... ./i18n/i18n/locale/de/LC_MESSAGES/i18n.po:210: ...this is the location of the first definition msgfmt: found 1 fatal error ./i18n/i18n/locale/i18n.pot:13: duplicate message definition... ./i18n/i18n/locale/i18n.pot:2: ...this is the location of the first definition msgfmt: found 1 fatal error ./i18n/i18n/locale/zh_CN/LC_MESSAGES/i18n.po:309: duplicate message definition... ./i18n/i18n/locale/zh_CN/LC_MESSAGES/i18n.po:210: ...this is the location of the first definition msgfmt: found 1 fatal error ./i18n/i18n/locale/ko_KR/LC_MESSAGES/i18n.po:309: duplicate message definition... ./i18n/i18n/locale/ko_KR/LC_MESSAGES/i18n.po:210: ...this is the location of the first definition -- 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

What's Up, Doc? 29 January 2016
by Lana Brindley 29 Jan '16

29 Jan '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone, An incredibly hot week here in the antipodes, coupled with Australia Day has meant that I haven't been particularly productive this week. Luckily, the rest of you have picked up the slack, and things have been ticking along nicely. Thanks everyone :) == Progress towards Mitaka == 68 days to go! 368 bugs closed so far for this release. RST Conversions * All planned RST conversions are now complete! 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 DocImpact * After some discussion on the dev list, we're adjusting our approach to this problem. Watch this space. == Speciality Teams == '''HA Guide - Bogdan Dobrelya''' No update this week. '''Installation Guide - Christian Berendt''' AODH install instructions merged '''Networking Guide - Edgar Magana''' Networking guide versioning has been completed, we are publishing Liberty and Mitaka releases. Networking guide ToC has been updated and missing chapter have been assigned. Etherpad with the topic missing from the guide: https://etherpad.openstack.org/p/networking-guide '''Security Guide - Nathaniel Dillon''' No update this week. '''User Guides - Joseph Robinson''' Team meetings started again this week, and the large point was an IA reorg after content merging. Other discussion point included checking in with Docs liasons for Sahara, Trove, Murano, and Magneto plus checking in with interested volunteers for the User Guide Team. '''Ops and Arch Guides - Shilla Saebi''' Reorganization of the architecture guide is on-going. We have a full team of volunteers on our wiki <https://wiki.openstack.org/wiki/Documentation/OpsGuide>, but not much traction. We need more volunteers and we were looking to do a swarm in Manchester but not enough team members attending. Looking to maybe set one up for Austin. '''API Docs - Anne Gentle''' No update this week. '''Config Ref - Gauvain Pocentek''' No update this week. '''Training labs - Pranav Salunke, Roger Luethi''' Liberty support continues to make good progress. We can now launch an instance VM. Some clean up and reviewing still needs to be done. '''Training Guides - Matjaz Pancur''' Preparations for Austin Upstream training (https://review.openstack.org/#/c/271006/) New landing page for Training guides (http://docs.openstack.org/draft/training-guides/. '''Hypervisor Tuning Guide - Joe Topjian''' An update to to the Guide was posted back in December with a call for participation: http://lists.openstack.org/pipermail/openstack-operators/2015-December/0091… == Doc team meeting == Next meetings: US: Wednesday 3 February, 14:00 UTC APAC: Wednesday 10 February, 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… Note that there is currently discussion about moving the US meeting four hours later to 20:00 UTC. If you have a strong opinion on this matter, make sure you weigh in on the mailing list thread: http://lists.openstack.org/pipermail/openstack-docs/2016-January/008206.html - -- 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/ iQEcBAEBCAAGBQJWquVYAAoJELppzVb4+KUyBTQH/0M+ixT7g/MIePoZpFms5aSU SvLV/rAJe1dKbB2tNfq5ozNcWS/uMHB+w4bzHGjP+xexOvTUZNoBrKGLcufADMSS ekOMITnr69PLlXh5e+/G55/02sZUFmmq4ZC2xmDrgGbwZLohbLUA/L1G3o+oJGYy 2/KrNAQCutkEKTNwAN4NkA+cbSj8jM8UyVWfFzfEbywSmpmrrQyetEhfmZPj3g9t 7cUnqrRegHI7mwPGeLyM3O2bIj3CLKsmWDFEfzOfoUGDGDCQ6yGj8iv8u4PuA6Zt Mw041/PII0LWDCSvovYnsRoZXMcRGVFfWdBvrOVZaGZfVhZLK/2BrZPIr+r6EzA= =eKF8 -----END PGP SIGNATURE-----

1 0

Re: [Openstack-i18n] IBM translations to contribute
by Akihiro Motoki 28 Jan '16

28 Jan '16

Hi Doug, First, I don't have any strong opinion on importing Mitaka translation contribution from IBM. Any decision is okay to me. The reason is described below. In addition, as an i18n active member, growing OpenStack translation folks is important but each language team should be a team. All comments below is as one of Japanese team reviewer who reviewed about 50% of strings (> 10000 messages) in Liberty release. I hope the same thing never happens in the Nxx release. Before going to the detail, I must apologize my following message is rude, but let me share my feeling as an active Japanese reviewer. 2016-01-13 0:02 GMT+09:00 Douglas Fish <drfish(a)us.ibm.com>: > Hi Akihiro, > > I understand your concern. These are translations that were completed > outside of Zanata, using our previous process. They were translated using > the same guidelines as the previous IBM contributions. While they are > professionally done and well tested, they have not been written to conform > to OpenStack community guidelines. It's likely any issues that existed in > the previous IBM translations will exist with these as well. Personally I was disappointed significantly with this. I am feeling that my effort to review Japanese IBM translations in Liberty cycle should not be done. I and some reviewers spent not small amount of time to review them because we believe our comments will be feedback-ed to Mitaka translations, but it turns out that it wasted the time. Regarding Japanese translations, the contributed translations did not have the enough quality that we could release them as-is from various points. * Not a small number of terminologies used were not natural to experienced OpenStack operators, * Strings were translated but it seems actual context where strings were used were not checked, especially substitutions (like %s, %(xxx)s), * There are many inconsistency with the existing team guidelines. (I have various experiences of translating Japanese certification exam for IT engineers and I believe I know what quality is ready for such purposes) We left many comments in Zanata but they are not referred at all.............. We, at least me, made these comments to share our guidelines..... In addition, Japanese translation team provides a lot of information including our glossary, contact points, discussion channels through OpenStack wiki page, but it does not work so far.... I will stop writing my feeling here. > I agree this is not a good long term way to complete translations. I'm not > sure if you are aware, but our Italian translation center has completed a > pilot of working directly in Zanata. Notice the high completion percentage > for Horizon Italian. I expect to have broader participation in this area > during the translation of Mitaka. It depends on the progress of translations of each language and I hope it works well. In addition, growing translation community is a good thing in the longer term. > We would like to contribute these translations to help with the OpenStack > translation effort. I understand that because they were not translated with > the same guidelines they may instead be burdensome to the translators. I > believe this is the purpose of creating the branch for offline translations: > so that language coordinators can evaluate if the translations are actually > beneficial to our OpenStack translation efforts, or if they are inconsistent > with the language's guidelines and more trouble than they are worth. I > certainly understand that creating and populating a branch does not mean > that these translations will actually be accepted. For Mitaka translation contribution, I don't have a strong opinion and either option is okay to me. If we talk about only Japanese translations of Mitaka release, server translations do not affect GUI translations (and CLI translation if any). According to our survey in Japan, most of all operators prefer to English messages. Considering these situations, I think Japanese translations of server projects can be shipped as-is without reviews. We can discuss the translation guidelines for Nxxx release translations to address inconsistencies and mismatches. > I'd like to have the branch created so that the review can take place. What > do you think? As mentioned above, I am okay with either decision. I am just concerned and disappointed with the fact that all translation efforts are being done completely separately and hope it never happens. Akihiro > > Doug > > > ----- Original message ----- > From: Akihiro Motoki <amotoki(a)gmail.com> > To: Douglas Fish/Rochester/IBM@IBMUS > Cc: "openstack-i18n(a)lists.openstack.org" > <openstack-i18n(a)lists.openstack.org> > Subject: Re: [Openstack-i18n] IBM translations to contribute > Date: Mon, Jan 11, 2016 11:09 PM > > Hi Doug, > > Thanks for continuing the effort. > > I have two questions. > > First, why do we need to use a branch again. > We already set up the translation platform and IBM team can translate > on Zanata directly > as we discussed in Liberty cycle. There is no reason to use a branch > and push translation bursty again. > > Second, is existing community translation guideline per language team > honored in the contributed translations? > When talking about Japanese, we saw a lot of different translation > guidelines on wording in the last IBM translation contributed in > Liberty. > As a reviewer, we don't want to comment the same thing again. > After we Japanese review team reviewed Liberty contribution from IBM, > we don't receive any feedback/response/discussion from IBM team, > so I am afraid we need to do the similar again. It need to be avoided. > Otherwise reviewers will lose their energy. > Could you comment on the situation? > > Thanks, > Akihiro > > > 2016-01-12 12:54 GMT+09:00 Douglas Fish <drfish(a)us.ibm.com>: >> We have translations to contribute for languages >> de es fr it ja ko_KR pt_BR ru zh_CN zh_TW >> for ceilometer, cinder, glance, keystone, neutron, and nova >> >> These are additional translations performed by the same teams that >> translated our previous contributions. They have been reviewed and tested. >> I >> estimate up to 35K messages will be contributed across the 10 languages >> and >> 6 components. >> >> Following the process outlined here >> >> http://lists.openstack.org/pipermail/openstack-i18n/2015-September/001388.h… >> I am requesting that a branch be created in Zanata to facilitate review of >> these translations by the language coordinators. >> >> Thanks >> >> Doug >> >> >> _______________________________________________ >> Openstack-i18n mailing list >> Openstack-i18n(a)lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n >> > > > >

6 7

Fwd: [openstack-dev] [all][i18n] Rework of translation setup
by Andreas Jaeger 28 Jan '16

28 Jan '16

FYI, I'll copy resources around for python-* and oslo.* projects, Andreas -------- Forwarded Message -------- Subject: [openstack-dev] [all][i18n] Rework of translation setup Date: Thu, 28 Jan 2016 13:13:50 +0100 From: Andreas Jaeger <aj(a)microfocus.com> Reply-To: OpenStack Development Mailing List (not for usage questions) <openstack-dev(a)lists.openstack.org> Organization: SUSE Linux GmbH, Nuernberg, GF: Felix Imendörffer, Jane Smithard, Graham Norton , HRB 21284 (AG Nuernberg) To: OpenStack Development Mailing List (not for usage questions) <openstack-dev(a)lists.openstack.org> Projects that want to setup translations for their repositories run into a few common problems and we're addressing these now to make the setup for everybody easier. The problems they run into came from limitations of the current infra scripts, so we rework the infra scripts. We want to have a simple and consistent setup for translations - with a sensible consistency. Right now it’s consistent for python projects but not sensible in some cases. See here for the full spec: http://specs.openstack.org/openstack-infra/infra-specs/specs/translation_se… We're working basically on two major changes: a) The same setup for django projects. b) Locate files for python projects in a better place. b) only affects olso.* and python-*client projects: We need to update setup.cfg, your i18n file and move the files from $reponame/locale/$reponame.pot to $modulename/locale/modulename.pot - so placing it in your source directory and not besides it. While we move files around, we also stopped syncing of translations for olso* and python-client projects. So, please review these changes quickly and merge them. For a) we will review each django project and send patches for them as well. Also, we make our scripts more robust - and will document this properly. If you have any questions, please reach out to us. We hope that this will make translation setup for projects easier, Akihiro Motoki & Andreas Jaeger -- 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 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 -- 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

1 0

Re: [Openstack-i18n] IRC meeting today
by Jeremy Stanley 22 Jan '16

22 Jan '16

On 2016-01-22 14:17:23 +0800 (+0800), Ying Chun Guo wrote: [...] > Zanata has API to query translators activities. [...] Oh, that's excellent news! Maybe the update I heard we were still needing was so that we could let non-administrators query that? > Adding them to "extra ATCs" is a way. > Are there any other options to grant them the election rights ? At the moment you'll need to continue updating the extra-atcs list. The tool which queries our contributors in Gerrit could be extended to also query Zanata, but I haven't even seen the API documentation for that yet so I can't gauge how long it would take me to integrate into what I have. Longer term, of course we want this data source automatically integrated with our contributor listing tools. For the curious, https://review.openstack.org/263971 is the current state of development on the new framework I'm using for determining electoral rolls and qualifiers for contributor summit codes. -- Jeremy Stanley

1 0

IRC meeting today
by Ying Chun Guo 22 Jan '16

22 Jan '16

Hello, team We will have our regular meeting today, at 1300UTC in #openstack-meeting. I'm going to cover following topics: * Discussion: Glossary management process * Discussion: IBM contributions * Status update: Installation guide translation * Status update: Translation check website * Status update: Stackalytics feature Feel free to propose other topics if you like. Best regards Ying Chun Guo (Daisy)

3 3

What's Up, Doc? 22 January 2016
by Lana Brindley 22 Jan '16

22 Jan '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone, We seem to be more or less back into the swing of things here in docs land this week, with our meeting schedule back up and running, and now our very first full-length newsletter for 2016! We only have two and a half months until Mitaka goes out, but we're in great shape so far, with 345 bugs dealt with, and all the planned RST conversions complete. Most of the discussion this week has been around API documentation and Fairy Slipper, Docs Tools and some site theme changes, and a little back and forth on meeting times. == Progress towards Mitaka == 75 days to go! 345 bugs closed so far for this release. RST Conversions * All RST conversions are now complete! Well done to all the contributors and reviewers who made this happen so quickly this time around. We are now, with only a couple of exceptions, completely converted. Great job :) 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 DocImpact * After some discussion on the dev list, we're adjusting our approach to this problem. Watch this space. == Speciality Teams == '''HA Guide - Bogdan Dobrelya''' Meeting moved http://lists.openstack.org/pipermail/openstack-docs/2016-January/008209.html. Kenneth finished his Galera patch https://review.openstack.org/#/c/263075/, there were also several patches from different contributors, so things are improving. '''Installation Guide - Christian Berendt''' AODH instructions near completion, EU/US meeting moved (Every two weeks (on even weeks) on Tuesday at 1600 UTC), APAC meeting will be dropped the next weeks if if not more participants join. '''Networking Guide - Edgar Magana''' No update this week. '''Security Guide - Nathaniel Dillon''' No update this week. '''User Guides - Joseph Robinson''' One patch combining Images and Instances content merged, and a patch on Shared File Systems is now available for review. User Guide team meetings are set to begin next Thursday, with guidelines for combining admin and cloud admin files a topic for discussion. '''Ops and Arch Guides - Shilla Saebi''' No update this week. '''API Docs - Anne Gentle''' Anne imported and triaged over 60 GitHub Issues into Launchpad bugs. Anne working on build jobs for making API docs with fairy-slipper: https://review.openstack.org/#/c/269809. Anne emailed over 25 individuals about the plans for API docs and answered follow-up questions. Karen worked on validated Swagger: https://review.openstack.org/#/c/266527/. Need to release fairy-slipper this week or next. '''Config Ref - Gauvain Pocentek''' No update this week. '''Training labs - Roger Luethi''' Liberty is making good progress, trying to get Liberty patches working. Early beginnings of Fedora support switched to CentOS. Copy-on-write disks for KVM. Bug fixing and refactoring, as usual. Early work on python port. Plan to host training labs on a web page. '''Training Guides - Matjaz Pancur''' German translation of the Upstream training (http://docs.openstack.org/de/upstream-training/) - this makes 3 full translations (en, de, ko_kr), ja is at 80%. A patch that enables direct bug reporting on the slides (https://review.openstack.org/#/c/259654/) several other patches. '''Hyperviser Tuning Guide - Joe Topjian''' No update this week. == Core Team Changes == The next core team review will occur on 1 February. In the meantime, it's probably a good time to go over what being a core means, and how the review system works. For more detail, see the Contributor Guide: http://docs.openstack.org/contributor-guide/docs-review.html Docs cores have the ability to +2 docs reviews, and they also have the ability to merge reviews. Reviews are merged by cores only once there's been *two* +2 votes, and at least one +1. There are very few exceptions to this rule, for changes that need to go through very quickly to resolve gate breakages or similar, but this rule holds in just about every situation. Cores are assigned based on merit, usually through the core review process that we do every month. During a core review, the PTL gathers statistics on reviews made, and patches created and merged, and uses that to determine who should be added to (or removed from) the core list. That then goes to a vote of the existing core team before being actioned and announced. Core team members also have the ability to nominate (and vote on) exceptional team members, where the statistics might not reflect the amount of effort they have put in. If you ever have any questions about becoming a docs core, or about getting your docs patch merged, you can contact the team on the usual docs mailing list, or ping any of us on IRC. == Doc team meeting == The US team meeting was held last week, you can read the minutes here: https://wiki.openstack.org/wiki/Documentation/MeetingLogs#2016-01-20 Next meetings: APAC: Wednesday 27 January, 00:30 UTC US: Wednesday 3 February, 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… Note that there is currently discussion about moving the US meeting four hours later to 20:00 UTC. If you have a strong opinion on this matter, make sure you weigh in on the mailing list thread: http://lists.openstack.org/pipermail/openstack-docs/2016-January/008206.html - -- 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/ iQEcBAEBCAAGBQJWoafKAAoJELppzVb4+KUyFR8H/1so79V/BvFSAehklcbyDmZG JYkHQwrMUiTREN0y4l2ccegtgYWKeXEd01holKTMxxzR1KAcibi2eBMGjizNbIdt L8Add2BIPB8zwlqR0zrBAVKzecUth4EpvWLBTU4UDuHIHoF6cyOL3RZWKmkEg7/o GD7H/Yt264qFFPmQ8t8Flq5mUE892s2aReDVFkXPmmkNzBtIGDmzu13P6Y5zX4YX xzUSWJmBDTJPaz/0IsG8Sc46R3gs15hV7wtcCPwVtQXVZ18mKkYYz02zKQzpW518 Z8ysKgwHYkRhn+cxgsg10bV8/NePyxvgvHnknTLpbBZOV700kCmSTEmP3V3LUQw= =6VAi -----END PGP SIGNATURE-----

1 0