On Fri, Dec 3, 2010 at 10:00 AM, Larry Cafiero <span dir="ltr"><<a href="mailto:larry.cafiero@gmail.com">larry.cafiero@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="gmail_quote"><div class="im">On Fri, Dec 3, 2010 at 3:48 AM, Greg DeKoenigsberg <span dir="ltr"><<a href="mailto:greg.dekoenigsberg@gmail.com" target="_blank">greg.dekoenigsberg@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>To be clear: much of this responsibility should fall on the advocates for these spins. "Hey Meego, want more marketing? Recruit some folks to the marketing team who care about Meego to help carry the load." <br>
</blockquote></div><div> <br>This is probably the most relevant paragraph in this entire thread, and thanks Greg for making this point. Instead of "much of the responsibility," though, I'd say "most of the responsibility" or even arguably "all of the responsibility."<br>
</div></div></blockquote><div><br>But then the question becomes: if spin folks are entirely response bringing volunteers to help with these tasks, what's their incentive to send them to another team to do the work?<br>
<br>The analogue in the working world: I'm not going to recruit a resource so that resource can be "managed" by someone else in such a way that I only get that resource part-time. I'm going to recruit someone who works for me, and does my bidding, and I'm going to hoard that resource, unless there's a *clear* benefit to me for sharing that resource. <br>
<br>Seems to me like we've got two ways of providing resources to various subprojects: 1. infrastructure support, and 2. people support. I would argue that we've done a good job at 1., and a poor job at 2.<br><br>
Maybe the "Spins SIG" should have a strong focus on improving infrastructure support. Improving kopers, QA infrastructure, build hosts -- those are things that we can figure out how to scale. Scaling people is much harder, and clearly much more contentious.<br>
<br>--g<br></div></div>