Open Stack

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The best way to track what the documentation team are doing is to follow
the newsletters I send out every week[1]. I can add the i18n list to the
distribution for that, if you think it helps?

I'll also send mail to the speciality team leads, asking them to update
you with their Liberty progress.

Does that help?

Lana

1: https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc

On 16/06/15 05:07, Akihiro Motoki wrote:
> Hi,
> 
> Very late reply :-(
> 
> Is there any reference wiki page or something to track the current status
> in the side of Documentation team?
> 
> I am just afraid that having this kind of page in I18N team side tends to
> lead
> the lack of interest from the docs team. I am just raising a negative
> question
> to explore how we can sync the status with a minimum effort.
> 
> Thanks,
> Akihiro
> 
> 2015-05-22 2:57 GMT+09:00 Lana Brindley <openstack at lanabrindley.com>:
> 
>> This is a great idea!
>>
>> Daisy: I would also like to sync up with you again (while you’re still in
>> Vancouver, if possible), to discuss our plan for migrating the next
>> documents to RST.
>>
>> L
>>
>> On 21 May 2015, at 10:42 am, Ying Chun Guo <guoyingc at cn.ibm.com> wrote:
>>
>> Thank you, Anne.
>>
>> We use a wiki page to track the status of documentation:
>>
>> https://wiki.openstack.org/wiki/I18nTeam/docs-translation#Document_categorize
>>
>> I hope specialty team leads could keep an eye on this table.
>> If there is any changes of your documents, like, changing from stable to
>> unstable, changing from unstable to stable,
>> let the translation team know by sending an email to openstack-i18n
>> mailing list.
>> So that we could make a translation plan for your documents.
>>
>> Thanks.
>> Best regards
>> Ying Chun Guo (Daisy)
>>
>>
>> Anne Gentle <annegentle at justwriteclick.com> wrote on 2015/05/22 01:35:14:
>>
>>> From: Anne Gentle <annegentle at justwriteclick.com>
>>> To: "openstack-docs at lists.openstack.org" <openstack-
>>> docs at lists.openstack.org>, "openstack-i18n at lists.openstack.org"
>>> <openstack-i18n at lists.openstack.org>
>>> Date: 2015/05/22 01:35
>>> Subject: [Openstack-i18n] Specialty teams connecting to translation team
>>>
>>> Hi all,
>>> I'm sitting here in Vancouver next to Daisy (Ying Chun Guo) who
>>> leads the i18N efforts for OpenStack. She would like each specialty
>>> team lead to connect with the i18N team to communicate the amount of
>>> change expected so that they can evaluate the timing of translation,
>>> and how much is done that can be translated.
>>>
>>> We also had a session with the i18N team and want to work on more
>>> communication with each team, and I think the specialty team leads
>>> are a great way to start that effort.
>>>
>>> Thoughts or ideas? Let us know.
>>> Thanks,
>>> Anne
>>>
>>> --
>>> Anne Gentle
>>> annegentle at justwriteclick.com
>> _______________________________________________
>>> Openstack-i18n mailing list
>>> Openstack-i18n at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
>> _______________________________________________
>> OpenStack-docs mailing list
>> OpenStack-docs at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>>
>>
>> Lana Brindley
>> Technical Writer
>> Rackspace Cloud Builders Australia
>>
>>
>>
>>
>> _______________________________________________
>> OpenStack-docs mailing list
>> OpenStack-docs at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>>
>>
> 


- -- 
Lana Brindley
Technical Writer
Rackspace Cloud Builders Australia
http://lanabrindley.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJVf1sKAAoJELppzVb4+KUyR0oH/2qj9JEhgtt8Mf+d6THyVm/a
MRJ96rXugvrop4nAsxPr7KpUOA3ipdeBG04rKClVPq+cdBTwWNsiHeplSHwTB+US
qDYkxCrimDR5FHdGuJgJQANaEfi0YsxLyLzCAaSKHaGymPvj4wsehFMcD7pgAgKw
YlOIL5uhh0l47sKD3XTxLxD07tL+4+wi8SDG+O3u4toVw9UmIj2onQbPzaxP+ttZ
a/xCVs0mNT5G57Okbm+Y4lIzqqNR7sqWxgVIPWDl/yz9vBNf6qtLEyGWS5/94mZ8
wqM3KYz+u3lFXKJf6AsTTTEW5lD97k+ZIeySR1la8qPshYTZn0NR2x7Nsd3FauE=
=+mvc
-----END PGP SIGNATURE-----