Open Stack

On Sep 10, 2014, at 2:23 AM, Lauren Sell <lauren at openstack.org<mailto:lauren at openstack.org>> wrote:

I’m wondering if it might make sense to move forward with team phone calls / mailing list emails, and wait to do a f2f in Paris since we’re only two months out.

Whatever happens, let’s move forward with team phone calls / mailing list emails. Practically speaking, let’s just continue to use the user-committee mailing list for the time being until we have a name we can give to the working group.

One possible agenda suggestion: if we can get some app developers / end users in the room, it would be great to gather feedback on developer.openstack.org<http://developer.openstack.org/> and the type of content that would be useful to them as we build out this section going forward.

Yes. Let’s get as much of our audience in the room as possible.

The bulk of the effort of the initial release of developer.openstack.org<http://developer.openstack.org> went into infra issues. I welcome the evolution of developer.openstack.org<http://developer.openstack.org> by the community. The primary exemplar in this area for open source is developer.mozilla.org<http://developer.mozilla.org>. It’s amazing really. And they’re going toe to toe with Microsoft, Google, and Apple.

I also think one of the primary functions of this group should be getting feedback into the development process (as well as efforts like defcore) to improve the platform and experience for app developers.

This would be ideal. If we could achieve the same level of success that the Operators working group has, that would be incredible.

Finally, we mentioned this on the first call, but the Foundation is posting a job opening for an app dev community manager, who I think could play an important supporting many of these efforts. We’ll be promoting the new position next week, so please let us know if you have any recommendations from your networks.

Hmmmmm…if any of you have the people responsible for developer.mozilla.org<http://developer.mozilla.org> in your networks, that might be a good place to start. ;)

Thanks,
Everett

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/user-committee/attachments/20140910/a18413ba/attachment.html>