Jump to: navigation, search

Difference between revisions of "Governance/Foundation/UserCommittee"

m
m (OpenStack User Committee)
 
(139 intermediate revisions by 12 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.  The user committee is advised by Working Groups, each of whom represents different user audiences and interests.
+
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[1].
 
 
* 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].
 
<br><br>
 
Attend our weekly IRC meetings on Monday at 1900 UTC, if there are no agenda items that need to be discussed then the meeting will be cancelled.<br>
 
 
 
== Meeting Agenda/Previous Meeting Logs ==
 
Next meeting: '''<u>Monday, June 12, 2017 at 1800 UTC</u>''' in (freenode) #openstack-meeting
 
<br>
 
Upcoming Session: June 12
 
- Action Items from previous meetings
 
    1. Finalize approach proposed for WG Status meetings.  Immediate Proposal is to have the first Monthly UC meeting at which we will also have WG Status be June 21 0500UTC. http://lists.openstack.org/pipermail/user-committee/2017-June/002107.html
 
    2. Help UC with items from last weeks meeting - Propose others to volunteer to help
 
  
Previous Agenda: June 5, 2017:
 
  1. Send request to WGs chair to review the list of members
 
  2. Finalize and document procedure for extra AUC - text file that would be approved by UC Core
 
  3. Review what was has been proposed since initial implementation about AUC Criteria:
 
  4. Finalize meetings schedule and approach (includes cancelling by Friday if no agenda items) and notify entire Foundation team.
 
  5. Review and finalize approach proposed for WG Status meetings: http://lists.openstack.org/pipermail/user-committee/2017-May/002093.html
 
- Determine which WGs will be attending the Denver PTG and whether space is required
 
  
Previous Agenda/Etherpad from Boston Summit: https://etherpad.openstack.org/p/BOS-forum-user-committee-session
+
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]).
  
Previous Agenda: May 1st, 2017:
 
- Final Preparations for Boston Forum
 
- OpenStack Shared Interest Groups
 
  - https://docs.google.com/document/d/1gTeN5ZB2AnPPXejXOm08sQ75Fc-cMs-x-dOGwfsyM8w
 
- Open Items
 
  
Previous Agenda:
+
=== Current members ===
- Recap UC Session at the Ops Meetup (10min)
+
You can find a list of the current User Committee members [https://governance.openstack.org/uc/#current-members here].
- Vote on moving UC meeting to weekly (skipping as it makes sense; similar to the TC model) (3min)
 
- Discuss mentoring plan for UC members (WG chair pairing, helping new WG members, etc.) (12min)
 
- Review initial draft of official WGs guidelines (20min)
 
- Financial WG proposal (10min) https://docs.google.com/document/d/1a5PGnOIGBzONGFlkSF766piGtTX9WdR6ngQSfHwq_Cw/edit?usp=sharing
 
- Open Items (5min)
 
  
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/
 
[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 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 [http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee user-committee mailing list].
 
  
=== Working Groups and Teams ===
+
=== Working Groups & 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:
+
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].
  
* [[Working Group Template]]
 
* [[Procedure for Creating a New Working Group]]
 
  
{| 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 - Working Teams !! Status !! Co-Chairs !! User Audience !! Tag !! Expected Outcomes
 
|-
 
| [[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 needs and issues for OpenStack adoption and deployment
 
|-
 
| [[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, Sundar Krishnamurthy || 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|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).
 
|-
 
|  [[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.
 
|-
 
| [[Ops-telecom-nfv|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.
 
|-
 
| [[ProductTeam|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|Scientific Working Group]] || Active || Stig Telfer & Blair Blethwaite || Scientific Institutions Deploying, Operating and Contributing to OpenStack || #Scientific-WG || see wiki page
 
|}
 

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.