<div dir="ltr"><div><div style="background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial"><font color="#202124" face="Roboto, RobotoDraft, Helvetica, Arial, sans-serif"><div style="color:rgb(34,34,34);font-family:sans-serif;text-decoration-style:initial;text-decoration-color:initial"><div style="background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial">Hi all,</div><div style="background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial"><br></div><div style="background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial"># I added<span> </span><span style="color:rgb(32,33,36);font-family:Roboto,RobotoDraft,Helvetica,Arial,sans-serif">edge-computing ML as the edge computing team uses a separate list other than the SIG ML.</span><br></div></div><div style="color:rgb(34,34,34);font-family:sans-serif;text-decoration-style:initial;text-decoration-color:initial"><font color="#202124" face="Roboto, RobotoDraft, Helvetica, Arial, sans-serif"># The original discussion happened in openstack-sigs ML. I just forgot to add the edge ML.</font></div><div style="color:rgb(34,34,34);font-family:sans-serif;text-decoration-style:initial;text-decoration-color:initial"><font color="#202124" face="Roboto, RobotoDraft, Helvetica, Arial, sans-serif"><br></font></div></font></div><div style="background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial"><font color="#202124" face="Roboto, RobotoDraft, Helvetica, Arial, sans-serif">What is the next step of the translation of the edge computing white paper with RST?</font></div><div style="background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial">My temporary translation publishing [1] should not be published as-is due to the CC BY-ND license. This is to prove how it works.<br></div><div style="background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial">I would like to move this forward and am happy to help the setup of a repo if needed.</div><div style="background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial"><br></div><div style="background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial">Where can we discuss this?</div><div style="background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial">The edge computing group meeting is not listed at <a href="http://eavesdrop.openstack.org/">http://eavesdrop.openstack.org/</a> and I don't know when and where it happens.</div><div style="background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial"><br></div><div style="background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial"><span style="color:rgb(32,33,36);font-family:Roboto,RobotoDraft,Helvetica,Arial,sans-serif">[1] <a href="https://amotoki.github.io/edge-computing-whitepaper/">https://amotoki.github.io/edge-computing-whitepaper/</a></span><br></div></div><div><div><font color="#202124" face="Roboto, RobotoDraft, Helvetica, Arial, sans-serif"><br></font></div><div><font color="#202124" face="Roboto, RobotoDraft, Helvetica, Arial, sans-serif">Thanks,</font></div><div>Akihiro</div><div><br></div><div><div class="gmail_quote"><div dir="ltr">2018年5月29日(火) 23:37 Akihiro Motoki <<a href="mailto:amotoki@gmail.com">amotoki@gmail.com</a>>:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><span style="color:rgb(34,34,34);font-family:sans-serif;font-size:14px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">Hi Ildiko and all,</span><div style="color:rgb(34,34,34);font-family:sans-serif;font-size:14px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><br></div><div style="color:rgb(34,34,34);font-family:sans-serif;font-size:14px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial">I am happy to hear that HTML-based publishing is now on the table :)</div><div style="color:rgb(34,34,34);font-family:sans-serif;font-size:14px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial">I am synced with Ian and Frank on this topic, though I failed to join the conversation at Vancouver.</div><div style="color:rgb(34,34,34);font-family:sans-serif;font-size:14px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial">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.</div><div style="color:rgb(34,34,34);font-family:sans-serif;font-size:14px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial">I am happy to help setting up a new doc infrastructure and/or publishing translations.</div><div style="color:rgb(34,34,34);font-family:sans-serif;font-size:14px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><br></div><div style="color:rgb(34,34,34);font-family:sans-serif;font-size:14px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial">Regarding the license, CC BY-ND license turned out a bit too strict in our collaborative works when I checked the current one.</div><div style="color:rgb(34,34,34);font-family:sans-serif;font-size:14px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial">Hopefully we can get a good conclusion for further similar cases.</div><div style="color:rgb(34,34,34);font-family:sans-serif;font-size:14px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><br></div><div style="color:rgb(34,34,34);font-family:sans-serif;font-size:14px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial">Thanks,</div><div style="color:rgb(34,34,34);font-family:sans-serif;font-size:14px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial">Akihiro</div><div style="color:rgb(34,34,34);font-family:sans-serif;font-size:14px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"><br></div><br></div><br><div class="gmail_quote"><div dir="ltr">2018年5月29日(火) 23:19 Ildiko Vancsa <<a href="mailto:ildiko.vancsa@gmail.com" target="_blank">ildiko.vancsa@gmail.com</a>>:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi Akihiro and All,<br>
<br>
Thank you for your efforts on helping with publishing the white paper in additional languages.<br>
<br>
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.<br>
<br>
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.<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>> 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>
> <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>
<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>
</blockquote></div></blockquote></div></div></div></div>