From eumel at arcor.de  Tue Oct  2 05:30:47 2018
From: eumel at arcor.de (Frank Kloeker)
Date: Tue, 02 Oct 2018 07:30:47 +0200
Subject: [OpenStack-I18n] [I18n] No Office Hour this week
Message-ID: <1f1e9b3f843d712df48f30e7956334b7@arcor.de>

Hello,

due the national holiday in Germany tomorrow and the long weekend after 
that, there will be no I18n Office Hour this week. Next session will be 
held on 2018/10/11 13:00 UTC [1].

kind regards

Frank

[1] https://wiki.openstack.org/wiki/Meetings/I18nTeamMeeting


From ianyrchoi at gmail.com  Sat Oct 27 17:06:20 2018
From: ianyrchoi at gmail.com (Ian Y. Choi)
Date: Sun, 28 Oct 2018 02:06:20 +0900
Subject: [OpenStack-I18n] [Proposal] I18n Contributor Guide doc folder to
 follow documentation structure
Message-ID: <a85f5a5d-17bb-b7c8-5b73-e65093d21f56@gmail.com>

Hello team,

I18n contributor guide ( https://docs.openstack.org/i18n/latest/ ) is 
based on rst files in
http://git.openstack.org/cgit/openstack/i18n/tree/doc/source folder, but 
the folder structure is different from
other project documents after project document migration [1].

How about moving rst files except index.rst into "contributor" folder 
like [2]
to follow project document structure?


With many thanks,

/Ian

[1] 
http://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migration.html#proposed-change
[2] http://git.openstack.org/cgit/openstack/horizon/tree/doc/source/


From amotoki at gmail.com  Sun Oct 28 10:27:55 2018
From: amotoki at gmail.com (Akihiro Motoki)
Date: Sun, 28 Oct 2018 19:27:55 +0900
Subject: [OpenStack-I18n] [Proposal] I18n Contributor Guide doc folder
 to follow documentation structure
In-Reply-To: <a85f5a5d-17bb-b7c8-5b73-e65093d21f56@gmail.com>
References: <a85f5a5d-17bb-b7c8-5b73-e65093d21f56@gmail.com>
Message-ID: <CALhU9tkC26ikMh_WLCcyTkqhqDqo6yawh3a-imkd3SEf=_4ZDw@mail.gmail.com>

Basically +1.
I would like to raise a question whether it makes sense to move all
contents to contributor/.
Some contents are for the infra and/or i18n admin. They might fit into
admin/.
The i18n repo is different from other repositories, so the categories of
contributor, admin, and user might be different.
At least I believe our current contents should be categorized.

Thought?

2018年10月28日(日) 2:06 Ian Y. Choi <ianyrchoi at gmail.com>:

> Hello team,
>
> I18n contributor guide ( https://docs.openstack.org/i18n/latest/ ) is
> based on rst files in
> http://git.openstack.org/cgit/openstack/i18n/tree/doc/source folder, but
> the folder structure is different from
> other project documents after project document migration [1].
>
> How about moving rst files except index.rst into "contributor" folder
> like [2]
> to follow project document structure?
>
>
> With many thanks,
>
> /Ian
>
> [1]
>
> http://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migration.html#proposed-change
> [2] http://git.openstack.org/cgit/openstack/horizon/tree/doc/source/
>
> _______________________________________________
> OpenStack-I18n mailing list
> OpenStack-I18n at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-i18n/attachments/20181028/ee326ea8/attachment-0001.html>

From amotoki at gmail.com  Sun Oct 28 10:29:23 2018
From: amotoki at gmail.com (Akihiro Motoki)
Date: Sun, 28 Oct 2018 19:29:23 +0900
Subject: [OpenStack-I18n] [Proposal] I18n Contributor Guide doc folder
 to follow documentation structure
In-Reply-To: <CALhU9tkC26ikMh_WLCcyTkqhqDqo6yawh3a-imkd3SEf=_4ZDw@mail.gmail.com>
References: <a85f5a5d-17bb-b7c8-5b73-e65093d21f56@gmail.com>
 <CALhU9tkC26ikMh_WLCcyTkqhqDqo6yawh3a-imkd3SEf=_4ZDw@mail.gmail.com>
Message-ID: <CALhU9tmNH_17o0M_VZFrnR6v38FE_LmhcxdyiH6gztgsVSiUUw@mail.gmail.com>

Another question.
What is the main motivation behind this proposal?
If all contents fit into "contributor", "contributor" directory just will
add another extra path.

2018年10月28日(日) 19:27 Akihiro Motoki <amotoki at gmail.com>:

> Basically +1.
> I would like to raise a question whether it makes sense to move all
> contents to contributor/.
> Some contents are for the infra and/or i18n admin. They might fit into
> admin/.
> The i18n repo is different from other repositories, so the categories of
> contributor, admin, and user might be different.
> At least I believe our current contents should be categorized.
>
> Thought?
>
> 2018年10月28日(日) 2:06 Ian Y. Choi <ianyrchoi at gmail.com>:
>
>> Hello team,
>>
>> I18n contributor guide ( https://docs.openstack.org/i18n/latest/ ) is
>> based on rst files in
>> http://git.openstack.org/cgit/openstack/i18n/tree/doc/source folder, but
>> the folder structure is different from
>> other project documents after project document migration [1].
>>
>> How about moving rst files except index.rst into "contributor" folder
>> like [2]
>> to follow project document structure?
>>
>>
>> With many thanks,
>>
>> /Ian
>>
>> [1]
>>
>> http://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migration.html#proposed-change
>> [2] http://git.openstack.org/cgit/openstack/horizon/tree/doc/source/
>>
>> _______________________________________________
>> OpenStack-I18n mailing list
>> OpenStack-I18n at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-i18n/attachments/20181028/357ed215/attachment.html>

From eumel at arcor.de  Tue Oct 30 07:22:41 2018
From: eumel at arcor.de (Frank Kloeker)
Date: Tue, 30 Oct 2018 08:22:41 +0100
Subject: [OpenStack-I18n] [Proposal] I18n Contributor Guide doc folder
 to follow documentation structure
In-Reply-To: <CALhU9tmNH_17o0M_VZFrnR6v38FE_LmhcxdyiH6gztgsVSiUUw@mail.gmail.com>
References: <a85f5a5d-17bb-b7c8-5b73-e65093d21f56@gmail.com>
 <CALhU9tkC26ikMh_WLCcyTkqhqDqo6yawh3a-imkd3SEf=_4ZDw@mail.gmail.com>
 <CALhU9tmNH_17o0M_VZFrnR6v38FE_LmhcxdyiH6gztgsVSiUUw@mail.gmail.com>
Message-ID: <a6985f973f9e15e84c1beff5fc14cd22@arcor.de>

Yeah, that was also my first reaction. A restructured, more standardized 
I18n guide would be good. But before we have to define for us, who is 
user, who is administrator and who is contributor (in the direction of 
translation or contributor to I18n tools).
And nevertheless before that we have to finish the developement of the 
project doc translation pipelines, that depends mostly on me.

kind regards

Frank

Am 2018-10-28 11:29, schrieb Akihiro Motoki:
> Another question.
> What is the main motivation behind this proposal?
> 
> If all contents fit into "contributor", "contributor" directory just
> will add another extra path.
> 
> 2018年10月28日(日) 19:27 Akihiro Motoki <amotoki at gmail.com>:
> 
>> Basically +1.
>> I would like to raise a question whether it makes sense to move all
>> contents to contributor/.
>> 
>> Some contents are for the infra and/or i18n admin. They might fit
>> into admin/.
>> The i18n repo is different from other repositories, so the
>> categories of contributor, admin, and user might be different.
>> At least I believe our current contents should be categorized.
>> 
>> Thought?
>> 
>> 2018年10月28日(日) 2:06 Ian Y. Choi <ianyrchoi at gmail.com>:
>> 
>>> Hello team,
>>> 
>>> I18n contributor guide ( https://docs.openstack.org/i18n/latest/ )
>>> is
>>> based on rst files in
>>> http://git.openstack.org/cgit/openstack/i18n/tree/doc/source
>>> folder, but
>>> the folder structure is different from
>>> other project documents after project document migration [1].
>>> 
>>> How about moving rst files except index.rst into "contributor"
>>> folder
>>> like [2]
>>> to follow project document structure?
>>> 
>>> With many thanks,
>>> 
>>> /Ian
>>> 
>>> [1]
>>> 
>> 
> http://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migration.html#proposed-change
>>> [2]
>>> http://git.openstack.org/cgit/openstack/horizon/tree/doc/source/
>>> 
>>> _______________________________________________
>>> 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 ianyrchoi at gmail.com  Tue Oct 30 13:37:08 2018
From: ianyrchoi at gmail.com (Ian Y. Choi)
Date: Tue, 30 Oct 2018 22:37:08 +0900
Subject: [OpenStack-I18n] [Proposal] I18n Contributor Guide doc folder
 to follow documentation structure
In-Reply-To: <a6985f973f9e15e84c1beff5fc14cd22@arcor.de>
References: <a85f5a5d-17bb-b7c8-5b73-e65093d21f56@gmail.com>
 <CALhU9tkC26ikMh_WLCcyTkqhqDqo6yawh3a-imkd3SEf=_4ZDw@mail.gmail.com>
 <CALhU9tmNH_17o0M_VZFrnR6v38FE_LmhcxdyiH6gztgsVSiUUw@mail.gmail.com>
 <a6985f973f9e15e84c1beff5fc14cd22@arcor.de>
Message-ID: <fe0a35b3-16ed-3cb7-08cc-4fc13c28ecae@gmail.com>

My main motivation on this proposal is
: I think placing this script: https://review.openstack.org/#/c/613752/ 
to some repo(s) under I18n team governance
would be so great and I want to centralize such a script into 
openstack/i18n repository currently.

I understand that defining each section on the document into admin, 
user, and contributor would give burden
to I18n people, but this might be a good start point to define cores 
with more fine-grained manner
(FYI: 
http://eavesdrop.openstack.org/irclogs/%23openstack-i18n/%23openstack-i18n.2018-10-19.log.html#t2018-10-19T14:06:08 
).


Frank Kloeker wrote on 10/30/2018 4:22 PM:
> Yeah, that was also my first reaction. A restructured, more 
> standardized I18n guide would be good. But before we have to define 
> for us, who is user, who is administrator and who is contributor (in 
> the direction of translation or contributor to I18n tools).
> And nevertheless before that we have to finish the developement of the 
> project doc translation pipelines, that depends mostly on me.

We are the same team - I will try to cooperate with you, and please help 
I18n team PTL, I18n members :)


With many thanks,

/Ian



>
> kind regards
>
> Frank
>
> Am 2018-10-28 11:29, schrieb Akihiro Motoki:
>> Another question.
>> What is the main motivation behind this proposal?
>>
>> If all contents fit into "contributor", "contributor" directory just
>> will add another extra path.
>>
>> 2018年10月28日(日) 19:27 Akihiro Motoki <amotoki at gmail.com>:
>>
>>> Basically +1.
>>> I would like to raise a question whether it makes sense to move all
>>> contents to contributor/.
>>>
>>> Some contents are for the infra and/or i18n admin. They might fit
>>> into admin/.
>>> The i18n repo is different from other repositories, so the
>>> categories of contributor, admin, and user might be different.
>>> At least I believe our current contents should be categorized.
>>>
>>> Thought?
>>>
>>> 2018年10月28日(日) 2:06 Ian Y. Choi <ianyrchoi at gmail.com>:
>>>
>>>> Hello team,
>>>>
>>>> I18n contributor guide ( https://docs.openstack.org/i18n/latest/ )
>>>> is
>>>> based on rst files in
>>>> http://git.openstack.org/cgit/openstack/i18n/tree/doc/source
>>>> folder, but
>>>> the folder structure is different from
>>>> other project documents after project document migration [1].
>>>>
>>>> How about moving rst files except index.rst into "contributor"
>>>> folder
>>>> like [2]
>>>> to follow project document structure?
>>>>
>>>> With many thanks,
>>>>
>>>> /Ian
>>>>
>>>> [1]
>>>>
>>>
>> http://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migration.html#proposed-change 
>>
>>>> [2]
>>>> http://git.openstack.org/cgit/openstack/horizon/tree/doc/source/
>>>>
>>>> _______________________________________________
>>>> 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 ianyrchoi at gmail.com  Tue Oct 30 14:10:42 2018
From: ianyrchoi at gmail.com (Ian Y. Choi)
Date: Tue, 30 Oct 2018 23:10:42 +0900
Subject: [OpenStack-I18n] Sharing upstream contribution mentoring result
	with Korea user group
Message-ID: <09a62e2d-6caf-da1a-71ac-989aeea494ec@gmail.com>

Hello,

I got involved organizing & mentoring Korean people for OpenStack 
upstream contribution for about last two months,
and would like to share with community members.

Total nine mentees had started to learn OpenStack, contributed, and 
finally survived as volunteers for
  1) developing OpenStack mobile app for better mobile user interfaces 
and experiences
     (inspired from https://github.com/stackerz/app which worked on Juno 
release), and
  2) translating OpenStack official project artifacts including documents,
      and Container Whitepaper ( 
https://www.openstack.org/containers/leveraging-containers-and-openstack/ ).

Korea user group organizers (Seongsoo Cho, Taehee Jang, Hocheol Shin, 
Sungjin Kang, and Andrew Yongjoon Kong)
all helped to organize total 8 offline meetups + one mini-hackathon and 
mentored to attendees.

The followings are brief summary:
  - "OpenStack Controller" Android app is available on Play Store
   : 
https://play.google.com/store/apps/details?id=openstack.contributhon.com.openstackcontroller
    (GitHub: https://github.com/kosslab-kr/openstack-controller )

  - Most high-priority projects (although it is not during string freeze 
period) and documents are
    100% translated into Korean: Horizon, OpenStack-Helm, I18n Guide, 
and Container Whitepaper.

  - Total 18,695 words were translated into Korean by four contributors
   (confirmed through Zanata API: 
https://translate.openstack.org/rest/stats/user/[Zanata 
ID]/2018-08-16..2018-10-25 ):

+------------+---------------+-----------------+
| Zanata ID  | Name          | Number of words |
+------------+---------------+-----------------+
| ardentpark | Soonyeul Park | 12517           |
+------------+---------------+-----------------+
| bnitech    | Dongbim Im    | 693             |
+------------+---------------+-----------------+
| csucom     | Sungwook Choi | 4397            |
+------------+---------------+-----------------+
| jaeho93    | Jaeho Cho     | 1088            |
+------------+---------------+-----------------+

  - The list of projects translated into Korean are described as:

+-------------------------------------+-----------------+
| Project                             | Number of words |
+-------------------------------------+-----------------+
| api-site                            | 20              |
+-------------------------------------+-----------------+
| cinder                              | 405             |
+-------------------------------------+-----------------+
| designate-dashboard                 | 4               |
+-------------------------------------+-----------------+
| horizon                             | 3226            |
+-------------------------------------+-----------------+
| i18n                                | 434             |
+-------------------------------------+-----------------+
| ironic                              | 4               |
+-------------------------------------+-----------------+
| Leveraging Containers and OpenStack | 5480            |
+-------------------------------------+-----------------+
| neutron-lbaas-dashboard             | 5               |
+-------------------------------------+-----------------+
| openstack-helm                      | 8835            |
+-------------------------------------+-----------------+
| trove-dashboard                     | 89              |
+-------------------------------------+-----------------+
| zun-ui                              | 193             |
+-------------------------------------+-----------------+

I would like to really appreciate all co-mentors and participants on 
such a big event for promoting OpenStack contribution.
The venue and food were supported by Korea Open Source Software 
Development Center ( https://kosslab.kr/ ).


With many thanks,

/Ian


From eumel at arcor.de  Tue Oct 30 15:27:21 2018
From: eumel at arcor.de (Frank Kloeker)
Date: Tue, 30 Oct 2018 16:27:21 +0100
Subject: [OpenStack-I18n] [openstack-community] Sharing upstream
 contribution mentoring result with Korea user group
In-Reply-To: <09a62e2d-6caf-da1a-71ac-989aeea494ec@gmail.com>
References: <09a62e2d-6caf-da1a-71ac-989aeea494ec@gmail.com>
Message-ID: <4b3bddc23f79663c0d8ea4188f13c3b7@arcor.de>

Hi Ian,

thanks for sharing. What a great user story about community work and 
contributing to OpenStack. I think you did a great job as mentor and 
organizer. I want to keep you with us.

Welcome new contributors any many thanks for translation and 
programming. Hopefully you feel comfortable and have enough energy and 
fun to work further on OpenStack.

kind regards
Frank

Am 2018-10-30 15:10, schrieb Ian Y. Choi:
> Hello,
> 
> I got involved organizing & mentoring Korean people for OpenStack
> upstream contribution for about last two months,
> and would like to share with community members.
> 
> Total nine mentees had started to learn OpenStack, contributed, and
> finally survived as volunteers for
>  1) developing OpenStack mobile app for better mobile user interfaces
> and experiences
>     (inspired from https://github.com/stackerz/app which worked on
> Juno release), and
>  2) translating OpenStack official project artifacts including 
> documents,
>      and Container Whitepaper (
> https://www.openstack.org/containers/leveraging-containers-and-openstack/
> ).
> 
> Korea user group organizers (Seongsoo Cho, Taehee Jang, Hocheol Shin,
> Sungjin Kang, and Andrew Yongjoon Kong)
> all helped to organize total 8 offline meetups + one mini-hackathon
> and mentored to attendees.
> 
> The followings are brief summary:
>  - "OpenStack Controller" Android app is available on Play Store
>   :
> https://play.google.com/store/apps/details?id=openstack.contributhon.com.openstackcontroller
>    (GitHub: https://github.com/kosslab-kr/openstack-controller )
> 
>  - Most high-priority projects (although it is not during string
> freeze period) and documents are
>    100% translated into Korean: Horizon, OpenStack-Helm, I18n Guide,
> and Container Whitepaper.
> 
>  - Total 18,695 words were translated into Korean by four contributors
>   (confirmed through Zanata API:
> https://translate.openstack.org/rest/stats/user/[Zanata
> ID]/2018-08-16..2018-10-25 ):
> 
> +------------+---------------+-----------------+
> | Zanata ID  | Name          | Number of words |
> +------------+---------------+-----------------+
> | ardentpark | Soonyeul Park | 12517           |
> +------------+---------------+-----------------+
> | bnitech    | Dongbim Im    | 693             |
> +------------+---------------+-----------------+
> | csucom     | Sungwook Choi | 4397            |
> +------------+---------------+-----------------+
> | jaeho93    | Jaeho Cho     | 1088            |
> +------------+---------------+-----------------+
> 
>  - The list of projects translated into Korean are described as:
> 
> +-------------------------------------+-----------------+
> | Project                             | Number of words |
> +-------------------------------------+-----------------+
> | api-site                            | 20              |
> +-------------------------------------+-----------------+
> | cinder                              | 405             |
> +-------------------------------------+-----------------+
> | designate-dashboard                 | 4               |
> +-------------------------------------+-----------------+
> | horizon                             | 3226            |
> +-------------------------------------+-----------------+
> | i18n                                | 434             |
> +-------------------------------------+-----------------+
> | ironic                              | 4               |
> +-------------------------------------+-----------------+
> | Leveraging Containers and OpenStack | 5480            |
> +-------------------------------------+-----------------+
> | neutron-lbaas-dashboard             | 5               |
> +-------------------------------------+-----------------+
> | openstack-helm                      | 8835            |
> +-------------------------------------+-----------------+
> | trove-dashboard                     | 89              |
> +-------------------------------------+-----------------+
> | zun-ui                              | 193             |
> +-------------------------------------+-----------------+
> 
> I would like to really appreciate all co-mentors and participants on
> such a big event for promoting OpenStack contribution.
> The venue and food were supported by Korea Open Source Software
> Development Center ( https://kosslab.kr/ ).
> 
> 
> With many thanks,
> 
> /Ian
> 
> _______________________________________________
> Community mailing list
> Community at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/community



From doug at doughellmann.com  Tue Oct 30 17:14:05 2018
From: doug at doughellmann.com (Doug Hellmann)
Date: Tue, 30 Oct 2018 13:14:05 -0400
Subject: [OpenStack-I18n] [openstack-community] Sharing upstream
	contribution mentoring result with Korea user group
In-Reply-To: <09a62e2d-6caf-da1a-71ac-989aeea494ec@gmail.com>
References: <09a62e2d-6caf-da1a-71ac-989aeea494ec@gmail.com>
Message-ID: <m2bm7bz7aa.fsf@doughellmann.com>

"Ian Y. Choi" <ianyrchoi at gmail.com> writes:

> Hello,
>
> I got involved organizing & mentoring Korean people for OpenStack 
> upstream contribution for about last two months,
> and would like to share with community members.
>
> Total nine mentees had started to learn OpenStack, contributed, and 
> finally survived as volunteers for
>   1) developing OpenStack mobile app for better mobile user interfaces 
> and experiences
>      (inspired from https://github.com/stackerz/app which worked on Juno 
> release), and
>   2) translating OpenStack official project artifacts including documents,
>       and Container Whitepaper ( 
> https://www.openstack.org/containers/leveraging-containers-and-openstack/ ).
>
> Korea user group organizers (Seongsoo Cho, Taehee Jang, Hocheol Shin, 
> Sungjin Kang, and Andrew Yongjoon Kong)
> all helped to organize total 8 offline meetups + one mini-hackathon and 
> mentored to attendees.
>
> The followings are brief summary:
>   - "OpenStack Controller" Android app is available on Play Store
>    : 
> https://play.google.com/store/apps/details?id=openstack.contributhon.com.openstackcontroller
>     (GitHub: https://github.com/kosslab-kr/openstack-controller )
>
>   - Most high-priority projects (although it is not during string freeze 
> period) and documents are
>     100% translated into Korean: Horizon, OpenStack-Helm, I18n Guide, 
> and Container Whitepaper.
>
>   - Total 18,695 words were translated into Korean by four contributors
>    (confirmed through Zanata API: 
> https://translate.openstack.org/rest/stats/user/[Zanata 
> ID]/2018-08-16..2018-10-25 ):
>
> +------------+---------------+-----------------+
> | Zanata ID  | Name          | Number of words |
> +------------+---------------+-----------------+
> | ardentpark | Soonyeul Park | 12517           |
> +------------+---------------+-----------------+
> | bnitech    | Dongbim Im    | 693             |
> +------------+---------------+-----------------+
> | csucom     | Sungwook Choi | 4397            |
> +------------+---------------+-----------------+
> | jaeho93    | Jaeho Cho     | 1088            |
> +------------+---------------+-----------------+
>
>   - The list of projects translated into Korean are described as:
>
> +-------------------------------------+-----------------+
> | Project                             | Number of words |
> +-------------------------------------+-----------------+
> | api-site                            | 20              |
> +-------------------------------------+-----------------+
> | cinder                              | 405             |
> +-------------------------------------+-----------------+
> | designate-dashboard                 | 4               |
> +-------------------------------------+-----------------+
> | horizon                             | 3226            |
> +-------------------------------------+-----------------+
> | i18n                                | 434             |
> +-------------------------------------+-----------------+
> | ironic                              | 4               |
> +-------------------------------------+-----------------+
> | Leveraging Containers and OpenStack | 5480            |
> +-------------------------------------+-----------------+
> | neutron-lbaas-dashboard             | 5               |
> +-------------------------------------+-----------------+
> | openstack-helm                      | 8835            |
> +-------------------------------------+-----------------+
> | trove-dashboard                     | 89              |
> +-------------------------------------+-----------------+
> | zun-ui                              | 193             |
> +-------------------------------------+-----------------+
>
> I would like to really appreciate all co-mentors and participants on 
> such a big event for promoting OpenStack contribution.
> The venue and food were supported by Korea Open Source Software 
> Development Center ( https://kosslab.kr/ ).
>
>
> With many thanks,
>
> /Ian
>
> _______________________________________________
> Community mailing list
> Community at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/community

This is an excellent success story, Ian, thank you for sharing it and
for leading the effort.

Doug