[OpenStack-I18n] Fwd: [openstack-dev] [all][ptl][tc] extra ATCs for newton
amotoki at gmail.com
Fri Aug 12 05:04:48 UTC 2016
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
IMHO it must be improved.
2016-08-12 9:00 GMT+09:00 Kato, Tomoyuki <kato.tomoyuki at jp.fujitsu.com>:
> Hi Akihiro,
> Unfortunately, automation activity is on-going.
> Therefore, our ATC process in Newton is the same way as Mitaka.
> 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.
>> ---------- Forwarded message ----------
>> From: Doug Hellmann <doug at 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 at 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  and TC Charter , 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.
>>  http://www.openstack.org/legal/technical-committee-member-policy/
>>  http://governance.openstack.org/reference/charter.html#voters-for-tc-seats-atc
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> OpenStack-I18n mailing list
>> OpenStack-I18n at lists.openstack.org
> OpenStack-I18n mailing list
> OpenStack-I18n at lists.openstack.org
More information about the OpenStack-I18n