<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">On Apr 8, 2016, at 1:57 PM, Major Hayden <<a href="mailto:major@mhtx.net" class="">major@mhtx.net</a>> wrote:<br class=""><div><blockquote type="cite" class=""><br class="Apple-interchange-newline"><div class=""><div class="">On 04/08/2016 03:31 PM, Jeremy Stanley wrote:<br class=""><blockquote type="cite" class="">Thanks for taking this up--some people just need<br class="">encouragement/suggestions for better ways to make an impact. On the<br class="">other hand, if you find that many of them have addresses at the same<br class="">company domain... well I guess we can find people higher up the<br class="">ladder in those companies and talk to them about how to channel<br class="">their employee quotas/incentives in more productive directions for<br class="">the community as well.<br class=""></blockquote><br class="">Hey folks,<br class=""><br class="">I have sent five emails so far and I received two responses already. Both of the people who replied said they are new to OpenStack and how to do reviews. They welcomed more input on how to find the right code reviews and how to complete the review. They weren't aware that these particular contributions were seen as unhelpful or gaming the system.<br class=""></div></div></blockquote><div><br class=""></div><div>First, thanks Major for reaching out and asking questions. </div><div><br class=""></div><div>Having just caught this thread, I was a bit startled by the assumption of ill-intent vs. a straight-up “Hey, this seems silly. Why are they doing this? We should ask!” That’s a bummer attitude for us to launch out with.</div><div><br class=""></div>I’m glad to see a few folks approach it as, “They probably don’t know” and offer blog posts. Might be good to get some of these incorporated into <a href="https://wiki.openstack.org/wiki/How_To_Contribute" class="">https://wiki.openstack.org/wiki/How_To_Contribute</a> so that n00bs (like me) get guidance early.</div><div><br class=""></div><div>I can’t speak for others, but I can say I’ve made it abundantly clear in my org that Stackalytics isn’t a useful or interesting metric beyond knowing where we’re contributing (and not). As a leaderboard, it’s untrustworthy because there’s no guarantee that any contribution it tracks is making value for OpenStack operators or users. I suspect that we’re reflecting on attitudes past, but I could be wrong.</div><div><br class=""></div><div><blockquote type="cite" class=""><div class=""><div class="">Would it make sense to encourage cores/PTLs on these projects to reach out to these users and share gerrit dashboard[1] links? A PTL shared some of these with me and it certainly helped me focus better on the right reviews.</div></div></blockquote><blockquote type="cite" class=""><div class=""><div class=""><br class="">[1] <a href="https://github.com/openstack/gerrit-dash-creator" class="">https://github.com/openstack/gerrit-dash-creator</a><br class=""></div></div></blockquote><div><br class=""></div>That seems smart in general. Most of the projects have a getting started page; I like the Nova one[1] because it calls out reviews as a good way to start familiarizing yourself with the code, and points out their code review guide[2].</div><div><br class=""></div><div>Always good to see you, Major. Big fan of your work. =]</div><div><br class=""></div><div>—j</div><div><br class=""></div><div>[1] <a href="http://docs.openstack.org/developer/nova/how_to_get_involved.html" class="">http://docs.openstack.org/developer/nova/how_to_get_involved.html</a></div><div>[2] <a href="http://docs.openstack.org/developer/nova/code-review.html#code-review" class="">http://docs.openstack.org/developer/nova/code-review.html#code-review</a></div><br class=""></body></html>