[OpenStack-I18n] [Openstack-sigs] Edge Computing Whitepaper Translation

Ian Y. Choi ianyrchoi at gmail.com
Tue May 29 15:42:34 UTC 2018

Hello Akihiro,

Looks so amazing! Thanks a lot for your lots of progress on translated 
edge computing white paper publication
with RST-based method, which is much preferred from I18n team, Docs 
team, and all upstream projects.

In my honest opinion, using *one* unified tool in all OpenStack area 
including official projects and publication
would be best, but more discussion and agreement on multiple different 
teams (+ Foundation) would be needed I think.
When I attended to a Forum on ops-guide during Summit last week, I found 
that ops-guide would want to convert from Wiki-based format to RST-based 
It would be pretty nice if we all use RST-based documents to many 
places, but more things (e.g., current implementation,
maintenance, ...) need to be considered I think.

Now I would like to ask more opinions on:

- @amotoki: How long does it take to convert original text file + texts 
on a PDF file to RST-based formats?
                         Did you do it manually and would it be also 
rather easy for other members such as me or Foundation staff?

- @Foundation: Is it okay for translated white papers to publish with 
RST-based tools as Akihiro did, since RST-based tools
                              are much easier to publish translated 
documents and sync translated resources (po files)?

- @Foundation: OpenStack documents use CC BY 3.0. Would it be fine for 
translated white papers to use similar CC
                             rather than CC BY-ND 4.0, for original edge 
computing white paper document or cause intellectual issues?

- All (including translators): For design stuff, just making use of 
openstackdocstheme would be pretty fine?
         For example, I forked from Akihiro's github repo, and published 
using openstackdocstheme
         to https://ianychoi.github.io/edge-computing-whitepaper/
         (e.g., https://ianychoi.github.io/edge-computing-whitepaper/ja/ ).

With many thanks,


Akihiro Motoki wrote on 5/29/2018 11:37 PM:
> Hi Ildiko and all,
> I am happy to hear that HTML-based publishing is now on the table :)
> I am synced with Ian and Frank on this topic, though I failed to join 
> the conversation at Vancouver.
> RST based process is used much in the community and translation 
> publishinng of project docs which Ian and us are working on will make 
> the continuous publishing easier.
> I am happy to help setting up a new doc infrastructure and/or 
> publishing translations.
> Regarding the license, CC BY-ND license turned out a bit too strict in 
> our collaborative works when I checked the current one.
> Hopefully we can get a good conclusion for further similar cases.
> Thanks,
> Akihiro
> 2018年5月29日(火) 23:19 Ildiko Vancsa <ildiko.vancsa at gmail.com 
> <mailto:ildiko.vancsa at gmail.com>>:
>     Hi Akihiro and All,
>     Thank you for your efforts on helping with publishing the white
>     paper in additional languages.
>     I talked to Ian and Frank last week about this topic and the
>     conundrum on the Foundation side whether or not to do the print
>     version for the translations as that is what slows down the
>     process a lot due to the design work it requires.
>     We got to the conclusion with our team from the Foundation (cc’ed
>     Allison, Jimmy and Wes) to do HTML-based publishing to reduce this
>     overhead. We need to clarify now on the process and as Jeremy
>     indicated the licensing as well.
>     Thanks,
>     Ildikó
>     > On 2018. May 29., at 15:50, Jeremy Stanley <fungi at yuggoth.org
>     <mailto:fungi at yuggoth.org>> wrote:
>     >
>     > On 2018-05-29 18:50:23 +0900 (+0900), Akihiro Motoki wrote:
>     > [...]
>     >> NOTE: Anyway I need to grant it from the foundation because CC
>     >> Attribution-NoDerivatives 4.0 International license does not allow
>     >> me to share translations without permission. I updated this files
>     >> only for discussion and will close this soon.
>     > [...]
>     >
>     > It seems like this is a really poor choice of license as it's
>     > impairing open collaboration. Even Creative Commons suggests that
>     > the CC BY-ND license is unsuitable for free cultural works:
>     >
>     > https://creativecommons.org/share-your-work/public-domain/freeworks/
>     >
>     > We should see about getting this changed to CC BY like is used for
>     > other collaborative works produced by our community.
>     > --
>     > Jeremy Stanley
>     > _______________________________________________
>     > openstack-sigs mailing list
>     > openstack-sigs at lists.openstack.org
>     <mailto:openstack-sigs at lists.openstack.org>
>     > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs
>     _______________________________________________
>     openstack-sigs mailing list
>     openstack-sigs at lists.openstack.org
>     <mailto:openstack-sigs at lists.openstack.org>
>     http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs
> _______________________________________________
> OpenStack-I18n mailing list
> OpenStack-I18n at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n

More information about the OpenStack-I18n mailing list