from:"Frank Kloeker"

[openstack-dev] [docs][i18n] Team photos Berlin Summit

2018-11-16 Thread Frank Kloeker


Hello,

I would like to share my photos from the poster ehibition which provided 
I18n for the Summit, some impressions from our sessions, the team photos 
and the afterstack team dinner in Grunewald. Feel free to contribute 
more pictures for people they don't were with us.

Have a save trip home and hopefully you enjoyed the Berlin Summit.

Frank

link: https://photos.app.goo.gl/i9Wnq7QyukpG29VF6


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack-I18n] [docs][i18n] Team dinner Berlin Summit

2018-11-15 Thread Frank Kloeker


Hello again,

if you don't want to participate the Onboarding session we may meet 
around 6 at the registration. I think there is still a possibility to 
make a team picture on the right side near the sponsor wall.


kind regards

Frank

Am 2018-11-14 15:02, schrieb Frank Kloeker:

Hello,

thanks to all participants of the OpenStack Summit in Berlin.
Hopefully you have an event with enough success and fun so far. I
really appreciate that you are here in Berlin.
To round up I would like to have the Docs- and I18n team for a team
dinner on Thursday, after the Onboarding Session. I reserved a table
for 18:30 on Restaurant Scheune
(https://www.google.com/maps/reserve/v/dine/m/DH2FjXOtEXw). We can
start on the CityCube possibly on foot.
I want to skip the I18n Office Hour on Thursday.

kind regards

Frank

menu: http://www.scheune-restaurant.de/

___
OpenStack-I18n mailing list
openstack-i...@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [docs][i18n] Team dinner Berlin Summit

2018-11-14 Thread Frank Kloeker


Hello,

thanks to all participants of the OpenStack Summit in Berlin. Hopefully 
you have an event with enough success and fun so far. I really 
appreciate that you are here in Berlin.
To round up I would like to have the Docs- and I18n team for a team 
dinner on Thursday, after the Onboarding Session. I reserved a table for 
18:30 on Restaurant Scheune 
(https://www.google.com/maps/reserve/v/dine/m/DH2FjXOtEXw). We can start 
on the CityCube possibly on foot.

I want to skip the I18n Office Hour on Thursday.

kind regards

Frank

menu: http://www.scheune-restaurant.de/

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [openstack-community] Sharing upstream contribution mentoring result with Korea user group

2018-10-30 Thread Frank Kloeker


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
commun...@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/community



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [I18n] No Office Hour this week

2018-10-01 Thread Frank Kloeker


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

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [docs] Nominating Ian Y. Choi for openstack-doc-core

2018-09-20 Thread Frank Kloeker


Am 2018-09-19 20:54, schrieb Andreas Jaeger:

On 2018-09-19 20:50, Petr Kovar wrote:

Hi all,

Based on our PTG discussion, I'd like to nominate Ian Y. Choi for
membership in the openstack-doc-core team. I think Ian doesn't need an
introduction, he's been around for a while, recently being deeply 
involved
in infra work to get us robust support for project team docs 
translation and

PDF builds.

Having Ian on the core team will also strengthen our integration with
the i18n community.

Please let the ML know should you have any objections.


The opposite ;), heartly agree with adding him,

Andreas


++

Frank


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [I18n] Stein translation plans and prio

2018-09-16 Thread Frank Kloeker


Hello,

the PTG is just over and now we are at the beginning of the work for 
Stein cycle. First of all let me thank all supporters for the I18n team 
and all individuals who help to present OpenStack in different 
languages. We have made so much progress since the formation of the 
team.


What are the workflows now for the Stein cycle:
1. Project documentation translation
We have now the right Zuul jobs in the flow to pull and push 
documentation from project repos to Zanata and back. At the moment there 
are 3 early-bird projects on the list: Horizon, OpenStack Ansible, and 
OpenStack Helm. Expanding this list will be the main work in the cycle.

2. Whitepaper translation
Early this year we started with translation of Edge Computing 
Whitepaper. After solving issues with publishing translated content we 
have here now also a flow from the origin document through translation 
platform and back. Container whitepaper is the second project in this 
space.

3. Stein Dashboard translation
All translation strings from stable/rocky branch are merged back to 
master and we work ahead on the master branch. There are 22 projects on 
that list.


All plans and prios are linked on the frontpage of translation platform 
https://translate.openstack.org

Keep the stones rolling on the Stein cycle.

kind regards
Frank (PTL I18n)

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [openstack-ansible] Stepping down from OpenStack-Ansible core

2018-08-31 Thread Frank Kloeker


Hey Andy,

I can only underline what Ian says. It was a pleasure to work with you, 
many thanks for your kind support all the time. Keep your ears stiff, 
what we say in Germany. And good luck :)


kind regards
Frank

Am 2018-08-30 20:05, schrieb Ian Y. Choi:

Hello Andy,

Thanks a lot for your work on OpenStack-Ansible team.

It was very happy to collaborate with you as different teams (me: I18n
team) during Ocata and Pike release cycles,
and I think I18n team now has better insight on OpenStack-Ansible
thanks to the help from you and so many kind contributors.


With many thanks,

/Ian

Andy McCrae wrote on 8/31/2018 2:40 AM:
Now that Rocky is all but ready it seems like a good time! Since 
changing roles I've not been able to keep up enough focus on reviews 
and other obligations - so I think it's time to step aside as a core 
reviewer.


I want to say thanks to everybody in the community, I'm really proud 
to see the work we've done and how the OSA team has grown. I've 
learned a tonne from all of you - it's definitely been a great 
experience.


Thanks,
Andy


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [all] Berlin Hackathon: Hacking the Edge

2018-08-27 Thread Frank Kloeker


Hello,

For the weekend before the Berlin Summit we plan an additional
OpenStack community event: "Hacking the Edge" Hackathon.
The idea is to build together a community cloud based on
Edge technology.

We're looking for volunteers:

Developers
Try out the newest software version from your projects like Nova,
Cinder, and Neutron. What's the requirements for Edge and what
makes sense? Install different components on different devices and
connects all of them.

Operators
Operation of Edge Cloud is also a challenge. Changes from 'must be
online' to 'maybe online'. Which measuring methods are available for
monitoring? Where are my backups? Do we need an operation center
also in the Edge?

Architects
General Edge Cloud Architecture. How is the plan for connecting new
devices with different connectivity. Scalable application and
life cycle management.

Bring your own devices like laptop, Raspberry PI, WIFI routers, which
you would connect to the Edge Cloud.

We host the event location and provide infrastructure, maybe together
with a couple of 5G devices, because the venue has one of the first
5G antennas in Germany.

Everybody is welcome to join and have fun. We are only limited
on the event space.  More details are also in the event description.

Don't be afraid to ask me directly, via e-mail or IRC.

kind regards

Frank (eumel8)

Registration: https://openstack-hackathon-berlin.eventbrite.com/
Collected ideas/workpad:
https://etherpad.openstack.org/p/hacking_the_edge_hackathon_berlin

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [I18n] Translation Imports

2018-08-09 Thread Frank Kloeker


Hello,

maybe you missed it, translation import jobs are back today. Please 
merge "Imported Translations from Zanata" as soon as possible so we can 
move fast forward with Rocky translation.
If you have already branched to stable/rocky please aware that we 
releasenotes translation manage only in master branch.
Special thanks to openstack-infra and the zuul team for the fast error 
handling.


kind regards
Frank

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [i18n] Edge and Containers whitepapers ready for translation

2018-08-07 Thread Frank Kloeker

Many thanks, Jimmy! At last I draw your attention to Stackalytics.
Translation metrics for whitepapers not counted there. Maybe you have an
advice for https://review.openstack.org/#/c/588965/

kind regards

Frank

Am 2018-08-06 21:07, schrieb Jimmy McArthur:

A heads up that the Translators are now listed at the bottom of the
page as well, along with the rest of the paper contributors:

https://www.openstack.org/edge-computing/cloud-edge-computing-beyond-the-data-center?lang=ja_JP

Cheers!
Jimmy

Frank Kloeker wrote:

Hi Jimmy,

thanks for announcement. Great stuff! It looks really great and it's
easy to navigate. I think a special thanks goes to Sebastian for
designing the pages. One small remark: have you tried text-align:
justify? I think it would be a little bit more readable, like a
science paper (German word is: Ordnung)
I put the projects again on the frontpage of the translation platform,
so we'll get more translations shortly.

kind regards

Frank

Am 2018-08-02 21:07, schrieb Jimmy McArthur:

The Edge and Containers translations are now live. As new
translations become available, we will add them to the page.

https://www.openstack.org/containers/
https://www.openstack.org/edge-computing/

Note that the Chinese translation has not been added to Zanata at
this

time, so I've left the PDF download up on that page.

Thanks everyone and please let me know if you have questions or
concerns!

Cheers!
Jimmy

Jimmy McArthur wrote:

Frank,

We expect to have these papers up this afternoon. I'll update this
thread when we do.

Thanks!
Jimmy

Frank Kloeker wrote:

Hi Sebastian,

okay, it's translated now. In Edge whitepaper is the problem with
XML-Parsing of the term AT Don't know how to escape this. Maybe
you will see the warning during import too.

kind regards

Frank

Am 2018-07-30 20:09, schrieb Sebastian Marcet:

Hi Frank,
i was double checking pot file and realized that original pot
missed
some parts of the original paper (subsections of the paper)
apologizes

on that
i just re uploaded an updated pot file with missing subsections

regards

On Mon, Jul 30, 2018 at 2:20 PM, Frank Kloeker
wrote:

Hi Jimmy,

from the GUI I'll get this link:

https://translate.openstack.org/rest/file/translation/edge-computing/pot-translation/de/po?docId=cloud-edge-computing-beyond-the-data-center

[1]

paper version are only in container whitepaper:

https://translate.openstack.org/rest/file/translation/leveraging-containers-openstack/paper/de/po?docId=leveraging-containers-and-openstack

[2]

In general there is no group named papers

kind regards

Frank

Am 2018-07-30 17:06, schrieb Jimmy McArthur:
Frank,

We're getting a 404 when looking for the pot file on the Zanata
API:

https://translate.openstack.org/rest/file/translation/papers/papers/de/po?docId=edge-computing

[3]

As a result, we can't pull the po files. Any idea what might be
happening?

Seeing the same thing with both papers...

Thank you,
Jimmy

Frank Kloeker wrote:
Hi Jimmy,

Korean and German version are now done on the new format. Can you
check publishing?

thx

Frank

Am 2018-07-19 16:47, schrieb Jimmy McArthur:
Hi all -

Follow up on the Edge paper specifically:

https://translate.openstack.org/iteration/view/edge-computing/pot-translation/documents?dswid=-3192

[4] This is now available. As I mentioned on IRC this morning, it
should
be VERY close to the PDF. Probably just needs a quick review.

Let me know if I can assist with anything.

Thank you to i18n team for all of your help!!!

Cheers,
Jimmy

Jimmy McArthur wrote:
Ian raises some great points :) I'll try to address below...

Ian Y. Choi wrote:
Hello,

that additional design resource cost.
On the other hand, the source strings of edge computing
whitepaper

which I18n team previously translated do not include HTML markup
tags, since the source strings are based on just text format.
The version that Akihiro put together was based on the Edge PDF,
which we unfortunately didn't have the resources to implement in
the

same format.

the reasons

Re: [openstack-dev] [i18n] Edge and Containers whitepapers ready for translation

2018-08-03 Thread Frank Kloeker

Hi Jimmy,

thanks for announcement. Great stuff! It looks really great and it's
easy to navigate. I think a special thanks goes to Sebastian for
designing the pages. One small remark: have you tried text-align:
justify? I think it would be a little bit more readable, like a science
paper (German word is: Ordnung)
I put the projects again on the frontpage of the translation platform,
so we'll get more translations shortly.

kind regards

Frank

Am 2018-08-02 21:07, schrieb Jimmy McArthur:

The Edge and Containers translations are now live. As new
translations become available, we will add them to the page.

https://www.openstack.org/containers/
https://www.openstack.org/edge-computing/

Note that the Chinese translation has not been added to Zanata at this
time, so I've left the PDF download up on that page.

Thanks everyone and please let me know if you have questions or
concerns!

Cheers!
Jimmy

Jimmy McArthur wrote:

Frank,

We expect to have these papers up this afternoon. I'll update this
thread when we do.

Thanks!
Jimmy

Frank Kloeker wrote:

Hi Sebastian,

okay, it's translated now. In Edge whitepaper is the problem with
XML-Parsing of the term AT Don't know how to escape this. Maybe
you will see the warning during import too.

kind regards

Frank

Am 2018-07-30 20:09, schrieb Sebastian Marcet:

Hi Frank,
i was double checking pot file and realized that original pot missed
some parts of the original paper (subsections of the paper)
apologizes

on that
i just re uploaded an updated pot file with missing subsections

regards

On Mon, Jul 30, 2018 at 2:20 PM, Frank Kloeker
wrote:

Hi Jimmy,

from the GUI I'll get this link:

https://translate.openstack.org/rest/file/translation/edge-computing/pot-translation/de/po?docId=cloud-edge-computing-beyond-the-data-center

[1]

paper version are only in container whitepaper:

https://translate.openstack.org/rest/file/translation/leveraging-containers-openstack/paper/de/po?docId=leveraging-containers-and-openstack

[2]

In general there is no group named papers

kind regards

Frank

Am 2018-07-30 17:06, schrieb Jimmy McArthur:
Frank,

We're getting a 404 when looking for the pot file on the Zanata
API:

https://translate.openstack.org/rest/file/translation/papers/papers/de/po?docId=edge-computing

[3]

As a result, we can't pull the po files. Any idea what might be
happening?

Seeing the same thing with both papers...

Thank you,
Jimmy

Frank Kloeker wrote:
Hi Jimmy,

Korean and German version are now done on the new format. Can you
check publishing?

thx

Frank

Am 2018-07-19 16:47, schrieb Jimmy McArthur:
Hi all -

Follow up on the Edge paper specifically:

https://translate.openstack.org/iteration/view/edge-computing/pot-translation/documents?dswid=-3192

[4] This is now available. As I mentioned on IRC this morning, it
should
be VERY close to the PDF. Probably just needs a quick review.

Let me know if I can assist with anything.

Thank you to i18n team for all of your help!!!

Cheers,
Jimmy

Jimmy McArthur wrote:
Ian raises some great points :) I'll try to address below...

Ian Y. Choi wrote:
Hello,

that additional design resource cost.
On the other hand, the source strings of edge computing whitepaper
which I18n team previously translated do not include HTML markup
tags, since the source strings are based on just text format.
The version that Akihiro put together was based on the Edge PDF,
which we unfortunately didn't have the resources to implement in
the

same format.

I really appreciate Akihiro's work on RST-based support on
publishing translated edge computing whitepapers, since
translators do not have to re-translate all the strings.
I would like to second this. It took a lot of initiative to work on
the RST-based translation. At the moment, it's just not usable for
the reasons mentioned above.
On the other hand, it seems that I18n team needs to investigate on
translating similar strings of HTML-based edge computing whitepaper
source strings, which would discourage translators.
Can you expand on this? I'm not entirely clear on why the HTML
based translation is more difficult.

That's my point of view on translating edge computing whitepaper.

For translating container whitepaper, I want to further ask the
followings since *I18n-based tools*
would mean for translators that translators can test

Re: [openstack-dev] [i18n] Edge and Containers whitepapers ready for translation

2018-07-31 Thread Frank Kloeker

Hi Sebastian,

okay, it's translated now. In Edge whitepaper is the problem with
XML-Parsing of the term AT Don't know how to escape this. Maybe you
will see the warning during import too.

kind regards

Frank

Am 2018-07-30 20:09, schrieb Sebastian Marcet:

Hi Frank,
i was double checking pot file and realized that original pot missed
some parts of the original paper (subsections of the paper) apologizes
on that
i just re uploaded an updated pot file with missing subsections

regards

On Mon, Jul 30, 2018 at 2:20 PM, Frank Kloeker wrote:

Hi Jimmy,

from the GUI I'll get this link:

https://translate.openstack.org/rest/file/translation/edge-computing/pot-translation/de/po?docId=cloud-edge-computing-beyond-the-data-center

[1]

paper version are only in container whitepaper:

https://translate.openstack.org/rest/file/translation/leveraging-containers-openstack/paper/de/po?docId=leveraging-containers-and-openstack

[2]

In general there is no group named papers

kind regards

Frank

Am 2018-07-30 17:06, schrieb Jimmy McArthur:
Frank,

We're getting a 404 when looking for the pot file on the Zanata API:

https://translate.openstack.org/rest/file/translation/papers/papers/de/po?docId=edge-computing

[3]

As a result, we can't pull the po files. Any idea what might be
happening?

Seeing the same thing with both papers...

Thank you,
Jimmy

Frank Kloeker wrote:
Hi Jimmy,

Korean and German version are now done on the new format. Can you
check publishing?

thx

Frank

Am 2018-07-19 16:47, schrieb Jimmy McArthur:
Hi all -

Follow up on the Edge paper specifically:

https://translate.openstack.org/iteration/view/edge-computing/pot-translation/documents?dswid=-3192

[4] This is now available. As I mentioned on IRC this morning, it
should
be VERY close to the PDF. Probably just needs a quick review.

Let me know if I can assist with anything.

Thank you to i18n team for all of your help!!!

Cheers,
Jimmy

Jimmy McArthur wrote:
Ian raises some great points :) I'll try to address below...

Ian Y. Choi wrote:
Hello,

When I saw overall translation source strings on container
whitepaper, I would infer that new edge computing whitepaper
source strings would include HTML markup tags.
One of the things I discussed with Ian and Frank in Vancouver is
the expense of recreating PDFs with new translations. It's
prohibitively expensive for the Foundation as it requires design
resources which we just don't have. As a result, we created the
Containers whitepaper in HTML, so that it could be easily updated
w/o working with outside design contractors. I indicated that we
would also be moving the Edge paper to HTML so that we could prevent
that additional design resource cost.
On the other hand, the source strings of edge computing whitepaper
which I18n team previously translated do not include HTML markup
tags, since the source strings are based on just text format.
The version that Akihiro put together was based on the Edge PDF,
which we unfortunately didn't have the resources to implement in the
same format.

That's my point of view on translating edge computing whitepaper.

For translating container whitepaper, I want to further ask the
followings since *I18n-based tools*
would mean for translators that translators can test and publish
translated whitepapers locally:

- How to build translated container whitepaper using original
Silverstripe-based repository?
https://docs.openstack.org/i18n/latest/tools.html [5] describes
well how to build translated artifacts for RST-based OpenStack
repositories
but I could not find the way how to build translated container
whitepaper with translated resources on Zanata.
This is a little tricky. It's possible to set up a local version
of the OpenStack website

(https://github.com/OpenStackweb/openstack-org/blob/master/installation.md

[6]). However, we have to manually ingest the po files as they are
completed and then push them out to production, so that wouldn't do
much to help with your local build. I'm open to suggestions on how
we can make this process easier for the i18n team.

Thank you,
Jimmy

With many thanks,

/Ian

Jimmy McArthur wrote on 7/17/2018 11:01 PM:
Frank,

I'm sorry to hear about the displeasure around the Edge paper. As
mentioned in a prior thread, the RST format that Akihiro worked did
not work with the Zanata process that we have been

Re: [openstack-dev] [i18n] Edge and Containers whitepapers ready for translation

2018-07-30 Thread Frank Kloeker

Hi Jimmy,

from the GUI I'll get this link:
https://translate.openstack.org/rest/file/translation/edge-computing/pot-translation/de/po?docId=cloud-edge-computing-beyond-the-data-center

paper version are only in container whitepaper:

https://translate.openstack.org/rest/file/translation/leveraging-containers-openstack/paper/de/po?docId=leveraging-containers-and-openstack

In general there is no group named papers

kind regards

Frank

Am 2018-07-30 17:06, schrieb Jimmy McArthur:

Frank,

We're getting a 404 when looking for the pot file on the Zanata API:
https://translate.openstack.org/rest/file/translation/papers/papers/de/po?docId=edge-computing

As a result, we can't pull the po files. Any idea what might be
happening?

Seeing the same thing with both papers...

Thank you,
Jimmy

Frank Kloeker wrote:

Hi Jimmy,

Korean and German version are now done on the new format. Can you
check publishing?

thx

Frank

Am 2018-07-19 16:47, schrieb Jimmy McArthur:

Hi all -

Follow up on the Edge paper specifically:
https://translate.openstack.org/iteration/view/edge-computing/pot-translation/documents?dswid=-3192
This is now available. As I mentioned on IRC this morning, it should

be VERY close to the PDF. Probably just needs a quick review.

Let me know if I can assist with anything.

Thank you to i18n team for all of your help!!!

Cheers,
Jimmy

Jimmy McArthur wrote:

Ian raises some great points :) I'll try to address below...

Ian Y. Choi wrote:

Hello,

When I saw overall translation source strings on container
whitepaper, I would infer that new edge computing whitepaper

source strings would include HTML markup tags.
One of the things I discussed with Ian and Frank in Vancouver is the
expense of recreating PDFs with new translations. It's
prohibitively expensive for the Foundation as it requires design
resources which we just don't have. As a result, we created the
Containers whitepaper in HTML, so that it could be easily updated
w/o working with outside design contractors. I indicated that we
would also be moving the Edge paper to HTML so that we could prevent
that additional design resource cost.

On the other hand, the source strings of edge computing whitepaper
which I18n team previously translated do not include HTML markup
tags, since the source strings are based on just text format.
The version that Akihiro put together was based on the Edge PDF,
which we unfortunately didn't have the resources to implement in the
same format.

I really appreciate Akihiro's work on RST-based support on
publishing translated edge computing whitepapers, since

translators do not have to re-translate all the strings.
I would like to second this. It took a lot of initiative to work on
the RST-based translation. At the moment, it's just not usable for
the reasons mentioned above.

On the other hand, it seems that I18n team needs to investigate on
translating similar strings of HTML-based edge computing whitepaper
source strings, which would discourage translators.
Can you expand on this? I'm not entirely clear on why the HTML based
translation is more difficult.

That's my point of view on translating edge computing whitepaper.

For translating container whitepaper, I want to further ask the
followings since *I18n-based tools*
would mean for translators that translators can test and publish
translated whitepapers locally:

- How to build translated container whitepaper using original
Silverstripe-based repository?
https://docs.openstack.org/i18n/latest/tools.html describes well
how to build translated artifacts for RST-based OpenStack
repositories
but I could not find the way how to build translated container
whitepaper with translated resources on Zanata.
This is a little tricky. It's possible to set up a local version of
the OpenStack website
(https://github.com/OpenStackweb/openstack-org/blob/master/installation.md).
However, we have to manually ingest the po files as they are
completed and then push them out to production, so that wouldn't do
much to help with your local build. I'm open to suggestions on how
we can make this process easier for the i18n team.

Thank you,
Jimmy

With many thanks,

/Ian

Jimmy McArthur wrote on 7/17/2018 11:01 PM:

Frank,

I'm sorry to hear about the displeasure around the Edge paper. As
mentioned in a prior thread, the RST format that Akihiro worked
did not work with the Zanata process that we have been using with
our CMS. Additionally, the existing EDGE page is a PDF, so we had
to build a new template to work with the new HTML whitepaper
layout we created for the Containers paper. I outlined this in the
thread " [OpenStack-I18n] [Edge-computing] [Openstack-sigs] Edge
Computing Whitepaper Translation" on 6/25/18 and mentioned we
would be ready with the template around 7/13.

We completed the work on the new whitepaper template and then put
out the pot files on Zanata so we can get the po language f

Re: [openstack-dev] [i18n] Edge and Containers whitepapers ready for translation

2018-07-30 Thread Frank Kloeker

Hi Jimmy,

Korean and German version are now done on the new format. Can you check
publishing?

thx

Frank

Am 2018-07-19 16:47, schrieb Jimmy McArthur:

Hi all -

Follow up on the Edge paper specifically:
https://translate.openstack.org/iteration/view/edge-computing/pot-translation/documents?dswid=-3192

This is now available. As I mentioned on IRC this morning, it should
be VERY close to the PDF. Probably just needs a quick review.

Let me know if I can assist with anything.

Thank you to i18n team for all of your help!!!

Cheers,
Jimmy

Jimmy McArthur wrote:

Ian raises some great points :) I'll try to address below...

Ian Y. Choi wrote:

Hello,

When I saw overall translation source strings on container
whitepaper, I would infer that new edge computing whitepaper

source strings would include HTML markup tags.
One of the things I discussed with Ian and Frank in Vancouver is the
expense of recreating PDFs with new translations. It's prohibitively
expensive for the Foundation as it requires design resources which we
just don't have. As a result, we created the Containers whitepaper in
HTML, so that it could be easily updated w/o working with outside
design contractors. I indicated that we would also be moving the Edge
paper to HTML so that we could prevent that additional design resource
cost.

On the other hand, the source strings of edge computing whitepaper
which I18n team previously translated do not include HTML markup
tags, since the source strings are based on just text format.
The version that Akihiro put together was based on the Edge PDF, which
we unfortunately didn't have the resources to implement in the same
format.

I really appreciate Akihiro's work on RST-based support on publishing
translated edge computing whitepapers, since

That's my point of view on translating edge computing whitepaper.

For translating container whitepaper, I want to further ask the
followings since *I18n-based tools*
would mean for translators that translators can test and publish
translated whitepapers locally:

- How to build translated container whitepaper using original
Silverstripe-based repository?
https://docs.openstack.org/i18n/latest/tools.html describes well
how to build translated artifacts for RST-based OpenStack
repositories
but I could not find the way how to build translated container
whitepaper with translated resources on Zanata.
This is a little tricky. It's possible to set up a local version of
the OpenStack website
(https://github.com/OpenStackweb/openstack-org/blob/master/installation.md).
However, we have to manually ingest the po files as they are
completed and then push them out to production, so that wouldn't do
much to help with your local build. I'm open to suggestions on how we
can make this process easier for the i18n team.

Thank you,
Jimmy

With many thanks,

/Ian

Jimmy McArthur wrote on 7/17/2018 11:01 PM:

Frank,

I'm sorry to hear about the displeasure around the Edge paper. As
mentioned in a prior thread, the RST format that Akihiro worked did
not work with the Zanata process that we have been using with our
CMS. Additionally, the existing EDGE page is a PDF, so we had to
build a new template to work with the new HTML whitepaper layout we
created for the Containers paper. I outlined this in the thread "
[OpenStack-I18n] [Edge-computing] [Openstack-sigs] Edge Computing
Whitepaper Translation" on 6/25/18 and mentioned we would be ready
with the template around 7/13.

We completed the work on the new whitepaper template and then put
out the pot files on Zanata so we can get the po language files
back. If this process is too cumbersome for the translation team,
I'm open to discussion, but right now our entire translation process
is based on the official OpenStack Docs translation process outlined
by the i18n team:
https://docs.openstack.org/i18n/latest/en_GB/tools.html

Again, I realize Akihiro put in some work on his own proposing the
new translation type. If the i18n team is moving to this format
instead, we can work on redoing our process.

Please let me know if I can clarify further.

Thanks,
Jimmy

Frank Kloeker wrote:

Hi Jimmy,

permission was added for you and Sebastian. The Container
Whitepaper is on the Zanata frontpage now. But we removed Edge
Computing whitepaper last week because there is a kind of
displeasure in the team since the results of translation are still
not published besi

[openstack-dev] [I18n] [PTL] [Election] Candidacy for I18n PTL in Stein Cycle

2018-07-25 Thread Frank Kloeker


[posted & mailed] https://review.openstack.org/#/c/585663/

This is my announcement for re-candidacy as I18n PTL in Stein Cycle.

At first a quick review what we've done in the last cycle:

1. Zanata upgrade done. As one of the first community's we're running
Zanata Release 4 in production. A big success and a great user
experiense for all.
2. Translation Check Site done. We were able to win Deutsche Telekom as
sponsor for resources, so now we are able to host our own Translation
Check Site. From my point of view this solves different problems
which we had in the past and now we can check translation strings very
fast on our requirements.
3. Aquire more people to the team. I had great experiences during the
OpenStack Days in Krakow and Budapest. I shared informationen what our
team is doing and how I18n works in the OpenStack Community.
I've got many inspirations and hopefully some new team members :-)

What I mostly like is getting things done. In this cycle we should get
ready project doc translations. We started already with some projects
as a proof of concept and we're still working on it. To get that around,
involve more projects and involve more project team members for
translations is the biggest challenge for me in this cycle.
On the other hand we have Edge Computing whitepaper and Container
whitepaper on our translation plan. With a new technology in use to
publish the translation results very fast on the web page.

Beside that we have the OpenStack Summit Berlin in that cycle. For me
a special event, since I live and work in Berlin. I expect a lot of
collaboration and knowledge sharing with I18n and the OpenStack
Community in general.

That's my plan for Stein, I'm looking forward to your vote.

Frank

Email: eu...@arcor.de
IRC: eumel8
Twitter: eumel_8

OpenStack Profile:
https://www.openstack.org/community/members/profile/45058/frank-kloeker


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [i18n] Edge and Containers whitepapers ready for translation

2018-07-17 Thread Frank Kloeker


Hi Jimmy,

permission was added for you and Sebastian. The Container Whitepaper is 
on the Zanata frontpage now. But we removed Edge Computing whitepaper 
last week because there is a kind of displeasure in the team since the 
results of translation are still not published beside Chinese version. 
It would be nice if we have a commitment from the Foundation that 
results are published in a specific timeframe. This includes your 
requirements until the translation should be available.


thx Frank

Am 2018-07-16 17:26, schrieb Jimmy McArthur:

Sorry, I should have also added... we additionally need permissions so
that we can add the a new version of the pot file to this project:
https://translate.openstack.org/project/view/edge-computing/versions?dswid=-7835

Thanks!
Jimmy



Jimmy McArthur wrote:

Hi all -

We have both of the current whitepapers up and available for 
translation.  Can we promote these on the Zanata homepage?


https://translate.openstack.org/project/view/leveraging-containers-openstack?dswid=5684 
https://translate.openstack.org/iteration/view/edge-computing/master/documents?dswid=5684 
Thanks all!

Jimmy



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [docs][i18n][ptg] PTG infos on Etherpad

2018-07-13 Thread Frank Kloeker


Hello,

the Docs and I18n team will also present during the PTG in Denver. The 
rough plan told us on Monday/Tuesday. As usually we're in the same room 
and will use also the same Etherpad on [1],
which I have shameless copied from the last PTG in Denver, so we have 
all this usefull links for Station 26 already there :)


Please write down your topics and your possible participation. The 
Etherpad from the previous PTG is also linked as a reminder.


many thanks

Frank

[1] https://etherpad.openstack.org/p/docs-i18n-ptg-stein

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [all][ptg] Wiki page for Etherpads

2018-07-13 Thread Frank Kloeker


Hello,

just wondering there was not Wiki page for the upcoming PTG in Denver, 
so I've just created [1] and put in the links what I found here. Please 
check and update if required.


thx

Frank

[1] https://wiki.openstack.org/wiki/PTG/Stein/Etherpads

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [I18n] [Docs] Forum session Vancouver

2018-05-16 Thread Frank Kloeker


Good morning,

just a quick note when packing the suitcase: We have a Docs/I18n Forum 
session on Monday 21th, 13:30, direct after lunch [1]. Take the chance 
to discuss topics about project onboarding with translation or 
documentation, usage of translated documents or tools. Or just come to 
say Hello :-)

Looking forward to see you there!

kind regards

Frank (PTL I18n)


[1] 
https://etherpad.openstack.org/p/docs-i18n-project-onboarding-vancouver


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [I18n] Office Hours, Thursday, 2018/04/26 13:00-14:00 UTC & 2018/05/03 07:00-08:00 UTC

2018-04-23 Thread Frank Kloeker


Hello,

the I18n team wants to change something in collaboration and 
communication with other teams and users. Instead of team meetings we 
offer around the Summit an open communication on Freenode IRC 
#openstack-i18n channel.  Feel free to add your topics on the wiki page 
on [1]. Or better join one of our Office Hours to discuss topis around 
I18n. We are especially interested on:


* Feedback about quality of translation in different languages
* New projects or documents with interests on translation
* New ideas like AI for I18n or new feature requests for Zanata, our 
translation platform


You can meet us in person together with Docs team on the Project 
Onboarding Session during the Vancouver Summit [2].


kind regards

Frank
PTL I18n

[1] https://wiki.openstack.org/wiki/Meetings/I18nTeamMeeting
[2] 
https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21627/docsi18n-project-onboarding



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Poll: S Release Naming

2018-03-14 Thread Frank Kloeker


Hi,

it's critical, I would say. They canceled the registration just today 
[1], but there are still copyrights for name parts like  "S-Bahn 
Halleipzig". I would remove it from the voting list to prevent us from 
trouble. S-Bahn is not really a location in Berlin. If it does, S-Bahn 
is broken ;-)


kind regards

Frank (from Berlin)

[1] 
https://register.dpma.de/DPMAregister/marke/registerHABM?AKZ=007392194


Am 2018-03-14 13:14, schrieb Jeremy Freudberg:

Hi Dmitry,

According to Wikipedia [0] the trademark was removed. The citation [1]
is actually inaccurate; it was not the final ruling. Regardless [2]
seems to reflect the final result which is that the trademark is
cancelled.

Hope this helps.

[0]
https://en.wikipedia.org/wiki/S-train#Germany,_Austria_and_Switzerland
(end of paragraph
[1]
http://juris.bundespatentgericht.de/cgi-bin/rechtsprechung/document.py?Gericht=bpatg=en=Aktuell=23159=1=323=1.pdf
[2]
http://www.eurailpress.de/news/bahnbetrieb/single-view/news/bundesgerichtshof-db-verliert-marke-s-bahn.html

On Wed, Mar 14, 2018 at 7:50 AM, Dmitry Tantsur 
wrote:


Hi,

I suspect that S-Bahn may be a protected (copyright, trademark,
whatever) name. Did you have a chance to check it?

On 03/14/2018 12:58 AM, Paul Belanger wrote:


Greetings all,

It is time again to cast your vote for the naming of the S
Release. This time
is little different as we've decided to use a public polling
option over per
user private URLs for voting. This means, everybody should proceed
to use the
following URL to cast their vote:






https://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_40b95cb2be3fcdf1=8cfdc1f5df5fe4d3

[1]

Because this is a public poll, results will currently be only
viewable by myself
until the poll closes. Once closed, I'll post the URL making the
results
viewable to everybody. This was done to avoid everybody seeing the
results while
the public poll is running.

The poll will officially end on 2018-03-21 23:59:59[1], and
results will be
posted shortly after.

[1]




http://git.openstack.org/cgit/openstack/governance/tree/reference/release-naming.rst

[2]
---

According to the Release Naming Process, this poll is to determine
the
community preferences for the name of the R release of OpenStack.
It is
possible that the top choice is not viable for legal reasons, so
the second or
later community preference could wind up being the name.

Release Name Criteria

Each release name must start with the letter of the ISO basic
Latin alphabet
following the initial letter of the previous release, starting
with the
initial release of "Austin". After "Z", the next name should start
with
"A" again.

The name must be composed only of the 26 characters of the ISO
basic Latin
alphabet. Names which can be transliterated into this character
set are also
acceptable.

The name must refer to the physical or human geography of the
region
encompassing the location of the OpenStack design summit for the
corresponding release. The exact boundaries of the geographic
region under
consideration must be declared before the opening of nominations,
as part of
the initiation of the selection process.

The name must be a single word with a maximum of 10 characters.
Words that
describe the feature should not be included, so "Foo City" or "Foo
Peak"
would both be eligible as "Foo".

Names which do not meet these criteria but otherwise sound really
cool
should be added to a separate section of the wiki page and the TC
may make
an exception for one or more of them to be considered in the
Condorcet poll.
The naming official is responsible for presenting the list of
exceptional
names for consideration to the TC before the poll opens.

Exact Geographic Region

The Geographic Region from where names for the S release will come
is Berlin

Proposed Names

Spree (a river that flows through the Saxony, Brandenburg and
Berlin states of
Germany)

SBahn (The Berlin S-Bahn is a rapid transit system in and around
Berlin)

Spandau (One of the twelve boroughs of Berlin)

Stein (Steinstraße or "Stein Street" in Berlin, can also be
conveniently
abbreviated as )

Steglitz (a locality in the South Western part of the city)

Springer (Berlin is headquarters of Axel Springer publishing
house)

Staaken (a locality within the Spandau borough)

Schoenholz (A zone in the Niederschönhausen district of Berlin)

Shellhaus (A famous office building)

Suedkreuz ("southern cross" - a railway station in
Tempelhof-Schöneberg)

Schiller (A park in the Mitte borough)

Saatwinkel (The name of a super tiny beach, and its surrounding
neighborhood)
(The adjective form, Saatwinkler is also a really cool
bridge but
that form is too long)

Sonne (Sonnenallee is the name of a large street in Berlin
crossing the former
wall, also translates as "sun")

Savigny (Common place in City-West)

Soorstreet (Street in Berlin restrict Charlottenburg)

Solar (Skybar in Berlin)

See (Seestraße or "See Street" in Berlin)

Thanks,
Paul

[openstack-dev] [I18n] Translation plan & priorities for Rocky

2018-03-06 Thread Frank Kloeker


Good morning,

welcome to the Rocky translation release cycle! We merged today on our 
translation platform the stable-queens translations back to master and 
created a new translation dashboard on [1]. There are 19 projects 
identified for translation in Rocky. Please check your own project, if 
it meets your expectations.


Furthermore we have 5 documentation projects still on the list [2]. 
There is a very good progress and only deltas are required to translate.


Additional we have the translation for the Edge Computing Whitepaper 
still online [3]. If you are interested to have this in your language, 
please go ahead. New language version will be accepted.


Early April we want to start with a new User Survey Translation. There 
will be very few changes. Due the upcoming Summit in Berlin we want to 
translate the results of the survey also, at least to German.


Last but not least, as Petr mentioned yesterday evening on 
openstack-dev, our big goal for Rocky is project doc translation. We 
already talked to some project teams in Dublin and we're still in 
preparation before we can start. If you have any questions or hints, let 
me know.


kind regards

Frank
PTL I18n

[1] 
https://translate.openstack.org/version-group/view/Rocky-dashboard-translation

[2] https://translate.openstack.org/version-group/view/doc-resources
[3] 
https://translate.openstack.org/iteration/view/edge-computing/master/documents


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Zanata upgrade to version 4

2018-03-01 Thread Frank Kloeker


Am 2018-03-01 02:00, schrieb Ian Wienand:

On 02/27/2018 09:32 PM, Frank Kloeker wrote:

We will take the chance now to upgrade our translation platform to a
new version.


This has been completed and translate.o.o is now running 4.3.3.  For
any issues reply, or catch any infra-root in #openstack-infra


Good morning from the PTG,

thanks Ian, for the very professional work. This is a great progress to 
got Zanata 4 now online.
As I tested and seen so far there are no issues, only a big count of 
Zanata imports. So please go on and merge the last changes into the 
project repos.


many thanks

Frank


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] Zanata upgrade to version 4

2018-02-27 Thread Frank Kloeker


Hello,

the translation phase for Queens is just over. Many thanks for all that 
work during the cycle and translations in different OpenStack projects.
We will take the chance now to upgrade our translation platform to a new 
version. We don't expect bigger issues because we tested the upgrade 
process anyway on translate-dev.openstack.org. Nevertheless the platform 
could be not available this week. So please note the hint.


kind regards

Frank
(PTL I18n)

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Election] Process Tweaks

2018-02-16 Thread Frank Kloeker


Am 2018-02-15 23:07, schrieb Jeremy Stanley:

On 2018-02-15 22:24:31 +0100 (+0100), Frank Kloeker wrote:
[...]
There is one task with validation openstackid, which validated the 
given
email address. Problem is here, translators using different email 
addresses

for Zanata and it's not possible to validate the user with his name.
Difficult.

[...]

As long as the address you get from Zanata appears in at least one
of the E-mail address fields of the contributor's foundation
individual member profile, then the foundation member lookup API
should be able to locate the correct record for validation. In that
regard, it shouldn't be any more of a problem than it is for code
contributors (where at least one of the addresses for their Gerrit
account needs to appear in at least one of the E-mail address fields
for their member profile).


Hi fungi,

there is no connection between user data in Zanata and user data in the 
openstackid database. This means I can choose as email address whatever 
I want in Zanata. Only my openstackid identifier will be stored there. 
We can advise the user, to configure this email address in the 
foundation member profile. The same is in stackalytics like there: 
https://raw.githubusercontent.com/openstack/stackalytics/master/etc/default_data.json


kind regards

Frank

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Election] Process Tweaks

2018-02-15 Thread Frank Kloeker


Am 2018-02-15 20:09, schrieb Kendall Nelson:

Hello Everyone,

Over the last few elections, with changes to the election cycle (i.e.
the separation of PTL and TC elections not being back to back), the
scripts in place have become somewhat outdated and brittle.

[...]

3. Create separate jobs for both docs build and candidate validation
(and run separate validation functions for TC elections versus PTL
elections).

Please feel free to raise comments, concerns, or better ideas!

The plan is to schedule time at the PTG to start hacking on some of
these items so feedback before then would be fantastic!


Hi Kendall,

we have this in developement for I18n Extra-ATC collection on [1], the 
generated stats on [2].
There is one task with validation openstackid, which validated the given 
email address. Problem is here, translators using different email 
addresses for Zanata and it's not possible to validate the user with his 
name. Difficult.

PTG hacking session would be nice. Wednesday/Thursday afternoon?

kind regards

Frank

[1] https://review.openstack.org/#/c/531600/7/playbooks/generate_atc.yml
[2] 
https://wiki.openstack.org/wiki/I18nTeam/ATC_statistics#Queens_cycle_.282017-07-01_to_2018-01-10.29


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [release] Release countdown for week R-3, February 3 - 9

2018-02-02 Thread Frank Kloeker


Am 2018-02-01 23:42, schrieb Sean McGinnis:

We are already starting on RC week. Time flies when you're having fun.

Development Focus
-

The Release Candidate (RC) deadline is this Thursday, the 8th. Work 
should be
focused on any release-critical bugs and wrapping up and remaining 
feature

work.

General Information
---

All cycle-with-milestones and cycle-with-intermediary projects should 
cut their
stable/queens branch by the end of this week. This branch will track 
the Queens

release.

Once stable/queens has been created, master will will be ready to 
switch to
Rocky development. While master will no longer be frozen, please 
prioritize any

work necessary for completing Queens plans.


[...]
Thx, Sean.
If your project contains translation stuff like Horizon Dashboard 
Plugins, please send me a note when you switch to stable/queens branch, 
so we can prepare translation platform in time with the new branch.


thx
Frank (eumel8)


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [I18n][PTL] PTL nomination for I18n

2018-01-30 Thread Frank Kloeker


This is my announcement for re-candidacy as I18n PTL in Rocky Cycle.

The time from the last cycle passed very fast. I had to manage all the
things that a PTL expects. But we documented everything very well and I
always had the full support of the team. I asked the team and it would
continue to support me, which is why I take the chance again.
This is the point to say thank you to all that we have achieved many
things and we are a great community!

Now it's time to finish things:

1. Zanata upgrade. We are in the middle of the upgrade process. The dev
server is sucessfull upgraded and the new Zanata versions fits all our
requirements to automate things more and more.
Now we are in the hot release phase and when it's over, the live
upgrade can start.

2. Translation check site. A little bit out of scope in Queens release
because of lack of resources. We'll try this again in Rocky.

3. Aquire more people to the team. That will be the main part of my work
as PTL in Rocky. We've won 3 new language teams in the last cycle and
can Openstack serve in Indian, Turkish and Esperanto. There is even more
potential for strengthening existing teams or creating new ones.
For this we have great OpenStack events in Europe this year, at least
the Fall Summit in Berlin. We plan workshops and presentations.

The work of the translation team is also becoming more colorful. We have
project documentation translation in the order books, translation user
survey and white papers for working groups.

We are well prepared, but we also look to the future, for example how
AI-programming can support us in the translation work.

If the plan suits you, I look forward to your vote.

Frank

Email: eu...@arcor.de
IRC: eumel8
Twitter: eumel_8

OpenStack Profile:
https://www.openstack.org/community/members/profile/45058/frank-kloeker

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] Dublin PTG format

2017-11-30 Thread Frank Kloeker


Am 2017-11-27 11:58, schrieb Thierry Carrez:
[...]

We have two options in how we do the split for predetermined topics. We
used to split the week between Mon-Tue (themes) and Wed-Fri (teams). 
The

general idea there was to allow some people only interested in a team
meeting to only attend the second part of the week. However most people
attend all 5 days, and during event feedback some people suggested that
"themes" should be in the mornings and "teams" in the afternoons (and
all Friday).

What would be your preference ? The Mon-Tue/Wed-Fri split means less
room changes, which make it easier on the events team. So all else 
being

equal we'd rather keep it the way it is, but I'm open to changing it if
attendees think it's a good idea.

If you have any other suggestion (that we could implement in the 3
months we have between now and the event) please let me know :)


Hi Thierry,

I'd like the idea about themes and teams. Themes bring the opportunity 
to learn work methods and learn ways of working together, across 
OpenStack project teams and new people who are interested. There are so 
many things to learn from the OpenStack community like documentation, 
code review, code testing, automation, project work. This is the chance 
to prove the 4 O's and to give a platform for it.
Call it Summit 2.0. For 2 days, people who are not members of any 
project team but who are interested in their work or in the workings of 
the OpenStack community.
The other 3 days are really for project team work. I think 2 days would 
be also enough plus 1 day cross-project team work.
I'm not sure if I explained that correctly. I learned so much about 
working methods in the community. I think there may be more people 
proving it and maybe new enthusiastically people are joining in.


These are my thoughts about themes and teams :)

kind regards

Frank (@eumel8)

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [I18n] New Language Team for Esperanto

2017-11-24 Thread Frank Kloeker


Hello,

I kindly want to announce that we have setup a new language on our 
translation platform: Esperanto [1].

Please welcome our newest team member in this context: Georg Hennemann.
He wants to take care of the concerns of this particular language at 
OpenStack. Please support him in his future work and the build of a 
language team.


many thanks

Frank
PTL I18n

[1] https://en.wikipedia.org/wiki/Esperanto


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [I18n] survey about translation of project repo documentation

2017-11-09 Thread Frank Kloeker


Dear all,

hopefully you had a nice Summit and you're safe at home or on the way 
again.
During the week the I18n team was thinking about documentation 
translating in project repos. The doc migration is almost done and now 
it's a good time to start. But there are a lot's of projects and the 
state of things is different. To get an impression how important this 
topic is and which projects are interested We've create a survey to 
figure it out [1]. Please take part in the survey till 2017/11/15 
23:59:59


many thanks

Frank (PTL I18n)

[1] https://www.surveymonkey.de/r/HSD5YTD

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [PTG] [I18n] No IRC meeting this week

2017-09-13 Thread Frank Kloeker


Good morning,

this week we will not hold an IRC meeting for the I18n team. Take the 
opportunity to meet us in real together with the Documentation Team 
today at the PTG in Colorado Ballroom C or ping us in #openstack-i18n or 
#openstack-ptg. Announcements as usualy on [1].


kind regards

Frank (eumel8)
PTL I18n

[1] http://ptg.openstack.org/ptg.html

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [PTG] Video interviews at PTG, now scheduling

2017-09-12 Thread Frank Kloeker


It's on the Atrium Level left from the restaurant.

Am 2017-09-11 17:12, schrieb David Moreau Simard:

Rich,

Where are the interviews taking place ?

David Moreau Simard
Senior Software Engineer | OpenStack RDO

dmsimard = [irc, github, twitter]


On Tue, Aug 22, 2017 at 8:43 AM, Rich Bowen  wrote:

Now that the PTG schedule is up, I'd like to invite you to sign up for
my video interview series. I'll be conducting interviews at the PTG,
with the goal of:

* Telling our users what's new in Pike, and what to expect in Queens
* Put a human face on the upstream developer community
* Show the awesome cooperation and collaboration between projects and
between companies

Sign up at:
https://docs.google.com/spreadsheets/d/1KNHuo9Yb5kbjZAYGQ_PAo-YFndD8QTdaKzaPoct_aaU/edit?usp=sharing

A few tips:

* Talk with your project about who should do the interview, and what 
you

want to highlight.
* Consider having several people sign up to do an interview (no more
than 3, please)
* Consider doing an interview that is cross-project, to talk about 
this

collaboration
* If you know of a user/customer who will be at the PTG who has a cool
use-case, encourage them to sign up
* Please read the notes on the "Planning for your interview" tab of 
the

spreadsheet.

If you'd like to see examples of what I'm going for, I did this on a
much smaller scale in Atlanta, with just Red Hat engineers. Please 
see:

https://www.youtube.com/watch?v=5kT-Sv3rkTw=PLOuHvpVx7kYksG0NFaCaQsSkrUlj3Oq4S

Thanks!

--
Rich Bowen - rbo...@redhat.com
RDO Community Liaison
http://rdoproject.org
@RDOCommunity

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [PTG][I18n][Doc] PTG planning Denver

2017-09-01 Thread Frank Kloeker


Good morning,

it's only a week to the next PTG in Denver. I would like to invite you 
to visit our project etherpad on [1]. We as I18n team are together with 
the Doc team in the same room and we share also our planning on the 
etherpad.
Monday morning we reserved some time to say "Hello" to everybody. Take 
the chance to meet us and let me know if you have some topics for the 
translation team.


kind regards

Frank (eumel8)
PTL I18n

[1] https://etherpad.openstack.org/p/docs-i18n-ptg-queens

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Elections] Candidacy for I18n PTL (Queens)

2017-07-31 Thread Frank Kloeker


Good morning!

Today I would like to announce my candidacy as I18n PTL in Queens cycle.

I've been in the OpenStack Community since 2015, active as a translator 
in the
German team. I participated in my first OpenStack Summit in Tokyo and 
met the
I18n team for the first time at the Design Summit. It was an exciting 
moment to

meet people from all over the world working on the same thing.
It is not just translations, but working with different cultures, views 
and ...

time zones. These are the magical dimensions and challenges.
After Tokyo we had virtual midcycle sprint to develop the translation 
check

site, one of the tools to help translators in their work.
I met more people during Barcelona Summit and sank deeper and deeper 
into the
work of OpenStack and I18n. In Boston we had our own session to show the 
work of
the I18n team. We prepared a workshop also which was not so successful, 
but the

preparation was great and we can repeat it at any time.

At this point I would like to thank Ianychoi for his excellent work in 
the past
as PTL. He is tireless, full of energy, and brought I18n far forward. He 
was for
me in the last weeks a kind of mentor to learn all the things related to 
I18n

and PTL.  Nevertheless, I still need support from the entire team to
successfully manage this task.

What goals have I set for myself for Queens:
1. Completion of the translation check site. I have been involved in 
this

project since 2015 and now it has to be finished :-)
2. Automate all the things. We have some manual work in I18n and our 
tools that

are to automate to make the work easier.
3. Aquire more people to the team. We have great teams that do a lot. 
But we
also get more work through translate new OpenStack projects or the User 
Survey.


I hope I have given a good overview. Contact me directly if you have any
questions or requests. On good cooperation in a new cycle of OpenStack!

kind regards

Frank

Email: eu...@arcor.de
IRC: eumel8
Twitter: eumel_8

OpenStack Profile:
https://www.openstack.org/community/members/profile/45058/frank-kloeker


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack-I18n] [I18n] PTL Candidacy for Pike

2017-01-26 Thread Frank Kloeker

Ian,

we know you as a reliable, ethusiastic and friendly guy of the OpenStack
community. I take the opportunity to thank you for your work at all. And
I'm very happy that you want to continue to work in the project. Go
ahead, you may always have strength and energy for the new challenges.

kind regards

Frank

Am 2017-01-26 17:38, schrieb Ian Y. Choi:

Hello,

I am writing to announce my candidacy for I18n Pike PTL.

To retrospect my activities in Ocata cycle,
my overall feeling is that Ocata cycle is really short.
In fact, I acknowledge that most of the action items I wrote in [1]
are still on-going or have not completed yet.
Nevertheless, the followings are some memorable activities which I have
involved with and also would like to continue during upcoming Pike
cycle:

* Well summarized action items from Ocata Design Summit [2]
* IRC meeting time change accordingly with two bi-weekly schedules
* Publicizing IRC meeting announcement and logs [3]
* On-going effort on Zanata upgrade with Xenial with infra team
* Clearer communication on translation imports and criteria [4, 5]
* Landing page updates for translated documents
* Co-participation in Pike PTG with Documentation team [6]

I am seeing that there are many upstream translations,
and many I18n team members participate with great and kind help.
I really appreciate their contributions and also the help from
especially Infrastructure team, Documentation team, and Zanata
development

team members. I believe that I am able to continue my effort to finish
what I wrote in [1] and make for better I18n.

Please support and encourage me again.

With many thanks,

/Ian

[1]
https://git.openstack.org/cgit/openstack/election/plain/candidates/ocata/I18n/ianychoi.txt
[2] https://etherpad.openstack.org/p/barcelona-i18n-meetup
[3] https://wiki.openstack.org/wiki/I18N/MeetingLogs
[4]
http://docs.openstack.org/developer/i18n/reviewing-translation-import.html

[5] http://docs.openstack.org/developer/i18n/infra.html
[6] https://www.openstack.org/ptg

___
OpenStack-I18n mailing list
openstack-i...@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

37 matches

Mail list logo