Jump to: navigation, search

Difference between revisions of "Governance/Foundation/UserCommittee"

 
(197 intermediate revisions by 19 users not shown)
Line 1: Line 1:
 +
{| style="color:#000000; border:solid 1px #A8A8A8; padding:0.5em; margin:0.5em 0; background-color:#FFFFFF;font-size:95%; vertical-align:middle;"
 +
| style="padding:1em;width: 40px" | [[Image:Warning.svg|40px]]
 +
| '''Old Page'''
 +
This page was used during the drafting process for the bylaws of the original OpenStack Foundation and could contain outdated information. The official version of the bylaws is kept at the Foundation website: http://www.openstack.org/legal/bylaws-of-the-openstack-foundation/
  
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 current official website of the Open Infrastructure Foundation can be found at https://www.openinfra.dev
 +
|}
  
The user committee mission is to:
+
== OpenStack User Committee ==
  
* Consolidate user requirements and present these to the management board and technical committee[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. The [https://www.openstack.org/foundation/user-committee/ 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
 
* 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
 
 
[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 [http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee 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 [https://docs.google.com/a/openstack.org/forms/d/1HOwsPp44fNbWv9zgvXW8ZnCaKszg_XKu7vmLbrPFMzQ/edit form].
+
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]).
  
Attend our fortnightly IRC meetings, alternating between times convenient for US and APAC attendees:
 
Next US meeting: '''Monday, Oct 10th, 2016 at 1900 UTC''' in (freenode) #openstack-meeting
 
  
Proposed Agenda:
+
=== Current members ===
* Provide an status of UC charter and next steps
+
You can find a list of the current User Committee members [https://governance.openstack.org/uc/#current-members here].
* AUC update
 
** https://drive.google.com/open?id=0B_yCSDGnhIbzcXFENjBOeUtqRFk
 
* PWG: Forum Suggestions
 
** https://drive.google.com/file/d/0BxtM4AiszlEyNEdqbVhNTVgzaWM/view?usp=sharing
 
* BCN Summit - UC and WG sessions
 
  
Logs from past meetings:
 
* http://eavesdrop.openstack.org/meetings/user_committee/2015/
 
* http://eavesdrop.openstack.org/meetings/uc/2016/
 
[http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee Subscribe to the Mailing List]
 
[http://lists.openstack.org/pipermail/user-committee/ Mailing List Archives]
 
  
== Structure ==
+
=== User Committee Charter ===
 +
You can find a copy of the User Committee Charter [https://governance.openstack.org/uc/reference/charter.html here].
  
The structure of the user committee is currently being defined. Jon Proulx, Edgar Magana and Shilla Saebi have been nominated by the management board and technical committee to work with the community. 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].
+
=== Working Groups & Teams ===
* more recent ideas [https://docs.google.com/document/d/12nu4FbdC7n7PzQmXo9-eSKa1Ca8TXSQxHwbrbNtQLWM/edit?usp=sharing Scaling out the User Committee]
+
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].
* Ideas from Vancouver: https://etherpad.openstack.org/p/uc-2015
 
and post your thoughts on the [http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee user-committee mailing list].
 
  
  
=== Working Groups and Teams ===
+
=== Mailing-list ===
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:
+
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 Template]]
 
* [[Procedure for Creating a New Working Group]]
 
 
 
{| class="wikitable sortable"
 
|-
 
! 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.
 
|-
 
| [[ProductTeam|Product Working Group]] || Active || Carol Barrett, 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.
 
|-
 
| [[AUCRecognition|AUC Recognition]] || Active || Shamail Tahir, Maish Saidel-Keesing || Whole of Community || #Recognition-WG || To assist the User Committee with defining its constituency
 
|-
 
| [[Scientific_working_group|Scientific Working Group]] || Active || Stig Telfer & Blair Blethwaite || Scientific Institutions Deploying, Operating and Contributing to OpenStack || #Scientific-WG || see wiki page
 
|-
 
|  [[Operations/Tags|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.
 
|-
 
| [[Enterprise Working Group]] || Active || Carol Barrett || Enterprise Vendors and Customers || #Enterprise-WG || Action plans to solve Enterprise Private Cloud needs and issues.
 
|-
 
| [[Large Deployment Team]] || Active || Matt Van Winkle || Operators || #Deploy-WG || To discuss the needs and issues of those running large OpenStack deployments
 
|-
 
| [[Application Ecosystem 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.
 
|-
 
| [[TelcoWorkingGroup|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.
 
|-
 
|  [[Diversity|Diversity Working Group]] || Active || Carol Barrett, Kavit Munshi, Roland Chan || All Community Members || #Diversity-WG || see wiki page: https://wiki.openstack.org/wiki/Diversity
 
|}
 
 
 
=== Working Groups Chairs Directory ===
 
 
 
 
 
{| class="wikitable sortable"
 
|-
 
! Name !! Email
 
|-
 
| Curtis Collicutt || curtis@serverascode.com
 
|-
 
| Carol Barrett || carol.l.barrett@intel.com
 
|-
 
| Kavit Munshi || kavit@aptira.com
 
|-
 
| Roland Chan || roland@aptira.com
 
|-
 
| Matt Van Winkle || mvanwink@rackspace.com
 
|-
 
| Stig Telfer || stig.openstack@telfer.org
 
|-
 
| Blair Bethwaite || blair.bethwaite@gmail.com
 
|-
 
| Shamail Tahir || itzshamail@gmail.com
 
|-
 
| Maish Saidel-Keesing || maishsk@maishsk.com
 
|-
 
| Tom Fifield || tom@openstack.org
 
|-
 
| Edgar Magana || emagana@gmail.com
 
|-
 
| Jon Proulx || jon@csail.mit.edu
 
|-
 
| Shilla Saebi || shilla.saebi@gmail.com
 
|-
 
| Chris Dent || chris.dent@gmail.com
 
|-
 
| Michael McCune || msm@redhat.com
 
|-
 
| Everett Toews || everett.toews@rackspace.com
 
|-
 
| Christopher Aedo || doc@aedo.net
 
|-
 
| Patricia Montenegro || patricia.montenegro@intel.com
 
|-
 
|}
 

Latest revision as of 17:43, 24 August 2021

Warning.svg Old Page

This page was used during the drafting process for the bylaws of the original OpenStack Foundation and could contain outdated information. The official version of the bylaws is kept at the Foundation website: http://www.openstack.org/legal/bylaws-of-the-openstack-foundation/

The current official website of the Open Infrastructure Foundation can be found at https://www.openinfra.dev

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.