<div dir="ltr">inline<br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Mar 31, 2014 at 12:21 PM, matt <span dir="ltr"><<a href="mailto:matt@nycresistor.com" target="_blank">matt@nycresistor.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div>Incentives is a very interesting question.<br><br>What sort of incentives exist for devs? <br>
<br>Acknowledged as Contributor ( ATC ) to OpenStack -- ( resume fodder, free ticket to summit )<br></div>
Voting in PTL, TC<br><br></div><div>I guess those are the official benefits. There are the unofficial ones such as being saught after in the job market. <br></div></div></blockquote><div><br></div><div>I think that beyond those top level incentives, there are also more subtle recognitions as well. Loads of metrics are derived from code contributions, companies compete over it, etc. Openstack is primarily viewed by most people as a coding project. (I think this is the wrong strategy, but I think that the crux of the issue is this view today)</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div></div><div>What sort of incentives do you envision for operators?<br></div></div></blockquote>
<div><br></div><div>I think that we should start by considering the ways that we want operators to contribute:</div><div> - design review</div><div> - detailed bug reports</div><div> - requirements* (this one i think is the best handled at the moment, but could bear improvement)</div>
<div><br></div><div>Basically, you have people who understand how large systems need to work in order to function well; you want to capture their expertise and use it to improve the openstack design/implementation. Telling these people to commit code is pretty much ass backward, both because they have a different kind of role, and a different set of expertise, though it is what we tell them to do today. (they can write doc, which helps others, but not the contributor, at least not directly). </div>
<div> </div><div>IMO, the big problem is that there isn't a receptor site for these contributions. If you file tickets, no one pays attention. There is an argument that this is the role of commercial outfits, but that doesn't result in a particularly compete open effort. As far as I can tell, this is because we don't give devs any incentive to pay attention to real deployments, aside from any local relationships they might have.</div>
<div><br></div><div>(as an aside, the project has developed a great immune system to cope with the extreme growth it has faced, but this results in an large barrier to entry when ops folks try to casually contribute something)</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div></div><div>I mean with ATCs it's easy to set a barrier... did you contribute code. How do you quantify an operators contribution to OpenStack? When an operator is distinguished as an active contributor do we provide them with the same abilities as an ATC in dev? There is no PTL for operators... no need for voting for TC... though maybe they should? <br>
</div></div></blockquote><div><br></div><div>I think this activity should be focused around detailed critiques and bug reports. That is *the* way that you get ops people involved. You could run metrics in a similar fashion to the dev side. </div>
<div><br></div><div>I suspect that the early addition of this kind of feedback would result in a usable ceilometer, just to pick an example out of the air.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div></div><div>It raises interesting questions. And I think it starts with, do we want to create a role for an ATC outside of development ( I think we already do for documentation contributors ). If so, are they an ATC or an ATC*. Then comes the question of quantifying contribution.<br>
<br></div><div>What are your thoughts?</div></div></blockquote><div><br></div><div>I'm not so concerned about the metrics/gamification of it. I'm just tired of not having anyone to productively work with. </div><div>
-nld</div></div></div></div>