<div dir="ltr"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span class="">> Secondly, it's difficult to get stack-analytics credit for back<br></span><span class="">> ports, as the preferred method is to cherry pick the code, and<br></span><span class="">> that keeps the original author's name. I've personally gotten a<br></span><span class="">> few commits into stable, but have nothing to show for it in<br></span><span class="">> stack-analytics (if I'm doing it wrong, I'm happy to be<br></span><span class="">> corrected).<br></span>[...]<br>Stackalytics isn't an official OpenStack project, but you should<br>file a bug[2] against it if there's a feature you want its authors<br>to consider adding.</blockquote><div class="gmail_extra"><br></div><div class="gmail_extra">Stackalytics tracks commits into stable branches, e.g. for Neutron stable/juno they are visible at <a href="http://stackalytics.com/?metric=commits&module=neutron&release=juno">http://stackalytics.com/?metric=commits&module=neutron&release=juno</a>. Commits are also shown in activity log for specific project or person, so if someone interested in pulling them into weekly report - they will be there.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Thanks,</div><div class="gmail_extra">Ilya</div><div class="gmail_extra"><br><div class="gmail_quote">2015-02-10 19:45 GMT+03:00 Jeremy Stanley <span dir="ltr"><<a href="mailto:fungi@yuggoth.org" target="_blank">fungi@yuggoth.org</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">On 2015-02-10 15:20:46 +0000 (+0000), Kevin Bringard (kevinbri) wrote:<br>
[...]<br>
<span class="">> I've been talking with a few people about this very thing lately,<br>
> and I think much of it is caused by what appears to be our<br>
> actively discouraging people from working on it. Most notably, ATC<br>
> is only being given to folks committing to the current branch<br>
> (<a href="https://ask.openstack.org/en/question/45531/atc-pass-for-the-openstack-summit/" target="_blank">https://ask.openstack.org/en/question/45531/atc-pass-for-the-openstack-summit/</a>).<br>
<br>
</span>The comments on that answer are somewhat misleading, so I'll follow<br>
up there as well to set the record straight. The script[1] which<br>
identifies ATCs for the purpose of technical elections and summit<br>
passes is based entirely on Gerrit owners (uploaders) of changes<br>
merged to official projects within a particular time period. It<br>
doesn't treat master differently from any other branches. People who<br>
do the work to upload backports to stable branches absolutely do get<br>
counted for this purpose. People who only review changes uploaded by<br>
others do not (unless they are manually added to the "extra-atcs"<br>
file in the openstack/governance repo), but that is the case for all<br>
branches including master so not something stable-branch specific.<br>
<br>
Though I *personally* hope that is not the driving force to convince<br>
people to work on stable support. If it is, then we've already lost<br>
on this front.<br>
<span class=""><br>
> Secondly, it's difficult to get stack-analytics credit for back<br>
> ports, as the preferred method is to cherry pick the code, and<br>
> that keeps the original author's name. I've personally gotten a<br>
> few commits into stable, but have nothing to show for it in<br>
> stack-analytics (if I'm doing it wrong, I'm happy to be<br>
> corrected).<br>
</span>[...]<br>
<br>
Stackalytics isn't an official OpenStack project, but you should<br>
file a bug[2] against it if there's a feature you want its authors<br>
to consider adding.<br>
<br>
[1] <a href="https://git.openstack.org/cgit/openstack-infra/system-config/tree/tools/atc/email_stats.py" target="_blank">https://git.openstack.org/cgit/openstack-infra/system-config/tree/tools/atc/email_stats.py</a><br>
[2] <a href="https://bugs.launchpad.net/stackalytics/+filebug" target="_blank">https://bugs.launchpad.net/stackalytics/+filebug</a><br>
<span class=""><font color="#888888">--<br>
Jeremy Stanley<br>
</font></span><div class=""><div class="h5"><br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br></div></div>