ATC candidates listing
Hi Daisy, Action item from last meeting. Japanese team finished ATC candidates listing. Thanks, KATO Tomoyuki
Dear coordinators, We are starting the process to get active translators free "ATC" registration codes for Tokyo summit. I need your help to finish below two items in order to get "ATC" codes for them. 1. Collect the email+name pairs for those ATC candidates [1]. I have exported the translators contribution statistics from Transifex since 2014.11.1 to 2015.7.16. Please collect email+name of those translators who has translated more than 200 words, and fill in the table. KATO Tomoyuki has finished the collection of Japanese team. You could use his input as a reference. 2. Have those ATC candidates to sign the ICLA. "Sign the appropriate Individual Contributor License Agreement" in [2] clearly gives guidance to sign the ICLA. If you meet with any problems, please contact with me. I hope we could finish these steps before August 15th. Thus we might have enough time to run through the remained process. When you have done your work, send an email to me. Thank you. Best regards Ying Chun Guo (Daisy) [1] https://docs.google.com/spreadsheets/d/1YpDJU_uNA4I5fzFG69T6L9gpFsy5yNtA9a-l... [2] http://docs.openstack.org/infra/manual/developers.html#account-setup KATO Tomoyuki <tomo@dream.daynight.jp> wrote on 07/26/2015 09:14:14 PM:
From: KATO Tomoyuki <tomo@dream.daynight.jp> To: openstack-i18n@lists.openstack.org Date: 07/26/2015 09:14 PM Subject: [Openstack-i18n] ATC candidates listing
Hi Daisy,
Action item from last meeting. Japanese team finished ATC candidates listing.
Thanks, KATO Tomoyuki
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
Hello Daisy, I have started to contact the french translators, but I am not able to edit the spreadsheet :/ Can you please give me some writing rights ? Thanks a lot :) Best, F. On Wed, Jul 29, 2015 at 9:58 AM, Ying Chun Guo <guoyingc@cn.ibm.com> wrote:
Dear coordinators,
We are starting the process to get active translators free "ATC" registration codes for Tokyo summit. I need your help to finish below two items in order to get "ATC" codes for them.
1. Collect the email+name pairs for those ATC candidates [1]. I have exported the translators contribution statistics from Transifex since 2014.11.1 to 2015.7.16. Please collect email+name of those translators who has translated more than 200 words, and fill in the table. KATO Tomoyuki has finished the collection of Japanese team. You could use his input as a reference.
2. Have those ATC candidates to sign the ICLA. "Sign the appropriate Individual Contributor License Agreement" in [2] clearly gives guidance to sign the ICLA. If you meet with any problems, please contact with me.
I hope we could finish these steps before August 15th. Thus we might have enough time to run through the remained process.
When you have done your work, send an email to me. Thank you.
Best regards Ying Chun Guo (Daisy)
[1] https://docs.google.com/spreadsheets/d/1YpDJU_uNA4I5fzFG69T6L9gpFsy5yNtA9a-l... *[2] *http://docs.openstack.org/infra/manual/developers.html#account-setup
KATO Tomoyuki <tomo@dream.daynight.jp> wrote on 07/26/2015 09:14:14 PM:
From: KATO Tomoyuki <tomo@dream.daynight.jp> To: openstack-i18n@lists.openstack.org Date: 07/26/2015 09:14 PM Subject: [Openstack-i18n] ATC candidates listing
Hi Daisy,
Action item from last meeting. Japanese team finished ATC candidates listing.
Thanks, KATO Tomoyuki
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
On 2015-07-29 15:58:15 +0800 (+0800), Ying Chun Guo wrote: [...]
2. Have those ATC candidates to sign the ICLA. "Sign the appropriate Individual Contributor License Agreement" in [2] clearly gives guidance to sign the ICLA. If you meet with any problems, please contact with me. [...]
It's worth noting that this also requires you to _first_ join the OpenStack Foundation as an Individual Member (it's free and only takes a minute). People skimming the account setup document often accidentally skip that step and then get confused. Basically you go to https://www.openstack.org/join/ and select the "Foundation Member" button (not "Community Member"). -- Jeremy Stanley
Yes, becoming a foundation member is required for all contributors. Thank you for the reminder. Best regards Ying Chun Guo (Daisy) Jeremy Stanley <fungi@yuggoth.org> wrote on 07/29/2015 09:12:12 PM:
From: Jeremy Stanley <fungi@yuggoth.org> To: openstack-i18n@lists.openstack.org Date: 07/29/2015 09:12 PM Subject: Re: [Openstack-i18n] ATC candidates listing - call for coodinators' action
On 2015-07-29 15:58:15 +0800 (+0800), Ying Chun Guo wrote: [...]
2. Have those ATC candidates to sign the ICLA. "Sign the appropriate Individual Contributor License Agreement" in [2] clearly gives guidance to sign the ICLA. If you meet with any problems, please contact with me. [...]
It's worth noting that this also requires you to _first_ join the OpenStack Foundation as an Individual Member (it's free and only takes a minute). People skimming the account setup document often accidentally skip that step and then get confused. Basically you go to https://www.openstack.org/join/ and select the "Foundation Member" button (not "Community Member"). -- Jeremy Stanley [attachment "signature.asc" deleted by Ying Chun Guo/China/IBM] _______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
I write all these down in a wiki page about how to become a translator, please help to improve. https://wiki.openstack.org/wiki/I18nTeam/become-a-official-translator Best regards Ying Chun Guo (Daisy) Jeremy Stanley <fungi@yuggoth.org> wrote on 07/29/2015 09:12:12 PM:
From: Jeremy Stanley <fungi@yuggoth.org> To: openstack-i18n@lists.openstack.org Date: 07/29/2015 09:12 PM Subject: Re: [Openstack-i18n] ATC candidates listing - call for coodinators' action
On 2015-07-29 15:58:15 +0800 (+0800), Ying Chun Guo wrote: [...]
2. Have those ATC candidates to sign the ICLA. "Sign the appropriate Individual Contributor License Agreement" in [2] clearly gives guidance to sign the ICLA. If you meet with any problems, please contact with me. [...]
It's worth noting that this also requires you to _first_ join the OpenStack Foundation as an Individual Member (it's free and only takes a minute). People skimming the account setup document often accidentally skip that step and then get confused. Basically you go to https://www.openstack.org/join/ and select the "Foundation Member" button (not "Community Member"). -- Jeremy Stanley [attachment "signature.asc" deleted by Ying Chun Guo/China/IBM] _______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
On 2015-07-30 16:40:48 +0800 (+0800), Ying Chun Guo wrote:
I write all these down in a wiki page about how to become a translator, please help to improve.
https://wiki.openstack.org/wiki/I18nTeam/become-a-official-translator
For the sake of maintainability, please avoid duplicating any steps documented at http://docs.openstack.org/infra/manual/developers.html#account-setup and link to it instead for those aspects of the account setup process. If it's lacking detail or unclear on how to set up (Launchpad, Foundation, Gerrit) accounts then please help us extend and clarify it accordingly. Thanks! -- Jeremy Stanley
Hi Daisy, I am confused with the wiki page you wrote about becoming a new translator. The wiki page mentions only Zanata and Transifex is not mentioned. Should a new translator use Zanata *right now* (and at least for Libetry) for translations? AFAIK, we are still using Transifex. I was ask from a Japanese folk who wants to start translations and advised him to use Transifex. Is it correct or not? What is the official process and suggestions? If someone has made a work on Transifex from now, can he/she get ATC status if he/she satisfies the requirements? If not, we should announce the situation more clearly to avoid confusion. I believe I followed almost all discussion in this list, but the situation is still unclear to me. Akihiro 2015-07-30 17:40 GMT+09:00 Ying Chun Guo <guoyingc@cn.ibm.com>:
I write all these down in a wiki page about how to become a translator, please help to improve.
https://wiki.openstack.org/wiki/I18nTeam/become-a-official-translator
Best regards Ying Chun Guo (Daisy)
Jeremy Stanley <fungi@yuggoth.org> wrote on 07/29/2015 09:12:12 PM:
From: Jeremy Stanley <fungi@yuggoth.org> To: openstack-i18n@lists.openstack.org Date: 07/29/2015 09:12 PM Subject: Re: [Openstack-i18n] ATC candidates listing - call for coodinators' action
On 2015-07-29 15:58:15 +0800 (+0800), Ying Chun Guo wrote: [...]
2. Have those ATC candidates to sign the ICLA. "Sign the appropriate Individual Contributor License Agreement" in [2] clearly gives guidance to sign the ICLA. If you meet with any problems, please contact with me. [...]
It's worth noting that this also requires you to _first_ join the OpenStack Foundation as an Individual Member (it's free and only takes a minute). People skimming the account setup document often accidentally skip that step and then get confused. Basically you go to https://www.openstack.org/join/ and select the "Foundation
Member" button (not "Community Member"). -- Jeremy Stanley [attachment "signature.asc" deleted by Ying Chun Guo/China/IBM] _______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
From: Akihiro Motoki <amotoki@gmail.com> To: Ying Chun Guo/China/IBM@IBMCN Cc: Jeremy Stanley <fungi@yuggoth.org>, "openstack- i18n@lists.openstack.org" <openstack-i18n@lists.openstack.org> Date: 08/03/2015 06:01 PM Subject: Re: [Openstack-i18n] ATC candidates listing - call for coodinators' action
Hi Daisy,
I am confused with the wiki page you wrote about becoming a new
Akihiro Motoki <amotoki@gmail.com> wrote on 08/03/2015 06:01:10 PM: translator.
The wiki page mentions only Zanata and Transifex is not mentioned.
Should a new translator use Zanata *right now* (and at least for Libetry) for translations? AFAIK, we are still using Transifex. I was ask from a Japanese folk who wants to start translations and advised him to use Transifex. Is it correct or not?
I'm sorry if I make you confused. The plan is to use Zanata for liberty translation. The wiki page describes steps to join I18n team when we use Zanata in the future. So I don't cover Transifex.
What is the official process and suggestions?
If someone has made a work on Transifex from now, can he/she get ATC status if he/she satisfies the requirements? If not, we should announce the situation more clearly to avoid confusion.
The primary goal to get ATC status for translators is to get them a free registration code for Tokyo summit. I have exported statistic data of translators' contributions from *Transifex* . If a translator contributed more than 200 new words translations since 2014.11.1, he is able to get a free code to summit. We don't start to use Zanata officially. So I don't use Zanata data. If you have more questions, please let me know.
I believe I followed almost all discussion in this list, but the situation is still unclear to me.
Akihiro
2015-07-30 17:40 GMT+09:00 Ying Chun Guo <guoyingc@cn.ibm.com>: I write all these down in a wiki page about how to become a translator, please help to improve.
https://wiki.openstack.org/wiki/I18nTeam/become-a-official-translator
Best regards Ying Chun Guo (Daisy)
Jeremy Stanley <fungi@yuggoth.org> wrote on 07/29/2015 09:12:12 PM:
From: Jeremy Stanley <fungi@yuggoth.org> To: openstack-i18n@lists.openstack.org Date: 07/29/2015 09:12 PM Subject: Re: [Openstack-i18n] ATC candidates listing - call for coodinators' action
On 2015-07-29 15:58:15 +0800 (+0800), Ying Chun Guo wrote: [...]
2. Have those ATC candidates to sign the ICLA. "Sign the appropriate Individual Contributor License Agreement" in [2] clearly gives guidance to sign the ICLA. If you meet with any problems, please contact with me. [...]
It's worth noting that this also requires you to _first_ join the OpenStack Foundation as an Individual Member (it's free and only takes a minute). People skimming the account setup document often accidentally skip that step and then get confused. Basically you go to https://www.openstack.org/join/ and select the "Foundation
Member" button (not "Community Member"). -- Jeremy Stanley [attachment "signature.asc" deleted by Ying Chun Guo/China/IBM] _______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
Thanks Daisy, 2015年8月4日火曜日、Ying Chun Guo<guoyingc@cn.ibm.com>さんは書きました:
Akihiro Motoki <amotoki@gmail.com <javascript:_e(%7B%7D,'cvml','amotoki@gmail.com');>> wrote on 08/03/2015 06:01:10 PM:
From: Akihiro Motoki <amotoki@gmail.com <javascript:_e(%7B%7D,'cvml','amotoki@gmail.com');>> To: Ying Chun Guo/China/IBM@IBMCN Cc: Jeremy Stanley <fungi@yuggoth.org <javascript:_e(%7B%7D,'cvml','fungi@yuggoth.org');>>, "openstack- i18n@lists.openstack.org <javascript:_e(%7B%7D,'cvml','i18n@lists.openstack.org');>" < openstack-i18n@lists.openstack.org <javascript:_e(%7B%7D,'cvml','openstack-i18n@lists.openstack.org');>> Date: 08/03/2015 06:01 PM Subject: Re: [Openstack-i18n] ATC candidates listing - call for coodinators' action
Hi Daisy,
I am confused with the wiki page you wrote about becoming a new translator. The wiki page mentions only Zanata and Transifex is not mentioned.
Should a new translator use Zanata *right now* (and at least for Libetry) for translations? AFAIK, we are still using Transifex. I was ask from a Japanese folk who wants to start translations and advised him to use Transifex. Is it correct or not?
I'm sorry if I make you confused. The plan is to use Zanata for liberty translation. The wiki page describes steps to join I18n team when we use Zanata in the future. So I don't cover Transifex.
May I add a note on Transifex, which describes we are still using Transifex atm.
What is the official process and suggestions?
If someone has made a work on Transifex from now, can he/she get ATC status if he/she satisfies the requirements? If not, we should announce the situation more clearly to avoid confusion.
The primary goal to get ATC status for translators is to get them a free registration code for Tokyo summit. I have exported statistic data of translators' contributions from *Transifex* . If a translator contributed more than 200 new words translations since 2014.11.1, he is able to get a free code to summit. We don't start to use Zanata officially. So I don't use Zanata data.
If you have more questions, please let me know.
Are translation activities on Transifex taken into account? I know you downloaded Transifex stats but can we gather the latest stats? Though it might not happen, I think we need to consider the future. What is the period? since 2014 Nov 1 to when? to Liberty release? Thanks,
I believe I followed almost all discussion in this list, but the situation is still unclear to me.
Akihiro
2015-07-30 17:40 GMT+09:00 Ying Chun Guo <guoyingc@cn.ibm.com <javascript:_e(%7B%7D,'cvml','guoyingc@cn.ibm.com');>>: I write all these down in a wiki page about how to become a translator, please help to improve.
https://wiki.openstack.org/wiki/I18nTeam/become-a-official-translator
Best regards Ying Chun Guo (Daisy)
Jeremy Stanley <fungi@yuggoth.org <javascript:_e(%7B%7D,'cvml','fungi@yuggoth.org');>> wrote on 07/29/2015 09:12:12 PM:
From: Jeremy Stanley <fungi@yuggoth.org <javascript:_e(%7B%7D,'cvml','fungi@yuggoth.org');>> To: openstack-i18n@lists.openstack.org <javascript:_e(%7B%7D,'cvml','openstack-i18n@lists.openstack.org');> Date: 07/29/2015 09:12 PM Subject: Re: [Openstack-i18n] ATC candidates listing - call for coodinators' action
On 2015-07-29 15:58:15 +0800 (+0800), Ying Chun Guo wrote: [...]
2. Have those ATC candidates to sign the ICLA. "Sign the appropriate Individual Contributor License Agreement" in [2] clearly gives guidance to sign the ICLA. If you meet with any problems, please contact with me. [...]
It's worth noting that this also requires you to _first_ join the OpenStack Foundation as an Individual Member (it's free and only takes a minute). People skimming the account setup document often accidentally skip that step and then get confused. Basically you go to https://www.openstack.org/join/ and select the "Foundation
Member" button (not "Community Member"). -- Jeremy Stanley [attachment "signature.asc" deleted by Ying Chun Guo/China/IBM] _______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org <javascript:_e(%7B%7D,'cvml','Openstack-i18n@lists.openstack.org');> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org <javascript:_e(%7B%7D,'cvml','Openstack-i18n@lists.openstack.org');> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
From: Akihiro Motoki <amotoki@gmail.com> To: Ying Chun Guo/China/IBM@IBMCN Cc: Jeremy Stanley <fungi@yuggoth.org>, "openstack- i18n@lists.openstack.org" <openstack-i18n@lists.openstack.org> Date: 08/04/2015 08:39 PM Subject: Re: [Openstack-i18n] ATC candidates listing - call for coodinators' action
Thanks Daisy,
2015年8月4日火曜日、Ying Chun Guo<guoyingc@cn.ibm.com>さんは書きました: Akihiro Motoki <amotoki@gmail.com> wrote on 08/03/2015 06:01:10 PM:
From: Akihiro Motoki <amotoki@gmail.com> To: Ying Chun Guo/China/IBM@IBMCN Cc: Jeremy Stanley <fungi@yuggoth.org>, "openstack- i18n@lists.openstack.org" <openstack-i18n@lists.openstack.org> Date: 08/03/2015 06:01 PM Subject: Re: [Openstack-i18n] ATC candidates listing - call for coodinators' action
Hi Daisy,
I am confused with the wiki page you wrote about becoming a new
Akihiro Motoki <amotoki@gmail.com> wrote on 08/04/2015 08:38:50 PM: translator.
The wiki page mentions only Zanata and Transifex is not mentioned.
Should a new translator use Zanata *right now* (and at least for Libetry) for translations? AFAIK, we are still using Transifex. I was ask from a Japanese folk who wants to start translations and advised him to use Transifex. Is it correct or not?
I'm sorry if I make you confused. The plan is to use Zanata for liberty translation. The wiki page describes steps to join I18n team when we use Zanata in the future. So I don't cover Transifex.
May I add a note on Transifex, which describes we are still using Transifex atm.
We probably will use Zanata for Liberty dashboard translation, which will start on September. I don't know you need to emphasis that we are still using Transifex .
What is the official process and suggestions?
If someone has made a work on Transifex from now, can he/she get ATC status if he/she satisfies the requirements? If not, we should announce the situation more clearly to avoid
confusion.
The primary goal to get ATC status for translators is to get them a free registration code for Tokyo summit. I have exported statistic data of translators' contributions from *Transifex* . If a translator contributed more than 200 new words translations since 2014.11.1, he is able to get a free code to summit. We don't start to use Zanata officially. So I don't use Zanata data.
If you have more questions, please let me know.
Are translation activities on Transifex taken into account? I know you downloaded Transifex stats but can we gather the latest stats? Though it might not happen, I think we need to consider the future. What is the period? since 2014 Nov 1 to when? to Liberty release?
In two dev life cycle, people who translate more than 200 words will get a registration code. I just following the similar way with openstack dev teams. 2014 Nov 1 is the date we starting Kilo development. The end date is when I exported the statistic data. Just like,when openstack foundation decide the dev ATC list to distribute their registration codes, the end date is also in the middle of a release. I only calculate the "translate words" this time, the "review words" is not included. Because I'm not able to get the review words from Transifex. In the future, both the translation and review will be take into consideration when calculating contributions. The primary goal to get this ATC list is to get them registration codes for Tokyo summit. There could be more people added to the list in the future. ATC list are not unchanged.
Thanks,
I believe I followed almost all discussion in this list, but the situation is still unclear to me.
Akihiro
2015-07-30 17:40 GMT+09:00 Ying Chun Guo <guoyingc@cn.ibm.com>: I write all these down in a wiki page about how to become a
translator,
please help to improve.
https://wiki.openstack.org/wiki/I18nTeam/become-a-official-translator
Best regards Ying Chun Guo (Daisy)
Jeremy Stanley <fungi@yuggoth.org> wrote on 07/29/2015 09:12:12 PM:
From: Jeremy Stanley <fungi@yuggoth.org> To: openstack-i18n@lists.openstack.org Date: 07/29/2015 09:12 PM Subject: Re: [Openstack-i18n] ATC candidates listing - call for coodinators' action
On 2015-07-29 15:58:15 +0800 (+0800), Ying Chun Guo wrote: [...]
2. Have those ATC candidates to sign the ICLA. "Sign the appropriate Individual Contributor License Agreement" in [2] clearly gives guidance to sign the ICLA. If you meet with any problems, please contact with me. [...]
It's worth noting that this also requires you to _first_ join the OpenStack Foundation as an Individual Member (it's free and only takes a minute). People skimming the account setup document often accidentally skip that step and then get confused. Basically you go to https://www.openstack.org/join/ and select the "Foundation
Member" button (not "Community Member"). -- Jeremy Stanley [attachment "signature.asc" deleted by Ying Chun Guo/China/IBM] _______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
Hi Daisy, Please find my response inline. One important point is a correction on the fact about ATC status, and some comment from my feeling. 2015-08-05 18:15 GMT+09:00 Ying Chun Guo <guoyingc@cn.ibm.com>:
Akihiro Motoki <amotoki@gmail.com> wrote on 08/04/2015 08:38:50 PM:
From: Akihiro Motoki <amotoki@gmail.com> To: Ying Chun Guo/China/IBM@IBMCN Cc: Jeremy Stanley <fungi@yuggoth.org>, "openstack- i18n@lists.openstack.org" <openstack-i18n@lists.openstack.org> Date: 08/04/2015 08:39 PM Subject: Re: [Openstack-i18n] ATC candidates listing - call for coodinators' action
Thanks Daisy,
2015年8月4日火曜日、Ying Chun Guo<guoyingc@cn.ibm.com>さんは書きました: Akihiro Motoki <amotoki@gmail.com> wrote on 08/03/2015 06:01:10 PM:
From: Akihiro Motoki <amotoki@gmail.com> To: Ying Chun Guo/China/IBM@IBMCN Cc: Jeremy Stanley <fungi@yuggoth.org>, "openstack- i18n@lists.openstack.org" <openstack-i18n@lists.openstack.org> Date: 08/03/2015 06:01 PM Subject: Re: [Openstack-i18n] ATC candidates listing - call for coodinators' action
Hi Daisy,
I am confused with the wiki page you wrote about becoming a new translator. The wiki page mentions only Zanata and Transifex is not mentioned.
Should a new translator use Zanata *right now* (and at least for Libetry) for translations? AFAIK, we are still using Transifex. I was ask from a Japanese folk who wants to start translations and advised him to use Transifex. Is it correct or not?
I'm sorry if I make you confused. The plan is to use Zanata for liberty translation. The wiki page describes steps to join I18n team when we use Zanata in the future. So I don't cover Transifex.
May I add a note on Transifex, which describes we are still using Transifex atm.
We probably will use Zanata for Liberty dashboard translation, which will start on September. I don't know you need to emphasis that we are still using Transifex .
Good to know we have Zanata in the next month :-) Thanks for all of your efforts. The reason I asked about Transifex until Zanata migration will be clarified after you read my comments below.
What is the official process and suggestions?
If someone has made a work on Transifex from now, can he/she get ATC status if he/she satisfies the requirements? If not, we should announce the situation more clearly to avoid
confusion.
The primary goal to get ATC status for translators is to get them a free registration code for Tokyo summit. I have exported statistic data of translators' contributions from *Transifex* . If a translator contributed more than 200 new words translations since 2014.11.1, he is able to get a free code to summit. We don't start to use Zanata officially. So I don't use Zanata data.
If you have more questions, please let me know.
Are translation activities on Transifex taken into account? I know you downloaded Transifex stats but can we gather the latest stats? Though it might not happen, I think we need to consider the future. What is the period? since 2014 Nov 1 to when? to Liberty release?
In two dev life cycle, people who translate more than 200 words will get a registration code. I just following the similar way with openstack dev teams. 2014 Nov 1 is the date we starting Kilo development. The end date is when I exported the statistic data.
Just like,when openstack foundation decide the dev ATC list to distribute their registration codes, the end date is also in the middle of a release.
I think this is the point you misunderstand. It is not what really happens. I would like to explain two points I think you misunderstand: - When ATC registration codes are sent? - ATC status definition itself. [When ATC registration codes are sent?] The foundation sends registration codes for folks with ATC status multiple times. The first mail is usually sent at the middle of the release, but that's not all. The foundation updates their ATC list periodically and send registration codes for newly added ATC until the dev cycle finished. (AFAIK, we have two or three extra rounds.) As a a result, all developers [ATC status definition] ATC status was previously given to contributors in the past two release cycle, but AFAIK from Vancouver Summit it was changed and contributor in the last one release cycle can get ATC status. Though I don't have the original definition at the moment, it is what Stefano answered at ask.openstack.org [1], so I believe it is the latest and reliable information. [1] https://ask.openstack.org/en/question/45531/atc-pass-for-the-openstack-summi... I only calculate the "translate words" this time, the "review words" is not
included. Because I'm not able to get the review words from Transifex. In the future, both the translation and review will be take into consideration when calculating contributions.
The primary goal to get this ATC list is to get them registration codes for Tokyo summit. There could be more people added to the list in the future. ATC list are not unchanged.
The first point is the main reason that I am asking in this thread. I would like to clarify what are different from the usual process and what we can if we follow the normal ATC definition. The actual definition of ATC for normal (non-I18n) contributors are as described above, but we are in a special stage and we may be able to have a bit different definition. If so, it is better to announce how it is different from the normal ATC definition. I am not sure how many such folks we have from now on, so IMHO we don't need to update the translation status from Transifex. If someone claims his/her ATC status based on a stats we haven't covered, we can and should coordinate his/her ATC status with the foundation. # If we don't have any requests, we can close Transifex translation and # force all translators to wait Zanata migration. I hope this discussion helps us. Thanks, Akihiro
Thanks,
I believe I followed almost all discussion in this list, but the situation is still unclear to me.
Akihiro
2015-07-30 17:40 GMT+09:00 Ying Chun Guo <guoyingc@cn.ibm.com>: I write all these down in a wiki page about how to become a
translator,
please help to improve.
https://wiki.openstack.org/wiki/I18nTeam/become-a-official-translator
Best regards Ying Chun Guo (Daisy)
Jeremy Stanley <fungi@yuggoth.org> wrote on 07/29/2015 09:12:12 PM:
From: Jeremy Stanley <fungi@yuggoth.org> To: openstack-i18n@lists.openstack.org Date: 07/29/2015 09:12 PM Subject: Re: [Openstack-i18n] ATC candidates listing - call for coodinators' action
On 2015-07-29 15:58:15 +0800 (+0800), Ying Chun Guo wrote: [...]
2. Have those ATC candidates to sign the ICLA. "Sign the appropriate Individual Contributor License Agreement" in [2] clearly gives guidance to sign the ICLA. If you meet with any problems, please contact with me. [...]
It's worth noting that this also requires you to _first_ join the OpenStack Foundation as an Individual Member (it's free and only takes a minute). People skimming the account setup document often accidentally skip that step and then get confused. Basically you go to https://www.openstack.org/join/ and select the "Foundation
Member" button (not "Community Member"). -- Jeremy Stanley [attachment "signature.asc" deleted by Ying Chun Guo/China/IBM] _______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
On 2015-08-06 23:01:27 +0900 (+0900), Akihiro Motoki wrote: [...]
[ATC status definition] ATC status was previously given to contributors in the past two release cycle, but AFAIK from Vancouver Summit it was changed and contributor in the last one release cycle can get ATC status. Though I don't have the original definition at the moment, it is what Stefano answered at ask.openstack.org, so I believe it is the latest and reliable information. [...]
It's best not to conflate "ATC" (legally defined in appendix 4 part 3.b of the foundation bylaws[1] used for determining voter rolls in technical elections) with complimentary discount codes sent to contributors (requirements for which are determined by the event organizers on the foundation staff and vary from cycle to cycle). For the Mitaka summit we're inviting contributors who have been involved since Kilo release day (April 30, 2015) as decided by the staff of the OpenStack Foundation based on criteria for available design summit space, logistics and supporting budget. Exceptions can be requested from summitreg@openstack.org or via TC resolution adding specific contributors to the "extra ATCs" list[2][3] (since contributors on that list receive summit discount codes automatically regardless of how recent their code contributions are). [1] http://www.openstack.org/legal/technical-committee-member-policy/ [2] http://git.openstack.org/cgit/openstack/governance/tree/reference/extra-atcs [3] http://governance.openstack.org/reference/projects/i18n.html#extra-atcs -- Jeremy Stanley
Hi all, I'm going to attempt to add some information here - hopefully I won't make it worse. On 06/08/15 19:31, Akihiro Motoki wrote:
The first point is the main reason that I am asking in this thread. I would like to clarify what are different from the usual process and what we can if we follow the normal ATC definition.
The actual definition of ATC for normal (non-I18n) contributors are as described above, but we are in a special stage and we may be able to have a bit different definition. If so, it is better to announce how it is different from the normal ATC definition.
As Motoki san notes, what we're doing at the moment is 'special'. Why? Normally, ATC status is automatically determined - by having a commit in a repository. We are able to easily check using our existing tooling. Our Transifex workflow does not allow for this 'easy', or 'standard' way. Our Zanata tooling in the future should be able to do this. However, we are in transition and do not yet have this working yet. Despite this, we still want to be able to recognize the hard work of our translators: they have waited long enough. Thankfully, the governance of the Technical Committee provides another way, so called: "Exceptional ATC Status". "Exceptional ATC Status" was designed so that important contributors who couldn't get ATC through the 'standard' way could still be recognised. It's not uncommon, and a current list of people with such status can be found here: https://github.com/openstack/governance/blob/master/reference/extra-atcs . "Exceptional" refers to the method of acquiring the status - the status itself has the same rights :) The reason we are collecting the lists is to submit an "Exceptional ATC Status" request on behalf of the translators. As per http://governance.openstack.org/reference/charter.html#voters-for-tc-seats-a... , we will send "an email to the TC chair". Given current progress on Zanata, we should only have to do this once, but it should assist with getting some ATC labels on badges in Tokyo :) Regards, Tom
Thank you for the explain, Tom. The patch to openstack governance is submitted. Again, the patch is just a temporary way for us to get discount codes and vote right. We will figure out an automatic way after we formally move to Zanata. @ team, please help to review. https://review.openstack.org/#/c/213989/ Best regards Ying Chun Guo (Daisy) Tom Fifield <tom@openstack.org> wrote on 08/07/2015 01:42:00 PM:
From: Tom Fifield <tom@openstack.org> To: openstack-i18n@lists.openstack.org Date: 08/07/2015 01:42 PM Subject: Re: [Openstack-i18n] ATC candidates listing - call for coodinators' action
Hi all,
I'm going to attempt to add some information here - hopefully I won't make it worse.
On 06/08/15 19:31, Akihiro Motoki wrote:
The first point is the main reason that I am asking in this thread. I would like to clarify what are different from the usual process and what we can if we follow the normal ATC definition.
The actual definition of ATC for normal (non-I18n) contributors are as described above, but we are in a special stage and we may be able to have a bit different definition. If so, it is better to announce how it is different from the normal ATC definition.
As Motoki san notes, what we're doing at the moment is 'special'.
Why?
Normally, ATC status is automatically determined - by having a commit in
a repository. We are able to easily check using our existing tooling.
Our Transifex workflow does not allow for this 'easy', or 'standard' way. Our Zanata tooling in the future should be able to do this.
However, we are in transition and do not yet have this working yet. Despite this, we still want to be able to recognize the hard work of our
translators: they have waited long enough.
Thankfully, the governance of the Technical Committee provides another way, so called: "Exceptional ATC Status".
"Exceptional ATC Status" was designed so that important contributors who
couldn't get ATC through the 'standard' way could still be recognised. It's not uncommon, and a current list of people with such status can be found here: https://github.com/openstack/governance/blob/master/reference/extra-atcs
. "Exceptional" refers to the method of acquiring the status - the status itself has the same rights :)
The reason we are collecting the lists is to submit an "Exceptional ATC Status" request on behalf of the translators. As per
http://governance.openstack.org/reference/charter.html#voters-for-tc-seats-a...
, we will send "an email to the TC chair".
Given current progress on Zanata, we should only have to do this once, but it should assist with getting some ATC labels on badges in Tokyo :)
Regards,
Tom
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
It's a reminder. I have gotten inputs from French, Japanese, Korean, Spanish team. If you or your team members want to get ATC codes for Tokyo summit, please input before August 15th. Best regards Ying Chun Guo (Daisy) Ying Chun Guo/China/IBM@IBMCN wrote on 07/29/2015 03:58:15 PM:
From: Ying Chun Guo/China/IBM@IBMCN To: openstack-i18n@lists.openstack.org Date: 07/29/2015 03:59 PM Subject: Re: [Openstack-i18n] ATC candidates listing - call for coodinators' action
Dear coordinators,
We are starting the process to get active translators free "ATC" registration codes for Tokyo summit. I need your help to finish below two items in order to get "ATC" codes for them.
1. Collect the email+name pairs for those ATC candidates [1]. I have exported the translators contribution statistics from Transifex since 2014.11.1 to 2015.7.16. Please collect email+name of those translators who has translated more than 200 words, and fill in the table. KATO Tomoyuki has finished the collection of Japanese team. You could use his input as a reference.
2. Have those ATC candidates to sign the ICLA. "Sign the appropriate Individual Contributor License Agreement" in [2] clearly gives guidance to sign the ICLA. If you meet with any problems, please contact with me.
I hope we could finish these steps before August 15th. Thus we might have enough time to run through the remained process.
When you have done your work, send an email to me. Thank you.
Best regards Ying Chun Guo (Daisy)
[1] https://docs.google.com/spreadsheets/d/ 1YpDJU_uNA4I5fzFG69T6L9gpFsy5yNtA9a-lSxnqeAY/edit#gid=1366189722 [2] http://docs.openstack.org/infra/manual/developers.html#account-setup
KATO Tomoyuki <tomo@dream.daynight.jp> wrote on 07/26/2015 09:14:14 PM:
From: KATO Tomoyuki <tomo@dream.daynight.jp> To: openstack-i18n@lists.openstack.org Date: 07/26/2015 09:14 PM Subject: [Openstack-i18n] ATC candidates listing
Hi Daisy,
Action item from last meeting. Japanese team finished ATC candidates listing.
Thanks, KATO Tomoyuki
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n _______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
Hi Daisy, FYI, working on this for the German team. Also see my direct mail to you. -- Thanks, Robert On Wednesday 05 August 2015, 16:08:56 Ying Chun Guo <guoyingc@cn.ibm.com> wrote:
It's a reminder. I have gotten inputs from French, Japanese, Korean, Spanish team. If you or your team members want to get ATC codes for Tokyo summit, please input before August 15th.
Best regards Ying Chun Guo (Daisy)
Ying Chun Guo/China/IBM@IBMCN wrote on 07/29/2015 03:58:15 PM:
From: Ying Chun Guo/China/IBM@IBMCN To: openstack-i18n@lists.openstack.org Date: 07/29/2015 03:59 PM Subject: Re: [Openstack-i18n] ATC candidates listing - call for coodinators' action
Dear coordinators,
We are starting the process to get active translators free "ATC" registration codes for Tokyo summit. I need your help to finish below two items in order to get "ATC" codes for them.
1. Collect the email+name pairs for those ATC candidates [1]. I have exported the translators contribution statistics from Transifex since 2014.11.1 to 2015.7.16. Please collect email+name of those translators who has translated more than 200 words, and fill in the table. KATO Tomoyuki has finished the collection of Japanese team. You could use his input as a reference.
2. Have those ATC candidates to sign the ICLA. "Sign the appropriate Individual Contributor License Agreement" in [2] clearly gives guidance to sign the ICLA. If you meet with any problems, please contact with me.
I hope we could finish these steps before August 15th. Thus we might have enough time to run through the remained process.
When you have done your work, send an email to me. Thank you.
Best regards Ying Chun Guo (Daisy)
[1] https://docs.google.com/spreadsheets/d/ 1YpDJU_uNA4I5fzFG69T6L9gpFsy5yNtA9a-lSxnqeAY/edit#gid=1366189722 [2] http://docs.openstack.org/infra/manual/developers.html#account-setup
KATO Tomoyuki <tomo@dream.daynight.jp> wrote on 07/26/2015 09:14:14 PM:
From: KATO Tomoyuki <tomo@dream.daynight.jp> To: openstack-i18n@lists.openstack.org Date: 07/26/2015 09:14 PM Subject: [Openstack-i18n] ATC candidates listing
Hi Daisy,
Action item from last meeting. Japanese team finished ATC candidates listing.
Thanks, KATO Tomoyuki
_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n _______________________________________________
Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
participants (7)
-
Akihiro Motoki
-
Francois Bureau
-
Jeremy Stanley
-
KATO Tomoyuki
-
Robert Simai
-
Tom Fifield
-
Ying Chun Guo