Difference between revisions of "Governance/Foundation/UserCommittee"
(→Structure) |
|||
Line 1: | Line 1: | ||
− | 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. | + | 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 mission is to: | |
− | |||
− | |||
− | |||
− | The user committee mission is to | ||
* Consolidate user requirements and present these to the management board and technical committee | * Consolidate user requirements and present these to the management board and technical committee | ||
Line 21: | Line 17: | ||
== Structure == | == Structure == | ||
− | The structure of the user committee is currently being defined. Tim Bell, Ryan Lane and J-C Martin have been nominated by the management board and technical committee to work with the community and determine the by-laws and scope. This process is ongoing | + | The structure of the user committee is currently being defined. Tim Bell, Ryan Lane and J-C Martin have been nominated by the management board and technical committee to work with the community and determine the by-laws and scope. This process is ongoing and your assistance is welcome - consider the following: |
− | + | * initial structure ideas [https://docs.google.com/document/d/1yD8TfqUik2dt5xo_jMVHMl7tw9oIJnEndLK8YqEToyo/edit document for review]. | |
+ | * more recent ideas [https://docs.google.com/document/d/12nu4FbdC7n7PzQmXo9-eSKa1Ca8TXSQxHwbrbNtQLWM/edit?usp=sharing Scaling out the User Committee] | ||
− | + | and post your thoughts on the [http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee user-committee mailing list]. |
Revision as of 01:24, 26 May 2014
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 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
How to Engage?
The committee co-ordinates via the user-commitee mailing list.
If you are interested in volunteering to help with User Committee efforts, please complete this form.
Structure
The structure of the user committee is currently being defined. Tim Bell, Ryan Lane and J-C Martin have been nominated by the management board and technical committee to work with the community and determine the by-laws and scope. 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
and post your thoughts on the user-committee mailing list.