From ianyrchoi at gmail.com  Wed Apr  1 13:30:40 2020
From: ianyrchoi at gmail.com (Ian Y. Choi)
Date: Wed, 1 Apr 2020 22:30:40 +0900
Subject: [OpenStack-I18n] [I18n][PTL][election] Nominations were over - no
	PTL candidacy
In-Reply-To: <CAJ6yrQhomxb=yuoZRz=mwODYX5E03H4YtQgt89qqYkOtkJ9qRg@mail.gmail.com>
References: <CAJ6yrQhomxb=yuoZRz=mwODYX5E03H4YtQgt89qqYkOtkJ9qRg@mail.gmail.com>
Message-ID: <6175f5cf-94e6-045d-6291-1effd140d6d8@gmail.com>

Hello,

I would like to share with I18n team members + OpenStackers who are 
interested in I18n that there were no PTL nominations for upcoming 
Victoria release cycle.
I am still serving as an appointed PTL since I cannot run for I18n PTL 
as an election official, but also I honestly tell that my contribution 
has been decreased due to my personal life
(my baby was born ~50 days ago - so busy but really happy as a father).

TC started to discuss on leaderless projects [1], and seems that a 
candidate to become to SIG [2] is being discussed as Docs team 
previously moved to Technical Writing SIG.
I would like to kindly ask opinions from I18n team - unless there are no 
other strong opinions, I will support to become SIG and try to move 
forward for next possible steps.


With many thanks,

/Ian

[1] https://etherpad.openstack.org/p/victoria-leaderless
[2] https://governance.openstack.org/sigs/

-------- Forwarded Message --------
Subject: 	[all][TC][PTL][election] Nominations Close & Campaigning Begins
Date: 	Tue, 31 Mar 2020 16:46:39 -0700
From: 	Kendall Nelson <kennelson11 at gmail.com>
To: 	OpenStack Discuss <openstack-discuss at lists.openstack.org>



The PTL and TC Nomination periods are now over. The official candidate lists
are available on the election website[0][1].

--PTL Election Details--

There are 16 projects without candidates, so according to this 
resolution[2], the TC will have to decide how the following projects 
will proceed: Adjutant Barbican Cloudkitty Congress I18n Infrastructure 
Loci Masakari Oslo Packaging_Rpm Placement Rally Swift Tacker Tricircle 
Zaqar

There are no projects with more than one candidate so we won't need to 
hold any runoffs! Congratulations to our new and returning PTLs! [0]

--TC Election Details--

The official candidate list is available on the election website[1].

There are will be a TC election following the campaigning period that 
has now begun and runs till Apr 07, 2020 23:45 UTC when the polling will 
begin.

You are encouraged to ask questions to the candidates on the ML to help 
inform your decisions when polling begins.

Thank you,

-Kendall (diablo_rojo) & the Election Officials

[0] https://governance.openstack.org/election/#victoria-ptl-candidates
[1] https://governance.openstack.org/election/#victoria-tc-candidates
[2] 
https://governance.openstack.org/resolutions/20141128-elections-process-for-leaderless-programs.html



From ianyrchoi at gmail.com  Thu Apr  2 11:43:29 2020
From: ianyrchoi at gmail.com (Ian Y. Choi)
Date: Thu, 2 Apr 2020 20:43:29 +0900
Subject: [OpenStack-I18n] User "mobarak_hossain_1" request to join
	[bn-IN] language team
In-Reply-To: <1738437819.457.1585819700840@translate01>
References: <1738437819.457.1585819700840@translate01>
Message-ID: <d6c71e0a-63f2-868d-58ce-7999696de65f@gmail.com>

Approved - welcome and please refer to 
https://docs.openstack.org/i18n/latest/ and i18n mailing list.


With many thanks,


/Ian

On 4/2/2020 6:28 PM, Zanata wrote:
>
> Dear Language Team Coordinator,
>
> Zanata user "Mobarak Hossain" with id "mobarak_hossain_1" is 
> requesting to join the bn-IN (বাংলা (ভারত)) language team
> Roles requested:
>
>   * Translator
>
> mobarak_hossain_1 has included the following message with this request:
>
> ------------------------------------------------------------------------
> We are working on openstack since 2013 . We are doing some research on 
> it . We already develop Documentation in our Native Language in Bangla 
> . Now we want to contribute for translation .
> ------------------------------------------------------------------------
>
> You can click the link below to go directly to the bn-IN language 
> request page to process the request. Please reply to Mobarak Hossain 
> at mobarak at plexus.com.bd when you have finished processing this request.
>
> https://translate.openstack.org/language/view/bn-IN/requests 
> <https://translate.openstack.org/language/view/bn-IN/requests>
>
> ------------------------------------------------------------------------
>
> You are receiving this mail because:
> There is no coordinator for language "bn-IN (Bengali (India))"
> You are an administrator
>
> This message generated by Zanata running at: 
> https://translate.openstack.org <https://translate.openstack.org>
>


From amotoki at gmail.com  Thu Apr  2 12:41:03 2020
From: amotoki at gmail.com (Akihiro Motoki)
Date: Thu, 2 Apr 2020 21:41:03 +0900
Subject: [OpenStack-I18n] [I18n][PTL][election] Nominations were over -
 no PTL candidacy
In-Reply-To: <6175f5cf-94e6-045d-6291-1effd140d6d8@gmail.com>
References: <CAJ6yrQhomxb=yuoZRz=mwODYX5E03H4YtQgt89qqYkOtkJ9qRg@mail.gmail.com>
 <6175f5cf-94e6-045d-6291-1effd140d6d8@gmail.com>
Message-ID: <CALhU9tn09ZtCnBB1j8TLHT1501MJorBaT5dkhzPqm=br+ETFkA@mail.gmail.com>

On Wed, Apr 1, 2020 at 10:31 PM Ian Y. Choi <ianyrchoi at gmail.com> wrote:
>
> Hello,
>
> I would like to share with I18n team members + OpenStackers who are
> interested in I18n that there were no PTL nominations for upcoming
> Victoria release cycle.
> I am still serving as an appointed PTL since I cannot run for I18n PTL
> as an election official, but also I honestly tell that my contribution
> has been decreased due to my personal life
> (my baby was born ~50 days ago - so busy but really happy as a father).

First of all, Congrats! Enjoy your new life stage!

> TC started to discuss on leaderless projects [1], and seems that a
> candidate to become to SIG [2] is being discussed as Docs team
> previously moved to Technical Writing SIG.
> I would like to kindly ask opinions from I18n team - unless there are no
> other strong opinions, I will support to become SIG and try to move
> forward for next possible steps.

I wonder what will change if we move to SIG.
That's a big question which hits me. We need to clarify what are the
scope of the i18n team (or SIG).

In my understanding, the roles the i18n team usually care are:
(1) to coordinate and help individual translation teams
    including handling translation failures detected during translation imports
(2) to maintain the translation platform and scripts which import
translation scripts
(3) to encourage translations support in individual projects (mainly
in horizon and horizon plugins)

What are things the SIG cares and who are responsible for what?
(1) and (2) still need to be covered.

Regarding (3), it is already cared by individual project teams like
horizon and their bug tracking system.
the i18n team is not involved so it can be out of scope of the SIG.

Thanks,
Akihiro

>
>
> With many thanks,
>
> /Ian
>
> [1] https://etherpad.openstack.org/p/victoria-leaderless
> [2] https://governance.openstack.org/sigs/
>
> -------- Forwarded Message --------
> Subject:        [all][TC][PTL][election] Nominations Close & Campaigning Begins
> Date:   Tue, 31 Mar 2020 16:46:39 -0700
> From:   Kendall Nelson <kennelson11 at gmail.com>
> To:     OpenStack Discuss <openstack-discuss at lists.openstack.org>
>
>
>
> The PTL and TC Nomination periods are now over. The official candidate lists
> are available on the election website[0][1].
>
> --PTL Election Details--
>
> There are 16 projects without candidates, so according to this
> resolution[2], the TC will have to decide how the following projects
> will proceed: Adjutant Barbican Cloudkitty Congress I18n Infrastructure
> Loci Masakari Oslo Packaging_Rpm Placement Rally Swift Tacker Tricircle
> Zaqar
>
> There are no projects with more than one candidate so we won't need to
> hold any runoffs! Congratulations to our new and returning PTLs! [0]
>
> --TC Election Details--
>
> The official candidate list is available on the election website[1].
>
> There are will be a TC election following the campaigning period that
> has now begun and runs till Apr 07, 2020 23:45 UTC when the polling will
> begin.
>
> You are encouraged to ask questions to the candidates on the ML to help
> inform your decisions when polling begins.
>
> Thank you,
>
> -Kendall (diablo_rojo) & the Election Officials
>
> [0] https://governance.openstack.org/election/#victoria-ptl-candidates
> [1] https://governance.openstack.org/election/#victoria-tc-candidates
> [2]
> https://governance.openstack.org/resolutions/20141128-elections-process-for-leaderless-programs.html
>
>
> _______________________________________________
> 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 Apr  7 13:19:26 2020
From: ianyrchoi at gmail.com (Ian Y. Choi)
Date: Tue, 7 Apr 2020 22:19:26 +0900
Subject: [OpenStack-I18n] User "mohib" request to join [bn-IN] language
	team
In-Reply-To: <1190407446.465.1586155747679@translate01>
References: <1190407446.465.1586155747679@translate01>
Message-ID: <32566c0e-1fa2-214e-7f07-345ade14be90@gmail.com>

Approved - welcome and please refer to
https://docs.openstack.org/i18n/latest/ and i18n mailing list.


With many thanks,


/Ian

On 4/6/2020 3:49 PM, Zanata wrote:
>
> Dear Language Team Coordinator,
>
> Zanata user "Md. Mohib Billah" with id "mohib" is requesting to join 
> the bn-IN (বাংলা (ভারত)) language team
> Roles requested:
>
>   * Translator
>
> mohib has included the following message with this request:
>
> ------------------------------------------------------------------------
> Hi, I am mohib. I am working on openstack installation and 
> administration since 2014. Now I want to contribute in translation 
> openstack documentation in Bangla. Please add me in your group. Thanks
> ------------------------------------------------------------------------
>
> You can click the link below to go directly to the bn-IN language 
> request page to process the request. Please reply to Md. Mohib Billah 
> at mohibbillah10 at gmail.com when you have finished processing this request.
>
> https://translate.openstack.org/language/view/bn-IN/requests 
> <https://translate.openstack.org/language/view/bn-IN/requests>
>
> ------------------------------------------------------------------------
>
> You are receiving this mail because:
> There is no coordinator for language "bn-IN (Bengali (India))"
> You are an administrator
>
> This message generated by Zanata running at: 
> https://translate.openstack.org <https://translate.openstack.org>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-i18n/attachments/20200407/13d2b5df/attachment.html>

From ianyrchoi at gmail.com  Tue Apr  7 13:43:25 2020
From: ianyrchoi at gmail.com (Ian Y. Choi)
Date: Tue, 7 Apr 2020 22:43:25 +0900
Subject: [OpenStack-I18n] [I18n][PTL][election] Nominations were over -
 no PTL candidacy
In-Reply-To: <cbf9fc70-51d5-571e-f858-a4af25bd5924@openstack.org>
References: <CAJ6yrQhomxb=yuoZRz=mwODYX5E03H4YtQgt89qqYkOtkJ9qRg@mail.gmail.com>
 <6175f5cf-94e6-045d-6291-1effd140d6d8@gmail.com>
 <CALhU9tn09ZtCnBB1j8TLHT1501MJorBaT5dkhzPqm=br+ETFkA@mail.gmail.com>
 <cbf9fc70-51d5-571e-f858-a4af25bd5924@openstack.org>
Message-ID: <28c0551a-537b-58b8-e26a-e945258d4c6e@gmail.com>

(Sharing with i18n mailing list)




With many thanks,

/Ian

On 4/3/2020 5:58 PM, Thierry Carrez wrote:
> Akihiro Motoki wrote:
>> [...]
>> I wonder what will change if we move to SIG.
>> That's a big question which hits me. We need to clarify what are the
>> scope of the i18n team (or SIG).
>
> The main difference between a SIG and a Project Team is that SIGs have 
> less constraints. Project Teams are typically used to produce a part 
> of the OpenStack release, and so we require some level of 
> accountability (know who is empowered to sign off releases, know how 
> to contact for embargoed security issues). That is why we currently 
> require that a PTL is determined every 6 months.
>
> SIGs on the other hand are just a group of people sharing a common 
> interest. There might be group leads, but no real need for a final 
> call to be made. It's just a way to pool resources toward a common goal.
>
> Historically we've considered translations as a "part" of the 
> openstack release, and so I18n is currently a project team. That said, 
> I18n is arguably a special interest, it does not really need PTLs to 
> be designated, and the release is OK even if some translations are not 
> complete. It's a 'best effort' work, so it does not require the heavy 
> type of accountability that we require from project teams.
>
> So in summary: making I18n a SIG would remove the need to designate a 
> PTL every 6 months, and just continue work as usual.
>


From aj at suse.com  Sun Apr 19 15:24:52 2020
From: aj at suse.com (Andreas Jaeger)
Date: Sun, 19 Apr 2020 17:24:52 +0200
Subject: [OpenStack-I18n] Retiring i18n-specs
Message-ID: <a8d219bc-d22f-df26-8e05-15d4b99f841b@suse.com>

Ian,

The i18n-specs repo was created 2016 and never used for anything, I
propose to abandon it.

If you agree, please abandon all open changes:
https://review.opendev.org/#/q/project:openstack/i18n-specs+is:open

And then I can propose changes to retire it and will need one further
change merge into the repo marking it as retired,

Andreas
-- 
 Andreas Jaeger aj at suse.com Twitter: jaegerandi
  SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D 90409 Nürnberg
   (HRB 36809, AG Nürnberg) GF: Felix Imendörffer
    GPG fingerprint = EF18 1673 38C4 A372 86B1  E699 5294 24A3 FF91 2ACB


From aj at suse.com  Tue Apr 21 20:27:49 2020
From: aj at suse.com (Andreas Jaeger)
Date: Tue, 21 Apr 2020 22:27:49 +0200
Subject: [OpenStack-I18n] Retiring i18n-specs
In-Reply-To: <a854f3c9-fe53-1006-7370-78deb3f28ee7@suse.com>
References: <a854f3c9-fe53-1006-7370-78deb3f28ee7@suse.com>
Message-ID: <d9a33230-5af0-1135-6c97-2795556e6531@suse.com>

On 18/04/2020 16.22, Andreas Jaeger wrote:
> Ian,
> 
> The i18n-specs repo was created 2016 and never used for anything, I
> propose to abandon it.
> 
> If you agree, please abandon all open changes:
> https://review.opendev.org/#/q/project:openstack/i18n-specs+is:open
> 
> And then I can propose changes to retire it and will need one further
> change merge into the repo marking it as retired,

Ian answered on https://review.opendev.org/720536 to move forward with
retiring the repo.

I pushed the changes to review:
https://review.opendev.org/#/q/topic:retire-i18n-specs

Also, the other 3 changes in
https://review.opendev.org/#/q/status:open+project:openstack/i18n-specs+branch:master
need to be abandoned,

Andreas
-- 
 Andreas Jaeger aj at suse.com Twitter: jaegerandi
  SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D 90409 Nürnberg
   (HRB 36809, AG Nürnberg) GF: Felix Imendörffer
    GPG fingerprint = EF18 1673 38C4 A372 86B1  E699 5294 24A3 FF91 2ACB


From ianyrchoi at gmail.com  Wed Apr 22 09:19:15 2020
From: ianyrchoi at gmail.com (Ian Y. Choi)
Date: Wed, 22 Apr 2020 18:19:15 +0900
Subject: [OpenStack-I18n] Retiring i18n-specs
In-Reply-To: <d9a33230-5af0-1135-6c97-2795556e6531@suse.com>
References: <a854f3c9-fe53-1006-7370-78deb3f28ee7@suse.com>
 <d9a33230-5af0-1135-6c97-2795556e6531@suse.com>
Message-ID: <f17c02bd-3ca9-7022-fa62-2ec542310b6a@gmail.com>

Thank you Andreas for dealing with this, and Motoki-san to move forward 
by reviewing the patches!



With many thanks,


/Ian

On 4/22/2020 5:27 AM, Andreas Jaeger wrote:
> On 18/04/2020 16.22, Andreas Jaeger wrote:
>> Ian,
>>
>> The i18n-specs repo was created 2016 and never used for anything, I
>> propose to abandon it.
>>
>> If you agree, please abandon all open changes:
>> https://review.opendev.org/#/q/project:openstack/i18n-specs+is:open
>>
>> And then I can propose changes to retire it and will need one further
>> change merge into the repo marking it as retired,
> Ian answered on https://review.opendev.org/720536 to move forward with
> retiring the repo.
>
> I pushed the changes to review:
> https://review.opendev.org/#/q/topic:retire-i18n-specs
>
> Also, the other 3 changes in
> https://review.opendev.org/#/q/status:open+project:openstack/i18n-specs+branch:master
> need to be abandoned,
>
> Andreas


From aj at suse.com  Fri Apr 24 09:02:25 2020
From: aj at suse.com (Andreas Jaeger)
Date: Fri, 24 Apr 2020 11:02:25 +0200
Subject: [OpenStack-I18n] Ussuri translations started,
	stopping Stein translations
Message-ID: <84c06b28-70d1-b2cb-032e-2d2645b39cfa@suse.com>

I've started to create ussuri branches in translate.openstack.org and
will at the some time make stein read-only.

I'll start with the dashboard projects - and then take continue later
tonight or over the weekend with others.

Any admin around that wants to help? Please speak up and go ahead. Keep
in mind to use the UI to copy all translations.

I'm pushing changes for the jobs as well now,
Andreas
-- 
 Andreas Jaeger aj at suse.com Twitter: jaegerandi
  SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D 90409 Nürnberg
   (HRB 36809, AG Nürnberg) GF: Felix Imendörffer
    GPG fingerprint = EF18 1673 38C4 A372 86B1  E699 5294 24A3 FF91 2ACB


From aj at suse.com  Fri Apr 24 09:13:45 2020
From: aj at suse.com (Andreas Jaeger)
Date: Fri, 24 Apr 2020 11:13:45 +0200
Subject: [OpenStack-I18n] Ussuri translations started,
 stopping Stein translations
In-Reply-To: <84c06b28-70d1-b2cb-032e-2d2645b39cfa@suse.com>
References: <84c06b28-70d1-b2cb-032e-2d2645b39cfa@suse.com>
Message-ID: <a03decf4-40b0-2ec6-643e-5ecc2acd5240@suse.com>

On 24.04.20 11:02, Andreas Jaeger wrote:
> I've started to create ussuri branches in translate.openstack.org and
> will at the some time make stein read-only.
> 
> I'll start with the dashboard projects - and then take continue later
> tonight or over the weekend with others.

Note: Don't translate release notes in Ussuri, they are only translated
in master, I'll try to delete them when copying but in case I forget,
just ignore them - the next merge will delete them,

Andreas
-- 
 Andreas Jaeger aj at suse.com Twitter: jaegerandi
  SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D 90409 Nürnberg
   (HRB 36809, AG Nürnberg) GF: Felix Imendörffer
    GPG fingerprint = EF18 1673 38C4 A372 86B1  E699 5294 24A3 FF91 2ACB


From amotoki at gmail.com  Fri Apr 24 13:20:28 2020
From: amotoki at gmail.com (Akihiro Motoki)
Date: Fri, 24 Apr 2020 22:20:28 +0900
Subject: [OpenStack-I18n] Ussuri translations started,
	stopping Stein translations
In-Reply-To: <84c06b28-70d1-b2cb-032e-2d2645b39cfa@suse.com>
References: <84c06b28-70d1-b2cb-032e-2d2645b39cfa@suse.com>
Message-ID: <CALhU9tn0mR9Xr=XYif7cs6vC5VM5kisTYwCKg7MXerYtqst0OA@mail.gmail.com>

On Fri, Apr 24, 2020 at 6:03 PM Andreas Jaeger <aj at suse.com> wrote:
>
> I've started to create ussuri branches in translate.openstack.org and
> will at the some time make stein read-only.
>
> I'll start with the dashboard projects - and then take continue later
> tonight or over the weekend with others.
>
> Any admin around that wants to help? Please speak up and go ahead. Keep
> in mind to use the UI to copy all translations.

Is it a fully manual process?
I am not a zanata admin and don't know the detail,
but if so it looks better to share the effort with several folks.

In addition, we need to document what we should do (for further
release cycles).

-amotoki

>
> I'm pushing changes for the jobs as well now,
> Andreas
> --
>  Andreas Jaeger aj at suse.com Twitter: jaegerandi
>   SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D 90409 Nürnberg
>    (HRB 36809, AG Nürnberg) GF: Felix Imendörffer
>     GPG fingerprint = EF18 1673 38C4 A372 86B1  E699 5294 24A3 FF91 2ACB
>
> _______________________________________________
> OpenStack-I18n mailing list
> OpenStack-I18n at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n


From aj at suse.com  Fri Apr 24 13:22:23 2020
From: aj at suse.com (Andreas Jaeger)
Date: Fri, 24 Apr 2020 15:22:23 +0200
Subject: [OpenStack-I18n] Ussuri translations started,
 stopping Stein translations
In-Reply-To: <CALhU9tn0mR9Xr=XYif7cs6vC5VM5kisTYwCKg7MXerYtqst0OA@mail.gmail.com>
References: <84c06b28-70d1-b2cb-032e-2d2645b39cfa@suse.com>
 <CALhU9tn0mR9Xr=XYif7cs6vC5VM5kisTYwCKg7MXerYtqst0OA@mail.gmail.com>
Message-ID: <51672811-fe63-a73e-11fd-cfa85d095b4d@suse.com>

On 24.04.20 15:20, Akihiro Motoki wrote:
> On Fri, Apr 24, 2020 at 6:03 PM Andreas Jaeger <aj at suse.com> wrote:
>>
>> I've started to create ussuri branches in translate.openstack.org and
>> will at the some time make stein read-only.
>>
>> I'll start with the dashboard projects - and then take continue later
>> tonight or over the weekend with others.
>>
>> Any admin around that wants to help? Please speak up and go ahead. Keep
>> in mind to use the UI to copy all translations.
> 
> Is it a fully manual process?

The copying cannot done via CLI, the CLI does not support copying ;(

> I am not a zanata admin and don't know the detail,
> but if so it looks better to share the effort with several folks.
> 
> In addition, we need to document what we should do (for further
> release cycles).

Isn't that already in i18n repo?

Andreas
-- 
 Andreas Jaeger aj at suse.com Twitter: jaegerandi
  SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D 90409 Nürnberg
   (HRB 36809, AG Nürnberg) GF: Felix Imendörffer
    GPG fingerprint = EF18 1673 38C4 A372 86B1  E699 5294 24A3 FF91 2ACB


From ianyrchoi at gmail.com  Fri Apr 24 16:02:34 2020
From: ianyrchoi at gmail.com (Ian Y. Choi)
Date: Sat, 25 Apr 2020 01:02:34 +0900
Subject: [OpenStack-I18n] Ussuri translations started,
 stopping Stein translations
In-Reply-To: <51672811-fe63-a73e-11fd-cfa85d095b4d@suse.com>
References: <84c06b28-70d1-b2cb-032e-2d2645b39cfa@suse.com>
 <CALhU9tn0mR9Xr=XYif7cs6vC5VM5kisTYwCKg7MXerYtqst0OA@mail.gmail.com>
 <51672811-fe63-a73e-11fd-cfa85d095b4d@suse.com>
Message-ID: <34b17e1d-b123-a66c-7c91-1be8b9572e65@gmail.com>

Thank you for calling out - it seems that currently only me as Zanata 
admin from I18n team is alive.

I will take care of that on the very early of next week (maybe, upcoming 
Sunday).


Hello Motoki-san,


The current documentation is available at 
https://docs.openstack.org/i18n/latest/release_management.html .

By the way, would you also help look I18n team as Zanata admin view if 
you are fine?

Note that Zanata admin privileges have been given to only I18n PTLs, 
Foundation, and Infra team members
but I am happy to support who speak up, volunteer, and go ahead under 
the agreement of existing active core reviewers. I can loop the 
communication
(Now I think about some simple NDA processes for securing privacy, 
although I might need to start another thread of communication).



With many thanks,


/Ian

On 4/24/2020 10:22 PM, Andreas Jaeger wrote:
> On 24.04.20 15:20, Akihiro Motoki wrote:
>> On Fri, Apr 24, 2020 at 6:03 PM Andreas Jaeger <aj at suse.com> wrote:
>>> I've started to create ussuri branches in translate.openstack.org and
>>> will at the some time make stein read-only.
>>>
>>> I'll start with the dashboard projects - and then take continue later
>>> tonight or over the weekend with others.
>>>
>>> Any admin around that wants to help? Please speak up and go ahead. Keep
>>> in mind to use the UI to copy all translations.
>> Is it a fully manual process?
> The copying cannot done via CLI, the CLI does not support copying ;(
>
>> I am not a zanata admin and don't know the detail,
>> but if so it looks better to share the effort with several folks.
>>
>> In addition, we need to document what we should do (for further
>> release cycles).
> Isn't that already in i18n repo?
>
> Andreas


From aj at suse.com  Sat Apr 25 11:48:33 2020
From: aj at suse.com (Andreas Jaeger)
Date: Sat, 25 Apr 2020 13:48:33 +0200
Subject: [OpenStack-I18n] Ussuri translations started,
 stopping Stein translations
In-Reply-To: <34b17e1d-b123-a66c-7c91-1be8b9572e65@gmail.com>
References: <84c06b28-70d1-b2cb-032e-2d2645b39cfa@suse.com>
 <CALhU9tn0mR9Xr=XYif7cs6vC5VM5kisTYwCKg7MXerYtqst0OA@mail.gmail.com>
 <51672811-fe63-a73e-11fd-cfa85d095b4d@suse.com>
 <34b17e1d-b123-a66c-7c91-1be8b9572e65@gmail.com>
Message-ID: <77a8c128-41f2-22c0-49d2-5b838015ebe2@suse.com>

On 24.04.20 18:02, Ian Y. Choi wrote:
> Thank you for calling out - it seems that currently only me as Zanata
> admin from I18n team is alive.
> 
> I will take care of that on the very early of next week (maybe, upcoming
> Sunday).

I've created all ussuri branches now, translators can start translating.

I have *not* updated the front page and the Ussuri groups. Ian, please
take care of that.

Andreas
-- 
 Andreas Jaeger aj at suse.com Twitter: jaegerandi
  SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D 90409 Nürnberg
   (HRB 36809, AG Nürnberg) GF: Felix Imendörffer
    GPG fingerprint = EF18 1673 38C4 A372 86B1  E699 5294 24A3 FF91 2ACB


From aj at suse.com  Sun Apr 26 12:31:14 2020
From: aj at suse.com (Andreas Jaeger)
Date: Sun, 26 Apr 2020 14:31:14 +0200
Subject: [OpenStack-I18n] Stop translating non-UI projects for stable
	branches?
Message-ID: <d8f572c4-4725-d188-68e6-026f9550bf86@suse.com>

Looking at the work to branch a new release and the amount of
translation done on stable branches for the non-ui projects (ceilometer,
cinder, nova etc), I propose to translate them *only* on master.

So, we would continue to translate on master and stable horizon and
friends - and that's all.

If there's a specific project that needs translation, we can change that
one for sure.

This reflects IMHO how translators translate today.

I've proposed the following change and marked it WIP for discussion here
and waiting until Ussuri release:
https://review.opendev.org/723217

Andreas
-- 
 Andreas Jaeger aj at suse.com Twitter: jaegerandi
  SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D 90409 Nürnberg
   (HRB 36809, AG Nürnberg) GF: Felix Imendörffer
    GPG fingerprint = EF18 1673 38C4 A372 86B1  E699 5294 24A3 FF91 2ACB


From ianyrchoi at gmail.com  Sun Apr 26 17:51:26 2020
From: ianyrchoi at gmail.com (Ian Y. Choi)
Date: Mon, 27 Apr 2020 02:51:26 +0900
Subject: [OpenStack-I18n] Ussuri translations started,
 stopping Stein translations
In-Reply-To: <77a8c128-41f2-22c0-49d2-5b838015ebe2@suse.com>
References: <84c06b28-70d1-b2cb-032e-2d2645b39cfa@suse.com>
 <CALhU9tn0mR9Xr=XYif7cs6vC5VM5kisTYwCKg7MXerYtqst0OA@mail.gmail.com>
 <51672811-fe63-a73e-11fd-cfa85d095b4d@suse.com>
 <34b17e1d-b123-a66c-7c91-1be8b9572e65@gmail.com>
 <77a8c128-41f2-22c0-49d2-5b838015ebe2@suse.com>
Message-ID: <2b3070fd-d2bc-990e-ce6a-6c8df238ed1a@gmail.com>

Thank you, Andreas. I have updated like the followings:


R-3 is/Hard StringFreeze/, and R-1 is for/Final RCs/- see 
now*Ussuri*release at*/OpenStack Release Schedule 
<https://releases.openstack.org/ussuri/schedule.html>/*:
https://releases.openstack.org/ussuri/schedule.html

  *

    Key priority: dashboard projects (available:*/Ussuri Dashboard
    translation project list
    <https://translate.openstack.org/version-group/view/Ussuri-dashboard-translation/projects>/*)
    -
    https://translate.openstack.org/version-group/view/Ussuri-dashboard-translation/projects

  *

    Also see other stable branch artifacts (available:*/Translation
    project list with stable branches
    <https://translate.openstack.org/version-group/view/project-master-list-with-stable/projects>/*,
    currently for*Ussuri*) -
    https://translate.openstack.org/version-group/view/project-master-list-with-stable/projects


With many thanks,


/Ian

On 4/25/2020 8:48 PM, Andreas Jaeger wrote:
> On 24.04.20 18:02, Ian Y. Choi wrote:
>> Thank you for calling out - it seems that currently only me as Zanata
>> admin from I18n team is alive.
>>
>> I will take care of that on the very early of next week (maybe, upcoming
>> Sunday).
> I've created all ussuri branches now, translators can start translating.
>
> I have *not* updated the front page and the Ussuri groups. Ian, please
> take care of that.
>
> Andreas


From ianyrchoi at gmail.com  Sun Apr 26 17:56:45 2020
From: ianyrchoi at gmail.com (Ian Y. Choi)
Date: Mon, 27 Apr 2020 02:56:45 +0900
Subject: [OpenStack-I18n] Stop translating non-UI projects for stable
 branches?
In-Reply-To: <d8f572c4-4725-d188-68e6-026f9550bf86@suse.com>
References: <d8f572c4-4725-d188-68e6-026f9550bf86@suse.com>
Message-ID: <f1d94ecc-16e2-0871-0556-c590841a3217@gmail.com>

Let's discuss after Ussuri release. Agree with reflecting the current 
translator nature today.


Related thoughts and discussions might be:

- List of UI projects: how we get this information?

- Target release: only for cycle-with-rc or including 
cycle-with-intermediary

- I18n team needs to stay with deeper eyes on release model changes 
(e.g., Horizon's cycle-with-rc -> cycle-with-intermediary during Ussuri 
cycle) & translation effort (e.g., how many translations are going on 
many projects)

- Needs to think about procedure how to deal with translation bugs on 
stable branches for master-only projects



With many thanks,


/Ian

On 4/26/2020 9:31 PM, Andreas Jaeger wrote:
> Looking at the work to branch a new release and the amount of
> translation done on stable branches for the non-ui projects (ceilometer,
> cinder, nova etc), I propose to translate them *only* on master.
>
> So, we would continue to translate on master and stable horizon and
> friends - and that's all.
>
> If there's a specific project that needs translation, we can change that
> one for sure.
>
> This reflects IMHO how translators translate today.
>
> I've proposed the following change and marked it WIP for discussion here
> and waiting until Ussuri release:
> https://review.opendev.org/723217
>
> Andreas


From aj at suse.com  Sun Apr 26 18:06:08 2020
From: aj at suse.com (Andreas Jaeger)
Date: Sun, 26 Apr 2020 20:06:08 +0200
Subject: [OpenStack-I18n] Stop translating non-UI projects for stable
 branches?
In-Reply-To: <f1d94ecc-16e2-0871-0556-c590841a3217@gmail.com>
References: <d8f572c4-4725-d188-68e6-026f9550bf86@suse.com>
 <f1d94ecc-16e2-0871-0556-c590841a3217@gmail.com>
Message-ID: <4a827dcb-c44c-619f-d172-3fb618fe35a2@suse.com>

On 26/04/2020 19.56, Ian Y. Choi wrote:
> Let's discuss after Ussuri release. Agree with reflecting the current
> translator nature today.

The change is WIP for now, I wanted to start the discussion so that we
can make a decision after Ussuri release.

> 
> Related thoughts and discussions might be:
> 
> - List of UI projects: how we get this information?

You have it already on translate.o.o with " Ussuri Dashboard translation
project list" UI = Dashboards


> - Target release: only for cycle-with-rc or including
> cycle-with-intermediary
>
> - I18n team needs to stay with deeper eyes on release model changes
> (e.g., Horizon's cycle-with-rc -> cycle-with-intermediary during Ussuri
> cycle) & translation effort (e.g., how many translations are going on
> many projects)

I'm not understanding how these play a role here. Creating intermediate
releases does not create new branches, so no change needed.


> 
> - Needs to think about procedure how to deal with translation bugs on
> stable branches for master-only projects

How many did we get in the past for the projects I propose to change to
master only?

I guess 99 % of the translation effort is on UI/Dashboard projects and
there's no change.


Andreas

> 
> 
> 
> With many thanks,
> 
> 
> /Ian
> 
> On 4/26/2020 9:31 PM, Andreas Jaeger wrote:
>> Looking at the work to branch a new release and the amount of
>> translation done on stable branches for the non-ui projects (ceilometer,
>> cinder, nova etc), I propose to translate them *only* on master.
>>
>> So, we would continue to translate on master and stable horizon and
>> friends - and that's all.
>>
>> If there's a specific project that needs translation, we can change that
>> one for sure.
>>
>> This reflects IMHO how translators translate today.
>>
>> I've proposed the following change and marked it WIP for discussion here
>> and waiting until Ussuri release:
>> https://review.opendev.org/723217
>>
>> Andreas


-- 
 Andreas Jaeger aj at suse.com Twitter: jaegerandi
  SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D 90409 Nürnberg
   (HRB 36809, AG Nürnberg) GF: Felix Imendörffer
    GPG fingerprint = EF18 1673 38C4 A372 86B1  E699 5294 24A3 FF91 2ACB


From amotoki at gmail.com  Mon Apr 27 01:36:53 2020
From: amotoki at gmail.com (Akihiro Motoki)
Date: Mon, 27 Apr 2020 10:36:53 +0900
Subject: [OpenStack-I18n] Stop translating non-UI projects for stable
	branches?
In-Reply-To: <4a827dcb-c44c-619f-d172-3fb618fe35a2@suse.com>
References: <d8f572c4-4725-d188-68e6-026f9550bf86@suse.com>
 <f1d94ecc-16e2-0871-0556-c590841a3217@gmail.com>
 <4a827dcb-c44c-619f-d172-3fb618fe35a2@suse.com>
Message-ID: <CALhU9tkmK_b9a-AeK9He+i_R4UVX8fimnX--8yDGcTaM1=7PGw@mail.gmail.com>

> > On 4/26/2020 9:31 PM, Andreas Jaeger wrote:
> >> Looking at the work to branch a new release and the amount of
> >> translation done on stable branches for the non-ui projects (ceilometer,
> >> cinder, nova etc), I propose to translate them *only* on master.

Generally agree with the proposal, but we should consider what are actually
translated in addition to the translation stats.
>From my knowledge, what we (not me :p but most translators) translate are
dashboard strings (in stable branches) and release notes (in the master branch).
Considering this, the proposal makes sense to me.

I am replying one by one below.

On Mon, Apr 27, 2020 at 3:06 AM Andreas Jaeger <aj at suse.com> wrote:
>
> On 26/04/2020 19.56, Ian Y. Choi wrote:
> > Let's discuss after Ussuri release. Agree with reflecting the current
> > translator nature today.
>
> The change is WIP for now, I wanted to start the discussion so that we
> can make a decision after Ussuri release.
>
> >
> > Related thoughts and discussions might be:
> >
> > - List of UI projects: how we get this information?
>
> You have it already on translate.o.o with " Ussuri Dashboard translation
> project list" UI = Dashboards

I think Ian's point is how to maintain the list in Zanata with the
minimum effort.

In horizon, we generate horizon plugin lists based on the deliverable
files in the releases repo.
The script checks the deliverable type is "horizon-plugin". It is now
run manually.
https://opendev.org/openstack/horizon/src/branch/master/tools/list-horizon-plugins.py

Perhaps, you can do the similar thing combined with
project-config/gerrit/projects.yaml
which defines which projects turn on translation.

> > - Target release: only for cycle-with-rc or including
> > cycle-with-intermediary
> >
> > - I18n team needs to stay with deeper eyes on release model changes
> > (e.g., Horizon's cycle-with-rc -> cycle-with-intermediary during Ussuri
> > cycle) & translation effort (e.g., how many translations are going on
> > many projects)
>
> I'm not understanding how these play a role here. Creating intermediate
> releases does not create new branches, so no change needed.

I think it affects when stable branches are created.
For projects with cycle-with-rc, we can expect that stable branches
are created at the week of RC1,
but for projects with cycle-with-intermediary, it is up to individual
teams and we cannot have
the general expectation on when stable branches are created.

> > - Needs to think about procedure how to deal with translation bugs on
> > stable branches for master-only projects
>
> How many did we get in the past for the projects I propose to change to
> master only?
>
> I guess 99 % of the translation effort is on UI/Dashboard projects and
> there's no change.

Andreas's proposal is based on the fact that non-UI projects only have
translations
on release notes and other contents like exception messages are not
translated at all.
Release notes translations only happen in the master branch, so there
is no need to
consider translation bugs on stable branches.

This reminds me a topic on translation bugs on older stable branches
which I raised before.
I got no reply on that. Perhaps we should accept direct fixes via
gerrit for such stable branches
which are no longer supported in zanata.

Akihiro

>
>
> Andreas
>
> >
> >
> >
> > With many thanks,
> >
> >
> > /Ian
> >
> > On 4/26/2020 9:31 PM, Andreas Jaeger wrote:
> >> Looking at the work to branch a new release and the amount of
> >> translation done on stable branches for the non-ui projects (ceilometer,
> >> cinder, nova etc), I propose to translate them *only* on master.
> >>
> >> So, we would continue to translate on master and stable horizon and
> >> friends - and that's all.
> >>
> >> If there's a specific project that needs translation, we can change that
> >> one for sure.
> >>
> >> This reflects IMHO how translators translate today.
> >>
> >> I've proposed the following change and marked it WIP for discussion here
> >> and waiting until Ussuri release:
> >> https://review.opendev.org/723217
> >>
> >> Andreas
>
>
> --
>  Andreas Jaeger aj at suse.com Twitter: jaegerandi
>   SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D 90409 Nürnberg
>    (HRB 36809, AG Nürnberg) GF: Felix Imendörffer
>     GPG fingerprint = EF18 1673 38C4 A372 86B1  E699 5294 24A3 FF91 2ACB
>
> _______________________________________________
> OpenStack-I18n mailing list
> OpenStack-I18n at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n


From aj at suse.com  Mon Apr 27 06:22:23 2020
From: aj at suse.com (Andreas Jaeger)
Date: Mon, 27 Apr 2020 08:22:23 +0200
Subject: [OpenStack-I18n] Stop translating non-UI projects for stable
 branches?
In-Reply-To: <CALhU9tkmK_b9a-AeK9He+i_R4UVX8fimnX--8yDGcTaM1=7PGw@mail.gmail.com>
References: <d8f572c4-4725-d188-68e6-026f9550bf86@suse.com>
 <f1d94ecc-16e2-0871-0556-c590841a3217@gmail.com>
 <4a827dcb-c44c-619f-d172-3fb618fe35a2@suse.com>
 <CALhU9tkmK_b9a-AeK9He+i_R4UVX8fimnX--8yDGcTaM1=7PGw@mail.gmail.com>
Message-ID: <639413d2-c5c0-e1f0-2cf8-66c2f2a39e39@suse.com>

On 27.04.20 03:36, Akihiro Motoki wrote:
> [..]
> This reminds me a topic on translation bugs on older stable branches
> which I raised before.
> I got no reply on that. Perhaps we should accept direct fixes via
> gerrit for such stable branches
> which are no longer supported in zanata.

Agreed - but I would only do it for severe ones, not for nits,

Andreas
-- 
 Andreas Jaeger aj at suse.com Twitter: jaegerandi
  SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D 90409 Nürnberg
   (HRB 36809, AG Nürnberg) GF: Felix Imendörffer
    GPG fingerprint = EF18 1673 38C4 A372 86B1  E699 5294 24A3 FF91 2ACB


From aj at suse.com  Mon Apr 27 06:29:17 2020
From: aj at suse.com (Andreas Jaeger)
Date: Mon, 27 Apr 2020 08:29:17 +0200
Subject: [OpenStack-I18n] Stop translating non-UI projects for stable
 branches?
In-Reply-To: <CALhU9tkmK_b9a-AeK9He+i_R4UVX8fimnX--8yDGcTaM1=7PGw@mail.gmail.com>
References: <d8f572c4-4725-d188-68e6-026f9550bf86@suse.com>
 <f1d94ecc-16e2-0871-0556-c590841a3217@gmail.com>
 <4a827dcb-c44c-619f-d172-3fb618fe35a2@suse.com>
 <CALhU9tkmK_b9a-AeK9He+i_R4UVX8fimnX--8yDGcTaM1=7PGw@mail.gmail.com>
Message-ID: <b8b4ccfe-2c95-1293-86d9-f64a87135139@suse.com>

On 27.04.20 03:36, Akihiro Motoki wrote:
>>> On 4/26/2020 9:31 PM, Andreas Jaeger wrote:
>>>> Looking at the work to branch a new release and the amount of
>>>> translation done on stable branches for the non-ui projects (ceilometer,
>>>> cinder, nova etc), I propose to translate them *only* on master.
> 
> Generally agree with the proposal, but we should consider what are actually
> translated in addition to the translation stats.
> From my knowledge, what we (not me :p but most translators) translate are
> dashboard strings (in stable branches) and release notes (in the master branch).
> Considering this, the proposal makes sense to me.
> 
> I am replying one by one below.
> 
> On Mon, Apr 27, 2020 at 3:06 AM Andreas Jaeger <aj at suse.com> wrote:
>>
>> On 26/04/2020 19.56, Ian Y. Choi wrote:
>>> Let's discuss after Ussuri release. Agree with reflecting the current
>>> translator nature today.
>>
>> The change is WIP for now, I wanted to start the discussion so that we
>> can make a decision after Ussuri release.
>>
>>>
>>> Related thoughts and discussions might be:
>>>
>>> - List of UI projects: how we get this information?
>>
>> You have it already on translate.o.o with " Ussuri Dashboard translation
>> project list" UI = Dashboards
> 
> I think Ian's point is how to maintain the list in Zanata with the
> minimum effort.
> 
> In horizon, we generate horizon plugin lists based on the deliverable
> files in the releases repo.
> The script checks the deliverable type is "horizon-plugin". It is now
> run manually.
> https://opendev.org/openstack/horizon/src/branch/master/tools/list-horizon-plugins.py

This seldom changes, doesn't it? We should update the docs on which job
to run, so that teams following the docs make the right choice.

> Perhaps, you can do the similar thing combined with
> project-config/gerrit/projects.yaml
> which defines which projects turn on translation.
> 
>>> - Target release: only for cycle-with-rc or including
>>> cycle-with-intermediary
>>>
>>> - I18n team needs to stay with deeper eyes on release model changes
>>> (e.g., Horizon's cycle-with-rc -> cycle-with-intermediary during Ussuri
>>> cycle) & translation effort (e.g., how many translations are going on
>>> many projects)
>>
>> I'm not understanding how these play a role here. Creating intermediate
>> releases does not create new branches, so no change needed.
> 
> I think it affects when stable branches are created.
> For projects with cycle-with-rc, we can expect that stable branches
> are created at the week of RC1,
> but for projects with cycle-with-intermediary, it is up to individual
> teams and we cannot have
> the general expectation on when stable branches are created.

Ah, I see.

But nothing on the timng changes my proposal - that is more a question
on when to create branches, correct?

Andreas
-- 
 Andreas Jaeger aj at suse.com Twitter: jaegerandi
  SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D 90409 Nürnberg
   (HRB 36809, AG Nürnberg) GF: Felix Imendörffer
    GPG fingerprint = EF18 1673 38C4 A372 86B1  E699 5294 24A3 FF91 2ACB


From aj at suse.com  Mon Apr 27 06:54:56 2020
From: aj at suse.com (Andreas Jaeger)
Date: Mon, 27 Apr 2020 08:54:56 +0200
Subject: [OpenStack-I18n] Stop translating non-UI projects for stable
 branches?
In-Reply-To: <CALhU9tkmK_b9a-AeK9He+i_R4UVX8fimnX--8yDGcTaM1=7PGw@mail.gmail.com>
References: <d8f572c4-4725-d188-68e6-026f9550bf86@suse.com>
 <f1d94ecc-16e2-0871-0556-c590841a3217@gmail.com>
 <4a827dcb-c44c-619f-d172-3fb618fe35a2@suse.com>
 <CALhU9tkmK_b9a-AeK9He+i_R4UVX8fimnX--8yDGcTaM1=7PGw@mail.gmail.com>
Message-ID: <2fe85842-1bd8-20fb-29ab-9c82725df2be@suse.com>

On 27.04.20 03:36, Akihiro Motoki wrote:
> [...]
> In horizon, we generate horizon plugin lists based on the deliverable
> files in the releases repo.
> The script checks the deliverable type is "horizon-plugin". It is now
> run manually.
> https://opendev.org/openstack/horizon/src/branch/master/tools/list-horizon-plugins.py

I've updated my change https://review.opendev.org/723217 to add stable
translations for those in the list, which moved networking-bgpvpn and
cloudkitty-dashboard to translate stable branches as well.

Change is still WIP - but shows what I'm proposing,
Andreas
-- 
 Andreas Jaeger aj at suse.com Twitter: jaegerandi
  SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D 90409 Nürnberg
   (HRB 36809, AG Nürnberg) GF: Felix Imendörffer
    GPG fingerprint = EF18 1673 38C4 A372 86B1  E699 5294 24A3 FF91 2ACB