<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, May 6, 2014 at 7:38 AM, Anne Gentle <span dir="ltr"><<a href="mailto:anne@openstack.org" target="_blank">anne@openstack.org</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>I believe that UX and DevEx are different areas of expertise and OpenStack could benefit more from a separate focused DevEx program</div></div></div></div>
</blockquote><div><br></div><div>Agreed.</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 class="gmail_extra"><div class="gmail_quote">
<div>I'm not sure Dean's proposal is quite "DevEx" though, and I don't know if a rename alone would take care of what I think it is. </div><div><br></div><div>- SDK maintenance and testing</div>
<div>- App-dev focus on docs</div><div>- Focus on improving automation tasks with unified CLI</div><div>- Processes and governance that could be separate from contrib devs</div><div>- Releases separate from the every six month timed release in order to serve app devs better with quicker turnaround (similar to the CLIs now)</div>
<div>- Integrated client with the goal of eliminating the client-per-project mess</div><div><br></div><div>Dean, what do you think of these ideas? Is there enough in common with the CLI user and app dev to consider this DevEx umbrella the program? Do you plan to get rid of <project>-clients, and does it make sense to do so? Also how do you plan to transition away from DevStack PTL role, have you found a replacement?</div>
</div></div></div></blockquote><div><br></div><div>Anne, this is why you are a writer and I am not. ;) I may steal that list...</div><div><br></div><div>What you have listed fits with what I see happening as the Client Tools adds the SDK projects (#1 and 2). #3, 5 and 6 are already goals for OSC[1]; and #4 is what we are here talking about now.</div>
</div><div><br></div><div>[1] I expect OSC to switch to use the Python OpenStack SDK as it becomes ready rather than attempt to salvage the existing client libs.</div><div><br></div><div>dt</div><div><br></div>-- <br><br>
Dean Troyer<br><a href="mailto:dtroyer@gmail.com">dtroyer@gmail.com</a><br>
</div></div>