|
|
| (226 intermediate revisions by 22 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 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 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].
| + | === Current members === |
| | + | You can find a list of the current User Committee members [https://governance.openstack.org/uc/#current-members here]. |
| | | | |
| − | Attend our fortnightly IRC meetings, alternating between times convenient for US and APAC attendees:
| |
| − | Next US meeting: '''Monday, May June 6th, 2016 at 1900 UTC''' in (freenode) #openstack-meeting
| |
| | | | |
| − | Proposed Agenda:
| + | === User Committee Charter === |
| − | * Review the initial draft for UC charter creation: https://docs.google.com/document/d/1QmLOeseAkjBWM_TXsUeKBErNaSHnuZp81II0T71ARfo/edit?usp=sharing
| + | You can find a copy of the User Committee Charter [https://governance.openstack.org/uc/reference/charter.html here]. |
| − | * Discuss feedback from TC on governance.openstack.org repos: http://lists.openstack.org/pipermail/openstack-tc/2016-June/001197.html
| |
| − | * Review WG & Functional Teams: UC would like to see them attending the IRC meetings.
| |
| | | | |
| − | 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]
| |
| | | | |
| − | Planning for Austin:
| + | === Working Groups & Teams === |
| − | The User Committee will have a session during the Austin Summit. We are using this etherpad to plan our agenda. Please add your proposals to it!<br /> | + | 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]. |
| − | https://etherpad.openstack.org/p/User_Committee_Austin_Planning | |
| | | | |
| − | == Structure ==
| |
| | | | |
| − | The structure of the user committee is currently being defined. Jon Proulx, Subbu Allamaraju 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:
| + | === 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. |
| − | * 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]
| |
| − | * 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 ===
| |
| − | 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]]
| |
| − | * [[Procedure for Creating a New Working Group]]
| |
| − | | |
| − | | |
| − | {| class="wikitable sortable"
| |
| − | |-
| |
| − | ! Pages describing Working Group or Working Teams !! Status !! Co-Chairs !! User Audience !! Tag !! Expected Outcomes
| |
| − | |-
| |
| − | | Application Developer Hackathon Working Group #[[AppDevHack-WG]] || Active || Michael Jenkins & Gonzalo De La Torre || Application Developers, DevOpps, SysAdmin, UX, Testing, etc. || #AppHack-WG || To provide advice and guidance for anyone looking to run a cloud application hackathon
| |
| − | |-
| |
| − | | [[TelcoWorkingGroup|Telco]] || Meetings subsumed into [[ProductTeam|Product Working Group]] and OpenNFV collaboration || Steve Gordon (sgordon) || Business Manager and Product Managers || #Telco-WG || 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> || Enterprise Vendors and Customers || #Enterprise-WG || Action plans to solve Enterprise Private Cloud needs and issues.
| |
| − | |-
| |
| − | | [[Application Ecosystem Working Group]] || Active || John Callaghan, Victor Diaz || Cloud Applications Developers || #AppEco-WG || To create an environment where a diverse array of applications built for OpenStack can thrive.
| |
| − | |-
| |
| − | | [[API Working Group]] || Active || Jay Pipes, Everett Toews || Operators and Application Developers || #API-WG || To propose, discuss, review, and advocate for API guidelines for all OpenStack Programs to follow.
| |
| − | |-
| |
| − | | [[Fault Genes Working Group #FaultGenes-WG]] || Active || Nemat Bidokhti || Operators and Application Developers || #Fault-WG || To create a failure mode taxonomy for Operators and Application Developers. To understand the DNA of failure in OpenStack.
| |
| − | |-
| |
| − | | [[Large Deployment Team]] || Active || Matt Van Winkle || Operators || #Deploy-WG || To discuss the needs and issues of those running large OpenStack deployments
| |
| − | |-
| |
| − | | [[LogWorkingGroup|Log Rationalisation]] || Active || Rochelle Grober, Jay Pipes || Operators || #Log-WG ||
| |
| − | |-
| |
| − | | [[AUCRecognition|AUC Recognition]] || Active || Shamail Tahir, Maish Saidel-Keesing || Whole of Community || #Recognition-WG || To assist the User Committee with defining its constituency
| |
| − | |-
| |
| − | | [[Ops Meetups Team]] || Active || Tom Fifield || Operators || #OpsMeet-Team || An open team for those who are passionate about [[Operations/Meetups|ops meetups]] to discuss and create the next successful events.
| |
| − | |-
| |
| − | | [[Osops]] (formerly [[Tools and Monitoring WG|Ops Tools]]) || Active || Joseph Bajin || Operators || #Monitor-WG || To discover and detail best practices in ops monitoring and tools, and facilitate tool sharing
| |
| − | |-
| |
| − | | [[Packaging]] || Sporadic Activity || None yet || Operators || #Package-WG || To be determined
| |
| − | |-
| |
| − | | [[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.
| |
| − | |-
| |
| − | | [[Operations/Tags|Ops Tags Team]] || Active || Tom Fifield, Subbu Allamaraju, 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.
| |
| − | |-
| |
| − | | [[User Survey Team]] || Active || Tom Fifield, Subbu Allamaraju, Jon Proulx, Shilla Saebi, Lauren Sell, Heidi Joy Tretheway || Whole of Community ||#UserSurvey-WG || The traditional group of people (user committee+foundation staff) who run the user survey.
| |
| − | |-
| |
| − | | [[Upgrades Working Group]] || Sporadic Activity || TBC || Operators || #Upgrade-WG || To ease the pain of OpenStack upgrades.
| |
| − | |-
| |
| − | | [[scientific working group]] || Active || Stig Telfer & Blair Blethwaite || Scientific Institutions Deploying, Operating and Contributing to OpenStack || #Scientific-WG || see wiki page
| |
| − | |}
| |
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:
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.
