From stig.openstack at telfer.org  Tue May  1 20:51:20 2018
From: stig.openstack at telfer.org (Stig Telfer)
Date: Tue, 1 May 2018 21:51:20 +0100
Subject: [Openstack-sigs] [scientific] IRC Meeting: SIG report and upstream
	activities
Message-ID: <1D60EFB5-04F6-433E-B203-CF5CDF17451D@telfer.org>

Hi All - 

We have a Scientific WG meeting in about 10 minutes time in IRC channel #openstack-meeting.  Everyone is welcome.

Today we’d like to talk about upstream activities in various forms.  The full agenda is here: 

https://wiki.openstack.org/wiki/Scientific_SIG#IRC_Meeting_May_1st_2018

Cheers,
Stig



From rleander at redhat.com  Wed May  2 09:40:10 2018
From: rleander at redhat.com (Rain Leander)
Date: Wed, 2 May 2018 11:40:10 +0200
Subject: [Openstack-sigs] [RDO] Rocky Test Days Milestone ONE
In-Reply-To: <CAOrUd9eXop5F+=OZ=UmeScO6NCmY02mApqoxuzyJiGT9sGTDFg@mail.gmail.com>
References: <CAOrUd9eXop5F+=OZ=UmeScO6NCmY02mApqoxuzyJiGT9sGTDFg@mail.gmail.com>
Message-ID: <CAOrUd9e5Fh3QmPQ6F8Zf=L-bN5deyCeGXcV+pKzhTVkn1ZfzLg@mail.gmail.com>

Can't wait to see everyone on #rdo TOMORROW! Thanks, in advance, for your
help!! !

Rain

On Tue, Apr 24, 2018 at 11:54 AM, Rain Leander <rleander at redhat.com> wrote:

> Hello everyone!
>
> Bust out your spoons cause we're about to test the first batch of Rocky
> [road] ice cream!
>
> Or, y'know, the first RDO [0] Rocky OpenStack milestone.
>
> On 03 and 04 May, next week Thursday and Friday, we'll have our first
> milestone test days [1] for Rocky OpenStack. We would love to get as wide
> participation in the RDO Test Days from our global team as possible!
>
> We're looking for developers, users, operators, quality engineers,
> writers, and, yes, YOU. If you're reading this, we want your help!
>
> Let's set new records on the amount of participants! The amount of
> tickets! The amount of feedback and questions and NOTES!
>
> Oh, my.
>
> But, seriously.
>
> I know that everyone has Important Stuff To Do but taking a few hours or a
> day to give things a run through at various points in the RDO cycle will
> benefit everyone. Not only will this help identify issues early in the
> development process, but you can be the one of the first to cut your teeth
> on the latest versions of your favorite deployment methods like TripleO,
> PackStack, and Kolla.
>
> So, please consider taking a break from your normal duties and spending at
> least a few hours with us in #rdo on Freenode.
>
> See you NEXT WEEK!
>
> [0] https://www.rdoproject.org/
> [1] https://www.rdoproject.org/testday/
> --
> K Rain Leander
> OpenStack Community Liaison
> Open Source and Standards Team
> https://www.rdoproject.org/
> http://community.redhat.com
>



-- 
K Rain Leander
OpenStack Community Liaison
Open Source and Standards Team
https://www.rdoproject.org/
http://community.redhat.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-sigs/attachments/20180502/b7891f18/attachment.html>

From rleander at redhat.com  Thu May  3 09:57:02 2018
From: rleander at redhat.com (Rain Leander)
Date: Thu, 3 May 2018 11:57:02 +0200
Subject: [Openstack-sigs] [RDO] Rocky Test Days Milestone ONE
In-Reply-To: <CAOrUd9e5Fh3QmPQ6F8Zf=L-bN5deyCeGXcV+pKzhTVkn1ZfzLg@mail.gmail.com>
References: <CAOrUd9eXop5F+=OZ=UmeScO6NCmY02mApqoxuzyJiGT9sGTDFg@mail.gmail.com>
 <CAOrUd9e5Fh3QmPQ6F8Zf=L-bN5deyCeGXcV+pKzhTVkn1ZfzLg@mail.gmail.com>
Message-ID: <CAOrUd9fgL+v4RMweznh1a7T0hMhhdcpx83+uLaThYheq0R7OuA@mail.gmail.com>

Welcome to RDO Test Days. We've started TODAY and will be testing for two
whole days! There's nowhere to sign up specifically unless you'd like to
play with the kolla environment. [0] If you're going to be testing on your
own stuff, just show up on #rdo and post results / workarounds in the
testing matrix. [1-5]

[0] https://etherpad.openstack.org/p/rdo-rocky-m1-cloud
<https://etherpad.openstack.org/p/rdo-rocky-m1-cloud>
[1] https://www.rdoproject.org/testday/
<https://www.rdoproject.org/testday/>
[2] https://www.rdoproject.org/testday/rocky/milestone1/
<https://www.rdoproject.org/testday/rocky/milestone1/>
[3] https://www.rdoproject.org/testday/tests/
<https://www.rdoproject.org/testday/tests/>
[4] https://www.rdoproject.org/testday/tests/post-installation-tests/
<https://www.rdoproject.org/testday/tests/post-installation-tests/>
[5] https://etherpad.openstack.org/p/rdo-test-days-rocky1-workarounds
<https://etherpad.openstack.org/p/rdo-test-days-rocky1-workarounds>

On Wed, May 2, 2018 at 11:40 AM, Rain Leander <rleander at redhat.com> wrote:

> Can't wait to see everyone on #rdo TOMORROW! Thanks, in advance, for your
> help!! !
>
> Rain
>
> On Tue, Apr 24, 2018 at 11:54 AM, Rain Leander <rleander at redhat.com>
> wrote:
>
>> Hello everyone!
>>
>> Bust out your spoons cause we're about to test the first batch of Rocky
>> [road] ice cream!
>>
>> Or, y'know, the first RDO [0] Rocky OpenStack milestone.
>>
>> On 03 and 04 May, next week Thursday and Friday, we'll have our first
>> milestone test days [1] for Rocky OpenStack. We would love to get as wide
>> participation in the RDO Test Days from our global team as possible!
>>
>> We're looking for developers, users, operators, quality engineers,
>> writers, and, yes, YOU. If you're reading this, we want your help!
>>
>> Let's set new records on the amount of participants! The amount of
>> tickets! The amount of feedback and questions and NOTES!
>>
>> Oh, my.
>>
>> But, seriously.
>>
>> I know that everyone has Important Stuff To Do but taking a few hours or
>> a day to give things a run through at various points in the RDO cycle will
>> benefit everyone. Not only will this help identify issues early in the
>> development process, but you can be the one of the first to cut your teeth
>> on the latest versions of your favorite deployment methods like TripleO,
>> PackStack, and Kolla.
>>
>> So, please consider taking a break from your normal duties and spending
>> at least a few hours with us in #rdo on Freenode.
>>
>> See you NEXT WEEK!
>>
>> [0] https://www.rdoproject.org/
>> [1] https://www.rdoproject.org/testday/
>> --
>> K Rain Leander
>> OpenStack Community Liaison
>> Open Source and Standards Team
>> https://www.rdoproject.org/
>> http://community.redhat.com
>>
>
>
>
> --
> K Rain Leander
> OpenStack Community Liaison
> Open Source and Standards Team
> https://www.rdoproject.org/
> http://community.redhat.com
>



-- 
K Rain Leander
OpenStack Community Liaison
Open Source and Standards Team
https://www.rdoproject.org/
http://community.redhat.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-sigs/attachments/20180503/e743d07f/attachment.html>

From rleander at redhat.com  Fri May  4 07:45:19 2018
From: rleander at redhat.com (Rain Leander)
Date: Fri, 4 May 2018 09:45:19 +0200
Subject: [Openstack-sigs] [RDO] Rocky Test Days Milestone ONE
In-Reply-To: <CAOrUd9fgL+v4RMweznh1a7T0hMhhdcpx83+uLaThYheq0R7OuA@mail.gmail.com>
References: <CAOrUd9eXop5F+=OZ=UmeScO6NCmY02mApqoxuzyJiGT9sGTDFg@mail.gmail.com>
 <CAOrUd9e5Fh3QmPQ6F8Zf=L-bN5deyCeGXcV+pKzhTVkn1ZfzLg@mail.gmail.com>
 <CAOrUd9fgL+v4RMweznh1a7T0hMhhdcpx83+uLaThYheq0R7OuA@mail.gmail.com>
Message-ID: <CAOrUd9d+4NgjowYw26dtEe3KG_7UwNcce0WPxXYZXYSVzKOqzA@mail.gmail.com>

It's the last day of RDO Test Days for Rocky milestone 1. If you've got the
time, bandwidth, and inclination, we'd love your help on Freenode IRC #rdo.
Thanks so much!

~Rain.

On Thu, May 3, 2018 at 11:57 AM, Rain Leander <rleander at redhat.com> wrote:

> Welcome to RDO Test Days. We've started TODAY and will be testing for two
> whole days! There's nowhere to sign up specifically unless you'd like to
> play with the kolla environment. [0] If you're going to be testing on
> your own stuff, just show up on #rdo and post results / workarounds in
> the testing matrix. [1-5]
>
> [0] https://etherpad.openstack.org/p/rdo-rocky-m1-cloud
> <https://etherpad.openstack.org/p/rdo-rocky-m1-cloud>
> [1] https://www.rdoproject.org/testday/
> <https://www.rdoproject.org/testday/>
> [2] https://www.rdoproject.org/testday/rocky/milestone1/
> <https://www.rdoproject.org/testday/rocky/milestone1/>
> [3] https://www.rdoproject.org/testday/tests/
> <https://www.rdoproject.org/testday/tests/>
> [4] https://www.rdoproject.org/testday/tests/post-installation-tests/
> <https://www.rdoproject.org/testday/tests/post-installation-tests/>
> [5] https://etherpad.openstack.org/p/rdo-test-days-rocky1-workarounds
> <https://etherpad.openstack.org/p/rdo-test-days-rocky1-workarounds>
>
> On Wed, May 2, 2018 at 11:40 AM, Rain Leander <rleander at redhat.com> wrote:
>
>> Can't wait to see everyone on #rdo TOMORROW! Thanks, in advance, for your
>> help!! !
>>
>> Rain
>>
>> On Tue, Apr 24, 2018 at 11:54 AM, Rain Leander <rleander at redhat.com>
>> wrote:
>>
>>> Hello everyone!
>>>
>>> Bust out your spoons cause we're about to test the first batch of Rocky
>>> [road] ice cream!
>>>
>>> Or, y'know, the first RDO [0] Rocky OpenStack milestone.
>>>
>>> On 03 and 04 May, next week Thursday and Friday, we'll have our first
>>> milestone test days [1] for Rocky OpenStack. We would love to get as wide
>>> participation in the RDO Test Days from our global team as possible!
>>>
>>> We're looking for developers, users, operators, quality engineers,
>>> writers, and, yes, YOU. If you're reading this, we want your help!
>>>
>>> Let's set new records on the amount of participants! The amount of
>>> tickets! The amount of feedback and questions and NOTES!
>>>
>>> Oh, my.
>>>
>>> But, seriously.
>>>
>>> I know that everyone has Important Stuff To Do but taking a few hours or
>>> a day to give things a run through at various points in the RDO cycle will
>>> benefit everyone. Not only will this help identify issues early in the
>>> development process, but you can be the one of the first to cut your teeth
>>> on the latest versions of your favorite deployment methods like TripleO,
>>> PackStack, and Kolla.
>>>
>>> So, please consider taking a break from your normal duties and spending
>>> at least a few hours with us in #rdo on Freenode.
>>>
>>> See you NEXT WEEK!
>>>
>>> [0] https://www.rdoproject.org/
>>> [1] https://www.rdoproject.org/testday/
>>> --
>>> K Rain Leander
>>> OpenStack Community Liaison
>>> Open Source and Standards Team
>>> https://www.rdoproject.org/
>>> http://community.redhat.com
>>>
>>
>>
>>
>> --
>> K Rain Leander
>> OpenStack Community Liaison
>> Open Source and Standards Team
>> https://www.rdoproject.org/
>> http://community.redhat.com
>>
>
>
>
> --
> K Rain Leander
> OpenStack Community Liaison
> Open Source and Standards Team
> https://www.rdoproject.org/
> http://community.redhat.com
>



-- 
K Rain Leander
OpenStack Community Liaison
Open Source and Standards Team
https://www.rdoproject.org/
http://community.redhat.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-sigs/attachments/20180504/1d62a635/attachment-0001.html>

From martialmichel at datamachines.io  Tue May  8 21:59:24 2018
From: martialmichel at datamachines.io (Martial Michel)
Date: Tue, 08 May 2018 21:59:24 +0000
Subject: [Openstack-sigs] [Scientific] Scientific SIG - IRC meeting Wed 9 at
	1100UTC
Message-ID: <CAAXGpAqqbp0AtSemmOic5O+oVC1297L+u+2vqoAaRD0GbHAVuQ@mail.gmail.com>

Hello,

We will have our IRC meeting in the #openstack-meeting channel at 1100 UTC
May 9th.
Final agenda will be at:
*https://wiki.openstack.org/wiki/Scientific_SIG#IRC_Meeting_May_8st_2018
<https://wiki.openstack.org/wiki/Scientific_SIG#IRC_Meeting_May_8st_2018>*


   1. SIG Cycle Report
      1. https://etherpad.openstack.org/p/scientific-sig-report-queens
   2. Call for Lighting Talks
      1.
      https://etherpad.openstack.org/p/scientific-sig-vancouver2018-lighting-talks
   3. AOB


All are welcome. Looking forward to seeing you there -- Martial
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-sigs/attachments/20180508/a4a22a41/attachment.html>

From lebre.adrien at free.fr  Wed May  9 13:50:45 2018
From: lebre.adrien at free.fr (lebre.adrien at free.fr)
Date: Wed, 9 May 2018 15:50:45 +0200 (CEST)
Subject: [Openstack-sigs] [FEMDC] IRC meeting postponed to next Wednesday
In-Reply-To: <1415866368.99080875.1525873695891.JavaMail.root@zimbra29-e5.priv.proxad.net>
Message-ID: <295656139.99088970.1525873845270.JavaMail.root@zimbra29-e5.priv.proxad.net>

Dear all, 

Neither Paul-Andre nor me can chair the meeting today so we propose to postpone it for one week. 
The agenda will be delivered soon but you can consider that next meeting will focus on the preparation of the Vancouver summit (presentations, F2F meetings...). 

Best regards, 
ad_ri3n_


From kennelson11 at gmail.com  Wed May  9 21:53:15 2018
From: kennelson11 at gmail.com (Kendall Nelson)
Date: Wed, 09 May 2018 21:53:15 +0000
Subject: [Openstack-sigs] [First Contact] [SIG] Forum Etherpads
Message-ID: <CAJ6yrQhVC1W9EOtYO7GoBFU4-f-S4On2dWj923Sbv4wb3QuHdw@mail.gmail.com>

Hello Everyone!

I created etherpads for both of our Forum Sessions that were accepted and
added them to the master list[1]. Please feel free to add discussion topics
to them whether you can attend or not!

First Contact SIG Operator Inclusion:
https://etherpad.openstack.org/p/FC-SIG-Ops-Inclusion

Drafting Requirements for Organisations Contributing to Open
https://etherpad.openstack.org/p/Reqs-for-Organisations-Contributing-to-OpenStack

11 Days till Forum Fun

-Kendall Nelson (diablo_rojo)

[1]https://wiki.openstack.org/wiki/Forum/Vancouver2018#Wednesday.2C_May_23
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-sigs/attachments/20180509/98327168/attachment.html>

From cdent+os at anticdent.org  Thu May 10 16:25:32 2018
From: cdent+os at anticdent.org (Chris Dent)
Date: Thu, 10 May 2018 17:25:32 +0100 (BST)
Subject: [Openstack-sigs] [all][api] POST /api-sig/news
Message-ID: <alpine.OSX.2.21.1805101723540.35024@cdent-a01.vmware.com>


Greetings OpenStack community,

Very quick meeting today, just edleafe and me (cdent). We reviewed last week's action items, both of which were accomplished, both related to the recent GraphQL [8] discussions [7] and preparation for a meeting of the API SIG at Forum [9]. If you're there we hope to see you.

There being no recent changes to pending guidelines nor bugs, we ended the meeting early.

As always if you're interested in helping out, in addition to coming to the meetings, there's also:

* The list of bugs [5] indicates several missing or incomplete guidelines.
* The existing guidelines [2] always need refreshing to account for changes over time. If you find something that's not quite right, submit a patch [6] to fix it.
* Have you done something for which you think guidance would have made things easier but couldn't find any? Submit a patch and help others [6].

# Newly Published Guidelines

None

# API Guidelines Proposed for Freeze

Guidelines that are ready for wider review by the whole community.

None

# Guidelines Currently Under Review [3]

* Update parameter names in microversion sdk spec
   https://review.openstack.org/#/c/557773/

* Add API-schema guide (still being defined)
   https://review.openstack.org/#/c/524467/

* A (shrinking) suite of several documents about doing version and service discovery
   Start at https://review.openstack.org/#/c/459405/

* WIP: microversion architecture archival doc (very early; not yet ready for review)
   https://review.openstack.org/444892

# Highlighting your API impacting issues

If you seek further review and insight from the API SIG about APIs that you are developing or changing, please address your concerns in an email to the OpenStack developer mailing list[1] with the tag "[api]" in the subject. In your email, you should include any relevant reviews, links, and comments to help guide the discussion of the specific challenge you are facing.

To learn more about the API SIG mission and the work we do, see our wiki page [4] and guidelines [2].

Thanks for reading and see you next week!

# References

[1] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[2] http://specs.openstack.org/openstack/api-wg/
[3] https://review.openstack.org/#/q/status:open+project:openstack/api-wg,n,z
[4] https://wiki.openstack.org/wiki/API_SIG
[5] https://bugs.launchpad.net/openstack-api-wg
[6] https://git.openstack.org/cgit/openstack/api-wg
[7] http://lists.openstack.org/pipermail/openstack-dev/2018-May/130219.html
[8] http://graphql.org/
[9] https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21798/api-special-interest-group-session

Meeting Agenda
https://wiki.openstack.org/wiki/Meetings/API-SIG#Agenda
Past Meeting Records
http://eavesdrop.openstack.org/meetings/api_sig/
Open Bugs
https://bugs.launchpad.net/openstack-api-wg

-- 
Chris Dent                       ٩◔̯◔۶           https://anticdent.org/
freenode: cdent                                         tw: @anticdent

From dimitri.pertin at inria.fr  Tue May 15 15:16:22 2018
From: dimitri.pertin at inria.fr (Dimitri Pertin)
Date: Tue, 15 May 2018 17:16:22 +0200
Subject: [Openstack-sigs] [SIG][Edge-computing][openstack-dev][FEMDC] Wed.
 16 May - FEMDC IRC Meeting 15:00 UTC
In-Reply-To: <295656139.99088970.1525873845270.JavaMail.root@zimbra29-e5.priv.proxad.net>
References: <295656139.99088970.1525873845270.JavaMail.root@zimbra29-e5.priv.proxad.net>
Message-ID: <fca565ba-a92a-cc36-af1e-9fe479987c64@inria.fr>

Dear all,

Here is a gentle reminder regarding the FEMDC meeting that was postponed 
from last week to tomorrow: May, the 16th at 15:00 UTC.

As a consequence, the meeting will be held on #edge-computing-irc

This meeting will focus on the preparation of the Vancouver summit 
(presentations, F2F sessions, ...). You can already check and fill this 
pad with you wishes/ideas:
https://etherpad.openstack.org/p/FEMDC_Vancouver

As usually, a draft of the agenda is available at line 550 and you are 
very welcome to add any item:
https://etherpad.openstack.org/p/massively_distributed_ircmeetings_2018

Best regards,

Dimitri



-------- Forwarded Message --------
Subject: [Edge-computing] [FEMDC] IRC meeting postponed to next Wednesday
Date: Wed, 9 May 2018 15:50:45 +0200 (CEST)
From: lebre.adrien at free.fr
To: OpenStack Development Mailing List (not for usage questions) 
<openstack-dev at lists.openstack.org>, openstack-sigs at lists.openstack.org, 
edge-computing at lists.openstack.org

Dear all,
Neither Paul-Andre nor me can chair the meeting today so we propose to 
postpone it for one week. The agenda will be delivered soon but you can 
consider that next meeting will focus on the preparation of the 
Vancouver summit (presentations, F2F meetings...).
Best regards, ad_ri3n_

_______________________________________________
Edge-computing mailing list
Edge-computing at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing


From martialmichel at datamachines.io  Tue May 15 20:15:40 2018
From: martialmichel at datamachines.io (Martial Michel)
Date: Tue, 15 May 2018 16:15:40 -0400
Subject: [Openstack-sigs] [scientific] Scientific SIG - IRC meeting Tue 15th
	at 2100 UTC
Message-ID: <CAAXGpAq1JaSm6EL4E3a6NSaiRaXK8ZwAR8rPbM4j3u+7T1gQ8g@mail.gmail.com>

Hello,

With a late email invitation, we will have our IRC meeting in the
#openstack-meeting
channel at 2100 UTC May 15th.
Final agenda will be at
https://wiki.openstack.org/wiki/Scientific_SIG#IRC_Meeting_May_15th_2018
and to be a repeat of last week in preparation for the summit next week


   1. SIG Cycle Report
      1. https://etherpad.openstack.org/p/scientific-sig-report-queens
   2. Call for Lighting Talks
      1. https://etherpad.openstack.org/p/scientific
      -sig-vancouver2018-lighting-talks
   3. AOB


All are welcome. Looking forward to seeing you there -- Martial
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-sigs/attachments/20180515/9704763e/attachment-0001.html>

From mebert at uvic.ca  Tue May 15 20:58:57 2018
From: mebert at uvic.ca (Marcus Ebert)
Date: Tue, 15 May 2018 13:58:57 -0700 (PDT)
Subject: [Openstack-sigs] [scientific] Scientific SIG - IRC meeting Tue
 15th	at 2100 UTC
In-Reply-To: <CAAXGpAq1JaSm6EL4E3a6NSaiRaXK8ZwAR8rPbM4j3u+7T1gQ8g@mail.gmail.com>
References: <CAAXGpAq1JaSm6EL4E3a6NSaiRaXK8ZwAR8rPbM4j3u+7T1gQ8g@mail.gmail.com>
Message-ID: <alpine.LRH.2.20.1805151325410.21189@heplw65.phys.uvic.ca>

Hello all,

I'm new to the list, so I would like to give a short introduction to what 
we do:
I'm with the HEP Research Computing group at UVic, where we utilize 
(Openstack) clouds for the computing needs of different High Energy 
Physics groups. We don't use just single clouds but work on a system that 
unifies all clouds available to us in a way that it looks like a single 
computing resource for the user jobs, and for that it also handles the 
distribution of needed images to the different clouds. In addition, we are 
working on a system that unifies cloud storage on different clouds into a 
unified storage space with a single endpoint for all user jobs on any 
cloud, no matter on which clouds the data ends up or from where it is 
read. Although we have this storage federation in production now, it is 
still mainly work in progress.

more general information can be found here:
http://heprc.phys.uvic.ca/
https://heprc.blogspot.ca/


Unfortunately, I can't join the IRC meeting today, but will be at the 
summit next week in Vancouver.
Could you please let me know which Scientific SIG activities are planned 
for it and on which days? (from the schedule, it's just Wednesday morning?)


Cheers,
  Marcus



On Tue, 15 May 2018, Martial Michel wrote:

> Hello,
>
> With a late email invitation, we will have our IRC meeting in the
> #openstack-meeting
> channel at 2100 UTC May 15th.
> Final agenda will be at
> https://wiki.openstack.org/wiki/Scientific_SIG#IRC_Meeting_May_15th_2018
> and to be a repeat of last week in preparation for the summit next week
>
>
>   1. SIG Cycle Report
>      1. https://etherpad.openstack.org/p/scientific-sig-report-queens
>   2. Call for Lighting Talks
>      1. https://etherpad.openstack.org/p/scientific
>      -sig-vancouver2018-lighting-talks
>   3. AOB
>
>
> All are welcome. Looking forward to seeing you there -- Martial
>


From lebre.adrien at free.fr  Wed May 16 15:05:30 2018
From: lebre.adrien at free.fr (lebre.adrien at free.fr)
Date: Wed, 16 May 2018 17:05:30 +0200 (CEST)
Subject: [Openstack-sigs] [SIG][Edge-computing][openstack-dev][FEMDC]
 Wed. 16 May - FEMDC IRC Meeting 15:00 UTC
In-Reply-To: <fca565ba-a92a-cc36-af1e-9fe479987c64@inria.fr>
Message-ID: <1910573070.31593773.1526483130740.JavaMail.root@zimbra29-e5.priv.proxad.net>


s/#edge-computing-irc/#edge-computing-group

Sorry for the typo. 
The meeting starts now. 

ad_ri3n_
----- Mail original -----
> De: "Dimitri Pertin" <dimitri.pertin at inria.fr>
> À: openstack-dev at lists.openstack.org
> Cc: openstack-sigs at lists.openstack.org, edge-computing at lists.openstack.org
> Envoyé: Mardi 15 Mai 2018 17:16:22
> Objet: [Openstack-sigs] [SIG][Edge-computing][openstack-dev][FEMDC] Wed. 16 May - FEMDC IRC Meeting 15:00 UTC
> 
> Dear all,
> 
> Here is a gentle reminder regarding the FEMDC meeting that was
> postponed
> from last week to tomorrow: May, the 16th at 15:00 UTC.
> 
> As a consequence, the meeting will be held on #edge-computing-irc
> 
> This meeting will focus on the preparation of the Vancouver summit
> (presentations, F2F sessions, ...). You can already check and fill
> this
> pad with you wishes/ideas:
> https://etherpad.openstack.org/p/FEMDC_Vancouver
> 
> As usually, a draft of the agenda is available at line 550 and you
> are
> very welcome to add any item:
> https://etherpad.openstack.org/p/massively_distributed_ircmeetings_2018
> 
> Best regards,
> 
> Dimitri
> 
> 
> 
> -------- Forwarded Message --------
> Subject: [Edge-computing] [FEMDC] IRC meeting postponed to next
> Wednesday
> Date: Wed, 9 May 2018 15:50:45 +0200 (CEST)
> From: lebre.adrien at free.fr
> To: OpenStack Development Mailing List (not for usage questions)
> <openstack-dev at lists.openstack.org>,
> openstack-sigs at lists.openstack.org,
> edge-computing at lists.openstack.org
> 
> Dear all,
> Neither Paul-Andre nor me can chair the meeting today so we propose
> to
> postpone it for one week. The agenda will be delivered soon but you
> can
> consider that next meeting will focus on the preparation of the
> Vancouver summit (presentations, F2F meetings...).
> Best regards, ad_ri3n_
> 
> _______________________________________________
> Edge-computing mailing list
> Edge-computing at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing
> 
> _______________________________________________
> openstack-sigs mailing list
> openstack-sigs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs
> 


From msm at redhat.com  Thu May 17 16:54:54 2018
From: msm at redhat.com (Michael McCune)
Date: Thu, 17 May 2018 12:54:54 -0400
Subject: [Openstack-sigs] [all][api] POST /api-sig/news
Message-ID: <CADE+ktS4VGPW_cNDGt2AxSOd4KzbP7fubT-oStXBVwE14+3dgA@mail.gmail.com>

Greetings OpenStack community,

Today's meeting was brief, primarily focused on planning for the
summit sessions[7][8] that the SIG will host and facilitate.

The first session[7], will be a Birds of a Feather (BoF) gathering
where the topics will be determined by the attendees. One topic that
will surely make that list is the GraphQL proof of concept for Neutron
that has been discussed on the mailing list[9].

The second session[8], will be a directed discussion addressing
technical debt in the REST APIs of OpenStack.  We're now at the point
where people would like to start removing old code. This session will
give interested parties details about how they can leverage
microversions and the guidelines of the SIG to reduce their debt, drop
old functionality, and improve the consistency of their APIs. It will
also clarify what it means when we bump the minimum microversion for a
service in the future and discuss plans for creating an OpenStack
community goal.

For both sessions, the SIG has aligned itself towards helping
coordinate discussions, clear up misunderstandings, and generally be
helpful in ensuring that all voices are heard and cross-cutting
concerns are addressed. If you are heading to summit, we hope to see
you there!

There being no recent changes to pending guidelines nor to bugs, we
ended the meeting early.

As always if you're interested in helping out, in addition to coming
to the meetings, there's also:

* The list of bugs [5] indicates several missing or incomplete guidelines.
* The existing guidelines [2] always need refreshing to account for
changes over time. If you find something that's not quite right,
submit a patch [6] to fix it.
* Have you done something for which you think guidance would have made
things easier but couldn't find any? Submit a patch and help others
[6].

# Newly Published Guidelines

None

# API Guidelines Proposed for Freeze

Guidelines that are ready for wider review by the whole community.

None

# Guidelines Currently Under Review [3]

* Update parameter names in microversion sdk spec
  https://review.openstack.org/#/c/557773/

* Add API-schema guide (still being defined)
  https://review.openstack.org/#/c/524467/

* A (shrinking) suite of several documents about doing version and
service discovery
  Start at https://review.openstack.org/#/c/459405/

* WIP: microversion architecture archival doc (very early; not yet
ready for review)
  https://review.openstack.org/444892

# Highlighting your API impacting issues

If you seek further review and insight from the API SIG about APIs
that you are developing or changing, please address your concerns in
an email to the OpenStack developer mailing list[1] with the tag
"[api]" in the subject. In your email, you should include any relevant
reviews, links, and comments to help guide the discussion of the
specific challenge you are facing.

To learn more about the API SIG mission and the work we do, see our
wiki page [4] and guidelines [2].

Thanks for reading and see you next week!

# References

[1] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[2] http://specs.openstack.org/openstack/api-wg/
[3] https://review.openstack.org/#/q/status:open+project:openstack/api-wg,n,z
[4] https://wiki.openstack.org/wiki/API_SIG
[5] https://bugs.launchpad.net/openstack-api-wg
[6] https://git.openstack.org/cgit/openstack/api-wg
[7] https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21798/api-special-interest-group-session
[8] https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21881/api-debt-cleanup
[9] http://lists.openstack.org/pipermail/openstack-dev/2018-May/130219.html

Meeting Agenda
https://wiki.openstack.org/wiki/Meetings/API-SIG#Agenda
Past Meeting Records
http://eavesdrop.openstack.org/meetings/api_sig/
Open Bugs
https://bugs.launchpad.net/openstack-api-wg


From gagehugo at gmail.com  Thu May 17 20:11:49 2018
From: gagehugo at gmail.com (Gage Hugo)
Date: Thu, 17 May 2018 15:11:49 -0500
Subject: [Openstack-sigs]  [Security] No meeting May 24th
Message-ID: <CAE4Awf_F2cYfNiiMwH=KcGLYe074WO1NcjSD58OYbALJjW+xkg@mail.gmail.com>

Hello,

Due to members attending the OpenStack summit in Vancouver, we will be
canceling the Security SIG meeting on May 24th.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-sigs/attachments/20180517/fd0bf741/attachment.html>

From ekcs.openstack at gmail.com  Wed May 23 23:39:16 2018
From: ekcs.openstack at gmail.com (Eric K)
Date: Wed, 23 May 2018 16:39:16 -0700
Subject: [Openstack-sigs] [self-healing] BoF in Vancouver tomorrow
Message-ID: <CAOakLUO5za90j+yJqfmo6z5dZduo-6z0hqi8peW3tkCjOKqzfQ@mail.gmail.com>

For everyone interested in self-healing infra, come share your
experience and your ideas with like-minded stackers, including folks
from 10+ projects working together to make OpenStack self-healing a
reality!

Thursday, May 24, 1:50pm-2:30pm
Vancouver Convention Centre West - Level Two - Room 217

https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21830/self-healing-sig-bof

Brainstorming etherpad:
https://etherpad.openstack.org/p/YVR-self-healing-brainstorming


From amotoki at gmail.com  Tue May 29 09:50:23 2018
From: amotoki at gmail.com (Akihiro Motoki)
Date: Tue, 29 May 2018 18:50:23 +0900
Subject: [Openstack-sigs] [OpenStack-I18n] Edge Computing Whitepaper
	Translation
In-Reply-To: <c68e66c8-2057-11ac-afe6-75f872543b45@gmail.com>
References: <fa5a8a2a5ee6c93814ca9a2f65f6043e@arcor.de>
 <CAPoDJhc+9-nNM37KEQutWpo+21s38bQ8O5kR4eWyKBGsK_8_Xg@mail.gmail.com>
 <c68e66c8-2057-11ac-afe6-75f872543b45@gmail.com>
Message-ID: <CALhU9tmq7J+6KCtzoWboxpgevVY3D3ezFcvBDipc3TFMc9XuwA@mail.gmail.com>

Hi folks involved in the edge computing whitepaper and its translations,

During the summit, we requested to publish more translations on the edge
computing whitepaper in several ways.
We now know the publication process currently used takes time to publish
more languages.

While I hope all translations are published via the official way,
considering this, I created RST version of the whitepaper as a trial,
RST version of the edge computing whitepaper is now available at [1] and
translations can be found at [2].
RST contents are based on the published PDF version [3] and translations
are pulled from Zanata.
There are some minor differences between the published contents and Zanata
contents,
so I need a quick dirty conversion like [4].

My effort is to explore a light way to publish translations quickly and I
do not stick to this way,

Thought?

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.

Thanks,
Akihiro

[1] https://github.com/amotoki/edge-computing-whitepaper
[2] https://amotoki.github.io/edge-computing-whitepaper/
[3] https://www.openstack.org/edge-computing/
[4]
https://github.com/amotoki/edge-computing-whitepaper/blob/master/adjust.sed
[4]



2018年3月1日(木) 13:08 Ian Y. Choi <ianyrchoi at gmail.com>:
>
> Now I see in Zanata that there are almost 100% translated resources on
edge-computing
> for Chinese (zh-CN), German, Indonesian, Korean, and Portuguese languages.
>
> Thanks a lot for kind contribution on such translation - I really think
that we are so strong team!
> (For Korean, @ujuc mostly translated and I could translate some string
translations and reviews.)
>
> @eumel8, would you share when we see translated documents like
> :
https://www.openstack.org/assets/edge/OpenStack-EdgeWhitepaper-v3-online.pdf
?
>
>
> With many thanks,
>
> /Ian
>
> SungJin Kang wrote on 2/7/2018 8:54 PM:
>
> OK,
> lol~~
>
> 2018-02-07 1:27 GMT+09:00 Frank Kloeker <eumel at arcor.de>:
>>
>> Hello I18n Team,
>>
>> maybe as you know beside the project teams there are also working groups
in the OpenStack Community. One of them is the Edge Computing Working
Group. This group produced a whitepaper which described the essence of Edge
Computing and want to translate that to spread knowledge and the Edge
Community. I think thats the point where we can help. I uploaded the
document on [1]. If you have some time and spend some efforts in this topic
please go ahead, any language translations are welcome. The completion date
is in 2 weeks.
>>
>> many thanks
>>
>> Frank
>>
>> please note: the document is only available with the document link on
[1]. The link in the language list doesn't work in this Zanata version.
>>
>>
>> [1]
https://translate.openstack.org/iteration/view/edge-computing/master/documents
>>
>>
>> _______________________________________________
>> OpenStack-I18n mailing list
>> OpenStack-I18n at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
>
>
>
>
> _______________________________________________
> OpenStack-I18n mailing list
> OpenStack-I18n at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
>
>
> _______________________________________________
> 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-sigs/attachments/20180529/c060471f/attachment-0001.html>

From fungi at yuggoth.org  Tue May 29 13:50:41 2018
From: fungi at yuggoth.org (Jeremy Stanley)
Date: Tue, 29 May 2018 13:50:41 +0000
Subject: [Openstack-sigs] [OpenStack-I18n] Edge Computing Whitepaper
	Translation
In-Reply-To: <CALhU9tmq7J+6KCtzoWboxpgevVY3D3ezFcvBDipc3TFMc9XuwA@mail.gmail.com>
References: <fa5a8a2a5ee6c93814ca9a2f65f6043e@arcor.de>
 <CAPoDJhc+9-nNM37KEQutWpo+21s38bQ8O5kR4eWyKBGsK_8_Xg@mail.gmail.com>
 <c68e66c8-2057-11ac-afe6-75f872543b45@gmail.com>
 <CALhU9tmq7J+6KCtzoWboxpgevVY3D3ezFcvBDipc3TFMc9XuwA@mail.gmail.com>
Message-ID: <20180529135041.cyjrl3vtpwajhicq@yuggoth.org>

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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-sigs/attachments/20180529/e2b5c100/attachment.sig>

From ildiko.vancsa at gmail.com  Tue May 29 14:18:37 2018
From: ildiko.vancsa at gmail.com (Ildiko Vancsa)
Date: Tue, 29 May 2018 16:18:37 +0200
Subject: [Openstack-sigs] [OpenStack-I18n] Edge Computing Whitepaper
 Translation
In-Reply-To: <20180529135041.cyjrl3vtpwajhicq@yuggoth.org>
References: <fa5a8a2a5ee6c93814ca9a2f65f6043e@arcor.de>
 <CAPoDJhc+9-nNM37KEQutWpo+21s38bQ8O5kR4eWyKBGsK_8_Xg@mail.gmail.com>
 <c68e66c8-2057-11ac-afe6-75f872543b45@gmail.com>
 <CALhU9tmq7J+6KCtzoWboxpgevVY3D3ezFcvBDipc3TFMc9XuwA@mail.gmail.com>
 <20180529135041.cyjrl3vtpwajhicq@yuggoth.org>
Message-ID: <558F16D9-EB0A-421F-8832-B2DE320E5555@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



From amotoki at gmail.com  Tue May 29 14:37:19 2018
From: amotoki at gmail.com (Akihiro Motoki)
Date: Tue, 29 May 2018 23:37:19 +0900
Subject: [Openstack-sigs] [OpenStack-I18n] Edge Computing Whitepaper
	Translation
In-Reply-To: <558F16D9-EB0A-421F-8832-B2DE320E5555@gmail.com>
References: <fa5a8a2a5ee6c93814ca9a2f65f6043e@arcor.de>
 <CAPoDJhc+9-nNM37KEQutWpo+21s38bQ8O5kR4eWyKBGsK_8_Xg@mail.gmail.com>
 <c68e66c8-2057-11ac-afe6-75f872543b45@gmail.com>
 <CALhU9tmq7J+6KCtzoWboxpgevVY3D3ezFcvBDipc3TFMc9XuwA@mail.gmail.com>
 <20180529135041.cyjrl3vtpwajhicq@yuggoth.org>
 <558F16D9-EB0A-421F-8832-B2DE320E5555@gmail.com>
Message-ID: <CALhU9tnRJDFszrCii-L4ZyoBCWHgSMExBBDC8M+=h6_jion6sg@mail.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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-sigs/attachments/20180529/4b7ecc1d/attachment.html>

From ianyrchoi at gmail.com  Tue May 29 15:42:34 2018
From: ianyrchoi at gmail.com (Ian Y. Choi)
Date: Wed, 30 May 2018 00:42:34 +0900
Subject: [Openstack-sigs] [OpenStack-I18n] Edge Computing Whitepaper
 Translation
In-Reply-To: <CALhU9tnRJDFszrCii-L4ZyoBCWHgSMExBBDC8M+=h6_jion6sg@mail.gmail.com>
References: <fa5a8a2a5ee6c93814ca9a2f65f6043e@arcor.de>
 <CAPoDJhc+9-nNM37KEQutWpo+21s38bQ8O5kR4eWyKBGsK_8_Xg@mail.gmail.com>
 <c68e66c8-2057-11ac-afe6-75f872543b45@gmail.com>
 <CALhU9tmq7J+6KCtzoWboxpgevVY3D3ezFcvBDipc3TFMc9XuwA@mail.gmail.com>
 <20180529135041.cyjrl3vtpwajhicq@yuggoth.org>
 <558F16D9-EB0A-421F-8832-B2DE320E5555@gmail.com>
 <CALhU9tnRJDFszrCii-L4ZyoBCWHgSMExBBDC8M+=h6_jion6sg@mail.gmail.com>
Message-ID: <4419cb40-5784-9334-093c-2e68e316d46d@gmail.com>

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 
format.
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,

/Ian


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




From stig.openstack at telfer.org  Tue May 29 20:46:57 2018
From: stig.openstack at telfer.org (Stig Telfer)
Date: Tue, 29 May 2018 22:46:57 +0200
Subject: [Openstack-sigs] [scientific] IRC meeting at 2100 UTC: Vancouver
	round-up
Message-ID: <236433A7-F10B-4A29-BA14-A256B36FE359@telfer.org>

Hello all - 

We have a Scientific SIG IRC meeting starting shortly in channel #openstack-meeting.  Everyone is welcome.

The agenda today is available here:

https://wiki.openstack.org/wiki/Scientific_SIG#IRC_Meeting_May_29th_2018 <https://wiki.openstack.org/wiki/Scientific_SIG#IRC_Meeting_May_29th_2018>

We’d like to catch up from the Vancouver summit, discuss events at the forum and hear everyone’s recommendations on talks to catch up on.

Cheers,
Stig

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-sigs/attachments/20180529/15697f32/attachment.html>

From amotoki at gmail.com  Tue May 29 23:17:39 2018
From: amotoki at gmail.com (Akihiro Motoki)
Date: Wed, 30 May 2018 08:17:39 +0900
Subject: [Openstack-sigs] [OpenStack-I18n] Edge Computing Whitepaper
	Translation
In-Reply-To: <4419cb40-5784-9334-093c-2e68e316d46d@gmail.com>
References: <fa5a8a2a5ee6c93814ca9a2f65f6043e@arcor.de>
 <CAPoDJhc+9-nNM37KEQutWpo+21s38bQ8O5kR4eWyKBGsK_8_Xg@mail.gmail.com>
 <c68e66c8-2057-11ac-afe6-75f872543b45@gmail.com>
 <CALhU9tmq7J+6KCtzoWboxpgevVY3D3ezFcvBDipc3TFMc9XuwA@mail.gmail.com>
 <20180529135041.cyjrl3vtpwajhicq@yuggoth.org>
 <558F16D9-EB0A-421F-8832-B2DE320E5555@gmail.com>
 <CALhU9tnRJDFszrCii-L4ZyoBCWHgSMExBBDC8M+=h6_jion6sg@mail.gmail.com>
 <4419cb40-5784-9334-093c-2e68e316d46d@gmail.com>
Message-ID: <CALhU9tnH-HQe0CteC0JwcZFzabfFwpROZCobU6pkHuCiNd_PDA@mail.gmail.com>

Hi Ian,

Thanks for more considerations.

2018年5月30日(水) 0:42 Ian Y. Choi <ianyrchoi at gmail.com>:

> 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
> format.
> 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.
>

RST can start from simpler cases and potentially supports more complicated
cases.
I personally prefer to using RST-based documents everywhere.


>
> 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?
>

Setting up the initial repo and converting the original text into RST
format was really simple.
It tooks only less than our hour.

In this case, I took extra two or three hous to cover the following, but I
don't think it always happens.
- to adjust Japanese translation to cover differences between the published
PDF version
  and the text uploaded to Zanata
- to automate the above differences for other languages


>
> - @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?
>

I don't mind using different licenses even if they don't block community
collaborations.
We have a number of documentations (TC governed project documents, SIG
documents, .....),
so it would be nice if we select licenses consistently.


>
> - 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/
> ).
>

Using openstackdocstheme would be nice when it is published in openstack.org
.
openstackdocstheme is intended to use for OpenStack *official* projects,
so I just didn't use it as an initial effort.

If we continue to use another variants of CC and openstackdocstheme,
we can update openstackdocstheme to support more CC licensees.

Thanks,
Akihiro


>
>
> With many thanks,
>
> /Ian
>
>
> 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
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-sigs/attachments/20180530/c5100c7b/attachment.html>

From kennelson11 at gmail.com  Wed May 30 04:51:19 2018
From: kennelson11 at gmail.com (Kendall Nelson)
Date: Tue, 29 May 2018 21:51:19 -0700
Subject: [Openstack-sigs] [First Contact] Meeting Cancelled
Message-ID: <CAJ6yrQji8U7wLMJYfoEQAPfXWcP3tXtVS4kqG+C41SnULcLMPw@mail.gmail.com>

Hello :)

Still recovering and catching up from the Summit last week so I think we
can cancel this week's meeting and pick up again next week.

- Kendall (diablo_rojo)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-sigs/attachments/20180529/c219e0f1/attachment.html>

From eumel at arcor.de  Wed May 30 08:03:03 2018
From: eumel at arcor.de (Frank Kloeker)
Date: Wed, 30 May 2018 10:03:03 +0200
Subject: [Openstack-sigs] [OpenStack-I18n] Edge Computing Whitepaper
 Translation
In-Reply-To: <CALhU9tnH-HQe0CteC0JwcZFzabfFwpROZCobU6pkHuCiNd_PDA@mail.gmail.com>
References: <fa5a8a2a5ee6c93814ca9a2f65f6043e@arcor.de>
 <CAPoDJhc+9-nNM37KEQutWpo+21s38bQ8O5kR4eWyKBGsK_8_Xg@mail.gmail.com>
 <c68e66c8-2057-11ac-afe6-75f872543b45@gmail.com>
 <CALhU9tmq7J+6KCtzoWboxpgevVY3D3ezFcvBDipc3TFMc9XuwA@mail.gmail.com>
 <20180529135041.cyjrl3vtpwajhicq@yuggoth.org>
 <558F16D9-EB0A-421F-8832-B2DE320E5555@gmail.com>
 <CALhU9tnRJDFszrCii-L4ZyoBCWHgSMExBBDC8M+=h6_jion6sg@mail.gmail.com>
 <4419cb40-5784-9334-093c-2e68e316d46d@gmail.com>
 <CALhU9tnH-HQe0CteC0JwcZFzabfFwpROZCobU6pkHuCiNd_PDA@mail.gmail.com>
Message-ID: <d50af07af8a49c0af0f8cc685f0875ee@arcor.de>

Good morning,

thanks to Akihiro and Ian to pushing that topic forward. What about PDF 
creation in Sphinx? Have you some experience to customize things with 
Latex like fonts, color, background picture, front picture? I tried this 
but without sucess.

kind regards

Frank

Am 2018-05-30 01:17, schrieb Akihiro Motoki:
> Hi Ian,
> 
> Thanks for more considerations.
> 
> 2018年5月30日(水) 0:42 Ian Y. Choi <ianyrchoi at gmail.com>:
> 
>> 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
>> format.
>> 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.
> 
> RST can start from simpler cases and potentially supports more
> complicated cases.
> I personally prefer to using RST-based documents everywhere.
> 
>> 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?
> 
> Setting up the initial repo and converting the original text into RST
> format was really simple.
> It tooks only less than our hour.
> 
> In this case, I took extra two or three hous to cover the following,
> but I don't think it always happens.
> - to adjust Japanese translation to cover differences between the
> published PDF version
>   and the text uploaded to Zanata
> - to automate the above differences for other languages
> 
>> - @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?
> 
> I don't mind using different licenses even if they don't block
> community collaborations.
> 
> We have a number of documentations (TC governed project documents, SIG
> documents, .....),
> so it would be nice if we select licenses consistently.
> 
>> - 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/ ).
> 
> Using openstackdocstheme would be nice when it is published in
> openstack.org [1].
> openstackdocstheme is intended to use for OpenStack *official*
> projects,
> 
> so I just didn't use it as an initial effort.
> 
> If we continue to use another variants of CC and openstackdocstheme,
> we can update openstackdocstheme to support more CC licensees.
> 
> Thanks,
> Akihiro
> 
>> With many thanks,
>> 
>> /Ian
>> 
>> 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
> 
> 
> Links:
> ------
> [1] http://openstack.org
> _______________________________________________
> openstack-sigs mailing list
> openstack-sigs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs



From ildiko.vancsa at gmail.com  Wed May 30 08:12:24 2018
From: ildiko.vancsa at gmail.com (Ildiko Vancsa)
Date: Wed, 30 May 2018 10:12:24 +0200
Subject: [Openstack-sigs] [OpenStack-I18n] Edge Computing Whitepaper
 Translation
In-Reply-To: <d50af07af8a49c0af0f8cc685f0875ee@arcor.de>
References: <fa5a8a2a5ee6c93814ca9a2f65f6043e@arcor.de>
 <CAPoDJhc+9-nNM37KEQutWpo+21s38bQ8O5kR4eWyKBGsK_8_Xg@mail.gmail.com>
 <c68e66c8-2057-11ac-afe6-75f872543b45@gmail.com>
 <CALhU9tmq7J+6KCtzoWboxpgevVY3D3ezFcvBDipc3TFMc9XuwA@mail.gmail.com>
 <20180529135041.cyjrl3vtpwajhicq@yuggoth.org>
 <558F16D9-EB0A-421F-8832-B2DE320E5555@gmail.com>
 <CALhU9tnRJDFszrCii-L4ZyoBCWHgSMExBBDC8M+=h6_jion6sg@mail.gmail.com>
 <4419cb40-5784-9334-093c-2e68e316d46d@gmail.com>
 <CALhU9tnH-HQe0CteC0JwcZFzabfFwpROZCobU6pkHuCiNd_PDA@mail.gmail.com>
 <d50af07af8a49c0af0f8cc685f0875ee@arcor.de>
Message-ID: <2448405B-AC8A-4240-B607-C4AD07EF061E@gmail.com>

Hi Frank,

As for white papers we decided to move forward with HTML-based publishing and will provide .po files for translation for the Edge paper and future white papers as well.

When we explored the PDF generation options we came to the conclusion that automating that would probably not worth the effort considering the adjustments to make to ensure that the paragraph endings, diagram placements, highlights, etc. are all in place following the high standards we set with our papers we’ve published so far. With all that said, I’m not against trying it, just would like to put the emphasis and priority on the online versions to make sure we get progress.

Thanks and Best Regards,
Ildikó


> On 2018. May 30., at 10:03, Frank Kloeker <eumel at arcor.de> wrote:
> 
> Good morning,
> 
> thanks to Akihiro and Ian to pushing that topic forward. What about PDF creation in Sphinx? Have you some experience to customize things with Latex like fonts, color, background picture, front picture? I tried this but without sucess.
> 
> kind regards
> 
> Frank
> 
> Am 2018-05-30 01:17, schrieb Akihiro Motoki:
>> Hi Ian,
>> Thanks for more considerations.
>> 2018年5月30日(水) 0:42 Ian Y. Choi <ianyrchoi at gmail.com>:
>>> 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
>>> format.
>>> 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.
>> RST can start from simpler cases and potentially supports more
>> complicated cases.
>> I personally prefer to using RST-based documents everywhere.
>>> 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?
>> Setting up the initial repo and converting the original text into RST
>> format was really simple.
>> It tooks only less than our hour.
>> In this case, I took extra two or three hous to cover the following,
>> but I don't think it always happens.
>> - to adjust Japanese translation to cover differences between the
>> published PDF version
>>  and the text uploaded to Zanata
>> - to automate the above differences for other languages
>>> - @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?
>> I don't mind using different licenses even if they don't block
>> community collaborations.
>> We have a number of documentations (TC governed project documents, SIG
>> documents, .....),
>> so it would be nice if we select licenses consistently.
>>> - 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/ ).
>> Using openstackdocstheme would be nice when it is published in
>> openstack.org [1].
>> openstackdocstheme is intended to use for OpenStack *official*
>> projects,
>> so I just didn't use it as an initial effort.
>> If we continue to use another variants of CC and openstackdocstheme,
>> we can update openstackdocstheme to support more CC licensees.
>> Thanks,
>> Akihiro
>>> With many thanks,
>>> /Ian
>>> 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
>> Links:
>> ------
>> [1] http://openstack.org
>> _______________________________________________
>> 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



From remo at rm.ht  Tue May 29 16:12:15 2018
From: remo at rm.ht (Remo Mattei)
Date: Tue, 29 May 2018 09:12:15 -0700
Subject: [Openstack-sigs] [OpenStack-I18n] Edge Computing Whitepaper
 Translation
In-Reply-To: <4419cb40-5784-9334-093c-2e68e316d46d@gmail.com>
References: <fa5a8a2a5ee6c93814ca9a2f65f6043e@arcor.de>
 <CAPoDJhc+9-nNM37KEQutWpo+21s38bQ8O5kR4eWyKBGsK_8_Xg@mail.gmail.com>
 <c68e66c8-2057-11ac-afe6-75f872543b45@gmail.com>
 <CALhU9tmq7J+6KCtzoWboxpgevVY3D3ezFcvBDipc3TFMc9XuwA@mail.gmail.com>
 <20180529135041.cyjrl3vtpwajhicq@yuggoth.org>
 <558F16D9-EB0A-421F-8832-B2DE320E5555@gmail.com>
 <CALhU9tnRJDFszrCii-L4ZyoBCWHgSMExBBDC8M+=h6_jion6sg@mail.gmail.com>
 <4419cb40-5784-9334-093c-2e68e316d46d@gmail.com>
Message-ID: <ED2A5414-CEAB-4D8A-A34B-417DB37D0C33@rm.ht>

Can I add why are we not considering asciidoc? The conversion to PDF, HTML and ebook will be super easy. 

Just wonder since the RST looks and feels more like markup. 

Thanks 

> On May 29, 2018, at 8:42 AM, Ian Y. Choi <ianyrchoi at gmail.com> wrote:
> 
> 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 format.
> 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/ <https://ianychoi.github.io/edge-computing-whitepaper/>
>         (e.g., https://ianychoi.github.io/edge-computing-whitepaper/ja/ <https://ianychoi.github.io/edge-computing-whitepaper/ja/> ).
> 
> 
> With many thanks,
> 
> /Ian
> 
> 
> 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> <mailto: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>
>>    <mailto: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>
>>    <mailto:openstack-sigs at lists.openstack.org <mailto:openstack-sigs at lists.openstack.org>>
>>    > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs <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>
>>    <mailto:openstack-sigs at lists.openstack.org <mailto:openstack-sigs at lists.openstack.org>>
>>    http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs>
>> 
>> 
>> 
>> _______________________________________________
>> OpenStack-I18n mailing list
>> OpenStack-I18n at lists.openstack.org <mailto:OpenStack-I18n at lists.openstack.org>
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n>
> 
> 
> 
> _______________________________________________
> OpenStack-I18n mailing list
> OpenStack-I18n at lists.openstack.org <mailto:OpenStack-I18n at lists.openstack.org>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-sigs/attachments/20180529/42a482db/attachment-0001.html>

From rm at rm.ht  Wed May 30 14:16:03 2018
From: rm at rm.ht (Remo Mattei)
Date: Wed, 30 May 2018 07:16:03 -0700
Subject: [Openstack-sigs] [OpenStack-I18n] Edge Computing Whitepaper
	Translation
In-Reply-To: <d50af07af8a49c0af0f8cc685f0875ee@arcor.de>
References: <fa5a8a2a5ee6c93814ca9a2f65f6043e@arcor.de>
 <CAPoDJhc+9-nNM37KEQutWpo+21s38bQ8O5kR4eWyKBGsK_8_Xg@mail.gmail.com>
 <c68e66c8-2057-11ac-afe6-75f872543b45@gmail.com>
 <CALhU9tmq7J+6KCtzoWboxpgevVY3D3ezFcvBDipc3TFMc9XuwA@mail.gmail.com>
 <20180529135041.cyjrl3vtpwajhicq@yuggoth.org>
 <558F16D9-EB0A-421F-8832-B2DE320E5555@gmail.com>
 <CALhU9tnRJDFszrCii-L4ZyoBCWHgSMExBBDC8M+=h6_jion6sg@mail.gmail.com>
 <4419cb40-5784-9334-093c-2e68e316d46d@gmail.com>
 <CALhU9tnH-HQe0CteC0JwcZFzabfFwpROZCobU6pkHuCiNd_PDA@mail.gmail.com>
 <d50af07af8a49c0af0f8cc685f0875ee@arcor.de>
Message-ID: <F79A10D5-C657-48EC-8EA6-41498FD61787@rm.ht>

I have done this Frank but asciidoc is 100 times easier to deal than Sphinx. 

Remo

> Il giorno 30 mag 2018, alle ore 01:03, Frank Kloeker <eumel at arcor.de> ha scritto:
> 
> Good morning,
> 
> thanks to Akihiro and Ian to pushing that topic forward. What about PDF creation in Sphinx? Have you some experience to customize things with Latex like fonts, color, background picture, front picture? I tried this but without sucess.
> 
> kind regards
> 
> Frank
> 
> Am 2018-05-30 01:17, schrieb Akihiro Motoki:
>> Hi Ian,
>> Thanks for more considerations.
>> 2018年5月30日(水) 0:42 Ian Y. Choi <ianyrchoi at gmail.com>:
>>> 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
>>> format.
>>> 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.
>> RST can start from simpler cases and potentially supports more
>> complicated cases.
>> I personally prefer to using RST-based documents everywhere.
>>> 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?
>> Setting up the initial repo and converting the original text into RST
>> format was really simple.
>> It tooks only less than our hour.
>> In this case, I took extra two or three hous to cover the following,
>> but I don't think it always happens.
>> - to adjust Japanese translation to cover differences between the
>> published PDF version
>>  and the text uploaded to Zanata
>> - to automate the above differences for other languages
>>> - @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?
>> I don't mind using different licenses even if they don't block
>> community collaborations.
>> We have a number of documentations (TC governed project documents, SIG
>> documents, .....),
>> so it would be nice if we select licenses consistently.
>>> - 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/ ).
>> Using openstackdocstheme would be nice when it is published in
>> openstack.org [1].
>> openstackdocstheme is intended to use for OpenStack *official*
>> projects,
>> so I just didn't use it as an initial effort.
>> If we continue to use another variants of CC and openstackdocstheme,
>> we can update openstackdocstheme to support more CC licensees.
>> Thanks,
>> Akihiro
>>> With many thanks,
>>> /Ian
>>> 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
>> Links:
>> ------
>> [1] http://openstack.org
>> _______________________________________________
>> openstack-sigs mailing list
>> 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



From ianyrchoi at gmail.com  Thu May 31 00:42:36 2018
From: ianyrchoi at gmail.com (Ian Y. Choi)
Date: Thu, 31 May 2018 09:42:36 +0900
Subject: [Openstack-sigs] [OpenStack-I18n] Edge Computing Whitepaper
 Translation
In-Reply-To: <F79A10D5-C657-48EC-8EA6-41498FD61787@rm.ht>
References: <fa5a8a2a5ee6c93814ca9a2f65f6043e@arcor.de>
 <CAPoDJhc+9-nNM37KEQutWpo+21s38bQ8O5kR4eWyKBGsK_8_Xg@mail.gmail.com>
 <c68e66c8-2057-11ac-afe6-75f872543b45@gmail.com>
 <CALhU9tmq7J+6KCtzoWboxpgevVY3D3ezFcvBDipc3TFMc9XuwA@mail.gmail.com>
 <20180529135041.cyjrl3vtpwajhicq@yuggoth.org>
 <558F16D9-EB0A-421F-8832-B2DE320E5555@gmail.com>
 <CALhU9tnRJDFszrCii-L4ZyoBCWHgSMExBBDC8M+=h6_jion6sg@mail.gmail.com>
 <4419cb40-5784-9334-093c-2e68e316d46d@gmail.com>
 <CALhU9tnH-HQe0CteC0JwcZFzabfFwpROZCobU6pkHuCiNd_PDA@mail.gmail.com>
 <d50af07af8a49c0af0f8cc685f0875ee@arcor.de>
 <F79A10D5-C657-48EC-8EA6-41498FD61787@rm.ht>
Message-ID: <c7735564-7249-2a0b-55db-5932c1443ec4@gmail.com>

Hello Remo,

I am not too much familiar with asciidoc, but would you share the 
followings?

- "100 times easier" means overall efficiency or just writing? Is there 
statistics on that?
- Is asciidoc also useful for describing much more contextual 
description such as tables, code blocks, api documents, custom themes, 
and so on?
- Is there some a kind of well-known tool-chains for asciidoc to support 
documentation and building with translated resources (e.g., po files) 
and for publication?

IMO choosing of asciidoc is also dependent to Documentation team I think.

Akihiro and me are saying that current Sphinx tool-chain sets which we 
have experienced and are familiar can help on building
edge computing whitepaper translation support without too much effort.


@Frank,
 > Customizing things with Latex like fonts, color, background picture, 
front picture?

I previously worked PDF files with basic theme stuff: e.g., 
https://docs.openstack.org/ocata/install-guide-obs/InstallGuide.pdf ,
although the stuff is not very easy - it would take some effort.
https://review.openstack.org/#/c/430263/ and 
https://review.openstack.org/#/c/439712/ would be cool reference for you 
I think.

For me, implementing PDF & publishing translated documents for project 
repositories has higher priority to me so I could not help building 
translated PDFs
for edge computing whitepaper with Sphinx stuff right now.


With many thanks,

/Ian

Remo Mattei wrote on 5/30/2018 11:16 PM:
> I have done this Frank but asciidoc is 100 times easier to deal than Sphinx.
>
> Remo
>
>> Il giorno 30 mag 2018, alle ore 01:03, Frank Kloeker <eumel at arcor.de> ha scritto:
>>
>> Good morning,
>>
>> thanks to Akihiro and Ian to pushing that topic forward. What about PDF creation in Sphinx? Have you some experience to customize things with Latex like fonts, color, background picture, front picture? I tried this but without sucess.
>>
>> kind regards
>>
>> Frank
>>
>> Am 2018-05-30 01:17, schrieb Akihiro Motoki:
>>> Hi Ian,
>>> Thanks for more considerations.
>>> 2018年5月30日(水) 0:42 Ian Y. Choi <ianyrchoi at gmail.com>:
>>>> 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
>>>> format.
>>>> 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.
>>> RST can start from simpler cases and potentially supports more
>>> complicated cases.
>>> I personally prefer to using RST-based documents everywhere.
>>>> 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?
>>> Setting up the initial repo and converting the original text into RST
>>> format was really simple.
>>> It tooks only less than our hour.
>>> In this case, I took extra two or three hous to cover the following,
>>> but I don't think it always happens.
>>> - to adjust Japanese translation to cover differences between the
>>> published PDF version
>>>   and the text uploaded to Zanata
>>> - to automate the above differences for other languages
>>>> - @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?
>>> I don't mind using different licenses even if they don't block
>>> community collaborations.
>>> We have a number of documentations (TC governed project documents, SIG
>>> documents, .....),
>>> so it would be nice if we select licenses consistently.
>>>> - 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/ ).
>>> Using openstackdocstheme would be nice when it is published in
>>> openstack.org [1].
>>> openstackdocstheme is intended to use for OpenStack *official*
>>> projects,
>>> so I just didn't use it as an initial effort.
>>> If we continue to use another variants of CC and openstackdocstheme,
>>> we can update openstackdocstheme to support more CC licensees.
>>> Thanks,
>>> Akihiro
>>>> With many thanks,
>>>> /Ian
>>>> 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
>>> Links:
>>> ------
>>> [1] http://openstack.org
>>> _______________________________________________
>>> openstack-sigs mailing list
>>> 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
>
> _______________________________________________
> OpenStack-I18n mailing list
> OpenStack-I18n at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n




From remo at rm.ht  Thu May 31 18:35:14 2018
From: remo at rm.ht (Remo Mattei)
Date: Thu, 31 May 2018 11:35:14 -0700
Subject: [Openstack-sigs] [OpenStack-I18n] Edge Computing Whitepaper
 Translation
In-Reply-To: <c7735564-7249-2a0b-55db-5932c1443ec4@gmail.com>
References: <fa5a8a2a5ee6c93814ca9a2f65f6043e@arcor.de>
 <CAPoDJhc+9-nNM37KEQutWpo+21s38bQ8O5kR4eWyKBGsK_8_Xg@mail.gmail.com>
 <c68e66c8-2057-11ac-afe6-75f872543b45@gmail.com>
 <CALhU9tmq7J+6KCtzoWboxpgevVY3D3ezFcvBDipc3TFMc9XuwA@mail.gmail.com>
 <20180529135041.cyjrl3vtpwajhicq@yuggoth.org>
 <558F16D9-EB0A-421F-8832-B2DE320E5555@gmail.com>
 <CALhU9tnRJDFszrCii-L4ZyoBCWHgSMExBBDC8M+=h6_jion6sg@mail.gmail.com>
 <4419cb40-5784-9334-093c-2e68e316d46d@gmail.com>
 <CALhU9tnH-HQe0CteC0JwcZFzabfFwpROZCobU6pkHuCiNd_PDA@mail.gmail.com>
 <d50af07af8a49c0af0f8cc685f0875ee@arcor.de>
 <F79A10D5-C657-48EC-8EA6-41498FD61787@rm.ht>
 <c7735564-7249-2a0b-55db-5932c1443ec4@gmail.com>
Message-ID: <F415AEF6-12DF-43AA-8C04-9B52A0C7AA4B@rm.ht>

Hi all, 
Here is what I use:

https://asciidoctor.org <https://asciidoctor.org/>


But it does support, tables, code blocks, themes etc.. I am not sure about the API since I have not used it that way. Here is the asciidoc doc about non-English language 

http://asciidoc.org/userguide.html#_using_asciidoc_with_non_english_languages <http://asciidoc.org/userguide.html#_using_asciidoc_with_non_english_languages>

Remo 

> On May 30, 2018, at 5:42 PM, Ian Y. Choi <ianyrchoi at gmail.com> wrote:
> 
> Hello Remo,
> 
> I am not too much familiar with asciidoc, but would you share the followings?
> 
> - "100 times easier" means overall efficiency or just writing? Is there statistics on that?
> - Is asciidoc also useful for describing much more contextual description such as tables, code blocks, api documents, custom themes, and so on?
> - Is there some a kind of well-known tool-chains for asciidoc to support documentation and building with translated resources (e.g., po files) and for publication?
> 
> IMO choosing of asciidoc is also dependent to Documentation team I think.
> 
> Akihiro and me are saying that current Sphinx tool-chain sets which we have experienced and are familiar can help on building
> edge computing whitepaper translation support without too much effort.
> 
> 
> @Frank,
> > Customizing things with Latex like fonts, color, background picture, front picture?
> 
> I previously worked PDF files with basic theme stuff: e.g., https://docs.openstack.org/ocata/install-guide-obs/InstallGuide.pdf <https://docs.openstack.org/ocata/install-guide-obs/InstallGuide.pdf> ,
> although the stuff is not very easy - it would take some effort.
> https://review.openstack.org/#/c/430263/ <https://review.openstack.org/#/c/430263/> and https://review.openstack.org/#/c/439712/ <https://review.openstack.org/#/c/439712/> would be cool reference for you I think.
> 
> For me, implementing PDF & publishing translated documents for project repositories has higher priority to me so I could not help building translated PDFs
> for edge computing whitepaper with Sphinx stuff right now.
> 
> 
> With many thanks,
> 
> /Ian
> 
> Remo Mattei wrote on 5/30/2018 11:16 PM:
>> I have done this Frank but asciidoc is 100 times easier to deal than Sphinx.
>> 
>> Remo
>> 
>>> Il giorno 30 mag 2018, alle ore 01:03, Frank Kloeker <eumel at arcor.de> ha scritto:
>>> 
>>> Good morning,
>>> 
>>> thanks to Akihiro and Ian to pushing that topic forward. What about PDF creation in Sphinx? Have you some experience to customize things with Latex like fonts, color, background picture, front picture? I tried this but without sucess.
>>> 
>>> kind regards
>>> 
>>> Frank
>>> 
>>> Am 2018-05-30 01:17, schrieb Akihiro Motoki:
>>>> Hi Ian,
>>>> Thanks for more considerations.
>>>> 2018年5月30日(水) 0:42 Ian Y. Choi <ianyrchoi at gmail.com>:
>>>>> 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
>>>>> format.
>>>>> 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.
>>>> RST can start from simpler cases and potentially supports more
>>>> complicated cases.
>>>> I personally prefer to using RST-based documents everywhere.
>>>>> 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?
>>>> Setting up the initial repo and converting the original text into RST
>>>> format was really simple.
>>>> It tooks only less than our hour.
>>>> In this case, I took extra two or three hous to cover the following,
>>>> but I don't think it always happens.
>>>> - to adjust Japanese translation to cover differences between the
>>>> published PDF version
>>>>  and the text uploaded to Zanata
>>>> - to automate the above differences for other languages
>>>>> - @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?
>>>> I don't mind using different licenses even if they don't block
>>>> community collaborations.
>>>> We have a number of documentations (TC governed project documents, SIG
>>>> documents, .....),
>>>> so it would be nice if we select licenses consistently.
>>>>> - 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/ ).
>>>> Using openstackdocstheme would be nice when it is published in
>>>> openstack.org [1].
>>>> openstackdocstheme is intended to use for OpenStack *official*
>>>> projects,
>>>> so I just didn't use it as an initial effort.
>>>> If we continue to use another variants of CC and openstackdocstheme,
>>>> we can update openstackdocstheme to support more CC licensees.
>>>> Thanks,
>>>> Akihiro
>>>>> With many thanks,
>>>>> /Ian
>>>>> 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
>>>> Links:
>>>> ------
>>>> [1] http://openstack.org
>>>> _______________________________________________
>>>> openstack-sigs mailing list
>>>> 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
>> 
>> _______________________________________________
>> OpenStack-I18n mailing list
>> OpenStack-I18n at lists.openstack.org <mailto:OpenStack-I18n at lists.openstack.org>
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n>
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-sigs/attachments/20180531/9b5ad364/attachment-0001.html>