Jump to: navigation, search

Application Ecosystem Working Group

Revision as of 20:38, 12 November 2015 by David F Flanders (talk | contribs) (Members)

Status: Active

Organizers: Bill Franklin


To create an ecosystem where a diverse array of applications built for OpenStack can thrive.


  • Grow the number of active OpenStack applications globally, for both private and public cloud use
  • Make it simpler to create applications for OpenStack by:
    • Improving introductory material
    • Ensuring appropriate tools and technical information is available, correct and easy to find
  • Further facilitating the association of those creating applications for OpenStack clouds with the OpenStack technical community by:
    • Improving developer.openstack.org, a portal for application creators
    • Analyzing and improving the 6-monthly conference, particularly the "Targeting OpenStack" track, and other more feedback-style sessions
    • Educating OpenStack's active technical community on the issues faced by those who are targeting OpenStack clouds


For email, we will use the user-committee mailing list and prefix the subject line with [app].

For IRC, we will use #openstack on Freenode.

For the OpenStack Summit, design summit sessions and/or conference sessions.

For meetings, In Planning

For liaisons (the liaison is the first line of contact for the AE WG team members), see Liaisons

Past Meetings


1. Application Ecosystem Feedback

Anyone in the application ecosystem needs a way to give feedback to the OpenStack community at large. This can be a daunting task for those outside of the community. The members of this working group need to gather and channel this feedback into one place where the people building OpenStack itself can consume it. We should be accepting of feedback in all its forms: conversations, email, IRC, blog posts, etc. The point is to act as a conduit and provide a way to get that feedback to the community.

2. Communicate Actionable Items

This working group has a large and diverse group of stakeholders. It's our responsibility to engage these stakeholders, keep them up to date, and communicate actionable items to them. Specifically the Liaisons are responsible for ensuring this happens.

3. Content

The content necessary to grow an application ecosystem comes in many forms. Some examples are:

  • Content for events (eg hackathons)
  • White papers
  • Code examples
  • Application examples
  • Application architectures
  • Presentations
  • Anything else you can think of

Where a particular piece of content lives will likely depend on the nature of the content.

How to Contribute

Contributions come in the form of the deliverables above.

1. To contribute feedback:

2. To communicate actionable items:

The Liaisons will know best how to communicate with their respective stakeholders.

3. To contribute content:

  1. Email your idea for content to the User Committee mailing list
  2. Discuss the content and where it should live
  3. Execute on that idea

4. Participate in the discussions at the weekly TODO (see Meetings).


There is the related API_Working_Group (API WG). The Application Ecosystem Working Group (AE WG) is complementary to the API WG. The AE WG is focused on anyone creating or running an application on OpenStack whereas the API WG is focused on guidelines for the APIs. The place where these groups meet in the middle is the API, which forms the contract between the two. Members of the AE WG are encouraged to be members of the API WG and vice versa.


How to Join

Join the user-committee mailing list, watch for emails that are prefixed by [app], and join the discussion. Start contributing to the deliverables.


Please add yourself to this list if you are committed to growing the Application Ecosystem for OpenStack.