Fwd: [openstack-dev] [all][ptl][tc] extra ATCs for newton
Forwarded to i18n list. My big question is what is our ATC process in Newton. I think everyone has the same question. IIRC, an effort to track translator activity automatically is on-going, but I don't know the current status. I believe it should be announced officially. Akihiro ---------- Forwarded message ---------- From: Doug Hellmann <doug@doughellmann.com> Date: 2016-08-11 1:24 GMT+09:00 Subject: [openstack-dev] [all][ptl][tc] extra ATCs for newton To: openstack-dev <openstack-dev@lists.openstack.org> It's time to make sure we have all of our active technical contributors (ATCs) identified for Newton. Following the Foundation bylaws [1] and TC Charter [2], Project teams should identify contributors who have had a significant impact this cycle but who would not qualify for ATC status using the regular process because they have not submitted a patch. Contributions might include, but aren't limited to, bug triage, design work, and documentation -- there is a lot of leeway in how teams define contribution for ATC status. The resulting list of names should be submitted as a patch to the "extra-atcs" section in openstack/governance/reference/projects.yaml for review by the TC. Although extra ATCs can be nominated at any point, there is a deadline to be included in the electorate for the next release cycle. The ATC list needs to be approved by the TC by 25 Aug, and in order to appear on the TC agenda to be discussed, the proposals need to be submitted by 16 Aug. PTLs can delegate preparing the patch to the governance repository, but please +1 the patch indicating that you agree with the list to avoid delays in the TC review. Thanks, Doug [1] http://www.openstack.org/legal/technical-committee-member-policy/ [2] http://governance.openstack.org/reference/charter.html#voters-for-tc-seats-a... __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Hi Akihiro, Unfortunately, automation activity is on-going. Therefore, our ATC process in Newton is the same way as Mitaka. https://review.openstack.org/#/c/351480/ Thanks, KATO Tomoyuki
Forwarded to i18n list.
My big question is what is our ATC process in Newton. I think everyone has the same question. IIRC, an effort to track translator activity automatically is on-going, but I don't know the current status. I believe it should be announced officially.
Akihiro
---------- Forwarded message ---------- From: Doug Hellmann <doug@doughellmann.com> Date: 2016-08-11 1:24 GMT+09:00 Subject: [openstack-dev] [all][ptl][tc] extra ATCs for newton To: openstack-dev <openstack-dev@lists.openstack.org>
It's time to make sure we have all of our active technical contributors (ATCs) identified for Newton.
Following the Foundation bylaws [1] and TC Charter [2], Project teams should identify contributors who have had a significant impact this cycle but who would not qualify for ATC status using the regular process because they have not submitted a patch. Contributions might include, but aren't limited to, bug triage, design work, and documentation -- there is a lot of leeway in how teams define contribution for ATC status.
The resulting list of names should be submitted as a patch to the "extra-atcs" section in openstack/governance/reference/projects.yaml for review by the TC.
Although extra ATCs can be nominated at any point, there is a deadline to be included in the electorate for the next release cycle. The ATC list needs to be approved by the TC by 25 Aug, and in order to appear on the TC agenda to be discussed, the proposals need to be submitted by 16 Aug.
PTLs can delegate preparing the patch to the governance repository, but please +1 the patch indicating that you agree with the list to avoid delays in the TC review.
Thanks, Doug
[1] http://www.openstack.org/legal/technical-committee-member-policy/ [2] http://governance.openstack.org/reference/charter.html#voters-for-tc-seats-a...
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________ OpenStack-I18n mailing list OpenStack-I18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
Hi, I understand the current situation, but it is better to announce the official policy to be acknowledged as ATC. We have the criteria (# of translated words) but it is not clear when is the deadline. As one translator, I always feel the deadline is suddenly cut without no announcement. IMHO it must be improved. Akihiro 2016-08-12 9:00 GMT+09:00 Kato, Tomoyuki <kato.tomoyuki@jp.fujitsu.com>:
Hi Akihiro,
Unfortunately, automation activity is on-going. Therefore, our ATC process in Newton is the same way as Mitaka.
https://review.openstack.org/#/c/351480/
Thanks, KATO Tomoyuki
Forwarded to i18n list.
My big question is what is our ATC process in Newton. I think everyone has the same question. IIRC, an effort to track translator activity automatically is on-going, but I don't know the current status. I believe it should be announced officially.
Akihiro
---------- Forwarded message ---------- From: Doug Hellmann <doug@doughellmann.com> Date: 2016-08-11 1:24 GMT+09:00 Subject: [openstack-dev] [all][ptl][tc] extra ATCs for newton To: openstack-dev <openstack-dev@lists.openstack.org>
It's time to make sure we have all of our active technical contributors (ATCs) identified for Newton.
Following the Foundation bylaws [1] and TC Charter [2], Project teams should identify contributors who have had a significant impact this cycle but who would not qualify for ATC status using the regular process because they have not submitted a patch. Contributions might include, but aren't limited to, bug triage, design work, and documentation -- there is a lot of leeway in how teams define contribution for ATC status.
The resulting list of names should be submitted as a patch to the "extra-atcs" section in openstack/governance/reference/projects.yaml for review by the TC.
Although extra ATCs can be nominated at any point, there is a deadline to be included in the electorate for the next release cycle. The ATC list needs to be approved by the TC by 25 Aug, and in order to appear on the TC agenda to be discussed, the proposals need to be submitted by 16 Aug.
PTLs can delegate preparing the patch to the governance repository, but please +1 the patch indicating that you agree with the list to avoid delays in the TC review.
Thanks, Doug
[1] http://www.openstack.org/legal/technical-committee-member-policy/ [2] http://governance.openstack.org/reference/charter.html#voters-for-tc-seats-a...
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________ 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
I believe we are waiting for Zanata upgrade to have this process automated (API for getting list of contributors). Kato, Do we know the status of getting Zanata upgrade? --------------------------------------------- Alex Eng Senior Software Engineer Globalisation Tools Engineering DID: +61 3514 8262 <callto:+61+3514+8262> Mobile: +614 2335 3457 <callto:+614+2335+3457> Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office: +61 7 3514 8100 <callto:+61+7+3514+8100> Fax: +61 7 3514 8199 <callto:+61+7+3514+8199> Website: www.redhat.com On Fri, Aug 12, 2016 at 3:04 PM, Akihiro Motoki <amotoki@gmail.com> wrote:
Hi,
I understand the current situation, but it is better to announce the official policy to be acknowledged as ATC. We have the criteria (# of translated words) but it is not clear when is the deadline. As one translator, I always feel the deadline is suddenly cut without no announcement. IMHO it must be improved.
Akihiro
2016-08-12 9:00 GMT+09:00 Kato, Tomoyuki <kato.tomoyuki@jp.fujitsu.com>:
Hi Akihiro,
Unfortunately, automation activity is on-going. Therefore, our ATC process in Newton is the same way as Mitaka.
https://review.openstack.org/#/c/351480/
Thanks, KATO Tomoyuki
Forwarded to i18n list.
My big question is what is our ATC process in Newton. I think everyone has the same question. IIRC, an effort to track translator activity automatically is on-going, but I don't know the current status. I believe it should be announced officially.
Akihiro
---------- Forwarded message ---------- From: Doug Hellmann <doug@doughellmann.com> Date: 2016-08-11 1:24 GMT+09:00 Subject: [openstack-dev] [all][ptl][tc] extra ATCs for newton To: openstack-dev <openstack-dev@lists.openstack.org>
It's time to make sure we have all of our active technical contributors (ATCs) identified for Newton.
Following the Foundation bylaws [1] and TC Charter [2], Project teams should identify contributors who have had a significant impact this cycle but who would not qualify for ATC status using the regular process because they have not submitted a patch. Contributions might include, but aren't limited to, bug triage, design work, and documentation -- there is a lot of leeway in how teams define contribution for ATC status.
The resulting list of names should be submitted as a patch to the "extra-atcs" section in openstack/governance/reference/projects.yaml for review by the TC.
Although extra ATCs can be nominated at any point, there is a deadline to be included in the electorate for the next release cycle. The ATC list needs to be approved by the TC by 25 Aug, and in order to appear on the TC agenda to be discussed, the proposals need to be submitted by 16 Aug.
PTLs can delegate preparing the patch to the governance repository, but please +1 the patch indicating that you agree with the list to avoid delays in the TC review.
Thanks, Doug
[1] http://www.openstack.org/legal/technical-committee-member-policy/ [2] http://governance.openstack.org/reference/charter.html# voters-for-tc-seats-atc
____________________________________________________________
OpenStack Development Mailing List (not for usage questions) Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject: unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________ 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
_______________________________________________ OpenStack-I18n mailing list OpenStack-I18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
I believe we are waiting for Zanata upgrade to have this process automated (API for getting list of contributors).
Kato, Do we know the status of getting Zanata upgrade?
Hi Alex, I don't know the status. However, I think Zanata upgrade helps the situation. Kato
Hello, Actually I do not know too much on Zanata upgrade details, but IIRC, upgrading to Ubuntu 16.04 (xenial) in openstack-infra was one of obstacles for Zanata upgrade [1]. May be we first need to upgrade to the running operating system to xenial? Since now lots of Jenkins jobs are with xenial, so I think it is a good timing to upgrade first OS and Zanata on translate-dev.o.o. Or are there other possible obstacles? [1] https://etherpad.openstack.org/p/austin-i18n-workshop With many thanks, /Ian Kato, Tomoyuki wrote on 8/12/2016 2:58 PM:
I believe we are waiting for Zanata upgrade to have this process automated (API for getting list of contributors).
Kato, Do we know the status of getting Zanata upgrade? Hi Alex, I don't know the status. However, I think Zanata upgrade helps the situation.
Kato
_______________________________________________ OpenStack-I18n mailing list OpenStack-I18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
Actually I do not know too much on Zanata upgrade details, but IIRC, upgrading to Ubuntu 16.04 (xenial) in openstack-infra was one of obstacles for Zanata upgrade [1].
Yes. It was the blocker for upgrading Zanata and I believe infra team is working on it. Just need to get updates from them On Fri, Aug 12, 2016 at 11:36 PM, Ian Y. Choi <ianyrchoi@gmail.com> wrote:
Hello,
Actually I do not know too much on Zanata upgrade details, but IIRC, upgrading to Ubuntu 16.04 (xenial) in openstack-infra was one of obstacles for Zanata upgrade [1].
May be we first need to upgrade to the running operating system to xenial? Since now lots of Jenkins jobs are with xenial, so I think it is a good timing to upgrade first OS and Zanata on translate-dev.o.o.
Or are there other possible obstacles?
[1] https://etherpad.openstack.org/p/austin-i18n-workshop
With many thanks,
/Ian
Kato, Tomoyuki wrote on 8/12/2016 2:58 PM:
I believe we are waiting for Zanata upgrade to have this process
automated (API for getting list of contributors).
Kato, Do we know the status of getting Zanata upgrade?
Hi Alex, I don't know the status. However, I think Zanata upgrade helps the situation.
Kato
_______________________________________________ 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
-- Alex Eng
Hello Alex, Alex Eng wrote on 8/13/2016 8:50 AM:
Actually I do not know too much on Zanata upgrade details, but IIRC, upgrading to Ubuntu 16.04 (xenial) in openstack-infra was one of obstacles for Zanata upgrade [1].
Yes. It was the blocker for upgrading Zanata and I believe infra team is working on it. Just need to get updates from them
Yep! Right, infra team is working. I met Elizabeth on IRC, but unfortunately she said "things are not help up, as infra team tries to find time to update our puppet manifests to support Xenial". I thought that upgrading to xenial would be easy since some test nodes (e.g., Jenkins) are with xenial, but the reality seems to be a little bit harder. She said long-lived servers (e.g., translate, translate-dev) are not using the same tooling as test nodes, and tools (e.g., exim) give errors on xenial when she checked last time. [1] http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra... With many thanks, /Ian
On Fri, Aug 12, 2016 at 11:36 PM, Ian Y. Choi <ianyrchoi@gmail.com <mailto:ianyrchoi@gmail.com>> wrote:
Hello,
Actually I do not know too much on Zanata upgrade details, but IIRC, upgrading to Ubuntu 16.04 (xenial) in openstack-infra was one of obstacles for Zanata upgrade [1].
May be we first need to upgrade to the running operating system to xenial? Since now lots of Jenkins jobs are with xenial, so I think it is a good timing to upgrade first OS and Zanata on translate-dev.o.o.
Or are there other possible obstacles?
[1] https://etherpad.openstack.org/p/austin-i18n-workshop <https://etherpad.openstack.org/p/austin-i18n-workshop>
With many thanks,
/Ian
Kato, Tomoyuki wrote on 8/12/2016 2:58 PM:
I believe we are waiting for Zanata upgrade to have this process automated (API for getting list of contributors).
Kato, Do we know the status of getting Zanata upgrade?
Hi Alex, I don't know the status. However, I think Zanata upgrade helps the situation.
Kato
_______________________________________________ OpenStack-I18n mailing list OpenStack-I18n@lists.openstack.org <mailto:OpenStack-I18n@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n>
_______________________________________________ OpenStack-I18n mailing list OpenStack-I18n@lists.openstack.org <mailto:OpenStack-I18n@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n>
-- Alex Eng
2016-08-12 6:04 GMT+01:00 Akihiro Motoki <amotoki@gmail.com>:
Hi,
I understand the current situation, but it is better to announce the official policy to be acknowledged as ATC. We have the criteria (# of translated words) but it is not clear when is the deadline. As one translator, I always feel the deadline is suddenly cut without no announcement. IMHO it must be improved.
Akihiro
2016-08-12 9:00 GMT+09:00 Kato, Tomoyuki <kato.tomoyuki@jp.fujitsu.com>:
Hi Akihiro,
Unfortunately, automation activity is on-going. Therefore, our ATC process in Newton is the same way as Mitaka.
https://review.openstack.org/#/c/351480/
Thanks, KATO Tomoyuki
Forwarded to i18n list.
My big question is what is our ATC process in Newton. I think everyone has the same question. IIRC, an effort to track translator activity automatically is on-going, but I don't know the current status. I believe it should be announced officially.
/FYI/ I just noticed that the deadline of extra ATC is defined in the release schedule. http://releases.openstack.org/newton/schedule.html#n-extra-atcs is for Newton and we will have similar one for Ocata as well.
Akihiro
---------- Forwarded message ---------- From: Doug Hellmann <doug@doughellmann.com> Date: 2016-08-11 1:24 GMT+09:00 Subject: [openstack-dev] [all][ptl][tc] extra ATCs for newton To: openstack-dev <openstack-dev@lists.openstack.org>
It's time to make sure we have all of our active technical contributors (ATCs) identified for Newton.
Following the Foundation bylaws [1] and TC Charter [2], Project teams should identify contributors who have had a significant impact this cycle but who would not qualify for ATC status using the regular process because they have not submitted a patch. Contributions might include, but aren't limited to, bug triage, design work, and documentation -- there is a lot of leeway in how teams define contribution for ATC status.
The resulting list of names should be submitted as a patch to the "extra-atcs" section in openstack/governance/reference/projects.yaml for review by the TC.
Although extra ATCs can be nominated at any point, there is a deadline to be included in the electorate for the next release cycle. The ATC list needs to be approved by the TC by 25 Aug, and in order to appear on the TC agenda to be discussed, the proposals need to be submitted by 16 Aug.
PTLs can delegate preparing the patch to the governance repository, but please +1 the patch indicating that you agree with the list to avoid delays in the TC review.
Thanks, Doug
[1] http://www.openstack.org/legal/technical-committee-member-policy/ [2] http://governance.openstack.org/reference/charter.html#voters-for-tc-seats-a...
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________ 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 (5)
-
Akihiro Motoki
-
Alex Eng
-
Alex Eng
-
Ian Y. Choi
-
Kato, Tomoyuki