OpenStack - User contributions [en]

CrossProjectLiaisons

2018-03-07T01:12:33Z

Kaizen:

Many of our cross-project teams need focused help for communicating with the other project teams. This page lists the people who have volunteered for that work.

== Oslo ==

There are now more projects consuming code from the Oslo incubator than we have Oslo contributors. That means we are going to need your help to make these migrations happen. We are asking for one person from each project to serve as a liaison between the project and Oslo, and to assist with integrating changes as we move code out of the incubator into libraries.

* The liaison should be active in the project and familiar with the project-specific requirements for having patches accepted, but does not need to be a core reviewer or the PTL.
* The liaison should be prepared to assist with writing and reviewing patches in their project as libraries are adopted, and with discussions of API changes to the libraries to make them easier to use within the project.
* Liaisons should pay attention to [Oslo] tagged messages on the openstack-dev mailing list.
* It is also useful for liaisons to be able to attend the Oslo team meeting ([[Meetings/Oslo]]) to participate in discussions and raise issues for real-time discussion.

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Barbican || Douglas Mendizábal || redrobot
|-
| Ceilometer || Julien Danjou || jd__
|-
| Cinder || Jay Bryant || jungleboyj
|-
| Cloudkitty || Christophe Sauthier || huats
|-
| Congress || Eric Kao || ekcs
|-
| Cue || Min Pae || sputnik13
|-
| Designate || ||
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Bhagyashri Shewale|| bhagyashris
|-
| Heat || Thomas Herve || therve
|-
| Horizon || Rob Cresswell || robcresswell
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || ||
|-
| Keystone || Lance Bragstad || lbragstad
|-
| Manila || Thomas Bechtold || toabctl
|-
| Mistral || Renat Akhmerov || rakhmerov
|-
| Murano || ||
|-
| Neutron || James Anziano || janzian
|-
| Nova || ||
|-
| [[Octavia]] || Michael Johnson || johnsom
|-
| Rally || Andrey Kurilin || andreykurilin
|-
| Sahara || Telles Nobrega, Shu Yingya || tellesnobrega, shuyingya
|-
| Senlin || Yanyan Hu || Yanyanhu
|-

| Swift || ||
|-
| Tricircle || Chaoyi Huang || joehuang
|-
| TripleO || Ben Nemec || bnemec
|-
| Trove || Manoj Kumar || kumarmn
|-
| Zaqar || Flavio Percoco || flaper87
|-
| Zun || Hongbin Lu || hongbin
|-
|}

== Release management ==

The Release Management Liaison is responsible for communication with the Release Management team. Its tasks are described in the project team guide: http://docs.openstack.org/project-team-guide/release-management.html . That task has been traditionally filled by the PTL, but they may now delegate this task if they wish.

* By default, the liaison will be the PTL.
* The liaison may further delegate work to other subject matter experts

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Barbican || Dave McCowan || dave-mccowan
|-
| Ceilometer || gordon chung || gordc
|-
| Cinder || Sean McGinnis || smcginnis
|-
| Congress || Eric Kao || ekcs
|-
| Designate || Graham Hayes || mugsie
|-
| Documentation || Petr Kovar || pkovar
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Brian Rosmaita || rosmaita
|-
| Heat || Thomas Herve || therve
|-
| Horizon || Ying Zuo || ying_zuo
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || Dmitry Tantsur || dtantsur
|-
| Keystone || Kristi Nikolla || knikolla
|-
| Kolla || Jeffrey Zhang || Jeffrey4l
|-
| Magnum || Spyros Trigazis || strigazi
|-
| Manila || Ben Swartzlander || bswartz
|-
| Mistral || Dougal Matthews || d0ugal
|-
| Murano ||Kirill Zaitsev || kzaitsev_
|-
| Neutron || Armando Migliaccio || armax
|-
| Nova || Sylvain Bauza || bauzas
|-
| OpenStackClient || Doug Hellmann || dhellmann
|-
| Oslo || Doug Hellmann || dhellmann
|-
| Packaging_Rpm || Dirk Mueller || dirk
|-
| Puppet OpenStack || Alex Schultz || mwhahaha
|-
| Rally || Andrey Kurilin || andreykurilin
|-
| Sahara || Telles Nobrega || tenobreg/tellesnobrega
|-
| Searchlight || Steve McLellan || sjmc7
|-
| Senlin || Qiming Teng || Qiming
|-
| Solum || Devdatta Kulkarni/ZhuRong || devkulkarni/zhurong
|-
| Storlets || Kota Tsuyuzaki || kota_
|-
| Swift || John Dickinson || notmyname
|-
| Tricircle || Zhiyuan Cai || zhiyuan
|-
| TripleO || Emilien Macchi || EmilienM
|-
| Trove || Manoj Kumar || kumarmn
|-
| Watcher || Alexander Chadin || alexchadin
|-
| Winstackers || Claudiu Belu || claudiub
|-
| Zaqar || Fei Long Wang || flwang
|-
| Zun || Hongbin Lu || hongbin
|}

== QA ==

There are now more projects that are being tested by Tempest, and Grenade or a part deployable by Devstack than we have QA contributors. That means we are going to need your help to keep on top of everything. We are asking for one person from each project to serve as a liaison between the project and QA, and to assist with integrating changes as we move forward.

The liaison should be a core reviewer for the project, but does not need to be the PTL. The liaison should be prepared to assist with writing and reviewing patches that interact with their project, and with discussions of changes to the QA projects to make them easier to use within the project.

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Barbican || Steve Heyman || hockeynut
|-
| Ceilometer || Chris Dent || cdent
|-
| Cinder || Scott DAngelo and Ivan Kolodyazhny || scottda and e0ne
|-
| Congress || Eric Kao || ekcs
|-
| Freezer || Guillermo Garcia || m3mo
|-
| Glance || Abhishek Kekane || abhishekk
|-
| Heat || Steve Baker || stevebaker
|-
| Horizon || Rob Cresswell || robcresswell
|-
| Ironic || ||
|-
| Keystone || Rodrigo Duarte || rodrigods
|-
| Manila || Dustin Schoenbrun || dustins
|-
| Murano || Victor Ryzhenkin || freerunner
|-
| Neutron || Kevin Benton || kevinbenton
|-
| Nova || Matt Riedemann || mriedem
|-
| Oslo || Davanum Srinivas || dims
|-
| Sahara || Luigi Toscano || tosky
|-
| Senlin || Haiwei Xu || haiwei-xu
|-
| Swift || Thiago da Silva || tdasilva
|-
| Trove || Craig Vyvial and Nirav Shah || cp16net and nshah
|-
| Zaqar || Fei Long Wang || flwang
|-
| Zun || Hongbin Lu || hongbin
|}

== Documentation ==

The OpenStack Documentation is centralized on docs.openstack.org but often there's a need for specialty information when reviewing patches or triaging doc bugs. A doc liaison should be available to triage doc bugs when the docs team members don't know enough to triage accurately, and be added to doc reviews that affect your project. You'd be notified through email when you're added either to a doc bug or a doc review. We also would appreciate attendance at the [https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting weekly doc team meeting], We meet weekly in #openstack-meeting every Wednesday at alternating times for different timezones:

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Barbican || Douglas Mendizábal || redrobot
|-
| Ceilometer || Ildiko Vancsa || ildikov
|-
| Cinder || Jay Bryant || jungleboyj
|-
| Congress || Aimee Ukasick || aimeeu
|-
| Designate || Graham Hayes || mugsie
|-
| Freezer || Guillermo Garcia || m3mo
|-
| Heat || Rabi Mishra || ramishra
|-
| Horizon || Rob Cresswell || robcresswell
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || Julia Kreger || TheJulia
|-
| Keystone || Lance Bragstad || lbragstad
|-
| Kolla || ||
|-
| Magnum || Spyros Trigazis || strigazi
|-
| Manila || Ben Swartzlander || bswartz
|-
| Mistral || Dougal Matthews || d0ugal
|-
| Murano || Kirill Zaitsev || kzaitsev_
|-
| Neutron || Boden Russel || boden
|-
| Nova || Zhenyu Zheng, Nicolas Bock || Kevin_Zheng, nicolasbock
|-
| OpenStack-Ansible || Amy Marrich || spotz
|-
| Ops || Robert Starmer ||
|-
| Oslo || Doug Hellmann || dhellmann
|-
| Puppet OpenStack || Emilien Macchi || EmilienM
|-
| Rally || Boris Pavlovic || boris-42
|-
| Sahara || Telles Nobrega and Elise Gafford || tellesnobrega egafford
|-
| Senlin || Cindia Blue || lixinhui
|-
| Swift || John Dickinson || notmyname
|-
| Tripleo || Steven Hardy || shardy
|-
| Trove || Trevor McCasland || trevormc
|-
| Watcher || Prudhvi Rao Shedimbi || pshedimb
|-
| Zaqar || Fei Long Wang || flwang
|-
| Zun || Hongbin Lu || hongbin
|}

== Stable Branch ==

The Stable Branch Liaison is responsible for making sure backports are proposed for critical issues in their project, and make sure proposed backports
are reviewed. They are also the contact point for stable branch release managers around point release times.

* By default, the liaison will be the PTL.
* The Stable Branch Liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in its PTL election.
* The liaison may further delegate work to other subject matter experts

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Barbican || Dave McCowan || dave-mccowan
|-
| Ceilometer || Eoghan Glynn || eglynn
|-
| Cinder || Jay Bryant || jungleboyj
|-
| Congress || Masahito Muroi || masahito
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Erno Kuvaja || jokke_
|-
| Heat || Zane Bitter || zaneb
|-
| Horizon || Rob Cresswell || robcresswell
|-
| Ironic || Dmitry Tantsur || dtantsur
|-
| Keystone || Colleen Murphy || cmurphy
|-
| Mistral || Renat Akhmerov || rakhmerov
|-
| Murano || Kirill Zaitsev || kzaitsev_
|-
| Neutron || Ihar Hrachyshka || ihrachys
|-
| Nova || Matt Riedemann || mriedem
|-
| Sahara || Vitaly Gridnev || vgridnev
|-
| Senlin|| Qiming Teng || Qiming
|-
| Swift || Matthew Oliver || mattoliverau
|-
| Trove || Sam Matzek || smatzek
|-
| Watcher || David Tardivel || dtardivel
|-
| Zaqar || Fei Long Wang || flwang
|-
|}

== Vulnerability management ==

The Vulnerability Management Team needs domain specialists to help assessing the impact of reported issues, coordinate the development of patches, review proposed patches and propose backports. The liaison should be familiar with the [https://security.openstack.org/vmt-process.html Vulnerability Management process] and embargo rules, and have a good grasp of security issues in software design.

* The liaison should be a core reviewer for the project, but does not need to be the PTL.
* By default, the liaison will be the PTL.
* The liaison is the first line of contact for the Vulnerability Management team members
* The liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in election its PTL
* The liaison may further delegate work to other subject matter experts
* The liaison maintains the members of the $PROJECT-coresec team in Launchpad (which can be given access to embargoed vulnerabilities)

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Barbican || Douglas Mendizábal or Charles Neill || redrobot / ccneill
|-
| Ceilometer || Lianhao Lu or Gordon Chung || llu/gordc
|-
| Cinder || ||
|-
| Congress || Masahito Muroi || masahito
|-
| Freezer || Saad Zaher or Pierre Mathieu || szaher or slashme
|-
| Glance || Brian Rosmaita || rosmaita
|-
| Heat || Steve Hardy || shardy
|-
| Horizon || Rob Cresswell || robcresswell
|-
| Ironic || ||
|-
| Keystone || Gage Hugo || gagehugo
|-
| Kolla || Michal Jastrzebski || inc0
|-
| Manila || Tom Barron || tbarron
|-
| Murano || Victor Ryzhenkin || freerunner
|-
| Neutron || Kevin Benton || kevinbenton
|-
| Nova || Michael Still || mikal
|-
| OpenStack-Ansible || Major Hayden || mhayden
|-
| Sahara || Telles Nobrega || tellesnobrega
|-
| Searchlight || Travis Tripp or Steve McLellan || TravT or sjmc7
|-
| Senlin || Qiming Teng || Qiming
|-
| Swift || ||
|-
| Trove || Manoj Kumar || kumarmn
|-
| Zaqar || Fei Long Wang || flwang
|-
|}

== API Working Group ==

The [[API_Working_Group|API Working Group]] seeks API subject matter experts for each project to communicate plans for API updates, review API guidelines with their project's view in mind, and review the API Working Group guidelines as they are drafted. The liaison should be familiar with the project's REST API design and future planning for changes to it.

The members of the [http://specs.openstack.org/openstack/api-wg/liaisons.html API Working Group Cross-Project Liaisons] are maintained in our repo. If you want to read the entire list of CPLs or add/remove yourself from the list, you'll need to update the [http://git.openstack.org/cgit/openstack/api-wg/tree/doc/source/liaisons.json liaisons.json] file. If you don't want to make the update yourself, please ask in #openstack-sdks on IRC and someone can make the change for you.

== Logging Working Group ==

The [[LogWorkingGroup|Log Working Group]] seeks experts for each project to assist with making the logging in projects match the new [http://specs.openstack.org/openstack/openstack-specs/specs/log-guidelines.html Logging Guidelines]

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Ironic || ||
|-
| Oslo || Doug Hellmann || dhellmann
|-
| Nova || John Garbutt || johnthetubaguy
|-
| Murano || ||
|-
| Sahara || Elise Gafford || egafford
|}

== Infra ==

These are the project specific groups of people that Infra will look to ACK changes to that project's test configuration. Changes to project-config and devstack-gate should be +1'd by these groups when they are related to their project. Note that in an emergency this may not always be possible and Infra will ask for forgiveness but generally we should look for these +1s.

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Congress || Any Congress core reviewer may ACK: Anusha Ramineni, Eric Kao, Tim Hinrichs, Masahito Muroi || ramineni, ekcs, thinrichs, masahito
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || ||
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || Dmitry Tantsur || dtantsur
|-
| Kolla || Any Kolla Core Reviewer may ack an infra change on behalf of the PTL || inc0, jeffrey4l, kfox1111, pbourke, sdake are primary contacts
|-
| Neutron || Ihar Hrachyshka, Armando Migliaccio, YAMAMOTO Takashi || ihrachys, armax, yamamoto
|-
| Documentation || Andreas Jaeger|| AJaeger

|-
| Trove || Manoj Kumar || kumarmn

|-
| Murano || Victor Ryzhenkin || freerunner

|-
| Sahara || Vitaliy Gridnev || Vitaliy Gridnev

|-
| Fuel || Aleksandra Fedorova, Igor Belikov || bookwar, igorbelikov
|-
| OpenStack-Ansible || Jean-Philippe Evrard, Jesse Pretorius || evrardjp, odyssey4me
|-
| Puppet OpenStack || Emilien Macchi, Alex Schultz || EmilienM, mwhahaha

|-
| TripleO || Emilien Macchi || EmilienM
|}

== I18n ==
I18n team is responsible for making OpenStack ubiquitously accessible to people of all language backgrounds. The team have translators from all over the world to translate OpenStack into different languages.

If you want to communicate with translators in I18n team, send email to openstack-i18n@lists.openstack.org.

* The liaison should be a core reviewer (or a person who is not a core reviewer but agreed & approved by PTL) for the project and understand i18n status of the project.
* The liaison should understand project release schedule very well.
* The liaison should notify I18n team happens of important moments in the project release in time. For example, happen of soft string freeze, happen of hard string freeze, and happen of RC1 cutting.
* The liaison should take care of translation patches to the project, and make sure the patches are successfully merged to the final release version. When the translation patch is failed, the liaison should notify I18n team.

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Barbican || ||
|-
| Cinder || ||
|-
| Designate || Graham Hayes || mugsie
|-
| Glance || Brian Rosmaita || rosmaita
|-
| Heat || ||
|-
| Horizon || Akihiro Motoki || amotoki
|-
| Ironic || ||
|-
| Keystone || ||
|-
| Magnum || Shu Muto || shu-mutou
|-
| Manila || ||
|-
| Monasca || ||
|-
| Murano || ||
|-
| Neutron || Akihiro Motoki || amotoki
|-
| Nova || ||
|-
| Oslo || ||
|-
| Sahara || Luigi Toscano, Jeremy Freudberg || tosky, jeremyfreudberg
|-
| Senlin || ||
|-
| Swift || ||
|-
| Tacker || ||
|-
| Telemetry || ||
|-
| TripleO || Julie Pichon || jpich
|-
| Trove || ||
|-
| Sahara || Chad Roberts || crobertsrh
|-
| Watcher || Yumeng Bao || Yumeng
|-
| Zaqar || ||
|-
|}

== Inter-project Liaisons ==

In some cases, it is useful to have liaisons between projects. [http://lists.openstack.org/pipermail/openstack-dev/2015-April/062327.html For example, it is useful for the Nova and Neutron projects to have liaisons, because the projects have complex interactions and dependencies.] Ideally, a cross-project effort should have two members, one from each project, to facilitate communication and knowledge transfer.

{| class="wikitable"
|-
! Projects !! Name !! IRC Handle !! Role
|-
| Nova / Neutron || || ||
|-
| || Sean K. Mooney || sean-k-mooney || Neutron liaison for Nova
|-
| Nova / Cinder || || ||
|-
| || Ildiko Vancsa || ildikov || Cinder liaison for Nova
|-
| || Matt Riedemann || mriedem || Nova liason for Cinder
|-
| Nova / Ironic || || ||
|-
| || Dmitry Tantsur || dtantsur || Ironic liaison for Nova
|-
| Neutron / Ironic || || ||
|-
| || Sukhdev Kapur || sukhdev || Neutron liaison for Ironic
|-
| || Sam Betts || sambetts || Ironic liaison for Neutron
|-
| Horizon / i18n || || ||
|-
| || Akihiro Motoki || amotoki || Horizon liaison for i18n
|-
| || TBD || || Heat liaison for Sahara
|-
| Fuel / Puppet || || ||
|-
| || Alex Schultz || mwhahaha || Fuel liaison for Puppet
|-
| Fuel / Ironic || || ||
|-
| || Evgeny L || evgenyl || Fuel liaison for Ironic
|-
| Bareon / Ironic || || ||
|-
| || Evgeny L || evgenyl || Bareon liaison for Ironic
|-
| Magnum / Kuryr || || ||
|-
| || Ton Ngo || tango || Magnum liaison for Kuryr
|-
| || Fawad Khaliq || fawadkhaliq || Kuryr liaison for Magnum
|-
| TripleO / Ironic || || ||
|-
| || Dmitry Tantsur || dtantsur || Ironic liaison for TripleO
|-
| Nova / Watcher || || ||
|-
| || Ed Leafe || edleafe || Nova liaison for Watcher
|}

=== Etherpads ===

The following is a list of etherpads that are used for inter-project liaisons, and are continuously updated.

Nova - Neutron: https://etherpad.openstack.org/p/nova-neutron

== Cross-Project Spec Liaisons ==

The OpenStack project relies on the cross-project spec liaisons from each participating project to help with coordination and cross-project spec related tasks. See full set of [http://docs.openstack.org/project-team-guide/cross-project.html#cross-project-specification-liaisons responsibilities] The liaison defaults to the PTL, but the PTL can also delegate the responsibilities to someone else on the team by updating this tableː

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Barbican || Douglas Mendizabal || redrobot
|-
| Cinder || Kendall Nelson || diablo_rojo
|-
| Congress || Eric Kao || ekcs
|-
| Cue || Min Pae || sputnik13
|-
| Designate || Graham hayes || mugsie
|-
| Dragonflow || Gal Sagie || gsagie
|-
| Freezer || Pierre Mahieu || slashme
|-
| Fuel || Andrew Woodward || xarses
|-
| Glance || ||
|-
| Heat || Rico Lin || ricolin
|-
| Horizon || David Lyle || david-lyle
|-
| Infrastructure || Matthew Wagoner || olaph
|-
| Ironic || ||
|-
| Keystone || Samuel de Medeiros Queiroz || samueldmq
|-
| Kolla || Swapnil Kulkarni || coolsvap
|-
| Kuryr || Gal Sagie || gsagie
|-
| Magnum || Adrian Otto || adrian_otto
|-
| Manila || Ben Swartzlander || bswartz
|-
| Mistral || Renat Akhmerov || rakhmerov
|-
| Monasca || Roland Hochmuth || rhochmuth
|-
| Murano || Kirill Zaitsev || kzaitsev_
|-
| Neutron || Kevin Benton || kevinbenton
|-
| Nova || Chris Dent || cdent
|-
| Oslo || Davanum Srinivas || dims
|-
| Puppet OpenStack || Alex Schultz || mwhahaha
|-
| Sahara || Telles Nobrega || tellesnobrega
|-
| Searchlight || Steve McLellan || sjmc7
|-
| Senlin || Qiming Teng || Qiming
|-
| Solum || Devdatta Kulkarni || devkulkarni
|-
| Swift || John Dickinson || notmyname
|-
| Tacker || Sridhar Ramaswamy || sridhar_ram
|-
| Telemetry || Gordon Chung || gordc
|-
| Trove || Maciej Jozefczyk || mjozefcz
|-
| Watcher || Susanne Balle || sballe
|-
| Zaqar || Fei Long Wang || flwang
|-
| Zun || Hongbin Lu || hongbin
|}

Governance/Foundation/UserCommittee

2017-12-18T13:56:56Z

Kaizen: /* Meeting Agenda/Previous Meeting Logs */

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 user committee mission is to:

* 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
* 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

[1]= the User Committee may request an agenda item for the Board's meeting.

== How to Engage? ==
The User Committee coordinates via the [http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee user-commitee mailing list] - feel free to join and post your ideas as well as via IRC on freenode in #openstack-uc channel. Consider joining the [https://governance.openstack.org/uc/#working-groups working groups] and [https://governance.openstack.org/uc/#teams teams] under UC governance found [https://governance.openstack.org/uc/ here].
 
Attend our weekly IRC meetings on Monday at 1800 UTC in #openstack-meeting NOTE: if there are no agenda items that need to be discussed then the meeting will be cancelled and a notification sent out via the mailing list.

== Meeting Agenda/Previous Meeting Logs ==

Future Proposed Meeting: "Monday, Dec 25, 2017 at 1800 UTC - Even Week" in (freenode) #openstack-uc
1. No meeting?

Future Proposed Meeting: "Monday, Dec 18, 2017 at 1400 UTC - Odd Week" in (freenode) #openstack-uc
1. Roll call
2. SIG Governance
3. Holiday meeting - cancel or keep?

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 ==

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 ===
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"
|-
! 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 Bethwaite & Martial Michel || Scientific Institutions Deploying, Operating and Contributing to OpenStack || #Scientific-WG || see wiki page
|}

Governance/Foundation/UserCommittee

2017-10-09T15:37:25Z

Kaizen: /* Meeting Agenda/Previous Meeting Logs */

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 user committee mission is to:

* 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
* 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

[1]= the User Committee may request an agenda item for the Board's meeting.

== How to Engage? ==
The User Committee coordinates via the [http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee user-commitee mailing list] - feel free to join and post your ideas as well as via IRC on freenode in #openstack-uc channel. Consider joining the [https://governance.openstack.org/uc/#working-groups working groups] and [https://governance.openstack.org/uc/#teams teams] under UC governance found [https://governance.openstack.org/uc/ here].
 
Attend our weekly IRC meetings on Monday at 1800 UTC in #openstack-meeting NOTE: if there are no agenda items that need to be discussed then the meeting will be cancelled and a notification sent out via the mailing list.

== Meeting Agenda/Previous Meeting Logs ==

Future Proposed Meeting: "Monday, Oct. 9th, 2017 at 1800 UTC" in (freenode) #openstack-meeting

1. Roll call
2. Review action items from previous meeting
3. Discuss next steps with User Survey
4. Discuss proposal to shift UC meeting to 1600 UTC (Saverio)
5. New contributor portal (mrhillsman)
6. Open Discussion

Previous Agenda: "Monday, Sep 11, 2017 at 1800 UTC" in (freenode) #openstack-meeting

1. Review action items from last meeting
2. UC User Survey status update - Allison
3. Open Discussion

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 ==

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 ===
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"
|-
! 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 Bethwaite & Martial Michel || Scientific Institutions Deploying, Operating and Contributing to OpenStack || #Scientific-WG || see wiki page
|}

Governance/Foundation/UserCommittee

2017-10-09T03:29:46Z

Kaizen: /* Meeting Agenda/Previous Meeting Logs */

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 user committee mission is to:

* 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
* 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

[1]= the User Committee may request an agenda item for the Board's meeting.

== How to Engage? ==
The User Committee coordinates via the [http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee user-commitee mailing list] - feel free to join and post your ideas as well as via IRC on freenode in #openstack-uc channel. Consider joining the [https://governance.openstack.org/uc/#working-groups working groups] and [https://governance.openstack.org/uc/#teams teams] under UC governance found [https://governance.openstack.org/uc/ here].
 
Attend our weekly IRC meetings on Monday at 1800 UTC in #openstack-meeting NOTE: if there are no agenda items that need to be discussed then the meeting will be cancelled and a notification sent out via the mailing list.

== Meeting Agenda/Previous Meeting Logs ==

Future Proposed Meeting: "Monday, Oct. 9th, 2017 at 1800 UTC" in (freenode) #openstack-meeting

1. Roll call
2. Review action items from previous meeting
3. Discuss next steps with User Survey
4. Open Discussion

Previous Agenda: "Monday, Sep 11, 2017 at 1800 UTC" in (freenode) #openstack-meeting

1. Review action items from last meeting
2. UC User Survey status update - Allison
3. Open Discussion

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 ==

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 ===
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"
|-
! 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 Bethwaite & Martial Michel || Scientific Institutions Deploying, Operating and Contributing to OpenStack || #Scientific-WG || see wiki page
|}

Governance/Foundation/UserCommittee

2017-09-25T13:55:51Z

Kaizen: /* Meeting Agenda/Previous Meeting Logs */

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 user committee mission is to:

* 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
* 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

[1]= the User Committee may request an agenda item for the Board's meeting.

== How to Engage? ==
The User Committee coordinates via the [http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee user-commitee mailing list] - feel free to join and post your ideas as well as via IRC on freenode in #openstack-uc channel. Consider joining the [https://governance.openstack.org/uc/#working-groups working groups] and [https://governance.openstack.org/uc/#teams teams] under UC governance found [https://governance.openstack.org/uc/ here].
 
Attend our weekly IRC meetings on Monday at 1800 UTC in #openstack-meeting NOTE: if there are no agenda items that need to be discussed then the meeting will be cancelled and a notification sent out via the mailing list.

== Meeting Agenda/Previous Meeting Logs ==

Future Proposed Meeting: "Monday, Sep 25, 2017 at 1800 UTC" in (freenode) #openstack-meeting

1. Roll call
2. Review action items from last meeting
3. Discuss next steps with user survey review, including both quantitative and qualitative analysis. I would like to propose scheduling a separate meeting next week to dive into questions / comments around the analysis and will propose a few times. (aprice)
4. Forum Topic Submissions
5. Open Discussion

Previous Agenda: "Monday, Sep 11, 2017 at 1800 UTC" in (freenode) #openstack-meeting

1. Review action items from last meeting
2. UC User Survey status update - Allison
3. Open Discussion

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 ==

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 ===
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"
|-
! 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 Bethwaite & Martial Michel || Scientific Institutions Deploying, Operating and Contributing to OpenStack || #Scientific-WG || see wiki page
|}

Governance/Foundation/UserCommittee

2017-07-28T15:44:47Z

Kaizen: /* Meeting Agenda/Previous Meeting Logs */

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 user committee mission is to:

* 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
* 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

[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.

 
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. 

== Meeting Agenda/Previous Meeting Logs ==

Future Proposed Meeting: '''Monday, July 31, 2017 at 1800 UTC''' in (freenode) #openstack-meeting
 
1. Review request from Public Cloud WG to be under UC governance (Tobias Rydberg)
* Criteria can be found at https://governance.openstack.org/uc/reference/new-uc-group-requirements.html
2. UC Election Planning Update

Previous Agenda: '''Monday, July 24, 2017 at 1800 UTC''' in (freenode) #openstack-meeting
 
1. Review outcome from last Wednesday UC WG Status meeting: . http://eavesdrop.openstack.org/meetings/uc/2017/uc.2017-07-19-05.03.log.html Possible next steps to finalize:
* Use Openstack-UC IRC as ongoing/virtual WG status
* Contact other WG leads to add their status
* Share IRC or perhaps summary with MLs: UC, Operators, SIGS, TC, Foundation?
2. UC meeting as Video Conference and IRC.

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 ==

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 ===
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"
|-
! 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 Bethwaite & Martial Michel || Scientific Institutions Deploying, Operating and Contributing to OpenStack || #Scientific-WG || see wiki page
|}

Meetings/product-team

2017-07-24T19:23:41Z

Kaizen: /* July 24th, 2017 (Monday @ 2100 UTC) Product Team Meeting Agenda */

= July 24th, 2017 (Monday @ 2100 UTC) Product Team Meeting Agenda =
* Review of action items

* Virtual Product WG Midcycle
** Finalize Agenda and decide how many days needed
** https://etherpad.openstack.org/p/VIR-pwg-meetup-2017q3

* Sydney Summit/Forum preparation
** Planning for sessions
*** Working Sessions
*** BoF
*** Roadmap

* Review PWG Repo / Dev Proposal
** https://review.openstack.org/#/q/project:openstack/development-proposals+status:open

* Open

 

''Information on previous agendas: https://etherpad.openstack.org/p/pwg_previous_agendas''

Governance/Foundation/UserCommittee

2017-07-16T20:26:42Z

Kaizen: /* Meeting Agenda/Previous Meeting Logs */

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 user committee mission is to:

* 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
* 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

[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.

 
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. 

== Meeting Agenda/Previous Meeting Logs ==

Future Proposed Meeting: '''Wednesday, July 19, 2017 at 0500 UTC''' as a Video Conference and also in (freenode) #openstack-meeting
 
Note that this is 1AM US ET, but daytime for Most of the World (not US)
 
1. Status Updates from the Working Groups. Expected that we will go down the WG list below and the WG Chairs or their delegate will outline their current efforts with aim to encourage more collaboration.
* Things that may overlap other WG or project teams should be highlighted.
* Q&A aimed at bringing more people to out subsequent WG sessions (the session we have in progress and clarify the date/time and method).
It's anticipated this will be a monthly topic.

Next meeting: '''Monday, July 10, 2017 at 1800 UTC''' in (freenode) #openstack-meeting
 
1. Review AUC and Extra-AUC Patch (https://review.openstack.org/#/c/479462/)
2. Review addition of WG/Team Requirements as UC reference doc (https://review.openstack.org/#/c/484208/)
3. SIG Update (Mailing List and Meta SIG Discussion)
4. Review attendance/agenda for July 19th WG Updates meeting
5. Discuss sessions submitted for Sydney Summit that require UC assistance (if any)
6. Open Discussion

Previous Agenda: July 10, 2017 Discussion Items
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 July 19 0500UTC. http://lists.openstack.org/pipermail/user-committee/2017-June/002107.html. Note that a followup e-mail was sent by Edgar to all WG chairs. I've also added the proposed July 19 above.
2. Finalize WG/Team requirements document. Even though SIGs concept is still being discussed, this document is needed for current existing WG/Team - https://docs.google.com/document/d/1r3KwaG-SbvaKCuAE52XwPCF7cRGDrNRg6dUhPQWs0vU
3. Review extra-aucs patch - https://review.openstack.org/#/c/479462/ - we should also discuss with Tom as there may already be code in place to capture this.
4. Open Discussion

Previous Agenda/Etherpad from Boston Summit: https://etherpad.openstack.org/p/BOS-forum-user-committee-session

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 ==

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 ===
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"
|-
! 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 Bethwaite & Martial Michel || Scientific Institutions Deploying, Operating and Contributing to OpenStack || #Scientific-WG || see wiki page
|}

Governance/Foundation/UserCommittee

2017-06-16T16:32:16Z

Kaizen: /* Meeting Agenda/Previous Meeting Logs */

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 user committee mission is to:

* 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
* 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

[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].
 
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. 

== Meeting Agenda/Previous Meeting Logs ==
Next meeting: '''Monday, June 19, 2017 at 1800 UTC''' in (freenode) #openstack-meeting
 
Upcoming Session: June 19
- TBD

Previous Agenda: June 12, 2017:
- 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/Etherpad from Boston Summit: https://etherpad.openstack.org/p/BOS-forum-user-committee-session

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 ==

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 ===
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"
|-
! 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
|}

Governance/Foundation/UserCommittee

2017-06-01T15:54:00Z

Kaizen: /* Meeting Agenda/Previous Meeting Logs */

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 user committee mission is to:

* 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
* 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

[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].
 
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. 

== Meeting Agenda/Previous Meeting Logs ==
Next meeting: '''Monday, June 5, 2017 at 1800 UTC''' in (freenode) #openstack-meeting
 
Upcoming Session: June 5
- Action Items from previous meetings
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
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:
- Recap UC Session at the Ops Meetup (10min)
- 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 ==

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 ===
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"
|-
! 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
|}

Forum/Boston2017

2017-05-05T21:20:49Z

Kaizen: /* Thursday */

The grand list of all of the Boston 2017 Forum etherpads. Please include Date, Time, and links to etherpads when adding new content. An [https://etherpad.openstack.org/p/BOS-forum-moderator-template etherpad template] (optional) is available if you need one.

'''See also - [https://www.openstack.org/summit/boston-2017/summit-schedule/#track=146 Full Forum Schedule]'''

'''See also - [[Forum/Boston2017#Thursday_Afternoon_session_sign-up|Thursday Afternoon session signup]]'''

'''See also - [https://ethercalc.openstack.org/Boston_Forum_Hacking_Rooms Hacking Rooms Schedule]'''

<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3">
__NOTOC__
</div>

= Event intro/closure =
* Forum 101 - https://etherpad.openstack.org/p/BOS-forum-101
* Boston feedback session - https://etherpad.openstack.org/p/BOS-summit-feedback

= Monday =
* [11:15am-11:55am] - Operating the VM and Baremetal platform (1/2) - https://etherpad.openstack.org/p/BOS-forum-operating-vm-and-baremetal
* [11:15am-12:45pm] - Nova - Project Onboarding - https://etherpad.openstack.org/p/BOS-forum-nova-project-onboarding
* [12:05pm-12:45pm] - OpenStack documentation: The future depends on all of us -
* [12:05pm-12:45pm] - WG chairs collaboration and WG overviews - https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews
* [2:00pm-2:40pm] - Evolving the Community Generated Roadmap - https://etherpad.openstack.org/p/BOS-forum-evolving-the-community-generated-roadmap
* [2:50pm-3:30pm] - Evolving the User Survey - https://etherpad.openstack.org/p/BOS-forum-evolving-the-user-survey
* [2:50pm-3:30pm] - Future of Configuration Management - https://etherpad.openstack.org/p/BOS-forum-future-of-configuration-management
* [3:40pm-4:20pm] - Making keystone consumable outside of OpenStack - https://etherpad.openstack.org/p/BOS-forum-consumable-keystone
* [4:40pm-5:20pm] - Next steps for RBAC and policy - https://etherpad.openstack.org/p/BOS-forum-next-steps-for-rbac-and-policy
* [4:40pm-5:20pm] - Should we kill Stackalytics? - https://etherpad.openstack.org/p/BOS-forum-should-we-kill-stackalytics
* [5:30pm-6:10pm] - Using Searchlight to list instances across cells in nova-api - https://etherpad.openstack.org/p/BOS-forum-using-searchlight-to-list-instances

= Tuesday =
* [11:15am-11:55am] Feedback from Users for I18n & Translation - Important Part? - https://etherpad.openstack.org/p/BOS-forum-i18n-translation-feedback-from-users
* [12:05pm-12:45pm] Enhancing Log Message Headers for RT Debug and Traceability - https://etherpad.openstack.org/p/BOS-forum-log-messages
* [12:05pm-12:45pm] LCOO Roadmap Working Session - https://etherpad.openstack.org/p/BOS-forum-LCOORoadmap
* [2:00pm-2:40pm] ETSI NFV Specs’ Requirements vs OpenStack Reality - https://etherpad.openstack.org/p/BOS-ETSI-NFV-Specs-Reqs-vs-OpenStack-Reality
* [2:00pm-2:40pm] Swift ops feedback session - https://etherpad.openstack.org/p/BOS-Swift-ops-feedback-session
* [2:00pm-3:30pm] Barbican and Security Projects Onboarding - https://etherpad.openstack.org/p/BOS-forum-barbican-onboarding
* [2:50pm-3:30pm] Skip-level upgrading - jumping ahead to catch up - https://etherpad.openstack.org/p/BOS-forum-skip-level-upgrading
* [4:40pm-5:20pm] Using Cinder for Nova Ephemeral Storage Backend - https://etherpad.openstack.org/p/BOS-forum-using-cinder-for-nova-ephemeral-storage
* [5:30pm-6:10pm] Features missing in OpenStack core for Public Cloud provider - https://etherpad.openstack.org/p/BOS-forum-Features-Missing-For-Public-Clouds

= Wednesday =
* [9:00am-9:40am] Oslo developer/operator feedback - https://etherpad.openstack.org/p/BOS-Oslo-brainstorming
* [9:00am-9:40am] Special hardware - https://etherpad.openstack.org/p/BOS-forum-special-hardware
* [9:00am-9:40am] Collaboration between Telecom/NFV related groups - https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration
* [9:50am-10:30am] oslo.messaging: Recommendations for Non-RabbitMQ Backends - https://etherpad.openstack.org/p/BOS_Forum_Oslo.Messaging_driver_recommendations
* [9:50am-10:30am] Vitrage Usability and New Insights: Where Do We Go Next? - https://etherpad.openstack.org/p/BOS-forum-vitrage-usability-and-new-insights
* [11:00am-11:40am] Compliance/Security Certification for upstream OpenStack - https://etherpad.openstack.org/p/BOS-forum-Compliance-Security-Certification
* [11:00am-11:40am] - Operating the VM and Baremetal platform (2/2) - https://etherpad.openstack.org/p/BOS-forum-operating-vm-and-baremetal
* [1:50pm-2:30pm] Kubernetes Ops on OpenStack - https://etherpad.openstack.org/p/BOS-forum-kubernetes-ops-on-openstack
* [1:50pm-2:30pm] App Developer Enablement - https://etherpad.openstack.org/p/BOS-forum-app-dev-enablement
* [1:50pm-2:30pm] Keystone Operator Feedback - https://etherpad.openstack.org/p/BOS-forum-keystone-operator-feedback
* [2:40pm-3:20pm] Product WG Working Session - https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session
* [2:40pm-3:20pm] Key Management Developer/Operator/Community Coordination - https://etherpad.openstack.org/p/BOS-forum-key-management
* [3:30pm-4:10pm] Compute Instance/Volume Affinity for HPC - https://etherpad.openstack.org/p/BOS-forum-compute-instance-volume-affinity-hpc
* [4:30pm-5:10pm] Moving Resource Claims from nova-compute to nova-scheduler - https://etherpad.openstack.org/p/BOS-forum-move-claims-from-compute-to-scheduler
* [4:30pm-5:10pm] Ops Tags WG session - https://etherpad.openstack.org/p/BOS-forum-ops-tags-wg-session
* [5:20pm-6:00pm] Large Heat Stacks (users/ops/developers) - https://etherpad.openstack.org/p/BOS-forum-Large-Heat-stacks

= Thursday =
* [9:00am-9:40am] Users/Operators: Contributing Multi-Project Requirements - https://etherpad.openstack.org/p/BOS-forum-contributing-multi-project-requirements
* [9:00am - 9:40am] Users / Operators adoption of QA tools / plugins - https://etherpad.openstack.org/p/BOS-forum-qa-tools-plugins
* [9:50am-10:30am] - Writing Applications for the VM and Baremetal Platform - https://etherpad.openstack.org/p/BOS-forum-using-vm-and-baremetal
* [11:00am-12:30pm] Queens Goals - https://etherpad.openstack.org/p/BOS-forum-Queens-Goals
* [11:50am-12:30pm] Shared Commercial Goals for OpenStack Public Cloud Providers - https://etherpad.openstack.org/p/BOS-forum-Shared-Commercial-Goals-Public-Clouds
* [1:30pm-2:10pm] User Committee Session - https://etherpad.openstack.org/p/BOS-forum-user-committee-session
* [2:20pm-3:00pm] Cloud-aware Application Support - https://etherpad.openstack.org/p/pike-forum-cloud-applications
* [5:00pm-5:40pm] UC Governance and Support of WGs - https://etherpad.openstack.org/p/BOS-forum-uc-governance-and-support-of-wgs

==Thursday Afternoon session sign-up==
If something new comes up during the week, or a session runs over and you need more time, please sign up for another Fishbowl slot on Thursday Afternoon here:

<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3">
* 1:30-2:10 MR102 - available
* 2:20-3:00 MR102 - available
* 3:10-3:50 MR102 - available
* 3:50-4:10 MR102 - available
* 4:10-4:50 MR102 - available
* 5:00-5:40 MR102 - available
* 1:30-2:10 MR103 - available
* 2:20-3:00 MR103 - [https://etherpad.openstack.org/p/pike-forum-cloud-applications Cloud-aware Application Support]
* 3:10-3:50 MR103 - available
* 3:50-4:10 MR103 - available
* 4:10-4:50 MR103 - available
* 5:00-5:40 MR103 - available
* 1:30-2:10 MR104 - available
* 2:20-3:00 MR104 - available
* 3:10-3:50 MR104 - available
* 3:50-4:10 MR104 - available
* 4:10-4:50 MR104 - available
* 5:00-5:40 MR104 - [https://etherpad.openstack.org/p/pike-forum-tc-gathering TC members open gathering]
</div>

░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░

==(old) Brainstorming==
Below here were the etherpads used during the agenda brainstorming process...

====Catch-alls====
* [https://etherpad.openstack.org/p/BOS-TC-brainstorming TC Catch-all]
* [https://etherpad.openstack.org/p/BOS-UC-brainstorming UC Catch-all]

====Project Teams====

=====Barbican=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Barbican-brainstorming

=====Cinder=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Cinder-brainstorming

=====Freezer=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Freezer-brainstorming

=====Glance=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Glance-brainstorming

=====Heat=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Heat-brainstorming

=====I18n=====
Brainstorming: https://etherpad.openstack.org/p/BOS-I18n-brainstorming

=====Ironic=====
Brainstorming: https://etherpad.openstack.org/p/BOS-ironic-brainstorming

=====Keystone=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Keystone-brainstorming

=====Nova=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Nova-brainstorming

=====Oslo=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Oslo-brainstorming

=====Watcher=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Watcher-brainstorming

=====QA=====
Brainstorming: https://etherpad.openstack.org/p/BOS-QA-brainstorming

=====Swift=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Swift-brainstorming

====UC Working Groups ====

=====Telecom/NFV Requirements=====
https://etherpad.openstack.org/p/BOS-UC-brainstorming-Telecom&NFV

=====Scientific WG=====
https://etherpad.openstack.org/p/BOS-UC-brainstorming-scientific-wg

=====Massively Distributed (Fog/Edge) WG=====
https://etherpad.openstack.org/p/BOS-UC-brainstorming-MassivelyDistributed-Fog-Edge

=====Public Cloud WG=====
https://etherpad.openstack.org/p/publiccloud-boston-forum-session

====Other Working Groups====

=====VM and Bare-metal platform group=====

Developer lead group looking for user and operator feedback around the user experience across Nova, Ironic, Cinder and Neutron. Looking at both humans using the system, those operating the system, and projects building on the "VM and Bare-metal" platform. Main activity will be ranking the relative priority of current efforts, and looking to identify any gaps.

https://etherpad.openstack.org/p/BOS-TC-vm-baremetal-platform

Forum/Boston2017

2017-05-05T21:07:35Z

Kaizen: /* Thursday */

The grand list of all of the Boston 2017 Forum etherpads. Please include Date, Time, and links to etherpads when adding new content. An [https://etherpad.openstack.org/p/BOS-forum-moderator-template etherpad template] (optional) is available if you need one.

'''See also - [https://www.openstack.org/summit/boston-2017/summit-schedule/#track=146 Full Forum Schedule]'''

'''See also - [[Forum/Boston2017#Thursday_Afternoon_session_sign-up|Thursday Afternoon session signup]]'''

'''See also - [https://ethercalc.openstack.org/Boston_Forum_Hacking_Rooms Hacking Rooms Schedule]'''

<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3">
__NOTOC__
</div>

= Event intro/closure =
* Forum 101 - https://etherpad.openstack.org/p/BOS-forum-101
* Boston feedback session - https://etherpad.openstack.org/p/BOS-summit-feedback

= Monday =
* [11:15am-11:55am] - Operating the VM and Baremetal platform (1/2) - https://etherpad.openstack.org/p/BOS-forum-operating-vm-and-baremetal
* [11:15am-12:45pm] - Nova - Project Onboarding - https://etherpad.openstack.org/p/BOS-forum-nova-project-onboarding
* [12:05pm-12:45pm] - OpenStack documentation: The future depends on all of us -
* [12:05pm-12:45pm] - WG chairs collaboration and WG overviews - https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews
* [2:00pm-2:40pm] - Evolving the Community Generated Roadmap - https://etherpad.openstack.org/p/BOS-forum-evolving-the-community-generated-roadmap
* [2:50pm-3:30pm] - Evolving the User Survey - https://etherpad.openstack.org/p/BOS-forum-evolving-the-user-survey
* [2:50pm-3:30pm] - Future of Configuration Management - https://etherpad.openstack.org/p/BOS-forum-future-of-configuration-management
* [3:40pm-4:20pm] - Making keystone consumable outside of OpenStack - https://etherpad.openstack.org/p/BOS-forum-consumable-keystone
* [4:40pm-5:20pm] - Next steps for RBAC and policy - https://etherpad.openstack.org/p/BOS-forum-next-steps-for-rbac-and-policy
* [4:40pm-5:20pm] - Should we kill Stackalytics? - https://etherpad.openstack.org/p/BOS-forum-should-we-kill-stackalytics
* [5:30pm-6:10pm] - Using Searchlight to list instances across cells in nova-api - https://etherpad.openstack.org/p/BOS-forum-using-searchlight-to-list-instances

= Tuesday =
* [11:15am-11:55am] Feedback from Users for I18n & Translation - Important Part? - https://etherpad.openstack.org/p/BOS-forum-i18n-translation-feedback-from-users
* [12:05pm-12:45pm] Enhancing Log Message Headers for RT Debug and Traceability - https://etherpad.openstack.org/p/BOS-forum-log-messages
* [12:05pm-12:45pm] LCOO Roadmap Working Session - https://etherpad.openstack.org/p/BOS-forum-LCOORoadmap
* [2:00pm-2:40pm] ETSI NFV Specs’ Requirements vs OpenStack Reality - https://etherpad.openstack.org/p/BOS-ETSI-NFV-Specs-Reqs-vs-OpenStack-Reality
* [2:00pm-2:40pm] Swift ops feedback session - https://etherpad.openstack.org/p/BOS-Swift-ops-feedback-session
* [2:00pm-3:30pm] Barbican and Security Projects Onboarding - https://etherpad.openstack.org/p/BOS-forum-barbican-onboarding
* [2:50pm-3:30pm] Skip-level upgrading - jumping ahead to catch up - https://etherpad.openstack.org/p/BOS-forum-skip-level-upgrading
* [4:40pm-5:20pm] Using Cinder for Nova Ephemeral Storage Backend - https://etherpad.openstack.org/p/BOS-forum-using-cinder-for-nova-ephemeral-storage
* [5:30pm-6:10pm] Features missing in OpenStack core for Public Cloud provider - https://etherpad.openstack.org/p/BOS-forum-Features-Missing-For-Public-Clouds

= Wednesday =
* [9:00am-9:40am] Oslo developer/operator feedback - https://etherpad.openstack.org/p/BOS-Oslo-brainstorming
* [9:00am-9:40am] Special hardware - https://etherpad.openstack.org/p/BOS-forum-special-hardware
* [9:00am-9:40am] Collaboration between Telecom/NFV related groups - https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration
* [9:50am-10:30am] oslo.messaging: Recommendations for Non-RabbitMQ Backends - https://etherpad.openstack.org/p/BOS_Forum_Oslo.Messaging_driver_recommendations
* [9:50am-10:30am] Vitrage Usability and New Insights: Where Do We Go Next? - https://etherpad.openstack.org/p/BOS-forum-vitrage-usability-and-new-insights
* [11:00am-11:40am] Compliance/Security Certification for upstream OpenStack - https://etherpad.openstack.org/p/BOS-forum-Compliance-Security-Certification
* [11:00am-11:40am] - Operating the VM and Baremetal platform (2/2) - https://etherpad.openstack.org/p/BOS-forum-operating-vm-and-baremetal
* [1:50pm-2:30pm] Kubernetes Ops on OpenStack - https://etherpad.openstack.org/p/BOS-forum-kubernetes-ops-on-openstack
* [1:50pm-2:30pm] App Developer Enablement - https://etherpad.openstack.org/p/BOS-forum-app-dev-enablement
* [1:50pm-2:30pm] Keystone Operator Feedback - https://etherpad.openstack.org/p/BOS-forum-keystone-operator-feedback
* [2:40pm-3:20pm] Product WG Working Session - https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session
* [2:40pm-3:20pm] Key Management Developer/Operator/Community Coordination - https://etherpad.openstack.org/p/BOS-forum-key-management
* [3:30pm-4:10pm] Compute Instance/Volume Affinity for HPC - https://etherpad.openstack.org/p/BOS-forum-compute-instance-volume-affinity-hpc
* [4:30pm-5:10pm] Moving Resource Claims from nova-compute to nova-scheduler - https://etherpad.openstack.org/p/BOS-forum-move-claims-from-compute-to-scheduler
* [4:30pm-5:10pm] Ops Tags WG session - https://etherpad.openstack.org/p/BOS-forum-ops-tags-wg-session
* [5:20pm-6:00pm] Large Heat Stacks (users/ops/developers) - https://etherpad.openstack.org/p/BOS-forum-Large-Heat-stacks

= Thursday =
* [9:00am-9:40am] Users/Operators: Contributing Multi-Project Requirements - https://etherpad.openstack.org/p/BOS-forum-contributing-multi-project-requirements
* [9:00am - 9:40am] Users / Operators adoption of QA tools / plugins - https://etherpad.openstack.org/p/BOS-forum-qa-tools-plugins
* [9:50am-10:30am] - Writing Applications for the VM and Baremetal Platform - https://etherpad.openstack.org/p/BOS-forum-using-vm-and-baremetal
* [11:00am-12:30pm] Queens Goals - https://etherpad.openstack.org/p/BOS-forum-Queens-Goals
* [11:50am-12:30pm] Shared Commercial Goals for OpenStack Public Cloud Providers - https://etherpad.openstack.org/p/BOS-forum-Shared-Commercial-Goals-Public-Clouds
* [1:30pm-2:10pm] User Committee Session - https://etherpad.openstack.org/p/BOS-forum-user-committee-session
* [2:20pm-3:00pm] Cloud-aware Application Support - https://etherpad.openstack.org/p/pike-forum-cloud-applications

==Thursday Afternoon session sign-up==
If something new comes up during the week, or a session runs over and you need more time, please sign up for another Fishbowl slot on Thursday Afternoon here:

<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3">
* 1:30-2:10 MR102 - available
* 2:20-3:00 MR102 - available
* 3:10-3:50 MR102 - available
* 3:50-4:10 MR102 - available
* 4:10-4:50 MR102 - available
* 5:00-5:40 MR102 - available
* 1:30-2:10 MR103 - available
* 2:20-3:00 MR103 - [https://etherpad.openstack.org/p/pike-forum-cloud-applications Cloud-aware Application Support]
* 3:10-3:50 MR103 - available
* 3:50-4:10 MR103 - available
* 4:10-4:50 MR103 - available
* 5:00-5:40 MR103 - available
* 1:30-2:10 MR104 - available
* 2:20-3:00 MR104 - available
* 3:10-3:50 MR104 - available
* 3:50-4:10 MR104 - available
* 4:10-4:50 MR104 - available
* 5:00-5:40 MR104 - [https://etherpad.openstack.org/p/pike-forum-tc-gathering TC members open gathering]
</div>

░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░

==(old) Brainstorming==
Below here were the etherpads used during the agenda brainstorming process...

====Catch-alls====
* [https://etherpad.openstack.org/p/BOS-TC-brainstorming TC Catch-all]
* [https://etherpad.openstack.org/p/BOS-UC-brainstorming UC Catch-all]

====Project Teams====

=====Barbican=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Barbican-brainstorming

=====Cinder=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Cinder-brainstorming

=====Freezer=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Freezer-brainstorming

=====Glance=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Glance-brainstorming

=====Heat=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Heat-brainstorming

=====I18n=====
Brainstorming: https://etherpad.openstack.org/p/BOS-I18n-brainstorming

=====Ironic=====
Brainstorming: https://etherpad.openstack.org/p/BOS-ironic-brainstorming

=====Keystone=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Keystone-brainstorming

=====Nova=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Nova-brainstorming

=====Oslo=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Oslo-brainstorming

=====Watcher=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Watcher-brainstorming

=====QA=====
Brainstorming: https://etherpad.openstack.org/p/BOS-QA-brainstorming

=====Swift=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Swift-brainstorming

====UC Working Groups ====

=====Telecom/NFV Requirements=====
https://etherpad.openstack.org/p/BOS-UC-brainstorming-Telecom&NFV

=====Scientific WG=====
https://etherpad.openstack.org/p/BOS-UC-brainstorming-scientific-wg

=====Massively Distributed (Fog/Edge) WG=====
https://etherpad.openstack.org/p/BOS-UC-brainstorming-MassivelyDistributed-Fog-Edge

=====Public Cloud WG=====
https://etherpad.openstack.org/p/publiccloud-boston-forum-session

====Other Working Groups====

=====VM and Bare-metal platform group=====

Developer lead group looking for user and operator feedback around the user experience across Nova, Ironic, Cinder and Neutron. Looking at both humans using the system, those operating the system, and projects building on the "VM and Bare-metal" platform. Main activity will be ranking the relative priority of current efforts, and looking to identify any gaps.

https://etherpad.openstack.org/p/BOS-TC-vm-baremetal-platform

Forum/Boston2017

2017-05-05T20:54:30Z

Kaizen: /* Wednesday */

The grand list of all of the Boston 2017 Forum etherpads. Please include Date, Time, and links to etherpads when adding new content. An [https://etherpad.openstack.org/p/BOS-forum-moderator-template etherpad template] (optional) is available if you need one.

'''See also - [https://www.openstack.org/summit/boston-2017/summit-schedule/#track=146 Full Forum Schedule]'''

'''See also - [[Forum/Boston2017#Thursday_Afternoon_session_sign-up|Thursday Afternoon session signup]]'''

'''See also - [https://ethercalc.openstack.org/Boston_Forum_Hacking_Rooms Hacking Rooms Schedule]'''

<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3">
__NOTOC__
</div>

= Event intro/closure =
* Forum 101 - https://etherpad.openstack.org/p/BOS-forum-101
* Boston feedback session - https://etherpad.openstack.org/p/BOS-summit-feedback

= Monday =
* [11:15am-11:55am] - Operating the VM and Baremetal platform (1/2) - https://etherpad.openstack.org/p/BOS-forum-operating-vm-and-baremetal
* [11:15am-12:45pm] - Nova - Project Onboarding - https://etherpad.openstack.org/p/BOS-forum-nova-project-onboarding
* [12:05pm-12:45pm] - OpenStack documentation: The future depends on all of us -
* [12:05pm-12:45pm] - WG chairs collaboration and WG overviews - https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews
* [2:00pm-2:40pm] - Evolving the Community Generated Roadmap - https://etherpad.openstack.org/p/BOS-forum-evolving-the-community-generated-roadmap
* [2:50pm-3:30pm] - Evolving the User Survey - https://etherpad.openstack.org/p/BOS-forum-evolving-the-user-survey
* [2:50pm-3:30pm] - Future of Configuration Management - https://etherpad.openstack.org/p/BOS-forum-future-of-configuration-management
* [3:40pm-4:20pm] - Making keystone consumable outside of OpenStack - https://etherpad.openstack.org/p/BOS-forum-consumable-keystone
* [4:40pm-5:20pm] - Next steps for RBAC and policy - https://etherpad.openstack.org/p/BOS-forum-next-steps-for-rbac-and-policy
* [4:40pm-5:20pm] - Should we kill Stackalytics? - https://etherpad.openstack.org/p/BOS-forum-should-we-kill-stackalytics
* [5:30pm-6:10pm] - Using Searchlight to list instances across cells in nova-api - https://etherpad.openstack.org/p/BOS-forum-using-searchlight-to-list-instances

= Tuesday =
* [11:15am-11:55am] Feedback from Users for I18n & Translation - Important Part? - https://etherpad.openstack.org/p/BOS-forum-i18n-translation-feedback-from-users
* [12:05pm-12:45pm] Enhancing Log Message Headers for RT Debug and Traceability - https://etherpad.openstack.org/p/BOS-forum-log-messages
* [12:05pm-12:45pm] LCOO Roadmap Working Session - https://etherpad.openstack.org/p/BOS-forum-LCOORoadmap
* [2:00pm-2:40pm] ETSI NFV Specs’ Requirements vs OpenStack Reality - https://etherpad.openstack.org/p/BOS-ETSI-NFV-Specs-Reqs-vs-OpenStack-Reality
* [2:00pm-2:40pm] Swift ops feedback session - https://etherpad.openstack.org/p/BOS-Swift-ops-feedback-session
* [2:00pm-3:30pm] Barbican and Security Projects Onboarding - https://etherpad.openstack.org/p/BOS-forum-barbican-onboarding
* [2:50pm-3:30pm] Skip-level upgrading - jumping ahead to catch up - https://etherpad.openstack.org/p/BOS-forum-skip-level-upgrading
* [4:40pm-5:20pm] Using Cinder for Nova Ephemeral Storage Backend - https://etherpad.openstack.org/p/BOS-forum-using-cinder-for-nova-ephemeral-storage
* [5:30pm-6:10pm] Features missing in OpenStack core for Public Cloud provider - https://etherpad.openstack.org/p/BOS-forum-Features-Missing-For-Public-Clouds

= Wednesday =
* [9:00am-9:40am] Oslo developer/operator feedback - https://etherpad.openstack.org/p/BOS-Oslo-brainstorming
* [9:00am-9:40am] Special hardware - https://etherpad.openstack.org/p/BOS-forum-special-hardware
* [9:00am-9:40am] Collaboration between Telecom/NFV related groups - https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration
* [9:50am-10:30am] oslo.messaging: Recommendations for Non-RabbitMQ Backends - https://etherpad.openstack.org/p/BOS_Forum_Oslo.Messaging_driver_recommendations
* [9:50am-10:30am] Vitrage Usability and New Insights: Where Do We Go Next? - https://etherpad.openstack.org/p/BOS-forum-vitrage-usability-and-new-insights
* [11:00am-11:40am] Compliance/Security Certification for upstream OpenStack - https://etherpad.openstack.org/p/BOS-forum-Compliance-Security-Certification
* [11:00am-11:40am] - Operating the VM and Baremetal platform (2/2) - https://etherpad.openstack.org/p/BOS-forum-operating-vm-and-baremetal
* [1:50pm-2:30pm] Kubernetes Ops on OpenStack - https://etherpad.openstack.org/p/BOS-forum-kubernetes-ops-on-openstack
* [1:50pm-2:30pm] App Developer Enablement - https://etherpad.openstack.org/p/BOS-forum-app-dev-enablement
* [1:50pm-2:30pm] Keystone Operator Feedback - https://etherpad.openstack.org/p/BOS-forum-keystone-operator-feedback
* [2:40pm-3:20pm] Product WG Working Session - https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session
* [2:40pm-3:20pm] Key Management Developer/Operator/Community Coordination - https://etherpad.openstack.org/p/BOS-forum-key-management
* [3:30pm-4:10pm] Compute Instance/Volume Affinity for HPC - https://etherpad.openstack.org/p/BOS-forum-compute-instance-volume-affinity-hpc
* [4:30pm-5:10pm] Moving Resource Claims from nova-compute to nova-scheduler - https://etherpad.openstack.org/p/BOS-forum-move-claims-from-compute-to-scheduler
* [4:30pm-5:10pm] Ops Tags WG session - https://etherpad.openstack.org/p/BOS-forum-ops-tags-wg-session
* [5:20pm-6:00pm] Large Heat Stacks (users/ops/developers) - https://etherpad.openstack.org/p/BOS-forum-Large-Heat-stacks

= Thursday =
* [9:00am-9:40am] Users/Operators: Contributing Multi-Project Requirements - https://etherpad.openstack.org/p/BOS-forum-contributing-multi-project-requirements
* [9:00am - 9:40am] Users / Operators adoption of QA tools / plugins - https://etherpad.openstack.org/p/BOS-forum-qa-tools-plugins
* [9:50am-10:30am] - Writing Applications for the VM and Baremetal Platform - https://etherpad.openstack.org/p/BOS-forum-using-vm-and-baremetal
* [11:00am-12:30pm] Queens Goals - https://etherpad.openstack.org/p/BOS-forum-Queens-Goals
* [11:50am-12:30pm] Shared Commercial Goals for OpenStack Public Cloud Providers - https://etherpad.openstack.org/p/BOS-forum-Shared-Commercial-Goals-Public-Clouds
* [2:20pm-3:00pm] Cloud-aware Application Support - https://etherpad.openstack.org/p/pike-forum-cloud-applications

==Thursday Afternoon session sign-up==
If something new comes up during the week, or a session runs over and you need more time, please sign up for another Fishbowl slot on Thursday Afternoon here:

<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3">
* 1:30-2:10 MR102 - available
* 2:20-3:00 MR102 - available
* 3:10-3:50 MR102 - available
* 3:50-4:10 MR102 - available
* 4:10-4:50 MR102 - available
* 5:00-5:40 MR102 - available
* 1:30-2:10 MR103 - available
* 2:20-3:00 MR103 - [https://etherpad.openstack.org/p/pike-forum-cloud-applications Cloud-aware Application Support]
* 3:10-3:50 MR103 - available
* 3:50-4:10 MR103 - available
* 4:10-4:50 MR103 - available
* 5:00-5:40 MR103 - available
* 1:30-2:10 MR104 - available
* 2:20-3:00 MR104 - available
* 3:10-3:50 MR104 - available
* 3:50-4:10 MR104 - available
* 4:10-4:50 MR104 - available
* 5:00-5:40 MR104 - [https://etherpad.openstack.org/p/pike-forum-tc-gathering TC members open gathering]
</div>

░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░

==(old) Brainstorming==
Below here were the etherpads used during the agenda brainstorming process...

====Catch-alls====
* [https://etherpad.openstack.org/p/BOS-TC-brainstorming TC Catch-all]
* [https://etherpad.openstack.org/p/BOS-UC-brainstorming UC Catch-all]

====Project Teams====

=====Barbican=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Barbican-brainstorming

=====Cinder=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Cinder-brainstorming

=====Freezer=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Freezer-brainstorming

=====Glance=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Glance-brainstorming

=====Heat=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Heat-brainstorming

=====I18n=====
Brainstorming: https://etherpad.openstack.org/p/BOS-I18n-brainstorming

=====Ironic=====
Brainstorming: https://etherpad.openstack.org/p/BOS-ironic-brainstorming

=====Keystone=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Keystone-brainstorming

=====Nova=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Nova-brainstorming

=====Oslo=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Oslo-brainstorming

=====Watcher=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Watcher-brainstorming

=====QA=====
Brainstorming: https://etherpad.openstack.org/p/BOS-QA-brainstorming

=====Swift=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Swift-brainstorming

====UC Working Groups ====

=====Telecom/NFV Requirements=====
https://etherpad.openstack.org/p/BOS-UC-brainstorming-Telecom&NFV

=====Scientific WG=====
https://etherpad.openstack.org/p/BOS-UC-brainstorming-scientific-wg

=====Massively Distributed (Fog/Edge) WG=====
https://etherpad.openstack.org/p/BOS-UC-brainstorming-MassivelyDistributed-Fog-Edge

=====Public Cloud WG=====
https://etherpad.openstack.org/p/publiccloud-boston-forum-session

====Other Working Groups====

=====VM and Bare-metal platform group=====

Developer lead group looking for user and operator feedback around the user experience across Nova, Ironic, Cinder and Neutron. Looking at both humans using the system, those operating the system, and projects building on the "VM and Bare-metal" platform. Main activity will be ranking the relative priority of current efforts, and looking to identify any gaps.

https://etherpad.openstack.org/p/BOS-TC-vm-baremetal-platform

Forum/Boston2017

2017-05-05T20:42:12Z

Kaizen: /* Monday */

The grand list of all of the Boston 2017 Forum etherpads. Please include Date, Time, and links to etherpads when adding new content. An [https://etherpad.openstack.org/p/BOS-forum-moderator-template etherpad template] (optional) is available if you need one.

'''See also - [https://www.openstack.org/summit/boston-2017/summit-schedule/#track=146 Full Forum Schedule]'''

'''See also - [[Forum/Boston2017#Thursday_Afternoon_session_sign-up|Thursday Afternoon session signup]]'''

'''See also - [https://ethercalc.openstack.org/Boston_Forum_Hacking_Rooms Hacking Rooms Schedule]'''

<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3">
__NOTOC__
</div>

= Event intro/closure =
* Forum 101 - https://etherpad.openstack.org/p/BOS-forum-101
* Boston feedback session - https://etherpad.openstack.org/p/BOS-summit-feedback

= Monday =
* [11:15am-11:55am] - Operating the VM and Baremetal platform (1/2) - https://etherpad.openstack.org/p/BOS-forum-operating-vm-and-baremetal
* [11:15am-12:45pm] - Nova - Project Onboarding - https://etherpad.openstack.org/p/BOS-forum-nova-project-onboarding
* [12:05pm-12:45pm] - OpenStack documentation: The future depends on all of us -
* [12:05pm-12:45pm] - WG chairs collaboration and WG overviews - https://etherpad.openstack.org/p/BOS-forum-wg-chairs-collaboration-and-WG-overviews
* [2:00pm-2:40pm] - Evolving the Community Generated Roadmap - https://etherpad.openstack.org/p/BOS-forum-evolving-the-community-generated-roadmap
* [2:50pm-3:30pm] - Evolving the User Survey - https://etherpad.openstack.org/p/BOS-forum-evolving-the-user-survey
* [2:50pm-3:30pm] - Future of Configuration Management - https://etherpad.openstack.org/p/BOS-forum-future-of-configuration-management
* [3:40pm-4:20pm] - Making keystone consumable outside of OpenStack - https://etherpad.openstack.org/p/BOS-forum-consumable-keystone
* [4:40pm-5:20pm] - Next steps for RBAC and policy - https://etherpad.openstack.org/p/BOS-forum-next-steps-for-rbac-and-policy
* [4:40pm-5:20pm] - Should we kill Stackalytics? - https://etherpad.openstack.org/p/BOS-forum-should-we-kill-stackalytics
* [5:30pm-6:10pm] - Using Searchlight to list instances across cells in nova-api - https://etherpad.openstack.org/p/BOS-forum-using-searchlight-to-list-instances

= Tuesday =
* [11:15am-11:55am] Feedback from Users for I18n & Translation - Important Part? - https://etherpad.openstack.org/p/BOS-forum-i18n-translation-feedback-from-users
* [12:05pm-12:45pm] Enhancing Log Message Headers for RT Debug and Traceability - https://etherpad.openstack.org/p/BOS-forum-log-messages
* [12:05pm-12:45pm] LCOO Roadmap Working Session - https://etherpad.openstack.org/p/BOS-forum-LCOORoadmap
* [2:00pm-2:40pm] ETSI NFV Specs’ Requirements vs OpenStack Reality - https://etherpad.openstack.org/p/BOS-ETSI-NFV-Specs-Reqs-vs-OpenStack-Reality
* [2:00pm-2:40pm] Swift ops feedback session - https://etherpad.openstack.org/p/BOS-Swift-ops-feedback-session
* [2:00pm-3:30pm] Barbican and Security Projects Onboarding - https://etherpad.openstack.org/p/BOS-forum-barbican-onboarding
* [2:50pm-3:30pm] Skip-level upgrading - jumping ahead to catch up - https://etherpad.openstack.org/p/BOS-forum-skip-level-upgrading
* [4:40pm-5:20pm] Using Cinder for Nova Ephemeral Storage Backend - https://etherpad.openstack.org/p/BOS-forum-using-cinder-for-nova-ephemeral-storage
* [5:30pm-6:10pm] Features missing in OpenStack core for Public Cloud provider - https://etherpad.openstack.org/p/BOS-forum-Features-Missing-For-Public-Clouds

= Wednesday =
* [9:00am-9:40am] Oslo developer/operator feedback - https://etherpad.openstack.org/p/BOS-Oslo-brainstorming
* [9:00am-9:40am] Special hardware - https://etherpad.openstack.org/p/BOS-forum-special-hardware
* [9:00am-9:40am] Collaboration between Telecom/NFV related groups - https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration
* [9:50am-10:30am] oslo.messaging: Recommendations for Non-RabbitMQ Backends - https://etherpad.openstack.org/p/BOS_Forum_Oslo.Messaging_driver_recommendations
* [9:50am-10:30am] Vitrage Usability and New Insights: Where Do We Go Next? - https://etherpad.openstack.org/p/BOS-forum-vitrage-usability-and-new-insights
* [11:00am-11:40am] Compliance/Security Certification for upstream OpenStack - https://etherpad.openstack.org/p/BOS-forum-Compliance-Security-Certification
* [11:00am-11:40am] - Operating the VM and Baremetal platform (2/2) - https://etherpad.openstack.org/p/BOS-forum-operating-vm-and-baremetal
* [1:50pm-2:30pm] Kubernetes Ops on OpenStack - https://etherpad.openstack.org/p/BOS-forum-kubernetes-ops-on-openstack
* [1:50pm-2:30pm] App Developer Enablement - https://etherpad.openstack.org/p/BOS-forum-app-dev-enablement
* [1:50pm-2:30pm] Keystone Operator Feedback - https://etherpad.openstack.org/p/BOS-forum-keystone-operator-feedback
* [2:40pm-3:20pm] Product WG Working Session - https://etherpad.openstack.org/p/BOS-forum-product-wg-working-session
* [2:40pm-3:20pm] Key Management Developer/Operator/Community Coordination - https://etherpad.openstack.org/p/BOS-forum-key-management
* [3:30pm-4:10pm] Compute Instance/Volume Affinity for HPC - https://etherpad.openstack.org/p/BOS-forum-compute-instance-volume-affinity-hpc
* [4:30pm-5:10pm] Moving Resource Claims from nova-compute to nova-scheduler - https://etherpad.openstack.org/p/BOS-forum-move-claims-from-compute-to-scheduler
* [5:20pm-6:00pm] Large Heat Stacks (users/ops/developers) - https://etherpad.openstack.org/p/BOS-forum-Large-Heat-stacks

= Thursday =
* [9:00am-9:40am] Users/Operators: Contributing Multi-Project Requirements - https://etherpad.openstack.org/p/BOS-forum-contributing-multi-project-requirements
* [9:00am - 9:40am] Users / Operators adoption of QA tools / plugins - https://etherpad.openstack.org/p/BOS-forum-qa-tools-plugins
* [9:50am-10:30am] - Writing Applications for the VM and Baremetal Platform - https://etherpad.openstack.org/p/BOS-forum-using-vm-and-baremetal
* [11:00am-12:30pm] Queens Goals - https://etherpad.openstack.org/p/BOS-forum-Queens-Goals
* [11:50am-12:30pm] Shared Commercial Goals for OpenStack Public Cloud Providers - https://etherpad.openstack.org/p/BOS-forum-Shared-Commercial-Goals-Public-Clouds
* [2:20pm-3:00pm] Cloud-aware Application Support - https://etherpad.openstack.org/p/pike-forum-cloud-applications

==Thursday Afternoon session sign-up==
If something new comes up during the week, or a session runs over and you need more time, please sign up for another Fishbowl slot on Thursday Afternoon here:

<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3">
* 1:30-2:10 MR102 - available
* 2:20-3:00 MR102 - available
* 3:10-3:50 MR102 - available
* 3:50-4:10 MR102 - available
* 4:10-4:50 MR102 - available
* 5:00-5:40 MR102 - available
* 1:30-2:10 MR103 - available
* 2:20-3:00 MR103 - [https://etherpad.openstack.org/p/pike-forum-cloud-applications Cloud-aware Application Support]
* 3:10-3:50 MR103 - available
* 3:50-4:10 MR103 - available
* 4:10-4:50 MR103 - available
* 5:00-5:40 MR103 - available
* 1:30-2:10 MR104 - available
* 2:20-3:00 MR104 - available
* 3:10-3:50 MR104 - available
* 3:50-4:10 MR104 - available
* 4:10-4:50 MR104 - available
* 5:00-5:40 MR104 - [https://etherpad.openstack.org/p/pike-forum-tc-gathering TC members open gathering]
</div>

░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░

==(old) Brainstorming==
Below here were the etherpads used during the agenda brainstorming process...

====Catch-alls====
* [https://etherpad.openstack.org/p/BOS-TC-brainstorming TC Catch-all]
* [https://etherpad.openstack.org/p/BOS-UC-brainstorming UC Catch-all]

====Project Teams====

=====Barbican=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Barbican-brainstorming

=====Cinder=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Cinder-brainstorming

=====Freezer=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Freezer-brainstorming

=====Glance=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Glance-brainstorming

=====Heat=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Heat-brainstorming

=====I18n=====
Brainstorming: https://etherpad.openstack.org/p/BOS-I18n-brainstorming

=====Ironic=====
Brainstorming: https://etherpad.openstack.org/p/BOS-ironic-brainstorming

=====Keystone=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Keystone-brainstorming

=====Nova=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Nova-brainstorming

=====Oslo=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Oslo-brainstorming

=====Watcher=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Watcher-brainstorming

=====QA=====
Brainstorming: https://etherpad.openstack.org/p/BOS-QA-brainstorming

=====Swift=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Swift-brainstorming

====UC Working Groups ====

=====Telecom/NFV Requirements=====
https://etherpad.openstack.org/p/BOS-UC-brainstorming-Telecom&NFV

=====Scientific WG=====
https://etherpad.openstack.org/p/BOS-UC-brainstorming-scientific-wg

=====Massively Distributed (Fog/Edge) WG=====
https://etherpad.openstack.org/p/BOS-UC-brainstorming-MassivelyDistributed-Fog-Edge

=====Public Cloud WG=====
https://etherpad.openstack.org/p/publiccloud-boston-forum-session

====Other Working Groups====

=====VM and Bare-metal platform group=====

Developer lead group looking for user and operator feedback around the user experience across Nova, Ironic, Cinder and Neutron. Looking at both humans using the system, those operating the system, and projects building on the "VM and Bare-metal" platform. Main activity will be ranking the relative priority of current efforts, and looking to identify any gaps.

https://etherpad.openstack.org/p/BOS-TC-vm-baremetal-platform

Forum/Boston2017

2017-04-24T13:47:15Z

Kaizen: /* Monday */

The grand list of all of the Boston 2017 Forum etherpads. Please include Date, Time, and links to etherpads when adding new content.

<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3">
__NOTOC__
</div>

= Event intro/closure =
* Forum 101 - https://etherpad.openstack.org/p/BOS-forum-101
* Boston feedback session - https://etherpad.openstack.org/p/BOS-summit-feedback

= Monday =
* Future of Configuration Management - https://etherpad.openstack.org/p/BOS-forum-future-of-configuration-management
* Evolving the Community Generated Roadmap - https://etherpad.openstack.org/p/BOS-forum-evolving-the-community-generated-roadmap

= Tuesday =

= Wednesday =
* https://etherpad.openstack.org/p/BOS-forum-telecom-nfv-collaboration
* https://etherpad.openstack.org/p/BOS-forum-Compliance-Security-Certification

= Thursday =
* https://etherpad.openstack.org/p/BOS-forum-Queens-Goals

░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░

==(old) Brainstorming==
Below here were the etherpads used during the agenda brainstorming process...

====Catch-alls====
* [https://etherpad.openstack.org/p/BOS-TC-brainstorming TC Catch-all]
* [https://etherpad.openstack.org/p/BOS-UC-brainstorming UC Catch-all]

====Project Teams====

=====Barbican=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Barbican-brainstorming

=====Cinder=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Cinder-brainstorming

=====Freezer=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Freezer-brainstorming

=====Glance=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Glance-brainstorming

=====Heat=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Heat-brainstorming

=====I18n=====
Brainstorming: https://etherpad.openstack.org/p/BOS-I18n-brainstorming

=====Ironic=====
Brainstorming: https://etherpad.openstack.org/p/BOS-ironic-brainstorming

=====Keystone=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Keystone-brainstorming

=====Nova=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Nova-brainstorming

=====Oslo=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Oslo-brainstorming

=====Watcher=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Watcher-brainstorming

=====QA=====
Brainstorming: https://etherpad.openstack.org/p/BOS-QA-brainstorming

=====Swift=====
Brainstorming: https://etherpad.openstack.org/p/BOS-Swift-brainstorming

====UC Working Groups ====

=====Telecom/NFV Requirements=====
https://etherpad.openstack.org/p/BOS-UC-brainstorming-Telecom&NFV

=====Scientific WG=====
https://etherpad.openstack.org/p/BOS-UC-brainstorming-scientific-wg

=====Massively Distributed (Fog/Edge) WG=====
https://etherpad.openstack.org/p/BOS-UC-brainstorming-MassivelyDistributed-Fog-Edge

=====Public Cloud WG=====
https://etherpad.openstack.org/p/publiccloud-boston-forum-session

====Other Working Groups====

=====VM and Bare-metal platform group=====

Developer lead group looking for user and operator feedback around the user experience across Nova, Ironic, Cinder and Neutron. Looking at both humans using the system, those operating the system, and projects building on the "VM and Bare-metal" platform. Main activity will be ranking the relative priority of current efforts, and looking to identify any gaps.

https://etherpad.openstack.org/p/BOS-TC-vm-baremetal-platform

Governance/Foundation/UserCommittee

2017-04-20T16:15:48Z

Kaizen: /* How to Engage? */

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 user committee mission is to:

* 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
* 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

[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].
 
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. 

== Meeting Agenda/Previous Meeting Logs ==
Next meeting: '''Monday, April 24th, 2017 at 1900 UTC''' in (freenode) #openstack-meeting
 
Proposed Agenda for April 24th, 2017:
-

Previous Agenda:
- Recap UC Session at the Ops Meetup (10min)
- 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 ==

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 ===
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"
|-
! 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
|}

Governance/Foundation/UserCommittee

2017-04-20T16:15:24Z

Kaizen: /* Meeting Agenda/Previous Meeting Logs */

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 user committee mission is to:

* 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
* 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

[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].
 
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. 

== Meeting Agenda/Previous Meeting Logs ==
Next meeting: '''Monday, April 24th, 2017 at 1900 UTC''' in (freenode) #openstack-meeting
 
Proposed Agenda for April 24th, 2017:
-

Previous Agenda:
- Recap UC Session at the Ops Meetup (10min)
- 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 ==

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 ===
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"
|-
! 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
|}

Governance/Foundation/UserCommittee

2017-04-20T16:14:37Z

Kaizen: /* Meeting Agenda/Previous Meeting Logs */

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 user committee mission is to:

* 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
* 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

[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].
 
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. 

== Meeting Agenda/Previous Meeting Logs ==
Next meeting: '''Monday, April 24th, 2017 at 1900 UTC''' in (freenode) #openstack-meeting
 
Proposed Agenda for April 24th, 2017:
-

Previous Agenda:
- Recap UC Session at the Ops Meetup (10min)
- 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 ==

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 ===
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"
|-
! 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
|}

Governance/Foundation/UserCommittee

2017-04-20T16:13:40Z

Kaizen: /* How to Engage? */

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 user committee mission is to:

* 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
* 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

[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].
 
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. 

== Meeting Agenda/Previous Meeting Logs ==
Next meeting: '''Monday, April 24th, 2017 at 1900 UTC''' in (freenode) #openstack-meeting
Proposed Agenda for April 24th, 2017:
-

Previous Agenda:
- Recap UC Session at the Ops Meetup (10min)
- 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 ==

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 ===
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"
|-
! 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
|}

Governance/Foundation/UserCommittee

2017-04-20T16:11:06Z

Kaizen: /* How to Engage? */

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 user committee mission is to:

* 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
* 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

[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].

Attend our fortnightly IRC meetings Every two weeks (on odd weeks) on Monday at 1900 UTC:
Next meeting: '''Monday, April 24th, 2017 at 1900 UTC''' in (freenode) #openstack-meeting

Proposed Agenda for April 24th, 2017:
-

Previous Agenda:
- Recap UC Session at the Ops Meetup (10min)
- 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 ==

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 ===
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"
|-
! 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
|}

Forum/Boston2017

2017-03-02T22:51:22Z

Kaizen: /* Team-specific */

The grand list of all of the Boston Forum etherpads. Please include the name of the team that started the pad.

==Catch-alls==
* [https://etherpad.openstack.org/p/BOS-TC-brainstorming TC Catch-all]
* [https://etherpad.openstack.org/p/BOS-UC-brainstorming UC Catch-all]

==Team-specific==

===Nova===

===Telecom/NFV Requirements===
https://etherpad.openstack.org/p/BOS-UC-brainstorming-Telecom&NFV

===Scientific WG===
https://etherpad.openstack.org/p/BOS-UC-brainstorming-scientific-wg

Forum/Boston2017

2017-03-02T22:12:23Z

Kaizen: /* Team-specific */

Governance/Foundation/UserCommittee

2017-02-27T17:41:44Z

Kaizen: /* How to Engage? */

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 user committee mission is to:

* 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
* 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

[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].

Attend our fortnightly IRC meetings Every two weeks (on odd weeks) on Monday at 1900 UTC:
Next US meeting: '''Monday, Feb 27th, 2017 at 1900 UTC''' in (freenode) #openstack-meeting

Proposed Agenda:
- Welcome UC elected members: Shamail and Melvin
- UC Chair - Election: https://governance.openstack.org/uc/reference/charter.html
- Product WG proposal: https://docs.google.com/presentation/d/1jTlO4UdNjc5cOKboeCNhLDEdttazWWlDgNxxulUrPNg/edit
- Review previous Action Items
- Board + TC + UC meeting in Boston (March 8-9, 2017)
- Review Forum Brainstorming Invite: https://etherpad.openstack.org/p/uc-forum-brainstorm-invite
- Forum Session Selection Candidates
- Working Group Update(s)
- Ops Midcycle (March 15-16, 2017) - Goals/Expectations
- Open Agenda

Previous Agenda:
- UC Election
- Boston planning
- Finalize on proposal from the Product Working Group for Forum - https://docs.google.com/presentation/d/1jTlO4UdNjc5cOKboeCNhLDEdttazWWlDgNxxulUrPNg/edit
- Open Agenda

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 ==

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 ===
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"
|-
! 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.
|-
| [[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 Private Cloud needs and issues.
|-
| [[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 || 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
|}

Enterprise Working Group

2017-01-15T22:43:29Z

Kaizen: /* Team Meeting */

__NOTOC__
'''Status''': Active

'''Organisers''': Carol Barrett <carol.l.barrett@intel.com>

=====Mail List=====
Sign-up for the User Committee mailing listː http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee

=====Mission & What We Do=====
* Identify and remove barriers to Enterprise adoption and deployment of OpenStack, through information from Enterprise Customers, Operators, Users, Analyst, etc.
* Collaborate on the development and tracking of [https://github.com/openstack/openstack-user-stories User Stories] with the Product WG.
* Partner with the OpenStack Foundation to create and promote eBooks, Customer testimonials, Reference Architectures and Solution Guides, etc. to educate and provide best practices for current and future Enterprise Customers.

=====Ocata Cycle Goals =====
* Finish e-commerce reference architecture - Lead: Kathy
* Publish a Containers for Applications reference architecture - Lead: Leong, with support from content experts
* Publish Migrating (or Moving) Applications to Cloud eBook - Lead: is Leong,with support from Kathy and Heidi Joy
* Increase the awareness of this WG and participation in our Goals by end-user organizations - Lead: Nicole
* New content and case studies on migrating from or coexisting with VMware - Lead: Grant, with support from Leong and Kathy

=====Summit & Meetup Notes=====
Austin Session notes: https://etherpad.openstack.org/p/Enterprise_WG_Austin_Meetup 
Tokyo Session notes: https://etherpad.openstack.org/p/Enterprise_WG_Tokyo_Meetup 
Vancouver session notesː https://etherpad.openstack.org/p/Win-The-Enterprise-Vancouver-Meetup

 
===Team Meeting===
 

The team meets weekly, on Tuesdays at 1900 UTC (11:00 AM Pacific) 
Call In Info: (888) 875-9370, Bridge: 3; PC: 1520326# 
Next Meeting Etherpad: https://etherpad.openstack.org/p/EWG_1_17_17 

Meeting calendar: [https://www.google.com/calendar/embed?src=openstack.org_c3rclpidijlk4tma0vn0cbajrk%40group.calendar.google.com&ctz=America/Chicago html view] and [https://www.google.com/calendar/ical/openstack.org_c3rclpidijlk4tma0vn0cbajrk%40group.calendar.google.com/public/basic.ics iCal, machine readable calendar]

Previous Etherpad links can be found here: https://etherpad.openstack.org/p/Enterprise_Work_Group_Archives

==== Enterprise ISV Interop Team ====

{| class="wikitable"
|-
| Team Description || Based upon Enterprise IT Mgr requirements for Application interoperability with OpenStack, this team works with ISVs to validate their application interoperability and publish How-To Guides, User Case studies and other collateral as needed.
|-
| Etherpad || https://etherpad.openstack.org/p/Enterprise-Business-ISV
|-
| Meeting Logistics || Wednesday 17:00 UTC; Please check [https://etherpad.openstack.org/p/Enterprise-Business-ISV etherpad] for dial-in information
|-
| Previous Meeting Notes || https://etherpad.openstack.org/p/Enterprise-Business-ISV-Archive 
|-
|}

==== Reference Architecture Team ====

{| class="wikitable"
|-
| Team Description || This team develops sample Reference Architectures for leading Workloads as a guide for Operators in planning their deployments.
|-
| Etherpad || https://etherpad.openstack.org/p/EWG_Workload_Reference_Architecture
|-
| Source Repository || https://github.com/openstack/workload-ref-archs
|-
| Meeting Logistics || Tuesday 20:00 UTC Please check [https://etherpad.openstack.org/p/EWG_Workload_Reference_Architecture etherpad] for dial-in information
|}

Meetings/product-team

2017-01-15T22:34:07Z

Kaizen: /* January 16, 2017 Product Team Meeting Agenda */

= January 16, 2017 Product Team Meeting Agenda =
* User Story Tracker Discussion
** https://review.openstack.org/#/c/419674/
** https://review.openstack.org/#/c/418549/
** http://featuretracker.openstack.org
* PWG at Forum Event
* Gap Analysis - Template and Location in Repo
* Review Capacity Management gaps analysis - (Gerald)
** https://etherpad.opnfv.org/p/promise_gap_analysis
* Midcycle Planning
** Planning Etherpad: https://etherpad.openstack.org/p/MIL-pwg-meetup
* Opens - All

= January 17th, 2017 (Tuesday 0600 UTC) Product Team Regional Meeting Agenda =
* Midcycle Planning
** Milan: https://etherpad.openstack.org/p/MIL-pwg-meetup
* User Story
** Baremetal
*** User Story Tracker http://featuretracker.openstack.org
** Logging
*** Status of new user story
* Opens

 

''Information on previous agendas: https://etherpad.openstack.org/p/pwg_previous_agendas''

Meetings/product-team

2017-01-15T22:33:40Z

Kaizen: /* January 9, 2017 Product Team Meeting Agenda */

= January 16, 2017 Product Team Meeting Agenda =
* User Story Tracker Discussion
** https://review.openstack.org/#/c/419674/
** https://review.openstack.org/#/c/418549/
* PWG at Forum Event
* Gap Analysis - Template and Location in Repo
* Review Capacity Management gaps analysis - (Gerald)
** https://etherpad.opnfv.org/p/promise_gap_analysis
* Midcycle Planning
** Planning Etherpad: https://etherpad.openstack.org/p/MIL-pwg-meetup
* Opens - All

= January 17th, 2017 (Tuesday 0600 UTC) Product Team Regional Meeting Agenda =
* Midcycle Planning
** Milan: https://etherpad.openstack.org/p/MIL-pwg-meetup
* User Story
** Baremetal
*** User Story Tracker http://featuretracker.openstack.org
** Logging
*** Status of new user story
* Opens

 

''Information on previous agendas: https://etherpad.openstack.org/p/pwg_previous_agendas''

ProductTeam

2017-01-04T20:08:10Z

Kaizen: /* Meeting and Communication Information */

= OpenStack Product Working Group =

== Meeting and Communication Information ==

'''Next Team Meeting will be on January 9, 2017 - Happy Holidays!'''

Date, time, and IRC channel: http://eavesdrop.openstack.org/#OpenStack_Product_WG
Past IRC meeting logs: http://eavesdrop.openstack.org/meetings/product_working_group/
Etherpad archives: https://etherpad.openstack.org/p/PWG_Archives
[http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee Subscribe to the User Committee Mailing List]
Please add [Product] tag in the subject line when sending messages to the User Committee Mailing List
[http://lists.openstack.org/pipermail/product-wg/ Product WG Mailing List Archives (archive of messages sent prior to Jan. 4th, 2017)]

== Ocata Cycle Priorities ==
* Establish simplified process for user-story creation, review and analysis to enable all Work Groups/Teams to contribute and enable a wider range of feedback.
**Lead: Shamail Tahir
* Complete the User Story Tracker
**Lead: Jamey
* Support the Community transitions: Redesigned work flow and User Committee expansion
** Lead: Carol

Ocata Midcycle Planning etherpad: https://etherpad.openstack.org/p/MIL-pwg-meetup

== Barcelona Summit ==
We will get together in Barcelona for a working session. The session is scheduled for October 27th from 11:00 - 12:30 in AC Hotel - P14 - Pedralbes. The session details are here: https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/16855/product-working-group-working-session.

The planning etherpad: https://etherpad.openstack.org/p/PWG_Session_Oct16_BCN

== Mission ==
We will support the OpenStack developer community in their desire to build open-source cloud software that reflects the needs of the various markets adopting the platform by creating user stories that reflect the voice of the end-users/operators. These user stories will focus on items that have traditionally been harder to implement based on the need for cross-project coordination and significant development time (spanning multiple releases). Finally, the team will also focus on sharing regular updates on directional insights for the platform (gathered from key members from the development community) in the form of a multi-release roadmap. The ultimate mission is to create a focus on areas that are high-impact and remove barriers to adoption/operation/scale of OpenStack clouds.

== Who we are ==
The product working group consists of product managers, technologists, and operators from a diverse set of organizations. The group is working to aggregate user stories from the market-focused teams (Enterprise, Telco, etc.) and cross-project functional teams (e.g. logging, upgrades, etc.), partner with the development community on resourcing, and help gather data to generate a multi-release roadmap. Most of the user stories being tracked by this team consists of items that can span multiple releases and usually have cross-project dependencies.

The group aims to **improve the quality of the delivery process, the delivered product, and the product experience for operators and end users**.

== Objectives ==
The objectives of this working group, based on the mission, are therefore to:

=== [https://github.com/openstack/openstack-user-stories Collect Feedback and Aggregate Requirements] ===
This group will collect (and aggregate) user, admin, customer, and operator requirements. The group should also interface with and gather data from, the other groups collecting requirements for specific verticals, markets, or user segments (e.g. Operators, Win The Enterprise, Personas, NFV/Telco, End Users/App Developers, etc.)

=== [[ProductTeam/User Stories|User Story Planning, Prioritization, and Development]] ===
Develop a repeatable, transparent, process for prioritization of [http://specs.openstack.org/openstack/openstack-user-stories/ user stories]; create blueprints/specs (or bug report) associated with the user story on a per-release cycle basis. The team will work within their organizations to fill any necessary resource gaps and create a tracker to track the implementation progress of the user story across projects and multiple releases. The criteria for the process along with the results should be clearly communicated with the community and our end-customers.

=== [[ProductTeam/MultiRelease Roadmap|Multi-release Roadmap]] ===
Generate a multi-release roadmap based on the aggregated data and resulting themes/requirements. The roadmap will be socialized, transparently, to community stakeholders for agreement and approval. After a roadmap has been established/approved, the OpenStack community will be notified of the results, the drivers for the decision, and its impact over multiple releases to consumers (and developers) of the platform.

== Methodology ==
The team requires establishing a workflow, identifying stakeholders/partners in the community, providing a means to track progress against user stories, and ensuring routine interlocks with other members/groups in the community due to the wide spectrum of items being worked on concurrently. The Product WG has established sub-teams/roles to divide tasks to ensure quality and timeliness of our collective output.

=== Sub-Teams / Roles ===
==== Roadmap Release Team ====
The roadmap release team consists of CPLs and other members of the Product WG. This team has a [[ProductTeam/MultiRelease Roadmap|dedicated sub-page]] which includes more information.

==== Product WG Cross Project Liaisons ====
OpenStack uses a concept called Cross Project Liaisons to facilitate communications between projects that might require collaboration/coordination with each other. The cross-project liaisons representing a certain team will co-locate with another team to become participating members and serve as the conduit between the two project teams. You can find a list of the Product WG CPLs here: https://wiki.openstack.org/wiki/CrossProjectLiaisons#Product_Working_Group

==== User Story Owners ====
The User Story Owners are members of the Product WG team who have volunteered to help manage/lead/track a user story from submission to completion. They will also help with the decomposition of the user stories into blueprints/specs, gather resources to aid with authoring/completing blueprints/specs, and work with the CPLs to ensure the "big picture"/objective associated with the user story is being taken into account since user stories will often include multiple "moving parts" in a single release and require tracking across releases.
 
While user stories are stored/tracked using the [https://github.com/openstack/openstack-user-stories openstack-user-stories repo] and the [http://specs.openstack.org/openstack/openstack-user-stories/ specs page]. The user story owners maintain a [https://wiki.openstack.org/wiki/ProductTeam/User_Stories#Sub-Pages_for_Active_User_Stories sub-page] for each user story to provide information on team meetings and additional artifacts.

==== OpenStack User Stories Core Members ====
The members of the openstack-user-stories-core team carefully review all changes proposed to the openstack-user-story repository (which is where the Product WG stores user stories and tracking data). The responsibilities, expectations, and process for membership in the openstack-user-stores-core team can be [[ProductTeam/Core_Team|found here]].

==== Series of Activities per Release ====
In conclusion, to achieve the various objectives, the Product WG will pursue multiple activities throughout each release. The chart below attempts to map these activities on top of the standard 6-month release schedule for OpenStack releases.

==FAQs==
The Product WG has compiled a list of [[ProductTeam/FrequentlyAskedQuestions|Frequently Asked Questions]].

[[File:Pwgactivities.png|framed|center]]

== Product WG Pilot Phase ==
This section covers key items that we will work on to integrate the Product team with other teams; PTLs, TC, and other User Committee working groups.

☑ Form a [[ProductTeam/User Stories|draft workflow]] for user story planning and prioritization 
☑ Present [http://www.slideshare.net/ShamailXD/a-glimpse-at-the-roadmap-deck-v5-final initial multi-release roadmap] at the Liberty summit 
☑ Review user stories being pursued during the pilot with the Cross Project team [[http://eavesdrop.openstack.org/meetings/crossproject/2015/crossproject.2015-09-01-21.00.html meeting log]] 
✅ Conduct gaps analysis, partner with developers, and present specs/blueprints in project meetings 
✅ Build user story tracker and share with community 
✅ Engage in operator and design summit sessions to gather and share feedback, respectively 
✅ At the Tokyo summit, present the multi-release direction for L through N releases 

== Sub-Pages ==
{| class="wikitable"
|-
| [[ProductTeam/User Stories|User Stories Landing Page]] || [[ProductTeam/MultiRelease Roadmap|Multi-Release Roadmap Sub-Team]]
|-
| [[ProductTeam/User Stories/Capacity Management|Capacity Management User Story]] || [[ProductTeam/User Stories/Lifecycle Management|Life-cycle Management for VMs]]
|-
| [[ProductTeam/User Stories/Onboarding Legacy Apps|On-boarding Legacy Apps User Story]]|| [[ProductTeam/User Stories/Rolling Upgrades|Rolling Upgrades User Story]]
|-
| [[ProductTeam/Core Team|Core Team Page]]||[http://specs.openstack.org/openstack/openstack-user-stories/ OpenStack User Stories Generated Page]
|}

[[Category: Working_Groups]]

ProductTeam

2017-01-04T19:52:53Z

Kaizen: /* Meeting and Communication Information */

= OpenStack Product Working Group =

== Meeting and Communication Information ==

'''Next Team Meeting will be on January 9, 2017 - Happy Holidays!'''

Date, time, and IRC channel: http://eavesdrop.openstack.org/#OpenStack_Product_WG
Past IRC meeting logs: http://eavesdrop.openstack.org/meetings/product_working_group/
Etherpad archives: https://etherpad.openstack.org/p/PWG_Archives
[http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee Subscribe to the User Committee Mailing List]
Please add [Product] tag in the subject line when sending messages to the User Committee Mailing List
[http://lists.openstack.org/pipermail/product-wg/ Product WG Mailing List Archives (new membership disabled)]

== Ocata Cycle Priorities ==
* Establish simplified process for user-story creation, review and analysis to enable all Work Groups/Teams to contribute and enable a wider range of feedback.
**Lead: Shamail Tahir
* Complete the User Story Tracker
**Lead: Jamey
* Support the Community transitions: Redesigned work flow and User Committee expansion
** Lead: Carol

Ocata Midcycle Planning etherpad: https://etherpad.openstack.org/p/MIL-pwg-meetup

== Barcelona Summit ==
We will get together in Barcelona for a working session. The session is scheduled for October 27th from 11:00 - 12:30 in AC Hotel - P14 - Pedralbes. The session details are here: https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/16855/product-working-group-working-session.

The planning etherpad: https://etherpad.openstack.org/p/PWG_Session_Oct16_BCN

== Mission ==
We will support the OpenStack developer community in their desire to build open-source cloud software that reflects the needs of the various markets adopting the platform by creating user stories that reflect the voice of the end-users/operators. These user stories will focus on items that have traditionally been harder to implement based on the need for cross-project coordination and significant development time (spanning multiple releases). Finally, the team will also focus on sharing regular updates on directional insights for the platform (gathered from key members from the development community) in the form of a multi-release roadmap. The ultimate mission is to create a focus on areas that are high-impact and remove barriers to adoption/operation/scale of OpenStack clouds.

== Who we are ==
The product working group consists of product managers, technologists, and operators from a diverse set of organizations. The group is working to aggregate user stories from the market-focused teams (Enterprise, Telco, etc.) and cross-project functional teams (e.g. logging, upgrades, etc.), partner with the development community on resourcing, and help gather data to generate a multi-release roadmap. Most of the user stories being tracked by this team consists of items that can span multiple releases and usually have cross-project dependencies.

The group aims to **improve the quality of the delivery process, the delivered product, and the product experience for operators and end users**.

== Objectives ==
The objectives of this working group, based on the mission, are therefore to:

=== [https://github.com/openstack/openstack-user-stories Collect Feedback and Aggregate Requirements] ===
This group will collect (and aggregate) user, admin, customer, and operator requirements. The group should also interface with and gather data from, the other groups collecting requirements for specific verticals, markets, or user segments (e.g. Operators, Win The Enterprise, Personas, NFV/Telco, End Users/App Developers, etc.)

=== [[ProductTeam/User Stories|User Story Planning, Prioritization, and Development]] ===
Develop a repeatable, transparent, process for prioritization of [http://specs.openstack.org/openstack/openstack-user-stories/ user stories]; create blueprints/specs (or bug report) associated with the user story on a per-release cycle basis. The team will work within their organizations to fill any necessary resource gaps and create a tracker to track the implementation progress of the user story across projects and multiple releases. The criteria for the process along with the results should be clearly communicated with the community and our end-customers.

=== [[ProductTeam/MultiRelease Roadmap|Multi-release Roadmap]] ===
Generate a multi-release roadmap based on the aggregated data and resulting themes/requirements. The roadmap will be socialized, transparently, to community stakeholders for agreement and approval. After a roadmap has been established/approved, the OpenStack community will be notified of the results, the drivers for the decision, and its impact over multiple releases to consumers (and developers) of the platform.

== Methodology ==
The team requires establishing a workflow, identifying stakeholders/partners in the community, providing a means to track progress against user stories, and ensuring routine interlocks with other members/groups in the community due to the wide spectrum of items being worked on concurrently. The Product WG has established sub-teams/roles to divide tasks to ensure quality and timeliness of our collective output.

=== Sub-Teams / Roles ===
==== Roadmap Release Team ====
The roadmap release team consists of CPLs and other members of the Product WG. This team has a [[ProductTeam/MultiRelease Roadmap|dedicated sub-page]] which includes more information.

==== Product WG Cross Project Liaisons ====
OpenStack uses a concept called Cross Project Liaisons to facilitate communications between projects that might require collaboration/coordination with each other. The cross-project liaisons representing a certain team will co-locate with another team to become participating members and serve as the conduit between the two project teams. You can find a list of the Product WG CPLs here: https://wiki.openstack.org/wiki/CrossProjectLiaisons#Product_Working_Group

==== User Story Owners ====
The User Story Owners are members of the Product WG team who have volunteered to help manage/lead/track a user story from submission to completion. They will also help with the decomposition of the user stories into blueprints/specs, gather resources to aid with authoring/completing blueprints/specs, and work with the CPLs to ensure the "big picture"/objective associated with the user story is being taken into account since user stories will often include multiple "moving parts" in a single release and require tracking across releases.
 
While user stories are stored/tracked using the [https://github.com/openstack/openstack-user-stories openstack-user-stories repo] and the [http://specs.openstack.org/openstack/openstack-user-stories/ specs page]. The user story owners maintain a [https://wiki.openstack.org/wiki/ProductTeam/User_Stories#Sub-Pages_for_Active_User_Stories sub-page] for each user story to provide information on team meetings and additional artifacts.

==== OpenStack User Stories Core Members ====
The members of the openstack-user-stories-core team carefully review all changes proposed to the openstack-user-story repository (which is where the Product WG stores user stories and tracking data). The responsibilities, expectations, and process for membership in the openstack-user-stores-core team can be [[ProductTeam/Core_Team|found here]].

==== Series of Activities per Release ====
In conclusion, to achieve the various objectives, the Product WG will pursue multiple activities throughout each release. The chart below attempts to map these activities on top of the standard 6-month release schedule for OpenStack releases.

==FAQs==
The Product WG has compiled a list of [[ProductTeam/FrequentlyAskedQuestions|Frequently Asked Questions]].

[[File:Pwgactivities.png|framed|center]]

== Product WG Pilot Phase ==
This section covers key items that we will work on to integrate the Product team with other teams; PTLs, TC, and other User Committee working groups.

☑ Form a [[ProductTeam/User Stories|draft workflow]] for user story planning and prioritization 
☑ Present [http://www.slideshare.net/ShamailXD/a-glimpse-at-the-roadmap-deck-v5-final initial multi-release roadmap] at the Liberty summit 
☑ Review user stories being pursued during the pilot with the Cross Project team [[http://eavesdrop.openstack.org/meetings/crossproject/2015/crossproject.2015-09-01-21.00.html meeting log]] 
✅ Conduct gaps analysis, partner with developers, and present specs/blueprints in project meetings 
✅ Build user story tracker and share with community 
✅ Engage in operator and design summit sessions to gather and share feedback, respectively 
✅ At the Tokyo summit, present the multi-release direction for L through N releases 

== Sub-Pages ==
{| class="wikitable"
|-
| [[ProductTeam/User Stories|User Stories Landing Page]] || [[ProductTeam/MultiRelease Roadmap|Multi-Release Roadmap Sub-Team]]
|-
| [[ProductTeam/User Stories/Capacity Management|Capacity Management User Story]] || [[ProductTeam/User Stories/Lifecycle Management|Life-cycle Management for VMs]]
|-
| [[ProductTeam/User Stories/Onboarding Legacy Apps|On-boarding Legacy Apps User Story]]|| [[ProductTeam/User Stories/Rolling Upgrades|Rolling Upgrades User Story]]
|-
| [[ProductTeam/Core Team|Core Team Page]]||[http://specs.openstack.org/openstack/openstack-user-stories/ OpenStack User Stories Generated Page]
|}

[[Category: Working_Groups]]

Governance/Foundation/UserCommittee

2016-12-12T21:22:39Z

Kaizen: /* Working Groups and Teams */

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 user committee mission is to:

* 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
* 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

[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].

Attend our fortnightly IRC meetings Every two weeks (on odd weeks) on Monday at 1900 UTC:
Next US meeting: '''Monday, Dec 5th, 2016 at 1900 UTC''' in (freenode) #openstack-meeting

Proposed Agenda:
* Review proposed bylaws changes:
https://docs.google.com/document/d/1QmLOeseAkjBWM_TXsUeKBErNaSHnuZp81II0T71ARfo/edit?usp=sharing
* Proposed charter changes (to match proposed bylaws):
https://review.openstack.org/#/c/404318/
* Open

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 ==

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].
* 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"
|-
! 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.
|-
| [[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.
|-
| [[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
|-
| [[Enterprise Working Group]] || Active || Carol Barrett || Enterprise Vendors and Customers || #Enterprise-WG || Action plans to solve Enterprise Private Cloud needs and issues.
|-
| [[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, Cecilia Comeaux || 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
|-
| [[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.
|-
| [[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.
|-
| [[Scientific_working_group|Scientific Working Group]] || Active || Stig Telfer & Blair Blethwaite || Scientific Institutions Deploying, Operating and Contributing to OpenStack || #Scientific-WG || see wiki page
|-
| [[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.
|}

=== 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
|-
| Jamey McCabe || jamemcc@gmail.com
|-
| Nemat Bidokhti || nematollah.bidokhti@huawei.com
|-
| Rochelle (Rocky) Grober || rochelle.grober@huawei.com
|-
|}

Governance/InteropWG

2016-12-07T05:41:13Z

Kaizen: Kaizen moved page Governance/DefCoreCommittee to Governance/InteropWG: DefCore Committee was renamed to Interop WG

This Committee was formed during the OpenStack Ice House Summit in Hong Kong by Board Resolution on 11/4.

''DefCore sets base requirements by defining 1) capabilities, 2) code and 3) must-pass tests for all OpenStack products. This definition uses community resources and involvement to drive interoperability by creating the minimum standards for products labeled "OpenStack."''

Our mission is to define "OpenStack Core" as chartered by the by-laws.

== Important Artifacts ==
# [https://github.com/openstack/defcore/blob/master/doc/source/process/Lexicon.rst Terms Definition]
# [https://github.com/openstack/defcore/blob/master/doc/source/process/CoreDefinition.rst 10 Core Principles] (board approved Hong Kong Summit)
# [https://github.com/openstack/defcore/blob/master/doc/source/process/PlatformCap.rst Capability Levels: Component and Platform] (board approved October 2014)
# [https://github.com/openstack/defcore/blob/master/doc/source/process/CoreCriteria.rst 12 Scoring Criteria] (board approved Atlanta Summit)
# [https://github.com/openstack/defcore/blob/master/doc/source/process/DesignatedSections.rst 10 Designed Sections Principles] (board approved December 2014)
# [https://github.com/openstack/defcore/blob/master/doc/source/process/GovernanceProcess.rst DefCore Governance:]
# [https://github.com/openstack/defcore/blob/master/doc/source/process/2015A.rst DefCore Process]
# Capabilities & Sections
## [https://github.com/openstack/defcore/blob/master/doc/source/guidelines/2015.03.rst 2015.03] (review [https://github.com/openstack/defcore/blob/master/2015.03.json JSON] for details)
## [https://github.com/openstack/defcore/blob/master/doc/source/guidelines/2015.04.rst 2015.04] (review [https://github.com/openstack/defcore/blob/master/2015.04.json JSON] for details)
## [https://github.com/openstack/defcore/blob/master/doc/source/guidelines/2015.05.rst 2015.05] (review [https://github.com/openstack/defcore/blob/master/2015.05.json JSON] for details)
## [https://github.com/openstack/defcore/blob/master/doc/source/guidelines/2015.07.rst 2015.07] (review [https://github.com/openstack/defcore/blob/master/2015.07.json JSON] for details)
## [https://github.com/openstack/defcore/blob/master/doc/source/guidelines/2016.01.rst 2016.01] (review [https://github.com/openstack/defcore/blob/master/2016.01.json JSON] for details)
## [https://github.com/openstack/defcore/blob/master/next.json next.json (current draft of next Guideline) ]

== Objective / Scope ==

The DefCore charter is around how the OpenStack brand is applied for commercial uses. Initially, this focus is on "what is core" and sustaining that definition over time. The scope will likely expand since brand is an ongoing concern related to specialized marks and other use cases.

There are three ways in which the community uses the OpenStack brand including referring to projects.
# General community use of the mark
# Project-specific use associated with development activity
# DefCore-governed commercial use

While the top two of these uses are out of scope for DefCore, the committee has a need to participate in the discussion to ensure consistent and clear use.

== How to Engage? ==

* Join the [http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee defcore-committee] list
* Join #openstack-interop on Freenode IRC
* Follow the code at https://github.com/openstack/defcore
* Join our weekly [[Governance/DefCoreCommittee#Meetings|meetings]]
* Learn the [https://github.com/openstack/defcore/blob/master/HACKING.rst rules for submitting changes]

== Meetings ==
Meeting times and channels can be found on the [http://eavesdrop.openstack.org/#DefCore_Committee_Meeting official OpenStack IRC meeting list]. An [http://eavesdrop.openstack.org/irc-meetings.ical ICS file] of all OpenStack meetings is also available. Logs of past meetings [http://eavesdrop.openstack.org/meetings/defcore/ can be found here].

== Process Cycles ==

Defining OpenStack Core is a long term process and we are doing the work in progressive cycles. For reference, we have named the cycles. This helps describe concrete deliverables for a cycle while allowing discussion of the broader long term issues. For example, we may say that "item X is important to DefCore but out of scope for Elephant." We have found that this approach to breaking down the problem is necessary to maintain community consensus because we are taking smaller bites of the larger challenge (aka eating the elephant).

See [https://github.com/openstack/defcore/blob/master/doc/source/process/ProcessCycles.rst Process Cycles]

The current cycle is named the '''''Scale Cycle'''''.

== Current Committee Leaders ==
Current Leaders:
* [http://www.openstack.org/community/members/profile/3106 Egle Sigler] (board member, co-chair)
* [https://www.openstack.org/community/members/profile/54 Mark T. Voelker] (co-chair)
* [http://www.openstack.org/community/members/profile/10331 Chris Hoge] (Foundation staff)

You can also find information about who is contributing to DefCore [http://stackalytics.com/?release=all&metric=commits&project_type=all&module=defcore here].

[[category: defcore]]
[[Category: Working_Groups]]

Governance/DefCoreCommittee

2016-12-07T05:41:13Z

Kaizen: Kaizen moved page Governance/DefCoreCommittee to Governance/InteropWG: DefCore Committee was renamed to Interop WG

#REDIRECT [[Governance/InteropWG]]

Governance/InteropWG/RefStack

2016-12-07T05:41:13Z

Kaizen: Kaizen moved page Governance/DefCoreCommittee/RefStack to Governance/InteropWG/RefStack: DefCore Committee was renamed to Interop WG

== RefStack Mission ==
== Summary ==
=== Driving Forces ===

=== Project Goals ===
The stake holders of this project include the full spectrum of people, automatons and organizations that will touch OpenStack installations in the future. These include:
* The OpenStack foundation
* Vendors and distributors
*Operations people and organizations
*Platform developers
*End Users
*etc
The use of RefStack itself will be a bit more limited. The groups most directly affected can be referred to as our "target audience."
==== Target Audience ====
===== Product Owners =====
===== Customers =====
* OpenStack Foundation
* Vendors
* Operators
=== Road Map ===
Long Term Roadmap

=== Finding Information ===
The RefStack Developer's pages can be found at [[RefStack]]. This information includes IRC channels and meetings, schedule meetings outside of the weekly IRC meetings, links to meeting logs and minutes, FAQs, and more.

Governance/DefCoreCommittee/RefStack

2016-12-07T05:41:13Z

Kaizen: Kaizen moved page Governance/DefCoreCommittee/RefStack to Governance/InteropWG/RefStack: DefCore Committee was renamed to Interop WG

#REDIRECT [[Governance/InteropWG/RefStack]]

AUCRecognition

2016-12-06T18:14:40Z

Kaizen: /* AUC (Active User Contributor) Recognition Working Group */

== AUC (Active User Contributor) Recognition Working Group ==
''Status: Disbanded (as of December 6th, 2016)''

User Committee Members: Edgar Magana, Jon Proulx, Shilla Saebi 
Working Group Organizers: Shamail Tahir (irc: shamail), Maish Saidel-Keesing (irc: maishsk)

=== Scope ===
This working group was created to assist the [[Governance/Foundation/UserCommittee|User Committee]] (UC) define its constituency in a manner similar to how the [[Governance/Foundation/TechnicalCommittee|Technical Committee]] (TC) has defined the designation of [http://governance.openstack.org/reference/charter.html#voters-for-tc-seats-atc Active Technical Contributors] (ATC)/[http://governance.openstack.org/reference/charter.html#voters-for-ptl-seats-apc Active Project Contributors] (APC) for participants eligible to participate in the electoral process for [http://governance.openstack.org/reference/charter.html#project-team-leads Project Team Leads] (PTL) and Technical Committee members. The User Committee formally started conversations to recognize contributions inside the OpenStack community that are out of scope for the ATC designation. The scope for this new designation is currently being refined but the intent is to recognize OpenStack community contributors (such as operators) that are not committing code to an [https://governance.openstack.org/reference/projects/ OpenStack TC sanctioned project]. OpenStack community contributions such as code contributions to repositories under User Committee governance (e.g. [https://github.com/osops OSOps], [https://github.com/openstack/ops-tags-team ops-tags], etc.), active participation in any User Committee working group (e.g. [[API_Working_Group|API-WG]], [[Enterprise Working Group|Enterprise-WG]], [[ProductTeam|Product-WG]], etc.), moderating sessions at OpenStack [[Operations/Meetups|Ops-meetups]], organizing OpenStack [https://groups.openstack.org/ user group meet-ups] across the world, and many other forms of contributions are currently being considered for inclusion in the formal definition of the User Committee constituency. Please see the [http://lists.openstack.org/pipermail/community/2016-March/001422.html email] from Edgar Magana (User Committee member) and logs from the [http://eavesdrop.openstack.org/meetings/uc/2016/uc.2016-03-14-19.00.log.html March 14th, 2016] User Committee IRC meeting for more information.

=== Duration ===
Please note that this working group was formed in March 2016 as a "working team" to achieve the specific goal of helping define the formal definition for "User Committee constituency" (e.g. identify people who would be eligible for the designation selected by the User Committee similar to what ATC is for the Technical Committee). Once this working team has met its objective, it will be disbanded. This is a high-priority need and therefore we anticipate making progress against our objective within weeks to months (at the most).

=== Meeting Information ===
There are no future meetings.

=== Approach ===
* Members met regularly using an OpenStack meeting channel on IRC
* We provided periodic updates to the User Committee (at least once a month) of our progress
* The working group sent an email to the OpenStack user committee and operators mailing lists as milestones were achieved to solicit feedback from the affected OpenStack community members
* The team provided a final read-out to the User Committee once our objective has been completed. The User Committee will relay the outcome and next steps to the broader OpenStack Community.

==== Milestones ====
{| class="wikitable"
|-
! Milestone !! Goal !! References !! Status
|-
| 1 || ''Create working group, raise awareness of the intent, and set team meeting details'' || https://etherpad.openstack.org/p/acc_plan_summary http://lists.openstack.org/pipermail/community/2016-March/001422.html http://lists.openstack.org/pipermail/community/2016-April/001481.html || ''Completed''
|-
| 2 || ''Identify which community members are included in constituency and group-related activities into roles || https://etherpad.openstack.org/p/uc-recognition-roles https://etherpad.openstack.org/p/uc-recog-m2-output'' || ''Completed''
|-
| 3 || Provide recommendations on how to gather identified metrics (favoring automation whenever possible) || https://etherpad.openstack.org/p/uc-recog-m3-output || ''Completed''
|-
| 4 || Identify metrics that can be used to validate eligibility for each role || https://etherpad.openstack.org/p/uc-recog-metrics || ''Completed''
|-
| 5 || Establish/identify review board for self-nominated members || https://etherpad.openstack.org/p/uc-recog-m5-output https://etherpad.openstack.org/p/Extra-AUC-review-board-criteria || ''Completed''
|-
| 6 || Share findings with User Committee through a final read-out || http://www.slideshare.net/ShamailXD/openstack-auc-overview || Completed
|-
| 7 || Disband working group once the objective has been achieved || || Completed
|}

Enterprise Working Group

2016-11-21T18:51:02Z

Kaizen: /* Team Meeting */

__NOTOC__
'''Status''': Active

'''Organisers''': Carol Barrett <carol.l.barrett@intel.com>

=====Mail List=====
Sign-up for the Enterprise Work Group mailing listː http://lists.openstack.org/cgi-bin/mailman/listinfo/enterprise-wg

=====Mission & What We Do=====
* Identify and remove barriers to Enterprise adoption and deployment of OpenStack, through information from Enterprise Customers, Operators, Users, Analyst, etc.
* Collaborate on the development and tracking of [https://github.com/openstack/openstack-user-stories User Stories] with the Product WG.
* Partner with the OpenStack Foundation to create and promote eBooks, Customer testimonials, Reference Architectures and Solution Guides, etc. to educate and provide best practices for current and future Enterprise Customers.

Meeting calendar: [https://www.google.com/calendar/embed?src=openstack.org_c3rclpidijlk4tma0vn0cbajrk%40group.calendar.google.com&ctz=America/Chicago html view] and [https://www.google.com/calendar/ical/openstack.org_c3rclpidijlk4tma0vn0cbajrk%40group.calendar.google.com/public/basic.ics iCal, machine readable calendar]

=====Summit & Meetup Notes=====
Austin Session notes: https://etherpad.openstack.org/p/Enterprise_WG_Austin_Meetup 
Tokyo Session notes: https://etherpad.openstack.org/p/Enterprise_WG_Tokyo_Meetup 
Vancouver session notesː https://etherpad.openstack.org/p/Win-The-Enterprise-Vancouver-Meetup

 
===Team Meeting===
 

The team meets weekly, on Mondays at 1900 UTC (11:00 AM Pacific) 
Call In Info: (888) 875-9370, Bridge: 3; PC: 1520326# 
Next Meeting Etherpad: https://etherpad.openstack.org/p/EWG_11_21_16 

Previous Etherpad links can be found here: https://etherpad.openstack.org/p/Enterprise_Work_Group_Archives

==== Enterprise ISV Interop Team ====

{| class="wikitable"
|-
| Team Description || Based upon Enterprise IT Mgr requirements for Application interoperability with OpenStack, this team works with ISVs to validate their application interoperability and publish How-To Guides, User Case studies and other collateral as needed.
|-
| Etherpad || https://etherpad.openstack.org/p/Enterprise-Business-ISV
|-
| Meeting Logistics || Wednesday 17:00 UTC; Please check [https://etherpad.openstack.org/p/Enterprise-Business-ISV etherpad] for dial-in information
|-
| Previous Meeting Notes || https://etherpad.openstack.org/p/Enterprise-Business-ISV-Archive 
|-
|}

==== Reference Architecture Team ====

{| class="wikitable"
|-
| Team Description || This team develops sample Reference Architectures for leading Workloads as a guide for Operators in planning their deployments.
|-
| Etherpad || https://etherpad.openstack.org/p/EWG_Workload_Reference_Architecture
|-
| Meeting Logistics || Tuesday 20:00 UTC Please check [https://etherpad.openstack.org/p/EWG_Workload_Reference_Architecture etherpad] for dial-in information
|}

Meetings/product-team

2016-11-21T06:12:11Z

Kaizen: /* November 21, 2016 Product Team Meeting Agenda */

= November 21, 2016 Product Team Meeting Agenda =
* Discuss Roadmap refresh plan for the Ocata cycle and future self-serve model – Shamail
* Overview of Swift questions about requirements and plans to setup a call to discuss
** https://docs.google.com/document/d/1dmpNy5vSeTRn7CBCnELMFXBvshauPbnqQdNASXFnjRY/edit?usp=sharing
* Ops Midcycle Discussion
** Location: Milan, Italy
** Attendance plan
* PTG Discussion
** Attendance plan
* Follow-up on “Definition of Done” email thread
** http://lists.openstack.org/pipermail/user-committee/2016-November/001413.html

= Sep 13th, 2016 (UTC) Product Team Regional Meeting Agenda =
* User story update
* Barcelona working team meeting planning
** Duration: BoF: 40 min session, Working Team: Half Day
** Scheduling: Which day (Tues, Wed, Thur)? AM or PM?
* Others

 

''Information on previous agendas: https://etherpad.openstack.org/p/pwg_previous_agendas''

AUCRecognition

2016-11-17T17:18:38Z

Kaizen: /* Meeting Information */

== AUC (Active User Contributor) Recognition Working Group ==
''Status: Working on milestone-6 (as of Sept 22nd, 2016)''

User Committee Members: Edgar Magana, Jon Proulx, Shilla Saebi 
Working Group Organizers: Shamail Tahir (irc: shamail), Maish Saidel-Keesing (irc: maishsk)

=== Scope ===
This working group was created to assist the [[Governance/Foundation/UserCommittee|User Committee]] (UC) define its constituency in a manner similar to how the [[Governance/Foundation/TechnicalCommittee|Technical Committee]] (TC) has defined the designation of [http://governance.openstack.org/reference/charter.html#voters-for-tc-seats-atc Active Technical Contributors] (ATC)/[http://governance.openstack.org/reference/charter.html#voters-for-ptl-seats-apc Active Project Contributors] (APC) for participants eligible to participate in the electoral process for [http://governance.openstack.org/reference/charter.html#project-team-leads Project Team Leads] (PTL) and Technical Committee members. The User Committee formally started conversations to recognize contributions inside the OpenStack community that are out of scope for the ATC designation. The scope for this new designation is currently being refined but the intent is to recognize OpenStack community contributors (such as operators) that are not committing code to an [https://governance.openstack.org/reference/projects/ OpenStack TC sanctioned project]. OpenStack community contributions such as code contributions to repositories under User Committee governance (e.g. [https://github.com/osops OSOps], [https://github.com/openstack/ops-tags-team ops-tags], etc.), active participation in any User Committee working group (e.g. [[API_Working_Group|API-WG]], [[Enterprise Working Group|Enterprise-WG]], [[ProductTeam|Product-WG]], etc.), moderating sessions at OpenStack [[Operations/Meetups|Ops-meetups]], organizing OpenStack [https://groups.openstack.org/ user group meet-ups] across the world, and many other forms of contributions are currently being considered for inclusion in the formal definition of the User Committee constituency. Please see the [http://lists.openstack.org/pipermail/community/2016-March/001422.html email] from Edgar Magana (User Committee member) and logs from the [http://eavesdrop.openstack.org/meetings/uc/2016/uc.2016-03-14-19.00.log.html March 14th, 2016] User Committee IRC meeting for more information.

=== Duration ===
Please note that this working group was formed in March 2016 as a "working team" to achieve the specific goal of helping define the formal definition for "User Committee constituency" (e.g. identify people who would be eligible for the designation selected by the User Committee similar to what ATC is for the Technical Committee). Once this working team has met its objective, it will be disbanded. This is a high-priority need and therefore we anticipate making progress against our objective within weeks to months (at the most).

=== Meeting Information ===
Schedule: Thursdays at 1900 UTC
IRC Channel (on freenode): <code><nowiki>#openstack-meeting-3</nowiki></code>
Logs from past meeting: http://eavesdrop.openstack.org/meetings/auc/
'''Next Meeting: [http://www.timeanddate.com/worldclock/fixedtime.html?msg=AUC+Recognition+WG+Team+Meeting&iso=20161117T19&p1=%3A Thursday, November 17th, 2016 at 1900 UTC]'''
'''Agenda'''
* AUC Activities recap from OpenStack Summit (maishk)
** https://etherpad.openstack.org/p/BCN-ops-AUC
* Open

=== Approach ===
* Members will meet regularly using an OpenStack meeting channel on IRC
* We will provide periodic updates to the User Committee (at least once a month) of our progress
* The working group will send an email to the OpenStack user committee and operators mailing lists as milestones are achieved to solicit feedback from the affected OpenStack community members
* The team will provide a final read-out to the User Committee once our objective has been completed. The User Committee will relay the outcome and next steps to the broader OpenStack Community.

==== Milestones ====
{| class="wikitable"
|-
! Milestone !! Goal !! References !! Status
|-
| 1 || ''Create working group, raise awareness of the intent, and set team meeting details'' || https://etherpad.openstack.org/p/acc_plan_summary http://lists.openstack.org/pipermail/community/2016-March/001422.html http://lists.openstack.org/pipermail/community/2016-April/001481.html || ''Completed''
|-
| 2 || ''Identify which community members are included in constituency and group-related activities into roles || https://etherpad.openstack.org/p/uc-recognition-roles https://etherpad.openstack.org/p/uc-recog-m2-output'' || ''Completed''
|-
| 3 || Provide recommendations on how to gather identified metrics (favoring automation whenever possible) || https://etherpad.openstack.org/p/uc-recog-m3-output || ''Completed''
|-
| 4 || Identify metrics that can be used to validate eligibility for each role || https://etherpad.openstack.org/p/uc-recog-metrics || ''Completed''
|-
| 5 || Establish/identify review board for self-nominated members || https://etherpad.openstack.org/p/uc-recog-m5-output https://etherpad.openstack.org/p/Extra-AUC-review-board-criteria || ''Completed''
|-
| 6 || Share findings with User Committee through a final read-out || || Completed
|-
| 7 || Disband working group once the objective has been achieved || || Pending
|}

AUCRecognition

2016-11-10T18:38:54Z

Kaizen: /* Meeting Information */

== AUC (Active User Contributor) Recognition Working Group ==
''Status: Working on milestone-6 (as of Sept 22nd, 2016)''

User Committee Members: Edgar Magana, Jon Proulx, Shilla Saebi 
Working Group Organizers: Shamail Tahir (irc: shamail), Maish Saidel-Keesing (irc: maishsk)

=== Scope ===
This working group was created to assist the [[Governance/Foundation/UserCommittee|User Committee]] (UC) define its constituency in a manner similar to how the [[Governance/Foundation/TechnicalCommittee|Technical Committee]] (TC) has defined the designation of [http://governance.openstack.org/reference/charter.html#voters-for-tc-seats-atc Active Technical Contributors] (ATC)/[http://governance.openstack.org/reference/charter.html#voters-for-ptl-seats-apc Active Project Contributors] (APC) for participants eligible to participate in the electoral process for [http://governance.openstack.org/reference/charter.html#project-team-leads Project Team Leads] (PTL) and Technical Committee members. The User Committee formally started conversations to recognize contributions inside the OpenStack community that are out of scope for the ATC designation. The scope for this new designation is currently being refined but the intent is to recognize OpenStack community contributors (such as operators) that are not committing code to an [https://governance.openstack.org/reference/projects/ OpenStack TC sanctioned project]. OpenStack community contributions such as code contributions to repositories under User Committee governance (e.g. [https://github.com/osops OSOps], [https://github.com/openstack/ops-tags-team ops-tags], etc.), active participation in any User Committee working group (e.g. [[API_Working_Group|API-WG]], [[Enterprise Working Group|Enterprise-WG]], [[ProductTeam|Product-WG]], etc.), moderating sessions at OpenStack [[Operations/Meetups|Ops-meetups]], organizing OpenStack [https://groups.openstack.org/ user group meet-ups] across the world, and many other forms of contributions are currently being considered for inclusion in the formal definition of the User Committee constituency. Please see the [http://lists.openstack.org/pipermail/community/2016-March/001422.html email] from Edgar Magana (User Committee member) and logs from the [http://eavesdrop.openstack.org/meetings/uc/2016/uc.2016-03-14-19.00.log.html March 14th, 2016] User Committee IRC meeting for more information.

=== Duration ===
Please note that this working group was formed in March 2016 as a "working team" to achieve the specific goal of helping define the formal definition for "User Committee constituency" (e.g. identify people who would be eligible for the designation selected by the User Committee similar to what ATC is for the Technical Committee). Once this working team has met its objective, it will be disbanded. This is a high-priority need and therefore we anticipate making progress against our objective within weeks to months (at the most).

=== Meeting Information ===
Schedule: Thursdays at 1900 UTC
IRC Channel (on freenode): <code><nowiki>#openstack-meeting-3</nowiki></code>
Logs from past meeting: http://eavesdrop.openstack.org/meetings/auc/
'''Next Meeting: [http://www.timeanddate.com/worldclock/fixedtime.html?msg=AUC+Recognition+WG+Team+Meeting&iso=20161110T19&p1=%3A Thursday, November 10th, 2016 at 1900 UTC]'''
'''Agenda'''
* AUC Activities recap from OpenStack Summit (maishk)
* Open

=== Approach ===
* Members will meet regularly using an OpenStack meeting channel on IRC
* We will provide periodic updates to the User Committee (at least once a month) of our progress
* The working group will send an email to the OpenStack user committee and operators mailing lists as milestones are achieved to solicit feedback from the affected OpenStack community members
* The team will provide a final read-out to the User Committee once our objective has been completed. The User Committee will relay the outcome and next steps to the broader OpenStack Community.

==== Milestones ====
{| class="wikitable"
|-
! Milestone !! Goal !! References !! Status
|-
| 1 || ''Create working group, raise awareness of the intent, and set team meeting details'' || https://etherpad.openstack.org/p/acc_plan_summary http://lists.openstack.org/pipermail/community/2016-March/001422.html http://lists.openstack.org/pipermail/community/2016-April/001481.html || ''Completed''
|-
| 2 || ''Identify which community members are included in constituency and group-related activities into roles || https://etherpad.openstack.org/p/uc-recognition-roles https://etherpad.openstack.org/p/uc-recog-m2-output'' || ''Completed''
|-
| 3 || Provide recommendations on how to gather identified metrics (favoring automation whenever possible) || https://etherpad.openstack.org/p/uc-recog-m3-output || ''Completed''
|-
| 4 || Identify metrics that can be used to validate eligibility for each role || https://etherpad.openstack.org/p/uc-recog-metrics || ''Completed''
|-
| 5 || Establish/identify review board for self-nominated members || https://etherpad.openstack.org/p/uc-recog-m5-output https://etherpad.openstack.org/p/Extra-AUC-review-board-criteria || ''Completed''
|-
| 6 || Share findings with User Committee through a final read-out || || Completed
|-
| 7 || Disband working group once the objective has been achieved || || Pending
|}

AUCRecognition

2016-10-10T19:13:39Z

Kaizen: /* Meeting Information */

== AUC (Active User Contributor) Recognition Working Group ==
''Status: Working on milestone-6 (as of Sept 22nd, 2016)''

User Committee Members: Edgar Magana, Jon Proulx, Shilla Saebi 
Working Group Organizers: Shamail Tahir (irc: shamail), Maish Saidel-Keesing (irc: maishsk)

=== Scope ===
This working group was created to assist the [[Governance/Foundation/UserCommittee|User Committee]] (UC) define its constituency in a manner similar to how the [[Governance/Foundation/TechnicalCommittee|Technical Committee]] (TC) has defined the designation of [http://governance.openstack.org/reference/charter.html#voters-for-tc-seats-atc Active Technical Contributors] (ATC)/[http://governance.openstack.org/reference/charter.html#voters-for-ptl-seats-apc Active Project Contributors] (APC) for participants eligible to participate in the electoral process for [http://governance.openstack.org/reference/charter.html#project-team-leads Project Team Leads] (PTL) and Technical Committee members. The User Committee formally started conversations to recognize contributions inside the OpenStack community that are out of scope for the ATC designation. The scope for this new designation is currently being refined but the intent is to recognize OpenStack community contributors (such as operators) that are not committing code to an [https://governance.openstack.org/reference/projects/ OpenStack TC sanctioned project]. OpenStack community contributions such as code contributions to repositories under User Committee governance (e.g. [https://github.com/osops OSOps], [https://github.com/openstack/ops-tags-team ops-tags], etc.), active participation in any User Committee working group (e.g. [[API_Working_Group|API-WG]], [[Enterprise Working Group|Enterprise-WG]], [[ProductTeam|Product-WG]], etc.), moderating sessions at OpenStack [[Operations/Meetups|Ops-meetups]], organizing OpenStack [https://groups.openstack.org/ user group meet-ups] across the world, and many other forms of contributions are currently being considered for inclusion in the formal definition of the User Committee constituency. Please see the [http://lists.openstack.org/pipermail/community/2016-March/001422.html email] from Edgar Magana (User Committee member) and logs from the [http://eavesdrop.openstack.org/meetings/uc/2016/uc.2016-03-14-19.00.log.html March 14th, 2016] User Committee IRC meeting for more information.

=== Duration ===
Please note that this working group was formed in March 2016 as a "working team" to achieve the specific goal of helping define the formal definition for "User Committee constituency" (e.g. identify people who would be eligible for the designation selected by the User Committee similar to what ATC is for the Technical Committee). Once this working team has met its objective, it will be disbanded. This is a high-priority need and therefore we anticipate making progress against our objective within weeks to months (at the most).

=== Meeting Information ===
Schedule: Thursdays at 1900 UTC
IRC Channel (on freenode): <code><nowiki>#openstack-meeting-3</nowiki></code>
Logs from past meeting: http://eavesdrop.openstack.org/meetings/auc/
'''Next Meeting: [http://www.timeanddate.com/worldclock/fixedtime.html?msg=AUC+Recognition+WG+Team+Meeting&iso=20161020T19&p1=%3A Thursday, October 20th, 2016 at 1900 UTC]'''
'''Agenda'''
* Review AUC section in UC Charter
** https://docs.google.com/document/d/1QmLOeseAkjBWM_TXsUeKBErNaSHnuZp81II0T71ARfo/edit
* Items needed for UC readout
* Open

=== Approach ===
* Members will meet regularly using an OpenStack meeting channel on IRC
* We will provide periodic updates to the User Committee (at least once a month) of our progress
* The working group will send an email to the OpenStack user committee and operators mailing lists as milestones are achieved to solicit feedback from the affected OpenStack community members
* The team will provide a final read-out to the User Committee once our objective has been completed. The User Committee will relay the outcome and next steps to the broader OpenStack Community.

==== Milestones ====
{| class="wikitable"
|-
! Milestone !! Goal !! References !! Status
|-
| 1 || ''Create working group, raise awareness of the intent, and set team meeting details'' || https://etherpad.openstack.org/p/acc_plan_summary http://lists.openstack.org/pipermail/community/2016-March/001422.html http://lists.openstack.org/pipermail/community/2016-April/001481.html || ''Completed''
|-
| 2 || ''Identify which community members are included in constituency and group-related activities into roles || https://etherpad.openstack.org/p/uc-recognition-roles https://etherpad.openstack.org/p/uc-recog-m2-output'' || ''Completed''
|-
| 3 || Provide recommendations on how to gather identified metrics (favoring automation whenever possible) || https://etherpad.openstack.org/p/uc-recog-m3-output || ''Completed''
|-
| 4 || Identify metrics that can be used to validate eligibility for each role || https://etherpad.openstack.org/p/uc-recog-metrics || ''Completed''
|-
| 5 || Establish/identify review board for self-nominated members || https://etherpad.openstack.org/p/uc-recog-m5-output https://etherpad.openstack.org/p/Extra-AUC-review-board-criteria || ''Completed''
|-
| 6 || Share findings with User Committee through a final read-out || || Pending
|-
| 7 || Disband working group once the objective has been achieved || || Pending
|}

Governance/Foundation/UserCommittee

2016-10-10T17:16:31Z

Kaizen: /* How to Engage? */

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 user committee mission is to:

* 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
* 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

[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].

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:
* Provide an status of UC charter and next steps
* AUC update
** https://drive.google.com/open?id=0B_yCSDGnhIbzcXFENjBOeUtqRFk
* PWG: Forum Suggestions
* 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 ==

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].
* 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"
|-
! 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, Michael Krotscheck || 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
|-
| Michael Krotscheck || michael.krotscheck@hpe.com
|-
| Patricia Montenegro || patricia.montenegro@intel.com
|-
|}

AUCRecognition

2016-10-10T15:54:20Z

Kaizen: /* Milestones */

== AUC (Active User Contributor) Recognition Working Group ==
''Status: Working on milestone-6 (as of Sept 22nd, 2016)''

User Committee Members: Edgar Magana, Jon Proulx, Shilla Saebi 
Working Group Organizers: Shamail Tahir (irc: shamail), Maish Saidel-Keesing (irc: maishsk)

=== Scope ===
This working group was created to assist the [[Governance/Foundation/UserCommittee|User Committee]] (UC) define its constituency in a manner similar to how the [[Governance/Foundation/TechnicalCommittee|Technical Committee]] (TC) has defined the designation of [http://governance.openstack.org/reference/charter.html#voters-for-tc-seats-atc Active Technical Contributors] (ATC)/[http://governance.openstack.org/reference/charter.html#voters-for-ptl-seats-apc Active Project Contributors] (APC) for participants eligible to participate in the electoral process for [http://governance.openstack.org/reference/charter.html#project-team-leads Project Team Leads] (PTL) and Technical Committee members. The User Committee formally started conversations to recognize contributions inside the OpenStack community that are out of scope for the ATC designation. The scope for this new designation is currently being refined but the intent is to recognize OpenStack community contributors (such as operators) that are not committing code to an [https://governance.openstack.org/reference/projects/ OpenStack TC sanctioned project]. OpenStack community contributions such as code contributions to repositories under User Committee governance (e.g. [https://github.com/osops OSOps], [https://github.com/openstack/ops-tags-team ops-tags], etc.), active participation in any User Committee working group (e.g. [[API_Working_Group|API-WG]], [[Enterprise Working Group|Enterprise-WG]], [[ProductTeam|Product-WG]], etc.), moderating sessions at OpenStack [[Operations/Meetups|Ops-meetups]], organizing OpenStack [https://groups.openstack.org/ user group meet-ups] across the world, and many other forms of contributions are currently being considered for inclusion in the formal definition of the User Committee constituency. Please see the [http://lists.openstack.org/pipermail/community/2016-March/001422.html email] from Edgar Magana (User Committee member) and logs from the [http://eavesdrop.openstack.org/meetings/uc/2016/uc.2016-03-14-19.00.log.html March 14th, 2016] User Committee IRC meeting for more information.

=== Duration ===
Please note that this working group was formed in March 2016 as a "working team" to achieve the specific goal of helping define the formal definition for "User Committee constituency" (e.g. identify people who would be eligible for the designation selected by the User Committee similar to what ATC is for the Technical Committee). Once this working team has met its objective, it will be disbanded. This is a high-priority need and therefore we anticipate making progress against our objective within weeks to months (at the most).

=== Meeting Information ===
Schedule: Thursdays at 1900 UTC
IRC Channel (on freenode): <code><nowiki>#openstack-meeting-3</nowiki></code>
Logs from past meeting: http://eavesdrop.openstack.org/meetings/auc/
'''Next Meeting: [http://www.timeanddate.com/worldclock/fixedtime.html?msg=AUC+Recognition+WG+Team+Meeting&iso=20161006T19&p1=%3A Thursday, October 6th, 2016 at 1900 UTC]'''
'''Agenda'''
* Review status of open action items
* Items needed for UC readout
* Open

=== Approach ===
* Members will meet regularly using an OpenStack meeting channel on IRC
* We will provide periodic updates to the User Committee (at least once a month) of our progress
* The working group will send an email to the OpenStack user committee and operators mailing lists as milestones are achieved to solicit feedback from the affected OpenStack community members
* The team will provide a final read-out to the User Committee once our objective has been completed. The User Committee will relay the outcome and next steps to the broader OpenStack Community.

==== Milestones ====
{| class="wikitable"
|-
! Milestone !! Goal !! References !! Status
|-
| 1 || ''Create working group, raise awareness of the intent, and set team meeting details'' || https://etherpad.openstack.org/p/acc_plan_summary http://lists.openstack.org/pipermail/community/2016-March/001422.html http://lists.openstack.org/pipermail/community/2016-April/001481.html || ''Completed''
|-
| 2 || ''Identify which community members are included in constituency and group-related activities into roles || https://etherpad.openstack.org/p/uc-recognition-roles https://etherpad.openstack.org/p/uc-recog-m2-output'' || ''Completed''
|-
| 3 || Provide recommendations on how to gather identified metrics (favoring automation whenever possible) || https://etherpad.openstack.org/p/uc-recog-m3-output || ''Completed''
|-
| 4 || Identify metrics that can be used to validate eligibility for each role || https://etherpad.openstack.org/p/uc-recog-metrics || ''Completed''
|-
| 5 || Establish/identify review board for self-nominated members || https://etherpad.openstack.org/p/uc-recog-m5-output https://etherpad.openstack.org/p/Extra-AUC-review-board-criteria || ''Completed''
|-
| 6 || Share findings with User Committee through a final read-out || || Pending
|-
| 7 || Disband working group once the objective has been achieved || || Pending
|}

AUCRecognition

2016-10-06T14:20:20Z

Kaizen: /* AUC (Active User Contributor) Recognition Working Group */

== AUC (Active User Contributor) Recognition Working Group ==
''Status: Working on milestone-6 (as of Sept 22nd, 2016)''

User Committee Members: Edgar Magana, Jon Proulx, Shilla Saebi 
Working Group Organizers: Shamail Tahir (irc: shamail), Maish Saidel-Keesing (irc: maishsk)

=== Scope ===
This working group was created to assist the [[Governance/Foundation/UserCommittee|User Committee]] (UC) define its constituency in a manner similar to how the [[Governance/Foundation/TechnicalCommittee|Technical Committee]] (TC) has defined the designation of [http://governance.openstack.org/reference/charter.html#voters-for-tc-seats-atc Active Technical Contributors] (ATC)/[http://governance.openstack.org/reference/charter.html#voters-for-ptl-seats-apc Active Project Contributors] (APC) for participants eligible to participate in the electoral process for [http://governance.openstack.org/reference/charter.html#project-team-leads Project Team Leads] (PTL) and Technical Committee members. The User Committee formally started conversations to recognize contributions inside the OpenStack community that are out of scope for the ATC designation. The scope for this new designation is currently being refined but the intent is to recognize OpenStack community contributors (such as operators) that are not committing code to an [https://governance.openstack.org/reference/projects/ OpenStack TC sanctioned project]. OpenStack community contributions such as code contributions to repositories under User Committee governance (e.g. [https://github.com/osops OSOps], [https://github.com/openstack/ops-tags-team ops-tags], etc.), active participation in any User Committee working group (e.g. [[API_Working_Group|API-WG]], [[Enterprise Working Group|Enterprise-WG]], [[ProductTeam|Product-WG]], etc.), moderating sessions at OpenStack [[Operations/Meetups|Ops-meetups]], organizing OpenStack [https://groups.openstack.org/ user group meet-ups] across the world, and many other forms of contributions are currently being considered for inclusion in the formal definition of the User Committee constituency. Please see the [http://lists.openstack.org/pipermail/community/2016-March/001422.html email] from Edgar Magana (User Committee member) and logs from the [http://eavesdrop.openstack.org/meetings/uc/2016/uc.2016-03-14-19.00.log.html March 14th, 2016] User Committee IRC meeting for more information.

=== Duration ===
Please note that this working group was formed in March 2016 as a "working team" to achieve the specific goal of helping define the formal definition for "User Committee constituency" (e.g. identify people who would be eligible for the designation selected by the User Committee similar to what ATC is for the Technical Committee). Once this working team has met its objective, it will be disbanded. This is a high-priority need and therefore we anticipate making progress against our objective within weeks to months (at the most).

=== Meeting Information ===
Schedule: Thursdays at 1900 UTC
IRC Channel (on freenode): <code><nowiki>#openstack-meeting-3</nowiki></code>
Logs from past meeting: http://eavesdrop.openstack.org/meetings/auc/
'''Next Meeting: [http://www.timeanddate.com/worldclock/fixedtime.html?msg=AUC+Recognition+WG+Team+Meeting&iso=20161006T19&p1=%3A Thursday, October 6th, 2016 at 1900 UTC]'''
'''Agenda'''
* Review status of open action items
* Items needed for UC readout
* Open

=== Approach ===
* Members will meet regularly using an OpenStack meeting channel on IRC
* We will provide periodic updates to the User Committee (at least once a month) of our progress
* The working group will send an email to the OpenStack user committee and operators mailing lists as milestones are achieved to solicit feedback from the affected OpenStack community members
* The team will provide a final read-out to the User Committee once our objective has been completed. The User Committee will relay the outcome and next steps to the broader OpenStack Community.

==== Milestones ====
{| class="wikitable"
|-
! Milestone !! Goal !! References !! Status
|-
| 1 || ''Create working group, raise awareness of the intent, and set team meeting details'' || https://etherpad.openstack.org/p/acc_plan_summary http://lists.openstack.org/pipermail/community/2016-March/001422.html http://lists.openstack.org/pipermail/community/2016-April/001481.html || ''Completed''
|-
| 2 || ''Identify which community members are included in constituency and group-related activities into roles || https://etherpad.openstack.org/p/uc-recognition-roles https://etherpad.openstack.org/p/uc-recog-m2-output'' || ''Completed''
|-
| 3 || Provide recommendations on how to gather identified metrics (favoring automation whenever possible) || https://etherpad.openstack.org/p/uc-recog-m3-output || ''Completed'' '''[Pending Review]'''
|-
| 4 || Identify metrics that can be used to validate eligibility for each role || https://etherpad.openstack.org/p/uc-recog-metrics || ''Completed'' '''[Pending Review]'''
|-
| 5 || Establish/identify review board for self-nominated members || https://etherpad.openstack.org/p/uc-recog-m5-output || ''Completed'' '''[Pending Review]'''
|-
| 6 || Share findings with User Committee through a final read-out || || Pending
|-
| 7 || Disband working group once the objective has been achieved || || Pending
|}

AUCRecognition

2016-09-22T18:21:04Z

Kaizen: /* AUC (Active User Contributor) Recognition Working Group */

== AUC (Active User Contributor) Recognition Working Group ==
''Status: Working on milestone-6 (as of Sept 22nd, 2016)''

User Committee Members: Edgar Magana, Jon Proulx, Shilla Saebi 
Working Group Organizers: Shamail Tahir (irc: shamail), Maish Saidel-Keesing (irc: maishsk)

=== Scope ===
This working group was created to assist the [[Governance/Foundation/UserCommittee|User Committee]] (UC) define its constituency in a manner similar to how the [[Governance/Foundation/TechnicalCommittee|Technical Committee]] (TC) has defined the designation of [http://governance.openstack.org/reference/charter.html#voters-for-tc-seats-atc Active Technical Contributors] (ATC)/[http://governance.openstack.org/reference/charter.html#voters-for-ptl-seats-apc Active Project Contributors] (APC) for participants eligible to participate in the electoral process for [http://governance.openstack.org/reference/charter.html#project-team-leads Project Team Leads] (PTL) and Technical Committee members. The User Committee formally started conversations to recognize contributions inside the OpenStack community that are out of scope for the ATC designation. The scope for this new designation is currently being refined but the intent is to recognize OpenStack community contributors (such as operators) that are not committing code to an [https://governance.openstack.org/reference/projects/ OpenStack TC sanctioned project]. OpenStack community contributions such as code contributions to repositories under User Committee governance (e.g. [https://github.com/osops OSOps], [https://github.com/openstack/ops-tags-team ops-tags], etc.), active participation in any User Committee working group (e.g. [[API_Working_Group|API-WG]], [[Enterprise Working Group|Enterprise-WG]], [[ProductTeam|Product-WG]], etc.), moderating sessions at OpenStack [[Operations/Meetups|Ops-meetups]], organizing OpenStack [https://groups.openstack.org/ user group meet-ups] across the world, and many other forms of contributions are currently being considered for inclusion in the formal definition of the User Committee constituency. Please see the [http://lists.openstack.org/pipermail/community/2016-March/001422.html email] from Edgar Magana (User Committee member) and logs from the [http://eavesdrop.openstack.org/meetings/uc/2016/uc.2016-03-14-19.00.log.html March 14th, 2016] User Committee IRC meeting for more information.

=== Duration ===
Please note that this working group was formed in March 2016 as a "working team" to achieve the specific goal of helping define the formal definition for "User Committee constituency" (e.g. identify people who would be eligible for the designation selected by the User Committee similar to what ATC is for the Technical Committee). Once this working team has met its objective, it will be disbanded. This is a high-priority need and therefore we anticipate making progress against our objective within weeks to months (at the most).

=== Meeting Information ===
Schedule: Thursdays at 1900 UTC
IRC Channel (on freenode): <code><nowiki>#openstack-meeting-3</nowiki></code>
Logs from past meeting: http://eavesdrop.openstack.org/meetings/auc/
'''Next Meeting: [http://www.timeanddate.com/worldclock/fixedtime.html?msg=AUC+Recognition+WG+Team+Meeting&iso=20160922T19&p1=%3A Thursday, September 22nd, 2016 at 1900 UTC]'''
'''Agenda'''
* Review status of open action items
* Items needed for UC readout
* Open

=== Approach ===
* Members will meet regularly using an OpenStack meeting channel on IRC
* We will provide periodic updates to the User Committee (at least once a month) of our progress
* The working group will send an email to the OpenStack user committee and operators mailing lists as milestones are achieved to solicit feedback from the affected OpenStack community members
* The team will provide a final read-out to the User Committee once our objective has been completed. The User Committee will relay the outcome and next steps to the broader OpenStack Community.

==== Milestones ====
{| class="wikitable"
|-
! Milestone !! Goal !! References !! Status
|-
| 1 || ''Create working group, raise awareness of the intent, and set team meeting details'' || https://etherpad.openstack.org/p/acc_plan_summary http://lists.openstack.org/pipermail/community/2016-March/001422.html http://lists.openstack.org/pipermail/community/2016-April/001481.html || ''Completed''
|-
| 2 || ''Identify which community members are included in constituency and group-related activities into roles || https://etherpad.openstack.org/p/uc-recognition-roles https://etherpad.openstack.org/p/uc-recog-m2-output'' || ''Completed''
|-
| 3 || Provide recommendations on how to gather identified metrics (favoring automation whenever possible) || https://etherpad.openstack.org/p/uc-recog-m3-output || ''Completed'' '''[Pending Review]'''
|-
| 4 || Identify metrics that can be used to validate eligibility for each role || https://etherpad.openstack.org/p/uc-recog-metrics || ''Completed'' '''[Pending Review]'''
|-
| 5 || Establish/identify review board for self-nominated members || https://etherpad.openstack.org/p/uc-recog-m5-output || ''Completed'' '''[Pending Review]'''
|-
| 6 || Share findings with User Committee through a final read-out || || Pending
|-
| 7 || Disband working group once the objective has been achieved || || Pending
|}

AUCRecognition

2016-09-22T18:20:17Z

Kaizen: /* Milestones */

== AUC (Active User Contributor) Recognition Working Group ==
''Status: Working on milestone-5 (as of July 13th, 2016)''

User Committee Members: Edgar Magana, Jon Proulx, Shilla Saebi 
Working Group Organizers: Shamail Tahir (irc: shamail), Maish Saidel-Keesing (irc: maishsk)

=== Scope ===
This working group was created to assist the [[Governance/Foundation/UserCommittee|User Committee]] (UC) define its constituency in a manner similar to how the [[Governance/Foundation/TechnicalCommittee|Technical Committee]] (TC) has defined the designation of [http://governance.openstack.org/reference/charter.html#voters-for-tc-seats-atc Active Technical Contributors] (ATC)/[http://governance.openstack.org/reference/charter.html#voters-for-ptl-seats-apc Active Project Contributors] (APC) for participants eligible to participate in the electoral process for [http://governance.openstack.org/reference/charter.html#project-team-leads Project Team Leads] (PTL) and Technical Committee members. The User Committee formally started conversations to recognize contributions inside the OpenStack community that are out of scope for the ATC designation. The scope for this new designation is currently being refined but the intent is to recognize OpenStack community contributors (such as operators) that are not committing code to an [https://governance.openstack.org/reference/projects/ OpenStack TC sanctioned project]. OpenStack community contributions such as code contributions to repositories under User Committee governance (e.g. [https://github.com/osops OSOps], [https://github.com/openstack/ops-tags-team ops-tags], etc.), active participation in any User Committee working group (e.g. [[API_Working_Group|API-WG]], [[Enterprise Working Group|Enterprise-WG]], [[ProductTeam|Product-WG]], etc.), moderating sessions at OpenStack [[Operations/Meetups|Ops-meetups]], organizing OpenStack [https://groups.openstack.org/ user group meet-ups] across the world, and many other forms of contributions are currently being considered for inclusion in the formal definition of the User Committee constituency. Please see the [http://lists.openstack.org/pipermail/community/2016-March/001422.html email] from Edgar Magana (User Committee member) and logs from the [http://eavesdrop.openstack.org/meetings/uc/2016/uc.2016-03-14-19.00.log.html March 14th, 2016] User Committee IRC meeting for more information.

=== Duration ===
Please note that this working group was formed in March 2016 as a "working team" to achieve the specific goal of helping define the formal definition for "User Committee constituency" (e.g. identify people who would be eligible for the designation selected by the User Committee similar to what ATC is for the Technical Committee). Once this working team has met its objective, it will be disbanded. This is a high-priority need and therefore we anticipate making progress against our objective within weeks to months (at the most).

=== Meeting Information ===
Schedule: Thursdays at 1900 UTC
IRC Channel (on freenode): <code><nowiki>#openstack-meeting-3</nowiki></code>
Logs from past meeting: http://eavesdrop.openstack.org/meetings/auc/
'''Next Meeting: [http://www.timeanddate.com/worldclock/fixedtime.html?msg=AUC+Recognition+WG+Team+Meeting&iso=20160922T19&p1=%3A Thursday, September 22nd, 2016 at 1900 UTC]'''
'''Agenda'''
* Review status of open action items
* Items needed for UC readout
* Open

=== Approach ===
* Members will meet regularly using an OpenStack meeting channel on IRC
* We will provide periodic updates to the User Committee (at least once a month) of our progress
* The working group will send an email to the OpenStack user committee and operators mailing lists as milestones are achieved to solicit feedback from the affected OpenStack community members
* The team will provide a final read-out to the User Committee once our objective has been completed. The User Committee will relay the outcome and next steps to the broader OpenStack Community.

==== Milestones ====
{| class="wikitable"
|-
! Milestone !! Goal !! References !! Status
|-
| 1 || ''Create working group, raise awareness of the intent, and set team meeting details'' || https://etherpad.openstack.org/p/acc_plan_summary http://lists.openstack.org/pipermail/community/2016-March/001422.html http://lists.openstack.org/pipermail/community/2016-April/001481.html || ''Completed''
|-
| 2 || ''Identify which community members are included in constituency and group-related activities into roles || https://etherpad.openstack.org/p/uc-recognition-roles https://etherpad.openstack.org/p/uc-recog-m2-output'' || ''Completed''
|-
| 3 || Provide recommendations on how to gather identified metrics (favoring automation whenever possible) || https://etherpad.openstack.org/p/uc-recog-m3-output || ''Completed'' '''[Pending Review]'''
|-
| 4 || Identify metrics that can be used to validate eligibility for each role || https://etherpad.openstack.org/p/uc-recog-metrics || ''Completed'' '''[Pending Review]'''
|-
| 5 || Establish/identify review board for self-nominated members || https://etherpad.openstack.org/p/uc-recog-m5-output || ''Completed'' '''[Pending Review]'''
|-
| 6 || Share findings with User Committee through a final read-out || || Pending
|-
| 7 || Disband working group once the objective has been achieved || || Pending
|}

AUCRecognition

2016-09-22T18:18:59Z

Kaizen: /* Meeting Information */

== AUC (Active User Contributor) Recognition Working Group ==
''Status: Working on milestone-5 (as of July 13th, 2016)''

User Committee Members: Edgar Magana, Jon Proulx, Shilla Saebi 
Working Group Organizers: Shamail Tahir (irc: shamail), Maish Saidel-Keesing (irc: maishsk)

=== Scope ===
This working group was created to assist the [[Governance/Foundation/UserCommittee|User Committee]] (UC) define its constituency in a manner similar to how the [[Governance/Foundation/TechnicalCommittee|Technical Committee]] (TC) has defined the designation of [http://governance.openstack.org/reference/charter.html#voters-for-tc-seats-atc Active Technical Contributors] (ATC)/[http://governance.openstack.org/reference/charter.html#voters-for-ptl-seats-apc Active Project Contributors] (APC) for participants eligible to participate in the electoral process for [http://governance.openstack.org/reference/charter.html#project-team-leads Project Team Leads] (PTL) and Technical Committee members. The User Committee formally started conversations to recognize contributions inside the OpenStack community that are out of scope for the ATC designation. The scope for this new designation is currently being refined but the intent is to recognize OpenStack community contributors (such as operators) that are not committing code to an [https://governance.openstack.org/reference/projects/ OpenStack TC sanctioned project]. OpenStack community contributions such as code contributions to repositories under User Committee governance (e.g. [https://github.com/osops OSOps], [https://github.com/openstack/ops-tags-team ops-tags], etc.), active participation in any User Committee working group (e.g. [[API_Working_Group|API-WG]], [[Enterprise Working Group|Enterprise-WG]], [[ProductTeam|Product-WG]], etc.), moderating sessions at OpenStack [[Operations/Meetups|Ops-meetups]], organizing OpenStack [https://groups.openstack.org/ user group meet-ups] across the world, and many other forms of contributions are currently being considered for inclusion in the formal definition of the User Committee constituency. Please see the [http://lists.openstack.org/pipermail/community/2016-March/001422.html email] from Edgar Magana (User Committee member) and logs from the [http://eavesdrop.openstack.org/meetings/uc/2016/uc.2016-03-14-19.00.log.html March 14th, 2016] User Committee IRC meeting for more information.

=== Duration ===
Please note that this working group was formed in March 2016 as a "working team" to achieve the specific goal of helping define the formal definition for "User Committee constituency" (e.g. identify people who would be eligible for the designation selected by the User Committee similar to what ATC is for the Technical Committee). Once this working team has met its objective, it will be disbanded. This is a high-priority need and therefore we anticipate making progress against our objective within weeks to months (at the most).

=== Meeting Information ===
Schedule: Thursdays at 1900 UTC
IRC Channel (on freenode): <code><nowiki>#openstack-meeting-3</nowiki></code>
Logs from past meeting: http://eavesdrop.openstack.org/meetings/auc/
'''Next Meeting: [http://www.timeanddate.com/worldclock/fixedtime.html?msg=AUC+Recognition+WG+Team+Meeting&iso=20160922T19&p1=%3A Thursday, September 22nd, 2016 at 1900 UTC]'''
'''Agenda'''
* Review status of open action items
* Items needed for UC readout
* Open

=== Approach ===
* Members will meet regularly using an OpenStack meeting channel on IRC
* We will provide periodic updates to the User Committee (at least once a month) of our progress
* The working group will send an email to the OpenStack user committee and operators mailing lists as milestones are achieved to solicit feedback from the affected OpenStack community members
* The team will provide a final read-out to the User Committee once our objective has been completed. The User Committee will relay the outcome and next steps to the broader OpenStack Community.

==== Milestones ====
{| class="wikitable"
|-
! Milestone !! Goal !! References !! Status
|-
| 1 || ''Create working group, raise awareness of the intent, and set team meeting details'' || https://etherpad.openstack.org/p/acc_plan_summary http://lists.openstack.org/pipermail/community/2016-March/001422.html http://lists.openstack.org/pipermail/community/2016-April/001481.html || ''Completed''
|-
| 2 || ''Identify which community members are included in constituency and group-related activities into roles || https://etherpad.openstack.org/p/uc-recognition-roles https://etherpad.openstack.org/p/uc-recog-m2-output'' || ''Completed''
|-
| 3 || Provide recommendations on how to gather identified metrics (favoring automation whenever possible) || https://etherpad.openstack.org/p/uc-recog-m3-output || ''Completed'' '''[Pending Review]'''
|-
| 4 || Identify metrics that can be used to validate eligibility for each role || https://etherpad.openstack.org/p/uc-recog-metrics || Pending
|-
| 5 || Establish/identify review board for self-nominated members || https://etherpad.openstack.org/p/uc-recog-m5-output || Pending
|-
| 6 || Share findings with User Committee through a final read-out || || Pending
|-
| 7 || Disband working group once the objective has been achieved || || Pending
|}

Meetings/product-team

2016-09-19T19:07:14Z

Kaizen: /* September 19th, 2016 Product Team Meeting Agenda */

= September 19th, 2016 Product Team Meeting Agenda =
* 9/26: Need someone to lead
* Barcelona Session Planning
** Planning etherpad: https://etherpad.openstack.org/p/PWG_Session_Oct16_BCN
* User Story Owner - Summit Plans
* CPL Update: Arkday (Rally), MarkBaker (Designate)
* Opens
** Community-Generated Roadmap (CGRM) Draft Review, 9/22 @ 1700 UTC (1P ET): https://zoom.us/j/272384703
 

= Sep 13th, 2016 (UTC) Product Team Regional Meeting Agenda =
* User story update
* Barcelona working team meeting planning
** Duration: BoF: 40 min session, Working Team: Half Day
** Scheduling: Which day (Tues, Wed, Thur)? AM or PM?
* Others

 

''Information on previous agendas: https://etherpad.openstack.org/p/pwg_previous_agendas''

AUCRecognition

2016-09-15T16:44:31Z

Kaizen: /* Meeting Information */

== AUC (Active User Contributor) Recognition Working Group ==
''Status: Working on milestone-5 (as of July 13th, 2016)''

User Committee Members: Edgar Magana, Jon Proulx, Shilla Saebi 
Working Group Organizers: Shamail Tahir (irc: shamail), Maish Saidel-Keesing (irc: maishsk)

=== Scope ===
This working group was created to assist the [[Governance/Foundation/UserCommittee|User Committee]] (UC) define its constituency in a manner similar to how the [[Governance/Foundation/TechnicalCommittee|Technical Committee]] (TC) has defined the designation of [http://governance.openstack.org/reference/charter.html#voters-for-tc-seats-atc Active Technical Contributors] (ATC)/[http://governance.openstack.org/reference/charter.html#voters-for-ptl-seats-apc Active Project Contributors] (APC) for participants eligible to participate in the electoral process for [http://governance.openstack.org/reference/charter.html#project-team-leads Project Team Leads] (PTL) and Technical Committee members. The User Committee formally started conversations to recognize contributions inside the OpenStack community that are out of scope for the ATC designation. The scope for this new designation is currently being refined but the intent is to recognize OpenStack community contributors (such as operators) that are not committing code to an [https://governance.openstack.org/reference/projects/ OpenStack TC sanctioned project]. OpenStack community contributions such as code contributions to repositories under User Committee governance (e.g. [https://github.com/osops OSOps], [https://github.com/openstack/ops-tags-team ops-tags], etc.), active participation in any User Committee working group (e.g. [[API_Working_Group|API-WG]], [[Enterprise Working Group|Enterprise-WG]], [[ProductTeam|Product-WG]], etc.), moderating sessions at OpenStack [[Operations/Meetups|Ops-meetups]], organizing OpenStack [https://groups.openstack.org/ user group meet-ups] across the world, and many other forms of contributions are currently being considered for inclusion in the formal definition of the User Committee constituency. Please see the [http://lists.openstack.org/pipermail/community/2016-March/001422.html email] from Edgar Magana (User Committee member) and logs from the [http://eavesdrop.openstack.org/meetings/uc/2016/uc.2016-03-14-19.00.log.html March 14th, 2016] User Committee IRC meeting for more information.

=== Duration ===
Please note that this working group was formed in March 2016 as a "working team" to achieve the specific goal of helping define the formal definition for "User Committee constituency" (e.g. identify people who would be eligible for the designation selected by the User Committee similar to what ATC is for the Technical Committee). Once this working team has met its objective, it will be disbanded. This is a high-priority need and therefore we anticipate making progress against our objective within weeks to months (at the most).

=== Meeting Information ===
Schedule: Thursdays at 1900 UTC
IRC Channel (on freenode): <code><nowiki>#openstack-meeting-3</nowiki></code>
Logs from past meeting: http://eavesdrop.openstack.org/meetings/auc/
'''Next Meeting: [http://www.timeanddate.com/worldclock/fixedtime.html?msg=AUC+Recognition+WG+Team+Meeting&iso=20160915T19&p1=%3A Thursday, September 15th, 2016 at 1900 UTC]'''
'''Agenda'''
* Review status of open action items
* Open

=== Approach ===
* Members will meet regularly using an OpenStack meeting channel on IRC
* We will provide periodic updates to the User Committee (at least once a month) of our progress
* The working group will send an email to the OpenStack user committee and operators mailing lists as milestones are achieved to solicit feedback from the affected OpenStack community members
* The team will provide a final read-out to the User Committee once our objective has been completed. The User Committee will relay the outcome and next steps to the broader OpenStack Community.

==== Milestones ====
{| class="wikitable"
|-
! Milestone !! Goal !! References !! Status
|-
| 1 || ''Create working group, raise awareness of the intent, and set team meeting details'' || https://etherpad.openstack.org/p/acc_plan_summary http://lists.openstack.org/pipermail/community/2016-March/001422.html http://lists.openstack.org/pipermail/community/2016-April/001481.html || ''Completed''
|-
| 2 || ''Identify which community members are included in constituency and group-related activities into roles || https://etherpad.openstack.org/p/uc-recognition-roles https://etherpad.openstack.org/p/uc-recog-m2-output'' || ''Completed''
|-
| 3 || Provide recommendations on how to gather identified metrics (favoring automation whenever possible) || https://etherpad.openstack.org/p/uc-recog-m3-output || ''Completed'' '''[Pending Review]'''
|-
| 4 || Identify metrics that can be used to validate eligibility for each role || https://etherpad.openstack.org/p/uc-recog-metrics || Pending
|-
| 5 || Establish/identify review board for self-nominated members || https://etherpad.openstack.org/p/uc-recog-m5-output || Pending
|-
| 6 || Share findings with User Committee through a final read-out || || Pending
|-
| 7 || Disband working group once the objective has been achieved || || Pending
|}

AUCRecognition

2016-09-15T16:43:38Z

Kaizen: /* Milestones */

== AUC (Active User Contributor) Recognition Working Group ==
''Status: Working on milestone-5 (as of July 13th, 2016)''

User Committee Members: Edgar Magana, Jon Proulx, Shilla Saebi 
Working Group Organizers: Shamail Tahir (irc: shamail), Maish Saidel-Keesing (irc: maishsk)

=== Scope ===
This working group was created to assist the [[Governance/Foundation/UserCommittee|User Committee]] (UC) define its constituency in a manner similar to how the [[Governance/Foundation/TechnicalCommittee|Technical Committee]] (TC) has defined the designation of [http://governance.openstack.org/reference/charter.html#voters-for-tc-seats-atc Active Technical Contributors] (ATC)/[http://governance.openstack.org/reference/charter.html#voters-for-ptl-seats-apc Active Project Contributors] (APC) for participants eligible to participate in the electoral process for [http://governance.openstack.org/reference/charter.html#project-team-leads Project Team Leads] (PTL) and Technical Committee members. The User Committee formally started conversations to recognize contributions inside the OpenStack community that are out of scope for the ATC designation. The scope for this new designation is currently being refined but the intent is to recognize OpenStack community contributors (such as operators) that are not committing code to an [https://governance.openstack.org/reference/projects/ OpenStack TC sanctioned project]. OpenStack community contributions such as code contributions to repositories under User Committee governance (e.g. [https://github.com/osops OSOps], [https://github.com/openstack/ops-tags-team ops-tags], etc.), active participation in any User Committee working group (e.g. [[API_Working_Group|API-WG]], [[Enterprise Working Group|Enterprise-WG]], [[ProductTeam|Product-WG]], etc.), moderating sessions at OpenStack [[Operations/Meetups|Ops-meetups]], organizing OpenStack [https://groups.openstack.org/ user group meet-ups] across the world, and many other forms of contributions are currently being considered for inclusion in the formal definition of the User Committee constituency. Please see the [http://lists.openstack.org/pipermail/community/2016-March/001422.html email] from Edgar Magana (User Committee member) and logs from the [http://eavesdrop.openstack.org/meetings/uc/2016/uc.2016-03-14-19.00.log.html March 14th, 2016] User Committee IRC meeting for more information.

=== Duration ===
Please note that this working group was formed in March 2016 as a "working team" to achieve the specific goal of helping define the formal definition for "User Committee constituency" (e.g. identify people who would be eligible for the designation selected by the User Committee similar to what ATC is for the Technical Committee). Once this working team has met its objective, it will be disbanded. This is a high-priority need and therefore we anticipate making progress against our objective within weeks to months (at the most).

=== Meeting Information ===
Schedule: Thursdays at 1900 UTC
IRC Channel (on freenode): <code><nowiki>#openstack-meeting-3</nowiki></code>
Logs from past meeting: http://eavesdrop.openstack.org/meetings/auc/
'''Next Meeting: [http://www.timeanddate.com/worldclock/fixedtime.html?msg=AUC+Recognition+WG+Team+Meeting&iso=20160901T19&p1=%3A Thursday, September 1st, 2016 at 1900 UTC]'''
'''Agenda'''
* Review feedback from Ops Meetup
** https://etherpad.openstack.org/p/NYC-ops-AUC
* Develop plan to close out WG in next 2-3 weeks

=== Approach ===
* Members will meet regularly using an OpenStack meeting channel on IRC
* We will provide periodic updates to the User Committee (at least once a month) of our progress
* The working group will send an email to the OpenStack user committee and operators mailing lists as milestones are achieved to solicit feedback from the affected OpenStack community members
* The team will provide a final read-out to the User Committee once our objective has been completed. The User Committee will relay the outcome and next steps to the broader OpenStack Community.

==== Milestones ====
{| class="wikitable"
|-
! Milestone !! Goal !! References !! Status
|-
| 1 || ''Create working group, raise awareness of the intent, and set team meeting details'' || https://etherpad.openstack.org/p/acc_plan_summary http://lists.openstack.org/pipermail/community/2016-March/001422.html http://lists.openstack.org/pipermail/community/2016-April/001481.html || ''Completed''
|-
| 2 || ''Identify which community members are included in constituency and group-related activities into roles || https://etherpad.openstack.org/p/uc-recognition-roles https://etherpad.openstack.org/p/uc-recog-m2-output'' || ''Completed''
|-
| 3 || Provide recommendations on how to gather identified metrics (favoring automation whenever possible) || https://etherpad.openstack.org/p/uc-recog-m3-output || ''Completed'' '''[Pending Review]'''
|-
| 4 || Identify metrics that can be used to validate eligibility for each role || https://etherpad.openstack.org/p/uc-recog-metrics || Pending
|-
| 5 || Establish/identify review board for self-nominated members || https://etherpad.openstack.org/p/uc-recog-m5-output || Pending
|-
| 6 || Share findings with User Committee through a final read-out || || Pending
|-
| 7 || Disband working group once the objective has been achieved || || Pending
|}

Enterprise Working Group

2016-09-09T22:26:17Z

Kaizen: /* Team Meeting */

__NOTOC__
'''Status''': Active

'''Organisers''': Carol Barrett <carol.l.barrett@intel.com>

=====Mail List=====
Sign-up for the Enterprise Work Group mailing listː http://lists.openstack.org/cgi-bin/mailman/listinfo/enterprise-wg

=====Mission & What We Do=====
* Identify and remove barriers to Enterprise adoption and deployment of OpenStack, through information from Enterprise Customers, Operators, Users, Analyst, etc.
* Collaborate on the development and tracking of [https://github.com/openstack/openstack-user-stories User Stories] with the Product WG.
* Partner with the OpenStack Foundation to create and promote eBooks, Customer testimonials, Reference Architectures and Solution Guides, etc. to educate and provide best practices for current and future Enterprise Customers.

Meeting calendar: [https://www.google.com/calendar/embed?src=openstack.org_c3rclpidijlk4tma0vn0cbajrk%40group.calendar.google.com&ctz=America/Chicago html view] and [https://www.google.com/calendar/ical/openstack.org_c3rclpidijlk4tma0vn0cbajrk%40group.calendar.google.com/public/basic.ics iCal, machine readable calendar]

=====Summit & Meetup Notes=====
Austin Session notes: https://etherpad.openstack.org/p/Enterprise_WG_Austin_Meetup 
Tokyo Session notes: https://etherpad.openstack.org/p/Enterprise_WG_Tokyo_Meetup 
Vancouver session notesː https://etherpad.openstack.org/p/Win-The-Enterprise-Vancouver-Meetup

 
===Team Meeting===
The team meets weekly, on Mondays at 1900 UTC (12:00PM Pacific) 
Call In Info: (888) 875-9370, Bridge: 3; PC: 7333828# 
Next Meeting Etherpad: https://etherpad.openstack.org/p/EWG_9_12_16 

Previous Etherpad links can be found here: https://etherpad.openstack.org/p/Enterprise_Work_Group_Archives

==== Enterprise ISV Interop Team ====

{| class="wikitable"
|-
| Team Description || Based upon Enterprise IT Mgr requirements for Application interoperability with OpenStack, this team works with ISVs to validate their application interoperability and publish How-To Guides, User Case studies and other collateral as needed.
|-
| Etherpad || https://etherpad.openstack.org/p/Enterprise-Business-ISV
|-
| Meeting Logistics || Wednesday 10:00AM PST; Please check [https://etherpad.openstack.org/p/Enterprise-Business-ISV etherpad] for dial-in information
|-
| Previous Meeting Notes || https://etherpad.openstack.org/p/Enterprise-Business-ISV-Archive 
|-
|}

Meetings/product-team

2016-09-09T22:20:54Z

Kaizen: /* September 12th, 2016 Product Team Meeting Agenda */

= September 12th, 2016 Product Team Meeting Agenda =
* Midcycle Review/Update
** https://etherpad.openstack.org/p/PWG_8_29_16
* Community Generated Roadmap - Update Plans
* Barcelona working team meeting planning
** Duration: BoF: 40 min session, Working Team: Half Day
** Scheduling: Which day (Tues, Wed, Thur)? AM or PM?
* Overview of Forum Proposal
** Overview of concept and identify volunteers
** https://www.dropbox.com/s/t3p3dc0stljsx88/diagram.png?dl=0
* Opens
 

= Sep 13th, 2016 (UTC) Product Team Regional Meeting Agenda =
* User story update
* Others
 

''Information on previous agendas: https://etherpad.openstack.org/p/pwg_previous_agendas''