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