As the number of production OpenStack deployments increase and more ecosystem partners add support for OpenStack clouds, it becomes increasingly important that the communities building services around OpenStack guide and influence the product evolution. The user committee's role is to represent the needs of the diverse range of OpenStack users. The user committee is advised by Working Groups, each of whom represents different user audiences and interests.
The user committee mission is to:
- Consolidate user requirements and present these to the management board and technical committee.
- Provide guidance for the development teams where user feedback is requested
- Track OpenStack deployments and usage, helping to share user stories and experiences
- Work with the user groups worldwide to keep the OpenStack community vibrant and informed
= the User Committee may request an agenda item for the Board's meeting.
How to Engage?
The User Committee and its Working Groups co-ordinate via the user-commitee mailing list - feel free to join and post your ideas.
Consider looking at the working groups and teams below and joining their activities.
If you are interested in volunteering to help with User Committee efforts, please complete this form.
Attend our fortnightly IRC meetings, alternating between times convenient for US and APAC attendees:
Next US meeting: Monday, May June 6th, 2016 at 1900 UTC in (freenode) #openstack-meeting
- Review the initial draft for UC charter creation: https://docs.google.com/document/d/1QmLOeseAkjBWM_TXsUeKBErNaSHnuZp81II0T71ARfo/edit?usp=sharing
- Discuss feedback from TC on governance.openstack.org repos: http://lists.openstack.org/pipermail/openstack-tc/2016-June/001197.html
- Review WG & Functional Teams: UC would like to see them attending the IRC meetings.
Logs from past meetings: * http://eavesdrop.openstack.org/meetings/user_committee/2015/ * http://eavesdrop.openstack.org/meetings/uc/2016/ Subscribe to the Mailing List Mailing List Archives
Planning for Austin:
The User Committee will have a session during the Austin Summit. We are using this etherpad to plan our agenda. Please add your proposals to it!
The structure of the user committee is currently being defined. Jon Proulx, Edgar Magana and Shilla Saebi have been nominated by the management board and technical committee to work with the community. This process is ongoing and your assistance is welcome - consider the following:
- initial structure ideas document for review.
- more recent ideas Scaling out the User Committee
- Ideas from Vancouver: https://etherpad.openstack.org/p/uc-2015
and post your thoughts on the user-committee mailing list.
Working Groups and Teams
The User Committee is currently looking at a structure that involves Working Groups to conduct specific packages of tasks. The Working Groups have a defined purpose and goal, and produce work to meet their stated aims. Working Groups will have their own leadership, which will be responsible for finding volunteers in the community to complete the work. Working Groups should be allowed to form naturally and easily where a need arises, without unnecessary bureaucratic burden. However, some controls should be enacted to ensure effort is best placed, and not duplicated, so please consider the procedure below:
|Working Group - Working Teams||Status||Co-Chairs||User Audience||Tag||Expected Outcomes|
|API Working Group||Active||Chris Dent, Michael McCune, Everett Toews||OpenStack contributors||#API-WG||To improve the developer experience of API users by converging the OpenStack API to a consistent and pragmatic RESTful design. The working group creates guidelines that all OpenStack projects should follow for new development, and promotes convergence of new APIs and future versions of existing APIs.|
|Product Working Group||Active||Carol Barrett, Shamail Tahir||Product and Business Managers||#Product-WG||To aggregate user stories from market-oriented work groups, partner with the development community on resources, and help gather data to generate a multi-release roadmap.|
|AUC Recognition||Active||Shamail Tahir, Maish Saidel-Keesing||Whole of Community||#Recognition-WG||To assist the User Committee with defining its constituency|
|Scientific Working Group||Active||Stig Telfer & Blair Blethwaite||Scientific Institutions Deploying, Operating and Contributing to OpenStack||#Scientific-WG||see wiki page|
|Ops Tags Team||Active||Tom Fifield, Edgar Magana, Jon Proulx, Shilla Saebi||Operators||#OpsTags-WG||A team to define tags for ops, allowing users to make better decisions by providing useful information about OpenStack software projects.|
|Enterprise Working Group||Active||Carol Barrett||Enterprise Vendors and Customers||#Enterprise-WG||Action plans to solve Enterprise Private Cloud needs and issues.|
|Large Deployment Team||Active||Matt Van Winkle||Operators||#Deploy-WG||To discuss the needs and issues of those running large OpenStack deployments|
|Application Ecosystem Working Group||Active||Patricia Montenegro, Michael Krotscheck||Cloud Applications Developers||#AppEco-WG||To create an environment where a diverse array of applications built for OpenStack can thrive.|
|Telecom/NFV||Active||Curtis Collicutt||Telecom and NFV||#openstack-nfv||Operators Telecom and NFV Team will work with the OpenStack community and ecosystem to benefit OpenStack Operators specifically running telecommunication services and Network Function Virtualization (NFV) systems utilizing OpenStack.|
|Diversity Working Group||Active||Carol Barrett, Kavit Munshi, Roland Chan||All Community Members||#Diversity-WG||see wiki page: https://wiki.openstack.org/wiki/Diversity|
Working Groups Chairs Directory
|Matt Van Winkleemail@example.com|