Jump to: navigation, search

Difference between revisions of "Application Ecosystem Working Group"

(Redirected page to App Dev Enablement Working Group)
(75 intermediate revisions by 13 users not shown)
Line 1: Line 1:
'''Status''': Active
#REDIRECT [[App_Dev_Enablement_Working_Group]]
'''Organizers''': [mailto:william.franklin@hp.com 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 [http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee 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  [[Application_Ecosystem_Working_Group#Liaisons|Liaisons]]
===Past Meetings===
* Tokyo https://etherpad.openstack.org/p/TYO-app-eco-wg
* Vancouver https://etherpad.openstack.org/p/YVR-app-eco-wg
* Philadelphia https://etherpad.openstack.org/p/PHL-ops-app-eco-wg
* Paris https://etherpad.openstack.org/p/kilo-summit-ops-app-eco
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 [[Application_Ecosystem_Working_Group#Liaisons|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
** e.g. [http://support.rightscale.com/12-Guides/Designers_Guide/Cloud_Solution_Architectures/Cloud_Computing_System_Architecture_Diagrams Cloud Computing System Architecture Diagrams] but with OpenStack services
* 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 [[Application_Ecosystem_Working_Group#Liaisons|Liaisons]] will know best how to communicate with their respective stakeholders.
3. To contribute content:
# Email your idea for content to the User Committee mailing list
# Discuss the content and where it should live
# 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.
== Liaisons ==
* [[Win_the_Enterprise|Win the Enterprise]]
** Maish Saidel-Keesing
** Bill Franklin
** Carol Barrett
*  [[API_Working_Group|API Working Group]]
** Everett Toews
** Lance Bragstad
* [[Governance/Foundation/UserCommittee|User Committee]]
** Jonathan Proulx
** Tim Bell
* [[Governance/TechnicalCommittee|Technical Committee]]
** Anne Gentle
** Rags Srinivas
* [http://www.openstack.org/foundation/board-of-directors/ OpenStack BoD]
** Chris Kemp
** Bill Franklin
* [[Governance/DefCoreCommittee|DefCore]]
** Jonathan Bryce
* [[CrossProjectLiaisons|Cross-Project Liaisons]]
==How to Join==
Join the [http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee 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.
* [mailto:chris.c.kemp@nebula.com Chris Kemp]
* [mailto:tom@openstack.org Tom Fifield]
* [mailto:evan@hp.com Evan Scheessele]
* [mailto:Shilla.Saebi@gmail.com Shilla Saebi]
* [mailto:victor.r.howard@gmail.com Victor Howard]
* [mailto:carol.l.barrett̊intel.com Carol Barrett]
* [mailto:ksa@slac.stanford.edu Karl Amrhein]
* [mailto:bmorel@internap.com Bruno Morel]
* [mailto:dff.openstack@gmail.com David F. Flanders]

Latest revision as of 22:30, 8 November 2016