Difference between revisions of "Governance/Foundation/UserCommittee"

Revision as of 18:45, 23 January 2013

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.

When the OpenStack Foundation was launched in 2012, there were two initial structures created. The management board provides strategic and financial oversight of Foundation resources and staff. The technical committee defines and stewards the technical direction of OpenStack software development. We are now establishing the user committee whose 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

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 through the foundation mailing list and points to this [1][document for review]]. Among the areas of discussion are the definition and representation model of the wide spectrum of users in different industry segments ranging from end-users submitting work to an OpenStack cloud through ecosystem partners using the APIs to provide additional services to those deploying and operating clouds in production. It is also planned to expand the committee further to cover both industry segments and user group representation along with running a user survey with the goal to present the results at the next summit.

For those of you who would like to help, please look at the points to review document and post your thoughts to the OpenStack foundation mailing list.

@@ Line 1: / Line 1: @@
 __NOTOC__
-The user committee is a newly formed organisation with the following aims:
+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.
-* define the long term bylaws for the user committee
+When the [[OpenStack]] Foundation was launched in 2012, there were two initial structures created. The management board provides strategic and financial oversight of Foundation resources and staff. The technical committee defines and stewards the technical direction of [[OpenStack]] software development. We are now establishing the user committee whose role is to represent the needs of the diverse range of [[OpenStack]] users.
-* define the categories of different users that the user committee will represent
-* consolidate user needs and present to the technical committee and management board to define action plans
-* keep track of users and their usage of [[OpenStack]] for the purpose of providing aggregate statistics to the foundation while maintaining confidentiality/anonymity as required
-* work with the [[OpenStack]] community manager to further expand the worldwide user group structures and keep them vibrant and informed
-The user committee was formed following the nomination of Tim Bell as the management board representative and Ryan Lane as the technical committee representative. As defined in the foundation bylaws (http://wiki.openstack.org/Governance/Foundation/Bylaws clause 4.14), Tim and Ryan have selected a 3rd candidate, JC Martin, to complete the initial user committee team.
+The user committee mission is to
-The current mandate and structure of the user committee is being developed around this [https://docs.google.com/document/d/1yD8TfqUik2dt5xo_jMVHMl7tw9oIJnEndLK8YqEToyo/edit document].
+* 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 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 through the foundation mailing list and points to this [https://docs.google.com/document/d/1yD8TfqUik2dt5xo_jMVHMl7tw9oIJnEndLK8YqEToyo/edit][document for review]]. Among the areas of discussion are the definition and representation model of the wide spectrum of users in different industry segments ranging from end-users submitting work to an [[OpenStack]] cloud through ecosystem partners using the APIs to provide additional services to those deploying and operating clouds in production. It is also planned to expand the committee further to cover both industry segments and user group representation along with running a user survey with the goal to present the results at the next summit.
+For those of you who would like to help, please look at the points to review document and post your thoughts to the [[OpenStack]] foundation mailing list.