<div dir="ltr">+1, nice idea, it could be really funny.<div><br></div><div>agreed with Thierry's note about automation.</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Feb 13, 2014 at 5:53 PM, Sean Dague <span dir="ltr"><<a href="mailto:sean@dague.net" target="_blank">sean@dague.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On 02/13/2014 05:37 AM, Thierry Carrez wrote:<br>
> Sandy Walsh wrote:<br>
>> The informal OpenStack motto is "automate everything", so perhaps we should consider some form of gamification [1] to help us? Can we offer badges, quests and challenges to new users to lead them on the way to being strong contributors?<br>
>><br>
>> "Fixed your first bug" badge<br>
>> "Updated the docs" badge<br>
>> "Got your blueprint approved" badge<br>
>> "Triaged a bug" badge<br>
>> "Reviewed a branch" badge<br>
>> "Contributed to 3 OpenStack projects" badge<br>
>> "Fixed a Cells bug" badge<br>
>> "Constructive in IRC" badge<br>
>> "Freed the gate" badge<br>
>> "Reverted branch from a core" badge<br>
>> etc.<br>
><br>
> I think that works if you only keep the ones you can automate.<br>
> "Constructive in IRC" for example sounds a bit subjective to me, and you<br>
> don't want to issue those badges one-by-one manually.<br>
><br>
> Second thing, you don't want the game to start polluting your bug<br>
> status, i.e. people randomly setting bugs to "triaged" to earn the<br>
> "Triaged a bug" badge. So the badges we keep should be provably useful ;)<br>
><br>
> A few other suggestions:<br>
> "Found a valid security issue" (to encourage security reports)<br>
> "Fixed a bug submitted by someone else" (to encourage attacking random bugs)<br>
> "Removed code" (to encourage tech debt reduction)<br>
> "Backported a fix to a stable branch" (to encourage backporting)<br>
> "Fixed a bug that was tagged nobody-wants-to-fix-this-one" (to encourage<br>
> people to attack critical / hard bugs)<br>
><br>
> We might need "protected" tags to automate this: tags that only some<br>
> people could set to bugs/tasks to designate "gate-freeing" or<br>
> "nobody-wants-to-fix-this-one" bugs that will give you badges if you fix<br>
> them.<br>
><br>
> So overall it's a good idea, but it sounds a bit tricky to automate it<br>
> properly to avoid bad side-effects.<br>
<br>
</div></div>Gamification is a cool idea, if someone were to implement it, I'd be +1.<br>
<br>
Realistically, the biggest issue I see with on-boarding is mentoring<br>
time. Especially with folks completely new to our structure, there is a<br>
lot of confusing things going on. And OpenStack is a ton to absorb. I<br>
get pinged a lot on IRC, answer when I can, and sometimes just have to<br>
ignore things because there are only so many hours in the day.<br>
<br>
I think Anita has been doing a great job with the Neutron CI onboarding<br>
and new folks, and that's given me perspective on just how many<br>
dedicated mentors we'd need to bring new folks on. With 400 new people<br>
showing up each release, it's a lot of engagement time. It's also<br>
investment in our future, as some of these folks will become solid<br>
contributors and core reviewers.<br>
<br>
So it seems like the only way we'd make real progress here is to get a<br>
chunk of people to devote some dedicated time to mentoring in the next<br>
cycle. Gamification might be most useful, but honestly I expect a "Start<br>
Here" page with the consolidated list of low-hanging-fruit bugs, and a<br>
Review Here page with all reviews for low hanging fruit bugs (so they<br>
don't get lost by core review team) would be a great start.<br>
<br>
The delays on reviews for relatively trivial fixes I think is something<br>
that is probably more demotivating to new folks than the lack of badges.<br>
So some ability to keep on top of that I think would be really great.<br>
<span class="HOEnZb"><font color="#888888"><br>
-Sean<br>
<br>
--<br>
Sean Dague<br>
Samsung Research America<br>
<a href="mailto:sean@dague.net">sean@dague.net</a> / <a href="mailto:sean.dague@samsung.com">sean.dague@samsung.com</a><br>
<a href="http://dague.net" target="_blank">http://dague.net</a><br>
<br>
</font></span><br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</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>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr"><div>Sincerely yours,</div><div>Sergey Lukjanov</div><div>Savanna Technical Lead</div><div>Mirantis Inc.</div></div>
</div>