[openstack-dev] [all][ptl][tc] extra ATCs for newton

Doug Hellmann doug at doughellmann.com
Wed Aug 10 21:38:54 UTC 2016


Excerpts from Michael Still's message of 2016-08-11 07:27:07 +1000:
> On Thu, Aug 11, 2016 at 7:12 AM, Doug Hellmann <doug at doughellmann.com>
> wrote:
> 
> > Excerpts from Michael Still's message of 2016-08-11 07:01:37 +1000:
> > > On Thu, Aug 11, 2016 at 2:24 AM, Doug Hellmann <doug at doughellmann.com>
> > > wrote:
> > >
> > > > 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.
> > > >
> > >
> > > I have a script to generate this that I wrote while Nova PTL. For
> > example:
> > >
> > > ~/src/openstack/nova$ /home/mikal/src/mikalstill/
> > hacks/tools/extra-atcs.py
> > > --since=2016-04-01 --expires="September 2017" --program "Compute"
> >
> > What data is that pulling?
> >
> 
> It is parsing the git commit log for examples of "Co-authored-by" entries,
> and filtering away those where the person also has a primary commit. IIRC
> last time I did this for real I needed to check that each person was also a
> foundation member, but that was manual as there was no API at the time.

Nice, that sounds like it would be useful to more teams.

Doug

> 
> > > Compute: Sonu (sonu.sudhakaran at gmail.com) [September 2017]
> > > Compute: Ahilan Rajadeva (rajadeva at us.ibm.com) [September 2017]
> > > Compute: Qiaowei Ren (qiaowei.ren at intel.com) [September 2017]
> > > Compute: Xiaowei Qian (xiaowei.qian at easystack.cn) [September 2017]
> > > Compute: Alin Balutoiu (abalutoiu at cloudbasesolutions.com) [September
> > 2017]
> > > Compute: Eli Qiao (qiaoliyong at gmail.com) [September 2017]
> > > Compute: Feodor Tersin (ftersin at hotmail.com) [September 2017]
> > > Compute: Samuel Matzek (smatzek at us.ibm.com) [September 2017]
> > > Compute: Raghuveer Shenoy (rshenoy at hp.com) [September 2017]
> > > Compute: Bartosz Fic (bartosz.fic at intel.com) [September 2017]
> > > Compute: Dmitry Guryanov (dguryanov at parallels.com) [September 2017]
> >
> > The format is different now (it goes in the YAML file instead of
> > stand-alone) but the data is the same so it should be easy to adapt the
> > output.
> >
> > Doug
> >
> > >
> > > Matt -- if that's useful feel free to base a governance review on it.
> >
> 
> Michael
> 



More information about the OpenStack-dev mailing list