<div dir="ltr">Hi Ian,<div><br></div><div>Thanks for more considerations.</div><div><br></div><div class="gmail_quote"><div dir="ltr">2018年5月30日(水) 0:42 Ian Y. Choi <<a href="mailto:ianyrchoi@gmail.com">ianyrchoi@gmail.com</a>>:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello Akihiro,<br>
<br>
Looks so amazing! Thanks a lot for your lots of progress on translated <br>
edge computing white paper publication<br>
with RST-based method, which is much preferred from I18n team, Docs <br>
team, and all upstream projects.<br>
<br>
In my honest opinion, using *one* unified tool in all OpenStack area <br>
including official projects and publication<br>
would be best, but more discussion and agreement on multiple different <br>
teams (+ Foundation) would be needed I think.<br>
When I attended to a Forum on ops-guide during Summit last week, I found <br>
that ops-guide would want to convert from Wiki-based format to RST-based <br>
format.<br>
It would be pretty nice if we all use RST-based documents to many <br>
places, but more things (e.g., current implementation,<br>
maintenance, ...) need to be considered I think.<br></blockquote><div><br></div><div>RST can start from simpler cases and potentially supports more complicated cases.</div><div>I personally prefer to using RST-based documents everywhere.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Now I would like to ask more opinions on:<br>
<br>
- @amotoki: How long does it take to convert original text file + texts <br>
on a PDF file to RST-based formats?<br>
Did you do it manually and would it be also <br>
rather easy for other members such as me or Foundation staff?<br></blockquote><div><br></div><div>Setting up the initial repo and converting the original text into RST format was really simple.</div><div>It tooks only less than our hour.</div><div><br></div><div>In this case, I took extra two or three hous to cover the following, but I don't think it always happens.</div><div>- to adjust Japanese translation to cover differences between the published PDF version</div><div> and the text uploaded to Zanata</div><div>- to automate the above differences for other languages</div><div> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
- @Foundation: Is it okay for translated white papers to publish with <br>
RST-based tools as Akihiro did, since RST-based tools<br>
are much easier to publish translated <br>
documents and sync translated resources (po files)?<br>
<br>
- @Foundation: OpenStack documents use CC BY 3.0. Would it be fine for <br>
translated white papers to use similar CC<br>
rather than CC BY-ND 4.0, for original edge <br>
computing white paper document or cause intellectual issues?<br></blockquote><div><br></div><div>I don't mind using different licenses even if they don't block community collaborations.<br></div><div>We have a number of documentations (TC governed project documents, SIG documents, .....),</div><div>so it would be nice if we select licenses consistently.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
- All (including translators): For design stuff, just making use of <br>
openstackdocstheme would be pretty fine?<br>
For example, I forked from Akihiro's github repo, and published <br>
using openstackdocstheme<br>
to <a href="https://ianychoi.github.io/edge-computing-whitepaper/" rel="noreferrer" target="_blank">https://ianychoi.github.io/edge-computing-whitepaper/</a><br>
(e.g., <a href="https://ianychoi.github.io/edge-computing-whitepaper/ja/" rel="noreferrer" target="_blank">https://ianychoi.github.io/edge-computing-whitepaper/ja/</a> ).<br></blockquote><div><br></div><div>Using openstackdocstheme would be nice when it is published in <a href="http://openstack.org">openstack.org</a>.</div><div>openstackdocstheme is intended to use for OpenStack *official* projects,<br></div><div>so I just didn't use it as an initial effort.</div><div><br></div><div>If we continue to use another variants of CC and openstackdocstheme,</div><div>we can update openstackdocstheme to support more CC licensees.</div><div><br></div><div>Thanks,</div><div>Akihiro</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<br>
With many thanks,<br>
<br>
/Ian<br>
<br>
<br>
Akihiro Motoki wrote on 5/29/2018 11:37 PM:<br>
> Hi Ildiko and all,<br>
><br>
> I am happy to hear that HTML-based publishing is now on the table :)<br>
> I am synced with Ian and Frank on this topic, though I failed to join <br>
> the conversation at Vancouver.<br>
> RST based process is used much in the community and translation <br>
> publishinng of project docs which Ian and us are working on will make <br>
> the continuous publishing easier.<br>
> I am happy to help setting up a new doc infrastructure and/or <br>
> publishing translations.<br>
><br>
> Regarding the license, CC BY-ND license turned out a bit too strict in <br>
> our collaborative works when I checked the current one.<br>
> Hopefully we can get a good conclusion for further similar cases.<br>
><br>
> Thanks,<br>
> Akihiro<br>
><br>
><br>
><br>
> 2018年5月29日(火) 23:19 Ildiko Vancsa <<a href="mailto:ildiko.vancsa@gmail.com" target="_blank">ildiko.vancsa@gmail.com</a> <br>
> <mailto:<a href="mailto:ildiko.vancsa@gmail.com" target="_blank">ildiko.vancsa@gmail.com</a>>>:<br>
><br>
> Hi Akihiro and All,<br>
><br>
> Thank you for your efforts on helping with publishing the white<br>
> paper in additional languages.<br>
><br>
> I talked to Ian and Frank last week about this topic and the<br>
> conundrum on the Foundation side whether or not to do the print<br>
> version for the translations as that is what slows down the<br>
> process a lot due to the design work it requires.<br>
><br>
> We got to the conclusion with our team from the Foundation (cc’ed<br>
> Allison, Jimmy and Wes) to do HTML-based publishing to reduce this<br>
> overhead. We need to clarify now on the process and as Jeremy<br>
> indicated the licensing as well.<br>
><br>
> Thanks,<br>
> Ildikó<br>
><br>
><br>
> > On 2018. May 29., at 15:50, Jeremy Stanley <<a href="mailto:fungi@yuggoth.org" target="_blank">fungi@yuggoth.org</a><br>
> <mailto:<a href="mailto:fungi@yuggoth.org" target="_blank">fungi@yuggoth.org</a>>> wrote:<br>
> ><br>
> > On 2018-05-29 18:50:23 +0900 (+0900), Akihiro Motoki wrote:<br>
> > [...]<br>
> >> NOTE: Anyway I need to grant it from the foundation because CC<br>
> >> Attribution-NoDerivatives 4.0 International license does not allow<br>
> >> me to share translations without permission. I updated this files<br>
> >> only for discussion and will close this soon.<br>
> > [...]<br>
> ><br>
> > It seems like this is a really poor choice of license as it's<br>
> > impairing open collaboration. Even Creative Commons suggests that<br>
> > the CC BY-ND license is unsuitable for free cultural works:<br>
> ><br>
> > <a href="https://creativecommons.org/share-your-work/public-domain/freeworks/" rel="noreferrer" target="_blank">https://creativecommons.org/share-your-work/public-domain/freeworks/</a><br>
> ><br>
> > We should see about getting this changed to CC BY like is used for<br>
> > other collaborative works produced by our community.<br>
> > --<br>
> > Jeremy Stanley<br>
> > _______________________________________________<br>
> > openstack-sigs mailing list<br>
> > <a href="mailto:openstack-sigs@lists.openstack.org" target="_blank">openstack-sigs@lists.openstack.org</a><br>
> <mailto:<a href="mailto:openstack-sigs@lists.openstack.org" target="_blank">openstack-sigs@lists.openstack.org</a>><br>
> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs</a><br>
><br>
><br>
> _______________________________________________<br>
> openstack-sigs mailing list<br>
> <a href="mailto:openstack-sigs@lists.openstack.org" target="_blank">openstack-sigs@lists.openstack.org</a><br>
> <mailto:<a href="mailto:openstack-sigs@lists.openstack.org" target="_blank">openstack-sigs@lists.openstack.org</a>><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> OpenStack-I18n mailing list<br>
> <a href="mailto:OpenStack-I18n@lists.openstack.org" target="_blank">OpenStack-I18n@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n</a><br>
<br>
<br>
</blockquote></div></div>