Open Stack

Hi all -

I wanted to give a quick update on this.  Because of some emergency 
server issues and last minute projects with the OpenStack website, we've 
had to push these back.  We're targeting July 13th for Edge (and 
hopefully Containers) whitepaper.

I'll also add that as part of the plan, we will be creating a new 
template in our system to make it MUCH easier to push future whitepaper 
content directly to Zanata.  I realize this feels a little slow and 
painful and everyone is eager to get it up, but I think we'll have a 
very good system once we're done.

Thank you all for your patience!
Jimmy

Jimmy McArthur wrote:
> We are currently targeting June 25 for the initial version of the Edge 
> whitepaper.  However, I'll know more by EOW next.
>
> Cheers,
> Jimmy
>
> Ildiko Vancsa wrote:
>> Hi Akihiro,
>>
>> It is on our priority list to put up the translated versions in an online format as well as work out to have the .po files available.
>>
>> Jimmy is looking into it and will give an update once we got some progress.
>>
>> Thanks and Best Regards,
>> Ildikó
>>
>>
>>> On 2018. Jun 8., at 10:14, Akihiro Motoki<amotoki at gmail.com>  wrote:
>>>
>>> Hi all,
>>>
>>> # I added edge-computing ML as the edge computing team uses a separate list other than the SIG ML.
>>> # The original discussion happened in openstack-sigs ML. I just forgot to add the edge ML.
>>>
>>> What is the next step of the translation of the edge computing white paper with RST?
>>> 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.
>>> I would like to move this forward and am happy to help the setup of a repo if needed.
>>>
>>> Where can we discuss this?
>>> The edge computing group meeting is not listed athttp://eavesdrop.openstack.org/  and I don't know when and where it happens.
>>>
>>> [1]https://amotoki.github.io/edge-computing-whitepaper/
>>>
>>> Thanks,
>>> Akihiro
>>>
>>> 2018年5月29日(火) 23:37 Akihiro Motoki<amotoki at gmail.com>:
>>> 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>:
>>> 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>  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
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs
>>> _______________________________________________
>>> openstack-sigs mailing list
>>> openstack-sigs at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs
>>> _______________________________________________
>>> Edge-computing mailing list
>>> Edge-computing at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
>>
>
> _______________________________________________
> OpenStack-I18n mailing list
> OpenStack-I18n at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-i18n/attachments/20180625/f6bf41cd/attachment-0001.html>