<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Feb 2, 2015 at 2:19 AM, Tom Fifield <span dir="ltr"><<a href="mailto:tom@openstack.org" target="_blank">tom@openstack.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span class="">On 01/02/15 23:12, Anne Gentle wrote:<br>
><br>
><br>
> On Sun, Feb 1, 2015 at 6:10 AM, KATO Tomoyuki <<a href="mailto:tomo@dream.daynight.jp">tomo@dream.daynight.jp</a><br>
</span>> <mailto:<a href="mailto:tomo@dream.daynight.jp">tomo@dream.daynight.jp</a>>> wrote:<br>
><br>
> > We have a new Sphinx theme for <a href="http://docs.openstack.org" target="_blank">docs.openstack.org</a> <<a href="http://docs.openstack.org" target="_blank">http://docs.openstack.org</a>>, called<br>
<span class="">> > openstackdocstheme. It should be available on pipy as soon as we can get it<br>
> > released. Once that's released I'll write instructions for how to apply it<br>
> > to migrated content. A huge thanks to Doug Hellman for getting it to<br>
> > releasable!<br>
> ><br>
> > We are working through migrations for the End User Guide and Admin User<br>
> > Guide, sign up for a section at<br>
> > <a href="https://wiki.openstack.org/wiki/Documentation/Migrate" target="_blank">https://wiki.openstack.org/wiki/Documentation/Migrate</a>.<br>
> ><br>
> > While migrating a chapter, I found I wanted some guidelines for how to<br>
> > migrate, so I wrote some here:<br>
> > <a href="https://wiki.openstack.org/wiki/Documentation/Migrate#Migration_Conventions" target="_blank">https://wiki.openstack.org/wiki/Documentation/Migrate#Migration_Conventions</a><br>
> > Feel free to disagree with my notes so far, but my main theme is "simplify."<br>
> ><br>
> > The Foundation is working on letting people know about the new home page<br>
</span>> > design for <a href="http://docs.openstack.org" target="_blank">docs.openstack.org</a> <<a href="http://docs.openstack.org" target="_blank">http://docs.openstack.org</a>> probably through a<br>
<span class="">> Superuser post so that we<br>
> > can dig into the techie details. :) Please let me know if you have<br>
> > questions, and realize we're working through the kinks as we go.<br>
><br>
> Do we have i18n tool chain for new format?<br>
><br>
><br>
> It is a work item to investigate how to make translations work with RST:<br>
> <a href="http://specs.openstack.org/openstack/docs-specs/specs/kilo/migrate-to-new-web-design.html#work-items" target="_blank">http://specs.openstack.org/openstack/docs-specs/specs/kilo/migrate-to-new-web-design.html#work-items</a><br>
><br>
<br>
</span>I'd just like to emphasize how critically important it is for any<br>
toolchain changes to continue to support i18n activities. Ubiquity is<br>
part of our mission, and the documentation must support this.<br>
<br>
It would seem unwise to embark on any mass migration to a new toolchain<br>
prior to this ability becoming available.<br>
<br></blockquote><div><br></div><div>Your wording is pretty harsh, Tom, I'd appreciate more faith in our community processes. Migration is quite manual so I expect the timing will be fine as laid out in the spec. Yes, we're behind on the schedule for the translation research item. </div><div><br></div><div>I've started a new thread on both this mailing list and the i18n mailing list to ask for specific technical testing for translation.</div><div><br></div><div><a href="http://lists.openstack.org/pipermail/openstack-docs/2015-February/005785.html">http://lists.openstack.org/pipermail/openstack-docs/2015-February/005785.html</a><br></div><div><br></div><div>Thanks,</div><div>Anne</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
<br>
Regards,<br>
<br>
<br>
<br>
Tom<br>
<br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">Anne Gentle<br><a href="mailto:annegentle@justwriteclick.com" target="_blank">annegentle@justwriteclick.com</a></div>
</div></div>