<div dir="ltr">On Tue, Jun 18, 2013 at 9:10 AM, Everett Toews <span dir="ltr"><<a href="mailto:everett.toews@rackspace.com" target="_blank">everett.toews@rackspace.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<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">
<div style="word-wrap:break-word">
<div>Hi All,</div>
<div><br>
</div>
<div>When I was writing a blog post [1], I found myself stumbling over distinguishing between the developers of OpenStack itself and the developers who build on top of it. It might seem like a minor thing but as we all know, naming things is one of the hardest
things in computer science. :)</div>
<div><br>
</div>
<div>I mulled over terms like solution developers, external developers, 3rd party developers, etc. but didn't care much for any of them. Now I'm thinking that in the spirit of the user committee and its draft charter [2] we should simply name them user developers.</div>
<div><br>
</div>
<div>It would be convenient if we could come to a (lazy) consensus on this and use one term moving forward as it's going to become more and more relevant as OpenStack matures.</div>
<div><br>
</div>
<div>Thoughts?</div>
<div><br></div></div></blockquote><div><br></div><div>The draft charter lists this user type as an ecosystem partner. I'm not a huge fan of user developer as people writing OpenStack itself are also users and are usually either operators or are distribution or appliance vendors.<div>
<br></div><div>- Ryan</div></div></div></div></div>