Jump to: navigation, search

Difference between revisions of "Governance/Foundation/UserCommittee"

(How to Engage?)
m (How to Engage?)
Line 28: Line 28:
  - Forum Session Selection Candidates
  - Forum Session Selection Candidates
  - Working Group Update(s)
  - Working Group Update(s)
  - Ops Midcycle - Goals/Expectations
  - Ops Midcycle (March 15-16, 2017) - Goals/Expectations
  - Open Agenda
  - Open Agenda

Revision as of 23:34, 24 February 2017

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[1].
  • 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

[1]= 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 Every two weeks (on odd weeks) on Monday at 1900 UTC: Next US meeting: Monday, Feb 27th, 2017 at 1900 UTC in (freenode) #openstack-meeting

Proposed Agenda:

- Welcome UC elected members: Shamail and Melvin
- UC Chair - Election: https://governance.openstack.org/uc/reference/charter.html
- Review previous Action Items
- Board + TC + UC meeting in Boston (March 8-9, 2017)
- Forum Session Selection Candidates
- Working Group Update(s)
- Ops Midcycle (March 15-16, 2017) - Goals/Expectations
- Open Agenda

Previous Agenda:

- UC Election
- Boston planning
- Finalize on proposal from the Product Working Group for Forum - https://docs.google.com/presentation/d/1jTlO4UdNjc5cOKboeCNhLDEdttazWWlDgNxxulUrPNg/edit
- Open Agenda
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
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.
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 Private Cloud needs and issues.
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 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 Blethwaite Scientific Institutions Deploying, Operating and Contributing to OpenStack #Scientific-WG see wiki page