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.
Attend our weekly IRC meetings on Monday at 1900 UTC, if there are no agenda items that need to be discussed then the meeting will be cancelled.
Meeting Agenda/Previous Meeting Logs
Future Proposed Meeting: Monday, Aug 21, 2017 at 1800 UTC in (freenode) #openstack-meeting</b>
1. Roll call 2. Welcome to new elected UC members 3. Review action items last meeting 4. Vote on Financial WG proposal 5. OpenDiscussion
Previous Agenda: Monday, July 31, 2017 at 1800 UTC in (freenode) #openstack-meeting
1. Review outcome from last July 19 UC WG Status meeting: . http://eavesdrop.openstack.org/meetings/uc/2017/uc.2017-07-19-05.03.log.html Possible next steps to finalize: * Use Openstack-UC IRC as ongoing/virtual WG status * Contact other WG leads to add their status * Share IRC or perhaps summary with MLs: UC, Operators, SIGS, TC, Foundation? 2. UC meeting as Video Conference and IRC. 3. Discuss re-opening the Financial WG request
Logs from past meetings: * http://eavesdrop.openstack.org/meetings/user_committee/2015/ * http://eavesdrop.openstack.org/meetings/uc/2016/ * http://eavesdrop.openstack.org/meetings/user_committee/2017/ * http://eavesdrop.openstack.org/meetings/uc/2017/ Subscribe to the Mailing List Mailing List Archives
The structure of the user committee has been recently updated - see https://governance.openstack.org/uc/index.html for more details if interested in the way that the user committee itself is formed and operates. Note that a large portion of it's mission is to support the working groups which are covered in more detail below. Any input on structure is welcome; 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|
|App Dev Enablement Working Group||Active||Patricia Montenegro, Christopher Aedo||Cloud Applications Developers||#AppEco-WG||To create an environment where a diverse array of applications built for OpenStack can thrive.|
|Enterprise Working Group||Active||Yih Leong Sun||Enterprise Vendors and Customers||#Enterprise-WG||Action plans to solve Enterprise needs and issues for OpenStack adoption and deployment|
|Fault_Genes_Working_Group||Active||Nemat Bidokhti, Rochelle (Rocky) Grober||Operators, OpenStack Contributors||#Fault-Genes||To improve OpenStack fault management by defining and developing fault handling policies through fault classification, types, root cause, consistent logging and fault insertion.|
|LCOO||Active||Jamey McCabe, Sundar Krishnamurthy||Multi-cloud Contributing Operators||#LCOO-WG||Body of OpenStack Operator-Contributors with a shared interest in accelerating the enterprise maturity and adoption of OpenStack and to drive Community awareness of platform enhancements necessary to address the unique use cases of network service providers and horizontally scaling, massively distributed cloud operators.|
|Large Deployment Team||Active||Matt Van Winkle||Operators||#Deploy-WG||To discuss the needs and issues of those running large OpenStack deployments|
|Massively Distributed Clouds||Active||Adrien Lebre||Operators, Telcos, Research Centers||#MassivelyDistributed||To debate and investigate how OpenStack can address Fog/Edge Computing use-cases (i.e. the supervision and use of a large number of remote data centers through a single distributed OpenStack system).|
|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.|
|Operators 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.|
|Product Working Group||Active||Yih Leong Sun, 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.|
|Scientific Working Group||Active||Stig Telfer, Blair Bethwaite & Martial Michel||Scientific Institutions Deploying, Operating and Contributing to OpenStack||#Scientific-WG||see wiki page|