<html><head><meta http-equiv="Content-Type" content="text/html charset=GB2312"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I find the framework/ application a real pleasure to work with.<div><br><div>@Doc team : I'll be more focusing on french translation rather than bug fixes for the days to come :-)</div><div><br></div><div> <br><div apple-content-edited="true">
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: 'Lucida Grande'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="font-family: Helvetica; "><span class="Apple-style-span" style="font-family: Helvetica; "><b style="color: rgb(19, 112, 138); ">Nuage & Co - Razique Mahroua</b></span><span class="Apple-style-span" style="color: rgb(19, 112, 138); font-family: Helvetica; "><b> </b></span><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="border-collapse: separate; font-variant: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span class="Apple-style-span" style="border-collapse: separate; font-variant: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-weight: normal; font-style: normal; "><font class="Apple-style-span" color="#13708a"><a href="mailto:razique.mahroua@gmail.com">razique.mahroua@gmail.com</a></font></div></span><br class="Apple-interchange-newline"><span></span><span style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-weight: normal; font-style: normal; "></span><span style="color: rgb(0, 0, 0); font-weight: normal; "></span></span><span><img height="125" width="125" id="4c40beda-8ddd-49c6-af26-1f5712dc32b5" apple-width="yes" apple-height="yes" src="cid:00E07450-433E-43E6-9005-48B8FD5C669F@la.fabrique"></span>
</span></span></span></div>
<br><div><div>Le 11 juil. 2012 ¨¤ 15:09, Ying Chun Guo <<a href="mailto:guoyingc@cn.ibm.com">guoyingc@cn.ibm.com</a>> a ¨¦crit :</div><br class="Apple-interchange-newline"><blockquote type="cite"><p><font size="2" face="sans-serif">Thank you! I have approved your request. If you meet with any problem, please let me know.</font><br>
<br>
<font size="2" face="sans-serif">Regards<br>
Daisy</font><br>
<br>
<tt><font size="2">Razique Mahroua <<a href="mailto:razique.mahroua@gmail.com">razique.mahroua@gmail.com</a>> wrote on 07/11/2012 04:17:18 PM:<br>
<br>
> Razique Mahroua <<a href="mailto:razique.mahroua@gmail.com">razique.mahroua@gmail.com</a>> </font></tt><br>
<tt><font size="2">> 07/11/2012 04:17 PM</font></tt><br>
<tt><font size="2">> <br>
> To</font></tt><br>
<tt><font size="2">> <br>
> Anne Gentle <<a href="mailto:anne@openstack.org">anne@openstack.org</a>>, </font></tt><br>
<tt><font size="2">> <br>
> cc</font></tt><br>
<tt><font size="2">> <br>
> Ying Chun Guo/China/IBM@IBMCN, "diane.fleming" <br>
> <<a href="mailto:diane.fleming@rackspace.com">diane.fleming@rackspace.com</a>>, <a href="mailto:openstack-doc-core@lists.launchpad.net">openstack-doc-core@lists.launchpad.net</a></font></tt><br>
<tt><font size="2">> <br>
> Subject</font></tt><br>
<tt><font size="2">> <br>
> Re: [Openstack-doc-core] Doc translation prototype</font></tt><br>
<tt><font size="2">> <br>
> Woaw, great work sir.</font></tt><br>
<tt><font size="2">> Thanks Anne for the transcript, (and welcome Atul :-) )</font></tt><br>
<tt><font size="2">> <br>
> @Daisy : I just requested french language on Transifex, the <br>
> workflow is quite clear, thank you</font></tt><br>
<tt><font size="2">> <br>
> Nuage & Co - Razique Mahroua </font></tt><br>
<tt><font size="2">> <a href="mailto:razique.mahroua@gmail.com">razique.mahroua@gmail.com</a></font></tt><br>
<tt><font size="2">> <br>
> [image removed] </font></tt><br>
<tt><font size="2">> <br>
> Le 10 juil. 2012 ¨¤ 14:48, Anne Gentle a ¨¦crit :</font></tt><br>
<tt><font size="2">> <br>
> Fantastic news. <br>
> <br>
> I've created a blueprint here:<br>
> <a href="https://blueprints.launchpad.net/openstack-manuals/+spec/">https://blueprints.launchpad.net/openstack-manuals/+spec/</a><br>
> documentation-translation <br>
> You did all the great work with the specification, thank you so much. <br>
> <br>
> All, we discussed translation at yesterday's doc team meeting. You <br>
> can look at the transcript here:<br>
> <a href="http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/">http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/</a><br>
> openstack-meeting.2012-07-09-20.03.log.html<br>
> <br>
> Doc team, be sure you read the documents and understand the process <br>
> for translation. <br>
> <br>
> Daisy, one thing I wondered about testing is whether any of these <br>
> are complete enough translations to see an entire document in a non-<br>
> English language?<br>
> <br>
> Also, Daisy, let me know if you need any connections to the CI team.<br>
> I often talk to them on IRC in #openstack-infra. <br>
> <br>
> Thanks,<br>
> Anne<br>
</font></tt><br>
<tt><font size="2">> On Tue, Jul 10, 2012 at 4:15 AM, Ying Chun Guo <<a href="mailto:guoyingc@cn.ibm.com">guoyingc@cn.ibm.com</a>> wrote:</font></tt><br>
<tt><font size="2">> Hi, team<br>
> <br>
> Just let you know, I find a way to successfully update the translation files<br>
> when the original English sources are updated. So I think this prototype is<br>
> completed by now.<br>
> <br>
> Next step, I think it's to work with CI team to make the process <br>
> more automatic.<br>
> <br>
> To Anne, do you think we are ready to register a bule print about <br>
> translation process now?<br>
> <br>
> <br>
> ----- Forwarded by Ying Chun Guo/China/IBM on 07/10/2012 05:06 PM -----<br>
</font></tt><br>
<tt><font size="2">> <br>
> Ying Chun Guo/China/IBM</font></tt><br>
<tt><font size="2">> 07/09/2012 02:29 PM</font></tt><br>
<tt><font size="2">> <br>
> <ecblank.gif></font></tt><br>
<tt><font size="2">> To</font></tt><br>
<tt><font size="2">> <br>
> <ecblank.gif></font></tt><br>
<tt><font size="2">> Anne Gentle <<a href="mailto:anne@openstack.org">anne@openstack.org</a>>, </font></tt><br>
<tt><font size="2">> <br>
> <ecblank.gif></font></tt><br>
<tt><font size="2">> cc</font></tt><br>
<tt><font size="2">> <br>
> <ecblank.gif></font></tt><br>
<tt><font size="2">> <a href="mailto:annegentle@justwriteclick.com">annegentle@justwriteclick.com</a>, "diane.fleming" <<a href="mailto:diane.fleming@rackspace.com">diane.fleming@rackspace.com</a>>, <br>
> <a href="mailto:openstack-doc-core@lists.launchpad.net">openstack-doc-core@lists.launchpad.net</a></font></tt><br>
<tt><font size="2">> <br>
> <ecblank.gif></font></tt><br>
<tt><font size="2">> Subject</font></tt><br>
<tt><font size="2">> <br>
> <ecblank.gif></font></tt><br>
<tt><font size="2">> Doc translation prototype<doclink.gif></font></tt><br>
<tt><font size="2">> <br>
> <ecblank.gif></font></tt><br>
<tt><font size="2">> <br>
> <ecblank.gif></font></tt><br>
<tt><font size="2">> <br>
> Hi, Anne and team<br>
> <br>
> I created a prototype of document translation, to verify the <br>
> process: slicing, uploading, translating, <br>
> downloading, merging, and PDF/HTML generating.<br>
> <br>
> The source codes are in <a href="https://github.com/daisy-ycguo/openstack-manuals-i18n">https://github.com/daisy-ycguo/openstack-manuals-i18n</a>.<br>
> The document is here: <a href="https://gist.github.com/3037139">https://gist.github.com/3037139</a>.<br>
> <br>
> You can try to create a Chinese version of api-quick-start and <br>
> openstack-api-programming following<br>
> the guidance in <a href="https://gist.github.com/3037139">https://gist.github.com/3037139</a> as a coordinator. If<br>
> you meet with any problems, please<br>
> let me know.<br>
> <br>
> I don't use separate repository for each language in this prototype.<br>
> I think separate repository<br>
> will make the synchronization very complex. In this prototype, I <br>
> only keep the English DocBook and a serials of<br>
> PO files. The latest Chinese DocBook can be generated from these resources.<br>
> <br>
> There is still an important part missed in this prototype. That is: <br>
> when the original English doc book is updated, how to handle?<br>
> I'm working on it now, and will let you know the updates if I have.<br>
> <br>
> All the steps in this prototype need to be done manually. As to <br>
> automation, we can consult with CI team's to see which steps can be<br>
> integrated with Jenkins.<br>
> <br>
> Regards<br>
> Daisy<br>
> <br>
> <a href="mailto:annegentle@justwriteclick.com">annegentle@justwriteclick.com</a> wrote on 06/27/2012 05:35:19 AM:<br>
> <br>
> > Anne Gentle <<a href="mailto:anne@openstack.org">anne@openstack.org</a>> <br>
> > Sent by: <a href="mailto:annegentle@justwriteclick.com">annegentle@justwriteclick.com</a><br>
> > <br>
> > 06/27/2012 05:35 AM<br>
> > <br>
> > To<br>
> > <br>
> > <a href="mailto:openstack-doc-core@lists.launchpad.net">openstack-doc-core@lists.launchpad.net</a>, "diane.fleming" <br>
> > <<a href="mailto:diane.fleming@rackspace.com">diane.fleming@rackspace.com</a>>, Ying Chun Guo/China/IBM@IBMCN, <br>
> > <br>
> > cc<br>
> > <br>
> > Subject<br>
> > <br>
> > What's up, doc?<br>
> > <br>
> > Hi all -<br>
> > I wanted to give status updates on some in-flight items since I'm on<br>
> > vacation for a while and we'll have our next doc team meeting right<br>
> > after I get back, July 10. So, here goes:<br>
> > <br>
> > DocImpact flag - The CI team is designing a flag system integrated<br>
> > into Gerrit that'll work something like this:<br>
> > 1. Developer makes a patch and submits it to one of the OpenStack projects.<br>
> > 2. Developer puts "DocImpact" somewhere in the commit message.<br>
> > 3. A Gerrit hook sends an email with a <a href="http://review.openstack.org">review.openstack.org</a> link to<br>
> > the <a href="mailto:openstack-doc-core@lists.launchpad.net">openstack-doc-core@lists.launchpad.net</a> email.<br>
> > 4. A member of the doc team can click through on the<br>
> > <a href="http://review.openstack.org">review.openstack.org</a> link to take a look at the patch and determine<br>
> > whether to log a Doc Bug (as a task), review the patch if it contains<br>
> > docs, or some other action.<br>
> > Any discussion on this new flag implementation?<br>
> > <br>
> > Deployment Template Blueprint - I've revised this again from F2 (which<br>
> > is July 5th) to F3 (mid-August) because I'm talking to third-party<br>
> > editors about including case studies for TryStack or Mediawiki in one<br>
> > of their upcoming books, licensed Creative Commons. What I've found<br>
> > though is that TryStack is still working on their Essex upgrade and<br>
> > I'm not sure if Mediawiki is staying on Diablo. So, this blueprint is<br>
> > in flight but in a holding pattern. Anyone is welcome to pick up on it<br>
> > and start writing though. Good way to be a third-party author if<br>
> > you're interested in such things!<br>
> > <br>
> > Content Sharing Blueprint - I'm planning with a contract team to<br>
> > devise a proof-of-concept for<br>
> > <a href="https://blueprints.launchpad.net/openstack-manuals/+spec/design-">https://blueprints.launchpad.net/openstack-manuals/+spec/design-</a><br>
> > content-sharing<br>
> > in the next two-three months. Hopefully we'll have easier content<br>
> > sharing for API guides by the end of summer.<br>
> > <br>
> > API Try-it-out Blueprint - On hold, no resources to work on this <br>
> > that I know of.<br>
> > <br>
> > Metadata on built documents - Looking for status on this from the<br>
> > clouddocs tool team.<br>
> > <br>
> > TryStack and <a href="http://api.openstack.org">api.openstack.org</a> - TryStack will be upgraded to Essex<br>
> > and when that happens, the <a href="http://api.openstack.org">api.openstack.org</a> site needs to change to<br>
> > display v2 for all Compute API calls instead of v1.1. Noting here so<br>
> > you all know there's a dependency on TryStack for updating<br>
> > <a href="http://api.openstack.org">api.openstack.org</a>.<br>
> > <br>
> > Translations - I've been discussing the design of translations for all<br>
> > projects and for the documentation itself with Daisy (Ying Chun Guo,<br>
> > CCed). The Maven plugin,<br>
> > <a href="https://github.com/rackspace/clouddocs-maven-plugin">https://github.com/rackspace/clouddocs-maven-plugin</a>, now supports<br>
> > building Chinese language PDFs for example. In addition, Daisy has<br>
> > created a "slicing" tool that creates .pot files that she can upload<br>
> > to Transifex, the website that OpenStack translators can use to<br>
> > collaborate on translations. One big audacious idea is to have<br>
> > separate repositories for each language for documentation. Separate<br>
> > repos per language would enable native-language reviewers to review<br>
> > translations - and it would also enable native-language speakers to<br>
> > write their own documents rather than only translating. I pitch this<br>
> > idea because I've seen it work well with FLOSS Manuals - such as<br>
> > <a href="http://fr.flossmanuals.net">fr.flossmanuals.net</a> - where there's a native speaker growing the<br>
> > community around the docs. It's a way of leaning into the chaos - we<br>
> > can't ultimately control releases and languages and the amount that's<br>
> > completed, so maybe we let each language have a level of completion.<br>
> > Would love thoughts on this.<br>
> > <br>
> > That's what's up, doc - let me know if you have questions and I'd love<br>
> > discussion around these items.<br>
> > <br>
> > Thanks,<br>
> > Anne<br>
> > </font></tt><br>
<tt><font size="2">> <br>
> <br>
> -- <br>
> Mailing list: <a href="https://launchpad.net/~openstack-doc-core">https://launchpad.net/~openstack-doc-core</a><br>
> Post to : <a href="mailto:openstack-doc-core@lists.launchpad.net">openstack-doc-core@lists.launchpad.net</a><br>
> Unsubscribe : <a href="https://launchpad.net/~openstack-doc-core">https://launchpad.net/~openstack-doc-core</a><br>
> More help : <a href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a></font></tt><br>
<tt><font size="2">> [image removed] </font></tt></p></blockquote></div><br></div></div></body></html>