Jump to: navigation, search

Difference between revisions of "Governance/Foundation/UserCommittee"

(Working Groups)
m (OpenStack User Committee)
 
(291 intermediate revisions by 28 users not shown)
Line 1: Line 1:
 +
== OpenStack User Committee ==
  
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.
+
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 [https://www.openstack.org/foundation/user-committee/ OpenStack 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
 
* Provide guidance for the development teams where user feedback is requested
 
* Provide guidance for the development teams where user feedback is requested
* Track [[OpenStack]] deployments and usage, helping to share user stories and experiences
+
* 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
+
* Work with the user groups worldwide to keep the OpenStack community vibrant and informed
 
 
== How to Engage? ==
 
 
 
The committee co-ordinates via the [http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee user-commitee mailing list].
 
  
If you are interested in volunteering to help with User Committee efforts, please complete this [https://docs.google.com/a/openstack.org/forms/d/1HOwsPp44fNbWv9zgvXW8ZnCaKszg_XKu7vmLbrPFMzQ/edit form].
 
  
== Structure ==
+
The UC governance website at https://governance.openstack.org/uc/ contains all reference documents and resolutions voted by the OpenStack User Committee (which are openly managed via proposed changes to the [http://git.openstack.org/cgit/openstack/governance openstack/governance git repository]).
  
The structure of the user committee is currently being defined. Tim Bell, Jon Proulx and Subbu Allamaraju 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].
+
=== Current members ===
* more recent ideas [https://docs.google.com/document/d/12nu4FbdC7n7PzQmXo9-eSKa1Ca8TXSQxHwbrbNtQLWM/edit?usp=sharing Scaling out the User Committee]
+
You can find a list of the current User Committee members [https://governance.openstack.org/uc/#current-members here].
  
and post your thoughts on the [http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee user-committee mailing list].
 
  
 +
=== User Committee Charter ===
 +
You can find a copy of the User Committee Charter [https://governance.openstack.org/uc/reference/charter.html here].
  
=== 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 Template]]
+
=== Working Groups & Teams ===
* [[Procedure for Creating a New Working Group]]
+
The User Committee working groups and teams aim to help users represent and achieve their needs through collaboration in the upstream community. The working groups and teams can be created as-needed and grow organically. You can find a list of the current Working Groups and Teams [https://governance.openstack.org/uc/#teams here] and the requirements for establishing new Working Groups and Teams can be found [https://governance.openstack.org/uc/reference/new-uc-group-requirements.html here].
  
  
{| class="wikitable sortable"
+
=== Mailing-list ===
|-
+
The [http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee user-committee mailing-list] is used for communication within the User Committee. Posting is moderated for non-members.
! Working Group !! Status !! Organisers !! Expected Outcomes
 
|-
 
| [[TelcoWorkingGroup|Telco]] || Active || Steve Gordon || Define the use cases and identify and prioritise the requirements which are needed to deploy, manage, and run telecommunication services on top of OpenStack.  
 
|-
 
| [[Enterprise Working Group]] || Active || Carol Barrett <carol.l.barrett@intel.com>  || Action plans to solve Enterprise Private Cloud needs and issues.
 
|-
 
| [[Application Ecosystem Working Group]] || Active || Bill Franklin, Tom Fifield || To create an environment where a diverse array of applications built for OpenStack can thrive.
 
|-
 
| [[API Working Group]] || Active ||  Jay Pipes, Christopher Yeoh, Everett Toews || To propose, discuss, review, and advocate for API guidelines for all OpenStack Programs to follow.
 
|-
 
| [[Large Deployment Team]] || Active || Matt Van Winkle || To discuss the needs and issues of those running large OpenStack deployments
 
|-
 
| [[LogWorkingGroup|Log Rationalisation]] || Active || Rochelle Grober, Jay Pipes ||
 
|-
 
| [[Tools and Monitoring WG|Ops Tools]] || Sporadic Activity || Debbo Dutta, Joe Topjian || To discover and detail best practices in ops monitoring and tools, and facilitate tool sharing
 
|-
 
| Packaging || Sporadic Activity || None yet || To be determined
 
|-
 
| [[ProductTeam|Product Management]] || Active || None yet || To be determined
 
|-
 
| [[Operations/Tags|Ops Tags Team]] || Forming || Tom Fifield, Tim Bell, Subbu Allamaraju, Jon Proulx || A team to define tags for ops, allowing users to make better decisions by providing useful information about OpenStack software projects.
 
|}
 

Latest revision as of 18:42, 22 October 2018

OpenStack User Committee

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 OpenStack 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 UC governance website at https://governance.openstack.org/uc/ contains all reference documents and resolutions voted by the OpenStack User Committee (which are openly managed via proposed changes to the openstack/governance git repository).


Current members

You can find a list of the current User Committee members here.


User Committee Charter

You can find a copy of the User Committee Charter here.


Working Groups & Teams

The User Committee working groups and teams aim to help users represent and achieve their needs through collaboration in the upstream community. The working groups and teams can be created as-needed and grow organically. You can find a list of the current Working Groups and Teams here and the requirements for establishing new Working Groups and Teams can be found here.


Mailing-list

The user-committee mailing-list is used for communication within the User Committee. Posting is moderated for non-members.