<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Thu, Aug 11, 2016 at 7:38 AM, Doug Hellmann <span dir="ltr"><<a href="mailto:doug@doughellmann.com" target="_blank">doug@doughellmann.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Excerpts from Michael Still's message of 2016-08-11 07:27:07 +1000:<br>
<div><div class="h5">> On Thu, Aug 11, 2016 at 7:12 AM, Doug Hellmann <<a href="mailto:doug@doughellmann.com">doug@doughellmann.com</a>><br>
> wrote:<br>
><br>
> > Excerpts from Michael Still's message of 2016-08-11 07:01:37 +1000:<br>
> > > On Thu, Aug 11, 2016 at 2:24 AM, Doug Hellmann <<a href="mailto:doug@doughellmann.com">doug@doughellmann.com</a>><br>
> > > wrote:<br>
> > ><br>
> > > > It's time to make sure we have all of our active technical contributors<br>
> > > > (ATCs) identified for Newton.<br>
> > > ><br>
> > > > Following the Foundation bylaws [1] and TC Charter [2], Project<br>
> > > > teams should identify contributors who have had a significant impact<br>
> > > > this cycle but who would not qualify for ATC status using the regular<br>
> > > > process because they have not submitted a patch. Contributions<br>
> > > > might include, but aren't limited to, bug triage, design work, and<br>
> > > > documentation -- there is a lot of leeway in how teams define<br>
> > > > contribution for ATC status.<br>
> > > ><br>
> > > > The resulting list of names should be submitted as a patch to the<br>
> > > > "extra-atcs" section in openstack/governance/<wbr>reference/projects.yaml<br>
> > > > for review by the TC.<br>
> > > ><br>
> > > > Although extra ATCs can be nominated at any point, there is a<br>
> > > > deadline to be included in the electorate for the next release<br>
> > > > cycle. The ATC list needs to be approved by the TC by 25 Aug, and<br>
> > > > in order to appear on the TC agenda to be discussed, the proposals<br>
> > > > need to be submitted by 16 Aug.<br>
> > > ><br>
> > > > PTLs can delegate preparing the patch to the governance repository, but<br>
> > > > please +1 the patch indicating that you agree with the list to avoid<br>
> > > > delays in the TC review.<br>
> > > ><br>
> > ><br>
> > > I have a script to generate this that I wrote while Nova PTL. For<br>
> > example:<br>
> > ><br>
> > > ~/src/openstack/nova$ /home/mikal/src/mikalstill/<br>
> > hacks/tools/extra-atcs.py<br>
> > > --since=2016-04-01 --expires="September 2017" --program "Compute"<br>
> ><br>
> > What data is that pulling?<br>
> ><br>
><br>
> It is parsing the git commit log for examples of "Co-authored-by" entries,<br>
> and filtering away those where the person also has a primary commit. IIRC<br>
> last time I did this for real I needed to check that each person was also a<br>
> foundation member, but that was manual as there was no API at the time.<br>
<br>
</div></div>Nice, that sounds like it would be useful to more teams.</blockquote><div><br></div><div>At the time I proposed it for the tools directory in the governance repo, but it never actually landed. The code is at if people want to borrow. Consider it under the Apache license.</div><div><br></div><div>Michael </div></div><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">Rackspace Australia</div>
</div></div>