OpenStack - User contributions [en]

CrossProjectLiaisons

2020-06-05T16:25:39Z

Colleen Murphy: /* First Contact SIG */

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 far more projects consuming code from Oslo libraries than we have Oslo contributors. That means it is not possible for the Oslo team to keep track of how every project is using Oslo code. We are asking for one person from each project to serve as a liaison between the project and Oslo, to let us know when they are having issues with a library, and to assist with work like migrating off deprecated features.

* 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 || Moisés Guimarães de Medeiros || moguimar
|-
| Ceilometer || Julien Danjou || jd__
|-
| Cinder || Jay Bryant || jungleboyj
|-
| Cloudkitty || Christophe Sauthier || huats
|-
| Congress || Eric Kao || ekcs
|-
| Cue || Min Pae || sputnik13
|-
| Cyborg || Shaohe Feng || shaohe_feng
|-
| Designate || ||
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Abhishek Kekane|| akekane
|-
| Heat || Thomas Herve || therve
|-
| Horizon || Ivan Kolodyazhny || e0ne
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || ||
|-
| Keystone || ||
|-
| Manila || Thomas Bechtold || toabctl
|-
| Mistral || Dougal Matthews || d0ugal
|-
| Murano || Rong Zhu || zhurong
|-
| Neutron || Bernard Cafarelli || bcafarel
|-
| Nova || Stephen Finucane || stephenfin
|-
| [[Octavia]] || Michael Johnson || johnsom
|-
| Placement || Chris Dent || cdent
|-
| Qinling || Lingxian Kong || kong
|-
| 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

The liaisons list is now being maintained in the [https://opendev.org/openstack/releases/src/branch/master/data/release_liaisons.yaml release's repo here]. If you want to add/update liaison info, please submit a patch to the releases repository.

== 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
|-
| Cyborg || Li Zhu || zhuli
|-
| Freezer || Guillermo Garcia || m3mo
|-
| Glance || Abhishek Kekane || abhishekk
|-
| Heat || Steve Baker || stevebaker
|-
| Horizon || Ivan Kolodyazhny || e0ne
|-
| Ironic || ||
|-
| Keystone || Vishakha Agarwal || vishakha
|-
| Manila || Dustin Schoenbrun || dustins
|-
| Murano || Rong Zhu || zhurong
|-
| Neutron || Slawek Kaplonski || slaweq
|-
| Nova || Ghanshyam Mann || gmann
|-
| Oslo || Davanum Srinivas || dims
|-
| Qinling || Lingxian Kong || kong
|-
| 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
|-
| Cyborg || Yumeng Bao || Yumeng_Bao
|-
| Designate || Graham Hayes || mugsie
|-
| Freezer || Guillermo Garcia || m3mo
|-
| Heat || Rabi Mishra || ramishra
|-
| Horizon || Ivan Kolodyazhny || e0ne
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || Julia Kreger || TheJulia
|-
| Keystone || Vishakha Agarwal || vishakha
|-
| Kolla || Mark Goddard || mgoddard
|-
| Magnum || Spyros Trigazis || strigazi
|-
| Manila || Tom Barron || tbarron
|-
| Mistral || Dougal Matthews || d0ugal
|-
| Murano || Rong Zhu || zhurong
|-
| Neutron || Akihiro Motoki || amotoki
|-
| Nova || Stephen Finucane || stephenfin
|-
| Octavia || Michael Johnson || johnsom
|-
| OpenStack-Ansible || Amy Marrich || spotz
|-
| Ops || Robert Starmer ||
|-
| Oslo || Stephen Finucane || stephenfin
|-
| Puppet OpenStack || Emilien Macchi || EmilienM
|-
| Qinling || Lingxian Kong || kong
|-
| Rally || Boris Pavlovic || boris-42
|-
| Sahara || Telles Nobrega and Luigi Toscano || tellesnobrega, tosky
|-
| 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
|-
| Cyborg || Howard Huang || zhipeng
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Erno Kuvaja || jokke_
|-
| Heat || Zane Bitter || zaneb
|-
| Horizon || Akihiro Motoki || amotoki
|-
| Ironic || Dmitry Tantsur || dtantsur
|-
| Keystone || ||
|-
| Manila || Goutham Pacha Ravi || gouthamr
|-
| Mistral || Dougal Matthews || d0ugal
|-
| Murano || Rong Zhu || zhurong
|-
| Neutron || Brian Haley || haleyb
|-
| Nova || Lee Yarwood || lyarwood
|-
| Octavia || Carlos Goncalves || cgoncalves
|-
| Placement || Matt Riedemann || mriedem
|-
| Qinling || Lingxian Kong || kong
|-
| Sahara || Telles Nobrega || tellesnobrega
|-
| Senlin|| Qiming Teng || Qiming
|-
| Swift || Matthew Oliver || mattoliverau
|-
| Trove || Sam Matzek || smatzek
|-
| Watcher || David Tardivel || dtardivel
|-
| Zaqar || Fei Long Wang || flwang
|-
| Zun || Hongbin Lu || hongbin
|-
|}

== 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 unless explicitly listed.
* 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's core security review team in Launchpad or StoryBoard (reviewers who will be given access to embargoed vulnerabilities by the VMT)
* If the project has multiple core security review teams for different deliverables they should be listed together in the appropriate column.

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle !! Security Team
|-
| Barbican || Douglas Mendizábal or Charles Neill || redrobot / ccneill ||
|-
| Cinder || || || [https://launchpad.net/~cinder-coresec/+members all deliverables]
|-
| Glance || Brian Rosmaita || rosmaita || [https://launchpad.net/~glance-coresec/+members all deliverables]
|-
| Heat || Steve Hardy || shardy ||
|-
| Horizon || Ivan Kolodyazhny || e0ne || [https://launchpad.net/~horizon-coresec/+members all deliverables]
|-
| Keystone || Gage Hugo || gagehugo || [https://launchpad.net/~keystone-coresec/+members all deliverables]
|-
| Neutron || Miguel Lavalle || mlavalle || [https://launchpad.net/~neutron-coresec/+members all deliverables]
|-
| Nova || Michael Still || mikal || [https://launchpad.net/~nova-coresec/+members all deliverables]
|-
| Oslo || || || [https://launchpad.net/~oslo-coresec/+members all deliverables]
|-
| Sahara || Telles Nobrega || tellesnobrega ||
|-
| Swift || || || [https://launchpad.net/~swift-coresec/+members all deliverables]
|-
| Trove || Manoj Kumar || kumarmn ||
|-
|}

== API-SIG ==

The [[API_SIG|API-SIG]] 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-SIG 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-sig/liaisons.html API-SIG 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-sig/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 || Rong Zhu || zhurong
|-
| Sahara || Telles Nobrega || tellesnobrega
|}

== 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 || Erno Kuvaja, Brian Rosmaita || jokke_, rosmaita
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || Dmitry Tantsur || dtantsur
|-
| Kolla || Any Kolla Core Reviewer may ack an infra change on behalf of the PTL || mgoddard, jeffrey4l, egonzalez, spsurya, hrw, mandre are primary contacts
|-
| Neutron || Slawek Kaplonski, YAMAMOTO Takashi || slaweq, yamamoto
|-
| Documentation || Andreas Jaeger|| AJaeger

|-
| Trove || Manoj Kumar || kumarmn

|-
| Murano || Rong Zhu || zhurong

|-
| Sahara || Telles Nobrega and Luigi Toscano || tellesnobrega, tosky

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

|-
| Airship || Matt McEuen || mattmceuen
|}

== 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 || Abhishek Kekane || akekane
|-
| Heat || ||
|-
| Horizon || Akihiro Motoki || amotoki
|-
| Ironic || ||
|-
| Keystone || Vishakha Agarwal || vishakha
|-
| 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 || ||
|-
| Trove || ||
|-
| Watcher || Yumeng Bao || Yumeng
|-
| Zaqar || ||
|-
|}

== First Contact SIG ==

First Contact SIG aims to provide a place for new contributors to come for information and advice. This group will also analyze and document successful contribution models while seeking out and providing information to new members of the community. First Contact SIG project liaisons are important that they are connected with someone who can
get them up to speed on a project.

By default, the liaison will be the PTL. More than one liaison covering different TZ is recommended.

{| class="wikitable sortable"
! Name
! IRC
! Email
! Timezone
! Project
|-
| Masahito Muroi
| masahito
| muroi.masahito@lab.ntt.co.jp
|
| Blazar
|-
| Samuel Cassiba
| scas
| samuel@cassi.ba
| UTC-7
| [[Chef|Chef OpenStack]]
|-
| Jay Bryant
| jungleboyj
| jungleboyj@gmail.com
| UTC-6
| [[Cinder|Cinder]]
|-
| Ivan Kolodyazhny
| e0ne
| e0ne@e0ne.info
| UTC+3
| [[Cinder|Cinder]]
|-
| Luka Peschke
| peschk_l
| luka.peschke@objectif-libre.com
| CEST (UTC+2)
| Cloudkitty
|-
| Eric Kao
| ekcs
| ekcs.openstack@gmail.com
| UTC-8
| [[Congress|Congress]]
|-
| Ivan Kolodyazhny
| e0ne
| e0ne@e0ne.info
| UTC+3
| [[Horizon|Horizon]]
|-
| Howard Huang
| zhipeng
| zhipengh512@gmail.com
| UTC+8
| [[Cyborg/FirstContact|Cyborg]]
|-
| Graham Hayes
| mugsie
| gr@ham.ie
| UTC +1
| Designate
|-
| Petr Kovar
| pkovar
| pkovar@redhat.com
| UTC +1
| Documentation
|-
| Andrey Pavlov
| andrey-mp
| andrey.mp@gmail.com
|
| ec2-API
|-
| Saad Zaher
| szaher
| eng.szaher@gmail.com
|
| Freezer
|-
| Erno Kuvaja
| jokke_
| jokke@usr.fi
|
| Glance
|-
| Rico Lin
| ricolin
| rico.lin.guanyu@gmail.com
| UTC+8
| [[Heat|Heat]]
|-
| Frank Kloeker
| eumel8
| f.kloeker@telekom.de
| UTC+1
| I18n
|-
| Clark Boylan
| clarkb
| clark.boylan@gmail.com
| UTC+8
| Infrastructure
|-
| Julia Kreger
| TheJulia
| juliaashleykreger@gmail.com
| UTC+8
| Ironic
|-
| Ying Chen
| chenying
| ying.chen@huawei.com
|
| Karbor
|-
| Mark Goddard
| mgoddard
| mark@stackhpc.com
| UTC
| Kayobe
|-
| Kristi Nikolla
| knikolla
|
|
| Keystone
|-
| Sam Yaple
| SamYaple
| sam+git@yaple.net
|
| LOCI
|-
| Spyros Trigazis
| strigazi
| spyridon.trigazis@cern.ch
|
| Magnum
|-
| Sampath Priyankara
| samP
| sam47priya@gmail.com
|
| Masakari
|-
| Stefano Canepa
| sc
| sc@linux.it
| UTC
| Monasca
|-
| Rong Zhu
| zhurong
| aaronzhu1121@gmail.com
| UTC+8
| Murano
|-
| Miguel Lavalle
| mlavalle
| miguel.lavalle@huawei.com
| UTC-6
| [[Neutron|Neutron]]
|-
| Slawek Kaplonski
| slaweq
| skaplons@redhat.com
| UTC+1
| [[Neutron|Neutron]]
|-
| Eric Fried
| efried
| openstack@fried.cc
| UTC-6
| Nova
|-
| Alex Xu
| alex_xu
| hejie.xu@intel.com
| UTC+8
| Nova
|-
| Michael Johnson
| johnsom
| johnsomor@gmail.com
| UTC-8
| [[Octavia|Octavia]]
|-
| James Page
| jamespage
| james.page@ubuntu.com
|
| OpenStack Charms
|-
| Jean-Philippe Evrard
| evrardjp
| jean-philippe@evrard.me
| UTC+2
| OpenStack-Ansible
|-
| Matt McEuen
| mattmceuen
| matt.mceuen@att.com
| UTC-6
| OpenStack-Helm
|-
| Chason Chan (chenxing)
| chason
| chason.chan@foxmail.com
| UTC+8
| OpenStack-Manuals
|-
| Dean Troyer
| dtroyer
| dtroyer@gmail.com
|
| OpenStackClient
|-
| Ben Nemec
| bnemec
| bnemec@redhat.com
| UTC-6
| Oslo
|-
| Javier Peña
| jpena
| jpena@redhat.com
|
| Packaging-rpm
|-
| Ed Leafe
| edleafe
| ed@leafe.com
| UTC-6
| Placement
|-
| Matthew Edmonds
| edmondsw
| edmondsw@us.ibm.com
| UTC-5
| PowerVMStackers
|-
| Ghanshyam Mann
| gmann
| gmann@ghanshyammann.com
| UTC-6
| [[QA|QA]]
|-
| Andrey Kurilin
| andreykurilin
| andr.kurilin@gmail.com
|
| Rally
|-
| Chris Hoge
| hogepodge
| chris@openstack.org
|
| Refstack
|-
| Sean McGinnis
| smcginnis
| sean.mcginnis@huawei.com
| UTC-6
| Release Management
|-
| Matthew Thode
| prometheanfire
| mthode@mthode.org
|
| Requirements
|-
| Telles Mota Vidal Nobrega
| tellesnobrega
| tenobrebrega@redhat.com
|
| Sahara
|-
| Trinh Nguyen
| dangtrinhnt
| dangtrinhnt@gmail.com
| UTC+9
| [https://wiki.openstack.org/wiki/Searchlight Searchlight]
|-
| Duc Truong
| dtruong
| duc.openstack@gmail.com
| UTC-8
| [[Senlin|Senlin]]
|-
| Rong Zhu
| zhurong
| aaronzhu1121@gmail.com
| UTC+8
| Solum
|-
| Tony Breeds
| tonyb
| tony@bakeyournoodle.com
| UTC +10
| Stable Branch Maintenance
|-
| Kota Tsuyuzaki
| kota_
| tsuyuzaki@lab.ntt.co.jp
|
| Storlets
|-
| Matt Oliver
| mattolverau
| matt@oliver.net.au
| UTC+10
| Swift
|-
| John Dickinson
| notmyname
| me@not.mn
| UTC-8
| Swift
|-
| Yong Sheng Gong
| gongysh
| gong.yongsheng@99cloud.net
|
| Tacker
|-
| Trinh Nguyen
| dangtrinhnt
| dangtrinhnt@gmail.com
|
| Telemetry
|-
| Zhiyuan Cai
| zhiyuan
| luckyvega.g@gmail.com
|
| Tricircle
|-
| Alex Schultz
| mwhahaha
| aschultz@redhat.com
|
| TripleO
|-
| Lingxian Kong
| lxkong
| anlin.kong@gmail.com
| UTC+12
| Trove
|-
| Alexander Chadin
| alexchadin
| a.chadin@servionica.ru
| UTC+3
| Watcher
|-
| Claudiu Belu
| claudiub
| cbelu@cloudbasesolutions.com
|
| Winstackers
|-
| Wang Hao
| wanghao
| szmatch1986@gmail.com
|
| Zaqar
|-
| Hongbin Lu
| hongbin
| hongbin.lu@huawei.com
| UTC-5
| Zun
|-
| Victoria Martinez de la Cruz
| vkmc
| victoria@redhat.com
| UTC-3
| Manila
|-
| Dougal Matthews
| d0ugal
| dougal@redhat.com
| UTC+0
| Mistral
|-
| Renat Akhmerov
| rakhmerov
| renat.akhmerov@nokia.com
| UTC+7
| Mistral
|-
| Omer Anson
| oanson
| omer.anson@toganetworks.com
| UTC+2
| [[Dragonflow|DragonFlow]]
|-
| Surya Prakash Singh
| spsurya
| singh.surya64mnnit@gmail.com
| UTC+9
| [[Kolla|Kolla]]
|-
| Daniel Mellado
| dmellado
| dmellado@redhat.com
| UTC+1
| [[Kuryr|Kuryr]]
|-
| Irena Berezovsky
| irenab
| Irena.berezovsky@toganetworks.com
| UTC+2
| [[Kuryr|Kuryr]]
|-
| Mohammed Naser
| mnaser
| mnaser@vexxhost.com
| UTC-5
| Puppet OpenStack
|-
| Ghanshyam Mann
| gmann
| gmann@ghanshyammann.com
| UTC-6
| [[Nova|Nova]]
|-
| Dharmendra Kushwaha
| dkushwaha
| dharmendra.kushwaha@india.nec.com
| UTC+5:30
| [[Tacker|Tacker]]
|-
| Jeffrey Zhang
| Jeffrey4l
| zhang.lei.fly@gmail.com
| UTC+8
| [[Kolla|Kolla]]
|-
|Canwei Li
| licanwei
| li.canwei2@zte.com.cn
| UTC+8
| [[Watcher|Watcher]]
|-
|Ade Lee
| alee
| alee@redhat.com
| UTC-4
| [[Barbican|Barbican]]
|-
|Lingxian Kong
| lxkong
| anlin.kong@gmail.com
| UTC+12
| [[Qinling|Qinling]]
|-
|Ifat Afek
| ifat_afek
| ifat.afek@nokia.com
| UTC+3
| [[Vitrage|Vitrage]]
|-
| Eduardo Gonzalez Gutierrez
| egonzalez
| dabarren@gmail.com
| UTC+1
| [[Kolla|Kolla]]
|-
| Mark Goddard
| mgoddard
| mark@stackhpc.com
| UTC
| [[Kolla|Kolla]]
|}

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

CrossProjectLiaisons

2020-06-05T16:23:33Z

Colleen Murphy: /* Stable Branch */

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 far more projects consuming code from Oslo libraries than we have Oslo contributors. That means it is not possible for the Oslo team to keep track of how every project is using Oslo code. We are asking for one person from each project to serve as a liaison between the project and Oslo, to let us know when they are having issues with a library, and to assist with work like migrating off deprecated features.

* 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 || Moisés Guimarães de Medeiros || moguimar
|-
| Ceilometer || Julien Danjou || jd__
|-
| Cinder || Jay Bryant || jungleboyj
|-
| Cloudkitty || Christophe Sauthier || huats
|-
| Congress || Eric Kao || ekcs
|-
| Cue || Min Pae || sputnik13
|-
| Cyborg || Shaohe Feng || shaohe_feng
|-
| Designate || ||
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Abhishek Kekane|| akekane
|-
| Heat || Thomas Herve || therve
|-
| Horizon || Ivan Kolodyazhny || e0ne
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || ||
|-
| Keystone || ||
|-
| Manila || Thomas Bechtold || toabctl
|-
| Mistral || Dougal Matthews || d0ugal
|-
| Murano || Rong Zhu || zhurong
|-
| Neutron || Bernard Cafarelli || bcafarel
|-
| Nova || Stephen Finucane || stephenfin
|-
| [[Octavia]] || Michael Johnson || johnsom
|-
| Placement || Chris Dent || cdent
|-
| Qinling || Lingxian Kong || kong
|-
| 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

The liaisons list is now being maintained in the [https://opendev.org/openstack/releases/src/branch/master/data/release_liaisons.yaml release's repo here]. If you want to add/update liaison info, please submit a patch to the releases repository.

== 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
|-
| Cyborg || Li Zhu || zhuli
|-
| Freezer || Guillermo Garcia || m3mo
|-
| Glance || Abhishek Kekane || abhishekk
|-
| Heat || Steve Baker || stevebaker
|-
| Horizon || Ivan Kolodyazhny || e0ne
|-
| Ironic || ||
|-
| Keystone || Vishakha Agarwal || vishakha
|-
| Manila || Dustin Schoenbrun || dustins
|-
| Murano || Rong Zhu || zhurong
|-
| Neutron || Slawek Kaplonski || slaweq
|-
| Nova || Ghanshyam Mann || gmann
|-
| Oslo || Davanum Srinivas || dims
|-
| Qinling || Lingxian Kong || kong
|-
| 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
|-
| Cyborg || Yumeng Bao || Yumeng_Bao
|-
| Designate || Graham Hayes || mugsie
|-
| Freezer || Guillermo Garcia || m3mo
|-
| Heat || Rabi Mishra || ramishra
|-
| Horizon || Ivan Kolodyazhny || e0ne
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || Julia Kreger || TheJulia
|-
| Keystone || Vishakha Agarwal || vishakha
|-
| Kolla || Mark Goddard || mgoddard
|-
| Magnum || Spyros Trigazis || strigazi
|-
| Manila || Tom Barron || tbarron
|-
| Mistral || Dougal Matthews || d0ugal
|-
| Murano || Rong Zhu || zhurong
|-
| Neutron || Akihiro Motoki || amotoki
|-
| Nova || Stephen Finucane || stephenfin
|-
| Octavia || Michael Johnson || johnsom
|-
| OpenStack-Ansible || Amy Marrich || spotz
|-
| Ops || Robert Starmer ||
|-
| Oslo || Stephen Finucane || stephenfin
|-
| Puppet OpenStack || Emilien Macchi || EmilienM
|-
| Qinling || Lingxian Kong || kong
|-
| Rally || Boris Pavlovic || boris-42
|-
| Sahara || Telles Nobrega and Luigi Toscano || tellesnobrega, tosky
|-
| 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
|-
| Cyborg || Howard Huang || zhipeng
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Erno Kuvaja || jokke_
|-
| Heat || Zane Bitter || zaneb
|-
| Horizon || Akihiro Motoki || amotoki
|-
| Ironic || Dmitry Tantsur || dtantsur
|-
| Keystone || ||
|-
| Manila || Goutham Pacha Ravi || gouthamr
|-
| Mistral || Dougal Matthews || d0ugal
|-
| Murano || Rong Zhu || zhurong
|-
| Neutron || Brian Haley || haleyb
|-
| Nova || Lee Yarwood || lyarwood
|-
| Octavia || Carlos Goncalves || cgoncalves
|-
| Placement || Matt Riedemann || mriedem
|-
| Qinling || Lingxian Kong || kong
|-
| Sahara || Telles Nobrega || tellesnobrega
|-
| Senlin|| Qiming Teng || Qiming
|-
| Swift || Matthew Oliver || mattoliverau
|-
| Trove || Sam Matzek || smatzek
|-
| Watcher || David Tardivel || dtardivel
|-
| Zaqar || Fei Long Wang || flwang
|-
| Zun || Hongbin Lu || hongbin
|-
|}

== 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 unless explicitly listed.
* 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's core security review team in Launchpad or StoryBoard (reviewers who will be given access to embargoed vulnerabilities by the VMT)
* If the project has multiple core security review teams for different deliverables they should be listed together in the appropriate column.

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle !! Security Team
|-
| Barbican || Douglas Mendizábal or Charles Neill || redrobot / ccneill ||
|-
| Cinder || || || [https://launchpad.net/~cinder-coresec/+members all deliverables]
|-
| Glance || Brian Rosmaita || rosmaita || [https://launchpad.net/~glance-coresec/+members all deliverables]
|-
| Heat || Steve Hardy || shardy ||
|-
| Horizon || Ivan Kolodyazhny || e0ne || [https://launchpad.net/~horizon-coresec/+members all deliverables]
|-
| Keystone || Gage Hugo || gagehugo || [https://launchpad.net/~keystone-coresec/+members all deliverables]
|-
| Neutron || Miguel Lavalle || mlavalle || [https://launchpad.net/~neutron-coresec/+members all deliverables]
|-
| Nova || Michael Still || mikal || [https://launchpad.net/~nova-coresec/+members all deliverables]
|-
| Oslo || || || [https://launchpad.net/~oslo-coresec/+members all deliverables]
|-
| Sahara || Telles Nobrega || tellesnobrega ||
|-
| Swift || || || [https://launchpad.net/~swift-coresec/+members all deliverables]
|-
| Trove || Manoj Kumar || kumarmn ||
|-
|}

== API-SIG ==

The [[API_SIG|API-SIG]] 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-SIG 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-sig/liaisons.html API-SIG 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-sig/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 || Rong Zhu || zhurong
|-
| Sahara || Telles Nobrega || tellesnobrega
|}

== 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 || Erno Kuvaja, Brian Rosmaita || jokke_, rosmaita
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || Dmitry Tantsur || dtantsur
|-
| Kolla || Any Kolla Core Reviewer may ack an infra change on behalf of the PTL || mgoddard, jeffrey4l, egonzalez, spsurya, hrw, mandre are primary contacts
|-
| Neutron || Slawek Kaplonski, YAMAMOTO Takashi || slaweq, yamamoto
|-
| Documentation || Andreas Jaeger|| AJaeger

|-
| Trove || Manoj Kumar || kumarmn

|-
| Murano || Rong Zhu || zhurong

|-
| Sahara || Telles Nobrega and Luigi Toscano || tellesnobrega, tosky

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

|-
| Airship || Matt McEuen || mattmceuen
|}

== 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 || Abhishek Kekane || akekane
|-
| Heat || ||
|-
| Horizon || Akihiro Motoki || amotoki
|-
| Ironic || ||
|-
| Keystone || Vishakha Agarwal || vishakha
|-
| 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 || ||
|-
| Trove || ||
|-
| Watcher || Yumeng Bao || Yumeng
|-
| Zaqar || ||
|-
|}

== First Contact SIG ==

First Contact SIG aims to provide a place for new contributors to come for information and advice. This group will also analyze and document successful contribution models while seeking out and providing information to new members of the community. First Contact SIG project liaisons are important that they are connected with someone who can
get them up to speed on a project.

By default, the liaison will be the PTL. More than one liaison covering different TZ is recommended.

{| class="wikitable sortable"
! Name
! IRC
! Email
! Timezone
! Project
|-
| Masahito Muroi
| masahito
| muroi.masahito@lab.ntt.co.jp
|
| Blazar
|-
| Samuel Cassiba
| scas
| samuel@cassi.ba
| UTC-7
| [[Chef|Chef OpenStack]]
|-
| Jay Bryant
| jungleboyj
| jungleboyj@gmail.com
| UTC-6
| [[Cinder|Cinder]]
|-
| Ivan Kolodyazhny
| e0ne
| e0ne@e0ne.info
| UTC+3
| [[Cinder|Cinder]]
|-
| Luka Peschke
| peschk_l
| luka.peschke@objectif-libre.com
| CEST (UTC+2)
| Cloudkitty
|-
| Eric Kao
| ekcs
| ekcs.openstack@gmail.com
| UTC-8
| [[Congress|Congress]]
|-
| Ivan Kolodyazhny
| e0ne
| e0ne@e0ne.info
| UTC+3
| [[Horizon|Horizon]]
|-
| Howard Huang
| zhipeng
| zhipengh512@gmail.com
| UTC+8
| [[Cyborg/FirstContact|Cyborg]]
|-
| Graham Hayes
| mugsie
| gr@ham.ie
| UTC +1
| Designate
|-
| Petr Kovar
| pkovar
| pkovar@redhat.com
| UTC +1
| Documentation
|-
| Andrey Pavlov
| andrey-mp
| andrey.mp@gmail.com
|
| ec2-API
|-
| Saad Zaher
| szaher
| eng.szaher@gmail.com
|
| Freezer
|-
| Erno Kuvaja
| jokke_
| jokke@usr.fi
|
| Glance
|-
| Rico Lin
| ricolin
| rico.lin.guanyu@gmail.com
| UTC+8
| [[Heat|Heat]]
|-
| Frank Kloeker
| eumel8
| f.kloeker@telekom.de
| UTC+1
| I18n
|-
| Clark Boylan
| clarkb
| clark.boylan@gmail.com
| UTC+8
| Infrastructure
|-
| Julia Kreger
| TheJulia
| juliaashleykreger@gmail.com
| UTC+8
| Ironic
|-
| Ying Chen
| chenying
| ying.chen@huawei.com
|
| Karbor
|-
| Mark Goddard
| mgoddard
| mark@stackhpc.com
| UTC
| Kayobe
|-
| Colleen Murphy
| cmurphy
| colleen@gazlene.net
| UTC-7
| Keystone
|-
| Sam Yaple
| SamYaple
| sam+git@yaple.net
|
| LOCI
|-
| Spyros Trigazis
| strigazi
| spyridon.trigazis@cern.ch
|
| Magnum
|-
| Sampath Priyankara
| samP
| sam47priya@gmail.com
|
| Masakari
|-
| Stefano Canepa
| sc
| sc@linux.it
| UTC
| Monasca
|-
| Rong Zhu
| zhurong
| aaronzhu1121@gmail.com
| UTC+8
| Murano
|-
| Miguel Lavalle
| mlavalle
| miguel.lavalle@huawei.com
| UTC-6
| [[Neutron|Neutron]]
|-
| Slawek Kaplonski
| slaweq
| skaplons@redhat.com
| UTC+1
| [[Neutron|Neutron]]
|-
| Eric Fried
| efried
| openstack@fried.cc
| UTC-6
| Nova
|-
| Alex Xu
| alex_xu
| hejie.xu@intel.com
| UTC+8
| Nova
|-
| Michael Johnson
| johnsom
| johnsomor@gmail.com
| UTC-8
| [[Octavia|Octavia]]
|-
| James Page
| jamespage
| james.page@ubuntu.com
|
| OpenStack Charms
|-
| Jean-Philippe Evrard
| evrardjp
| jean-philippe@evrard.me
| UTC+2
| OpenStack-Ansible
|-
| Matt McEuen
| mattmceuen
| matt.mceuen@att.com
| UTC-6
| OpenStack-Helm
|-
| Chason Chan (chenxing)
| chason
| chason.chan@foxmail.com
| UTC+8
| OpenStack-Manuals
|-
| Dean Troyer
| dtroyer
| dtroyer@gmail.com
|
| OpenStackClient
|-
| Ben Nemec
| bnemec
| bnemec@redhat.com
| UTC-6
| Oslo
|-
| Javier Peña
| jpena
| jpena@redhat.com
|
| Packaging-rpm
|-
| Ed Leafe
| edleafe
| ed@leafe.com
| UTC-6
| Placement
|-
| Matthew Edmonds
| edmondsw
| edmondsw@us.ibm.com
| UTC-5
| PowerVMStackers
|-
| Ghanshyam Mann
| gmann
| gmann@ghanshyammann.com
| UTC-6
| [[QA|QA]]
|-
| Andrey Kurilin
| andreykurilin
| andr.kurilin@gmail.com
|
| Rally
|-
| Chris Hoge
| hogepodge
| chris@openstack.org
|
| Refstack
|-
| Sean McGinnis
| smcginnis
| sean.mcginnis@huawei.com
| UTC-6
| Release Management
|-
| Matthew Thode
| prometheanfire
| mthode@mthode.org
|
| Requirements
|-
| Telles Mota Vidal Nobrega
| tellesnobrega
| tenobrebrega@redhat.com
|
| Sahara
|-
| Trinh Nguyen
| dangtrinhnt
| dangtrinhnt@gmail.com
| UTC+9
| [https://wiki.openstack.org/wiki/Searchlight Searchlight]
|-
| Duc Truong
| dtruong
| duc.openstack@gmail.com
| UTC-8
| [[Senlin|Senlin]]
|-
| Rong Zhu
| zhurong
| aaronzhu1121@gmail.com
| UTC+8
| Solum
|-
| Tony Breeds
| tonyb
| tony@bakeyournoodle.com
| UTC +10
| Stable Branch Maintenance
|-
| Kota Tsuyuzaki
| kota_
| tsuyuzaki@lab.ntt.co.jp
|
| Storlets
|-
| Matt Oliver
| mattolverau
| matt@oliver.net.au
| UTC+10
| Swift
|-
| John Dickinson
| notmyname
| me@not.mn
| UTC-8
| Swift
|-
| Yong Sheng Gong
| gongysh
| gong.yongsheng@99cloud.net
|
| Tacker
|-
| Trinh Nguyen
| dangtrinhnt
| dangtrinhnt@gmail.com
|
| Telemetry
|-
| Zhiyuan Cai
| zhiyuan
| luckyvega.g@gmail.com
|
| Tricircle
|-
| Alex Schultz
| mwhahaha
| aschultz@redhat.com
|
| TripleO
|-
| Lingxian Kong
| lxkong
| anlin.kong@gmail.com
| UTC+12
| Trove
|-
| Alexander Chadin
| alexchadin
| a.chadin@servionica.ru
| UTC+3
| Watcher
|-
| Claudiu Belu
| claudiub
| cbelu@cloudbasesolutions.com
|
| Winstackers
|-
| Wang Hao
| wanghao
| szmatch1986@gmail.com
|
| Zaqar
|-
| Hongbin Lu
| hongbin
| hongbin.lu@huawei.com
| UTC-5
| Zun
|-
| Victoria Martinez de la Cruz
| vkmc
| victoria@redhat.com
| UTC-3
| Manila
|-
| Dougal Matthews
| d0ugal
| dougal@redhat.com
| UTC+0
| Mistral
|-
| Renat Akhmerov
| rakhmerov
| renat.akhmerov@nokia.com
| UTC+7
| Mistral
|-
| Omer Anson
| oanson
| omer.anson@toganetworks.com
| UTC+2
| [[Dragonflow|DragonFlow]]
|-
| Surya Prakash Singh
| spsurya
| singh.surya64mnnit@gmail.com
| UTC+9
| [[Kolla|Kolla]]
|-
| Daniel Mellado
| dmellado
| dmellado@redhat.com
| UTC+1
| [[Kuryr|Kuryr]]
|-
| Irena Berezovsky
| irenab
| Irena.berezovsky@toganetworks.com
| UTC+2
| [[Kuryr|Kuryr]]
|-
| Mohammed Naser
| mnaser
| mnaser@vexxhost.com
| UTC-5
| Puppet OpenStack
|-
| Ghanshyam Mann
| gmann
| gmann@ghanshyammann.com
| UTC-6
| [[Nova|Nova]]
|-
| Dharmendra Kushwaha
| dkushwaha
| dharmendra.kushwaha@india.nec.com
| UTC+5:30
| [[Tacker|Tacker]]
|-
| Jeffrey Zhang
| Jeffrey4l
| zhang.lei.fly@gmail.com
| UTC+8
| [[Kolla|Kolla]]
|-
|Canwei Li
| licanwei
| li.canwei2@zte.com.cn
| UTC+8
| [[Watcher|Watcher]]
|-
|Ade Lee
| alee
| alee@redhat.com
| UTC-4
| [[Barbican|Barbican]]
|-
|Lingxian Kong
| lxkong
| anlin.kong@gmail.com
| UTC+12
| [[Qinling|Qinling]]
|-
|Ifat Afek
| ifat_afek
| ifat.afek@nokia.com
| UTC+3
| [[Vitrage|Vitrage]]
|-
| Eduardo Gonzalez Gutierrez
| egonzalez
| dabarren@gmail.com
| UTC+1
| [[Kolla|Kolla]]
|-
| Mark Goddard
| mgoddard
| mark@stackhpc.com
| UTC
| [[Kolla|Kolla]]
|}

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

Consistent and Secure Default Policies Popup Team

2020-04-22T17:42:29Z

Colleen Murphy: /* Leads */

== Problem Description ==

Existing policy defaults suffer from three major faults:

# the admin-ness problem: use of policy rules like 'is_admin' or hard-coded is-admin checks results in the admin-anywhere-admin-everywhere problem and drastically inhibits true multi-tenancy since by default customers cannot have admin rights on their own projects or domains
# insecure custom roles: many policy rules simply use "" as the rule, which means there is no rule: anyone can perform that action. This means creation of a custom role (say, "nova-autoscaler" requires editing every policy file across every service to block users with such a rule from performing actions unrelated to their role
# related to #2, no support for read-only roles: keystone now has a "reader" role that comes out of the box when keystone is bootstrapped, but it currently has very little value because of the use of empty rules in service policies: users with the "reader" role can still perform write actions on services if the policy rule for such an action is empty.

== Team Goal ==

The keystone project has migrated all of its default policies to 1) use oslo.policy's scope_types attribute, which allows the policy engine to understand "system scope" and distinguish between an admin role assignment on a project versus an admin role assignment on the entire system, 2) ensure all rules use one of the default roles (admin, member, and reader) which both ensures support for a read-only role and prevents custom roles from accidental over-permissiveness. Although the problems being solved are slightly different, the keystone team found it was easiest to migrate everything at once. The rest of the OpenStack services can use this migration as a template for securing their own policies.

== Popup Team Completion Criteria ==

This team will be disbanded after:

# The majority of the projects listed below have completed their policy migrations
# A document is published detailing any pitfalls, lessons learned, and best practices that other teams should be aware of
# A community goal is proposed and accepted by the TC

== Communication ==

Use topic:policy-popup in Gerrit.

Use subject tag [policy] for mailing list discussions.

Use #openstack-dev for synchronous discussions.

== Leads ==

# Raildo Mascena <rmascena@redhat.com> (raildo)
# Ghanshyam Mann <gmann@ghanshyammann.com> (gmann)

== Liaisons ==

* Barbican: Douglas Mendizábal (redrobot)
* Nova: Ghanshyam Mann (gmann)
* Neutron: Miguel Lavalle (mlavalle)
* Cinder: Brian Rosmaita (rosmaita)
* Cyborg: Yumeng Bao (yumeng_bao@yahoo.com)
* Manila: Goutham Pacha Ravi (gouthamr)

== Members ==

* Mohammed Naser <mnaser@vexxhost.com>
* Douglas Mendizábal (IRC: redrobot) - Barbican - We're supere interested in getting this implemented for Barbican
* Ade Lee (ade_lee) - barbican
* Miguel Lavalle (mlavalle) - neutron
* Chandan Kumar (chandankumar/raukadah)<chkumar@redhat.com> - Help on Tempest and Patrole side
* Akihiro Motoki (amotoki) - horizon (horizon needs to support the new mechanism of policy definitions. It is different from server side support, so the team needs to explore its own way)
* Tobias Rydberg (tobberydberg)
* Erik McCormick <emccormick@cirrusseven.com> (emccormick)
* Tergel Munkhbat tergel@fibo.cloud
* Ghanshyam Mann (gmann): Nova, QA adopt testing for the new roles.
* Vishakha Agarwal (vishakha)- Keystone

== Team Design Documents ==

=== Keystone (completed; use as a reference) ===

* http://specs.openstack.org/openstack/keystone-specs/specs/keystone/ongoing/policy-goals-and-roadmap.html
* https://bugs.launchpad.net/keystone/+bugs?field.status%3Alist=FIXRELEASED&field.tag=default-roles+system-scope&field.tags_combinator=ANY

=== Barbican ===

* https://wiki.openstack.org/wiki/Barbican/Policy

=== Nova ===

* https://specs.openstack.org/openstack/nova-specs/specs/ussuri/approved/policy-defaults-refresh.html

=== Neutron ===

none yet

=== Cinder ===

none yet

=== Cyborg ===

* https://wiki.openstack.org/wiki/Cyborg/Policy
* https://review.opendev.org/699099

=== Manila ===

none yet

== Progress ==

=== Barbican ===

TBA

=== Nova ===

https://blueprints.launchpad.net/nova/+spec/policy-defaults-refresh

=== Neutron ===

TBA

=== Cinder ===

TBA

=== Cyborg ===

https://storyboard.openstack.org/#!/story/2007024

=== Manila ===

TBA

== Reviews ==

https://review.opendev.org/#/q/is:open+topic:policy-popup

https://review.opendev.org/#/q/topic:bp/policy-defaults-refresh+(status:open+OR+status:merged)

== References ==

* All about scopes: https://docs.openstack.org/keystone/latest/contributor/services.html#authorization-scopes
* Default roles and scopes: https://docs.openstack.org/keystone/latest/admin/service-api-protection.html
* Migration steps: https://etherpad.openstack.org/p/policy-migration-steps
* Tool to test custom policy : https://pagure.io/openstack-access-policy

Consistent and Secure Default Policies Popup Team

2020-01-21T18:21:33Z

Colleen Murphy: /* Progress */

== Problem Description ==

Existing policy defaults suffer from three major faults:

# the admin-ness problem: use of policy rules like 'is_admin' or hard-coded is-admin checks results in the admin-anywhere-admin-everywhere problem and drastically inhibits true multi-tenancy since by default customers cannot have admin rights on their own projects or domains
# insecure custom roles: many policy rules simply use "" as the rule, which means there is no rule: anyone can perform that action. This means creation of a custom role (say, "nova-autoscaler" requires editing every policy file across every service to block users with such a rule from performing actions unrelated to their role
# related to #2, no support for read-only roles: keystone now has a "reader" role that comes out of the box when keystone is bootstrapped, but it currently has very little value because of the use of empty rules in service policies: users with the "reader" role can still perform write actions on services if the policy rule for such an action is empty.

== Team Goal ==

The keystone project has migrated all of its default policies to 1) use oslo.policy's scope_types attribute, which allows the policy engine to understand "system scope" and distinguish between an admin role assignment on a project versus an admin role assignment on the entire system, 2) ensure all rules use one of the default roles (admin, member, and reader) which both ensures support for a read-only role and prevents custom roles from accidental over-permissiveness. Although the problems being solved are slightly different, the keystone team found it was easiest to migrate everything at once. The rest of the OpenStack services can use this migration as a template for securing their own policies.

== Popup Team Completion Criteria ==

This team will be disbanded after:

# The majority of the projects listed below have completed their policy migrations
# A document is published detailing any pitfalls, lessons learned, and best practices that other teams should be aware of
# A community goal is proposed and accepted by the TC

== Communication ==

Use topic:policy-popup in Gerrit.

Use subject tag [policy] for mailing list discussions.

Use #openstack-dev for synchronous discussions.

== Leads ==

# Colleen Murphy <colleen@gazlene.net> (cmurphy) [Seeking a replacement]
# Ghanshyam Mann <gmann@ghanshyammann.com> (gmann)

== Liaisons ==

* Barbican: Douglas Mendizábal (redrobot)
* Nova: Ghanshyam Mann (gmann)
* Neutron: Miguel Lavalle (mlavalle)
* Cinder: Brian Rosmaita (rosmaita)
* Cyborg: Yumeng Bao (yumeng_bao@yahoo.com)
* Manila: Goutham Pacha Ravi (gouthamr)

== Members ==

* Mohammed Naser <mnaser@vexxhost.com>
* Douglas Mendizábal (IRC: redrobot) - Barbican - We're supere interested in getting this implemented for Barbican
* Ade Lee (ade_lee) - barbican
* Miguel Lavalle (mlavalle) - neutron
* Chandan Kumar (chandankumar/raukadah)<chkumar@redhat.com> - Help on Tempest and Patrole side
* Akihiro Motoki (amotoki) - horizon (horizon needs to support the new mechanism of policy definitions. It is different from server side support, so the team needs to explore its own way)
* Tobias Rydberg (tobberydberg)
* Erik McCormick <emccormick@cirrusseven.com> (emccormick)
* Tergel Munkhbat tergel@fibo.cloud
* Ghanshyam Mann (gmann): Nova, QA adopt testing for the new roles.
* Vishakha Agarwal (vishakha)- Keystone

== Team Design Documents ==

=== Keystone (completed; use as a reference) ===

* http://specs.openstack.org/openstack/keystone-specs/specs/keystone/ongoing/policy-goals-and-roadmap.html
* https://bugs.launchpad.net/keystone/+bugs?field.status%3Alist=FIXRELEASED&field.tag=default-roles+system-scope&field.tags_combinator=ANY

=== Barbican ===

* https://wiki.openstack.org/wiki/Barbican/Policy

=== Nova ===

* https://specs.openstack.org/openstack/nova-specs/specs/ussuri/approved/policy-defaults-refresh.html

=== Neutron ===

none yet

=== Cinder ===

none yet

=== Cyborg ===

* https://wiki.openstack.org/wiki/Cyborg/Policy
* https://review.opendev.org/699099

=== Manila ===

none yet

== Progress ==

=== Barbican ===

TBA

=== Nova ===

https://blueprints.launchpad.net/nova/+spec/policy-defaults-refresh

=== Neutron ===

TBA

=== Cinder ===

TBA

=== Cyborg ===

https://storyboard.openstack.org/#!/story/2007024

=== Manila ===

TBA

== Reviews ==

https://review.opendev.org/#/q/is:open+topic:policy-popup

https://review.opendev.org/#/q/topic:bp/policy-defaults-refresh+(status:open+OR+status:merged)

== References ==

* All about scopes: https://docs.openstack.org/keystone/latest/contributor/services.html#authorization-scopes
* Default roles and scopes: https://docs.openstack.org/keystone/latest/admin/service-api-protection.html
* Migration steps: https://etherpad.openstack.org/p/policy-migration-steps
* Tool to test custom policy : https://pagure.io/openstack-access-policy

Consistent and Secure Default Policies Popup Team

2020-01-21T18:19:20Z

Colleen Murphy: /* Cyborg */

== Problem Description ==

Existing policy defaults suffer from three major faults:

# the admin-ness problem: use of policy rules like 'is_admin' or hard-coded is-admin checks results in the admin-anywhere-admin-everywhere problem and drastically inhibits true multi-tenancy since by default customers cannot have admin rights on their own projects or domains
# insecure custom roles: many policy rules simply use "" as the rule, which means there is no rule: anyone can perform that action. This means creation of a custom role (say, "nova-autoscaler" requires editing every policy file across every service to block users with such a rule from performing actions unrelated to their role
# related to #2, no support for read-only roles: keystone now has a "reader" role that comes out of the box when keystone is bootstrapped, but it currently has very little value because of the use of empty rules in service policies: users with the "reader" role can still perform write actions on services if the policy rule for such an action is empty.

== Team Goal ==

The keystone project has migrated all of its default policies to 1) use oslo.policy's scope_types attribute, which allows the policy engine to understand "system scope" and distinguish between an admin role assignment on a project versus an admin role assignment on the entire system, 2) ensure all rules use one of the default roles (admin, member, and reader) which both ensures support for a read-only role and prevents custom roles from accidental over-permissiveness. Although the problems being solved are slightly different, the keystone team found it was easiest to migrate everything at once. The rest of the OpenStack services can use this migration as a template for securing their own policies.

== Popup Team Completion Criteria ==

This team will be disbanded after:

# The majority of the projects listed below have completed their policy migrations
# A document is published detailing any pitfalls, lessons learned, and best practices that other teams should be aware of
# A community goal is proposed and accepted by the TC

== Communication ==

Use topic:policy-popup in Gerrit.

Use subject tag [policy] for mailing list discussions.

Use #openstack-dev for synchronous discussions.

== Leads ==

# Colleen Murphy <colleen@gazlene.net> (cmurphy) [Seeking a replacement]
# Ghanshyam Mann <gmann@ghanshyammann.com> (gmann)

== Liaisons ==

* Barbican: Douglas Mendizábal (redrobot)
* Nova: Ghanshyam Mann (gmann)
* Neutron: Miguel Lavalle (mlavalle)
* Cinder: Brian Rosmaita (rosmaita)
* Cyborg: Yumeng Bao (yumeng_bao@yahoo.com)
* Manila: Goutham Pacha Ravi (gouthamr)

== Members ==

* Mohammed Naser <mnaser@vexxhost.com>
* Douglas Mendizábal (IRC: redrobot) - Barbican - We're supere interested in getting this implemented for Barbican
* Ade Lee (ade_lee) - barbican
* Miguel Lavalle (mlavalle) - neutron
* Chandan Kumar (chandankumar/raukadah)<chkumar@redhat.com> - Help on Tempest and Patrole side
* Akihiro Motoki (amotoki) - horizon (horizon needs to support the new mechanism of policy definitions. It is different from server side support, so the team needs to explore its own way)
* Tobias Rydberg (tobberydberg)
* Erik McCormick <emccormick@cirrusseven.com> (emccormick)
* Tergel Munkhbat tergel@fibo.cloud
* Ghanshyam Mann (gmann): Nova, QA adopt testing for the new roles.
* Vishakha Agarwal (vishakha)- Keystone

== Team Design Documents ==

=== Keystone (completed; use as a reference) ===

* http://specs.openstack.org/openstack/keystone-specs/specs/keystone/ongoing/policy-goals-and-roadmap.html
* https://bugs.launchpad.net/keystone/+bugs?field.status%3Alist=FIXRELEASED&field.tag=default-roles+system-scope&field.tags_combinator=ANY

=== Barbican ===

* https://wiki.openstack.org/wiki/Barbican/Policy

=== Nova ===

* https://specs.openstack.org/openstack/nova-specs/specs/ussuri/approved/policy-defaults-refresh.html

=== Neutron ===

none yet

=== Cinder ===

none yet

=== Cyborg ===

* https://wiki.openstack.org/wiki/Cyborg/Policy
* https://review.opendev.org/699099

=== Manila ===

none yet

== Progress ==

=== Nova ===

https://blueprints.launchpad.net/nova/+spec/policy-defaults-refresh

== Reviews ==

https://review.opendev.org/#/q/is:open+topic:policy-popup

https://review.opendev.org/#/q/topic:bp/policy-defaults-refresh+(status:open+OR+status:merged)

== References ==

* All about scopes: https://docs.openstack.org/keystone/latest/contributor/services.html#authorization-scopes
* Default roles and scopes: https://docs.openstack.org/keystone/latest/admin/service-api-protection.html
* Migration steps: https://etherpad.openstack.org/p/policy-migration-steps
* Tool to test custom policy : https://pagure.io/openstack-access-policy

Consistent and Secure Default Policies Popup Team

2020-01-21T18:14:19Z

Colleen Murphy: /* Reviews */

== Problem Description ==

Existing policy defaults suffer from three major faults:

# the admin-ness problem: use of policy rules like 'is_admin' or hard-coded is-admin checks results in the admin-anywhere-admin-everywhere problem and drastically inhibits true multi-tenancy since by default customers cannot have admin rights on their own projects or domains
# insecure custom roles: many policy rules simply use "" as the rule, which means there is no rule: anyone can perform that action. This means creation of a custom role (say, "nova-autoscaler" requires editing every policy file across every service to block users with such a rule from performing actions unrelated to their role
# related to #2, no support for read-only roles: keystone now has a "reader" role that comes out of the box when keystone is bootstrapped, but it currently has very little value because of the use of empty rules in service policies: users with the "reader" role can still perform write actions on services if the policy rule for such an action is empty.

== Team Goal ==

The keystone project has migrated all of its default policies to 1) use oslo.policy's scope_types attribute, which allows the policy engine to understand "system scope" and distinguish between an admin role assignment on a project versus an admin role assignment on the entire system, 2) ensure all rules use one of the default roles (admin, member, and reader) which both ensures support for a read-only role and prevents custom roles from accidental over-permissiveness. Although the problems being solved are slightly different, the keystone team found it was easiest to migrate everything at once. The rest of the OpenStack services can use this migration as a template for securing their own policies.

== Popup Team Completion Criteria ==

This team will be disbanded after:

# The majority of the projects listed below have completed their policy migrations
# A document is published detailing any pitfalls, lessons learned, and best practices that other teams should be aware of
# A community goal is proposed and accepted by the TC

== Communication ==

Use topic:policy-popup in Gerrit.

Use subject tag [policy] for mailing list discussions.

Use #openstack-dev for synchronous discussions.

== Leads ==

# Colleen Murphy <colleen@gazlene.net> (cmurphy) [Seeking a replacement]
# Ghanshyam Mann <gmann@ghanshyammann.com> (gmann)

== Liaisons ==

* Barbican: Douglas Mendizábal (redrobot)
* Nova: Ghanshyam Mann (gmann)
* Neutron: Miguel Lavalle (mlavalle)
* Cinder: Brian Rosmaita (rosmaita)
* Cyborg: Yumeng Bao (yumeng_bao@yahoo.com)
* Manila: Goutham Pacha Ravi (gouthamr)

== Members ==

* Mohammed Naser <mnaser@vexxhost.com>
* Douglas Mendizábal (IRC: redrobot) - Barbican - We're supere interested in getting this implemented for Barbican
* Ade Lee (ade_lee) - barbican
* Miguel Lavalle (mlavalle) - neutron
* Chandan Kumar (chandankumar/raukadah)<chkumar@redhat.com> - Help on Tempest and Patrole side
* Akihiro Motoki (amotoki) - horizon (horizon needs to support the new mechanism of policy definitions. It is different from server side support, so the team needs to explore its own way)
* Tobias Rydberg (tobberydberg)
* Erik McCormick <emccormick@cirrusseven.com> (emccormick)
* Tergel Munkhbat tergel@fibo.cloud
* Ghanshyam Mann (gmann): Nova, QA adopt testing for the new roles.
* Vishakha Agarwal (vishakha)- Keystone

== Team Design Documents ==

=== Keystone (completed; use as a reference) ===

* http://specs.openstack.org/openstack/keystone-specs/specs/keystone/ongoing/policy-goals-and-roadmap.html
* https://bugs.launchpad.net/keystone/+bugs?field.status%3Alist=FIXRELEASED&field.tag=default-roles+system-scope&field.tags_combinator=ANY

=== Barbican ===

* https://wiki.openstack.org/wiki/Barbican/Policy

=== Nova ===

* https://specs.openstack.org/openstack/nova-specs/specs/ussuri/approved/policy-defaults-refresh.html

=== Neutron ===

none yet

=== Cinder ===

none yet

=== Cyborg ===

* https://wiki.openstack.org/wiki/Cyborg/Policy

=== Manila ===

none yet

== Progress ==

=== Nova ===

https://blueprints.launchpad.net/nova/+spec/policy-defaults-refresh

== Reviews ==

https://review.opendev.org/#/q/is:open+topic:policy-popup

https://review.opendev.org/#/q/topic:bp/policy-defaults-refresh+(status:open+OR+status:merged)

== References ==

* All about scopes: https://docs.openstack.org/keystone/latest/contributor/services.html#authorization-scopes
* Default roles and scopes: https://docs.openstack.org/keystone/latest/admin/service-api-protection.html
* Migration steps: https://etherpad.openstack.org/p/policy-migration-steps
* Tool to test custom policy : https://pagure.io/openstack-access-policy

Consistent and Secure Default Policies Popup Team

2020-01-21T18:14:09Z

Colleen Murphy: /* Reviews */

== Problem Description ==

Existing policy defaults suffer from three major faults:

# the admin-ness problem: use of policy rules like 'is_admin' or hard-coded is-admin checks results in the admin-anywhere-admin-everywhere problem and drastically inhibits true multi-tenancy since by default customers cannot have admin rights on their own projects or domains
# insecure custom roles: many policy rules simply use "" as the rule, which means there is no rule: anyone can perform that action. This means creation of a custom role (say, "nova-autoscaler" requires editing every policy file across every service to block users with such a rule from performing actions unrelated to their role
# related to #2, no support for read-only roles: keystone now has a "reader" role that comes out of the box when keystone is bootstrapped, but it currently has very little value because of the use of empty rules in service policies: users with the "reader" role can still perform write actions on services if the policy rule for such an action is empty.

== Team Goal ==

The keystone project has migrated all of its default policies to 1) use oslo.policy's scope_types attribute, which allows the policy engine to understand "system scope" and distinguish between an admin role assignment on a project versus an admin role assignment on the entire system, 2) ensure all rules use one of the default roles (admin, member, and reader) which both ensures support for a read-only role and prevents custom roles from accidental over-permissiveness. Although the problems being solved are slightly different, the keystone team found it was easiest to migrate everything at once. The rest of the OpenStack services can use this migration as a template for securing their own policies.

== Popup Team Completion Criteria ==

This team will be disbanded after:

# The majority of the projects listed below have completed their policy migrations
# A document is published detailing any pitfalls, lessons learned, and best practices that other teams should be aware of
# A community goal is proposed and accepted by the TC

== Communication ==

Use topic:policy-popup in Gerrit.

Use subject tag [policy] for mailing list discussions.

Use #openstack-dev for synchronous discussions.

== Leads ==

# Colleen Murphy <colleen@gazlene.net> (cmurphy) [Seeking a replacement]
# Ghanshyam Mann <gmann@ghanshyammann.com> (gmann)

== Liaisons ==

* Barbican: Douglas Mendizábal (redrobot)
* Nova: Ghanshyam Mann (gmann)
* Neutron: Miguel Lavalle (mlavalle)
* Cinder: Brian Rosmaita (rosmaita)
* Cyborg: Yumeng Bao (yumeng_bao@yahoo.com)
* Manila: Goutham Pacha Ravi (gouthamr)

== Members ==

* Mohammed Naser <mnaser@vexxhost.com>
* Douglas Mendizábal (IRC: redrobot) - Barbican - We're supere interested in getting this implemented for Barbican
* Ade Lee (ade_lee) - barbican
* Miguel Lavalle (mlavalle) - neutron
* Chandan Kumar (chandankumar/raukadah)<chkumar@redhat.com> - Help on Tempest and Patrole side
* Akihiro Motoki (amotoki) - horizon (horizon needs to support the new mechanism of policy definitions. It is different from server side support, so the team needs to explore its own way)
* Tobias Rydberg (tobberydberg)
* Erik McCormick <emccormick@cirrusseven.com> (emccormick)
* Tergel Munkhbat tergel@fibo.cloud
* Ghanshyam Mann (gmann): Nova, QA adopt testing for the new roles.
* Vishakha Agarwal (vishakha)- Keystone

== Team Design Documents ==

=== Keystone (completed; use as a reference) ===

* http://specs.openstack.org/openstack/keystone-specs/specs/keystone/ongoing/policy-goals-and-roadmap.html
* https://bugs.launchpad.net/keystone/+bugs?field.status%3Alist=FIXRELEASED&field.tag=default-roles+system-scope&field.tags_combinator=ANY

=== Barbican ===

* https://wiki.openstack.org/wiki/Barbican/Policy

=== Nova ===

* https://specs.openstack.org/openstack/nova-specs/specs/ussuri/approved/policy-defaults-refresh.html

=== Neutron ===

none yet

=== Cinder ===

none yet

=== Cyborg ===

* https://wiki.openstack.org/wiki/Cyborg/Policy

=== Manila ===

none yet

== Progress ==

=== Nova ===

https://blueprints.launchpad.net/nova/+spec/policy-defaults-refresh

== Reviews ==

https://review.opendev.org/#/q/is:open+topic:policy-popup
https://review.opendev.org/#/q/topic:bp/policy-defaults-refresh+(status:open+OR+status:merged)

== References ==

* All about scopes: https://docs.openstack.org/keystone/latest/contributor/services.html#authorization-scopes
* Default roles and scopes: https://docs.openstack.org/keystone/latest/admin/service-api-protection.html
* Migration steps: https://etherpad.openstack.org/p/policy-migration-steps
* Tool to test custom policy : https://pagure.io/openstack-access-policy

Consistent and Secure Default Policies Popup Team

2020-01-21T18:13:38Z

Colleen Murphy: /* Progress */

== Problem Description ==

Existing policy defaults suffer from three major faults:

# the admin-ness problem: use of policy rules like 'is_admin' or hard-coded is-admin checks results in the admin-anywhere-admin-everywhere problem and drastically inhibits true multi-tenancy since by default customers cannot have admin rights on their own projects or domains
# insecure custom roles: many policy rules simply use "" as the rule, which means there is no rule: anyone can perform that action. This means creation of a custom role (say, "nova-autoscaler" requires editing every policy file across every service to block users with such a rule from performing actions unrelated to their role
# related to #2, no support for read-only roles: keystone now has a "reader" role that comes out of the box when keystone is bootstrapped, but it currently has very little value because of the use of empty rules in service policies: users with the "reader" role can still perform write actions on services if the policy rule for such an action is empty.

== Team Goal ==

The keystone project has migrated all of its default policies to 1) use oslo.policy's scope_types attribute, which allows the policy engine to understand "system scope" and distinguish between an admin role assignment on a project versus an admin role assignment on the entire system, 2) ensure all rules use one of the default roles (admin, member, and reader) which both ensures support for a read-only role and prevents custom roles from accidental over-permissiveness. Although the problems being solved are slightly different, the keystone team found it was easiest to migrate everything at once. The rest of the OpenStack services can use this migration as a template for securing their own policies.

== Popup Team Completion Criteria ==

This team will be disbanded after:

# The majority of the projects listed below have completed their policy migrations
# A document is published detailing any pitfalls, lessons learned, and best practices that other teams should be aware of
# A community goal is proposed and accepted by the TC

== Communication ==

Use topic:policy-popup in Gerrit.

Use subject tag [policy] for mailing list discussions.

Use #openstack-dev for synchronous discussions.

== Leads ==

# Colleen Murphy <colleen@gazlene.net> (cmurphy) [Seeking a replacement]
# Ghanshyam Mann <gmann@ghanshyammann.com> (gmann)

== Liaisons ==

* Barbican: Douglas Mendizábal (redrobot)
* Nova: Ghanshyam Mann (gmann)
* Neutron: Miguel Lavalle (mlavalle)
* Cinder: Brian Rosmaita (rosmaita)
* Cyborg: Yumeng Bao (yumeng_bao@yahoo.com)
* Manila: Goutham Pacha Ravi (gouthamr)

== Members ==

* Mohammed Naser <mnaser@vexxhost.com>
* Douglas Mendizábal (IRC: redrobot) - Barbican - We're supere interested in getting this implemented for Barbican
* Ade Lee (ade_lee) - barbican
* Miguel Lavalle (mlavalle) - neutron
* Chandan Kumar (chandankumar/raukadah)<chkumar@redhat.com> - Help on Tempest and Patrole side
* Akihiro Motoki (amotoki) - horizon (horizon needs to support the new mechanism of policy definitions. It is different from server side support, so the team needs to explore its own way)
* Tobias Rydberg (tobberydberg)
* Erik McCormick <emccormick@cirrusseven.com> (emccormick)
* Tergel Munkhbat tergel@fibo.cloud
* Ghanshyam Mann (gmann): Nova, QA adopt testing for the new roles.
* Vishakha Agarwal (vishakha)- Keystone

== Team Design Documents ==

=== Keystone (completed; use as a reference) ===

* http://specs.openstack.org/openstack/keystone-specs/specs/keystone/ongoing/policy-goals-and-roadmap.html
* https://bugs.launchpad.net/keystone/+bugs?field.status%3Alist=FIXRELEASED&field.tag=default-roles+system-scope&field.tags_combinator=ANY

=== Barbican ===

* https://wiki.openstack.org/wiki/Barbican/Policy

=== Nova ===

* https://specs.openstack.org/openstack/nova-specs/specs/ussuri/approved/policy-defaults-refresh.html

=== Neutron ===

none yet

=== Cinder ===

none yet

=== Cyborg ===

* https://wiki.openstack.org/wiki/Cyborg/Policy

=== Manila ===

none yet

== Progress ==

=== Nova ===

https://blueprints.launchpad.net/nova/+spec/policy-defaults-refresh

== Reviews ==

https://review.opendev.org/#/q/is:open+topic:policy-popup

== References ==

* All about scopes: https://docs.openstack.org/keystone/latest/contributor/services.html#authorization-scopes
* Default roles and scopes: https://docs.openstack.org/keystone/latest/admin/service-api-protection.html
* Migration steps: https://etherpad.openstack.org/p/policy-migration-steps
* Tool to test custom policy : https://pagure.io/openstack-access-policy

Consistent and Secure Default Policies Popup Team

2019-12-23T17:50:32Z

Colleen Murphy: /* References */

== Problem Description ==

Existing policy defaults suffer from three major faults:

# the admin-ness problem: use of policy rules like 'is_admin' or hard-coded is-admin checks results in the admin-anywhere-admin-everywhere problem and drastically inhibits true multi-tenancy since by default customers cannot have admin rights on their own projects or domains
# insecure custom roles: many policy rules simply use "" as the rule, which means there is no rule: anyone can perform that action. This means creation of a custom role (say, "nova-autoscaler" requires editing every policy file across every service to block users with such a rule from performing actions unrelated to their role
# related to #2, no support for read-only roles: keystone now has a "reader" role that comes out of the box when keystone is bootstrapped, but it currently has very little value because of the use of empty rules in service policies: users with the "reader" role can still perform write actions on services if the policy rule for such an action is empty.

== Team Goal ==

The keystone project has migrated all of its default policies to 1) use oslo.policy's scope_types attribute, which allows the policy engine to understand "system scope" and distinguish between an admin role assignment on a project versus an admin role assignment on the entire system, 2) ensure all rules use one of the default roles (admin, member, and reader) which both ensures support for a read-only role and prevents custom roles from accidental over-permissiveness. Although the problems being solved are slightly different, the keystone team found it was easiest to migrate everything at once. The rest of the OpenStack services can use this migration as a template for securing their own policies.

== Popup Team Completion Criteria ==

This team will be disbanded after:

# The majority of the projects listed below have completed their policy migrations
# A document is published detailing any pitfalls, lessons learned, and best practices that other teams should be aware of
# A community goal is proposed and accepted by the TC

== Communication ==

Use topic:policy-popup in Gerrit.

Use subject tag [policy] for mailing list discussions.

Use #openstack-dev for synchronous discussions.

== Leads ==

# Colleen Murphy <colleen@gazlene.net> (cmurphy) [Seeking a replacement]
# Ghanshyam Mann <gmann@ghanshyammann.com> (gmann)

== Liaisons ==

* Barbican: Douglas Mendizábal (redrobot)
* Nova: Ghanshyam Mann (gmann)
* Neutron: Miguel Lavalle (mlavalle)
* Cinder: Brian Rosmaita (rosmaita)
* Cyborg: Yumeng Bao (yumeng_bao@yahoo.com)
* Manila: Goutham Pacha Ravi (gouthamr)

== Members ==

* Mohammed Naser <mnaser@vexxhost.com>
* Douglas Mendizábal (IRC: redrobot) - Barbican - We're supere interested in getting this implemented for Barbican
* Ade Lee (ade_lee) - barbican
* Miguel Lavalle (mlavalle) - neutron
* Chandan Kumar (chandankumar/raukadah)<chkumar@redhat.com> - Help on Tempest and Patrole side
* Akihiro Motoki (amotoki) - horizon (horizon needs to support the new mechanism of policy definitions. It is different from server side support, so the team needs to explore its own way)
* Tobias Rydberg (tobberydberg)
* Erik McCormick <emccormick@cirrusseven.com> (emccormick)
* Tergel Munkhbat tergel@fibo.cloud
* Ghanshyam Mann (gmann): Nova, QA adopt testing for the new roles.
* Vishakha Agarwal (vishakha)- Keystone

== Team Design Documents ==

=== Keystone (completed; use as a reference) ===

* http://specs.openstack.org/openstack/keystone-specs/specs/keystone/ongoing/policy-goals-and-roadmap.html
* https://bugs.launchpad.net/keystone/+bugs?field.status%3Alist=FIXRELEASED&field.tag=default-roles+system-scope&field.tags_combinator=ANY

=== Barbican ===

* https://wiki.openstack.org/wiki/Barbican/Policy

=== Nova ===

* https://specs.openstack.org/openstack/nova-specs/specs/ussuri/approved/policy-defaults-refresh.html

=== Neutron ===

none yet

=== Cinder ===

none yet

=== Cyborg ===

* https://wiki.openstack.org/wiki/Cyborg/Policy

=== Manila ===

none yet

== Progress ==

TBD - each project may have its own tracking mechanism, to be linked here

== Reviews ==

https://review.opendev.org/#/q/is:open+topic:policy-popup

== References ==

* All about scopes: https://docs.openstack.org/keystone/latest/contributor/services.html#authorization-scopes
* Default roles and scopes: https://docs.openstack.org/keystone/latest/admin/service-api-protection.html
* Migration steps: https://etherpad.openstack.org/p/policy-migration-steps
* Tool to test custom policy : https://pagure.io/openstack-access-policy

Manila/Meetings

2019-12-19T05:15:27Z

Colleen Murphy: /* Next meeting */

= Weekly Manila team meeting =
'''NOTE MEETING TIME: Thursday at 15:00 UTC'''

If you're interested in management of shared filesystems for OpenStack, we have a weekly meetings in <code><nowiki>#openstack-meeting-alt</nowiki></code>, on Thursdays at 15:00 UTC. Please feel free to add items to the agenda below. NOTE: When adding topics please include your IRC name so we know who's topic it is and how to get more info.

'''Previous meeting logs can be found here:''' http://eavesdrop.openstack.org/meetings/manila/

'''Add your name to the following list if you would like a courtesy ping:''' xyang toabctl bswartz ganso erlon tpsilva vkmc amito jgrosso dviroel lseki carloss tbarron

== Next meeting ==
'''NOTE:''' ''Include your IRC nickname next to agenda items so that you can be called upon in the meeting and arrive at the meeting promptly if placing items in agenda. You might want to put this on your calendar if you are adding items.''

'''Scheduled for 19 Dec 2019, 15:00 UTC'''
# Announcements
# Tracking our work (gouthamr)
#* #link: https://review.opendev.org/#/c/642222
# Bugs (jgrosso)
#* #link: https://etherpad.openstack.org/p/manila-bug-triage-pad-new (Bug Triage etherpad)
# Policy popup team (cmurphy)
#* How does the manila team want to organize and track policy work?
#* Any questions about the implementation that I can answer?
# Open Discussion

'''No meeting 12 Dec 2019, 15:00 UTC''' - http://lists.openstack.org/pipermail/openstack-discuss/2019-December/011538.html

== Previous meetings ==

'''Scheduled for 5 Dec 2019, 15:00 UTC'''
# Announcements
# Ussuri Virtual PTG (gouthamr)
#* #link: http://lists.openstack.org/pipermail/openstack-discuss/2019-December/011387.html
#* #link: https://etherpad.openstack.org/p/shanghai-ptg-manila-virtual
# Bugs (jgrosso)
#* #link: https://etherpad.openstack.org/p/manila-bug-triage-pad-new (Bug Triage etherpad)
# Open Discussion

'''Scheduled for 28 Nov 2019, 15:00 UTC'''

'''NOTE:''': This day is a holiday in the US (Thanksgiving), so attendance may be low. Please post urgent topics earlier and add your name.
# Announcements
#* Chair for the week is carloss
#* Our remote only PTG will happen in few weeks (If you haven't voted in the poll and want to attend to the meeting, please add your vote in #link: https://xoyondo.com/dp/qQbsoHtNhi4DCki)
#* The presentation videos of the OpenInfra Summit in Shanghai are being uploaded
# Bugs
#* Bug Czar (jgrosso) will not be available
#* #link: https://etherpad.openstack.org/p/manila-bug-triage-pad-new (Bug Triage etherpad)
# Open Discussion

'''No meeting 21 Nov 2019, 15:00 UTC''' - http://lists.openstack.org/pipermail/openstack-discuss/2019-October/010486.html

'''Scheduled for 14 Nov 2019, 15:00 UTC'''
# Announcements
#* New releases from stable branches
#* '''No meeting 21 Nov 2019, 15:00 UTC''' - http://lists.openstack.org/pipermail/openstack-discuss/2019-October/010486.html
# Project Technical Gathering Notes (tbarron)
# Capability Filter enhancement:
#* Make extra_specs value as case-insensitive (https://review.opendev.org/#/c/688053/)
# Bugs (jgrosso)
# Open Discussion

'''No meeting 7 Nov 2019, 15:00 UTC''' - http://lists.openstack.org/pipermail/openstack-discuss/2019-October/010486.html

'''Scheduled for 31 Oct 2019, 15:00 UTC'''
# Announcements
#* R-28: http://lists.openstack.org/pipermail/openstack-discuss/2019-October/010369.html
#* Upcoming meetings
#* #link: http://lists.openstack.org/pipermail/openstack-discuss/2019-October/010444.html (RDO Interviews)
#* #link: http://lists.openstack.org/pipermail/openstack-discuss/2019-October/010421.html (Ussuri Goals update)
# Python2.7 support ending soon
#* #link: http://lists.openstack.org/pipermail/openstack-discuss/2019-October/010142.html (OpenStack Mailing list discussion)
#* #link: https://review.opendev.org/#/c/691178/ (Ussuri Goal)
#* #link: https://review.opendev.org/#/q/status:open++topic:drop-py2+project:%255E.*manila.* (manila changes)
# Ussuri PTG
#** #link: https://xoyondo.com/dp/qQbsoHtNhi4DCki Remote-only PTG Poll
#** #link: https://etherpad.openstack.org/p/manila-shanghai-ptg-planning PTG Planning Etherpad
# Bugs (jgrosso)
# Open Discussion

'''Scheduled for 24 Oct 2019, 15:00 UTC'''
# Announcements
# Release from stable/queens
# Python manilaclient breakage
#* https://review.opendev.org/#/c/686142/ (no-code-change patch)
#* https://launchpad.net/bugs/1849377 (share networks tests bug)
#* https://review.opendev.org/#/c/690411/ (fix for LP 1849377)
# Ussuri PTG
#** #link: https://xoyondo.com/dp/qQbsoHtNhi4DCki Remote-only PTG Poll
#** #link: https://etherpad.openstack.org/p/manila-shanghai-ptg-planning PTG Planning Etherpad
# Add Horizon folks to manila-ui-core? (tbarron)
#* http://lists.openstack.org/pipermail/openstack-discuss/2019-October/010303.html
# Bugs (jgrosso)
# Open Discussion

'''Scheduled for 17 Oct 2019, 15:00 UTC'''
# Announcements
#* Train release has shipped
#** #link: http://lists.openstack.org/pipermail/openstack-discuss/2019-October/010156.html
#* stable/queens is going to be in EM soon
#** #link: http://lists.openstack.org/pipermail/openstack-discuss/2019-October/010161.html
#* New manila releases:
#** #link: https://review.opendev.org/#/c/689047/ Bug-fix releases for manila-ui
#** #link: https://review.opendev.org/#/c/687967/ Release manila-tempest-plugin 0.4.1
# Retire older branches?
#* Driverfixes branches
#** #link: https://opendev.org/openstack/manila/src/branch/driverfixes/mitaka
#** #link: https://opendev.org/openstack/manila/src/branch/driverfixes/newton
#** #link: https://opendev.org/openstack/manila/src/branch/driverfixes/ocata
#* Stable branches
#** #link: https://opendev.org/openstack/manila/src/branch/stable/ocata
#** #link: https://opendev.org/openstack/manila/src/branch/stable/pike
# Ussuri PTG
#** #link: https://etherpad.openstack.org/p/manila-shanghai-ptg-planning PTG Planning Etherpad
# Bugs (jgrosso)
# Open Discussion

'''Scheduled for 10 Oct 2019, 15:00 UTC'''
# Announcements
#* Core Team changes
#** #link: http://lists.openstack.org/pipermail/openstack-discuss/2019-October/009910.html
#* List of Shanghai events:
#** #link: https://www.openstack.org/summit/shanghai-2019/summit-schedule/global-search?t=manila
#** #link: https://www.openstack.org/ptg/
# "Meet the project leaders" opportunities in Shanghai
#* #link http://lists.openstack.org/pipermail/openstack-discuss/2019-October/009925.html
#* #link https://etherpad.openstack.org/p/meet-the-project-leaders
# Ussuri PTG Planning
#* #link: https://etherpad.openstack.org/p/manila-shanghai-ptg-planning PTG Planning Etherpad
# Bugs (jgrosso)
# Open Discussion

'''Scheduled for 3 Oct 2019, 15:00 UTC'''
# Announcements
#* Ussuri Schedule is live
#** #link: https://releases.openstack.org/ussuri/schedule.html
#* Manila specific deadlines have been proposed
#** #link: https://review.opendev.org/#/c/686303/
#* Core Team changes
#** #link: http://lists.openstack.org/pipermail/openstack-discuss/2019-October/009910.html
# How are our release candidates faring?
# Tempest test breakage (dviroel)
#* #link: https://bugs.launchpad.net/tempest/+bug/1846236
#* #link: https://review.opendev.org/#/c/686008/
# Python3 for third party CI
#* #link: https://wiki.openstack.org/w/index.php?title=Manila/TrainCycle#Python3_Testing
# Ussuri PTG Planning
#** #link: https://etherpad.openstack.org/p/manila-shanghai-ptg-planning PTG Planning Etherpad
# Bugs (jgrosso)
# Open Discussion

'''Scheduled for 26 September 2019, 15:00 UTC'''
# Announcements
#* Schedule
#** #LINK: https://releases.openstack.org/train/schedule.html Train Release Schedule
#* RC1 release is due today!
#** #LINK: https://review.opendev.org/#/c/684068/
#* Forum Submissions
#** #LINK: https://etherpad.openstack.org/p/manila-shanghai-forum-brainstorming
# RC1 reviews
#* #LINK: https://etherpad.openstack.org/p/manila-train-review-focus Review focus etherpad
# Ussuri OpenStack Wide goals
#* #LINK: http://lists.openstack.org/pipermail/openstack-discuss/2019-August/008277.html
#* #LINK: https://etherpad.openstack.org/p/PVG-u-series-goals
# Changing the meeting time (gouthamr)
#* #LINK: http://eavesdrop.openstack.org Current Meetings schedule for channel availability
# Bugs (jgrosso)
# Open Discussion

'''Scheduled for 19 September 2019, 15:00 UTC'''
# Announcements
#* Schedule
#** #LINK: https://releases.openstack.org/train/schedule.html Train Release Schedule
#** Next week is RC1 target, the two weeks til final RC: let's flush out and fix bugs!
#** Reminder that we are in String, Requirements, and (of course) Feature Freeze
#* Forum Submissions are due tomorrow
#**https://etherpad.openstack.org/p/manila-shanghai-forum-brainstorming
# tempest 3rd party CI
#* #LINK: https://wiki.openstack.org/w/index.php?title=Manila/TrainCycle#Python3_Testing Wiki page on $subject
# Cross Project Goals
#* #LINK: http://lists.openstack.org/pipermail/openstack-discuss/2019-August/008570.html -- PDF docs generation
#** client, ui, and manila are done -- would be good to get tempest plugin, specs
#* #LINK: https://storyboard.openstack.org/#!/story/2005477 -- IPv6 testing
#** https://review.opendev.org/#/c/682716/
# Our Work - Reviews
#* #LINK: https://etherpad.openstack.org/p/manila-train-review-focus Review focus etherpad
# Bugs
# Open Discussion

'''Scheduled for 12 September 2019, 15:00 UTC'''
# Announcements
#* Schedule
#** #LINK: https://releases.openstack.org/train/schedule.html Train Release Schedule
#** Train Milestone 3 is here
#** Feature Freeze, Soft StringFreeze, Requirements Freeze, Final release for client libraries
#** RC1 will be the week of 23 September
#* Forum Submissions open till 20 September
#**https://etherpad.openstack.org/p/manila-shanghai-forum-brainstorming
# tempest 3rd party CI
#* #LINK: https://wiki.openstack.org/w/index.php?title=Manila/TrainCycle#Python3_Testing Wiki page on $subject
# Cross Project Goals
#* #LINK: http://lists.openstack.org/pipermail/openstack-discuss/2019-August/008570.html
#* #LINK: https://storyboard.openstack.org/#!/story/2005477
# Our Work - Reviews
#* #LINK: https://etherpad.openstack.org/p/manila-train-review-focus Review focus etherpad
# Bugs
# Open Discussion

'''Scheduled for 5 September 2019, 15:00 UTC'''
# Announcements
#* Goutham Pacha Ravi will be Manila PTL for Ussuri cycle!
#* Schedule
#** #LINK: https://releases.openstack.org/train/schedule.html Train Release Schedule
#** Train Milestone 3 and Feature Freeze next week, 12 September: "No featureful patch should be landed after this point."
#* Forum Submissions open till 20 September
#**https://etherpad.openstack.org/p/manila-shanghai-forum-brainstorming
# tempest 3rd party CI
#* #LINK: https://wiki.openstack.org/w/index.php?title=Manila/TrainCycle#Python3_Testing Wiki page on $subject
# Cross Project Goals
#* #LINK: http://lists.openstack.org/pipermail/openstack-discuss/2019-August/008570.html
# Our Work - Reviews
#* #LINK: https://etherpad.openstack.org/p/manila-train-review-focus Review focus etherpad
# Bugs
# Open Discussion

'''No meeting 29 August 2019, 15:00 UTC'''

'''Scheduled for 22 August 2019, 15:00 UTC'''
# Announcements
#* Schedule
#** #LINK: https://releases.openstack.org/train/schedule.html Train Release Schedule
#** Train Milestone 3 and Feature Freeze in three weeks, 12 September: "No featureful patch should be landed after this point."
# Python3 tempest 3rd party CI
#* #LINK: https://wiki.openstack.org/w/index.php?title=Manila/TrainCycle#Python3_Testing Wiki page on $subject
# Cross Project Goals
#* #LINK: http://lists.openstack.org/pipermail/openstack-discuss/2019-August/008570.html
# Our Work - Reviews
#* #LINK: https://etherpad.openstack.org/p/manila-train-review-focus Review focus etherpad
# Bugs
# Open Discussion

'''Scheduled for 15 August 2019, 15:00 UTC'''
# Announcements
#* Schedule
#** #LINK: https://releases.openstack.org/train/schedule.html Train Release Schedule
#** Manila Feature Proposal Freeze '''here''': " All new Manila features must be proposed and substantially completed, with unit tests by the end of the week."
#** Train Milestone 3 and Feature Freeze in four weeks, 12 September: "No featureful patch should be landed after this point."
#* Summit and PTG 4-8 November in Shanghai
#** #LINK: https://etherpad.openstack.org/p/manila-shanghai-ptg-planning PTG Planning Etherpad
# Python3 tempest 3rd party CI
#* #LINK: https://wiki.openstack.org/w/index.php?title=Manila/TrainCycle#Python3_Testing Wiki page on $subject
# Our Work - Reviews
#* #LINK: https://etherpad.openstack.org/p/manila-train-review-focus Review focus etherpad
# Bugs
# Open Discussion

'''Scheduled for 8 August 2019, 15:00 UTC'''
# Announcements
#* Schedule
#** #LINK: https://releases.openstack.org/train/schedule.html Train Release Schedule
#** Manila Feature Proposal Freeze '''next week''': "All new Manila features must be proposed and substantially completed, with unit tests and documentation by the end of the week."
#** Train Milestone 3 and Feature Freeze in five weeks, 12 September: "No featureful patch should be landed after this point."
#* Summit and PTG 4-8 November in Shanghai
#** #LINK: https://etherpad.openstack.org/p/manila-shanghai-ptg-planning PTG Planning Etherpad:
#** #LINK: https://www.openstack.org/summit/shanghai-2019/summit-schedule Summit Schedule
#*** #LINK: https://www.openstack.org/summit/shanghai-2019/summit-schedule/events/24239/adopt-a-share-today-how-to-bring-your-existing-shared-filesystem-under-manilas-management
#*** #LINK: https://www.openstack.org/summit/shanghai-2019/summit-schedule/events/24279/easy-multi-tenant-kubernetes-rwx-storage-with-cloud-provider-openstack-and-manila-csi
# Python3 tempest 3rd party CI
#* #LINK: http://lists.openstack.org/pipermail/openstack-discuss/2019-August/008255.html OpenStack Discuss list email on $subject
#* #LINK: https://wiki.openstack.org/w/index.php?title=Manila/TrainCycle&action=submit#Python3_Testing Wiki page on $subject
#* #LINK: https://bugs.launchpad.net/manila/+bug/1833160 py37 urllib/eventlet issue
# Our Work - Reviews
#* #LINK: https://review.opendev.org/#/c/657775/ Infortrend driver (Merged)
#* #LINK: https://review.opendev.org/#/c/664269/ NexentaStor5 NFS driver refactor
#* #LINK: https://review.opendev.org/#/c/647538/ remove keystoneclient dependency from manilaclient
#* #LINK: https://review.opendev.org/#/c/650986/ Fix pagination does not speed up queries bug
#* #LINK: https://review.opendev.org/#/q/topic:bp/share-network-multiple-subnets+(status:open+OR+status:merged)
# Bugs
# Open Discussion

'''Scheduled for 1 August 2019, 15:00 UTC'''
# Announcements
# Python3 tempest
#* first party jobs are python 3: https://review.opendev.org/#/c/671031/
#* third party jobs?
# Our Work - Reviews
#* #LINK: https://review.opendev.org/#/c/657775/ Infortrend driver
#* #LINK: https://review.opendev.org/#/c/664269/ NexentaStor5 NFS driver refactor
#* #LINK: https://review.opendev.org/#/c/647538/ remove keystoneclient dependency from manilaclient
#* #LINK: https://review.opendev.org/#/c/650986/ Fix pagination does not speed up queries bug
#* #LINK: https://review.opendev.org/#/q/topic:bp/share-network-multiple-subnets+(status:open+OR+status:merged)
# Bugs
# Open Discussion

'''Scheduled for 25 July 2019, 15:00 UTC'''
# Announcements
#* M2 is here!
# Python3 for Third Party CI
# Our Work - Reviews
#* #LINK: https://review.opendev.org/#/c/657775/ Infortrend driver
#* #LINK: https://review.opendev.org/#/c/664269/ NexentaStor5 NFS driver refactor
#* #LINK: https://review.opendev.org/#/c/671031/ Run tempest jobs under py3
#* #LINK: https://review.opendev.org/#/q/topic:CephFS-NFS-IPv6+(status:open+OR+status:merged)
#* #LINK: https://review.opendev.org/#/c/647538/ remove keystoneclient dependency from manilaclient
#* #LINK: https://review.opendev.org/#/c/650986/ Fix pagination does not speed up queries bug
#* #LINK: https://review.opendev.org/#/q/topic:bp/share-network-multiple-subnets+(status:open+OR+status:merged)
# Bugs
# OSC usage of set/unset logic
# Open Discussion

'''Scheduled for 18 July 2019, 15:00 UTC'''
# Announcements
# Our Work - Reviews
#* #LINK: https://review.opendev.org/#/c/657775/ Infortrend driver
#* #LINK: https://review.opendev.org/#/c/647538/ remove keystoneclient dependency from manilaclient
#* #LINK: https://review.opendev.org/#/c/667744/ fix `manila list --count True` command
#* #LINK: https://review.opendev.org/#/c/670510/ IPv6 support in CephFS/NFS back end
#* #LINK: https://review.opendev.org/#/c/671027/ Run IPv6 scenario tests with CephFS/NFS back end
#* #LINK: https://review.opendev.org/#/c/650986/ Fix pagination does not speed up queries bug
#* #LINK: https://review.opendev.org/#/q/topic:bp/share-network-multiple-subnets+(status:open+OR+status:merged)
# Bugs
# Open Discussion

'''Scheduled for 11 July 2019, 15:00 UTC'''
# Announcements
# Our Work - Specs
#* #LINK: https://review.opendev.org/#/c/644218 OSC support for Manila
#* #LINK: https://review.opendev.org/#/c/609537 Create share from snapshots in another pool or back end
# Cycle Goals
#* PDF doc creation
#* #LINK: https://governance.openstack.org/tc/goals/train/pdf-doc-generation.html
#* #LINK: http://lists.openstack.org/pipermail/openstack-discuss/2019-June/007301.html
# Bugs (vhariria)
# Open Discussion

'''No meeting 4 July 2019, 15:00 UTC -- US Holiday'''

'''Scheduled for 27 June 2019, 15:00 UTC'''
# Announcements
#* Shanghai summit CFP deadline
#** LINK: http://lists.openstack.org/pipermail/openstack-discuss/2019-June/007376.html
# PTG planning
#* LINK: http://lists.openstack.org/pipermail/openstack-discuss/2019-June/007079.html
# Our Work
#* New Driver reviews
#** LINK: https://review.opendev.org/#/c/636819/ INSPUR - ready to merge?
#** LINK: https://review.opendev.org/#/c/657775/ INFORTREND
#** LINK: https://review.opendev.org/#/c/664269/ NexentaStor5 NFS driver refactor
#* Specs
#** Add update share-type API to Share Types https://review.opendev.org/#/c/661209
#** Manila support in python-openstackclient https://review.opendev.org/#/c/644218
#** Create share from snapshots in another pool or back end https://review.opendev.org/#/c/609537
#* stable/stein gate failures
#** LINK: https://review.opendev.org/#/c/667721
# Open Discussion

'''Scheduled for 20 June 2019, 15:00 UTC'''
# Announcements
# Bugs (jgrosso)
# Kubecon report (tbarron - carried from last week)
# Open Discussion

'''Scheduled for 13 June 2019, 15:00 UTC'''
# Announcements
# Dealing with launchpad spam
#* https://answers.launchpad.net/launchpad/+question/681282 (tbarron)
# Allowing toggling visibility of share types (gouthamr)
#* #LINK: : https://review.opendev.org/#/c/661209/ (Spec: Add update share-type API to Share Types)
# Security Services testing in tempest (gouthamr)
#* #LINK https://bugs.launchpad.net/manila/+bug/1699856
# Bugs (jgrosso)
# Kubecon report (tbarron - carried from last week)
# Open Discussion

'''Scheduled for 6 June 2019, 15:00 UTC'''
# Announcements
#* Train 1 Milestone this week
# New Drivers ready for review
#* LINK https://review.opendev.org/#/c/657775 (Infortrend)
#* LINK https://review.opendev.org/#/c/636819 (Inspur)
# Specs ready for review?
#* LINK https://review.opendev.org/609537 (dviroel)
#* LINK https://review.opendev.org/#/c/644218/ (vkmc/enriquetaso)
#* LINK https://review.opendev.org/#/c/619925/ (lseki ?)
# Introducing Outreachy Intern and Mentors
# Bugs (jgrosso)
#* LINK https://etherpad.openstack.org/p/manila-bug-triage-pad
# Conference reports
#* LINK https://ceph.com/cephalocon/barcelona-2019/ (Cephalocon Barcelona)
#** LINK https://www.youtube.com/watch?v=xD7d21o6JLc&list=PLrBUGiINAakNCnQUosh63LpHbf84vegNu&index=57&t=871s (James Blair: Highly available Git on CephFS with Rook and Kubernetes on OpenStack)
#** LINK https://static.sched.com/hosted_files/cephalocon2019/86/Rook-Deployed%20NFS%20Clusters%20over%20CephFS.pdf (Donnelly and Layton plans for CephFS via NFS under rook on k8s)
#** LINK https://static.sched.com/hosted_files/cephalocon2019/ce/Cephalocon_%20RWX%20Storage%20for%20Containers%20with%20CephFS%20and%20Manila.pdf (my talk on Manila CSI, etc.)
#* LINK https://kccnceu19.sched.com/ (Kubecon Barcelona)
#** LINK https://static.sched.com/hosted_files/kccnceu19/55/SIG-OpenStack%20KubeCon%20Barcelona%202019.pdf (OpenStack SIG Intro/Deep Dive)
#** LINK https://kccnceu19.sched.com/speaker/saad_ali.1w8kd0qk (Saad Ali's talks)
#** LINK https://static.sched.com/hosted_files/kccnceu19/45/Rook%20Project%20Intro.pdf (Rook project intro)
#** LINK https://static.sched.com/hosted_files/kccnceu19/cf/slides.pdf (K8s Storage 101l by David Zhu and Jan Safranek)
#** LINK https://kccnceu19.sched.com/event/MPfh/improving-availability-for-stateful-applications-in-kubernetes-michelle-au-google (Michelle Au: Improving Availability for Stateful Apps)
#* LINK https://indico.cern.ch/event/776411/timetable/#20190527 (CERN OpenStack Day)
# Open Discussion

'''No meeting 30 May 2019'''

'''Scheduled for 23 May 2019, 15:00 UTC'''
# Announcements
# New Drivers
#* #LINK: https://review.opendev.org/#/c/657775/ (Infortrend)
#* #LINK: https://review.opendev.org/#/c/636819/ (Inspur)
# Bugs (jgrosso)
#* LINK https://etherpad.openstack.org/p/manila-bug-triage-pad
# Open Discussion

'''Scheduled for 6 May 2019, 15:00 UTC'''
# Announcements
#* Photos from PTG
#** #LINK https://www.dropbox.com/sh/fydqjehy9h5y728/AACql7AzbeYByedYevFvFUoia/Manila?dl=0&subfolder_nav_tracking=1
# PTG summary (thanks vkmc!)
#* #LINK http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006246.html
# Planning Our Work (thanks gouthamr!)
#* #LINK https://wiki.openstack.org/wiki/Manila/TrainCycle
# Specs
#* #LINK https://review.opendev.org/#/c/657894/
#* #LINK https://review.opendev.org/#/c/659161/
#* #LINK https://review.opendev.org/#/c/657900/
#* #LINK https://review.opendev.org/#/c/657893/
#* #LINK https://review.opendev.org/#/c/644218/
#* #LINK https://review.opendev.org/#/c/609537/
# Bugs (jgrosso)
#* LINK https://etherpad.openstack.org/p/manila-bug-triage-pad
# Open Discussion

'''Scheduled for 9 May 2019, 15:00 UTC'''
# Announcements
#* Parking lot for old unimplemented specs
#* #LINK https://review.opendev.org/#/c/657894/
# Summit (29 April 29-May 1) and PTG (May 2-4) summary, action items
#* #LINK https://etherpad.openstack.org/p/manila-ptg-train
# Train Schedule
#* #LINK https://review.opendev.org/#/c/655667/
#* #LINK https://wiki.openstack.org/wiki/Manila/TrainCycle
# Extend share when clients are connected (gouthamr)
#* #LINK https://review.opendev.org/#/c/531568/
#* #LINK http://logs.openstack.org/68/531568/26/check/manila-tempest-dsvm-scenario/1ea651d/logs/testr_results.html.gz
# Bugs (jgrosso)
#* LINK https://etherpad.openstack.org/p/manila-bug-triage-pad
# Open Discussion

'''No meeting 2 May 2019, 15:00 UTC -- PTG'''

'''Scheduled for 25 April 2019, 15:00 UTC'''
# Announcements
# Summit (29 April 29-May 1) and PTG (May 2-4) reminders
#* #LINK: https://www.openstack.org/summit/denver-2019/summit-schedule/global-search?t=Manila
#* #LINK https://www.openstack.org/ptg#tab_schedule
#* https://etherpad.openstack.org/p/manila-denver-train-ptg-planning
# Stein Retrospective
#* #LINK https://etherpad.openstack.org/p/manila-stein-retrospective
# Train Schedule
#* #LINK https://review.opendev.org/#/c/655667/
# Bugs (jgrosso)
#* LINK https://etherpad.openstack.org/p/manila-bug-triage-pad
# Open Discussion

'''Scheduled for 18 April 2019, 15:00 UTC'''
# Announcements
#* Summit April 29 - May 1
#* #LINK: https://www.openstack.org/summit/denver-2019/summit-schedule/global-search?t=Manila
#* PTG May 2 - May 4
#** Schedule https://www.openstack.org/ptg#tab_schedule
#** Manila planning etherpad https://etherpad.openstack.org/p/manila-denver-train-ptg-planning
# Stable/branch backports cadence (gouthamr)
# Bugs (jgrosso)
#* LINK https://etherpad.openstack.org/p/manila-bug-triage-pad
# Open Discussion

'''Scheduled for 11 April 2019, 15:00 UTC'''
# Announcements
#* Stein shipped yesterday!
# Stable/branch backports pending
#* #LINK: https://review.openstack.org/#/q/status:open+project:openstack/manila+branch:stable/queens
#* #LINK: https://review.openstack.org/#/q/status:open+project:openstack/manila-ui+branch:stable/queens
# Followup on: Third party CIs and devs: DevStack plugin changes - we will no longer support installing manila-tempest-plugin
#* #LINK: https://review.openstack.org/#/c/646037/ (manila devstack plugin changes)
#* #LINK: https://review.openstack.org/#/c/648716/ (manila-tempest-plugin changes)
# Bugs (jgrosso)
#* LINK https://etherpad.openstack.org/p/manila-bug-triage-pad
# Open Discussion

'''Scheduled for 4 April 2019, 15:00 UTC'''
# Announcements
# Attn: Third party CIs and devs: DevStack plugin changes - we will no longer support installing manila-tempest-plugin
#* #LINK: https://review.openstack.org/#/c/646037/ (manila devstack plugin changes)
#* #LINK: https://review.openstack.org/#/c/648716/ (manila-tempest-plugin changes)
# Bugs (jgrosso)
#* LINK https://etherpad.openstack.org/p/manila-bug-triage-pad
# Open Discussion

'''Scheduled for 28 March 2019, 15:00 UTC'''
# Announcements
#* RC2 week for Stein, findal RC Monday 1 April, Stein release 10 April
#** no bugs backported to stable stein, no need for another rc
# PTG
#* Schedule: https://www.openstack.org/ptg/#tab_schedule
#* email re: extra time, etc: http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003955.html
#* Planning Etherpad https://etherpad.openstack.org/p/manila-denver-train-ptg-planning
# Run All DSVM jobs under py3
#* https://review.openstack.org/#/c/646037/
#** adds a py2 dummy job to maintain py2 coverage through Train
# Bugs (grosso)
#* LINK https://etherpad.openstack.org/p/manila-bug-triage-pad
# Open Discussion

'''Scheduled for 21 March 2019, 15:00 UTC'''
# Announcements
#* RC1 today & proposed stable/rocy and stable/queens releases
#** stable/stein will be cut and master will be open to changes for train and for potential backports
#** also hard string freeze
#* Final RCs 1 April
#* Release 10 April
# PTG
#* Planning Etherpad https://etherpad.openstack.org/p/manila-denver-train-ptg-planning
# Last minute bug fixes for rc
# Bugs (grosso)
#* LINK https://etherpad.openstack.org/p/manila-bug-triage-pad
# Open Discussion

'''Scheduled for 14 March 2019, 15:00 UTC'''
# Announcements
#* We're in Feature Freeze, Soft String Freeze, Requirements Freeze
#* Hard string freeze and first release candidate March 21
#* Reldase week starts 1 April 2019
#**only critical bugs accepted
#* Stein release 8 April 2019
# PTG
#* Planning Etherpad https://etherpad.openstack.org/p/manila-denver-train-ptg-planning
# Bugs (grosso)
#* LINK https://etherpad.openstack.org/p/manila-bug-triage-pad
# Open Discussion

'''Scheduled for 7 March 2019, 15:00 UTC'''
# Announcements
#* python-manilaclient release review posted
#** https://review.openstack.org/#/c/641642/
#* We are in Feature Freeze
#** manage share servers work merged
#* Will submit forum topics later today
#** still time to add to the brainstorming etherpad:
#*** LINK https://etherpad.openstack.org/p/DEN-train-forum-manila-brainstorming
# Bugs (grosso)
#* LINK https://etherpad.openstack.org/p/manila-bug-triage-pad
# Open Discussion

''Scheduled for 28 February 2019, 15:00 UTC'''
# Announcements
#* TC election underway
#** http://lists.openstack.org/pipermail/openstack-discuss/2019-February/003227.html
#*** remember to vote by 5 March
#* Forum submissions are open through next week
#** http://lists.openstack.org/pipermail/openstack-discuss/2019-February/003073.html
#** soliciting brainstorming on our etherpad: http://lists.openstack.org/pipermail/openstack-discuss/2019-February/003059.html
#* Schedule reminders
#** LINK https://releases.openstack.org/stein/schedule.html
#** feature freeze and client library freeze 7 March -- one week from today
# Tracking our work
#* LINK https://wiki.openstack.org/wiki/Manila/SteinCycle
#** https://review.openstack.org/#/q/topic:bp/manage-unmanage-with-share-servers+(status:open+OR+status:merged) (ganso)
#** openstack sdk progress (amito)
#** uwsgi progress (vkmc)
# Bugs (grosso)
#* LINK http://lists.openstack.org/pipermail/openstack-discuss/2019-February/002404.html
#* LINK https://etherpad.openstack.org/p/manila-bug-triage-pad
# Open Discussion

'''Scheduled for 21 February 2019, 15:00 UTC'''
# Announcements
# Schedule reminders
#* LINK https://releases.openstack.org/stein/schedule.html
#* feature proposal freeze Today
#** All new Manila features must be proposed and substantially complete, with unit tests by 21 February 2019 (23:59 UTC).
#* feature freeze and client library freeze 7 March
# Tracking our work
#* LINK https://wiki.openstack.org/wiki/Manila/SteinCycle
#** https://review.openstack.org/#/q/topic:bp/manage-unmanage-with-share-servers+(status:open+OR+status:merged)
#** Outreachy interns and OSC work
# Bugs (gouthamr for jgrosso)
#* LINK http://lists.openstack.org/pipermail/openstack-discuss/2019-February/002404.html
#* LINK https://etherpad.openstack.org/p/manila-bug-triage-pad
# Open Discussion

'''Scheduled for 14 February 2019, 15:00 UTC'''
# Announcements
# Vision Reflection
#* LINK http://lists.openstack.org/pipermail/openstack-discuss/2019-February/002678.html
#* LINK https://review.openstack.org/#/c/636770/
# Schedule reminders
#* LINK https://releases.openstack.org/stein/schedule.html
#* feature proposal freeze 21 February
#* feature freeze and client library freeze 7 March
# Inspur Instorage driver
#* https://review.openstack.org/#/c/636819
#* new driver submission deadline was 10 January for Stein
# Tracking our work
#* LINK https://wiki.openstack.org/wiki/Manila/SteinCycle
#* https://review.openstack.org/#/q/topic:bp/manage-unmanage-with-share-servers+(status:open+OR+status:merged)
# Bugs (gouthamr for jgrosso)
#* LINK http://lists.openstack.org/pipermail/openstack-discuss/2019-February/002404.html
#* LINK https://etherpad.openstack.org/p/manila-bug-triage-pad
# Open Discussion

'''Scheduled for 7 February 2019, 15:00 UTC'''
# Announcements
# Schedule reminders
#* LINK https://releases.openstack.org/stein/schedule.html
#* feature proposal freeze 21 February
#* feature freeze and client library freeze 7 March
# Bugs (jgrosso)
#* LINK http://lists.openstack.org/pipermail/openstack-discuss/2019-February/002404.html
#* LINK https://etherpad.openstack.org/p/manila-bug-triage-pad
# Tracking our work
#* LINK https://wiki.openstack.org/wiki/Manila/SteinCycle
# Open Discussion

'''Scheduled for 31 January 2019, 15:00 UTC'''
# Announcements
# Share shrinking issue - can we let the backend/driver prevent data loss without detecting it? (gouthamr)
#* LINK: https://review.openstack.org/#/c/632615/13/manila/share/drivers/dell_emc/plugins/unity/client.py@309
# pylint again
#* LINK: https://review.openstack.org/#/c/633576/
# skip third-party jobs on WIP patches?
# Bugs (jgrosso)
#* https://etherpad.openstack.org/p/manila-bug-triage-pad

'''Scheduled for 24 January 2019, 15:00 UTC'''
# Announcements
# Scheduler speedup (carthaca)
#* https://review.openstack.org/#/c/619576/
# AZ work (gouthamr)
#* https://review.openstack.org/#/c/629958/
#* https://review.openstack.org/#/c/630886/
#* https://review.openstack.org/#/c/630039/
# Pylint issues (ganso)
#* [http://logs.openstack.org/58/629958/2/check/openstack-tox-pylint/d3056f6/job-output.txt.gz#_2019-01-23_19_20_57_403442 Example]
#* [https://review.openstack.org/632992 fixes one issue]
#* [https://github.com/PyCQA/pylint/issues/697 Trickier ] Ideas?
# Gate issues (tbarron)
#* https://review.openstack.org/#/c/631846/
# Bugs (jgrosso)
#* https://etherpad.openstack.org/p/manila-bug-triage-pad
# Open Discussion

''Scheduled for 17 January 2019, 15:00 UTC'''
# Announcements
# Python 3 jobs
#* manila-ui: https://review.openstack.org/#/c/629538/ merged
#* manila (dummy): https://review.openstack.org/#/c/629143/ merged
#* manila (lvm): https://review.openstack.org/#/c/623061/ still needs work
#* python-manilaclient: https://review.openstack.org/#/c/629536/ needs review
#* python-manilaclient: https://review.openstack.org/#/c/630462/ needs review
# Gate issues
# Bugs
#* https://etherpad.openstack.org/p/manila-bug-triage-pad
# Open Discussion

'''Scheduled for 10 January 2019, 15:00 UTC'''
# Announcements
#* Stein Milestone 2
# Python 3 jobs
#* manila (dummy): https://review.openstack.org/#/c/629143/
#* manila (lvm): https://review.openstack.org/#/c/623061/
#* python-manilaclient: https://review.openstack.org/#/c/629536/
#* manila-ui: https://review.openstack.org/#/c/629538/
# Gate issues
# Our Work
#* Testing py3 first in devstack by default: https://review.openstack.org/#/c/623061/
# Bugs
#* https://etherpad.openstack.org/p/manila-bug-triage-pad
# Open Discussion

'''Scheduled for 3 January 2019, 15:00 UTC'''
# Announcements
#* Stein Milestone 2 - week of Jan 7
# New User/Developer Experience
#* https://review.openstack.org/#/c/627020/ merged, thanks Goutham!
# Gate issues
# Our Work
#* Priority for access rules: https://review.openstack.org/#/c/572283/ updated for review
#* Testing py3 first in devstack by default: https://review.openstack.org/#/c/623061/
# Bugs
#* https://etherpad.openstack.org/p/manila-bug-triage-pad
# Open Discussion

'''No meeting 27 December 2018'''

'''Scheduled for 20 December 2018, 15:00 UTC'''
# Announcements
#* Stein Milestone 2 - week of Jan 7
# Skip meeting 27 December?
# Kubecon report (xyang, bswartz, gouthamr)
# Gate issues
# Our Work
#* Priority for access rules: https://review.openstack.org/#/c/572283/ updated for review
#* Testing py3 first in devstack by default: https://review.openstack.org/#/c/623061/
# Bugs
#* https://etherpad.openstack.org/p/manila-bug-triage-pad
# Open Discussion

'''No meeting 13 December 2018'''

'''Scheduled for 6 December 2018, 15:00 UTC'''
# Announcements
#* Stein Milestone 2 - week of Jan 7
#** Driver submission deadline
# Need new Bug Czar (gouthamr)
# Our Work
#* Priority for access rules: https://review.openstack.org/#/c/572283/ updated for review
#* Testing py3 first in devstack by default: https://review.openstack.org/#/c/623061/
# Bugs
#* https://etherpad.openstack.org/p/manila-bug-triage-pad
# Open Discussion

'''Scheduled for 29 November 2018, 15:00 UTC'''
# Announcements
# Berlin Summit Summary
# Spec Reviews
#*'''Manage/Unmanage Share Servers''' https://review.openstack.org/#/c/607342
#*'''Share Networks Span Subnets'''
#** https://review.openstack.org/#/c/391805/
#** https://review.openstack.org/#/c/615947/
#*'''Create share from snapshots in another pool or back end''' https://review.openstack.org/#/c/609537/
#*'''Storage Availability Zone Improvements''' https://review.openstack.org/#/c/616123/
#*'''Share and Back End Capabilities Improvements''' https://review.openstack.org/#/c/616383/
# Open Discussion

'''No meeting 22 November 2018""

'''Scheduled for 15 November 2018, 15:00 UTC'''
# Announcements
#* No meeting next week?
#* Announcement on Bug Tsar Role (dustins)
# Spec Reviews
#*'''Manage/Unmanage Share Servers''' https://review.openstack.org/#/c/607342
#*'''Share Networks Span Subnets'''
#** https://review.openstack.org/#/c/391805/
#** https://review.openstack.org/#/c/615947/
#*'''Create share from snapshots in another pool or back end''' https://review.openstack.org/#/c/609537/
#*'''Storage Availability Zone Improvements''' https://review.openstack.org/#/c/616123/
#*'''Share and Back End Capabilities Improvements''' https://review.openstack.org/#/c/616383/
# Open Discussion

'''Scheduled for 8 November 2018, 15:00 UTC'''
# Announcements
#*'''Manila at the Summit''' https://www.openstack.org/summit/berlin-2018/summit-schedule/global-search?t=manila
#** Also: '''Practical CephFS with NFS today using OpenStack Manila''' on Ceph Day (Monday): https://ceph.com/cephdays/ceph-day-berlin/
#* Do we meet next week?
# Spec Reviews
#*'''Manage/Unmanage Share Servers''' https://review.openstack.org/#/c/607342
#*'''Share Networks Span Subnets'''
#** https://review.openstack.org/#/c/391805/
#** https://review.openstack.org/#/c/615947/1
#*'''Create share from snapshots in another pool or back end''' https://review.openstack.org/#/c/609537/
#*'''Storage Availability Zone Improvements''' https://review.openstack.org/#/c/616123/
#*'''Share and Back End Capabilities Improvements''' https://review.openstack.org/#/c/616383/
# Open Discussion

'''Scheduled for 1 November 2018, 15:00 UTC'''
# Announcements
# Technical Vision (zaneb)
#* '''Mail from Zane''' http://lists.openstack.org/pipermail/openstack-dev/2018-October/136033.html
#* '''Review''' https://review.openstack.org/#/c/592205/
# Spec Reviews
# Planning Our Work
#*'''Work Plan Page''' https://wiki.openstack.org/wiki/Manila/SteinCycle
# Let's talk about bugs!
#*'''Bug Triage Page''' https://wiki.openstack.org/wiki/Manila/SteinCycle#Bug_Triage
# Open Discussion

'''No meeting 25 October 2018, 15:00 UTC'''

'''Scheduled for 18 October 2018, 15:00 UTC'''
# Announcements
# Code Review Guideline up for review (gouthamr)
#* #LINK: https://review.openstack.org/#/c/609598/
# Access rule priorization case when there are conflicting rules with the same priority
#* #LINK: https://review.openstack.org/#/c/572283/22/manila/share/access.py@381
# Planning Our Work
#*'''Work Plan Page''' https://wiki.openstack.org/wiki/Manila/SteinCycle
# Let's talk about bugs!
#*'''Bug Triage Page''' https://wiki.openstack.org/wiki/Manila/SteinCycle#Bug_Triage
# Open Discussion

'''Scheduled for 11 October 2018, 15:00 UTC'''
# Announcements
# Planning Our Work
#*'''Work Plan Page''' https://wiki.openstack.org/wiki/Manila/SteinCycle
# Let's talk about bugs!
#*'''Bug Triage Page''' https://wiki.openstack.org/wiki/Manila/SteinCycle#Bug_Triage
# Open Discussion

'''Scheduled for 4 October 2018, 15:00 UTC'''
# Announcements
# Formalizing and changing Review guidelines (gouthamr)
#* #LINK: https://etherpad.openstack.org/p/manila-review-guidelines
# Planning Our Work
#*'''Work Plan Page''' https://wiki.openstack.org/wiki/Manila/SteinCycle
# Let's talk about bugs!
#*'''Bug Triage Page''' https://wiki.openstack.org/wiki/Manila/SteinCycle#Bug_Triage
# Open Discussion

'''Scheduled for 27 September 2018, 15:00 UTC'''
# Announcements
#* '''Forum Submissions:''' https://www.openstack.org/summit/berlin-2018/vote-for-speakers
#**No actual vote, decision by 9 October.
#* '''T-series goal likely to require OSC integration''' http://lists.openstack.org/pipermail/openstack-dev/2018-September/135107.html
# MidCycle? Bug swat days?
#* '''Stein cycle schedule''' https://releases.openstack.org/stein/schedule.html
# Planning Our Work
#*'''Work Plan Page''' https://wiki.openstack.org/wiki/Manila/SteinCycle
# Let's talk about bugs!
#*'''Bug Triage Page''' https://wiki.openstack.org/wiki/Manila/SteinCycle#Bug_Triage
# Open Discussion

'''Scheduled for 20 September 2018, 15:00 UTC'''
# Announcements
#* '''Stein cycle schedule''' https://releases.openstack.org/stein/schedule.html
#* '''Forum topic submission deadline 26 September''' http://lists.openstack.org/pipermail/openstack-dev/2018-September/134740.html
#** Our topic brainstorming: https://etherpad.openstack.org/p/manila-berlin-forum-brainstorm
# '''PTG summary and look ahead''' https://etherpad.openstack.org/p/manila-ptg-stein-summation
# Mid-cycle and regional Bug Scrubs?
# Open Discussion

'''No meeting 13 September 2018, 15:00 UTC due to PTG'''

'''Scheduled for 6 September 2018, 15:00 UTC'''
# Announcements
#* PTG next week, no weekly meeting Thursday 13 September
#* '''Reminder: PTG planning etherpad:''' https://etherpad.openstack.org/p/manila-ptg-planning-denver-2018
#* Dinner with Cinder team Tuesday night at 7:30
#* Rocky Retrospective etherpad: https://etherpad.openstack.org/p/manila-rocky-retrospective
#* Berlin Forum brainstorm etherpad: https://etherpad.openstack.org/p/manila-berlin-forum-brainstorm
# Open Discussion

'''No meeting 30 August 2018, 15:00 UTC'''

'''Scheduled for 23 August 2018, 15:00 UTC'''
# Announcements
#* Manila tempest plugin was released last Friday, 17 August 2018
#* No extra rc candidates
#* Final Rocky release 29 August 2018
#* '''Reminder: PTG planning etherpad:''' https://etherpad.openstack.org/p/manila-ptg-planning-denver-2018
#* Doodle poll for combined dinner with Cinder team: https://doodle.com/poll/8rm3ahdyhmrtx5gp
# Bugs (dustins)
#* https://etherpad.openstack.org/p/manila-bug-triage-pad
# Open Discussion

'''Scheduled for 16 August 2018, 15:00 UTC'''
# Announcements
#* '''Final RCs and intermediary releases next week''' https://releases.openstack.org/rocky/schedule.html#r-finalrc
#* '''Reminder: PTG planning etherpad:''' https://etherpad.openstack.org/p/manila-ptg-planning-denver-2018
# rc & manila-tempest-plugin releases
#* any blockers for rc? any must-haves for manila-tempest plugin?
# Bugs (dustins)
#* https://etherpad.openstack.org/p/manila-bug-triage-pad
# Open Discussion

'''Scheduled for 9 August 2018, 15:00 UTC'''
# Announcements
#* '''RC1" reviews posted for rc1 and to release & branch manila and manila-ui
#* '''Hard string freeze''' https://releases.openstack.org/rocky/schedule.html#r-hard-sf
#* '''Final RCs and intermediary releases''' https://releases.openstack.org/rocky/schedule.html#r-finalrc
#* '''Reminder: PTG planning etherpad:''' https://etherpad.openstack.org/p/manila-ptg-planning-denver-2018
# API wsgi service and python 3: eventlet. mod_wsgi, uwsgi
# Bugs (dustins)
#* https://etherpad.openstack.org/p/manila-bug-triage-pad
# Open Discussion

'''Scheduled for 2 August 2018, 15:00 UTC'''
# Announcements
#* Manila PTL for Stein cycle
#* '''Up next:''' RC1 target week - Aug 6-10 https://releases.openstack.org/rocky/schedule.html
#* '''Reminder: PTG planning etherpad:''' https://etherpad.openstack.org/p/manila-ptg-planning-denver-2018
#Python3 Stein Goal and Third Party Jobs
#*http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-08-01.log.html#t2018-08-01T19:38:26
# Review Focus
#* https://etherpad.openstack.org/p/manila-rocky-review-focus
# Bugs (dustins)
#* https://etherpad.openstack.org/p/manila-bug-triage-pad
# Open Discussion

'''Scheduled for 26 July 2018, 15:00 UTC'''
# Announcements
#* '''Upon Us:''' Milestone 3 - Today! https://releases.openstack.org/rocky/schedule.html
#* '''Up next:''' RC1 target week - Aug 6-10
#* '''Reminder: PTG planning etherpad:''' https://etherpad.openstack.org/p/manila-ptg-planning-denver-2018
# Rocky Goal Completion
#* https://governance.openstack.org/tc/goals/rocky/index.html
# Review Focus
#* https://etherpad.openstack.org/p/manila-rocky-review-focus
# Bugs (dustins)
#* https://etherpad.openstack.org/p/manila-bug-triage-pad
# Open Discussion

'''Scheduled for 19 July 2018, 15:00 UTC'''
# Announcements
#* '''Reminder: PTG planning etherpad:''' https://etherpad.openstack.org/p/manila-ptg-planning-denver-2018
# Review Focus
#* '''Upon Us:''' Milestone 3 - 26 July 2018
#* https://etherpad.openstack.org/p/manila-rocky-review-focus
# Bugs (dustins)
#* https://etherpad.openstack.org/p/manila-bug-triage-pad
# Open Discussion

'''Scheduled for 12 July 2018, 15:00 UTC'''
# Announcements
#* '''PTG planning etherpad:''' https://etherpad.openstack.org/p/manila-ptg-planning-denver-2018
# Review Focus
#* '''Upon us:''' Manila Feature Proposal Freeze - 9-13th July 2018
#* '''Up next:''' Milestone 3 - 26 July 2018
#* https://etherpad.openstack.org/p/manila-rocky-review-focus
# Special Casing of API Schema Validation (gouthamr)
#* https://review.openstack.org/#/c/473464/11/manila/api/v2/quota_sets.py@94
#* https://review.openstack.org/#/c/572283/3/manila/api/common.py@406
#* http://eavesdrop.openstack.org/meetings/manila/2017/manila.2017-07-13-15.00.log.txt
# Bugs (dustins)
#* https://etherpad.openstack.org/p/manila-bug-triage-pad
# Open Discussion

'''No meeting 5 July 2018'''

'''Scheduled for 28 June 2018, 15:00 UTC'''
#Announcements
#*PTG: http://lists.openstack.org/pipermail/openstack-dev/2018-June/131881.html
#stable/branch gates
#*https://review.openstack.org/#/c/576227/
#*https://review.openstack.org/#/c/578558/
#Review Focus
#* Milestone 3 - 26 July 2018
#*https://etherpad.openstack.org/p/manila-rocky-review-focus
#Bugs (dustins)
#* https://etherpad.openstack.org/p/manila-bug-triage-pad
# Open Discussion

''Scheduled for 21 June 2018, 15:00 UTC'''
#Announcements
#* Milestone 3 - 26 July 2018
#Beijing Bug Smash
#*https://etherpad.openstack.org/p/OpenSource-Hackathon-Rocky-Beijing-Bugs-List
# Meeting time (bswartz)
# Open Discussion

'''Scheduled for 14 June 2018, 15:00 UTC'''
#Announcements
#Feature Spec Work
#*https://review.openstack.org/#/c/572283/
#*https://review.openstack.org/#/c/563429/
#*https://review.openstack.org/#/c/570708
#China Bug Smash
#*https://etherpad.openstack.org/p/OpenSource-Hackathon-8-beijing
#*https://etherpad.openstack.org/p/OpenSource-Hackathon-Rocky-Beijing-Bugs-List
# Change Review Guide
#* https://review.openstack.org/#/c/574888
# Storyboard again
# Bugs
#* https://etherpad.openstack.org/p/manila-bug-triage-pad
# Open Discussion

'''Scheduled for 7 June 2018, 15:00 UTC'''
#Announcements
#*Rocky-2 milestone https://releases.openstack.org/rocky/schedule.html
#*New driver submission deadline
#New Drivers
#*https://etherpad.openstack.org/p/manila-rocky-drivers
#Feature Spec Work
#*https://review.openstack.org/#/c/572283/
#*https://review.openstack.org/#/c/563429/
#*https://review.openstack.org/#/c/570708
#Summit Roundup
#*https://www.openstack.org/summit/vancouver-2018/summit-schedule/global-search?t=manila
# Bugs (dustins)
#* https://etherpad.openstack.org/p/manila-bug-triage-pad
# Open Discussion

'''No meeting 24 May 2018 or 28 May 2018 due to Vancouver Summit'''

'''Scheduled for 17 May 2018, 15:00 UTC'''
# Python3 Status (vkmc, gouthamr)
#* https://bugs.launchpad.net/manila/+bug/1482633
#* http://lists.openstack.org/pipermail/openstack-dev/2018-May/130463.html
#* Feasibility of using WSGI and stop using the built-in server? This not only affect us with Py3 support but also for manila users wanting to use TLS.
# Missing share servers in ensure_shares driver method (ganso)
# Bugs (dustins)
#* https://etherpad.openstack.org/p/manila-bug-triage-pad
# Open Discussion

'''Scheduled for 10 May 2018, 15:00 UTC'''
# New Drivers
#* https://etherpad.openstack.org/p/manila-rocky-drivers
# Python3 Status
#* https://review.openstack.org/#/c/552121/
# Bugs (dustins)
#* https://etherpad.openstack.org/p/manila-bug-triage-pad
# Open Discussion

'''Scheduled for 3 May 2018, 15:00 UTC'''
# New Drivers
#* https://etherpad.openstack.org/p/manila-rocky-drivers
# Bugs (dustins)
#* https://etherpad.openstack.org/p/manila-bug-triage-pad
# Open Discussion

'''Scheduled for 26 April 2018, 15:00 UTC'''
# Specs
#* https://review.openstack.org/#/c/546301
#* https://review.openstack.org/#/c/552935
# Bugs (dustins)
#* https://etherpad.openstack.org/p/manila-bug-triage-pad
# Open Discussion

'''Scheduled for 19 April 2018, 15:00 UTC'''
# Spec Freeze and extensions
#* https://etherpad.openstack.org/p/manila-rocky-specs
# Bugs (dustins)
#* https://etherpad.openstack.org/p/manila-bug-triage-pad
# Open Discussion

'''Scheduled for 12 April 2018, 15:00 UTC'''
# Spec Reviews
#* https://etherpad.openstack.org/p/manila-rocky-specs
# New Drivers
#* https://etherpad.openstack.org/p/manila-rocky-drivers
# priority for access rule spec review
#* Do we require a limitation for value of the access rule priority (1~100).
#* Is priority also needed for 'deny' rules? (what do we do when the address range of a 'deny' rule overlaps the address range of an 'allow' rule) (amito)
# Bugs (dustins)
#* https://etherpad.openstack.org/p/manila-bug-triage-pad
# Open Discussion

'''Scheduled for 5 April 2018, 15:00 UTC'''
# Stable policy changes
#* https://review.openstack.org/#/c/548916
#* https://review.openstack.org/#/c/552733/
# Failing jobs in gate
#* https://review.openstack.org/#/c/557062/
# Spec Reviews
#* https://etherpad.openstack.org/p/manila-rocky-specs
# Open Discussion

'''Scheduled for 29 Mar 2018, 15:00 UTC'''
# Spec Reviews again
#* https://etherpad.openstack.org/p/manila-rocky-specs
# Failing jobs in gate
# Let's Go Over New Bugs (dustins)
#* https://etherpad.org/p/manila-bug-triage-pad

''Scheduled for 22 Mar 2018, 15:00 UTC'''
# Summit
#* Forum: https://etherpad.openstack.org/p/YVR-manila-brainstorming
#* Project Update and Onboarding sessions
# Spec Reviews
#* https://etherpad.openstack.org/p/manila-rocky-specs
#* Spec review day like nova? http://lists.openstack.org/pipermail/openstack-dev/2018-March/128575.html
# Fostering contribution to upstream manila
# Let's Go Over New Bugs (dustins)
#* https://etherpad.openstack.org/p/manila-bug-triage-pad
# Open Discussion

'''Scheduled for 15 Mar 2018, 15:00 UTC'''
# StoryBoard Progress Report (diablorojo)
# How to update the content that's in the tempest scenario tests spec? (vkmc)
#* https://github.com/openstack/manila-specs/blob/master/specs/ocata/scenario-tests.rst
#* Make spec not tied to particular release?
#* Use a different doc type?
# Let's Go Over New Bugs (dustins)
#* https://etherpad.openstack.org/p/manila-bug-triage-pad
# Open Discussion

'''Scheduled for 15 Feb 2018, 15:00 UTC'''
# PTG Planning

'''Scheduled for 8 Feb 2018, 15:00 UTC'''
# Rocky PTL
# RC1
#* https://launchpad.net/manila/+milestone/queens-rc1

'''Scheduled for 1 Feb 2018, 15:00 UTC'''
# Rocky PTL
#* http://lists.openstack.org/pipermail/openstack-dev/2018-January/126767.html

'''Scheduled for 25 Jan 2018, 15:00 UTC'''
# Feature Freeze / Queens milestone-3 (bswartz)

'''Scheduled for 11 Jan 2018, 15:00 UTC'''
# Let's go over new bugs (dustins)
#* https://etherpad.openstack.org/p/manila-bug-triage-pad
# Open Discussion

'''Scheduled for 4 Jan 2018, 15:00 UTC'''
# Generic driver attach problems (bswartz)

'''Scheduled for 7 Dec 2017, 15:00 UTC'''
# How should we fix "shares cannot be found by name in admin context" (zhongjun)
#* https://bugs.launchpad.net/manila/+bug/1721787
#* https://review.openstack.org/#/c/522607/
#* https://review.openstack.org/#/c/522452/
# Outstanding driver work? (tbarron)
#* infinidat https://review.openstack.org/#/c/515432/
#* cephfs-nfs HA https://review.openstack.org/#/c/510547/
# Tag M2? (tbarron)

'''Scheduled for 30 Nov 2017, 15:00 UTC'''
# Report from Wuhan Bug Smash
## https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Queens-Wuhan-Bugs-List
# Use v3 cinder client instead of v2 cinder client (zhongjun)
## https://review.openstack.org/#/c/522478/

'''Scheduled for 16 Nov 2017, 15:00 UTC'''
# The Manila community was not very active. (junboli)
## - patches cost long time to review and merge.
## - less response for questions in IRC channel.
## - more core members are required.
# Bug smash in China (zhongjun)
# IPv6 driver capabilities required variables (ganso)
# 3rd Party CIs may have to change to use Manila Tempest Plugin repo (raissa)
## https://review.openstack.org/#/c/512300/

'''Scheduled for 26 Oct 2017, 15:00 UTC'''
# Manila test image (bswartz)
## https://review.openstack.org/#/q/status:open+project:openstack/manila-test-image

'''Scheduled for 19 Oct 2017, 15:00 UTC'''
# Spec freeze / milestone 1 (bswartz)
# py2 -> py3 (vkmc)
## https://bugs.launchpad.net/manila/+bug/1482633 && https://review.openstack.org/#/c/289382/
# Let's go over new bugs (dustins)
## https://etherpad.openstack.org/p/manila-bug-triage-pad
# Zuul V3 migration status (raissa)
## https://review.openstack.org/#/c/512559/ https://review.openstack.org/#/c/513075/ https://review.openstack.org/#/c/513076/
## https://docs.openstack.org/infra/manual/zuulv3.html#legacy-job-migration-details

'''Scheduled for 12 Oct 2017, 15:00 UTC'''
# Manila Driver Maintainers and the DriverLog (dustins)
# Important Manila Bugs (dustins)

'''Scheduled for 5 Oct, 2017, 15:00 UTC'''
# Gate issues
# drivers_private_storage hard-delete vs soft-delete (ganso)
# Bug Czar (dustins)
# Open discussion

'''Scheduled for 28 Sep, 2017, 15:00 UTC'''
# Discuss and elicit Feedback for PTG
# Bug Tsar/Czar (dustins)
# Open discussion

'''Scheduled for 14 Sep, 2017, 15:00 UTC'''
# Add total count information in our list APIs (zhongjun)
# Register and Document Policy in Code (zhongjun)
# Dynamic Log Level (zhongjun)
# Install guide tesing (bswartz)
# Automatic generation of docs for configuration options (bswartz)
# Timeouts (bswartz)

'''Scheduled for 7 Sep, 2017, 15:00 UTC'''
# Specs and deadlines
# Open Discussion

'''Scheduled for 31 Aug, 2017, 15:00 UTC'''
# Docs for share groups (bswartz)
#* API Ref
#* Admin guide
#* More?
# Move manila_tempest_tests to a new repo (raissa)
# Open Discussion

'''Scheduled for 17 Aug, 2017, 15:00 UTC'''
# PTG
#* https://etherpad.openstack.org/p/manila-ptg-queens

'''Scheduled for 10 Aug, 2017, 15:00 UTC'''
# Bugs / RC1 Status
#* https://launchpad.net/manila/+milestone/pike-rc1
#* Quotas
#** https://bugs.launchpad.net/manila/+bug/1707379
#** https://bugs.launchpad.net/manila/+bug/1707378
#* https://bugs.launchpad.net/manila/+bug/1659023

'''Scheduled for 27 Jul, 2017, 15:00 UTC'''
# Feature Freeze
#* https://launchpad.net/manila/+milestone/pike-3
# Bug Squash Day
#* https://etherpad.openstack.org/p/pike-manila-bug-squash
# Python 3 in Queens

'''Scheduled for 20 Jul, 2017, 15:00 UTC'''
# FPF Exception request - ONTAP QoS (gouthamr)
#* http://lists.openstack.org/pipermail/openstack-dev/2017-July/119858.html
#* https://review.openstack.org/#/c/484933/
# IPv6 access revisited (bswartz)
# Milestone 3
# Open Discussion

'''Scheduled for 13 Jul, 2017, 15:00 UTC'''
# Feature Freeze
# Driverfixes
# Docs migration
# Bug Squash Day
# Per share type quotas

'''Scheduled for 29 Jun, 2017, 15:00 UTC'''
# Revisit priorities for Pike
# Bug squash?
# Open Discussion

'''Scheduled for 22 Jun, 2017, 15:00 UTC'''
# IPv6 Status
# Driver fixes to branches beyond stable/R-1 (gouthamr)

'''Scheduled for 15 Jun, 2017, 15:00 UTC'''
# How should support both IPv6 and IPv4 with DHSS=true
# IDs and instance IDs in the driver interface
#* https://bugs.launchpad.net/manila/+bug/1697581
#* https://review.openstack.org/#/c/433854/12/manila/db/sqlalchemy/models.py
#* https://review.openstack.org/#/c/473864/

'''Scheduled for 8 Jun, 2017, 15:00 UTC'''
# Milestone 2
# IPv6 Testing
# Open Discussion

Scheduled for 1 Jun, 2017, 15:00 UTC

Share groups + UI
Open Discussion

'''Scheduled for 18 May, 2017, 15:00 UTC'''
# PTG involvement
#* http://lists.openstack.org/pipermail/openstack-dev/2017-May/116921.html

'''Scheduled for 4 May, 2017, 15:00 UTC'''
# Share usage monitoring (zhongjun)
#* https://review.openstack.org/#/c/459150/
# Summit/PTG
# Open Discussion

'''Scheduled for 27 Apr, 2017, 15:00 UTC'''

# Notification about vponomaryov's stepping out of project
#* Valeriy Ponomaryov, known as "vponomaryov" in IRC, will be involved in Manila project till the middle of June. Then he will have other responsibilities.
# Share usage monitoring (zhongjun)
#* https://review.openstack.org/#/c/459150/

'''Scheduled for 20 Apr, 2017, 15:00 UTC'''

# Ensure shares (zhongjun)
#* https://review.openstack.org/#/c/446494/
# Update shares (zhongjun)
#* https://review.openstack.org/#/c/453553/
# Infinite shares (zhongjun)
#* https://review.openstack.org/#/c/452097/
#* What "infinite" shares ought to be?
#* How should we collect actual share usage?
# API filtering (zhongjun)
#* https://review.openstack.org/#/c/447775/

'''Scheduled for 13 Apr, 2017, 15:00 UTC'''
# Spec Freeze
# Open Discussion

'''Scheduled for 6 Apr, 2017, 15:00 UTC'''
# Concurrency bugs with LVM driver? [http://lists.openstack.org/pipermail/openstack-dev/2017-April/114945.html email ] (tbarron)
# Pike Specs
#* https://etherpad.openstack.org/p/manila-pike-spec-review-focus

'''Scheduled for 30 Mar, 2017, 15:00 UTC'''
# ensure share(zhongjun_)
#*https://review.openstack.org/#/c/446494

'''Scheduled for 23 Mar, 2017, 15:00 UTC'''
# SSL certificate verification
# Specs
#* https://review.openstack.org/#/q/status:open+project:openstack/manila-specs
# Open Discussion

'''Scheduled for 9 Mar, 2017, 15:00 UTC'''
# Specs Deadline (continued) (bswartz)
# Community Goals (bswartz)
#* https://github.com/openstack/governance/blob/master/goals/pike/deploy-api-in-wsgi.rst
#* https://github.com/openstack/governance/blob/master/goals/pike/python35.rst
# Experimental APIs (bswartz)
# Refactor of Tempest scenario base classes (bswartz)
#* http://lists.openstack.org/pipermail/openstack-dev/2017-March/113071.html

'''Scheduled for 2 Mar, 2017, 15:00 UTC'''
# Experimental Features (bswartz)
# Specs Deadline (bswartz)
# Open Discussion

'''Scheduled for 16 Feb, 2017, 15:00 UTC'''
# i18n liason needed
#* https://wiki.openstack.org/wiki/CrossProjectLiaisons#I18n
# PTG
#* https://etherpad.openstack.org/p/manila-pike-ptg-topics

'''Scheduled for 2 Feb, 2017, 15:00 UTC'''
# Microversions (rhagarty)
#* Do we follow Cinder's lead and provide an easy way for other projects to know our current supported microversion? (see https://review.openstack.org/#/c/420119). This would provide the mechanism for the Manila UI to determine if features should/should not be made available to the user.
# Share groups bugs
#* https://bugs.launchpad.net/manila/+bug/1660321
#* https://bugs.launchpad.net/manila/+bug/1660319
#* https://bugs.launchpad.net/manila/+bug/1659023
#* https://bugs.launchpad.net/manila/+bug/1661266
#* https://bugs.launchpad.net/manila/+bug/1661268
# LVM revert to snapshot

'''Scheduled for 26 Jan, 2017, 15:00 UTC'''
# Feature Freeze
#* IPv6
# Open Discussion

'''Scheduled for 19 Jan, 2017, 15:00 UTC'''
# Specs implementation status (bswartz)
#* https://etherpad.openstack.org/p/manila-ocata-code-review-focus
# Filterscheduler warning in logs (ravichandran)
#* "WARNING manila.scheduler.manager [-] Scheduler driver path manila.scheduler.filter_scheduler.FilterScheduler is deprecated, update your configuration to the new path manila.scheduler.drivers.filter.FilterScheduler "
# How to see the recently committed changes to (master branch ) /config-reference/shared-file-systems/drivers/hpe-3par-share-driver.html in docs.openstack.org.(ravichandran)
# How to update the tables inside manuals.Is it auto updated from the code. (ravichandran)
#* Is there any way to call some scripts or manila cli commands with in setupClass of tempest tests to address the prerequisite steps of backedn
# Open Discussion

'''Scheduled for 22 Dec, 2016, 15:00 UTC'''
# Specs implementation status (bswartz)
# briefly clarify the "24 hour rule" (tbarron)
# Manila CI Tempest Test Cases are Failing (ravichandran)

'''Scheduled for 8 Dec, 2016, 15:00 UTC'''
# PTG (bswartz)
# Default share type (tbarron)
# migration-start new command syntax (ganso)
# remove access-update fallback to access_allow/deny? (tbarron)
# decision of deadline for driver config docs in devref removal (ganso)
# Specs implementation status (bswartz)

'''Scheduled for 1 Dec, 2016, 15:00 UTC'''
# Discussion about driver docs in devref (ganso)
# Specs implementation status (bswartz)

'''Scheduled for 17 Nov, 2016, 15:00 UTC'''
# Spec review & prioritization (bswartz)
#* https://etherpad.openstack.org/p/manila-ocata-spec-review-focus
#* https://review.openstack.org/#/q/status:open+project:openstack/manila-specs

'''Scheduled for 10 Nov, 2016, 15:00 UTC'''
# Decide defaults for migration options (ganso)
#* https://review.openstack.org/#/c/392291

'''Scheduled for 3 Nov, 2016, 15:00 UTC'''
# Spec review & prioritization
#* https://review.openstack.org/#/q/project:%22%255Eopenstack/manila-specs%22++status:open
#* https://etherpad.openstack.org/p/manila-ocata-spec-review-focus
#* List of open specs
#** manila-ipv6
#** add-db-manage-purge
#** create-share-from-snapshot-extra-spec
#** support-quota-usage-in-detail
#** ocata-migration-improvements
#** data-service-jobs-table
#** add-share-type-filter-to-get-pools
#** manila-share-revert-to-snapshot
#** scenario-tests
#** mountable_snapshots
#** share-network-multiple-subnets
#** share-retype
#** multiple_protocol_share
#** access-groups
#** backup_share
#** manila-share-groups
#** data-service-api
#* vponomaryov's prioritiesː https://docs.google.com/document/d/1zdMNuQTIqrtDtzbdcxyZVn8SoPN9pbtv_HSLVR3Eld0/edit

'''Scheduled for 20 Oct, 2016, 15:00 UTC'''
# Specs and Deadlines (bswartz)
#* https://review.openstack.org/#/c/374883/
# Adding invalid user to the access rule changes valid access rule state from 'active' to 'error' (ravichandran)
# Open Discussion

'''Scheduled for 13 Oct, 2016, 15:00 UTC'''
# Ocata Design Summit
#* https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Manila%3A
# PTG

'''Scheduled for 6 Oct, 2016, 15:00 UTC'''
# Microversion-ing addition or removal of transitional ('micro') states (gouthamr)
#* https://review.openstack.org/#/c/369668/

'''Scheduled for 29 Sep, 2016, 15:00 UTC'''
# Ocata Design Summit
#* https://etherpad.openstack.org/p/manila-ocata-design-summit-topics
# Open Discussion

'''Scheduled for 22 Sep, 2016, 15:00 UTC'''
# Specs process
#* https://review.openstack.org/#/c/374883

'''Scheduled for 8 Sep, 2016, 15:00 UTC'''
# RC1 status
#* https://launchpad.net/manila/+milestone/newton-rc1
# Project Logo
#* http://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_6f0d111cec78c5ef&akey=d34a751f2d084d79
# Container Driver Security (aovchinnikov)
#* https://review.openstack.org/#/c/353463/
# Security "vulnerability-managed" tag for manila (tbarron)
# Zanata translations for manila-client and manila-ui (tbarron)
# Tempest direction (tbarron)

'''Scheduled for 1 Sep, 2016, 15:00 UTC'''
# Mascot (bswartz)
# Vulnerability Management

'''Scheduled for 25 Aug, 2016, 15:00 UTC'''
# Huawei share replication and CI
# IPv6 (cknight)
# Open Discussion

'''Scheduled for 18 Aug, 2016, 15:00 UTC'''
# Driver private data admin API
#* Disagreement abounds on how this API is to be designed, tested, and presented.
#* https://review.openstack.org/#/c/315346/
# Scenario tests are broken
#* http://logs.openstack.org/86/309286/34/check/gate-manila-tempest-dsvm-scenario/610f96e/console.html
# Revert to snapshot
#* https://review.openstack.org/#/c/340502/
#* https://review.openstack.org/#/c/356682/

"Scheduled for 11 Aug, 2016, 15:00 UTC"
# None

'''Scheduled for 4 Aug, 2016, 15:00 UTC'''
# Migration APIs
#* http://lists.openstack.org/pipermail/openstack-dev/2016-August/100682.html
# Correct approach for avoiding races

'''Scheduled for 28 Jul, 2016, 15:00 UTC'''
# Stepping Down as Docs Liaison (dustins)
#* Current job responsibilities don't give me the time to devote to this that I'd like to have, so it should go to someone else with a passion for documentation and has the willingness and desire for taking up the mantle.
# N-3 Review focus
#* https://etherpad.openstack.org/p/manila-newton3-priorities

'''Scheduled for 21 Jul, 2016, 15:00 UTC'''
# Migrate API reference into tree (dgonzalez)
#* https://review.openstack.org/#/c/313874/

'''Scheduled for 14 Jul, 2016, 15:00 UTC'''
# N-2 milestone
# Managing initial security (of the root directory) for new shares
# Mascot/Logo discussion
# Tempest alternatives

'''Scheduled for 30 Jun, 2016, 15:00 UTC'''
# non-disruptive nfs-ganesha export modifications (rraja/tbarron)
#* https://sourceforge.net/p/nfs-ganesha/mailman/message/35173839
# share backup spec discussion (zhongjun)
#* https://review.openstack.org/#/c/330306

'''Scheduled for 23 Jun, 2016, 15:00 UTC'''
# Implement extend and shrink features for glusterfs driver (DaiDV)
# Do all drivers have to inherit from driver.ShareDriver? (mkoderer)
# Creating a second share instance for driver-assisted migration (ganso)

'''Scheduled for 16 Jun, 2016, 15:00 UTC'''
# A share support multiple protocols (zhongjun)
#* https://review.openstack.org/#/c/329392/
# Drivers with minimum size for shares (tpsilva)

'''Scheduled for 9 Jun, 2016, 15:00 UTC'''
# HPB feature (mkoderer)
# the fate of nova-network support in manila (gouthamr)
# multi-AZ tests in the gate

'''Scheduled for 2 Jun, 2016, 15:00 UTC'''
# N-1 milestone (bswartz)
# Decision on APIv1 removal for newton (bswartz)
# Model updates from drivers (bswartz)
# Midcycle meetup
# Spec update
#* New spec - Extending share networks to span subnets - https://review.openstack.org/#/c/323646/ (gouthamr)

'''Scheduled for 26 May, 2016, 15:00 UTC'''
# N-1 milestone
# Update access remaining work
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup
#* Nova-network removal
#* APIv1 removal
#* Model updates from the driver

'''Scheduled for 19 May, 2016, 15:00 UTC'''
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup
#* UI Customization
# Share Backup(zhongjun)
# Snapshot Restore (cknight)
# Specs (ganso)

'''Scheduled for 12 May, 2016, 15:00 UTC'''
# Driver private storage: https://review.openstack.org/#/c/315346/ (xyang)
#* Admin wants to check driver private storage before doing some actions on a resource, i.e., force delete a share or unmanage a share.
#* The patch proposes to add admin API to retrieve driver private storage data. Alternative approach proposed by Valeriy to use manila-manage (i.e., manila-manage driver-private-storage <uuid of a resource>). Which one should we choose?
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup
#* Py3 functional tests
#* Replication with share networks
#* Service-check
#* Container driver

'''Scheduled for 5 May, 2016, 15:00 UTC'''
# Topics not covered at design summit https://etherpad.openstack.org/p/newton-manila-contributor-meetup
#* Documentation update (dustins/gouthamr)
#* User messages
#* Experimental features in UI
#* Share/snapshot size mismatch
# BP Specs (tbarron)
#* Need to ensure that the repo doesn't become "a wasteland of partial ideas where hope goes to die." (See http://lists.openstack.org/pipermail/openstack-dev/2016-May/094026.html)

'''Scheduled for 14 Apr, 2016, 15:00 UTC'''
# Manage API retrying (gouthamr/nidhimittalhada)
# Tempest test structuring - resource sharing and cleanup issues (akerr)
# Snapshot support common capability in the documentation (gouthamr)

'''Scheduled for 7 Apr, 2016, 15:00 UTC'''
# Access rules (bswartz)
# Design summit planning (bswartz)
#* Link: https://etherpad.openstack.org/p/manila-newton-summit-topics
# Release notes, continued (gouthamr)
#* Link: https://review.openstack.org/#/c/300656/
# Midcycle meetup
# Access Groups
#* https://wiki.openstack.org/wiki/Manila/design/access_groups
# Revert to snapshot

'''Scheduled for 31 Mar, 2016, 15:00 UTC'''
# Mitaka release status
#* RC1 expected to be the Mitaka release build
#* Last day for a re-spin is today
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/090877.html
# Design summit planning
#* Final schedule confirms 2 fishbowls, 4 working sessions, 1 half-day meetup
#** http://lists.openstack.org/pipermail/openstack-dev/2016-March/091032.html
#* Voting open now for summit topics
#** https://etherpad.openstack.org/p/manila-newton-summit-topics
# Manila Documentation (gouthamr)
#* Where do our docs live? how do we maintain them? (In Tree: devref, adminref | out of tree: install-guide, config-ref, cloud-admin guide)
#* Need a docs liaison
#** https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation
#* Release Notes
#** http://docs.openstack.org/developer/reno/usage.html
# Managing/unmanaging replicated shares and snapshots (gouthamr)

'''Scheduled for 24 Mar, 2016, 15:00 UTC'''
# Design summit planning
#* https://etherpad.openstack.org/p/manila-newton-summit-topics
# Question about share servers (Jay.Xu)
#* Is there a way to get gateway IP address when the API setup_server() is invoked. I did not see this attribute in the input parameter network_info. Gateway IP is mandatory to create the interface for EMC storage which will be release coming soon, so it is expected that we can add the gateway IP into NetworkAllocation model if not.

'''Scheduled for 10 Mar, 2016, 15:00 UTC'''
# Common Capabilities Matrix (dustins)
#* https://review.openstack.org/#/c/288504/
#* I'm adding a table in the Developer Reference documentation to show which common capabilities are supported by which backends and when that support started.
#* I've got most drivers covered now.
#* If you want me to add your capabilities, leave a review on the patch and I'll update the table!

'''Scheduled for 25 Feb, 2016, 15:00 UTC'''

# OpenStack bug smash event (toabctl, mkoderer)
## link: https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Mitaka
# Status of new drivers
## M.3 deadline is a week away.
## Only a few things have merged in the last couple days. At this rate, many things won't make it.
## Zuul is busy and will only get worse until the deadline.
## Multiple Manila gate breakages have occurred recently, and more are likely.
## The Manila tests are very unreliable at concurrency > 1.
## The generic driver is too slow to pass the gate at concurrency = 1.
## The new drivers *are* fast enough to run at concurrency = 1.
## The new drivers may not be 100% done, but they are done enough to pass reliably at concurrency = 1.
## We should switch voting to the new drivers NOW, or start throwing stuff overboard for the release.
# Next Manila mid-cycle location
## Proposal is to do it in Germany
## Need to know who could attend at that location.
## Would it make a difference if the Cinder mid-cycle happens in Dublin, and the Manila meeting is immediately before or after the Cinder one?

'''Scheduled for 18 Feb, 2016, 15:00 UTC'''

# Feature Proposal Freeze (bswartz)
# Open Discussion

'''Scheduled for 11 Feb, 2016, 15:00 UTC'''

# Hierarchical port binding support (mkoderer)
#* https://wiki.openstack.org/wiki/Manila/design/manila-newton-hpb-support
#* https://blueprints.launchpad.net/manila/+spec/manila-hpb-support
#* https://review.openstack.org/#/c/277731/
# Next Manila mid-cycle (mkoderer)
#* https://etherpad.openstack.org/p/manila-n-release-midcycle
# Replication + ZFS Driver (bswartz)
#* https://review.openstack.org/#/c/238572
# Driver FPF (bswartz)
#* https://review.openstack.org/#/c/279090/
#* https://review.openstack.org/#/c/278169/
# HDFS CI (bswartz)
'''Scheduled for 4 Feb, 2016, 15:00 UTC'''
# Data service handling protocol mount commands (ganso)
#* https://etherpad.openstack.org/p/manila-data-service-mount-meeting
# Separate process for copy on data service (tpsilva)
# ZFS driver (bswartz)
# First party drivers share migration support cooperation (ganso)

'''Scheduled for 28 Jan, 2016, 15:00 UTC'''
# Hierarchical port binding support (mkoderer)
#* https://etherpad.openstack.org/p/manila-hierarchical-port-binding
# Core reviewer team and other manila-related projects (bswartz)
# Replication status (bswartz)

'''Scheduled for 21 Jan, 2016, 15:00 UTC'''
# Update_access backwards compatibility approach discussion. (ganso)
# Exposing the Data Service to drivers. (ganso)
# Snapshot manage/unmanage (bswartz)

'''Scheduled for 17 Dec, 2015, 15:00 UTC'''
# Proposal for share groups (cknight)
# Liberty.1 stable release (bswartz)

'''Scheduled for 10 Dec, 2015, 15:00 UTC'''
# The most of the driver already report the "'QoS_support': False" to scheduler. Does we need to remove it or save it as Qos support flat? and write 'QoS_support' to capabilities_and_extra_specs.rst?(zhongjun)
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hpe/hpe_3par_driver.py#L391
##https://github.com/openstack/manila/blob/master/manila/share/drivers/hitachi/hds_hnas.py#L354
##https://github.com/openstack/manila/blob/master/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py#L257
##https://github.com/openstack/manila/blob/master/manila/scheduler/host_manager.py#L111
##https://review.openstack.org/#/c/247286/4/doc/source/devref/capabilities_and_extra_specs.rst
# Architectural concerns and interoperability of new features (cknight)

'''Scheduled for 3 Dec, 2015, 15:00 UTC'''
# Midcycle meetup
# Add "data loss" flag in DB migrations which lead to losing of existing data and update "manila-manage db sync" command to forbid applying such migrations without "--force" flag (u_glide)
# Reorganization of Manila scheduler to merge oslo-incubator code and simplify future maintenance (cknight)
## https://review.openstack.org/#/c/252060/
## Mostly for awareness, this is now merged and should be backwards compatible.
## Cinder could benefit from a similar treatment. And with the incubator gone, we could explore a common library with the Cinder team, since the heretofore shared components are certain to diverge over time, but I'm not sure how receptive they would be. Xing?
# CI reliability
## Why should we merge patches for drivers whose CI systems consistently fail? This negates the value of CI. I think that accepting patches that aren't proven by CI does a disservice to everyone, most of all to the driver owners themselves. Refusing to merge driver patches without a good CI result for that driver seems like a gentler and more uniform-over-time approach than threatening to throw out a driver near the end of a release. And why make our illustrious and overworked PTL be the CI policeman when all core reviewers could simply glance at the corresponding CI result before giving +A? (cknight)
## http://ci-watch.tintri.com/project?project=manila
## https://review.openstack.org/#/c/232293/
## https://review.openstack.org/#/c/235522/
## https://review.openstack.org/#/c/235726/
## https://review.openstack.org/#/c/249999/
## https://review.openstack.org/#/c/237454/

'''Scheduled for 19 Nov, 2015, 15:00 UTC'''
# GB --> GiB (markstur)
# OpenStack Manuals and Devref (markstur)
#* Config Ref (and others) are moving to .RST!
#* How should we document prior releases in devref?
# Midcycle Meetup Date (bswartz)
# Deadlines for features (bswartz)
#* Feature proposal freeze vs Big Features
#* New drivers
# Data Copy Service network approach discussion (ganso)
#* https://drive.google.com/file/d/0B30HPZmaePCHMlAzcjJlYm5rRTA/view?usp=sharing

'''Scheduled for 12 Nov, 2015, 15:00 UTC'''
# Which method is better for Manila QoS(independent way or just use extra specs ) (zhongjun)
#* link:http://paste.openstack.org/show/477677/
#*If use extra specs to config QoS, Does we first need add “QoS_support=true/false” in share_type. Does we need to add QoS_support flag in common capabilities
#**https://github.com/openstack/manila/blob/master/doc/source/devref/capabilities_and_extra_specs.rst)?
#** eg: share_type: qos_support='<is> True' or '<is> False'
#** netapp:max_iops=100 or qos:netapp:max_iops=100 or qos:max_iops=100
#** driver update: qos_support=true
#** An alternative could be to have the driver report a range
# Manila DR update (ameade)
#* Still no reviews on https://review.openstack.org/#/c/238572/
#* First-party driver implementation? Which driver, current generic or new solution? When do we need this implemented and who wants to do it?
#* Replication_change share state - This is the state of the share when any of it's replicas are being promoted. Is 'replication_change' good or is there a better phrase?
# Manila Driver minimum requirements document update (ganso)
# Manila Data Copy service name (bswartz)
#*https://review.openstack.org/#/c/244286/
# Upcoming change for Manila CI hooks (vponomaryov)
#*https://review.openstack.org/#/c/243233/
# Manilaclient enhancement to provide request_id when set http_log_debug is True. It will co-ordinate the request and its id, so it will be helpful to filter the log and the failed request. (Jay Xu)
#*http://paste.openstack.org/show/478675/

'''Scheduled for 5 Nov, 2015, 15:00 UTC'''
# Decide on read-only access rules as a required feature
# Manila DR - Design/Code feedback (gouthamr)
#* [https://wiki.openstack.org/wiki/Manila/design/manila-mitaka-data-replication Design Document]
#* [https://review.openstack.org/#/c/238572/ Core Implementation on Gerrit]
#* [https://review.openstack.org/#/c/235448/ Client Implementation on Gerrit]

'''Scheduled for 1 Oct, 2015, 15:00 UTC'''
# Liberty RC2 status
#* https://launchpad.net/manila/+milestone/liberty-rc2
#* https://review.openstack.org/#/q/project:openstack/manila+branch:stable/liberty,n,z
# Mitaka Design Summit
#* https://etherpad.openstack.org/p/manila-mitaka-summit-topics
# Vendor driver docs
#* https://github.com/openstack/manila/blob/master/doc/source/devref/share_back_ends_feature_support_mapping.rst
# Manila Client Nova Style Microversion Support (cfouts)
#* https://review.openstack.org/#/c/229142/
#* http://docs.openstack.org/developer/manila/devref/api_microversion_dev.html

'''Scheduled for 24 Sep, 2015, 15:00 UTC'''
# 3rd-party CI status
#* http://ec2-54-67-102-119.us-west-1.compute.amazonaws.com:5000/?project=openstack/manila&user=&timeframe=72&start=&end=&page_size=500
#* http://ci-watch.tintri.com/project?project=manila
# Liberty RC status
# Support for QoS in Manila (zhongjun2)
#* https://blueprints.launchpad.net/manila/+spec/manila-support-qos
#* https://wiki.openstack.org/wiki/Manila/QoS
# Reminder for backend driver maintainers to update feature support table (toabctl)
#* http://docs.openstack.org/developer/manila/devref/share_back_ends_feature_support_mapping.html
# Regression when using NetApp - license issue with netapp_lib (toabctl)
#* https://bugs.launchpad.net/cinder/+bug/1499334
# Mitaka Design Summit
#* Propose topics - https://etherpad.openstack.org/p/manila-mitaka-summit-topics
# Vendor driver docs
# Open Discussion

Meetings/CyborgTeamMeeting

2019-12-18T00:40:08Z

Colleen Murphy: /* Agenda */

[[Category: Cyborg]]
[[Category: Meetings]]

== Weekly IRC Cyborg team meeting ==
* Where: <code><nowiki>#openstack-cyborg</nowiki></code> IRC channel
* When: Every Thursday at UTC 0300 (China @11 am Thu; US West Coast @8 pm Wed)

If you are not familiar with IRC, please read https://wiki.openstack.org/wiki/IRC .
You can use the web client for Freenode: http://webchat.freenode.net/?channels=openstack-cyborg.

If you want to attend but the time is not friendly to you, please post an email message in openstack-discuss.

Previous meeting logs at: http://eavesdrop.openstack.org/irclogs/%23openstack-cyborg/

=== Agenda ===
* Dec 18, 2019:
# Policy popup team (cmurphy)
## How does the cyborg team want to organize and track the work?
## Any questions I can help with at this time?
* Dec 11, 2019:
# [https://wiki.openstack.org/wiki/Consistent_and_Secure_Default_Policies_Popup_Team Secure_Default_Policies_Popup_Team]
# [https://etherpad.openstack.org/p/cyborg-ptg-ussuri Devstack conf table for multinode]
# Functional testing
# [https://etherpad.openstack.org/p/cyborg-ussuri-programming-apis Programming API proposal review], [https://review.opendev.org/#/c/698190 Shogo's programming patch]
# Storyboard, Cyborg client patches, tempest patches, main patches
* Dec 4, 2019:
# [https://etherpad.openstack.org/p/cyborg-ussuri-functional-test-plan Functional testing]
# Patches
* Nov 27, 2019:
# Decide whether to drop v1 API.
# Programming API proposal review: https://etherpad.openstack.org/p/cyborg-ussuri-programming-apis
# Functional tests update
# Storyboard review and update
* Nov 20, 2019:
# Nova status update: reviews needed
# General update: Devstack py3 (https://review.opendev.org/#/c/649097) merged
# Programming APi proposal: https://etherpad.openstack.org/p/cyborg-ussuri-programming-apis
# Review Who's Doing What, storyboard, patches
* Oct 31, 2019:
# Summit/PTG prep: move to [https://etherpad.openstack.org/p/shanghai-ptg-cyborg official etherpad]?, project onboarding in PTG, update in summit, demo
# tempest parallel tests: device profile names uniqueness, fake driver has only 1 resource, self.instance?
# Remove Justin Kilpatrick as core reviewer?
# Reviews: https://review.opendev.org/#/c/685542/
* Oct 30, 2019:
# Py2 -> Py3 migration: Do we care? If so, we need a grenade job.
# Followup: Document use cases and usage models (e.g. reserve devices for non-VM usage, enable/disable devices)
* Oct 23, 2019:
# Project updates: clarification
# Reviews: Doc patches merged and new, Glance API servers
# [http://ptg.openstack.org PTG]:
## will consolidate [https://etherpad.openstack.org/p/cyborg-ptg-ussuri planning etherpad] into [https://etherpad.openstack.org/p/shanghai-ptg-cyborg final etherpad]
## [http://lists.openstack.org/pipermail/openstack-discuss/2019-October/010047.html tables in a room]
## Team photo shoot on Thu afternoon 2 pm
* Oct 16, 2019:
# [https://etherpad.openstack.org/p/cyborg-ptg-ussuri PTG Etherpad]: add topics
# Team dinner date/time
# Project updates: Not at Summit, but in etherpad. Slides/etherpad due after the Summit.
* Aug 28
# Python 3, RBAC, client
# Code reviews
# ARQ states and transitions
# Nova functional tests
# Rm cyborg devstack job once the tempest job is introduced?

* Aug 21 (Thu in China, Wed in US):
# Python 3
# Close patch series by this week: other stuff depends on it.
* Aug 13:
# Meeting time; os-acc discontinuance
# Python-cyborgclient support, Python 3
# Do we need fake driver-based tempest for Cyborg patches?
# Storyboard tasks: RBAC, Cyborg functional tests, Nova functional tests that mock Cyborg API
* Aug 6, 2019:
# Bindep: packages for in-tree drivers?
# Drivers: Specs (use cases, CI, etc.), test plans
# Checking fake driver with Nova
# Storyboard tasks
* July 23, 2019: Spec/patch reviews.
* July 9, 2019:
# Fix https://opendev.org/openstack/cyborg-specs/src/branch/master/specs/train/cyborg-accelerator-driver.rst : location, content
# Spec review
* July 2, 2019: Spec review
* June 25, 2019: Spec review.
* June 18, 2019
# Device profile: unique names.
# Format for controlpath_id and attach_handles.
# Need to close specs. See [https://releases.openstack.org/train/schedule.html Train milestones]. Past Milestone 1.
# Zoom meeting tomorrow: use the time to review specs.

* June 11, 2019
# Cyborg-Nova CI: Fake driver (tempest), Fake Cyborg API (Nova functional test fixture)
# Python cyborg client, Python 3 migration: any opens or questions?
# Cyborg specs and patches

* June 4/5, 2019:
# Python cyborg client decision: http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006543.html
# Cyborg APi fixtures in Nova: need an owner. See [https://review.opendev.org/#/c/603955/13/specs/train/approved/nova-cyborg-interaction.rst,unified Line 409]
# Cyborg specs: [https://review.opendev.org/#/c/593726 discovery spec], [https://review.opendev.org/#/c/658498/ specs/index.rst], [https://review.opendev.org/#/c/602978/ device-profiles], [https://review.opendev.org/#/c/605237/ Instance-ops]
# Cyborg patches: Why not asserts, control path id; walk through all patches
# Zoom call tomorrow for scrubbing patches/specs?

* May 28/29, 2019:
# Nova spec update (https://review.opendev.org/#/c/603955/)
# Python cyborg client update
# Communication updates: have default IRC 'hangout times'?
# Cyborg spec, code reviews

* May 21/22, 2019:
# Cyborg spec reviews
# Nova spec review
# Merge plan and Nova notification patch status
# Python 3 transition
# Any topics for Zoom meeting tomorrow?

* May 14/15, 2019:
# Cyborg Spec reviews
# Nova spec review
# Pilot merge plan: split into smaller patches for review?, db schema change ([https://docs.openstack.org/glance/latest/contributor/database_migrations.html reference])
# Python 3 transition (time permitting. Trying to start early in cycle because there could be surprises.)

== Weekly Cyborg Zoom meeting ==
* Where: Zoom https://zoom.us/j/7680202060 [New Zoom URL for Train]
* When: Every Thursday at UTC 0130 (China @9:30 am Thu; US West Coast @6:30 pm Wed)
This is engineering-focused, and may include presentations etc.

=== Agenda ===
* June 26/27, 2019: Cancelled after agreement in IRC.
* June 19/20: We will have a session. We will use the session to review specs.
* June 12/13, 2019: No session. Please review specs.
* June 5/6, 2019:
# Cyborg API fixture or fake Cyborg driver?
# Cyborg specs and patches

* May 22/23, 2019: Cancelled
* May 15/16, 2019: Not scheduled (will start from May 21/22 with new Zoom account)

Network/Meetings

2019-12-16T17:17:51Z

Colleen Murphy: /* On Demand Agenda */

The OpenStack Networking Team ([[Neutron]]) holds public meetings as advertised on [http://eavesdrop.openstack.org/#Neutron_Team_Meeting OpenStack IRC Meetings Calendar]. If you are unable to attend, please check the most recent [http://eavesdrop.openstack.org/meetings/networking/ logs.]

=== Announcements / Reminders ===

* Still looking for "new daddies" for
** neutron-fwaas: http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010929.html
** neutron-vpnaas: http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010931.html
* Removing of neutron-interconnection from stadium project is done
* It's Ussuri-1 milestone week: https://releases.openstack.org/ussuri/schedule.html
* We now have review priority also in stadium projects' patches: https://review.opendev.org/#/c/696628/
* Voting for "V" release name is now open: http://lists.openstack.org/pipermail/openstack-discuss/2019-December/011477.html
* Shanghai PTG summary: http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010702.html and also on http://kaplonski.pl/blog/shanghai_ptg_summary/ (with photos from team dinner)

=== Blueprints ===

Blueprints which we should include in Ussuri milestones:
* Blueprints for Ussuri-1: https://launchpad.net/neutron/+milestone/ussuri-1
* https://blueprints.launchpad.net/neutron/+spec/enginefacade-switch - there is this "check patch" https://review.opendev.org/#/c/545501/
* https://blueprints.launchpad.net/neutron/+spec/secgroups-custom-ethertypes - API Support for Managing Custom Ethertypes
* https://blueprints.launchpad.net/neutron/+spec/neutron-ovn-merge - Convergence of ML2+OVS+DVR and OVN
* https://blueprints.launchpad.net/neutron/+spec/multiple-segment-per-network-per-host - spec is here: https://review.opendev.org/#/c/657170
* https://blueprints.launchpad.net/neutron/+spec/neutron-classifier-neutron-qos - there is series of patches in https://review.opendev.org/#/q/topic:qos-classifier+(status:open+OR+status:merged) - spec still not done https://review.opendev.org/#/c/678865/
* https://blueprints.launchpad.net/neutron/+spec/metadata-over-ipv6
* https://blueprints.launchpad.net/neutron/+spec/tagging-on-post
* https://blueprints.launchpad.net/neutron/+spec/evacuate-agent-resources
* https://bugs.launchpad.net/neutron/+bug/1841067 - [RFE] SR-IOV agent depends on mac addresses for getting bound ports
* https://blueprints.launchpad.net/neutron/+spec/fip-pf-description
* https://blueprints.launchpad.net/neutron/+spec/default-dns-zone-per-tenant

=== Community Goals ===

This slot is to used to track the progress of the community goals.
https://governance.openstack.org/tc/goals/index.html#release-cycles

* Support IPv6-Only Deployments (slaweq)
** https://governance.openstack.org/tc/goals/train/ipv6-support-and-testing.html
** https://storyboard.openstack.org/#!/story/2005477 (This seems to be used to track gmann's job changes)
** Patches for stadium projects are needed:
*** https://review.opendev.org/#/q/topic:ipv6-only-deployment-and-testing+(status:open+OR+status:merged)+(project:%255Eopenstack/neutron.*+OR+project:%255Eopenstack/networking-.*)
*** I need to check and update https://review.opendev.org/#/c/686043/ - as we talked with gmann to propose one neutron-tempest-plugin ipv6 job which will run all tempest plugin tests using ipv6 only,

* Drop Python 2.7 Support (njohnston)
** https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html
** Etherpad: https://etherpad.openstack.org/p/neutron-train-zuulv3-py27drop

* Project Specific PTL and Contributor Documentation
** Proposal not merged yet: https://review.opendev.org/#/c/691737/

=== Bugs and Gate issues ===

amotoki was bug deputy last week. I don't see any report from him yet.

More discussion on this topic takes place during the Neutron CI meeting: https://wiki.openstack.org/wiki/Meetings/NeutronCI

* [https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.tag=gate-failure Confirmed gate failures]
* [https://bugs.launchpad.net/neutron/+bugs?field.tag=needs-attention Bugs that need attention]
* [https://bugs.launchpad.net/neutron/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=NEW&field.status%3Alist=OPINION&field.status%3Alist=INVALID&field.status%3Alist=WONTFIX&field.status%3Alist=EXPIRED&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=FIXRELEASED&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.tag=deprecation All bug reports associated to deprecation issues]
* [https://goo.gl/KtEwbL Bugs Sheet]
* [http://grafana.openstack.org/dashboard/db/neutron-failure-rate Grafana dashboards]

==== Bug deputy ====

You can find more information about what the role is here: https://docs.openstack.org/neutron/latest/contributor/policies/bugs.html#neutron-bug-deputy

During the Denver PTG we made the decision to institute a fixed rotation for the the bugs deputy role. The current scheduled rotation is the following:

{| class="wikitable" style="text-align: center;"
|-
! Date !! who !! note
|-
| September-30-2019 || Bernard Cafarelli (bcafarel) ||
|-
| October-7-2019 || Slawek Kaplonski (slaweq) ||
|-
| October-14-2019 || Hongbin Lu (hongbin) ||
|-
| October-21-2019 || Brian Haley (haleyb) ||
|-
| October-28-2019 || Lajos Katona (lajoskatona) ||
|-
| November-4-2019 || Ryan Tidwell (tidwellr) ||
|-
| November-11-2019 || Swaminathan Vasudevan (Swami) ||
|-
| November-18-2019 || Akihiro Motoki (amotoki) || switched with Miguel Lavalle (mlavalle)
|-
| November-25-2019 || Nate Johnston (njohnston) ||
|-
| December-2-2019 || Miguel Lavalle (mlavalle) || switched with Akihiro Motoki (amotoki)
|-
| December-9-2019 || YAMAMOTO Takashi (yamamoto) ||
|-
| December-16-2019 || Bence Romsics (rubasov) ||
|}

Next bug deputy round
{| class="wikitable" style="text-align: center;"
|-
! Date !! who !! note
|-
| December-23-2019 || Bernard Cafarelli (bcafarel) || switched with Miguel Lavalle (mlavalle)
|-
| December-30-2019 || Slawek Kaplonski (slaweq) ||
|-
| January-6-2020 || Hongbin Lu (hongbin) ||
|-
| Januaryu-13-2020 || Brian Haley (haleyb) ||
|-
| January-20-2020 || Lajos Katona (lajoskatona) ||
|-
| January-27-2020 || Ryan Tidwell (tidwellr) ||
|-
| February-3-2020 || Swaminathan Vasudevan (Swami) ||
|-
| February-10-2020 || Akihiro Motoki (amotoki) ||
|-
| February-17-2020 || Nate Johnston (njohnston) ||
|-
| Fabruary-24-2020 || Miguel Lavalle (mlavalle) || switched with Bernard Cafarelli (bcafarel)
|-
| March-2-2020 || YAMAMOTO Takashi (yamamoto) ||
|-
| March-9-2020 || Bence Romsics (rubasov) ||
|}

In preparation for their duty week, deputies are encouraged to review the Neutron bugs policy: https://docs.openstack.org/neutron/latest/contributor/policies/bugs.html

=== Neutron performance subteam (Monday meetings) ===

=== Networking OVN and ML2+OVS+DVR Convergence (Tuesday meetings) ===

Merge OVN into Neutron tree:
* Blueprint: https://blueprints.launchpad.net/neutron/+spec/neutron-ovn-merge
* Proposed rehome plan: https://ethercalc.openstack.org/networking-ovn-migration
* Planning Etherpad https://etherpad.openstack.org/p/neutron-networking-ovn-merge
* Spec: https://review.opendev.org/#/c/658414/

=== Docs ===

* The future of OpenStack documentation - http://lists.openstack.org/pipermail/openstack-dev/2016-July/099012.html
* Documentation bugs - https://bugs.launchpad.net/neutron/+bugs?field.tag=doc

=== CLI/SDK ===

SDK migration of neutronclient python bindings
https://etherpad.openstack.org/p/neutron-openstacksdk-migration

Status of changes to deliver OSC (this needs to be revisit)
* https://etherpad.openstack.org/p/osc-transition-priorities
* http://docs.openstack.org/developer/python-neutronclient/devref/transition_to_osc.html

=== Neutron-lib, planned refactoring and other impacts ===

I proposed release of new neutron-lib version without:
* https://review.opendev.org/#/c/695205/

Those are included:
* https://review.opendev.org/#/c/692580/ - merged
* https://review.opendev.org/#/c/696308/ - merged
* https://review.opendev.org/#/c/696070/ - merged

Release patch https://review.opendev.org/#/c/697956/

HOUSE KEEPING
* Neutron-lib work items and volunteers are being tracked via etherpad: https://etherpad.openstack.org/p/neutron-lib-volunteers-and-punch-list
* For a list of "current" consumers who receive neutron-lib updates and consumption patches, see: http://codesearch.openstack.org/?q=neutron-lib-current
* For a complete list of neutron-lib consumption patches that may impact consumers see: https://review.openstack.org/#/q/message:%22NeutronLibImpact%22

PATCHES THAT NEED REVIEWS
* Decouple DB workstream/blueprint: https://review.openstack.org/#/q/status:open+topic:bp/neutronlib-decouple-db+label:Workflow%253D0
* Callback payload workstream: https://review.openstack.org/#/q/status:open+topic:use-callback-payloads+label:Workflow%253D0
* Updating projects for Zuul v3: https://review.openstack.org/#/q/status:open+topic:neutronlib-zuulv3

=== On Demand Agenda ===

We can only pick one or two topics we can talk in the time left of the meeting. People should add ideas to the topics section. We will select one or two topics we can chew during the next meeting. Please follow the template below:

* Topic for the meeting (keep this template, please):
** (your nickname): brief description.
*** More details
** (cmurphy): Policy pop-up team sync up
*** How do you want to organize and track the work?
*** What questions do you have about implementation?

== Previous meeting logs ==
* Previous meetings, with their notes and logs, can be found [http://eavesdrop.openstack.org/meetings/networking/ here].
** [http://eavesdrop.openstack.org/meetings/networking/2019/?C=M;O=D networking-2019]
** [http://eavesdrop.openstack.org/meetings/networking/2018/?C=M;O=D networking-2018]
** [http://eavesdrop.openstack.org/meetings/networking/2017/?C=M;O=D networking-2017]
** [http://eavesdrop.openstack.org/meetings/networking/2016/?C=M;O=D networking-2016]
** [http://eavesdrop.openstack.org/meetings/networking/2015/?C=M;O=D networking-2015]
** [http://eavesdrop.openstack.org/meetings/networking/2014/?C=M;O=D networking-2014]
** [http://eavesdrop.openstack.org/meetings/networking/2013/?C=M;O=D networking-2013]
** [http://eavesdrop.openstack.org/meetings/quantum/2013/?C=M;O=D quantum-2013]
** [http://eavesdrop.openstack.org/meetings/quantum/2012/?C=M;O=D quantum-2012]

First Contact SIG

2019-12-04T01:08:29Z

Colleen Murphy: /* First Contact SIG */

Consistent and Secure Default Policies Popup Team

2019-11-27T20:43:50Z

Colleen Murphy: /* Popup Team Completion Criteria */

== Problem Description ==

Existing policy defaults suffer from three major faults:

# the admin-ness problem: use of policy rules like 'is_admin' or hard-coded is-admin checks results in the admin-anywhere-admin-everywhere problem and drastically inhibits true multi-tenancy since by default customers cannot have admin rights on their own projects or domains
# insecure custom roles: many policy rules simply use "" as the rule, which means there is no rule: anyone can perform that action. This means creation of a custom role (say, "nova-autoscaler" requires editing every policy file across every service to block users with such a rule from performing actions unrelated to their role
# related to #2, no support for read-only roles: keystone now has a "reader" role that comes out of the box when keystone is bootstrapped, but it currently has very little value because of the use of empty rules in service policies: users with the "reader" role can still perform write actions on services if the policy rule for such an action is empty.

== Team Goal ==

The keystone project has migrated all of its default policies to 1) use oslo.policy's scope_types attribute, which allows the policy engine to understand "system scope" and distinguish between an admin role assignment on a project versus an admin role assignment on the entire system, 2) ensure all rules use one of the default roles (admin, member, and reader) which both ensures support for a read-only role and prevents custom roles from accidental over-permissiveness. Although the problems being solved are slightly different, the keystone team found it was easiest to migrate everything at once. The rest of the OpenStack services can use this migration as a template for securing their own policies.

== Popup Team Completion Criteria ==

This team will be disbanded after:

# The majority of the projects listed below have completed their policy migrations
# A document is published detailing any pitfalls, lessons learned, and best practices that other teams should be aware of
# A community goal is proposed and accepted by the TC

== Communication ==

Use topic:policy-popup in Gerrit.

Use subject tag [policy] for mailing list discussions.

Use #openstack-dev for synchronous discussions.

== Leads ==

# Colleen Murphy <colleen@gazlene.net> (cmurphy) [Seeking a replacement]
# Ghanshyam Mann <gmann@ghanshyammann.com> (gmann)

== Liaisons ==

* Barbican: Douglas Mendizábal (redrobot)
* Nova: Ghanshyam Mann (gmann)
* Neutron: Miguel Lavalle (mlavalle)
* Cinder: Brian Rosmaita (rosmaita)
* Cyborg: Yumeng Bao (yumeng_bao@yahoo.com)
* Manila: Goutham Pacha Ravi (gouthamr)

== Members ==

* Mohammed Naser <mnaser@vexxhost.com>
* Douglas Mendizábal (IRC: redrobot) - Barbican - We're supere interested in getting this implemented for Barbican
* Ade Lee (ade_lee) - barbican
* Miguel Lavalle (mlavalle) - neutron
* Chandan Kumar (chandankumar/raukadah)<chkumar@redhat.com> - Help on Tempest and Patrole side
* Akihiro Motoki (amotoki) - horizon (horizon needs to support the new mechanism of policy definitions. It is different from server side support, so the team needs to explore its own way)
* Tobias Rydberg (tobberydberg)
* Erik McCormick <emccormick@cirrusseven.com> (emccormick)
* Tergel Munkhbat tergel@fibo.cloud
* Ghanshyam Mann (gmann): Nova, QA adopt testing for the new roles.
* Vishakha Agarwal (vishakha)- Keystone

== Team Design Documents ==

=== Keystone (completed; use as a reference) ===

* http://specs.openstack.org/openstack/keystone-specs/specs/keystone/ongoing/policy-goals-and-roadmap.html
* https://bugs.launchpad.net/keystone/+bugs?field.status%3Alist=FIXRELEASED&field.tag=default-roles+system-scope&field.tags_combinator=ANY

=== Barbican ===

* https://wiki.openstack.org/wiki/Barbican/Policy

=== Nova ===

* https://specs.openstack.org/openstack/nova-specs/specs/ussuri/approved/policy-defaults-refresh.html

=== Neutron ===

none yet

=== Cinder ===

none yet

=== Cyborg ===

none yet

=== Manila ===

none yet

== Progress ==

TBD - each project may have its own tracking mechanism, to be linked here

== Reviews ==

https://review.opendev.org/#/q/is:open+topic:policy-popup

== References ==

* All about scopes: https://docs.openstack.org/keystone/latest/contributor/services.html#authorization-scopes
* Default roles and scopes: https://docs.openstack.org/keystone/latest/admin/service-api-protection.html

Consistent and Secure Default Policies Popup Team

2019-11-27T20:43:19Z

Colleen Murphy: /* Team Design Documents */

== Problem Description ==

Existing policy defaults suffer from three major faults:

# the admin-ness problem: use of policy rules like 'is_admin' or hard-coded is-admin checks results in the admin-anywhere-admin-everywhere problem and drastically inhibits true multi-tenancy since by default customers cannot have admin rights on their own projects or domains
# insecure custom roles: many policy rules simply use "" as the rule, which means there is no rule: anyone can perform that action. This means creation of a custom role (say, "nova-autoscaler" requires editing every policy file across every service to block users with such a rule from performing actions unrelated to their role
# related to #2, no support for read-only roles: keystone now has a "reader" role that comes out of the box when keystone is bootstrapped, but it currently has very little value because of the use of empty rules in service policies: users with the "reader" role can still perform write actions on services if the policy rule for such an action is empty.

== Team Goal ==

The keystone project has migrated all of its default policies to 1) use oslo.policy's scope_types attribute, which allows the policy engine to understand "system scope" and distinguish between an admin role assignment on a project versus an admin role assignment on the entire system, 2) ensure all rules use one of the default roles (admin, member, and reader) which both ensures support for a read-only role and prevents custom roles from accidental over-permissiveness. Although the problems being solved are slightly different, the keystone team found it was easiest to migrate everything at once. The rest of the OpenStack services can use this migration as a template for securing their own policies.

== Popup Team Completion Criteria ==

This team will be disbanded after:

# The barbican, nova, neutron, cinder, and cyborg projects have completed their policy migrations
# A document is published detailing any pitfalls, lessons learned, and best practices that other teams should be aware of
# A community goal is proposed and accepted by the TC

== Communication ==

Use topic:policy-popup in Gerrit.

Use subject tag [policy] for mailing list discussions.

Use #openstack-dev for synchronous discussions.

== Leads ==

# Colleen Murphy <colleen@gazlene.net> (cmurphy) [Seeking a replacement]
# Ghanshyam Mann <gmann@ghanshyammann.com> (gmann)

== Liaisons ==

* Barbican: Douglas Mendizábal (redrobot)
* Nova: Ghanshyam Mann (gmann)
* Neutron: Miguel Lavalle (mlavalle)
* Cinder: Brian Rosmaita (rosmaita)
* Cyborg: Yumeng Bao (yumeng_bao@yahoo.com)
* Manila: Goutham Pacha Ravi (gouthamr)

== Members ==

* Mohammed Naser <mnaser@vexxhost.com>
* Douglas Mendizábal (IRC: redrobot) - Barbican - We're supere interested in getting this implemented for Barbican
* Ade Lee (ade_lee) - barbican
* Miguel Lavalle (mlavalle) - neutron
* Chandan Kumar (chandankumar/raukadah)<chkumar@redhat.com> - Help on Tempest and Patrole side
* Akihiro Motoki (amotoki) - horizon (horizon needs to support the new mechanism of policy definitions. It is different from server side support, so the team needs to explore its own way)
* Tobias Rydberg (tobberydberg)
* Erik McCormick <emccormick@cirrusseven.com> (emccormick)
* Tergel Munkhbat tergel@fibo.cloud
* Ghanshyam Mann (gmann): Nova, QA adopt testing for the new roles.
* Vishakha Agarwal (vishakha)- Keystone

== Team Design Documents ==

=== Keystone (completed; use as a reference) ===

* http://specs.openstack.org/openstack/keystone-specs/specs/keystone/ongoing/policy-goals-and-roadmap.html
* https://bugs.launchpad.net/keystone/+bugs?field.status%3Alist=FIXRELEASED&field.tag=default-roles+system-scope&field.tags_combinator=ANY

=== Barbican ===

* https://wiki.openstack.org/wiki/Barbican/Policy

=== Nova ===

* https://specs.openstack.org/openstack/nova-specs/specs/ussuri/approved/policy-defaults-refresh.html

=== Neutron ===

none yet

=== Cinder ===

none yet

=== Cyborg ===

none yet

=== Manila ===

none yet

== Progress ==

TBD - each project may have its own tracking mechanism, to be linked here

== Reviews ==

https://review.opendev.org/#/q/is:open+topic:policy-popup

== References ==

* All about scopes: https://docs.openstack.org/keystone/latest/contributor/services.html#authorization-scopes
* Default roles and scopes: https://docs.openstack.org/keystone/latest/admin/service-api-protection.html

Consistent and Secure Default Policies Popup Team

2019-11-27T20:42:52Z

Colleen Murphy: /* Liaisons */

== Problem Description ==

Existing policy defaults suffer from three major faults:

# the admin-ness problem: use of policy rules like 'is_admin' or hard-coded is-admin checks results in the admin-anywhere-admin-everywhere problem and drastically inhibits true multi-tenancy since by default customers cannot have admin rights on their own projects or domains
# insecure custom roles: many policy rules simply use "" as the rule, which means there is no rule: anyone can perform that action. This means creation of a custom role (say, "nova-autoscaler" requires editing every policy file across every service to block users with such a rule from performing actions unrelated to their role
# related to #2, no support for read-only roles: keystone now has a "reader" role that comes out of the box when keystone is bootstrapped, but it currently has very little value because of the use of empty rules in service policies: users with the "reader" role can still perform write actions on services if the policy rule for such an action is empty.

== Team Goal ==

The keystone project has migrated all of its default policies to 1) use oslo.policy's scope_types attribute, which allows the policy engine to understand "system scope" and distinguish between an admin role assignment on a project versus an admin role assignment on the entire system, 2) ensure all rules use one of the default roles (admin, member, and reader) which both ensures support for a read-only role and prevents custom roles from accidental over-permissiveness. Although the problems being solved are slightly different, the keystone team found it was easiest to migrate everything at once. The rest of the OpenStack services can use this migration as a template for securing their own policies.

== Popup Team Completion Criteria ==

This team will be disbanded after:

# The barbican, nova, neutron, cinder, and cyborg projects have completed their policy migrations
# A document is published detailing any pitfalls, lessons learned, and best practices that other teams should be aware of
# A community goal is proposed and accepted by the TC

== Communication ==

Use topic:policy-popup in Gerrit.

Use subject tag [policy] for mailing list discussions.

Use #openstack-dev for synchronous discussions.

== Leads ==

# Colleen Murphy <colleen@gazlene.net> (cmurphy) [Seeking a replacement]
# Ghanshyam Mann <gmann@ghanshyammann.com> (gmann)

== Liaisons ==

* Barbican: Douglas Mendizábal (redrobot)
* Nova: Ghanshyam Mann (gmann)
* Neutron: Miguel Lavalle (mlavalle)
* Cinder: Brian Rosmaita (rosmaita)
* Cyborg: Yumeng Bao (yumeng_bao@yahoo.com)
* Manila: Goutham Pacha Ravi (gouthamr)

== Members ==

* Mohammed Naser <mnaser@vexxhost.com>
* Douglas Mendizábal (IRC: redrobot) - Barbican - We're supere interested in getting this implemented for Barbican
* Ade Lee (ade_lee) - barbican
* Miguel Lavalle (mlavalle) - neutron
* Chandan Kumar (chandankumar/raukadah)<chkumar@redhat.com> - Help on Tempest and Patrole side
* Akihiro Motoki (amotoki) - horizon (horizon needs to support the new mechanism of policy definitions. It is different from server side support, so the team needs to explore its own way)
* Tobias Rydberg (tobberydberg)
* Erik McCormick <emccormick@cirrusseven.com> (emccormick)
* Tergel Munkhbat tergel@fibo.cloud
* Ghanshyam Mann (gmann): Nova, QA adopt testing for the new roles.
* Vishakha Agarwal (vishakha)- Keystone

== Team Design Documents ==

=== Keystone (completed; use as a reference) ===

* http://specs.openstack.org/openstack/keystone-specs/specs/keystone/ongoing/policy-goals-and-roadmap.html
* https://bugs.launchpad.net/keystone/+bugs?field.status%3Alist=FIXRELEASED&field.tag=default-roles+system-scope&field.tags_combinator=ANY

=== Barbican ===

* https://wiki.openstack.org/wiki/Barbican/Policy

=== Nova ===

* https://specs.openstack.org/openstack/nova-specs/specs/ussuri/approved/policy-defaults-refresh.html

=== Neutron ===

none yet

=== Cinder ===

none yet

=== Cyborg ===

none yet

== Progress ==

TBD - each project may have its own tracking mechanism, to be linked here

== Reviews ==

https://review.opendev.org/#/q/is:open+topic:policy-popup

== References ==

* All about scopes: https://docs.openstack.org/keystone/latest/contributor/services.html#authorization-scopes
* Default roles and scopes: https://docs.openstack.org/keystone/latest/admin/service-api-protection.html

Consistent and Secure Default Policies Popup Team

2019-11-26T16:49:30Z

Colleen Murphy: /* Team Design Documents */

== Problem Description ==

Existing policy defaults suffer from three major faults:

# the admin-ness problem: use of policy rules like 'is_admin' or hard-coded is-admin checks results in the admin-anywhere-admin-everywhere problem and drastically inhibits true multi-tenancy since by default customers cannot have admin rights on their own projects or domains
# insecure custom roles: many policy rules simply use "" as the rule, which means there is no rule: anyone can perform that action. This means creation of a custom role (say, "nova-autoscaler" requires editing every policy file across every service to block users with such a rule from performing actions unrelated to their role
# related to #2, no support for read-only roles: keystone now has a "reader" role that comes out of the box when keystone is bootstrapped, but it currently has very little value because of the use of empty rules in service policies: users with the "reader" role can still perform write actions on services if the policy rule for such an action is empty.

== Team Goal ==

The keystone project has migrated all of its default policies to 1) use oslo.policy's scope_types attribute, which allows the policy engine to understand "system scope" and distinguish between an admin role assignment on a project versus an admin role assignment on the entire system, 2) ensure all rules use one of the default roles (admin, member, and reader) which both ensures support for a read-only role and prevents custom roles from accidental over-permissiveness. Although the problems being solved are slightly different, the keystone team found it was easiest to migrate everything at once. The rest of the OpenStack services can use this migration as a template for securing their own policies.

== Popup Team Completion Criteria ==

This team will be disbanded after:

# The barbican, nova, neutron, cinder, and cyborg projects have completed their policy migrations
# A document is published detailing any pitfalls, lessons learned, and best practices that other teams should be aware of
# A community goal is proposed and accepted by the TC

== Communication ==

Use topic:policy-popup in Gerrit.

Use subject tag [policy] for mailing list discussions.

Use #openstack-dev for synchronous discussions.

== Leads ==

# Colleen Murphy <colleen@gazlene.net> (cmurphy) [Seeking a replacement]
# Ghanshyam Mann <gmann@ghanshyammann.com> (gmann)

== Liaisons ==

* Barbican: Douglas Mendizábal (redrobot)
* Nova: Ghanshyam Mann (gmann)
* Neutron: Miguel Lavalle (mlavalle)
* Cinder: Brian Rosmaita (rosmaita)
* Cyborg: Zhipeng (Howard) Huang (zhipeng)

== Members ==

* Mohammed Naser <mnaser@vexxhost.com>
* Douglas Mendizábal (IRC: redrobot) - Barbican - We're supere interested in getting this implemented for Barbican
* Ade Lee (ade_lee) - barbican
* Miguel Lavalle (mlavalle) - neutron
* Chandan Kumar (chandankumar/raukadah)<chkumar@redhat.com> - Help on Tempest and Patrole side
* Akihiro Motoki (amotoki) - horizon (horizon needs to support the new mechanism of policy definitions. It is different from server side support, so the team needs to explore its own way)
* Tobias Rydberg (tobberydberg)
* Erik McCormick <emccormick@cirrusseven.com> (emccormick)
* Tergel Munkhbat tergel@fibo.cloud
* Ghanshyam Mann (gmann): Nova, QA adopt testing for the new roles.
* Vishakha Agarwal (vishakha)- Keystone

== Team Design Documents ==

=== Keystone (completed; use as a reference) ===

* http://specs.openstack.org/openstack/keystone-specs/specs/keystone/ongoing/policy-goals-and-roadmap.html
* https://bugs.launchpad.net/keystone/+bugs?field.status%3Alist=FIXRELEASED&field.tag=default-roles+system-scope&field.tags_combinator=ANY

=== Barbican ===

* https://wiki.openstack.org/wiki/Barbican/Policy

=== Nova ===

* https://specs.openstack.org/openstack/nova-specs/specs/ussuri/approved/policy-defaults-refresh.html

=== Neutron ===

none yet

=== Cinder ===

none yet

=== Cyborg ===

none yet

== Progress ==

TBD - each project may have its own tracking mechanism, to be linked here

== Reviews ==

https://review.opendev.org/#/q/is:open+topic:policy-popup

== References ==

* All about scopes: https://docs.openstack.org/keystone/latest/contributor/services.html#authorization-scopes
* Default roles and scopes: https://docs.openstack.org/keystone/latest/admin/service-api-protection.html

Consistent and Secure Default Policies Popup Team

2019-11-26T16:49:09Z

Colleen Murphy: /* Liaisons */

== Problem Description ==

Existing policy defaults suffer from three major faults:

# the admin-ness problem: use of policy rules like 'is_admin' or hard-coded is-admin checks results in the admin-anywhere-admin-everywhere problem and drastically inhibits true multi-tenancy since by default customers cannot have admin rights on their own projects or domains
# insecure custom roles: many policy rules simply use "" as the rule, which means there is no rule: anyone can perform that action. This means creation of a custom role (say, "nova-autoscaler" requires editing every policy file across every service to block users with such a rule from performing actions unrelated to their role
# related to #2, no support for read-only roles: keystone now has a "reader" role that comes out of the box when keystone is bootstrapped, but it currently has very little value because of the use of empty rules in service policies: users with the "reader" role can still perform write actions on services if the policy rule for such an action is empty.

== Team Goal ==

The keystone project has migrated all of its default policies to 1) use oslo.policy's scope_types attribute, which allows the policy engine to understand "system scope" and distinguish between an admin role assignment on a project versus an admin role assignment on the entire system, 2) ensure all rules use one of the default roles (admin, member, and reader) which both ensures support for a read-only role and prevents custom roles from accidental over-permissiveness. Although the problems being solved are slightly different, the keystone team found it was easiest to migrate everything at once. The rest of the OpenStack services can use this migration as a template for securing their own policies.

== Popup Team Completion Criteria ==

This team will be disbanded after:

# The barbican, nova, neutron, cinder, and cyborg projects have completed their policy migrations
# A document is published detailing any pitfalls, lessons learned, and best practices that other teams should be aware of
# A community goal is proposed and accepted by the TC

== Communication ==

Use topic:policy-popup in Gerrit.

Use subject tag [policy] for mailing list discussions.

Use #openstack-dev for synchronous discussions.

== Leads ==

# Colleen Murphy <colleen@gazlene.net> (cmurphy) [Seeking a replacement]
# Ghanshyam Mann <gmann@ghanshyammann.com> (gmann)

== Liaisons ==

* Barbican: Douglas Mendizábal (redrobot)
* Nova: Ghanshyam Mann (gmann)
* Neutron: Miguel Lavalle (mlavalle)
* Cinder: Brian Rosmaita (rosmaita)
* Cyborg: Zhipeng (Howard) Huang (zhipeng)

== Members ==

* Mohammed Naser <mnaser@vexxhost.com>
* Douglas Mendizábal (IRC: redrobot) - Barbican - We're supere interested in getting this implemented for Barbican
* Ade Lee (ade_lee) - barbican
* Miguel Lavalle (mlavalle) - neutron
* Chandan Kumar (chandankumar/raukadah)<chkumar@redhat.com> - Help on Tempest and Patrole side
* Akihiro Motoki (amotoki) - horizon (horizon needs to support the new mechanism of policy definitions. It is different from server side support, so the team needs to explore its own way)
* Tobias Rydberg (tobberydberg)
* Erik McCormick <emccormick@cirrusseven.com> (emccormick)
* Tergel Munkhbat tergel@fibo.cloud
* Ghanshyam Mann (gmann): Nova, QA adopt testing for the new roles.
* Vishakha Agarwal (vishakha)- Keystone

== Team Design Documents ==

=== Keystone (completed; use as a reference) ===

* http://specs.openstack.org/openstack/keystone-specs/specs/keystone/ongoing/policy-goals-and-roadmap.html
* https://bugs.launchpad.net/keystone/+bugs?field.status%3Alist=FIXRELEASED&field.tag=default-roles+system-scope&field.tags_combinator=ANY

=== Barbican ===

* https://wiki.openstack.org/wiki/Barbican/Policy

=== Nova ===

* https://specs.openstack.org/openstack/nova-specs/specs/ussuri/approved/policy-defaults-refresh.html

=== Neutron ===

none yet

=== Cinder ===

none yet

== Progress ==

TBD - each project may have its own tracking mechanism, to be linked here

== Reviews ==

https://review.opendev.org/#/q/is:open+topic:policy-popup

== References ==

* All about scopes: https://docs.openstack.org/keystone/latest/contributor/services.html#authorization-scopes
* Default roles and scopes: https://docs.openstack.org/keystone/latest/admin/service-api-protection.html

Consistent and Secure Default Policies Popup Team

2019-11-26T16:46:57Z

Colleen Murphy: /* Popup Team Completion Criteria */

== Problem Description ==

Existing policy defaults suffer from three major faults:

# the admin-ness problem: use of policy rules like 'is_admin' or hard-coded is-admin checks results in the admin-anywhere-admin-everywhere problem and drastically inhibits true multi-tenancy since by default customers cannot have admin rights on their own projects or domains
# insecure custom roles: many policy rules simply use "" as the rule, which means there is no rule: anyone can perform that action. This means creation of a custom role (say, "nova-autoscaler" requires editing every policy file across every service to block users with such a rule from performing actions unrelated to their role
# related to #2, no support for read-only roles: keystone now has a "reader" role that comes out of the box when keystone is bootstrapped, but it currently has very little value because of the use of empty rules in service policies: users with the "reader" role can still perform write actions on services if the policy rule for such an action is empty.

== Team Goal ==

The keystone project has migrated all of its default policies to 1) use oslo.policy's scope_types attribute, which allows the policy engine to understand "system scope" and distinguish between an admin role assignment on a project versus an admin role assignment on the entire system, 2) ensure all rules use one of the default roles (admin, member, and reader) which both ensures support for a read-only role and prevents custom roles from accidental over-permissiveness. Although the problems being solved are slightly different, the keystone team found it was easiest to migrate everything at once. The rest of the OpenStack services can use this migration as a template for securing their own policies.

== Popup Team Completion Criteria ==

This team will be disbanded after:

# The barbican, nova, neutron, cinder, and cyborg projects have completed their policy migrations
# A document is published detailing any pitfalls, lessons learned, and best practices that other teams should be aware of
# A community goal is proposed and accepted by the TC

== Communication ==

Use topic:policy-popup in Gerrit.

Use subject tag [policy] for mailing list discussions.

Use #openstack-dev for synchronous discussions.

== Leads ==

# Colleen Murphy <colleen@gazlene.net> (cmurphy) [Seeking a replacement]
# Ghanshyam Mann <gmann@ghanshyammann.com> (gmann)

== Liaisons ==

* Barbican: Douglas Mendizábal (redrobot)
* Nova: Ghanshyam Mann (gmann)
* Neutron: Miguel Lavalle (mlavalle)
* Cinder: Brian Rosmaita (rosmaita)

== Members ==

* Mohammed Naser <mnaser@vexxhost.com>
* Douglas Mendizábal (IRC: redrobot) - Barbican - We're supere interested in getting this implemented for Barbican
* Ade Lee (ade_lee) - barbican
* Miguel Lavalle (mlavalle) - neutron
* Chandan Kumar (chandankumar/raukadah)<chkumar@redhat.com> - Help on Tempest and Patrole side
* Akihiro Motoki (amotoki) - horizon (horizon needs to support the new mechanism of policy definitions. It is different from server side support, so the team needs to explore its own way)
* Tobias Rydberg (tobberydberg)
* Erik McCormick <emccormick@cirrusseven.com> (emccormick)
* Tergel Munkhbat tergel@fibo.cloud
* Ghanshyam Mann (gmann): Nova, QA adopt testing for the new roles.
* Vishakha Agarwal (vishakha)- Keystone

== Team Design Documents ==

=== Keystone (completed; use as a reference) ===

* http://specs.openstack.org/openstack/keystone-specs/specs/keystone/ongoing/policy-goals-and-roadmap.html
* https://bugs.launchpad.net/keystone/+bugs?field.status%3Alist=FIXRELEASED&field.tag=default-roles+system-scope&field.tags_combinator=ANY

=== Barbican ===

* https://wiki.openstack.org/wiki/Barbican/Policy

=== Nova ===

* https://specs.openstack.org/openstack/nova-specs/specs/ussuri/approved/policy-defaults-refresh.html

=== Neutron ===

none yet

=== Cinder ===

none yet

== Progress ==

TBD - each project may have its own tracking mechanism, to be linked here

== Reviews ==

https://review.opendev.org/#/q/is:open+topic:policy-popup

== References ==

* All about scopes: https://docs.openstack.org/keystone/latest/contributor/services.html#authorization-scopes
* Default roles and scopes: https://docs.openstack.org/keystone/latest/admin/service-api-protection.html

Consistent and Secure Default Policies Popup Team

2019-11-26T16:46:22Z

Colleen Murphy: /* Chairs */

== Problem Description ==

Existing policy defaults suffer from three major faults:

# the admin-ness problem: use of policy rules like 'is_admin' or hard-coded is-admin checks results in the admin-anywhere-admin-everywhere problem and drastically inhibits true multi-tenancy since by default customers cannot have admin rights on their own projects or domains
# insecure custom roles: many policy rules simply use "" as the rule, which means there is no rule: anyone can perform that action. This means creation of a custom role (say, "nova-autoscaler" requires editing every policy file across every service to block users with such a rule from performing actions unrelated to their role
# related to #2, no support for read-only roles: keystone now has a "reader" role that comes out of the box when keystone is bootstrapped, but it currently has very little value because of the use of empty rules in service policies: users with the "reader" role can still perform write actions on services if the policy rule for such an action is empty.

== Team Goal ==

The keystone project has migrated all of its default policies to 1) use oslo.policy's scope_types attribute, which allows the policy engine to understand "system scope" and distinguish between an admin role assignment on a project versus an admin role assignment on the entire system, 2) ensure all rules use one of the default roles (admin, member, and reader) which both ensures support for a read-only role and prevents custom roles from accidental over-permissiveness. Although the problems being solved are slightly different, the keystone team found it was easiest to migrate everything at once. The rest of the OpenStack services can use this migration as a template for securing their own policies.

== Popup Team Completion Criteria ==

This team will be disbanded after:

# The barbican, nova, neutron, and cinder projects have completed their policy migrations
# A document is published detailing any pitfalls, lessons learned, and best practices that other teams should be aware of
# A community goal is proposed and accepted by the TC

== Communication ==

Use topic:policy-popup in Gerrit.

Use subject tag [policy] for mailing list discussions.

Use #openstack-dev for synchronous discussions.

== Leads ==

# Colleen Murphy <colleen@gazlene.net> (cmurphy) [Seeking a replacement]
# Ghanshyam Mann <gmann@ghanshyammann.com> (gmann)

== Liaisons ==

* Barbican: Douglas Mendizábal (redrobot)
* Nova: Ghanshyam Mann (gmann)
* Neutron: Miguel Lavalle (mlavalle)
* Cinder: Brian Rosmaita (rosmaita)

== Members ==

* Mohammed Naser <mnaser@vexxhost.com>
* Douglas Mendizábal (IRC: redrobot) - Barbican - We're supere interested in getting this implemented for Barbican
* Ade Lee (ade_lee) - barbican
* Miguel Lavalle (mlavalle) - neutron
* Chandan Kumar (chandankumar/raukadah)<chkumar@redhat.com> - Help on Tempest and Patrole side
* Akihiro Motoki (amotoki) - horizon (horizon needs to support the new mechanism of policy definitions. It is different from server side support, so the team needs to explore its own way)
* Tobias Rydberg (tobberydberg)
* Erik McCormick <emccormick@cirrusseven.com> (emccormick)
* Tergel Munkhbat tergel@fibo.cloud
* Ghanshyam Mann (gmann): Nova, QA adopt testing for the new roles.
* Vishakha Agarwal (vishakha)- Keystone

== Team Design Documents ==

=== Keystone (completed; use as a reference) ===

* http://specs.openstack.org/openstack/keystone-specs/specs/keystone/ongoing/policy-goals-and-roadmap.html
* https://bugs.launchpad.net/keystone/+bugs?field.status%3Alist=FIXRELEASED&field.tag=default-roles+system-scope&field.tags_combinator=ANY

=== Barbican ===

* https://wiki.openstack.org/wiki/Barbican/Policy

=== Nova ===

* https://specs.openstack.org/openstack/nova-specs/specs/ussuri/approved/policy-defaults-refresh.html

=== Neutron ===

none yet

=== Cinder ===

none yet

== Progress ==

TBD - each project may have its own tracking mechanism, to be linked here

== Reviews ==

https://review.opendev.org/#/q/is:open+topic:policy-popup

== References ==

* All about scopes: https://docs.openstack.org/keystone/latest/contributor/services.html#authorization-scopes
* Default roles and scopes: https://docs.openstack.org/keystone/latest/admin/service-api-protection.html

Consistent and Secure Default Policies Popup Team

2019-11-26T16:45:21Z

Colleen Murphy: /* Chairs */

== Problem Description ==

Existing policy defaults suffer from three major faults:

# the admin-ness problem: use of policy rules like 'is_admin' or hard-coded is-admin checks results in the admin-anywhere-admin-everywhere problem and drastically inhibits true multi-tenancy since by default customers cannot have admin rights on their own projects or domains
# insecure custom roles: many policy rules simply use "" as the rule, which means there is no rule: anyone can perform that action. This means creation of a custom role (say, "nova-autoscaler" requires editing every policy file across every service to block users with such a rule from performing actions unrelated to their role
# related to #2, no support for read-only roles: keystone now has a "reader" role that comes out of the box when keystone is bootstrapped, but it currently has very little value because of the use of empty rules in service policies: users with the "reader" role can still perform write actions on services if the policy rule for such an action is empty.

== Team Goal ==

The keystone project has migrated all of its default policies to 1) use oslo.policy's scope_types attribute, which allows the policy engine to understand "system scope" and distinguish between an admin role assignment on a project versus an admin role assignment on the entire system, 2) ensure all rules use one of the default roles (admin, member, and reader) which both ensures support for a read-only role and prevents custom roles from accidental over-permissiveness. Although the problems being solved are slightly different, the keystone team found it was easiest to migrate everything at once. The rest of the OpenStack services can use this migration as a template for securing their own policies.

== Popup Team Completion Criteria ==

This team will be disbanded after:

# The barbican, nova, neutron, and cinder projects have completed their policy migrations
# A document is published detailing any pitfalls, lessons learned, and best practices that other teams should be aware of
# A community goal is proposed and accepted by the TC

== Communication ==

Use topic:policy-popup in Gerrit.

Use subject tag [policy] for mailing list discussions.

Use #openstack-dev for synchronous discussions.

== Chairs ==

# Colleen Murphy <colleen@gazlene.net> (cmurphy) [Seeking a replacement]
# Ghanshyam Mann <gmann@ghanshyammann.com> (gmann)

== Liaisons ==

* Barbican: Douglas Mendizábal (redrobot)
* Nova: Ghanshyam Mann (gmann)
* Neutron: Miguel Lavalle (mlavalle)
* Cinder: Brian Rosmaita (rosmaita)

== Members ==

* Mohammed Naser <mnaser@vexxhost.com>
* Douglas Mendizábal (IRC: redrobot) - Barbican - We're supere interested in getting this implemented for Barbican
* Ade Lee (ade_lee) - barbican
* Miguel Lavalle (mlavalle) - neutron
* Chandan Kumar (chandankumar/raukadah)<chkumar@redhat.com> - Help on Tempest and Patrole side
* Akihiro Motoki (amotoki) - horizon (horizon needs to support the new mechanism of policy definitions. It is different from server side support, so the team needs to explore its own way)
* Tobias Rydberg (tobberydberg)
* Erik McCormick <emccormick@cirrusseven.com> (emccormick)
* Tergel Munkhbat tergel@fibo.cloud
* Ghanshyam Mann (gmann): Nova, QA adopt testing for the new roles.
* Vishakha Agarwal (vishakha)- Keystone

== Team Design Documents ==

=== Keystone (completed; use as a reference) ===

* http://specs.openstack.org/openstack/keystone-specs/specs/keystone/ongoing/policy-goals-and-roadmap.html
* https://bugs.launchpad.net/keystone/+bugs?field.status%3Alist=FIXRELEASED&field.tag=default-roles+system-scope&field.tags_combinator=ANY

=== Barbican ===

* https://wiki.openstack.org/wiki/Barbican/Policy

=== Nova ===

* https://specs.openstack.org/openstack/nova-specs/specs/ussuri/approved/policy-defaults-refresh.html

=== Neutron ===

none yet

=== Cinder ===

none yet

== Progress ==

TBD - each project may have its own tracking mechanism, to be linked here

== Reviews ==

https://review.opendev.org/#/q/is:open+topic:policy-popup

== References ==

* All about scopes: https://docs.openstack.org/keystone/latest/contributor/services.html#authorization-scopes
* Default roles and scopes: https://docs.openstack.org/keystone/latest/admin/service-api-protection.html

Consistent and Secure Default Policies Popup Team

2019-11-25T22:34:04Z

Colleen Murphy: /* Consistent and Secure Default Policies Popup Team */

== Problem Description ==

Existing policy defaults suffer from three major faults:

# the admin-ness problem: use of policy rules like 'is_admin' or hard-coded is-admin checks results in the admin-anywhere-admin-everywhere problem and drastically inhibits true multi-tenancy since by default customers cannot have admin rights on their own projects or domains
# insecure custom roles: many policy rules simply use "" as the rule, which means there is no rule: anyone can perform that action. This means creation of a custom role (say, "nova-autoscaler" requires editing every policy file across every service to block users with such a rule from performing actions unrelated to their role
# related to #2, no support for read-only roles: keystone now has a "reader" role that comes out of the box when keystone is bootstrapped, but it currently has very little value because of the use of empty rules in service policies: users with the "reader" role can still perform write actions on services if the policy rule for such an action is empty.

== Team Goal ==

The keystone project has migrated all of its default policies to 1) use oslo.policy's scope_types attribute, which allows the policy engine to understand "system scope" and distinguish between an admin role assignment on a project versus an admin role assignment on the entire system, 2) ensure all rules use one of the default roles (admin, member, and reader) which both ensures support for a read-only role and prevents custom roles from accidental over-permissiveness. Although the problems being solved are slightly different, the keystone team found it was easiest to migrate everything at once. The rest of the OpenStack services can use this migration as a template for securing their own policies.

== Popup Team Completion Criteria ==

This team will be disbanded after:

# The barbican, nova, neutron, and cinder projects have completed their policy migrations
# A document is published detailing any pitfalls, lessons learned, and best practices that other teams should be aware of
# A community goal is proposed and accepted by the TC

== Communication ==

Use topic:policy-popup in Gerrit.

Use subject tag [policy] for mailing list discussions.

Use #openstack-dev for synchronous discussions.

== Chairs ==

# Colleen Murphy <colleen@gazlene.net> (cmurphy) [Seeking a replacement]
# [Your name here!]

== Liaisons ==

* Barbican: Douglas Mendizábal (redrobot)
* Nova: Ghanshyam Mann (gmann)
* Neutron: Miguel Lavalle (mlavalle)
* Cinder: Brian Rosmaita (rosmaita)

== Members ==

* Mohammed Naser <mnaser@vexxhost.com>
* Douglas Mendizábal (IRC: redrobot) - Barbican - We're supere interested in getting this implemented for Barbican
* Ade Lee (ade_lee) - barbican
* Miguel Lavalle (mlavalle) - neutron
* Chandan Kumar (chandankumar/raukadah)<chkumar@redhat.com> - Help on Tempest and Patrole side
* Akihiro Motoki (amotoki) - horizon (horizon needs to support the new mechanism of policy definitions. It is different from server side support, so the team needs to explore its own way)
* Tobias Rydberg (tobberydberg)
* Erik McCormick <emccormick@cirrusseven.com> (emccormick)
* Tergel Munkhbat tergel@fibo.cloud
* Ghanshyam Mann (gmann): Nova, QA adopt testing for the new roles.
* Vishakha Agarwal (vishakha)- Keystone

== Team Design Documents ==

=== Keystone (completed; use as a reference) ===

* http://specs.openstack.org/openstack/keystone-specs/specs/keystone/ongoing/policy-goals-and-roadmap.html
* https://bugs.launchpad.net/keystone/+bugs?field.status%3Alist=FIXRELEASED&field.tag=default-roles+system-scope&field.tags_combinator=ANY

=== Barbican ===

* https://wiki.openstack.org/wiki/Barbican/Policy

=== Nova ===

* https://specs.openstack.org/openstack/nova-specs/specs/ussuri/approved/policy-defaults-refresh.html

=== Neutron ===

none yet

=== Cinder ===

none yet

== Progress ==

TBD - each project may have its own tracking mechanism, to be linked here

== Reviews ==

https://review.opendev.org/#/q/is:open+topic:policy-popup

== References ==

* All about scopes: https://docs.openstack.org/keystone/latest/contributor/services.html#authorization-scopes
* Default roles and scopes: https://docs.openstack.org/keystone/latest/admin/service-api-protection.html

Consistent and Secure Default Policies Popup Team

2019-11-25T22:33:44Z

Colleen Murphy: Consistent and Secure Default Policies Popup Team

= Consistent and Secure Default Policies Popup Team =

== Problem Description ==

Existing policy defaults suffer from three major faults:

# the admin-ness problem: use of policy rules like 'is_admin' or hard-coded is-admin checks results in the admin-anywhere-admin-everywhere problem and drastically inhibits true multi-tenancy since by default customers cannot have admin rights on their own projects or domains
# insecure custom roles: many policy rules simply use "" as the rule, which means there is no rule: anyone can perform that action. This means creation of a custom role (say, "nova-autoscaler" requires editing every policy file across every service to block users with such a rule from performing actions unrelated to their role
# related to #2, no support for read-only roles: keystone now has a "reader" role that comes out of the box when keystone is bootstrapped, but it currently has very little value because of the use of empty rules in service policies: users with the "reader" role can still perform write actions on services if the policy rule for such an action is empty.

== Team Goal ==

The keystone project has migrated all of its default policies to 1) use oslo.policy's scope_types attribute, which allows the policy engine to understand "system scope" and distinguish between an admin role assignment on a project versus an admin role assignment on the entire system, 2) ensure all rules use one of the default roles (admin, member, and reader) which both ensures support for a read-only role and prevents custom roles from accidental over-permissiveness. Although the problems being solved are slightly different, the keystone team found it was easiest to migrate everything at once. The rest of the OpenStack services can use this migration as a template for securing their own policies.

== Popup Team Completion Criteria ==

This team will be disbanded after:

# The barbican, nova, neutron, and cinder projects have completed their policy migrations
# A document is published detailing any pitfalls, lessons learned, and best practices that other teams should be aware of
# A community goal is proposed and accepted by the TC

== Communication ==

Use topic:policy-popup in Gerrit.

Use subject tag [policy] for mailing list discussions.

Use #openstack-dev for synchronous discussions.

== Chairs ==

# Colleen Murphy <colleen@gazlene.net> (cmurphy) [Seeking a replacement]
# [Your name here!]

== Liaisons ==

* Barbican: Douglas Mendizábal (redrobot)
* Nova: Ghanshyam Mann (gmann)
* Neutron: Miguel Lavalle (mlavalle)
* Cinder: Brian Rosmaita (rosmaita)

== Members ==

* Mohammed Naser <mnaser@vexxhost.com>
* Douglas Mendizábal (IRC: redrobot) - Barbican - We're supere interested in getting this implemented for Barbican
* Ade Lee (ade_lee) - barbican
* Miguel Lavalle (mlavalle) - neutron
* Chandan Kumar (chandankumar/raukadah)<chkumar@redhat.com> - Help on Tempest and Patrole side
* Akihiro Motoki (amotoki) - horizon (horizon needs to support the new mechanism of policy definitions. It is different from server side support, so the team needs to explore its own way)
* Tobias Rydberg (tobberydberg)
* Erik McCormick <emccormick@cirrusseven.com> (emccormick)
* Tergel Munkhbat tergel@fibo.cloud
* Ghanshyam Mann (gmann): Nova, QA adopt testing for the new roles.
* Vishakha Agarwal (vishakha)- Keystone

== Team Design Documents ==

=== Keystone (completed; use as a reference) ===

* http://specs.openstack.org/openstack/keystone-specs/specs/keystone/ongoing/policy-goals-and-roadmap.html
* https://bugs.launchpad.net/keystone/+bugs?field.status%3Alist=FIXRELEASED&field.tag=default-roles+system-scope&field.tags_combinator=ANY

=== Barbican ===

* https://wiki.openstack.org/wiki/Barbican/Policy

=== Nova ===

* https://specs.openstack.org/openstack/nova-specs/specs/ussuri/approved/policy-defaults-refresh.html

=== Neutron ===

none yet

=== Cinder ===

none yet

== Progress ==

TBD - each project may have its own tracking mechanism, to be linked here

== Reviews ==

https://review.opendev.org/#/q/is:open+topic:policy-popup

== References ==

* All about scopes: https://docs.openstack.org/keystone/latest/contributor/services.html#authorization-scopes
* Default roles and scopes: https://docs.openstack.org/keystone/latest/admin/service-api-protection.html

Forum/Shanghai2019

2019-09-09T22:32:52Z

Colleen Murphy: /* Etherpads from Teams and Working Groups */

== Etherpads ==
The grand list of all of the Shanghai 2019 [[Forum]] etherpads. Please add links to etherpads below!
(You might use the prior Forum entries for ideas: https://wiki.openstack.org/wiki/Forum/Berlin2018 or https://wiki.openstack.org/wiki/Forum/Denver2019)

At the Forum the entire OpenStack community (users and developers) gathers to brainstorm the requirements for the next release, gather feedback on the past version and have strategic discussions that go beyond just one release cycle. The Berlin Forum was the start of the planning phase for the '''U''' development cycle. Please prepare session ideas with feedback from the '''Train''' release in mind.

==List of Brainstorming Etherpads==

===Catch-alls===
If you want to post an idea, but aren't working with a specific team or working group, you can use these:
*[https://etherpad.openstack.org/p/PVG-UC-brainstorming UC Catch All ]

===Etherpads from Teams and Working Groups===
* Auto-scaling SIG: https://etherpad.openstack.org/p/PVG-auto-scaling-sig
* Cinder: https://etherpad.openstack.org/p/cinder-shanghai-forum-proposals
* First Contact SIG: https://etherpad.openstack.org/p/shanghai-forum-fc-sig-brainstorming
* Heat: https://etherpad.openstack.org/p/PVG-heat
* Manila: https://etherpad.openstack.org/p/manila-shanghai-forum-brainstorming
* Meta SIG: https://etherpad.openstack.org/p/PVG-meta-sig
* Neutron: https://etherpad.openstack.org/p/neutron-shanghai-forum-brainstorming
* Oslo: https://etherpad.openstack.org/p/oslo-shanghai-topics
* StoryBoard: https://etherpad.openstack.org/p/storyboard-shanghai-ptg-planning
* TC: https://etherpad.openstack.org/p/PVG-TC-brainstorming
* Keystone: https://etherpad.openstack.org/p/PVG-keystone-forum

===Etherpads from Pilot projects===
* StarlingX: https://etherpad.openstack.org/p/PVG-StarlingX-brainstorming

CrossProjectLiaisons

2019-05-21T16:56:14Z

Colleen Murphy: /* I18n */

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 far more projects consuming code from Oslo libraries than we have Oslo contributors. That means it is not possible for the Oslo team to keep track of how every project is using Oslo code. We are asking for one person from each project to serve as a liaison between the project and Oslo, to let us know when they are having issues with a library, and to assist with work like migrating off deprecated features.

* 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 || Moisés Guimarães de Medeiros || moguimar
|-
| Ceilometer || Julien Danjou || jd__
|-
| Cinder || Jay Bryant || jungleboyj
|-
| Cloudkitty || Christophe Sauthier || huats
|-
| Congress || Eric Kao || ekcs
|-
| Cue || Min Pae || sputnik13
|-
| Cyborg || Shaohe Feng || shaohe_feng
|-
| Designate || ||
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Abhishek Kekane|| akekane
|-
| Heat || Thomas Herve || therve
|-
| Horizon || Ivan Kolodyazhny || e0ne
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || ||
|-
| Keystone || ||
|-
| Manila || Thomas Bechtold || toabctl
|-
| Mistral || Dougal Matthews || d0ugal
|-
| Murano || Rong Zhu || zhurong
|-
| Neutron || Nate Johnston || njohnston
|-
| Nova || Stephen Finucane || stephenfin
|-
| [[Octavia]] || Michael Johnson || johnsom
|-
| Placement || Chris Dent || cdent
|-
| Qinling || Lingxian Kong || kong
|-
| 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
|-
| Cyborg || Howard Huang || zhipeng
|-
| Designate || Graham Hayes || mugsie
|-
| Documentation || Stephen Finucane || stephenfin
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Brian Rosmaita || rosmaita
|-
| Heat || Thomas Herve || therve
|-
| Horizon || Akihiro Motoki || amotoki
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || Dmitry Tantsur || dtantsur
|-
| Keystone || Kristi Nikolla || knikolla
|-
| Kolla || Mark Goddard || mgoddard
|-
| Magnum || Spyros Trigazis || strigazi
|-
| Manila || Tom Barron || tbarron
|-
| Mistral || Renat Akhmerov || rakhmerov
|-
| Murano || Felipe Monteiro || felipemonteiro
|-
| Neutron || Akihiro Motoki || amotoki
|-
| Nova || Sylvain Bauza, Matt Riedemann || bauzas, mriedem
|-
| Octavia || Michael Johnson || johnsom
|-
| OpenStackAnsible || Jean-Philippe Evrard || evrardjp
|-
| OpenStackClient || Doug Hellmann || dhellmann
|-
| Oslo || Doug Hellmann, Herve Beraud || dhellmann, hberaud
|-
| Packaging_Rpm || Dirk Mueller || dirk
|-
| Placement || Chris Dent || cdent
|-
| Puppet OpenStack || Alex Schultz || mwhahaha
|-
| Qinling || Lingxian Kong || lxkong
|-
| Rally || Andrey Kurilin || andreykurilin
|-
| Sahara || Telles Nobrega || tenobreg/tellesnobrega
|-
| Searchlight || Trinh Nguyen || dangtrinhnt
|-
| Senlin || Qiming Teng || Qiming
|-
| Solum || Devdatta Kulkarni || devkulkarni
|-
| Storlets || Kota Tsuyuzaki || kota_
|-
| Swift || John Dickinson || notmyname
|-
| Tricircle || Zhiyuan Cai || zhiyuan
|-
| TripleO || Emilien Macchi || EmilienM
|-
| Trove || Lingxian Kong || lxkong
|-
| Watcher || Canwei Li || licanwei
|-
| 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
|-
| Cyborg || Li Zhu || zhuli
|-
| Freezer || Guillermo Garcia || m3mo
|-
| Glance || Abhishek Kekane || abhishekk
|-
| Heat || Steve Baker || stevebaker
|-
| Horizon || Ivan Kolodyazhny || e0ne
|-
| Ironic || ||
|-
| Keystone || Vishakha Agarwal || vishakha
|-
| Manila || Dustin Schoenbrun || dustins
|-
| Murano || Rong Zhu || zhurong
|-
| Neutron || Slawek Kaplonski || slaweq
|-
| Nova || Matt Riedemann || mriedem
|-
| Oslo || Davanum Srinivas || dims
|-
| Qinling || Lingxian Kong || kong
|-
| 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
|-
| Cyborg || Yumeng Bao || Yumeng_Bao
|-
| Designate || Graham Hayes || mugsie
|-
| Freezer || Guillermo Garcia || m3mo
|-
| Heat || Rabi Mishra || ramishra
|-
| Horizon || Ivan Kolodyazhny || e0ne
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || Julia Kreger || TheJulia
|-
| Keystone || Vishakha Agarwal || vishakha
|-
| Kolla || Mark Goddard || mgoddard
|-
| Magnum || Spyros Trigazis || strigazi
|-
| Manila || Tom Barron || tbarron
|-
| Mistral || Dougal Matthews || d0ugal
|-
| Murano || Rong Zhu || zhurong
|-
| Neutron || Boden Russel || boden
|-
| Nova || Stephen Finucane || stephenfin
|-
| Octavia || Michael Johnson || johnsom
|-
| OpenStack-Ansible || Amy Marrich || spotz
|-
| Ops || Robert Starmer ||
|-
| Oslo || Stephen Finucane || stephenfin
|-
| Puppet OpenStack || Emilien Macchi || EmilienM
|-
| Qinling || Lingxian Kong || kong
|-
| Rally || Boris Pavlovic || boris-42
|-
| Sahara || Telles Nobrega and Luigi Toscano || tellesnobrega, tosky
|-
| 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
|-
| Cyborg || Howard Huang || zhipeng
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Erno Kuvaja || jokke_
|-
| Heat || Zane Bitter || zaneb
|-
| Horizon || Akihiro Motoki || amotoki
|-
| Ironic || Dmitry Tantsur || dtantsur
|-
| Keystone || Colleen Murphy || cmurphy
|-
| Manila || Goutham Pacha Ravi || gouthamr
|-
| Mistral || Dougal Matthews || d0ugal
|-
| Murano || Rong Zhu || zhurong
|-
| Neutron || Brian Haley || haleyb
|-
| Nova || Matt Riedemann || mriedem
|-
| Octavia || Carlos Goncalves || cgoncalves
|-
| Placement || Matt Riedemann || mriedem
|-
| Qinling || Lingxian Kong || kong
|-
| Sahara || Telles Nobrega || tellesnobrega
|-
| 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
|-
| Cyborg || Howard Huang || zhipeng
|-
| Freezer || Saad Zaher or Pierre Mathieu || szaher or slashme
|-
| Glance || Brian Rosmaita || rosmaita
|-
| Heat || Steve Hardy || shardy
|-
| Horizon || Ivan Kolodyazhny || e0ne
|-
| Ironic || ||
|-
| Keystone || Gage Hugo || gagehugo
|-
| Kolla || Mark Goddard || mgoddard
|-
| Manila || Tom Barron || tbarron
|-
| Murano || Rong Zhu || zhurong
|-
| Neutron || Miguel Lavalle || mlavalle
|-
| Nova || Michael Still || mikal
|-
| OpenStack-Ansible || Major Hayden || mhayden
|-
| Qinling || Lingxian Kong || kong
|-
| Sahara || Telles Nobrega || tellesnobrega
|-
| Searchlight || Trinh Nguyen || dangtrinhnt
|-
| Senlin || Qiming Teng || Qiming
|-
| Swift || ||
|-
| Trove || Manoj Kumar || kumarmn
|-
| Zaqar || Fei Long Wang || flwang
|-
|}

== API-SIG ==

The [[API_SIG|API-SIG]] 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-SIG 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-sig/liaisons.html API-SIG 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-sig/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 || Rong Zhu || zhurong
|-
| Sahara || Telles Nobrega || tellesnobrega
|}

== 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 || Erno Kuvaja, Brian Rosmaita || jokke_, rosmaita
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || Dmitry Tantsur || dtantsur
|-
| Kolla || Any Kolla Core Reviewer may ack an infra change on behalf of the PTL || mgoddard, jeffrey4l, egonzalez, spsurya, hrw, mandre are primary contacts
|-
| Neutron || Slawek Kaplonski, YAMAMOTO Takashi || slaweq, yamamoto
|-
| Documentation || Andreas Jaeger|| AJaeger

|-
| Trove || Manoj Kumar || kumarmn

|-
| Murano || Rong Zhu || zhurong

|-
| Sahara || Telles Nobrega and Luigi Toscano || tellesnobrega, tosky

|-
| 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 || Abhishek Kekane || akekane
|-
| Heat || ||
|-
| Horizon || Akihiro Motoki || amotoki
|-
| Ironic || ||
|-
| Keystone || Vishakha Agarwal || vishakha
|-
| 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 || ||
|-
| Watcher || Yumeng Bao || Yumeng
|-
| Zaqar || ||
|-
|}

== First Contact SIG ==

First Contact SIG aims to provide a place for new contributors to come for information and advice. This group will also analyze and document successful contribution models while seeking out and providing information to new members of the community. First Contact SIG project liaisons are important that they are connected with someone who can
get them up to speed on a project. The list of project liaisons are in [https://wiki.openstack.org/wiki/First_Contact_SIG First Contact SIG Wiki page].

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

CrossProjectLiaisons

2019-05-21T16:55:25Z

Colleen Murphy: /* Documentation */

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 far more projects consuming code from Oslo libraries than we have Oslo contributors. That means it is not possible for the Oslo team to keep track of how every project is using Oslo code. We are asking for one person from each project to serve as a liaison between the project and Oslo, to let us know when they are having issues with a library, and to assist with work like migrating off deprecated features.

* 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 || Moisés Guimarães de Medeiros || moguimar
|-
| Ceilometer || Julien Danjou || jd__
|-
| Cinder || Jay Bryant || jungleboyj
|-
| Cloudkitty || Christophe Sauthier || huats
|-
| Congress || Eric Kao || ekcs
|-
| Cue || Min Pae || sputnik13
|-
| Cyborg || Shaohe Feng || shaohe_feng
|-
| Designate || ||
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Abhishek Kekane|| akekane
|-
| Heat || Thomas Herve || therve
|-
| Horizon || Ivan Kolodyazhny || e0ne
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || ||
|-
| Keystone || ||
|-
| Manila || Thomas Bechtold || toabctl
|-
| Mistral || Dougal Matthews || d0ugal
|-
| Murano || Rong Zhu || zhurong
|-
| Neutron || Nate Johnston || njohnston
|-
| Nova || Stephen Finucane || stephenfin
|-
| [[Octavia]] || Michael Johnson || johnsom
|-
| Placement || Chris Dent || cdent
|-
| Qinling || Lingxian Kong || kong
|-
| 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
|-
| Cyborg || Howard Huang || zhipeng
|-
| Designate || Graham Hayes || mugsie
|-
| Documentation || Stephen Finucane || stephenfin
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Brian Rosmaita || rosmaita
|-
| Heat || Thomas Herve || therve
|-
| Horizon || Akihiro Motoki || amotoki
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || Dmitry Tantsur || dtantsur
|-
| Keystone || Kristi Nikolla || knikolla
|-
| Kolla || Mark Goddard || mgoddard
|-
| Magnum || Spyros Trigazis || strigazi
|-
| Manila || Tom Barron || tbarron
|-
| Mistral || Renat Akhmerov || rakhmerov
|-
| Murano || Felipe Monteiro || felipemonteiro
|-
| Neutron || Akihiro Motoki || amotoki
|-
| Nova || Sylvain Bauza, Matt Riedemann || bauzas, mriedem
|-
| Octavia || Michael Johnson || johnsom
|-
| OpenStackAnsible || Jean-Philippe Evrard || evrardjp
|-
| OpenStackClient || Doug Hellmann || dhellmann
|-
| Oslo || Doug Hellmann, Herve Beraud || dhellmann, hberaud
|-
| Packaging_Rpm || Dirk Mueller || dirk
|-
| Placement || Chris Dent || cdent
|-
| Puppet OpenStack || Alex Schultz || mwhahaha
|-
| Qinling || Lingxian Kong || lxkong
|-
| Rally || Andrey Kurilin || andreykurilin
|-
| Sahara || Telles Nobrega || tenobreg/tellesnobrega
|-
| Searchlight || Trinh Nguyen || dangtrinhnt
|-
| Senlin || Qiming Teng || Qiming
|-
| Solum || Devdatta Kulkarni || devkulkarni
|-
| Storlets || Kota Tsuyuzaki || kota_
|-
| Swift || John Dickinson || notmyname
|-
| Tricircle || Zhiyuan Cai || zhiyuan
|-
| TripleO || Emilien Macchi || EmilienM
|-
| Trove || Lingxian Kong || lxkong
|-
| Watcher || Canwei Li || licanwei
|-
| 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
|-
| Cyborg || Li Zhu || zhuli
|-
| Freezer || Guillermo Garcia || m3mo
|-
| Glance || Abhishek Kekane || abhishekk
|-
| Heat || Steve Baker || stevebaker
|-
| Horizon || Ivan Kolodyazhny || e0ne
|-
| Ironic || ||
|-
| Keystone || Vishakha Agarwal || vishakha
|-
| Manila || Dustin Schoenbrun || dustins
|-
| Murano || Rong Zhu || zhurong
|-
| Neutron || Slawek Kaplonski || slaweq
|-
| Nova || Matt Riedemann || mriedem
|-
| Oslo || Davanum Srinivas || dims
|-
| Qinling || Lingxian Kong || kong
|-
| 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
|-
| Cyborg || Yumeng Bao || Yumeng_Bao
|-
| Designate || Graham Hayes || mugsie
|-
| Freezer || Guillermo Garcia || m3mo
|-
| Heat || Rabi Mishra || ramishra
|-
| Horizon || Ivan Kolodyazhny || e0ne
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || Julia Kreger || TheJulia
|-
| Keystone || Vishakha Agarwal || vishakha
|-
| Kolla || Mark Goddard || mgoddard
|-
| Magnum || Spyros Trigazis || strigazi
|-
| Manila || Tom Barron || tbarron
|-
| Mistral || Dougal Matthews || d0ugal
|-
| Murano || Rong Zhu || zhurong
|-
| Neutron || Boden Russel || boden
|-
| Nova || Stephen Finucane || stephenfin
|-
| Octavia || Michael Johnson || johnsom
|-
| OpenStack-Ansible || Amy Marrich || spotz
|-
| Ops || Robert Starmer ||
|-
| Oslo || Stephen Finucane || stephenfin
|-
| Puppet OpenStack || Emilien Macchi || EmilienM
|-
| Qinling || Lingxian Kong || kong
|-
| Rally || Boris Pavlovic || boris-42
|-
| Sahara || Telles Nobrega and Luigi Toscano || tellesnobrega, tosky
|-
| 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
|-
| Cyborg || Howard Huang || zhipeng
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Erno Kuvaja || jokke_
|-
| Heat || Zane Bitter || zaneb
|-
| Horizon || Akihiro Motoki || amotoki
|-
| Ironic || Dmitry Tantsur || dtantsur
|-
| Keystone || Colleen Murphy || cmurphy
|-
| Manila || Goutham Pacha Ravi || gouthamr
|-
| Mistral || Dougal Matthews || d0ugal
|-
| Murano || Rong Zhu || zhurong
|-
| Neutron || Brian Haley || haleyb
|-
| Nova || Matt Riedemann || mriedem
|-
| Octavia || Carlos Goncalves || cgoncalves
|-
| Placement || Matt Riedemann || mriedem
|-
| Qinling || Lingxian Kong || kong
|-
| Sahara || Telles Nobrega || tellesnobrega
|-
| 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
|-
| Cyborg || Howard Huang || zhipeng
|-
| Freezer || Saad Zaher or Pierre Mathieu || szaher or slashme
|-
| Glance || Brian Rosmaita || rosmaita
|-
| Heat || Steve Hardy || shardy
|-
| Horizon || Ivan Kolodyazhny || e0ne
|-
| Ironic || ||
|-
| Keystone || Gage Hugo || gagehugo
|-
| Kolla || Mark Goddard || mgoddard
|-
| Manila || Tom Barron || tbarron
|-
| Murano || Rong Zhu || zhurong
|-
| Neutron || Miguel Lavalle || mlavalle
|-
| Nova || Michael Still || mikal
|-
| OpenStack-Ansible || Major Hayden || mhayden
|-
| Qinling || Lingxian Kong || kong
|-
| Sahara || Telles Nobrega || tellesnobrega
|-
| Searchlight || Trinh Nguyen || dangtrinhnt
|-
| Senlin || Qiming Teng || Qiming
|-
| Swift || ||
|-
| Trove || Manoj Kumar || kumarmn
|-
| Zaqar || Fei Long Wang || flwang
|-
|}

== API-SIG ==

The [[API_SIG|API-SIG]] 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-SIG 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-sig/liaisons.html API-SIG 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-sig/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 || Rong Zhu || zhurong
|-
| Sahara || Telles Nobrega || tellesnobrega
|}

== 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 || Erno Kuvaja, Brian Rosmaita || jokke_, rosmaita
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || Dmitry Tantsur || dtantsur
|-
| Kolla || Any Kolla Core Reviewer may ack an infra change on behalf of the PTL || mgoddard, jeffrey4l, egonzalez, spsurya, hrw, mandre are primary contacts
|-
| Neutron || Slawek Kaplonski, YAMAMOTO Takashi || slaweq, yamamoto
|-
| Documentation || Andreas Jaeger|| AJaeger

|-
| Trove || Manoj Kumar || kumarmn

|-
| Murano || Rong Zhu || zhurong

|-
| Sahara || Telles Nobrega and Luigi Toscano || tellesnobrega, tosky

|-
| 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 || Abhishek Kekane || akekane
|-
| 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 || ||
|-
| Watcher || Yumeng Bao || Yumeng
|-
| Zaqar || ||
|-
|}

== First Contact SIG ==

First Contact SIG aims to provide a place for new contributors to come for information and advice. This group will also analyze and document successful contribution models while seeking out and providing information to new members of the community. First Contact SIG project liaisons are important that they are connected with someone who can
get them up to speed on a project. The list of project liaisons are in [https://wiki.openstack.org/wiki/First_Contact_SIG First Contact SIG Wiki page].

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

CrossProjectLiaisons

2019-05-21T16:55:02Z

Colleen Murphy: /* QA */

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 far more projects consuming code from Oslo libraries than we have Oslo contributors. That means it is not possible for the Oslo team to keep track of how every project is using Oslo code. We are asking for one person from each project to serve as a liaison between the project and Oslo, to let us know when they are having issues with a library, and to assist with work like migrating off deprecated features.

* 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 || Moisés Guimarães de Medeiros || moguimar
|-
| Ceilometer || Julien Danjou || jd__
|-
| Cinder || Jay Bryant || jungleboyj
|-
| Cloudkitty || Christophe Sauthier || huats
|-
| Congress || Eric Kao || ekcs
|-
| Cue || Min Pae || sputnik13
|-
| Cyborg || Shaohe Feng || shaohe_feng
|-
| Designate || ||
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Abhishek Kekane|| akekane
|-
| Heat || Thomas Herve || therve
|-
| Horizon || Ivan Kolodyazhny || e0ne
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || ||
|-
| Keystone || ||
|-
| Manila || Thomas Bechtold || toabctl
|-
| Mistral || Dougal Matthews || d0ugal
|-
| Murano || Rong Zhu || zhurong
|-
| Neutron || Nate Johnston || njohnston
|-
| Nova || Stephen Finucane || stephenfin
|-
| [[Octavia]] || Michael Johnson || johnsom
|-
| Placement || Chris Dent || cdent
|-
| Qinling || Lingxian Kong || kong
|-
| 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
|-
| Cyborg || Howard Huang || zhipeng
|-
| Designate || Graham Hayes || mugsie
|-
| Documentation || Stephen Finucane || stephenfin
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Brian Rosmaita || rosmaita
|-
| Heat || Thomas Herve || therve
|-
| Horizon || Akihiro Motoki || amotoki
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || Dmitry Tantsur || dtantsur
|-
| Keystone || Kristi Nikolla || knikolla
|-
| Kolla || Mark Goddard || mgoddard
|-
| Magnum || Spyros Trigazis || strigazi
|-
| Manila || Tom Barron || tbarron
|-
| Mistral || Renat Akhmerov || rakhmerov
|-
| Murano || Felipe Monteiro || felipemonteiro
|-
| Neutron || Akihiro Motoki || amotoki
|-
| Nova || Sylvain Bauza, Matt Riedemann || bauzas, mriedem
|-
| Octavia || Michael Johnson || johnsom
|-
| OpenStackAnsible || Jean-Philippe Evrard || evrardjp
|-
| OpenStackClient || Doug Hellmann || dhellmann
|-
| Oslo || Doug Hellmann, Herve Beraud || dhellmann, hberaud
|-
| Packaging_Rpm || Dirk Mueller || dirk
|-
| Placement || Chris Dent || cdent
|-
| Puppet OpenStack || Alex Schultz || mwhahaha
|-
| Qinling || Lingxian Kong || lxkong
|-
| Rally || Andrey Kurilin || andreykurilin
|-
| Sahara || Telles Nobrega || tenobreg/tellesnobrega
|-
| Searchlight || Trinh Nguyen || dangtrinhnt
|-
| Senlin || Qiming Teng || Qiming
|-
| Solum || Devdatta Kulkarni || devkulkarni
|-
| Storlets || Kota Tsuyuzaki || kota_
|-
| Swift || John Dickinson || notmyname
|-
| Tricircle || Zhiyuan Cai || zhiyuan
|-
| TripleO || Emilien Macchi || EmilienM
|-
| Trove || Lingxian Kong || lxkong
|-
| Watcher || Canwei Li || licanwei
|-
| 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
|-
| Cyborg || Li Zhu || zhuli
|-
| Freezer || Guillermo Garcia || m3mo
|-
| Glance || Abhishek Kekane || abhishekk
|-
| Heat || Steve Baker || stevebaker
|-
| Horizon || Ivan Kolodyazhny || e0ne
|-
| Ironic || ||
|-
| Keystone || Vishakha Agarwal || vishakha
|-
| Manila || Dustin Schoenbrun || dustins
|-
| Murano || Rong Zhu || zhurong
|-
| Neutron || Slawek Kaplonski || slaweq
|-
| Nova || Matt Riedemann || mriedem
|-
| Oslo || Davanum Srinivas || dims
|-
| Qinling || Lingxian Kong || kong
|-
| 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
|-
| Cyborg || Yumeng Bao || Yumeng_Bao
|-
| Designate || Graham Hayes || mugsie
|-
| Freezer || Guillermo Garcia || m3mo
|-
| Heat || Rabi Mishra || ramishra
|-
| Horizon || Ivan Kolodyazhny || e0ne
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || Julia Kreger || TheJulia
|-
| Keystone || Lance Bragstad || lbragstad
|-
| Kolla || Mark Goddard || mgoddard
|-
| Magnum || Spyros Trigazis || strigazi
|-
| Manila || Tom Barron || tbarron
|-
| Mistral || Dougal Matthews || d0ugal
|-
| Murano || Rong Zhu || zhurong
|-
| Neutron || Boden Russel || boden
|-
| Nova || Stephen Finucane || stephenfin
|-
| Octavia || Michael Johnson || johnsom
|-
| OpenStack-Ansible || Amy Marrich || spotz
|-
| Ops || Robert Starmer ||
|-
| Oslo || Stephen Finucane || stephenfin
|-
| Puppet OpenStack || Emilien Macchi || EmilienM
|-
| Qinling || Lingxian Kong || kong
|-
| Rally || Boris Pavlovic || boris-42
|-
| Sahara || Telles Nobrega and Luigi Toscano || tellesnobrega, tosky
|-
| 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
|-
| Cyborg || Howard Huang || zhipeng
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Erno Kuvaja || jokke_
|-
| Heat || Zane Bitter || zaneb
|-
| Horizon || Akihiro Motoki || amotoki
|-
| Ironic || Dmitry Tantsur || dtantsur
|-
| Keystone || Colleen Murphy || cmurphy
|-
| Manila || Goutham Pacha Ravi || gouthamr
|-
| Mistral || Dougal Matthews || d0ugal
|-
| Murano || Rong Zhu || zhurong
|-
| Neutron || Brian Haley || haleyb
|-
| Nova || Matt Riedemann || mriedem
|-
| Octavia || Carlos Goncalves || cgoncalves
|-
| Placement || Matt Riedemann || mriedem
|-
| Qinling || Lingxian Kong || kong
|-
| Sahara || Telles Nobrega || tellesnobrega
|-
| 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
|-
| Cyborg || Howard Huang || zhipeng
|-
| Freezer || Saad Zaher or Pierre Mathieu || szaher or slashme
|-
| Glance || Brian Rosmaita || rosmaita
|-
| Heat || Steve Hardy || shardy
|-
| Horizon || Ivan Kolodyazhny || e0ne
|-
| Ironic || ||
|-
| Keystone || Gage Hugo || gagehugo
|-
| Kolla || Mark Goddard || mgoddard
|-
| Manila || Tom Barron || tbarron
|-
| Murano || Rong Zhu || zhurong
|-
| Neutron || Miguel Lavalle || mlavalle
|-
| Nova || Michael Still || mikal
|-
| OpenStack-Ansible || Major Hayden || mhayden
|-
| Qinling || Lingxian Kong || kong
|-
| Sahara || Telles Nobrega || tellesnobrega
|-
| Searchlight || Trinh Nguyen || dangtrinhnt
|-
| Senlin || Qiming Teng || Qiming
|-
| Swift || ||
|-
| Trove || Manoj Kumar || kumarmn
|-
| Zaqar || Fei Long Wang || flwang
|-
|}

== API-SIG ==

The [[API_SIG|API-SIG]] 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-SIG 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-sig/liaisons.html API-SIG 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-sig/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 || Rong Zhu || zhurong
|-
| Sahara || Telles Nobrega || tellesnobrega
|}

== 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 || Erno Kuvaja, Brian Rosmaita || jokke_, rosmaita
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || Dmitry Tantsur || dtantsur
|-
| Kolla || Any Kolla Core Reviewer may ack an infra change on behalf of the PTL || mgoddard, jeffrey4l, egonzalez, spsurya, hrw, mandre are primary contacts
|-
| Neutron || Slawek Kaplonski, YAMAMOTO Takashi || slaweq, yamamoto
|-
| Documentation || Andreas Jaeger|| AJaeger

|-
| Trove || Manoj Kumar || kumarmn

|-
| Murano || Rong Zhu || zhurong

|-
| Sahara || Telles Nobrega and Luigi Toscano || tellesnobrega, tosky

|-
| 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 || Abhishek Kekane || akekane
|-
| 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 || ||
|-
| Watcher || Yumeng Bao || Yumeng
|-
| Zaqar || ||
|-
|}

== First Contact SIG ==

First Contact SIG aims to provide a place for new contributors to come for information and advice. This group will also analyze and document successful contribution models while seeking out and providing information to new members of the community. First Contact SIG project liaisons are important that they are connected with someone who can
get them up to speed on a project. The list of project liaisons are in [https://wiki.openstack.org/wiki/First_Contact_SIG First Contact SIG Wiki page].

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

CrossProjectLiaisons

2019-05-21T16:54:15Z

Colleen Murphy: /* Oslo */

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 far more projects consuming code from Oslo libraries than we have Oslo contributors. That means it is not possible for the Oslo team to keep track of how every project is using Oslo code. We are asking for one person from each project to serve as a liaison between the project and Oslo, to let us know when they are having issues with a library, and to assist with work like migrating off deprecated features.

* 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 || Moisés Guimarães de Medeiros || moguimar
|-
| Ceilometer || Julien Danjou || jd__
|-
| Cinder || Jay Bryant || jungleboyj
|-
| Cloudkitty || Christophe Sauthier || huats
|-
| Congress || Eric Kao || ekcs
|-
| Cue || Min Pae || sputnik13
|-
| Cyborg || Shaohe Feng || shaohe_feng
|-
| Designate || ||
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Abhishek Kekane|| akekane
|-
| Heat || Thomas Herve || therve
|-
| Horizon || Ivan Kolodyazhny || e0ne
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || ||
|-
| Keystone || ||
|-
| Manila || Thomas Bechtold || toabctl
|-
| Mistral || Dougal Matthews || d0ugal
|-
| Murano || Rong Zhu || zhurong
|-
| Neutron || Nate Johnston || njohnston
|-
| Nova || Stephen Finucane || stephenfin
|-
| [[Octavia]] || Michael Johnson || johnsom
|-
| Placement || Chris Dent || cdent
|-
| Qinling || Lingxian Kong || kong
|-
| 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
|-
| Cyborg || Howard Huang || zhipeng
|-
| Designate || Graham Hayes || mugsie
|-
| Documentation || Stephen Finucane || stephenfin
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Brian Rosmaita || rosmaita
|-
| Heat || Thomas Herve || therve
|-
| Horizon || Akihiro Motoki || amotoki
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || Dmitry Tantsur || dtantsur
|-
| Keystone || Kristi Nikolla || knikolla
|-
| Kolla || Mark Goddard || mgoddard
|-
| Magnum || Spyros Trigazis || strigazi
|-
| Manila || Tom Barron || tbarron
|-
| Mistral || Renat Akhmerov || rakhmerov
|-
| Murano || Felipe Monteiro || felipemonteiro
|-
| Neutron || Akihiro Motoki || amotoki
|-
| Nova || Sylvain Bauza, Matt Riedemann || bauzas, mriedem
|-
| Octavia || Michael Johnson || johnsom
|-
| OpenStackAnsible || Jean-Philippe Evrard || evrardjp
|-
| OpenStackClient || Doug Hellmann || dhellmann
|-
| Oslo || Doug Hellmann, Herve Beraud || dhellmann, hberaud
|-
| Packaging_Rpm || Dirk Mueller || dirk
|-
| Placement || Chris Dent || cdent
|-
| Puppet OpenStack || Alex Schultz || mwhahaha
|-
| Qinling || Lingxian Kong || lxkong
|-
| Rally || Andrey Kurilin || andreykurilin
|-
| Sahara || Telles Nobrega || tenobreg/tellesnobrega
|-
| Searchlight || Trinh Nguyen || dangtrinhnt
|-
| Senlin || Qiming Teng || Qiming
|-
| Solum || Devdatta Kulkarni || devkulkarni
|-
| Storlets || Kota Tsuyuzaki || kota_
|-
| Swift || John Dickinson || notmyname
|-
| Tricircle || Zhiyuan Cai || zhiyuan
|-
| TripleO || Emilien Macchi || EmilienM
|-
| Trove || Lingxian Kong || lxkong
|-
| Watcher || Canwei Li || licanwei
|-
| 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
|-
| Cyborg || Li Zhu || zhuli
|-
| Freezer || Guillermo Garcia || m3mo
|-
| Glance || Abhishek Kekane || abhishekk
|-
| Heat || Steve Baker || stevebaker
|-
| Horizon || Ivan Kolodyazhny || e0ne
|-
| Ironic || ||
|-
| Keystone || Rodrigo Duarte || rodrigods
|-
| Manila || Dustin Schoenbrun || dustins
|-
| Murano || Rong Zhu || zhurong
|-
| Neutron || Slawek Kaplonski || slaweq
|-
| Nova || Matt Riedemann || mriedem
|-
| Oslo || Davanum Srinivas || dims
|-
| Qinling || Lingxian Kong || kong
|-
| 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
|-
| Cyborg || Yumeng Bao || Yumeng_Bao
|-
| Designate || Graham Hayes || mugsie
|-
| Freezer || Guillermo Garcia || m3mo
|-
| Heat || Rabi Mishra || ramishra
|-
| Horizon || Ivan Kolodyazhny || e0ne
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || Julia Kreger || TheJulia
|-
| Keystone || Lance Bragstad || lbragstad
|-
| Kolla || Mark Goddard || mgoddard
|-
| Magnum || Spyros Trigazis || strigazi
|-
| Manila || Tom Barron || tbarron
|-
| Mistral || Dougal Matthews || d0ugal
|-
| Murano || Rong Zhu || zhurong
|-
| Neutron || Boden Russel || boden
|-
| Nova || Stephen Finucane || stephenfin
|-
| Octavia || Michael Johnson || johnsom
|-
| OpenStack-Ansible || Amy Marrich || spotz
|-
| Ops || Robert Starmer ||
|-
| Oslo || Stephen Finucane || stephenfin
|-
| Puppet OpenStack || Emilien Macchi || EmilienM
|-
| Qinling || Lingxian Kong || kong
|-
| Rally || Boris Pavlovic || boris-42
|-
| Sahara || Telles Nobrega and Luigi Toscano || tellesnobrega, tosky
|-
| 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
|-
| Cyborg || Howard Huang || zhipeng
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Erno Kuvaja || jokke_
|-
| Heat || Zane Bitter || zaneb
|-
| Horizon || Akihiro Motoki || amotoki
|-
| Ironic || Dmitry Tantsur || dtantsur
|-
| Keystone || Colleen Murphy || cmurphy
|-
| Manila || Goutham Pacha Ravi || gouthamr
|-
| Mistral || Dougal Matthews || d0ugal
|-
| Murano || Rong Zhu || zhurong
|-
| Neutron || Brian Haley || haleyb
|-
| Nova || Matt Riedemann || mriedem
|-
| Octavia || Carlos Goncalves || cgoncalves
|-
| Placement || Matt Riedemann || mriedem
|-
| Qinling || Lingxian Kong || kong
|-
| Sahara || Telles Nobrega || tellesnobrega
|-
| 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
|-
| Cyborg || Howard Huang || zhipeng
|-
| Freezer || Saad Zaher or Pierre Mathieu || szaher or slashme
|-
| Glance || Brian Rosmaita || rosmaita
|-
| Heat || Steve Hardy || shardy
|-
| Horizon || Ivan Kolodyazhny || e0ne
|-
| Ironic || ||
|-
| Keystone || Gage Hugo || gagehugo
|-
| Kolla || Mark Goddard || mgoddard
|-
| Manila || Tom Barron || tbarron
|-
| Murano || Rong Zhu || zhurong
|-
| Neutron || Miguel Lavalle || mlavalle
|-
| Nova || Michael Still || mikal
|-
| OpenStack-Ansible || Major Hayden || mhayden
|-
| Qinling || Lingxian Kong || kong
|-
| Sahara || Telles Nobrega || tellesnobrega
|-
| Searchlight || Trinh Nguyen || dangtrinhnt
|-
| Senlin || Qiming Teng || Qiming
|-
| Swift || ||
|-
| Trove || Manoj Kumar || kumarmn
|-
| Zaqar || Fei Long Wang || flwang
|-
|}

== API-SIG ==

The [[API_SIG|API-SIG]] 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-SIG 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-sig/liaisons.html API-SIG 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-sig/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 || Rong Zhu || zhurong
|-
| Sahara || Telles Nobrega || tellesnobrega
|}

== 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 || Erno Kuvaja, Brian Rosmaita || jokke_, rosmaita
|-
| I18n || Frank Kloeker || eumel8
|-
| Ironic || Dmitry Tantsur || dtantsur
|-
| Kolla || Any Kolla Core Reviewer may ack an infra change on behalf of the PTL || mgoddard, jeffrey4l, egonzalez, spsurya, hrw, mandre are primary contacts
|-
| Neutron || Slawek Kaplonski, YAMAMOTO Takashi || slaweq, yamamoto
|-
| Documentation || Andreas Jaeger|| AJaeger

|-
| Trove || Manoj Kumar || kumarmn

|-
| Murano || Rong Zhu || zhurong

|-
| Sahara || Telles Nobrega and Luigi Toscano || tellesnobrega, tosky

|-
| 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 || Abhishek Kekane || akekane
|-
| 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 || ||
|-
| Watcher || Yumeng Bao || Yumeng
|-
| Zaqar || ||
|-
|}

== First Contact SIG ==

First Contact SIG aims to provide a place for new contributors to come for information and advice. This group will also analyze and document successful contribution models while seeking out and providing information to new members of the community. First Contact SIG project liaisons are important that they are connected with someone who can
get them up to speed on a project. The list of project liaisons are in [https://wiki.openstack.org/wiki/First_Contact_SIG First Contact SIG Wiki page].

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

First Contact SIG

2019-05-13T18:35:43Z

Colleen Murphy: /* Project Liaisons */

==First Contact SIG==

'''Our Mission'''

To provide a place for new contributors to come for information and advice. This group will also analyze and document successful contribution models while seeking out and providing information to new members of the community.

'''Chairs'''
* Kendall Nelson (diablo_rojo) UTC -7

'''Members'''
* Zhipeng Huang (zhipeng) UTC+8
* Amy Marrich (spotz) UTC-6
* Colleen Murphy (cmurphy) UTC+1
* Ildikó Váncsa (ildikov) UTC+1 (UTC+2 with daylight saving)
* Jay Bryant (jungleboyj) UTC-6
* Ghanshyam Mann (gmann) UTC+9
* Matt Oliver (mattolverau) UTC+10 (UTC+11 with daylight saving)
* Gergely Csatari (csatari) UTC+1 (UTC+2 with daylight saving)
* Surya Prakash Singh (spsurya) UTC+9

===Helpful Resources===
* [https://www.openstack.org/community/ Contributor Portal]
* [[Mentoring]]
* [[Outreachy]]

===Project Liaisons===

By default, the liaison will be the PTL. More than one liaison covering different TZ is recommended.

{| class="wikitable sortable"
! Name
! IRC
! Email
! Timezone
! Project
|-
| Masahito Muroi
| masahito
| muroi.masahito@lab.ntt.co.jp
|
| Blazar
|-
| Samuel Cassiba
| scas
| samuel@cassi.ba
| UTC-7
| [[Chef|Chef OpenStack]]
|-
| Jay Bryant
| jungleboyj
| jungleboyj@gmail.com
| UTC-6
| [[Cinder|Cinder]]
|-
| Ivan Kolodyazhny
| e0ne
| e0ne@e0ne.info
| UTC+3
| [[Cinder|Cinder]]
|-
| Luka Peschke
| peschk_l
| luka.peschke@objectif-libre.com
| CEST (UTC+2)
| Cloudkitty
|-
| Eric Kao
| ekcs
| ekcs.openstack@gmail.com
| UTC-8
| [[Congress|Congress]]
|-
| Ivan Kolodyazhny
| e0ne
| e0ne@e0ne.info
| UTC+3
| [[Horizon|Horizon]]
|-
| Howard Huang
| zhipeng
| zhipengh512@gmail.com
| UTC+8
| [[Cyborg/FirstContact|Cyborg]]
|-
| Graham Hayes
| mugsie
| gr@ham.ie
| UTC +1
| Designate
|-
| Petr Kovar
| pkovar
| pkovar@redhat.com
| UTC +1
| Documentation
|-
| Andrey Pavlov
| andrey-mp
| andrey.mp@gmail.com
|
| ec2-API
|-
| Saad Zaher
| szaher
| eng.szaher@gmail.com
|
| Freezer
|-
| Erno Kuvaja
| jokke_
| jokke@usr.fi
|
| Glance
|-
| Rico Lin
| ricolin
| rico.lin.guanyu@gmail.com
| UTC+8
| [[Heat|Heat]]
|-
| Frank Kloeker
| eumel8
| f.kloeker@telekom.de
| UTC+1
| I18n
|-
| Clark Boylan
| clarkb
| clark.boylan@gmail.com
| UTC+8
| Infrastructure
|-
| Julia Kreger
| TheJulia
| juliaashleykreger@gmail.com
| UTC+8
| Ironic
|-
| Ying Chen
| chenying
| ying.chen@huawei.com
|
| Karbor
|-
| Mark Goddard
| mgoddard
| mark@stackhpc.com
| UTC
| Kayobe
|-
| Colleen Murphy
| cmurphy
| colleen@gazlene.net
| UTC-7
| Keystone
|-
| Sam Yaple
| SamYaple
| sam+git@yaple.net
|
| LOCI
|-
| Spyros Trigazis
| strigazi
| spyridon.trigazis@cern.ch
|
| Magnum
|-
| Sampath Priyankara
| samP
| sam47priya@gmail.com
|
| Masakari
|-
| Cristiano Bellucci
| cbellucci
| Cristiano.bellucci@est.fujitsu.com
| UTC+1
| Monasca
|-
| Rong Zhu
| zhurong
| aaronzhu1121@gmail.com
| UTC+8
| Murano
|-
| Miguel Lavalle
| mlavalle
| miguel.lavalle@huawei.com
| UTC-6
| [[Neutron|Neutron]]
|-
| Slawek Kaplonski
| slaweq
| slawek@kaplonski.pl
| UTC+1
| [[Neutron|Neutron]]
|-
| Eric Fried
| efried
| openstack@fried.cc
| UTC-6
| Nova
|-
| Alex Xu
| alex_xu
| hejie.xu@intel.com
| UTC+8
| Nova
|-
| Michael Johnson
| johnsom
| johnsomor@gmail.com
| UTC-8
| [[Octavia|Octavia]]
|-
| James Page
| jamespage
| james.page@ubuntu.com
|
| OpenStack Charms
|-
| Jean-Philippe Evrard
| evrardjp
| jean-philippe@evrard.me
| UTC+2
| OpenStack-Ansible
|-
| Matt McEuen
| mattmceuen
| matt.mceuen@att.com
| UTC-6
| OpenStack-Helm
|-
| Chason Chan (chenxing)
| chason
| chason.chan@foxmail.com
| UTC+8
| OpenStack-Manuals
|-
| Dean Troyer
| dtroyer
| dtroyer@gmail.com
|
| OpenStackClient
|-
| Ben Nemec
| bnemec
| bnemec@redhat.com
| UTC-6
| Oslo
|-
| Javier Peña
| jpena
| jpena@redhat.com
|
| Packaging-rpm
|-
| Ed Leafe
| edleafe
| ed@leafe.com
| UTC-6
| Placement
|-
| Matthew Edmonds
| edmondsw
| edmondsw@us.ibm.com
| UTC-5
| PowerVMStackers
|-
| Ghanshyam Mann
| gmann
| gmann@ghanshyammann.com
| UTC-5
| [[QA|QA]]
|-
| Andrey Kurilin
| andreykurilin
| andr.kurilin@gmail.com
|
| Rally
|-
| Chris Hoge
| hogepodge
| chris@openstack.org
|
| Refstack
|-
| Sean McGinnis
| smcginnis
| sean.mcginnis@huawei.com
| UTC-6
| Release Management
|-
| Matthew Thode
| prometheanfire
| mthode@mthode.org
|
| Requirements
|-
| Telles Mota Vidal Nobrega
| tellesnobrega
| tenobrebrega@redhat.com
|
| Sahara
|-
| Trinh Nguyen
| dangtrinhnt
| dangtrinhnt@gmail.com
| UTC+9
| [https://wiki.openstack.org/wiki/Searchlight Searchlight]
|-
| Duc Truong
| dtruong
| duc.openstack@gmail.com
| UTC-8
| [[Senlin|Senlin]]
|-
| Rong Zhu
| zhurong
| aaronzhu1121@gmail.com
| UTC+8
| Solum
|-
| Tony Breeds
| tonyb
| tony@bakeyournoodle.com
| UTC +10
| Stable Branch Maintenance
|-
| Kota Tsuyuzaki
| kota_
| tsuyuzaki@lab.ntt.co.jp
|
| Storlets
|-
| Matt Oliver
| mattolverau
| matt@oliver.net.au
| UTC+10
| Swift
|-
| John Dickinson
| notmyname
| me@not.mn
| UTC-8
| Swift
|-
| Yong Sheng Gong
| gongysh
| gong.yongsheng@99cloud.net
|
| Tacker
|-
| Trinh Nguyen
| dangtrinhnt
| dangtrinhnt@gmail.com
|
| Telemetry
|-
| Zhiyuan Cai
| zhiyuan
| luckyvega.g@gmail.com
|
| Tricircle
|-
| Alex Schultz
| mwhahaha
| aschultz@redhat.com
|
| TripleO
|-
| Lingxian Kong
| lxkong
| anlin.kong@gmail.com
| UTC+12
| Trove
|-
| Alexander Chadin
| alexchadin
| a.chadin@servionica.ru
| UTC+3
| Watcher
|-
| Claudiu Belu
| claudiub
| cbelu@cloudbasesolutions.com
|
| Winstackers
|-
| Wang Hao
| wanghao
| szmatch1986@gmail.com
|
| Zaqar
|-
| Hongbin Lu
| hongbin
| hongbin.lu@huawei.com
| UTC-5
| Zun
|-
| Victoria Martinez de la Cruz
| vkmc
| victoria@redhat.com
| UTC-3
| Manila
|-
| Dougal Matthews
| d0ugal
| dougal@redhat.com
| UTC+0
| Mistral
|-
| Renat Akhmerov
| rakhmerov
| renat.akhmerov@nokia.com
| UTC+7
| Mistral
|-
| Omer Anson
| oanson
| omer.anson@toganetworks.com
| UTC+2
| [[Dragonflow|DragonFlow]]
|-
| Surya Prakash Singh
| spsurya
| singh.surya64mnnit@gmail.com
| UTC+9
| [[Kolla|Kolla]]
|-
| Daniel Mellado
| dmellado
| dmellado@redhat.com
| UTC+1
| [[Kuryr|Kuryr]]
|-
| Irena Berezovsky
| irenab
| Irena.berezovsky@toganetworks.com
| UTC+2
| [[Kuryr|Kuryr]]
|-
| Mohammed Naser
| mnaser
| mnaser@vexxhost.com
| UTC-5
| Puppet OpenStack
|-
| Ghanshyam Mann
| gmann
| gmann@ghanshyammann.com
| UTC-5
| [[Nova|Nova]]
|-
| Dharmendra Kushwaha
| dkushwaha
| dharmendra.kushwaha@india.nec.com
| UTC+5:30
| [[Tacker|Tacker]]
|-
| Jeffrey Zhang
| Jeffrey4l
| zhang.lei.fly@gmail.com
| UTC+8
| [[Kolla|Kolla]]
|-
|Canwei Li
| licanwei
| li.canwei2@zte.com.cn
| UTC+8
| [[Watcher|Watcher]]
|-
|Ade Lee
| alee
| alee@redhat.com
| UTC-4
| [[Barbican|Barbican]]
|-
|Lingxian Kong
| lxkong
| anlin.kong@gmail.com
| UTC+12
| [[Qinling|Qinling]]
|-
|Ifat Afek
| ifat_afek
| ifat.afek@nokia.com
| UTC+3
| [[Vitrage|Vitrage]]
|-
| Eduardo Gonzalez Gutierrez
| egonzalez
| dabarren@gmail.com
| UTC+1
| [[Kolla|Kolla]]
|-
| Mark Goddard
| mgoddard
| mark@stackhpc.com
| UTC
| [[Kolla|Kolla]]
|}

===Meeting Agenda===
The First Contact SIG team holds public weekly meeting:

* Channel: <code><nowiki>#openstack-upstream-institute</nowiki></code>
* Time: biweekly-odd on Wednesday at 0100 UTC.
* For Chair person: Start this meeting using: #startmeeting fc_sig
* The meeting minutes of previous meetings can be found here: [http://eavesdrop.openstack.org/meetings/fc_sig/ meeting minutes on eavesdrop]

'''Ping list:''' gmann, mattoliverau, cmurphy, tonyb, spotz

Standing Items:
* Announcements
** Update UTC offsets
* New Contributor Patches
** [https://review.openstack.org/#/q/reviewedby:%22Welcome%252C+new+contributor!+(10068)%22+is:open+-project:+openstack-dev/sandbox+AND+-project:openstack-dev/ci-sandbox Unmerged Patches Not in the sandbox or ci-sandbox]
** [https://review.openstack.org/#/q/reviewedby:%22Welcome%252C+new+contributor!+(10068)%22 All Changes]
** https://etherpad.openstack.org/p/FC_SIG_patch_checkup
** New Contributor the Month
* Ask.openstack.org Contribution Questions
** [https://ask.openstack.org/en/questions/scope:all/sort:activity-desc/tags:contribution/page:1/ 'Contribution' Tag]
**[https://ask.openstack.org/en/questions/scope:all/sort:activity-desc/tags:contributor/page:1/ 'Contributor' Tag]
** [https://ask.openstack.org/en/questions/scope:all/sort:activity-desc/tags:community/page:1/ 'Community' Tag]
** [https://ask.openstack.org/en/questions/scope:all/sort:activity-desc/tags:developer/page:1/ 'Developer' Tag']
** [https://ask.openstack.org/en/questions/scope:all/sort:activity-desc/tags:development/page:1/ 'Development' Tag]
** [https://ask.openstack.org/en/questions/tags:gettingstarted/ 'Getting Started' Tag]
** [https://ask.openstack.org/en/questions/tags:basics/ 'basics' Tag]
** [https://ask.openstack.org/en/questions/tags:beginner/ 'beginner' Tag]
** [https://ask.openstack.org/en/questions/tags:newbie/ 'newbie' Tag]
** [https://ask.openstack.org/en/questions/tags:noob/ 'noob' Tag]
** [https://ask.openstack.org/en/questions/tags:training/ 'training' Tag]
** [https://etherpad.openstack.org/p/ask.o.o-contribution Etherpad for Seeding Ask.O.O]

Other Items:
* Sandbox Bot
** http://lists.openstack.org/pipermail/openstack-discuss/2019-February/002291.html
** https://review.openstack.org/#/c/636466/1
* Summit + Forum Planning
** [https://www.openstack.org/summit/denver-2019/summit-schedule/events/23740/first-contact-sig-meet-and-greet FC SIG Meet and Greet]
** [https://www.openstack.org/summit/denver-2019/summit-schedule/events/23659/welcoming-new-contributors-state-of-the-union-and-deduplication-of-efforts Deduplication of Efforts]
* Project Liaisons
** Need to email openstack-discuss list to make sure the list is up to date with new PTLs
* People to Reach Out To
** [https://ethercalc.openstack.org/fc-sig-contact-list Pretty Ethercalc]

Forum/Denver2019

2019-04-10T16:06:59Z

Colleen Murphy: /* Monday April 29 */

== Etherpads ==
The grand list of all of the Denver 2019 [[Forum]] etherpads. Please add links to etherpads below!
(You might use the prior Forum entries for ideas: https://wiki.openstack.org/wiki/Forum/Berlin2018 )

At the Forum the entire OpenStack community (users and developers) gathers to brainstorm the requirements for the next release, gather feedback on the past version and have strategic discussions that go beyond just one release cycle. The Berlin Forum was the start of the planning phase for the '''T''' development cycle. Please prepare session ideas with feedback from the '''Stein''' release in mind.

=== Monday April 29 ===
[11:10-11:50] [https://etherpad.openstack.org/p/DEN-keystone-forum-sessions-app-creds Keystone Application Credentials: Status and Planning]

[12:00-12:40] [https://etherpad.openstack.org/p/DEN-keystone-forum-sessions-operator-feedback Keystone Operator Feedback]

[15:50-16:30] [https://etherpad.openstack.org/p/storyboard-pain-points Ibprouphen for Your StoryBoard Pain Points]

=== Tuesday April 30 ===
[16:20-17:00] [https://etherpad.openstack.org/p/new-contribs-state-and-deduplication Welcoming New Contributors State of the Union and Deduplication of Efforts]

[1710-1750] [https://etherpad.openstack.org/p/DEN-ops-war-stories-LT Ops War Stories/Architecture Show and Tell Lightning Talks]

=== Wednesday May 1 ===
[1340-1240] [https://etherpad.openstack.org/p/DEN-osc-compute-api-gaps Closing compute API feature gaps in the openstack CLI]

==List of Brainstorming Etherpads==

===Catch-alls===
If you want to post an idea, but aren't working with a specific team or working group, you can use these:
* [https://etherpad.openstack.org/p/DEN-Train-TC-brainstorming Technical Committee Catch-all]
* [https://etherpad.openstack.org/p/DEN-Train-UC-brainstorming User Committee Catch-all]

===Etherpads from Teams and Working Groups===
* [https://etherpad.openstack.org/p/DEN-auto-scaling-SIG Auto scaling SIG]
* [https://etherpad.openstack.org/p/DEN-Train-EWG-brainstorming Enterprise Working Group (EWG)]
* [https://etherpad.openstack.org/p/Denver-2019-Forum-DCN-Brainstorming DCN]
* [https://etherpad.openstack.org/p/DEN-fenix-forum-brainstorming Fenix]
* [https://etherpad.openstack.org/p/FC_SIG_Denver_forum_topics First Contact SIG]
* [https://etherpad.openstack.org/p/DEN-train-ironic-brainstorming Ironic]
* [https://etherpad.openstack.org/p/kayobe-train-forum Kayobe]
* [https://etherpad.openstack.org/p/DEN-keystone-forum-sessions Keystone]
* [https://etherpad.openstack.org/p/DEN-train-forum-manila-brainstorming Manila]
* [https://etherpad.openstack.org/p/DEN-train-nova-brainstorming Nova]
* [https://etherpad.openstack.org/p/edge-wg-forum-preparation-denver-2019 OSF Edge Computing Group]
* [https://etherpad.openstack.org/p/oslo-train-topics Oslo]
* [https://etherpad.openstack.org/p/DEN-Train-PublicCloudWG-brainstorming Public Cloud WG]
* [https://etherpad.openstack.org/p/DEN-train-forum-qa-brainstorming QA]
* [https://etherpad.openstack.org/p/DEN-self-healing-SIG Self healing SIG]
* [https://etherpad.openstack.org/p/SB_train_forum_brainstorming StoryBoard]
* [https://etherpad.openstack.org/p/DEN-Train-TC-brainstorming Technical Committee]
* [https://etherpad.openstack.org/p/tripleo-train-topics TripleO]

===Etherpads from Pilot projects===
* [https://etherpad.openstack.org/p/stx-forum-preparation-denver-2019 StarlingX]

Forum/Denver2019

2019-04-10T16:06:11Z

Colleen Murphy: /* Monday April 29 */

== Etherpads ==
The grand list of all of the Denver 2019 [[Forum]] etherpads. Please add links to etherpads below!
(You might use the prior Forum entries for ideas: https://wiki.openstack.org/wiki/Forum/Berlin2018 )

At the Forum the entire OpenStack community (users and developers) gathers to brainstorm the requirements for the next release, gather feedback on the past version and have strategic discussions that go beyond just one release cycle. The Berlin Forum was the start of the planning phase for the '''T''' development cycle. Please prepare session ideas with feedback from the '''Stein''' release in mind.

=== Monday April 29 ===
[11:10-11:50] [https://etherpad.openstack.org/p/DEN-keystone-forum-sessions-app-creds Keystone Application Credentials: Status and Planning]
[12:00-12:40] [https://etherpad.openstack.org/p/DEN-keystone-forum-sessions-operator-feedback Keystone Operator Feedback]
[15:50-16:30] [https://etherpad.openstack.org/p/storyboard-pain-points Ibprouphen for Your StoryBoard Pain Points]

=== Tuesday April 30 ===
[16:20-17:00] [https://etherpad.openstack.org/p/new-contribs-state-and-deduplication Welcoming New Contributors State of the Union and Deduplication of Efforts]

[1710-1750] [https://etherpad.openstack.org/p/DEN-ops-war-stories-LT Ops War Stories/Architecture Show and Tell Lightning Talks]

=== Wednesday May 1 ===
[1340-1240] [https://etherpad.openstack.org/p/DEN-osc-compute-api-gaps Closing compute API feature gaps in the openstack CLI]

==List of Brainstorming Etherpads==

===Catch-alls===
If you want to post an idea, but aren't working with a specific team or working group, you can use these:
* [https://etherpad.openstack.org/p/DEN-Train-TC-brainstorming Technical Committee Catch-all]
* [https://etherpad.openstack.org/p/DEN-Train-UC-brainstorming User Committee Catch-all]

===Etherpads from Teams and Working Groups===
* [https://etherpad.openstack.org/p/DEN-auto-scaling-SIG Auto scaling SIG]
* [https://etherpad.openstack.org/p/DEN-Train-EWG-brainstorming Enterprise Working Group (EWG)]
* [https://etherpad.openstack.org/p/Denver-2019-Forum-DCN-Brainstorming DCN]
* [https://etherpad.openstack.org/p/DEN-fenix-forum-brainstorming Fenix]
* [https://etherpad.openstack.org/p/FC_SIG_Denver_forum_topics First Contact SIG]
* [https://etherpad.openstack.org/p/DEN-train-ironic-brainstorming Ironic]
* [https://etherpad.openstack.org/p/kayobe-train-forum Kayobe]
* [https://etherpad.openstack.org/p/DEN-keystone-forum-sessions Keystone]
* [https://etherpad.openstack.org/p/DEN-train-forum-manila-brainstorming Manila]
* [https://etherpad.openstack.org/p/DEN-train-nova-brainstorming Nova]
* [https://etherpad.openstack.org/p/edge-wg-forum-preparation-denver-2019 OSF Edge Computing Group]
* [https://etherpad.openstack.org/p/oslo-train-topics Oslo]
* [https://etherpad.openstack.org/p/DEN-Train-PublicCloudWG-brainstorming Public Cloud WG]
* [https://etherpad.openstack.org/p/DEN-train-forum-qa-brainstorming QA]
* [https://etherpad.openstack.org/p/DEN-self-healing-SIG Self healing SIG]
* [https://etherpad.openstack.org/p/SB_train_forum_brainstorming StoryBoard]
* [https://etherpad.openstack.org/p/DEN-Train-TC-brainstorming Technical Committee]
* [https://etherpad.openstack.org/p/tripleo-train-topics TripleO]

===Etherpads from Pilot projects===
* [https://etherpad.openstack.org/p/stx-forum-preparation-denver-2019 StarlingX]

PTG/Train/Etherpads

2019-03-29T15:01:33Z

Colleen Murphy:

__NOTOC__

This is the list of etherpads for the Projects Team Gathering for the Train release in Denver, 2019. Each team can organize the content on their allocated day(s) in the way that seems to most appropriate to them. We suspect most teams will avoid strict timeboxed slots and will use etherpads to list topics to cover. This page lists those etherpads for easy reference.

For more details on the event, see the [https://www.openstack.org/ptg/ event website].

For what's happening '''right now''' (during the event), see the [http://ptg.openstack.org/ptg.html ptgbot page].

'''Projects:'''
* Cyborg - https://etherpad.openstack.org/p/cyborg-ptg-train
* Heat - https://etherpad.openstack.org/p/DEN-Train-Heat
* Horizon - https://etherpad.openstack.org/p/horizon-train-ptg
* Keystone - https://etherpad.openstack.org/p/keystone-train-ptg
* Nova - https://etherpad.openstack.org/p/nova-ptg-train
* Octavia - https://etherpad.openstack.org/p/octavia-train-ptg
* Placement - https://etherpad.openstack.org/p/placement-ptg-train
* Magnum - https://etherpad.openstack.org/p/magnum-train-ptg
* Manila - Planning: https://etherpad.openstack.org/p/manila-denver-train-ptg-planning | Minutes/Proceedings: https://etherpad.openstack.org/p/manila-ptg-train
* Monasca - https://etherpad.openstack.org/p/monasca-ptg-train
* Oslo - https://etherpad.openstack.org/p/oslo-train-topics

'''Cross-Project:'''
* Nova/Neutron - https://etherpad.openstack.org/p/ptg-train-xproj-nova-neutron
* Nova/Cyborg - https://etherpad.openstack.org/p/ptg-train-xproj-nova-cyborg
* Nova/Placement - https://etherpad.openstack.org/p/ptg-train-xproj-nova-placement

'''SIG/Theme/Other:'''
* Technical Committee - https://etherpad.openstack.org/p/tc-train-ptg

'''Pilot Projects:'''

'''Other:'''

OpenStack Upstream Institute Occasions

2019-03-12T10:20:57Z

Colleen Murphy: /* Denver Crew */

==Denver Training, 2019==

Before the Open Infrastructure Summit Denver, April 28-29, 2019.

===Denver Crew===

{| class="wikitable sortable"
|-
! Name !! IRC !! Mail !! Time Zone !! Projects/Areas !! Notes
|-
|Ildiko Vancsa
|ildikov
|ildiko@openstack.org
|CET
|Docs, Cinder, Nova, Telemetry
|
|-
|Kendall Nelson
|diablo_rojo
|knelson@openstack.org
|Pacific Time, US (UTC-8)
|Storyboard, Docs, First Contact SIG, Technical Elections, Mentoring & Outreach
|
|-
|Matt Oliver
|mattoliverau
|matt@oliver.net.au
|UTC+11 (AEST)
|Swift, First Contact SIG
|
|-
|Colleen Murphy
|cmurphy
|colleen@gazlene.net
|UTC+1/2 (CET/CEST)
|Keystone, Infra, Rpm-Packaging, First Contact SIG
|Sunday only
|}

==Berlin Training, 2018==

Before the OpenStack Summit Berlin, November 11-12, 2018.

===Berlin Crew===

{| class="wikitable sortable"
|-
! Name !! IRC !! Mail !! Time Zone !! Projects/Areas !! Notes
|-
|Ildiko Vancsa
|ildikov
|ildiko@openstack.org
|CET
|Docs, Cinder, Nova, Telemetry
|
|-
|Kendall Nelson
|diablo_rojo
|knelson@openstack.org
|Pacific Time, US (UTC-8)
|Storyboard, Docs, First Contact SIG, Technical Elections, Mentoring & Outreach
|
|-
|Ghanshyam Mann
|gmann
|gmann@ghanshyammann.com
|JST (UTC+9)
|QA, Nova, API
|Will be in Board Meeting on Monday
|-
|Amy Marrich
|spotz
|amy@demarco.com
|Central Time, US
|OSA, Docs. Community, Users
|Will have Board Meeting one day
|-
|Jay Bryant
|jungleboyj
|jsbryant@electronicjungle.net
|CDT (UTC-5)
|Cinder, Docs, Oslo, Manila
|Will be there Saturday and Sunday
|-
|Gergely Csatari
|csatari
|gergely.csatari@nokia.com
|CET
|Docs
|
|-
|Colleen Murphy
|cmurphy
|colleen@gazlene.net
|CET
|Keystone
|
|-
|Mark Korondi
|kmarc
|korondi.mark@gmail.com
|CET
|Training VM
|
|-
|Tony Breeds
|tonyb
|tony@bakeyournoodle.com
| UTC +10
| Stable, Release Management, Nova
|
|-
|Victoria Martinez de la Cruz
|vkmc
|vkmc@redhat.com
| UTC-3
| Manila
|
|-
| Ell Marquez
|
| ellstripes@gmail.com
|
|
|
|-
|Armstrong Foundjem
|armstrong
|foundjem@ieee.org
|UTC-5
|Mentoring
|-
|Daniel Abad
|vabada
|d.abad@cern.ch
| UTC +1
| Ironic
|
|}

==Vancouver Training, 2018==

Before the OpenStack Summit Vancouver, May 19-20, 2018.

===Vancouver Crew===

{| class="wikitable sortable"
|-
! Name !! IRC !! Mail !! Time Zone !! Projects/Areas !! Notes
|-
|Ildiko Vancsa
|ildikov
|ildiko@openstack.org
|CET
|Docs, Cinder, Nova, Telemetry
|
|-
|Kendall Nelson
|diablo_rojo
|knelson@openstack.org
|Pacific Time, US
|Cinder, os-brick, Storyboard
|
|-
|Masayuki Igawa
|masayukig
|masayuki@igawa.io
|JST
|QA(Tempest, stestr, openstack-health, stackviz, ...)
|still need to figure out my travel
|-
|Ghanshyam Mann
|gmann
|gmann@ghanshyammann.com
|JST (UTC+9)
|QA, Nova, API
|
|-
|Amy Marrich
|spotz
|amy@demarco.com
|Central Time, US
|OSA, Docs. Community, Users
|Will have board meeting on Sunday afternoon
|-
|Mark Korondi
|kmarc
|korondi.mark@gmail.com
|CET
|VM image,devstack,cli git vim, etc.
|still need to figure out my travel
|-
|Ian Y. Choi
|ianychoi
|ianyrchoi@gmail.com
|KST (UTC+9)
|Docs. I18n
|
|-
|Matthew Treinish
|mtreinish
|mtreinish@kortar.org
|EDT (UTC-4)
|
|
|-
|Jay Bryant
|jungleboyj
|jsbryant@electronicjungle.net
|CDT (UTC-5)
|Cinder, Docs, Oslo, Manila
|Will be there Saturday and Sunday
|-
|Gergely Csatari
|csatari
|gergely.csatari@nokia.com
|CET
|Docs
|
|-
|Rich Wellum
|rwellum
|rich.wellum@nokia.com
|EST
|Kolla, Openstack-Helm
|
|-
|Mars Toktonaliev
|marst
|mars.toktonaliev@nokia.com
|CST
|Docs
|
|-
|Victoria Martinez de la Cruz
|vkmc
|vkmc@redhat.com
|UTC-3
|Manila
|
|}

==Sydney Training==

Before the OpenStack Summit Sydney, November 4-5, 2017.

===Sydney Crew===

{| class="wikitable"
|Name
|IRC
|Mail
|Time Zone
|Projects/Areas
|Notes
|-
|Ildiko Vancsa
|ildikov
|ildiko@openstack.org
|CET
|Docs, Telemetry, Cinder, Nova
|
|-
|Kendall Nelson
|diablo_rojo
|knelson@openstack.org
|Pacific Time, US
|Cinder, os-brick, Storyboard
|
|-
|Mark Korondi
|kmArc
|korondi.mark@gmail.com
|CET
|Docs, Upstream Institute
|
|-
|Matthew Treinish
|mtreinish
|mtreinish@kortar.org
|Eastern Time, US
|QA, Infra, API, Nova, Glance
|
|-
|Ghanshyam Mann
|gmann
|ghanshyammann@gmail.com
|JST
|QA, Nova, API
|
|-
|Amy Marrich
|spotz
|amy@demarco.com
|Central Time, US
|OpenStack-Ansible, Docs
|
|-
|Sean McGinnis
|smcginnis
|sean.mcginnis@gmail.com
|Central Time, US
|Cinder
|
|-
|Jay Bryant
|jungleboyj
|jsbryant@electronicjungle.net
|Central Time, US
|Cinder, Docs
|
|-
|Gergely Csatari
|csatari
|gergely.csatari@nokia.com
|CET
|Docs
|
|-
|Victoria Martinez de la Cruz
|vkmc
|victoria@redhat.com
|ART
|Manila
|
|}

==Copenhagen Training==

Before the OpenStack Days Nordic event, October 18, 2017.

===Copenhagen Crew===

{| class="wikitable"
|Name
|IRC
|Mail
|Time Zone
|Projects/Areas
|Notes
|-
|Ildiko Vancsa
|ildikov
|ildiko@openstack.org
|CET
|Docs, Telemetry, Cinder, Nova
|
|-
|Kendall Nelson
|diablo_rojo
|knelson@openstack.org
|Central Time, US
|Cinder, os-brick, Storyboard
|
|-
|Mark Korondi
|kmArc
|korondi.mark@gmail.com
|CET
|Docs, Upstream Institute
|
|}

==London Office Hours==

During the OpenStack Days UK event, September 26, 2017.

===London Crew===

{| class="wikitable"
|Name
|IRC
|Mail
|Time Zone
|Projects/Areas
|Notes
|-
|Ildiko Vancsa
|ildikov
|ildiko@openstack.org
|CET
|Docs, Telemetry, Cinder, Nova
|
|-
|Kendall Nelson
|diablo_rojo
|knelson@openstack.org
|Central Time, US
|Cinder, os-brick, Storyboard
|
|}

==Beijing Training==

Before the OPNFV Summit, June 14-15, 2017.

===Beijing Crew===

{| class="wikitable"
|Name
|IRC
|Mail
|Time Zone
|Projects/Areas
|Notes
|-
|Dave Neary
|dneary
|dneary@redhat.com
|Eastern Time, US
|OPNFV and RDO - not directly in OpenStack
|
|-
|Gergely Csatari
|csatari
|gergely.csatari@nokia.com
|CET
|Docs, api-refs, Training Guides
|
|-
|Ildiko Vancsa
|ildikov
|ildiko@openstack.org
|CET
|Docs, Telemetry, Cinder, Nova
|
|-
|JiangShan 江姗
|
|jiangshan@ctsi.com.cn
|
|
|
|-
|Kendall Nelson
|diablo_rojo
|knelson@openstack.org
|Central Time, US
|Cinder, os-brick, Storyboard
|
|-
|Leo Ma
|
|majiajun@unitedstack.com
|
|
|
|-
|Rossella Sblendido
|rossella_s
|rsblendido@suse.com
|CET
|Neutron
|
|-
|ShangXiao 尚啸
|
|shangxiao@ctsi.com.cn
|
|
|
|}

== Boston training ==

Before the OpenStack Summit, May 6-7, 2017.

===Boston Crew===

{| class="wikitable"
|Name
|IRC
|Mail
|Time Zone
|Projects/Areas
|-
|Amy Marrich
|spotz
|amy@demarco.com
|Central Time, US
|Ansible
|-
|Flavio Percoco
|flaper87
|flavio@redhat.com
|
|
|-
|Gergely Csatari
|csatari
|gergely.csatari@nokia.com
|CET
|Docs, api-refs, Training Guides
|-
|Ghanshyam Mann
|gmann
|ghanshyammann@gmail.com
|JST(UTC+9)
|QA
|-
|Ian Y. Choi
|ianychoi
|ianyrchoi@gmail.com
|KST(UTC+9)
|Training Guides + Mentor for I18n
|-
|Ildiko Vancsa
|ildikov
|ildiko@openstack.org
|CET
|Docs, Telemetry, Cinder, Nova
|-
|Jay Bryant
|jungleboyj
|jungleboyj@gmail.com
|Central Time
|Manila
|-
|Jay Pipes
|jaypipes
|jaypipes@gmail.com
|Eastern US
|-
|KATO Tomoyuki
|katomo
|kato.tomoyuki@jp.fujitsu.com
|
|Docs, Training Guides, I18n
|-
|Kendall Nelson
|diablo_rojo
|knelson@openstack.org
|Central US
|Cinder, os-brick, Storyboard
|-
|Mars Toktonaliev
|marst
|mars.toktonaliev@nokia.com
|CST
|
|-
|Mark Korondi
|kmARC
|korondi.mark@gmail.com
|CET
|Training Guides, Swift, Training VM
|-
|Marton Kiss
|mrmartin
|marton.kiss@gmail.com
|CET
|
|-
|Matt Dorn
|madorn
|madorn@gmail.com
|Central Time, US
|Docs, Training Guides
|-
|Miguel A Lavalle
|mlavalle
|malavall@us.ibm.com
|US Central Time
|Neutron, Tempest
|-
|Samantha Blanco
|blancos
|samantha.blanco@att.com
|Eastern Time, US
|Patrole, Murano
|-
|Sean McGinnis
|smcginnis
|sean.mcginnis@gmail.com
|Central Time, US
|Cinder
|-
|Trevor McCasland
|trevormc
|tm2086@att.com
|Central Time, US
|Neutron, Trove
|-
|Victoria Martínez de la Cruz
|vkmc
|victoria@redhat.com
|
|Manila
|}

LibvirtDistroSupportMatrix

2018-09-27T08:38:48Z

Colleen Murphy: /* Distro minimum versions */

== Libvirt OS distribution support matrix ==

This page documents the libvirt versions present in the various distro versions that OpenStack Nova aims to be deployable with.

=== Libvirt min version change policy ===

At the start of each Nova development cycle this matrix will be consulted to determine if it is viable to drop support for any end-of-life or otherwise undesired distro versions. Based on this distro evaluation, it may be possible to increase the min required version of libvirt in Nova, and thus drop some compatibility code for older versions.

When a decision to update the minimum required libvirt version is made, there must be a warning issued for one cycle. This is achieved by editting nova/virt/libvirt/driver.py to set

NEXT_MIN_LIBVIRT_VESION = (X, Y, Z)

This causes a deprecation warning to be printed when Nova starts up warning the admin that the version of libvirt they are on will be dropped in the subsequent release.

After a version has been listed in NEXT_MIN_LIBVIRT_VERSION for one release cycle, the corresponding actual min required libvirt can be updated by setting

MIN_LIBVIRT_VESION = (X, Y, Z)

At this point of course, an even newer version might be set in NEXT_MIN_LIBVIRT_VERSION to repeat the process....

There is more background on the rationale used for picking minimum versions in the operators mailing list thread here:

http://lists.openstack.org/pipermail/openstack-operators/2015-May/007012.html

=== QEMU min version change policy ===

After deciding the minimum libvirt version, the minimum QEMU version is determined by looking for the lowest QEMU version from all the distros that support the decided libvirt version

=== Nova release min version ===

{| class="wikitable"
|-
! Nova version
! Current min libvirt
! Next min libvirt
! Current min QEMU
! Next min QEMU

|-
! Havana
| 0.9.6
| 0.9.6

|-
! Icehouse
| 0.9.6
| 0.9.11

|-
! Juno
| 0.9.11
| 0.9.11

|-
! Kilo
| 0.9.11
| 0.9.11

|-
! Liberty
| 0.9.11
| 0.10.2

|-
! Mitaka
| 0.10.2
| 1.2.1

|-
! Newton
| 1.2.1
| 1.2.1
| 1.5.3
| 1.5.3

|-
! Ocata
| 1.2.1
| 1.2.9
| 1.5.3
| 2.1.0

|-
! Pike
| 1.2.9
| 1.3.1
| 2.1.0
| 2.5.0

|-
! Queens
| 1.2.9
| 1.3.1
| 2.1.0
| 2.5.0

|-
! Rocky
| 1.3.1
| 3.0.0
| 2.5.0
| 2.8.0

|-
! Stein (draft)
| ? 3.0.0
| ? 4.0.0
| ? 2.8.0
| ? 2.11.0

|-
! T (draft)
| ?
| ?
| ?
| ?

|}

=== Distro minimum versions ===

This table provides information on a representative sample of OS distros and the version of libirt/qemu/libguestfs that they ship. This is *NOT* intended to be an exhaustive list of distros where OpenStack Nova can run - it is intended to run on any Linux distro which can satisfy the minimum required software versions. This table merely aims to help identify when min required versions can be reasonably updated without losing support for important OS distros.

When NEXT_MIN_LIBVIRT_VERSION is updated, any distros which don't meet that version should be changed to have <strike>strikethrough</strike> format.

When MIN_LIBVIRT_VERSION is updated, any distros which don't meet that version should be deleted from this table

{| class="wikitable"
|-
! OS Distro
! GA date
! Libvirt
! QEMU/KVM
! libguestfs

|-
! Debian !! !!

|-
| Stretch
| 2017-06-17
| 3.0.0
| 2.8.0
| 1.34.6

|-
| Buster/Sid
| checked on 2018-04-05
| 4.1.0
| 2.11
| 1.36.13

|-
! Fedora !! !!

|-
| 27
| 2017-11-14
| 3.7.0
| 2.10.0
| 1.37.29

|-
| 28
| 2018-05-01
| 4.1.0
| 2.11.1
| 1.38.0

|-
! KVM for IBM z Systems !! !!

|-
| 1.1.0
|
| 1.2.13
| 2.3.0
| N/A

|-
| 1.1.1
|
| 1.2.21
| 2.4.0
| N/A

|-
| 1.1.2
| 2016-11-11 ([https://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=OC&subtype=NA&htmlfid=897/ENUS5648-KVM&appname=totalstorage#lifecycl discontinued support on 2018-03-31])
| 1.3.3
| 2.6.0
| N/A

|-
! openSUSE !! !!

|-
| Leap 42.2
| 2016-11-16
| 2.0.0
| 2.6.1
| 1.32.4

|-
| Leap 42.3
| 2017-07
| 3.3.0
| 2.9.0
| 1.32.4

|-
| Leap 15.0
| 2018-05
| 4.0.0
| 2.11.1
| 1.38.0

|-
! Oracle Linux * !! !!

|-
| 7
|
| 3.10.0
| 2.9.0
| 1.36.3

|-
| FIXME
|
| FIXME
| FIXME
| FIXME

|-
! RHEL * !! !!

|-

| 7.3
| 2016-11-03
| 2.0.0
| 2.6.0
| 1.32.7

|-
| 7.4
| 2017-08-01
| 3.2.0
| 2.9.0
| 1.36.3

|-
| 7.5
| 2018-04-10
| 3.9.0
| 2.10.0
| 1.36.10

|-
| 7.6
|
| FIXME
| FIXME
| FIXME

|-

! SLES !! !!

|-
| 12
|
| 1.2.5
| 2.0.2
| 1.26.9

|-
| 12SP1
| 2016-01-12
| 1.2.18
| 2.3.1
| 1.26.10

|-
| 12SP2
| 2016-11
| 2.0.0
| 2.6.1
| 1.32.4

|-
| 12SP3
| 2017-09
| 3.3.0
| 2.9.0
| 1.32.4

|-
| 15
| 2018-07
| 4.0.0
| 2.11.1
| 1.38.0

|-
! Ubuntu !! !!

|-
| 14.04 (Trusty LTS)
|
| 1.2.2
| 2.0.0
| 1.24.5

|-
| 16.04 (Xenial LTS)
|
| 1.3.1
| 2.5.0
| 1.32.2

|-
| 18.04 (Bionic LTS)
| 2018-04-26
| 4.0.0
| 2.11
| 1.36.13
|}

NB: maintain alphabetical ordering of distros, followed by oldest released versions first

NB2: RHEL versions of QEMU refer to the qemu-kvm-rhev RPM, '''not''' the qemu-kvm RPM, since the former is what is intended for use with OpenStack

NB3: Oracle Linux versions for QEMU and libvirt refer to those used in the docker containers supplied with Oracle OpenStack 4.0. Newer versions will likely be adopted in subsequent releases of Oracle OpenStack. Versions bundled in the OS are aligned with RHEL (i.e. old). Whilst vanilla OpenStack on Oracle Linux is not supported, recent versions of QEMU and libvirt RPMs may be found in the "developer_UEKR5" YUM repository.

OpenStack health tracker

2018-08-21T08:02:58Z

Colleen Murphy: /* Packaging-RPM */

'''This page is a live document and contains notes from TC members working with project teams to ensure they have everything they need and are not running into issues. This information is not necessarily complete.'''

TC members are attached as liaisons to each of the project teams, [https://governance.openstack.org/sigs/ SIGs], or [https://governance.openstack.org/uc/ UC working groups]. The idea is for these liaisons to keep up with the general health of the group, understand any issues they encounter, and help them work with the TC on solutions if necessary. Some TC members may be more active within the group than the basic liaison responsibilities imply, but that is not required.

Liaisons should monitor their groups by:
* reading meeting logs or participating in meetings
* watching summit "project update" videos
* reading relevant messages on the mailing list
* talking with the PTL, chair, and other group members
* checking contribution rates and review turnaround times

== Liaisons ==
=== SIGs ===

{| class="wikitable"
|-
! Group !! TC members
|-
| API
|| mugsie
|-
| First Contact
|| fungi
|-
| K8s
|| dims
|-
| Meta
|| dhellmann
|-
| Resource Management
|| cdent
|-
| Scientific
|| pabelanger
|-
| Security
|| fungi
|-
| Self-healing
|| zaneb
|-
| Upgrade
|| emilien
|}

=== Working Groups ===

{| class="wikitable"
|-
! Group !! TC members
|-
| App Dev Enablement
|| zaneb
|-
| [[Diversity]]
|| fungi
|-
| Enterprise
||
|-
| Fault Genes
||
|-
| [[InteropWG|Interop]]
|| dims, fungi
|-
| LCOO
||
|-
| Large Deployment
|| pabelanger
|-
| Edge/Massively Distributed Clouds
|| ttx
|-
| Operators Telecom/NFV
|| smcginnis
|-
| Ops Tags
|| smcginnis
|-
| Product
||
|-
| [[ProfessionalCertification]]
||
|-
| Public Cloud
|| ttx
|}

=== Project Teams ===

{| class="wikitable"
|-
! Group !! TC members
|-
| Barbican
|| fungi, ttx
|-
| Blazar
|| cmurphy, mnaser
|-
| Chef Openstack
|| pabelanger, mnaser
|-
| Cinder
|| smcginnis, dims
|-
| Cloudkitty
|| ttx, dims
|-
| Congress
|| cdent, fungi
|-
| Cyborg
|| ttx, TheJulia
|-
| Designate
|| cmurphy, cdent
|-
| Documentation
|| dhellmann, pabelanger
|-
| Dragonflow
|| dims, cdent
|-
| Ec2-Api
|| TheJulia, cmurphy
|-
| Freezer
|| ttx, mugsie
|-
| Glance
|| smcginnis, mugsie
|-
| Heat
|| zaneb, emilien
|-
| Horizon
|| cmurphy, smcginnis
|-
| I18n
|| emilien, cdent
|-
| Infrastructure
|| fungi, mnaser
|-
| Ironic
|| mugsie, fungi
|-
| Karbor
|| ttx, mugsie
|-
| Keystone
|| fungi,cmurphy
|-
| Kolla
|| dims, TheJulia
|-
| Kuryr
|| dims, cdent
|-
| Loci
|| pabelanger, dims
|-
| Magnum
|| mnaser, dims
|-
| Manila
|| smcginnis, pabelanger
|-
| Masakari
|| pabelanger, cdent
|-
| Mistral
|| zaneb, cmurphy
|-
| Monasca
|| zaneb, TheJulia
|-
| Murano
|| dhellmann, emilien
|-
| Neutron
|| mugsie, dims
|-
| Nova
|| mnaser, dhellmann
|-
| Octavia
|| mnaser, mugsie
|-
| Openstack Charms
|| ttx, emilien
|-
| Openstack-Helm
|| ttx, dims
|-
| Openstackansible
|| mnaser, smcginnis
|-
| OpenStackClient
|| dhellmann, cmurphy
|-
| Openstacksdk
|| pabelanger, TheJulia
|-
| Oslo
|| dhellmann, mugsie
|-
| Packaging-Rpm
|| cmurphy, zaneb
|-
| Powervmstackers
|| emilien, TheJulia
|-
| Puppet Openstack
|| cmurphy, pabelanger
|-
| Qinling
|| zaneb, TheJulia
|-
| Quality Assurance
|| cdent, fungi
|-
| Rally
|| pabelanger, mnaser
|-
| Refstack
|| fungi, TheJulia
|-
| Release Management
|| dhellmann, smcginnis
|-
| Requirements
|| fungi, dhellmann
|-
| Sahara
|| emilien, pabelanger
|-
| Searchlight
|| mugsie, mnaser
|-
| Security
|| fungi, zaneb
|-
| Senlin
|| zaneb, smcginnis
|-
| Solum
|| zaneb, mnaser
|-
| Stable Branch Maintenance
|| fungi, smcginnis
|-
| Storlets
|| ttx, dhellmann
|-
| Swift
|| smcginnis, mugsie
|-
| Tacker
|| TheJulia, emilien
|-
| Telemetry
|| cdent, dhellmann
|-
| Tricircle
|| emilien, cdent
|-
| Tripleo
|| emilien, cmurphy
|-
| Trove
|| ttx, mugsie
|-
| Vitrage
|| emilien, dhellmann
|-
| Watcher
|| smcginnis, TheJulia
|-
| Winstackers
|| pabelanger, cdent
|-
| Zaqar
|| zaneb, dims
|-
| Zun
|| zaneb, ttx
|}

== Status updates ==

=== Barbican ===

=== Blazar ===
Reported issues
* Organizational diversity fragility: NTT represents 79% of core reviews
* Requested to be listed under project navigator on openstack.org (ttx mentioned that should be taken care of)
* A lot of work seems to be going around updating document linking

=== Chef OpenStack ===
Reported issues
* Individual fragility: Samuel Cassiba represents 75% of commits

=== Cinder ===
Update: June 22, 2018, smcginnis

* Some drop off in participation by some cores, but still active enough not to raise any red flags
* Overall less community involvement
* Project may just be "stable" and doesn't need as much activity as the past
* Still a lot of bug fix work to be done, but no major new features on the roadmap

=== Cloudkitty ===
Updated July 19, 2018 (ttx)

* Currently single-vendor (all cores from ObjectifLibre), failure to retain onboarded people
* Activity is low but stable (33 commits in Rocky so far compared to 57 total in Queens)
* Works to support standalone operation and reusability in a Prometheus-driven stack, good feedback from users on that strategy
* It's mostly in competition with homegrown solutions, which makes it a bit special
* IRC meetings do not appear on eavesdrop.openstack.org -- no regular meeting, focusing on doing some small group meeting for key topics
* Migrated to StoryBoard
* Limited ML engagement (mostly used for team-wide announcements)

=== Congress ===

Update 2018-07-30 by cdent

* Commits somewhat down from Queens (119 in Queens, 69 in Rocky so far)
* Commits and reviews in the hands of a small but diverse group
* Limited engagement on os-dev, but effective: http://lists.openstack.org/pipermail/openstack-dev/2018-May/130180.html
* IRC logged for both channel and meetings, low but steady traffic.
* Working to address step learning curve that new contributors face by refactoring tempest tests and associated documentation.

=== Cyborg ===
Update: 2018-07-10, TheJulia
* Email responded to by PTL on July 4th. PTL has nothing to really report.
* Activity seems to be moderately in-line with the prior cycle, although one of the cores has since become an independent contributor.
* Cyborg does presently hold a weekly meeting on Wednesdays which does appear active, otherwise IRC is quiet.
** There is no calendar entry on eavesdrop.openstack.org for cyborg, TheJulia let the PTL know.
* Email sent to the PTL to initiate communication on July 2nd

=== Designate ===
Last updated 2018-07-23 by cdent

* Low number of reviews, commits, and contributors but it is somewhat steady.
* A significant amount of the code activity is related to aligning with infra/testing/qa related goals and not feature development. "most of our work at the moment is based around fixing the gate / not breaking future versions"
* ML list use is light, but that's always been the case.
* IRC channel is not busy but is responsive.
* Lurking difficulties:
** As of yet, no support for WSGI, which will break things in a pure py3 environment (due to eventlet)
** Low number of reviews means meeting community goals difficult and distracting.
** Feature requesting is not formalized/transparent, people show up asking "why isn't thing X present?"
** Designate is present in many OpenStack distributions but vendors are not providing active contribution support.

Summary: muddling along, but struggling to address feature demands because of lack of incoming flow of people.

=== Diversity ===
Last updated 2018-07-03 by fungi
* The Diversity WG continues to have semi-weekly meetings in their IRC channel with anywhere from 2 to 8 participants (varying week to week)
* Current activities include finalizing the updated diversity survey and following up on feedback to the foundation event coordinators (preferred pronoun stickers for badges, some way to indicate visibly that you don't wish to be photographed, designated alcohol-free areas at official social events)
* Also communicating with the Women of OpenStack group about the possibility of more closely collaborating on sponsored event activities

=== Documentation ===
Update: 2018-07-18, pabelanger
* Revist meeting format at stein PTG
* To early to report on new office hours, but people still seem to as questions at random times.
* review queue is pretty stable
* suggestion in https://review.openstack.org/#/c/579177/, wondering if the TC could help the docs team promote some of the proposed docs guidelines
* could use more designer resources to work on some outstanding tasks wrt docs.o.o that we previously talked about in Dublin. I'm hoping to get some intern time secured from the Foundation in the coming weeks.
* Email send to PTL to initiate communication

=== Dragonflow ===
Reported issues
* Organizational diversity fragility: Huawei represents 100% of core reviews
* The team did not produce a Queens release. Their last release was 4.0.0 on Sept 1, 2017. Should projects that do not prepare releases be considered official? -- dhellmann
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]

=== ec2-api ===
Reported issues
* Individual fragility: Andrey Pavlov represents 100% of core reviews

Update: July 3, 2018 (cmurphy)
* Low activity due to general maturity
* Still actively used by operators, bugs are reported and fixed
* Three cores, all reportedly active
* Being part of OpenStack is still valued
** Operators are still using the project, so better to be coupled with OpenStack
** Depends on other components of OpenStack, so there is value in collaborating together

=== Freezer ===
Reported issues
* Still uses pycrypto [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131103.html]
* freezer and freezer-web-ui missed the Rocky-2 and Rocky-3 milestones
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]

=== Glance ===

=== Heat ===
Update: 2018-06-28, zaneb

* Under active development
* Only 4 active cores, 3 from Red Hat. This is limiting the amount of development that can be done and the velocity of the project.
** Especially struggling with stable reviews (only 1 active core, and the stable-maint team are the gatekeepers for adding more)
* Active on mailing list and IRC
* Regular IRC meetings
* [https://ethercalc.openstack.org/heat-mox-removal Excellent progress] on the (massive) mox-removal goal in Rocky
* The heat-translator sub-project no longer has any team overlap with the rest of the project, and is struggling for core reviewers. It might be time to [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131688.html consider another home for it].

=== Horizon ===
Update: July 20, cmurphy

* Lost several core reviewers recently
* Some promising new contributors, could become cores if they help with reviews more
* Nearly complete with mox goal
* Focus on cross-project plugins and CI coverage
* Lots of participation in weekly meetings
* Concern about getting help with AngularJS work
** Converting more of horizon to AngularJS is still seen as the right technical direction (it provides a better user experience) but community contribution is suffering from it
** Hard to ask devs from other OpenStack projects to add support for new features in non-Python
** Hard in general to attract new JS devs when OpenStack is mostly Python

=== I18n ===
Update: July 04, emilien

Reported issues: none, yet.
The team changed leadership in Queens.

Queens status:
* 87 modules touched (+87%)
* 17 languages supported (+6%)
* 55 active translators (-14%) (TODO, need to check with PTL if it has an impact)
* 7 companies support (-22%)
I18n team previously had team meetings but decided to have office hours instead.
Usually tracks completion of Rocky community goals.
A lot of collaboration with Doc team.
Dedicated mailing-list: openstack-i18n - pretty busy

Rocky:
* <strike>Help is wanted around doc translation. See https://review.openstack.org/#/c/545377 for example.</strike>

=== Infrastructure ===

=== Interop ===
Last updated 2018-07-03 by fungi
* Only a few active members of the Interop WG reviewing and contributing patches to the openstack/interop repository
* Affiliation is fairly diverse, but with so few active that's probably not really relevant
* Mandated to maintain interoperability guidelines in support of official trademark programs, so the board will likely step in if active participants fall below a minimum viable count
* Heavily dependent on the RefStack and QA teams for their tool development

=== Ironic ===

=== Karbor ===

=== Keystone ===
Update July 3, 2018 (cmurphy)
* High pressure due to being a central part of OpenStack
* Focus on "improving the commons" - policy/RBAC work, unified quota management, application development
* 10 cores with varying levels of activity, nearly all are at most part-time
** Concern over possibility of team burnout

=== Kolla ===
Update: 2018-07-30, TheJulia
* Discussion in IRC with the PTL about a week after initial contact in #openstack-tc
* PTL felt that the team was in a good state, that goals had been progressing.
* Slight increase in review activity/commits, overall seems fairly healthy.

Update: 2018-07-10, TheJulia
* No reply received. Follow-up email sent on 2017-07-10 and contact initiated on IRC.
* Email sent to the PTL to initiate communication on July 2nd

=== Kuryr ===
Updated 2018-08-13 by cdent, from an email response by dmellado to a message from dims
Reported issues
* Organizational diversity fragility: RedHat represents 79% of core reviews
** Considering moving or adding meetings to reach more timezones
* Making good headway in general
* Have some challenges with infra that they'd like to figure out:
** Would be good to have an openstack-infra k8s registry for containers
** Would be nice to have nested VMs with large RAM to test pods
* Need to work with neutron to deal with API slowness

=== Large Deployment ===
Update: 2018-07-14, pabelanger

=== Loci ===

Reported issues
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]
** Sam Yaple has agreed to run as PTL again

Update: 2018-08-09, pabelanger
* PTL missed original email, reason for delay.
* LOCI is now a single-repo project. Retired other repos.
* Is stable, but have not agreed and implemented a versioning system.
* Master branch of LOCI can build N-<HEAD of master> OpenStack currently, and this makes the stable branching structure a bit unappealing.
* LOCI has 3 independent efforts right now from a few people that are encouraging.
** aarch64 support though we haven't setup gates yet
** opensuse 15 support
** kolla-loci/loci-kolla support. The output will allow loci images to be used with kolla-ansible without kolla-ansible changes.
* core of LOCI is stable and solid throughout all of this. Most/all of this work is about integrations with other OpenStack projects with the long term goals of sharing the "deploy" gates with OSH/Kolla/Triple-O, testing LOCI images.
* Email send to PTL to initiate communication

=== Magnum ===

=== Manila ===
Update: June 22, 2018, smcginnis

* Project appears to be in good shape
* Focusing on bug fixes and stabilization rather than any big new features
* Drop of in involvement from EU, particularly from HPE and IBM
* Increase of participation from China makes EU drop off not as much of an issue other than time coverage
** Not a lot of involvement on IRC or weekly meeting though
* Lots of good interest downstream, particularly from HPC and telco communities

=== Masakari ===
Reported issues
* Low activity in Rocky for a "new" project
* Organizational diversity fragility: NTT represents 97% of core reviews

=== Mistral ===

=== Monasca ===
Update: August 14th, 2018
* Team is fairly small and tends to utilize a single core reviewer strategy to approve changes.
* Team is holding weekly meetings which seem quite active. Contributor activity seems stable compared to the prior cycle.
* Check-in email sent to the PTL on August 14th. PTL is on vacation until end of month.

=== Murano ===
* murano and murano-dashboard missed the Rocky-2 milestone

Update 13 June 2018, dhellmann

* Recent US government action against ZTE has had an impact on the team, because ZTE employees are key contributors to the project and the core team. It is unclear how much ZTE will be able to continue to contribute in the future. [https://www.nbcnews.com/politics/congress/senate-blocks-zte-deal-rebuke-trump-deal-n882196]
* The murano-core team has members froM AT&T and Mirantis, as well as ZTE.
* emilien sent email on 2018-07-17

Update 6 Aug 2018, dhellmann

* Rong Zhu responded with some hopeful comments about the ZTE situation improving (and it seems to have) and meaning that team members will be more active on IRC again

=== Nova ===

Update 5 July 2018, dhellmann

* melwitt reports "I can't think of any issues we need help with"

=== Octavia ===
* Feeling a small shortage of contributors (contributions & code review)
* OpenStack-wide "interruptions" affect team heavily
* Moving from screen to systemd affected team for ~4 weeks
* WSGI Implementation took time (and changes) and team feels community goals aren't super constructive to project
* Zuul V3 cutovers (and constant restarts) affect productivity and slow down progress
* Sometimes certain things that should be done the "OpenStack" way such as involving PTLs in decisions don't happen
* Storyboard issues: https://etherpad.openstack.org/p/storyboard-issues

=== Openstack Charms ===
Update: June 20, ttx

* Currently single-vendor (all cores from Canonical), but with some external participation
* Steady activity, keeping up with recent evolution (includes Vault and Gnocchi, integrates Designate with Neutron)
* Holds weekly IRC meetings with rotating chair
* Uses Launchpad, and is likely to stay there as it allows sharing tasks with Ubuntu packaging
* Limited ML engagement (thread left dangling at [http://lists.openstack.org/pipermail/openstack-dev/2018-April/129314.html])

=== OpenStack-Helm ===
Update: June 26, ttx

* Currently single-vendor (all cores from AT&T), but with external participation (SKT, 99cloud, Intel...)
* Increasing activity (412 commits in Rocky so far compared to 513 total in Queens)
* Holds weekly IRC meetings, pretty active discussions
* Migrated to StoryBoard
* Limited ML engagement (mostly used for team-wide announcements)
* OpenStack-Helm is release-independent -- it aims to support Newton -> master and track latest all the time. They are waiting until they reach a certain quality level (and stable interface) before declaring a 1.0. See [https://docs.openstack.org/openstack-helm/latest/specs/osh-1.0-requirements.html requirements for 1.0]. This explains lack of releases.

=== OpenStackAnsible ===

=== OpenStackClient ===
Update: 28 June 2018, dhellmann, cmurphy

* uses IRC and the mailing list but no meetings
* the review team is small, but there are several active reviewers not on the core team yet who are candidates
* there is quite a review backlog, but the PTL is optimistic that adding the new reviewers will help with that
* they are still interested in being included on the help wanted list (hence the "orange" status, for now)

=== Openstacksdk ===
Update: 2018-07-02, TheJulia
* Initial communication with PTL, should expect to follow-up with-in the next few days.

=== Oslo ===

Reported issues

* Most of the more active members are employed by Red Hat, so it would be good to bring in more diverse contributors
* oslo.privsep, taskflow, and oslo.service are used in several significant service projects, but are effectively unmaintained.
* oslo.service has some issues with the WSGI service not working under python3. The plan is to encourage all projects to stop using that feature, deprecate, then remove it.
* taskflow is one of several projects that needs to update to a newer version of networkx, but the API changes in networkx mean reworking some of taskflow. Supporting both versions of the APIs may be complicated.

Update: 12 June 2018, dhellmann

* The team is small, but active and working on recruiting.
* Team produces regular and frequent releases for the maintained libraries
* Team meets weekly using IRC
* Team had both onboarding and project update sessions in Vancouver
* The level of activity within each library varies.
* Several of the libraries are reaching a "stable" state in which they may not see many updates beyond bug fixes. This has spurred a discussion of how to treat projects like that, led by the release management team [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131341.html]

=== Packaging-RPM ===
Reported issues
* Organizational diversity fragility: SUSE represents 77% of core reviews
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.] (Update: PTL stepped up https://review.openstack.org/588617)
Update 21 Aug 2018 (cmurphy):
* Concern over low investment from original collaborators - was once a Mirantis/RH/SUSE project, now primary investment is mainly SUSE
* Not enough reviewers, and not a big pool of contributors to draw from given reduced corporate investment
* Seeing activity from several Asian companies but they don't participate in discussions, unclear on what their investment is or how to get them to engage more (some contributors seem to be clearly stats seeking)
* Requires significant effort to keep up to date, original vision of promoting CD by gating with other OpenStack projects and other deployment projects did not pan out (mostly due to lack of time for engagement)
* Not sure if it remains valuable to remain under governance

=== Powervmstackers ===

* Email sent on August 9th (emilien).
* No help is needed, and their collaboration with other projects became better over time.
* Contributions are indeed owned by IBM but they welcome (and have) external contributors.
* The project looks quite healthy so far, and nothing much to report now.

=== Puppet Openstack ===
Update: 2018-08-06 (cmurphy)
* Good progress on important features
** Puppet 5 support
** Debian support
* Some frustration with spam changes (compounded over multiple modules)
* Tripleo moving away from depending on Puppet so maintenance shifting more toward operators
* Overall seems to be growing traction and staying healthy

=== Qinling ===
Update: August 20th, 2018, TheJulia
* PTL Confirmed small team nature, and that the team is largely focused on getting all of the minimum needs taken care of to have a viable FaaS component.
* Emailed PTL on August 14th, 2018.
* Project does not seem to hold regular meetings, but also appears to early in gearing up additional interest.
* Rocky timeframe contributions are much more diverse than Queens timeframe contributions which is a good sign.
* Core reviewing seems to use a mix of one and two core reviewers, weighted heavily towards a single reviewer.

=== Quality Assurance ===

Discussion with gmann, 2018-08-07:
* overall healthy with most repos receiving attention from a diversity of contributors
* grenade is one repo which is of concern, largely due to sdague's departure
* switch to office hours has been positive, increasing doing and discussion, rather than simply reporting
* help from individuals usually associated with other projects important aspect of QA health

Outside of that discussion, there are [http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-08-02.log.html#t2018-08-02T16:13:21 concerns expressed] about QA being too focused on tempest, and tempest being too focused on Nova.

=== Rally ===
Reported issues
* Half on GitHub those days, and unwilling to drop direct branching ACLs
* Individual fragility: Andrey Kurilin represents 56% of commits
* Organizational diversity fragility: GoDaddy represents 97% of core reviews
* It looks like the project may be moving out of gerrit to GitHub? https://github.com/xrally and https://xrally.org -- dhellmann

=== Refstack ===

Reported issues
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]

Last updated 2018-07-03 by fungi
* The core review team has only two active members, both funded directly by the OpenStack Foundation (one reaching the end of that internship)
* The bulk of recent contributions to the main refstack deliverable are from the same two individuals
* Most recent outside development interest has been in the python-tempestconf library for tempest.conf generation, which has also produced some sideline support development in the refstack-client deliverable
* The Refstack effort is considered to be reaching feature-complete state in the coming weeks as some final pieces land, and then will likely be put in maintenance mode from a governance perspective
* The refstack and refstack-client deliverables may make sense to get adopted by the Interop WG so the Refstack team itself can be wound down and officially disbanded
* The python-tempestconf deliverable isn't necessarily a good fit for QA team adoption, but may be looking for an adoptive home or may warrant creation of its own official TC-recognized team

=== Release Management ===

Update: 28 June 2018, dhellmann & smcginnis

* The review work has become easier, but there are still only 3 team members. That leaves succession planning for the PTL role a bit up in the air, and also poses challenges with the members travel to conferences all at the same time.
* Working on a reviewers' guide to help with recruiting.
* Completed adjusting ACLs for all official teams to use the reviewable release process for deliverables that are part of the OpenStack release.

=== Requirements Management ===

* need more reviewers, badly, as discussed a joint leadership meeting in Vancouver

Update: 14 June 2018, dhellmann

* team has recently lost several members
* most work is really down to 3 people (Matt, Dirk, Tony)
* they work for 3 separate companies, but the team is so small that the diversity measures are questionable
* the changes this cycle to stop syncing requirements should lower the review burden somewhat, but the move to python 3 is going to take some work
* meets regularly
* accomplishments this cycle
** stopped syncing dependencies between projects
** working on networkx upgrade
** uncapped eventlet
** uncapped sphinx
** added optional lower-constraints test jobs for project teams that want them

=== Resource Management SIG ===

Update 2018-07-10, cdent. Summary: SIG is idling.

Concerns or Issues:
* While the project had some initial planning at [[Res_Mgmt_SIG]], little has happened since.
* This is likely due to the main participants being overbooked to be able to fit things in.
** cdent is one of those main participants and hasn't had a chance to do anything
* Given the desire for these evaluations to not include participants, cdent being the evaluator is probably not ideal

=== Sahara ===
Update: June 13, emilien

Reported issues: none, yet.
* The team changed leadership in Queens
* Last PTG was virtual
* Most commits in Rocky are from Red Hat (92% of core reviews)
* The team is really small, most of commits are done by 2 contributors and 3 contributors are active in reviews
* Latest survey shows that Sahara is used in production by 3% of deployments and 8% in test phase. 25% of users are interested by Sahara
* Following goals and releases
* Email sent to PTL on June 13th

=== Searchlight ===
Reported issues
* searchlight and searchlight-ui missed the Rocky-1 milestone
* Release forced for searchlight and searchlight-ui for the Rocky-2 milestone; also missed the Rocky-3 milestone
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]

=== Scientific ===
Update: July 17, pabelanger

=== Senlin ===

=== Solum ===
Reported issues
* Individual fragility: Zhurong represents 100% of core reviews
* Zhurong is employed by ZTE and recent US government actions might affecting contributions

=== Storlets ===

Update: August 9, ttx

* The team is essentially one person: Kota Tsuyuzaki the PTL represents 100% of core reviews
* Kota is pretty active though, and maintains the project well. He ran a project update session in Vancouver, and tries to recruit more contributors (including in local meetups).
* The team currently being one person, there are no IRC meetings or ML threads. Best way to join the team is the IRC channel (#openstack-storlets)

=== Swift ===
Update: July 3, smcginnis

* Team has recently lost two very active long time cores
* Activity has gone down, like many OpenStack projects, but there is still a large list of important work to complete
* Changed their policy to only require one +2
** Change in policy is allowing to land more code
** No bad side effects of this change have been encountered so far
* Some recent progress has been made on Python 3 compatibility

=== Tacker ===
Update: August 14th, 2018, TheJulia
* Reached out via email to the new PTL to obtain their perspective as to the current status.
* Worth noting that the new PTL is different than the prior PTL who was attributed to having 75% of the core reviews.
* They have meetings, although occasionally do seem to skip a week or two, but the team is relatively small and diverse which would make missing lacking quorum to have a meeting more of a possibility.

Reported issues
* Individual fragility: Yong Sheng Gong represents 75% of core reviews

=== Telemetry ===
Update: 2018-07-25, cdent
* Only two active cores and contributors (from Red Hat), despite [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131443.html continued value].
* Lowish number of commits and reviews, but about what one would expect for a small and stable project
* Effectively in maintenance mode
* Some potential for greater engagement with Monasca
* The features in ceilometer are being shrunk to meet the needs of the people who are making contributions and there is concern that lack of engagement by others will lead to something breaking.

=== Tricircle ===
Reported issues
* Not set up for zuulv3 so cannot land patches that interact with other repositories? http://lists.openstack.org/pipermail/openstack-dev/2018-June/131643.html
* email sent on July 18th 2018 (emilien)

=== TripleO ===
Update: June 13, emilien

* Mainly Red Hat (99% of core reviews). Some contributors from vendors (storage/network plugins)
* Number of contributors / core reviewers always increasing
* Quite healthy, no problem reported so far

=== Trove ===

Reported issues
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No valid PTL volunteer(s) for Stein.]
* During the public cloud issues session at the Rocky Forum someone in the room raised the question of whether Trove is still actively maintained.
** [https://etherpad.openstack.org/p/YVR-forum-missing-features-pc Missing features in OpenStack for public clouds] forum session notes

Update: June 12, ttx

* The team changed leadership in Rocky
* Zhao Chao handles bulk of commits (51%)
* The new team is small, but pretty alive and active. Needs more contributors to be stable.
* Mostly contributors in China (AWCloud, China Telecom, China Mobile)
* Drop in activity in Rocky: 45 commits by Rocky-2, to compare with the 245 commits in Queens
* Organizational diversity: 53% of commits are from AWCloud. Reviews are shared between 23% China Telecom, 19% China Mobile, 19% Awcloud. Last cycle with 41% IBM.
* Regular weekly meetings, well run with clear documentation of outcomes
* Tracks completion of Rocky community goals
* A few ML threads, but mostly to discuss things external to the team (new meeting time, stable maint team composition)
* Missed Rocky-2 milestone, but mostly due to a [http://eavesdrop.openstack.org/meetings/trove/2018/trove.2018-06-06-14.00.log.html#l-95 misunderstanding of release policy].
* No project update in Vancouver, but was discussed in meeting: sadly [http://eavesdrop.openstack.org/meetings/trove/2018/trove.2018-05-16-14.00.log.html#l-20 no team member was present].
* Reached out to PTL by email on June 12 for additional concerns / questions.

=== Upgrade SIG ===
WIP (emilien)

=== Vitrage ===

Reported issues
* Organizational diversity fragility: Nokia represents 80% of core reviews
* Affected by ZTE situation

Update 2018-07-18 (dhellmann)
* Meeting regularly on IRC
* One of their cores who works for ZTE has been absent for a while, but has returned to contributing.
* They usually have a hands-on lab at summits to attract users and potential contributors.
* The next PTG aligns with Jewish New Year, so many of their contributors will not be attending. They intend to have a virtual PTG instead.
* The CFP for the Berlin summit caught them off guard because it was so early, and they found it a bit hard to plan discussions because they don't even know what the next release will hold. They did submit a few talk proposals.
* Vitrage, by its nature, relies heavily on other projects. They have had good success working with other project teams, but do frequently struggle to find accurate and complete developer-oriented documentation for some of them.

=== Watcher ===
Update: 2018-07-10 TheJulia
* PTL inquires if there is any way for the TC to assist with raising awareness of Watcher.
* Actively recruiting and seeking out new contributors, and anticipating to meet community goals. Anticipating to create new roadmap at the PTG.
* Contributions appear mainly from NEC at this time, but history shows a moderately more diverse contributor base.
* PTL indicates core team is critically small, and that they have lost two out of five cores due to the ZTE withdraw due to the conflict with the US Government. Review metrics line up with what would be expected from loss of 40% of the core reviewers.
* Email sent to the PTL to initiate communication on July 2nd

=== Winstackers ===
Reported issues
* Individual fragility: Claudiu Belu represents 100% of core reviews
* Claudiu missed the deadline for being PTL but would like to continue
* His organization is invested in making sure that Hyper-V continues to be well supported in Nova, Neutron, Cinder
* Increased release velocity by Microsoft means greater change in Hyper-V
* Issues with having access to sufficient CI hardware for feature parity with other hypervisors, especially things like SR-IOV

=== Zaqar ===
Reported issues
* zaqar and zaqar-ui missed the Rocky-2 milestone

=== Zun ===

* PTL and ~25% of commits (in Queens) are from ZTE
* PTL non-responsive to email so far
* Regular meetings happening, mostly chaired by previous PTL (although current PTL has appeared on occasion)
* Healthy-looking pace of development still happening
* Loosened review policy to only require 1 reviewer: http://lists.openstack.org/pipermail/openstack-dev/2018-July/132582.html

OpenStack health tracker

2018-08-06T20:36:27Z

Colleen Murphy: /* Puppet Openstack */

'''This page is a live document and contains notes from TC members working with project teams to ensure they have everything they need and are not running into issues. This information is not necessarily complete.'''

TC members are attached as liaisons to each of the project teams, [https://governance.openstack.org/sigs/ SIGs], or [https://governance.openstack.org/uc/ UC working groups]. The idea is for these liaisons to keep up with the general health of the group, understand any issues they encounter, and help them work with the TC on solutions if necessary. Some TC members may be more active within the group than the basic liaison responsibilities imply, but that is not required.

Liaisons should monitor their groups by:
* reading meeting logs or participating in meetings
* watching summit "project update" videos
* reading relevant messages on the mailing list
* talking with the PTL, chair, and other group members
* checking contribution rates and review turnaround times

== Liaisons ==
=== SIGs ===

{| class="wikitable"
|-
! Group !! TC members
|-
| API
|| mugsie
|-
| First Contact
|| fungi
|-
| K8s
|| dims
|-
| Meta
|| dhellmann
|-
| Resource Management
|| cdent
|-
| Scientific
|| pabelanger
|-
| Security
|| fungi
|-
| Self-healing
|| zaneb
|-
| Upgrade
|| emilien
|}

=== Working Groups ===

{| class="wikitable"
|-
! Group !! TC members
|-
| App Dev Enablement
|| zaneb
|-
| [[Diversity]]
|| fungi
|-
| Enterprise
||
|-
| Fault Genes
||
|-
| [[InteropWG|Interop]]
|| dims, fungi
|-
| LCOO
||
|-
| Large Deployment
|| pabelanger
|-
| Edge/Massively Distributed Clouds
|| ttx
|-
| Operators Telecom/NFV
|| smcginnis
|-
| Ops Tags
|| smcginnis
|-
| Product
||
|-
| [[ProfessionalCertification]]
||
|-
| Public Cloud
|| ttx
|}

=== Project Teams ===

{| class="wikitable"
|-
! Group !! TC members
|-
| Barbican
|| fungi, ttx
|-
| Blazar
|| cmurphy, mnaser
|-
| Chef Openstack
|| pabelanger, mnaser
|-
| Cinder
|| smcginnis, dims
|-
| Cloudkitty
|| ttx, dims
|-
| Congress
|| cdent, fungi
|-
| Cyborg
|| ttx, TheJulia
|-
| Designate
|| cmurphy, cdent
|-
| Documentation
|| dhellmann, pabelanger
|-
| Dragonflow
|| dims, cdent
|-
| Ec2-Api
|| TheJulia, cmurphy
|-
| Freezer
|| ttx, mugsie
|-
| Glance
|| smcginnis, mugsie
|-
| Heat
|| zaneb, emilien
|-
| Horizon
|| cmurphy, smcginnis
|-
| I18n
|| emilien, cdent
|-
| Infrastructure
|| fungi, mnaser
|-
| Ironic
|| mugsie, fungi
|-
| Karbor
|| ttx, mugsie
|-
| Keystone
|| fungi,cmurphy
|-
| Kolla
|| dims, TheJulia
|-
| Kuryr
|| dims, cdent
|-
| Loci
|| pabelanger, dims
|-
| Magnum
|| mnaser, dims
|-
| Manila
|| smcginnis, pabelanger
|-
| Masakari
|| pabelanger, cdent
|-
| Mistral
|| zaneb, cmurphy
|-
| Monasca
|| zaneb, TheJulia
|-
| Murano
|| dhellmann, emilien
|-
| Neutron
|| mugsie, dims
|-
| Nova
|| mnaser, dhellmann
|-
| Octavia
|| mnaser, mugsie
|-
| Openstack Charms
|| ttx, emilien
|-
| Openstack-Helm
|| ttx, dims
|-
| Openstackansible
|| mnaser, smcginnis
|-
| OpenStackClient
|| dhellmann, cmurphy
|-
| Openstacksdk
|| pabelanger, TheJulia
|-
| Oslo
|| dhellmann, mugsie
|-
| Packaging-Rpm
|| cmurphy, zaneb
|-
| Powervmstackers
|| emilien, TheJulia
|-
| Puppet Openstack
|| cmurphy, pabelanger
|-
| Qinling
|| zaneb, TheJulia
|-
| Quality Assurance
|| cdent, fungi
|-
| Rally
|| pabelanger, mnaser
|-
| Refstack
|| fungi, TheJulia
|-
| Release Management
|| dhellmann, smcginnis
|-
| Requirements
|| fungi, dhellmann
|-
| Sahara
|| emilien, pabelanger
|-
| Searchlight
|| mugsie, mnaser
|-
| Security
|| fungi, zaneb
|-
| Senlin
|| zaneb, smcginnis
|-
| Solum
|| zaneb, mnaser
|-
| Stable Branch Maintenance
|| fungi, smcginnis
|-
| Storlets
|| ttx, dhellmann
|-
| Swift
|| smcginnis, mugsie
|-
| Tacker
|| TheJulia, emilien
|-
| Telemetry
|| cdent, dhellmann
|-
| Tricircle
|| emilien, cdent
|-
| Tripleo
|| emilien, cmurphy
|-
| Trove
|| ttx, mugsie
|-
| Vitrage
|| emilien, dhellmann
|-
| Watcher
|| smcginnis, TheJulia
|-
| Winstackers
|| pabelanger, cdent
|-
| Zaqar
|| zaneb, dims
|-
| Zun
|| zaneb, ttx
|}

== Status updates ==

=== Barbican ===

=== Blazar ===
Reported issues
* Organizational diversity fragility: NTT represents 79% of core reviews
* Requested to be listed under project navigator on openstack.org (ttx mentioned that should be taken care of)
* A lot of work seems to be going around updating document linking

=== Chef OpenStack ===
Reported issues
* Individual fragility: Samuel Cassiba represents 75% of commits

=== Cinder ===
Update: June 22, 2018, smcginnis

* Some drop off in participation by some cores, but still active enough not to raise any red flags
* Overall less community involvement
* Project may just be "stable" and doesn't need as much activity as the past
* Still a lot of bug fix work to be done, but no major new features on the roadmap

=== Cloudkitty ===
Updated July 19, 2018 (ttx)

* Currently single-vendor (all cores from ObjectifLibre), failure to retain onboarded people
* Activity is low but stable (33 commits in Rocky so far compared to 57 total in Queens)
* Works to support standalone operation and reusability in a Prometheus-driven stack, good feedback from users on that strategy
* It's mostly in competition with homegrown solutions, which makes it a bit special
* IRC meetings do not appear on eavesdrop.openstack.org -- no regular meeting, focusing on doing some small group meeting for key topics
* Migrated to StoryBoard
* Limited ML engagement (mostly used for team-wide announcements)

=== Congress ===

Update 2018-07-30 by cdent

* Commits somewhat down from Queens (119 in Queens, 69 in Rocky so far)
* Commits and reviews in the hands of a small but diverse group
* Limited engagement on os-dev, but effective: http://lists.openstack.org/pipermail/openstack-dev/2018-May/130180.html
* IRC logged for both channel and meetings, low but steady traffic.
* Working to address step learning curve that new contributors face by refactoring tempest tests and associated documentation.

=== Cyborg ===
Update: 2018-07-10, TheJulia
* Email responded to by PTL on July 4th. PTL has nothing to really report.
* Activity seems to be moderately in-line with the prior cycle, although one of the cores has since become an independent contributor.
* Cyborg does presently hold a weekly meeting on Wednesdays which does appear active, otherwise IRC is quiet.
** There is no calendar entry on eavesdrop.openstack.org for cyborg, TheJulia let the PTL know.
* Email sent to the PTL to initiate communication on July 2nd

=== Designate ===
Last updated 2018-07-23 by cdent

* Low number of reviews, commits, and contributors but it is somewhat steady.
* A significant amount of the code activity is related to aligning with infra/testing/qa related goals and not feature development. "most of our work at the moment is based around fixing the gate / not breaking future versions"
* ML list use is light, but that's always been the case.
* IRC channel is not busy but is responsive.
* Lurking difficulties:
** As of yet, no support for WSGI, which will break things in a pure py3 environment (due to eventlet)
** Low number of reviews means meeting community goals difficult and distracting.
** Feature requesting is not formalized/transparent, people show up asking "why isn't thing X present?"
** Designate is present in many OpenStack distributions but vendors are not providing active contribution support.

Summary: muddling along, but struggling to address feature demands because of lack of incoming flow of people.

=== Diversity ===
Last updated 2018-07-03 by fungi
* The Diversity WG continues to have semi-weekly meetings in their IRC channel with anywhere from 2 to 8 participants (varying week to week)
* Current activities include finalizing the updated diversity survey and following up on feedback to the foundation event coordinators (preferred pronoun stickers for badges, some way to indicate visibly that you don't wish to be photographed, designated alcohol-free areas at official social events)
* Also communicating with the Women of OpenStack group about the possibility of more closely collaborating on sponsored event activities

=== Documentation ===
Update: 2018-07-18, pabelanger
* Revist meeting format at stein PTG
* To early to report on new office hours, but people still seem to as questions at random times.
* review queue is pretty stable
* suggestion in https://review.openstack.org/#/c/579177/, wondering if the TC could help the docs team promote some of the proposed docs guidelines
* could use more designer resources to work on some outstanding tasks wrt docs.o.o that we previously talked about in Dublin. I'm hoping to get some intern time secured from the Foundation in the coming weeks.
* Email send to PTL to initiate communication

=== Dragonflow ===
Reported issues
* Organizational diversity fragility: Huawei represents 100% of core reviews
* The team did not produce a Queens release. Their last release was 4.0.0 on Sept 1, 2017. Should projects that do not prepare releases be considered official? -- dhellmann
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]

=== ec2-api ===
Reported issues
* Individual fragility: Andrey Pavlov represents 100% of core reviews

Update: July 3, 2018 (cmurphy)
* Low activity due to general maturity
* Still actively used by operators, bugs are reported and fixed
* Three cores, all reportedly active
* Being part of OpenStack is still valued
** Operators are still using the project, so better to be coupled with OpenStack
** Depends on other components of OpenStack, so there is value in collaborating together

=== Freezer ===
Reported issues
* Still uses pycrypto [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131103.html]
* freezer and freezer-web-ui missed the Rocky-2 and Rocky-3 milestones
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]

=== Glance ===

=== Heat ===
Update: 2018-06-28, zaneb

* Under active development
* Only 4 active cores, 3 from Red Hat. This is limiting the amount of development that can be done and the velocity of the project.
** Especially struggling with stable reviews (only 1 active core, and the stable-maint team are the gatekeepers for adding more)
* Active on mailing list and IRC
* Regular IRC meetings
* [https://ethercalc.openstack.org/heat-mox-removal Excellent progress] on the (massive) mox-removal goal in Rocky
* The heat-translator sub-project no longer has any team overlap with the rest of the project, and is struggling for core reviewers. It might be time to [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131688.html consider another home for it].

=== Horizon ===
Update: July 20, cmurphy

* Lost several core reviewers recently
* Some promising new contributors, could become cores if they help with reviews more
* Nearly complete with mox goal
* Focus on cross-project plugins and CI coverage
* Lots of participation in weekly meetings
* Concern about getting help with AngularJS work
** Converting more of horizon to AngularJS is still seen as the right technical direction (it provides a better user experience) but community contribution is suffering from it
** Hard to ask devs from other OpenStack projects to add support for new features in non-Python
** Hard in general to attract new JS devs when OpenStack is mostly Python

=== I18n ===
Update: July 04, emilien

Reported issues: none, yet.
The team changed leadership in Queens.

Queens status:
* 87 modules touched (+87%)
* 17 languages supported (+6%)
* 55 active translators (-14%) (TODO, need to check with PTL if it has an impact)
* 7 companies support (-22%)
I18n team previously had team meetings but decided to have office hours instead.
Usually tracks completion of Rocky community goals.
A lot of collaboration with Doc team.
Dedicated mailing-list: openstack-i18n - pretty busy

Rocky:
* <strike>Help is wanted around doc translation. See https://review.openstack.org/#/c/545377 for example.</strike>

=== Infrastructure ===

=== Interop ===
Last updated 2018-07-03 by fungi
* Only a few active members of the Interop WG reviewing and contributing patches to the openstack/interop repository
* Affiliation is fairly diverse, but with so few active that's probably not really relevant
* Mandated to maintain interoperability guidelines in support of official trademark programs, so the board will likely step in if active participants fall below a minimum viable count
* Heavily dependent on the RefStack and QA teams for their tool development

=== Ironic ===

=== Karbor ===

=== Keystone ===
Update July 3, 2018 (cmurphy)
* High pressure due to being a central part of OpenStack
* Focus on "improving the commons" - policy/RBAC work, unified quota management, application development
* 10 cores with varying levels of activity, nearly all are at most part-time
** Concern over possibility of team burnout

=== Kolla ===
Update: 2018-07-30, TheJulia
* Discussion in IRC with the PTL about a week after initial contact in #openstack-tc
* PTL felt that the team was in a good state, that goals had been progressing.
* Slight increase in review activity/commits, overall seems fairly healthy.

Update: 2018-07-10, TheJulia
* No reply received. Follow-up email sent on 2017-07-10 and contact initiated on IRC.
* Email sent to the PTL to initiate communication on July 2nd

=== Kuryr ===
Reported issues
* Organizational diversity fragility: RedHat represents 79% of core reviews

=== Large Deployment ===
Update: 2018-07-14, pabelanger

=== Loci ===

Reported issues
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]

Update: 2018-07-14, pabelanger
* Email send to PTL to initiate communication

=== Magnum ===

=== Manila ===
Update: June 22, 2018, smcginnis

* Project appears to be in good shape
* Focusing on bug fixes and stabilization rather than any big new features
* Drop of in involvement from EU, particularly from HPE and IBM
* Increase of participation from China makes EU drop off not as much of an issue other than time coverage
** Not a lot of involvement on IRC or weekly meeting though
* Lots of good interest downstream, particularly from HPC and telco communities

=== Masakari ===
Reported issues
* Low activity in Rocky for a "new" project
* Organizational diversity fragility: NTT represents 97% of core reviews

=== Mistral ===

=== Monasca ===

=== Murano ===
* murano and murano-dashboard missed the Rocky-2 milestone

Update 13 June 2018, dhellmann

* Recent US government action against ZTE has had an impact on the team, because ZTE employees are key contributors to the project and the core team. It is unclear how much ZTE will be able to continue to contribute in the future. [https://www.nbcnews.com/politics/congress/senate-blocks-zte-deal-rebuke-trump-deal-n882196]
* The murano-core team has members froM AT&T and Mirantis, as well as ZTE.
* emilien sent email on 2018-07-17

Update 6 Aug 2018, dhellmann

* Rong Zhu responded with some hopeful comments about the ZTE situation improving (and it seems to have) and meaning that team members will be more active on IRC again

=== Nova ===

Update 5 July 2018, dhellmann

* melwitt reports "I can't think of any issues we need help with"

=== Octavia ===
* Feeling a small shortage of contributors (contributions & code review)
* OpenStack-wide "interruptions" affect team heavily
* Moving from screen to systemd affected team for ~4 weeks
* WSGI Implementation took time (and changes) and team feels community goals aren't super constructive to project
* Zuul V3 cutovers (and constant restarts) affect productivity and slow down progress
* Sometimes certain things that should be done the "OpenStack" way such as involving PTLs in decisions don't happen
* Storyboard issues: https://etherpad.openstack.org/p/storyboard-issues

=== Openstack Charms ===
Update: June 20, ttx

* Currently single-vendor (all cores from Canonical), but with some external participation
* Steady activity, keeping up with recent evolution (includes Vault and Gnocchi, integrates Designate with Neutron)
* Holds weekly IRC meetings with rotating chair
* Uses Launchpad, and is likely to stay there as it allows sharing tasks with Ubuntu packaging
* Limited ML engagement (thread left dangling at [http://lists.openstack.org/pipermail/openstack-dev/2018-April/129314.html])

=== OpenStack-Helm ===
Update: June 26, ttx

* Currently single-vendor (all cores from AT&T), but with external participation (SKT, 99cloud, Intel...)
* Increasing activity (412 commits in Rocky so far compared to 513 total in Queens)
* Holds weekly IRC meetings, pretty active discussions
* Migrated to StoryBoard
* Limited ML engagement (mostly used for team-wide announcements)
* OpenStack-Helm is release-independent -- it aims to support Newton -> master and track latest all the time. They are waiting until they reach a certain quality level (and stable interface) before declaring a 1.0. See [https://docs.openstack.org/openstack-helm/latest/specs/osh-1.0-requirements.html requirements for 1.0]. This explains lack of releases.

=== OpenStackAnsible ===

=== OpenStackClient ===
Update: 28 June 2018, dhellmann, cmurphy

* uses IRC and the mailing list but no meetings
* the review team is small, but there are several active reviewers not on the core team yet who are candidates
* there is quite a review backlog, but the PTL is optimistic that adding the new reviewers will help with that
* they are still interested in being included on the help wanted list (hence the "orange" status, for now)

=== Openstacksdk ===
Update: 2018-07-02, TheJulia
* Initial communication with PTL, should expect to follow-up with-in the next few days.

=== Oslo ===

Reported issues

* Most of the more active members are employed by Red Hat, so it would be good to bring in more diverse contributors
* oslo.privsep, taskflow, and oslo.service are used in several significant service projects, but are effectively unmaintained.
* oslo.service has some issues with the WSGI service not working under python3. The plan is to encourage all projects to stop using that feature, deprecate, then remove it.
* taskflow is one of several projects that needs to update to a newer version of networkx, but the API changes in networkx mean reworking some of taskflow. Supporting both versions of the APIs may be complicated.

Update: 12 June 2018, dhellmann

* The team is small, but active and working on recruiting.
* Team produces regular and frequent releases for the maintained libraries
* Team meets weekly using IRC
* Team had both onboarding and project update sessions in Vancouver
* The level of activity within each library varies.
* Several of the libraries are reaching a "stable" state in which they may not see many updates beyond bug fixes. This has spurred a discussion of how to treat projects like that, led by the release management team [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131341.html]

=== Packaging-RPM ===
Reported issues
* Organizational diversity fragility: SUSE represents 77% of core reviews
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]

=== Powervmstackers ===

=== Puppet Openstack ===
Update: 2018-08-06 (cmurphy)
* Good progress on important features
** Puppet 5 support
** Debian support
* Some frustration with spam changes (compounded over multiple modules)
* Tripleo moving away from depending on Puppet so maintenance shifting more toward operators
* Overall seems to be growing traction and staying healthy

=== Qinling ===

=== Quality Assurance ===

cdent has started, 2018-07-24

=== Rally ===
Reported issues
* Half on GitHub those days, and unwilling to drop direct branching ACLs
* Individual fragility: Andrey Kurilin represents 56% of commits
* Organizational diversity fragility: GoDaddy represents 97% of core reviews
* It looks like the project may be moving out of gerrit to GitHub? https://github.com/xrally and https://xrally.org -- dhellmann

=== Refstack ===

Reported issues
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]

Last updated 2018-07-03 by fungi
* The core review team has only two active members, both funded directly by the OpenStack Foundation (one reaching the end of that internship)
* The bulk of recent contributions to the main refstack deliverable are from the same two individuals
* Most recent outside development interest has been in the python-tempestconf library for tempest.conf generation, which has also produced some sideline support development in the refstack-client deliverable
* The Refstack effort is considered to be reaching feature-complete state in the coming weeks as some final pieces land, and then will likely be put in maintenance mode from a governance perspective
* The refstack and refstack-client deliverables may make sense to get adopted by the Interop WG so the Refstack team itself can be wound down and officially disbanded
* The python-tempestconf deliverable isn't necessarily a good fit for QA team adoption, but may be looking for an adoptive home or may warrant creation of its own official TC-recognized team

=== Release Management ===

Update: 28 June 2018, dhellmann & smcginnis

* The review work has become easier, but there are still only 3 team members. That leaves succession planning for the PTL role a bit up in the air, and also poses challenges with the members travel to conferences all at the same time.
* Working on a reviewers' guide to help with recruiting.
* Completed adjusting ACLs for all official teams to use the reviewable release process for deliverables that are part of the OpenStack release.

=== Requirements Management ===

* need more reviewers, badly, as discussed a joint leadership meeting in Vancouver

Update: 14 June 2018, dhellmann

* team has recently lost several members
* most work is really down to 3 people (Matt, Dirk, Tony)
* they work for 3 separate companies, but the team is so small that the diversity measures are questionable
* the changes this cycle to stop syncing requirements should lower the review burden somewhat, but the move to python 3 is going to take some work
* meets regularly
* accomplishments this cycle
** stopped syncing dependencies between projects
** working on networkx upgrade
** uncapped eventlet
** uncapped sphinx
** added optional lower-constraints test jobs for project teams that want them

=== Resource Management SIG ===

Update 2018-07-10, cdent. Summary: SIG is idling.

Concerns or Issues:
* While the project had some initial planning at [[Res_Mgmt_SIG]], little has happened since.
* This is likely due to the main participants being overbooked to be able to fit things in.
** cdent is one of those main participants and hasn't had a chance to do anything
* Given the desire for these evaluations to not include participants, cdent being the evaluator is probably not ideal

=== Sahara ===
Update: June 13, emilien

Reported issues: none, yet.
* The team changed leadership in Queens
* Last PTG was virtual
* Most commits in Rocky are from Red Hat (92% of core reviews)
* The team is really small, most of commits are done by 2 contributors and 3 contributors are active in reviews
* Latest survey shows that Sahara is used in production by 3% of deployments and 8% in test phase. 25% of users are interested by Sahara
* Following goals and releases
* Email sent to PTL on June 13th

=== Searchlight ===
Reported issues
* searchlight and searchlight-ui missed the Rocky-1 milestone
* Release forced for searchlight and searchlight-ui for the Rocky-2 milestone; also missed the Rocky-3 milestone
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]

=== Scientific ===
Update: July 17, pabelanger

=== Senlin ===

=== Solum ===
Reported issues
* Individual fragility: Zhurong represents 100% of core reviews
* Zhurong is employed by ZTE and recent US government actions might affecting contributions

=== Storlets ===
Reported issues
* Individual fragility: Kota Tsuyuzaki represents 100% of core reviews

=== Swift ===
Update: July 3, smcginnis

* Team has recently lost two very active long time cores
* Activity has gone down, like many OpenStack projects, but there is still a large list of important work to complete
* Changed their policy to only require one +2
** Change in policy is allowing to land more code
** No bad side effects of this change have been encountered so far
* Some recent progress has been made on Python 3 compatibility

=== Tacker ===
Reported issues
* Individual fragility: Yong Sheng Gong represents 75% of core reviews

=== Telemetry ===
Update: 2018-07-25, cdent
* Only two active cores and contributors (from Red Hat), despite [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131443.html continued value].
* Lowish number of commits and reviews, but about what one would expect for a small and stable project
* Effectively in maintenance mode
* Some potential for greater engagement with Monasca
* The features in ceilometer are being shrunk to meet the needs of the people who are making contributions and there is concern that lack of engagement by others will lead to something breaking.

=== Tricircle ===
Reported issues
* Not set up for zuulv3 so cannot land patches that interact with other repositories? http://lists.openstack.org/pipermail/openstack-dev/2018-June/131643.html
* email sent on July 18th 2018 (emilien)

=== TripleO ===
Update: June 13, emilien

* Mainly Red Hat (99% of core reviews). Some contributors from vendors (storage/network plugins)
* Number of contributors / core reviewers always increasing
* Quite healthy, no problem reported so far

=== Trove ===

Reported issues
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No valid PTL volunteer(s) for Stein.]
* During the public cloud issues session at the Rocky Forum someone in the room raised the question of whether Trove is still actively maintained.
** [https://etherpad.openstack.org/p/YVR-forum-missing-features-pc Missing features in OpenStack for public clouds] forum session notes

Update: June 12, ttx

* The team changed leadership in Rocky
* Zhao Chao handles bulk of commits (51%)
* The new team is small, but pretty alive and active. Needs more contributors to be stable.
* Mostly contributors in China (AWCloud, China Telecom, China Mobile)
* Drop in activity in Rocky: 45 commits by Rocky-2, to compare with the 245 commits in Queens
* Organizational diversity: 53% of commits are from AWCloud. Reviews are shared between 23% China Telecom, 19% China Mobile, 19% Awcloud. Last cycle with 41% IBM.
* Regular weekly meetings, well run with clear documentation of outcomes
* Tracks completion of Rocky community goals
* A few ML threads, but mostly to discuss things external to the team (new meeting time, stable maint team composition)
* Missed Rocky-2 milestone, but mostly due to a [http://eavesdrop.openstack.org/meetings/trove/2018/trove.2018-06-06-14.00.log.html#l-95 misunderstanding of release policy].
* No project update in Vancouver, but was discussed in meeting: sadly [http://eavesdrop.openstack.org/meetings/trove/2018/trove.2018-05-16-14.00.log.html#l-20 no team member was present].
* Reached out to PTL by email on June 12 for additional concerns / questions.

=== Upgrade SIG ===
WIP (emilien)

=== Vitrage ===

Reported issues
* Organizational diversity fragility: Nokia represents 80% of core reviews
* Affected by ZTE situation

Update 2018-07-18 (dhellmann)
* Meeting regularly on IRC
* One of their cores who works for ZTE has been absent for a while, but has returned to contributing.
* They usually have a hands-on lab at summits to attract users and potential contributors.
* The next PTG aligns with Jewish New Year, so many of their contributors will not be attending. They intend to have a virtual PTG instead.
* The CFP for the Berlin summit caught them off guard because it was so early, and they found it a bit hard to plan discussions because they don't even know what the next release will hold. They did submit a few talk proposals.
* Vitrage, by its nature, relies heavily on other projects. They have had good success working with other project teams, but do frequently struggle to find accurate and complete developer-oriented documentation for some of them.

=== Watcher ===
Update: 2018-07-10 TheJulia
* PTL inquires if there is any way for the TC to assist with raising awareness of Watcher.
* Actively recruiting and seeking out new contributors, and anticipating to meet community goals. Anticipating to create new roadmap at the PTG.
* Contributions appear mainly from NEC at this time, but history shows a moderately more diverse contributor base.
* PTL indicates core team is critically small, and that they have lost two out of five cores due to the ZTE withdraw due to the conflict with the US Government. Review metrics line up with what would be expected from loss of 40% of the core reviewers.
* Email sent to the PTL to initiate communication on July 2nd

=== Winstackers ===
Reported issues
* Individual fragility: Claudiu Belu represents 100% of core reviews
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]

=== Zaqar ===
Reported issues
* zaqar and zaqar-ui missed the Rocky-2 milestone

=== Zun ===

* PTL and ~25% of commits (in Queens) are from ZTE
* PTL non-responsive to email so far
* Regular meetings happening, mostly chaired by previous PTL (although current PTL has appeared on occasion)
* Healthy-looking pace of development still happening
* Loosened review policy to only require 1 reviewer: http://lists.openstack.org/pipermail/openstack-dev/2018-July/132582.html

OpenStack health tracker

2018-08-06T20:35:58Z

Colleen Murphy: /* Puppet Openstack */

'''This page is a live document and contains notes from TC members working with project teams to ensure they have everything they need and are not running into issues. This information is not necessarily complete.'''

TC members are attached as liaisons to each of the project teams, [https://governance.openstack.org/sigs/ SIGs], or [https://governance.openstack.org/uc/ UC working groups]. The idea is for these liaisons to keep up with the general health of the group, understand any issues they encounter, and help them work with the TC on solutions if necessary. Some TC members may be more active within the group than the basic liaison responsibilities imply, but that is not required.

Liaisons should monitor their groups by:
* reading meeting logs or participating in meetings
* watching summit "project update" videos
* reading relevant messages on the mailing list
* talking with the PTL, chair, and other group members
* checking contribution rates and review turnaround times

== Liaisons ==
=== SIGs ===

{| class="wikitable"
|-
! Group !! TC members
|-
| API
|| mugsie
|-
| First Contact
|| fungi
|-
| K8s
|| dims
|-
| Meta
|| dhellmann
|-
| Resource Management
|| cdent
|-
| Scientific
|| pabelanger
|-
| Security
|| fungi
|-
| Self-healing
|| zaneb
|-
| Upgrade
|| emilien
|}

=== Working Groups ===

{| class="wikitable"
|-
! Group !! TC members
|-
| App Dev Enablement
|| zaneb
|-
| [[Diversity]]
|| fungi
|-
| Enterprise
||
|-
| Fault Genes
||
|-
| [[InteropWG|Interop]]
|| dims, fungi
|-
| LCOO
||
|-
| Large Deployment
|| pabelanger
|-
| Edge/Massively Distributed Clouds
|| ttx
|-
| Operators Telecom/NFV
|| smcginnis
|-
| Ops Tags
|| smcginnis
|-
| Product
||
|-
| [[ProfessionalCertification]]
||
|-
| Public Cloud
|| ttx
|}

=== Project Teams ===

{| class="wikitable"
|-
! Group !! TC members
|-
| Barbican
|| fungi, ttx
|-
| Blazar
|| cmurphy, mnaser
|-
| Chef Openstack
|| pabelanger, mnaser
|-
| Cinder
|| smcginnis, dims
|-
| Cloudkitty
|| ttx, dims
|-
| Congress
|| cdent, fungi
|-
| Cyborg
|| ttx, TheJulia
|-
| Designate
|| cmurphy, cdent
|-
| Documentation
|| dhellmann, pabelanger
|-
| Dragonflow
|| dims, cdent
|-
| Ec2-Api
|| TheJulia, cmurphy
|-
| Freezer
|| ttx, mugsie
|-
| Glance
|| smcginnis, mugsie
|-
| Heat
|| zaneb, emilien
|-
| Horizon
|| cmurphy, smcginnis
|-
| I18n
|| emilien, cdent
|-
| Infrastructure
|| fungi, mnaser
|-
| Ironic
|| mugsie, fungi
|-
| Karbor
|| ttx, mugsie
|-
| Keystone
|| fungi,cmurphy
|-
| Kolla
|| dims, TheJulia
|-
| Kuryr
|| dims, cdent
|-
| Loci
|| pabelanger, dims
|-
| Magnum
|| mnaser, dims
|-
| Manila
|| smcginnis, pabelanger
|-
| Masakari
|| pabelanger, cdent
|-
| Mistral
|| zaneb, cmurphy
|-
| Monasca
|| zaneb, TheJulia
|-
| Murano
|| dhellmann, emilien
|-
| Neutron
|| mugsie, dims
|-
| Nova
|| mnaser, dhellmann
|-
| Octavia
|| mnaser, mugsie
|-
| Openstack Charms
|| ttx, emilien
|-
| Openstack-Helm
|| ttx, dims
|-
| Openstackansible
|| mnaser, smcginnis
|-
| OpenStackClient
|| dhellmann, cmurphy
|-
| Openstacksdk
|| pabelanger, TheJulia
|-
| Oslo
|| dhellmann, mugsie
|-
| Packaging-Rpm
|| cmurphy, zaneb
|-
| Powervmstackers
|| emilien, TheJulia
|-
| Puppet Openstack
|| cmurphy, pabelanger
|-
| Qinling
|| zaneb, TheJulia
|-
| Quality Assurance
|| cdent, fungi
|-
| Rally
|| pabelanger, mnaser
|-
| Refstack
|| fungi, TheJulia
|-
| Release Management
|| dhellmann, smcginnis
|-
| Requirements
|| fungi, dhellmann
|-
| Sahara
|| emilien, pabelanger
|-
| Searchlight
|| mugsie, mnaser
|-
| Security
|| fungi, zaneb
|-
| Senlin
|| zaneb, smcginnis
|-
| Solum
|| zaneb, mnaser
|-
| Stable Branch Maintenance
|| fungi, smcginnis
|-
| Storlets
|| ttx, dhellmann
|-
| Swift
|| smcginnis, mugsie
|-
| Tacker
|| TheJulia, emilien
|-
| Telemetry
|| cdent, dhellmann
|-
| Tricircle
|| emilien, cdent
|-
| Tripleo
|| emilien, cmurphy
|-
| Trove
|| ttx, mugsie
|-
| Vitrage
|| emilien, dhellmann
|-
| Watcher
|| smcginnis, TheJulia
|-
| Winstackers
|| pabelanger, cdent
|-
| Zaqar
|| zaneb, dims
|-
| Zun
|| zaneb, ttx
|}

== Status updates ==

=== Barbican ===

=== Blazar ===
Reported issues
* Organizational diversity fragility: NTT represents 79% of core reviews
* Requested to be listed under project navigator on openstack.org (ttx mentioned that should be taken care of)
* A lot of work seems to be going around updating document linking

=== Chef OpenStack ===
Reported issues
* Individual fragility: Samuel Cassiba represents 75% of commits

=== Cinder ===
Update: June 22, 2018, smcginnis

* Some drop off in participation by some cores, but still active enough not to raise any red flags
* Overall less community involvement
* Project may just be "stable" and doesn't need as much activity as the past
* Still a lot of bug fix work to be done, but no major new features on the roadmap

=== Cloudkitty ===
Updated July 19, 2018 (ttx)

* Currently single-vendor (all cores from ObjectifLibre), failure to retain onboarded people
* Activity is low but stable (33 commits in Rocky so far compared to 57 total in Queens)
* Works to support standalone operation and reusability in a Prometheus-driven stack, good feedback from users on that strategy
* It's mostly in competition with homegrown solutions, which makes it a bit special
* IRC meetings do not appear on eavesdrop.openstack.org -- no regular meeting, focusing on doing some small group meeting for key topics
* Migrated to StoryBoard
* Limited ML engagement (mostly used for team-wide announcements)

=== Congress ===

Update 2018-07-30 by cdent

* Commits somewhat down from Queens (119 in Queens, 69 in Rocky so far)
* Commits and reviews in the hands of a small but diverse group
* Limited engagement on os-dev, but effective: http://lists.openstack.org/pipermail/openstack-dev/2018-May/130180.html
* IRC logged for both channel and meetings, low but steady traffic.
* Working to address step learning curve that new contributors face by refactoring tempest tests and associated documentation.

=== Cyborg ===
Update: 2018-07-10, TheJulia
* Email responded to by PTL on July 4th. PTL has nothing to really report.
* Activity seems to be moderately in-line with the prior cycle, although one of the cores has since become an independent contributor.
* Cyborg does presently hold a weekly meeting on Wednesdays which does appear active, otherwise IRC is quiet.
** There is no calendar entry on eavesdrop.openstack.org for cyborg, TheJulia let the PTL know.
* Email sent to the PTL to initiate communication on July 2nd

=== Designate ===
Last updated 2018-07-23 by cdent

* Low number of reviews, commits, and contributors but it is somewhat steady.
* A significant amount of the code activity is related to aligning with infra/testing/qa related goals and not feature development. "most of our work at the moment is based around fixing the gate / not breaking future versions"
* ML list use is light, but that's always been the case.
* IRC channel is not busy but is responsive.
* Lurking difficulties:
** As of yet, no support for WSGI, which will break things in a pure py3 environment (due to eventlet)
** Low number of reviews means meeting community goals difficult and distracting.
** Feature requesting is not formalized/transparent, people show up asking "why isn't thing X present?"
** Designate is present in many OpenStack distributions but vendors are not providing active contribution support.

Summary: muddling along, but struggling to address feature demands because of lack of incoming flow of people.

=== Diversity ===
Last updated 2018-07-03 by fungi
* The Diversity WG continues to have semi-weekly meetings in their IRC channel with anywhere from 2 to 8 participants (varying week to week)
* Current activities include finalizing the updated diversity survey and following up on feedback to the foundation event coordinators (preferred pronoun stickers for badges, some way to indicate visibly that you don't wish to be photographed, designated alcohol-free areas at official social events)
* Also communicating with the Women of OpenStack group about the possibility of more closely collaborating on sponsored event activities

=== Documentation ===
Update: 2018-07-18, pabelanger
* Revist meeting format at stein PTG
* To early to report on new office hours, but people still seem to as questions at random times.
* review queue is pretty stable
* suggestion in https://review.openstack.org/#/c/579177/, wondering if the TC could help the docs team promote some of the proposed docs guidelines
* could use more designer resources to work on some outstanding tasks wrt docs.o.o that we previously talked about in Dublin. I'm hoping to get some intern time secured from the Foundation in the coming weeks.
* Email send to PTL to initiate communication

=== Dragonflow ===
Reported issues
* Organizational diversity fragility: Huawei represents 100% of core reviews
* The team did not produce a Queens release. Their last release was 4.0.0 on Sept 1, 2017. Should projects that do not prepare releases be considered official? -- dhellmann
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]

=== ec2-api ===
Reported issues
* Individual fragility: Andrey Pavlov represents 100% of core reviews

Update: July 3, 2018 (cmurphy)
* Low activity due to general maturity
* Still actively used by operators, bugs are reported and fixed
* Three cores, all reportedly active
* Being part of OpenStack is still valued
** Operators are still using the project, so better to be coupled with OpenStack
** Depends on other components of OpenStack, so there is value in collaborating together

=== Freezer ===
Reported issues
* Still uses pycrypto [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131103.html]
* freezer and freezer-web-ui missed the Rocky-2 and Rocky-3 milestones
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]

=== Glance ===

=== Heat ===
Update: 2018-06-28, zaneb

* Under active development
* Only 4 active cores, 3 from Red Hat. This is limiting the amount of development that can be done and the velocity of the project.
** Especially struggling with stable reviews (only 1 active core, and the stable-maint team are the gatekeepers for adding more)
* Active on mailing list and IRC
* Regular IRC meetings
* [https://ethercalc.openstack.org/heat-mox-removal Excellent progress] on the (massive) mox-removal goal in Rocky
* The heat-translator sub-project no longer has any team overlap with the rest of the project, and is struggling for core reviewers. It might be time to [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131688.html consider another home for it].

=== Horizon ===
Update: July 20, cmurphy

* Lost several core reviewers recently
* Some promising new contributors, could become cores if they help with reviews more
* Nearly complete with mox goal
* Focus on cross-project plugins and CI coverage
* Lots of participation in weekly meetings
* Concern about getting help with AngularJS work
** Converting more of horizon to AngularJS is still seen as the right technical direction (it provides a better user experience) but community contribution is suffering from it
** Hard to ask devs from other OpenStack projects to add support for new features in non-Python
** Hard in general to attract new JS devs when OpenStack is mostly Python

=== I18n ===
Update: July 04, emilien

Reported issues: none, yet.
The team changed leadership in Queens.

Queens status:
* 87 modules touched (+87%)
* 17 languages supported (+6%)
* 55 active translators (-14%) (TODO, need to check with PTL if it has an impact)
* 7 companies support (-22%)
I18n team previously had team meetings but decided to have office hours instead.
Usually tracks completion of Rocky community goals.
A lot of collaboration with Doc team.
Dedicated mailing-list: openstack-i18n - pretty busy

Rocky:
* <strike>Help is wanted around doc translation. See https://review.openstack.org/#/c/545377 for example.</strike>

=== Infrastructure ===

=== Interop ===
Last updated 2018-07-03 by fungi
* Only a few active members of the Interop WG reviewing and contributing patches to the openstack/interop repository
* Affiliation is fairly diverse, but with so few active that's probably not really relevant
* Mandated to maintain interoperability guidelines in support of official trademark programs, so the board will likely step in if active participants fall below a minimum viable count
* Heavily dependent on the RefStack and QA teams for their tool development

=== Ironic ===

=== Karbor ===

=== Keystone ===
Update July 3, 2018 (cmurphy)
* High pressure due to being a central part of OpenStack
* Focus on "improving the commons" - policy/RBAC work, unified quota management, application development
* 10 cores with varying levels of activity, nearly all are at most part-time
** Concern over possibility of team burnout

=== Kolla ===
Update: 2018-07-30, TheJulia
* Discussion in IRC with the PTL about a week after initial contact in #openstack-tc
* PTL felt that the team was in a good state, that goals had been progressing.
* Slight increase in review activity/commits, overall seems fairly healthy.

Update: 2018-07-10, TheJulia
* No reply received. Follow-up email sent on 2017-07-10 and contact initiated on IRC.
* Email sent to the PTL to initiate communication on July 2nd

=== Kuryr ===
Reported issues
* Organizational diversity fragility: RedHat represents 79% of core reviews

=== Large Deployment ===
Update: 2018-07-14, pabelanger

=== Loci ===

Reported issues
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]

Update: 2018-07-14, pabelanger
* Email send to PTL to initiate communication

=== Magnum ===

=== Manila ===
Update: June 22, 2018, smcginnis

* Project appears to be in good shape
* Focusing on bug fixes and stabilization rather than any big new features
* Drop of in involvement from EU, particularly from HPE and IBM
* Increase of participation from China makes EU drop off not as much of an issue other than time coverage
** Not a lot of involvement on IRC or weekly meeting though
* Lots of good interest downstream, particularly from HPC and telco communities

=== Masakari ===
Reported issues
* Low activity in Rocky for a "new" project
* Organizational diversity fragility: NTT represents 97% of core reviews

=== Mistral ===

=== Monasca ===

=== Murano ===
* murano and murano-dashboard missed the Rocky-2 milestone

Update 13 June 2018, dhellmann

* Recent US government action against ZTE has had an impact on the team, because ZTE employees are key contributors to the project and the core team. It is unclear how much ZTE will be able to continue to contribute in the future. [https://www.nbcnews.com/politics/congress/senate-blocks-zte-deal-rebuke-trump-deal-n882196]
* The murano-core team has members froM AT&T and Mirantis, as well as ZTE.
* emilien sent email on 2018-07-17

Update 6 Aug 2018, dhellmann

* Rong Zhu responded with some hopeful comments about the ZTE situation improving (and it seems to have) and meaning that team members will be more active on IRC again

=== Nova ===

Update 5 July 2018, dhellmann

* melwitt reports "I can't think of any issues we need help with"

=== Octavia ===
* Feeling a small shortage of contributors (contributions & code review)
* OpenStack-wide "interruptions" affect team heavily
* Moving from screen to systemd affected team for ~4 weeks
* WSGI Implementation took time (and changes) and team feels community goals aren't super constructive to project
* Zuul V3 cutovers (and constant restarts) affect productivity and slow down progress
* Sometimes certain things that should be done the "OpenStack" way such as involving PTLs in decisions don't happen
* Storyboard issues: https://etherpad.openstack.org/p/storyboard-issues

=== Openstack Charms ===
Update: June 20, ttx

* Currently single-vendor (all cores from Canonical), but with some external participation
* Steady activity, keeping up with recent evolution (includes Vault and Gnocchi, integrates Designate with Neutron)
* Holds weekly IRC meetings with rotating chair
* Uses Launchpad, and is likely to stay there as it allows sharing tasks with Ubuntu packaging
* Limited ML engagement (thread left dangling at [http://lists.openstack.org/pipermail/openstack-dev/2018-April/129314.html])

=== OpenStack-Helm ===
Update: June 26, ttx

* Currently single-vendor (all cores from AT&T), but with external participation (SKT, 99cloud, Intel...)
* Increasing activity (412 commits in Rocky so far compared to 513 total in Queens)
* Holds weekly IRC meetings, pretty active discussions
* Migrated to StoryBoard
* Limited ML engagement (mostly used for team-wide announcements)
* OpenStack-Helm is release-independent -- it aims to support Newton -> master and track latest all the time. They are waiting until they reach a certain quality level (and stable interface) before declaring a 1.0. See [https://docs.openstack.org/openstack-helm/latest/specs/osh-1.0-requirements.html requirements for 1.0]. This explains lack of releases.

=== OpenStackAnsible ===

=== OpenStackClient ===
Update: 28 June 2018, dhellmann, cmurphy

* uses IRC and the mailing list but no meetings
* the review team is small, but there are several active reviewers not on the core team yet who are candidates
* there is quite a review backlog, but the PTL is optimistic that adding the new reviewers will help with that
* they are still interested in being included on the help wanted list (hence the "orange" status, for now)

=== Openstacksdk ===
Update: 2018-07-02, TheJulia
* Initial communication with PTL, should expect to follow-up with-in the next few days.

=== Oslo ===

Reported issues

* Most of the more active members are employed by Red Hat, so it would be good to bring in more diverse contributors
* oslo.privsep, taskflow, and oslo.service are used in several significant service projects, but are effectively unmaintained.
* oslo.service has some issues with the WSGI service not working under python3. The plan is to encourage all projects to stop using that feature, deprecate, then remove it.
* taskflow is one of several projects that needs to update to a newer version of networkx, but the API changes in networkx mean reworking some of taskflow. Supporting both versions of the APIs may be complicated.

Update: 12 June 2018, dhellmann

* The team is small, but active and working on recruiting.
* Team produces regular and frequent releases for the maintained libraries
* Team meets weekly using IRC
* Team had both onboarding and project update sessions in Vancouver
* The level of activity within each library varies.
* Several of the libraries are reaching a "stable" state in which they may not see many updates beyond bug fixes. This has spurred a discussion of how to treat projects like that, led by the release management team [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131341.html]

=== Packaging-RPM ===
Reported issues
* Organizational diversity fragility: SUSE represents 77% of core reviews
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]

=== Powervmstackers ===

=== Puppet Openstack ===
Update: 2018-08-06 (cmurphy)
Good progress on important features
* Puppet 5 support
* Debian support
Some frustration with spam changes (compounded over multiple modules)
Tripleo moving away from depending on Puppet so maintenance shifting more toward operators
Overall seems to be growing traction and staying healthy

=== Qinling ===

=== Quality Assurance ===

cdent has started, 2018-07-24

=== Rally ===
Reported issues
* Half on GitHub those days, and unwilling to drop direct branching ACLs
* Individual fragility: Andrey Kurilin represents 56% of commits
* Organizational diversity fragility: GoDaddy represents 97% of core reviews
* It looks like the project may be moving out of gerrit to GitHub? https://github.com/xrally and https://xrally.org -- dhellmann

=== Refstack ===

Reported issues
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]

Last updated 2018-07-03 by fungi
* The core review team has only two active members, both funded directly by the OpenStack Foundation (one reaching the end of that internship)
* The bulk of recent contributions to the main refstack deliverable are from the same two individuals
* Most recent outside development interest has been in the python-tempestconf library for tempest.conf generation, which has also produced some sideline support development in the refstack-client deliverable
* The Refstack effort is considered to be reaching feature-complete state in the coming weeks as some final pieces land, and then will likely be put in maintenance mode from a governance perspective
* The refstack and refstack-client deliverables may make sense to get adopted by the Interop WG so the Refstack team itself can be wound down and officially disbanded
* The python-tempestconf deliverable isn't necessarily a good fit for QA team adoption, but may be looking for an adoptive home or may warrant creation of its own official TC-recognized team

=== Release Management ===

Update: 28 June 2018, dhellmann & smcginnis

* The review work has become easier, but there are still only 3 team members. That leaves succession planning for the PTL role a bit up in the air, and also poses challenges with the members travel to conferences all at the same time.
* Working on a reviewers' guide to help with recruiting.
* Completed adjusting ACLs for all official teams to use the reviewable release process for deliverables that are part of the OpenStack release.

=== Requirements Management ===

* need more reviewers, badly, as discussed a joint leadership meeting in Vancouver

Update: 14 June 2018, dhellmann

* team has recently lost several members
* most work is really down to 3 people (Matt, Dirk, Tony)
* they work for 3 separate companies, but the team is so small that the diversity measures are questionable
* the changes this cycle to stop syncing requirements should lower the review burden somewhat, but the move to python 3 is going to take some work
* meets regularly
* accomplishments this cycle
** stopped syncing dependencies between projects
** working on networkx upgrade
** uncapped eventlet
** uncapped sphinx
** added optional lower-constraints test jobs for project teams that want them

=== Resource Management SIG ===

Update 2018-07-10, cdent. Summary: SIG is idling.

Concerns or Issues:
* While the project had some initial planning at [[Res_Mgmt_SIG]], little has happened since.
* This is likely due to the main participants being overbooked to be able to fit things in.
** cdent is one of those main participants and hasn't had a chance to do anything
* Given the desire for these evaluations to not include participants, cdent being the evaluator is probably not ideal

=== Sahara ===
Update: June 13, emilien

Reported issues: none, yet.
* The team changed leadership in Queens
* Last PTG was virtual
* Most commits in Rocky are from Red Hat (92% of core reviews)
* The team is really small, most of commits are done by 2 contributors and 3 contributors are active in reviews
* Latest survey shows that Sahara is used in production by 3% of deployments and 8% in test phase. 25% of users are interested by Sahara
* Following goals and releases
* Email sent to PTL on June 13th

=== Searchlight ===
Reported issues
* searchlight and searchlight-ui missed the Rocky-1 milestone
* Release forced for searchlight and searchlight-ui for the Rocky-2 milestone; also missed the Rocky-3 milestone
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]

=== Scientific ===
Update: July 17, pabelanger

=== Senlin ===

=== Solum ===
Reported issues
* Individual fragility: Zhurong represents 100% of core reviews
* Zhurong is employed by ZTE and recent US government actions might affecting contributions

=== Storlets ===
Reported issues
* Individual fragility: Kota Tsuyuzaki represents 100% of core reviews

=== Swift ===
Update: July 3, smcginnis

* Team has recently lost two very active long time cores
* Activity has gone down, like many OpenStack projects, but there is still a large list of important work to complete
* Changed their policy to only require one +2
** Change in policy is allowing to land more code
** No bad side effects of this change have been encountered so far
* Some recent progress has been made on Python 3 compatibility

=== Tacker ===
Reported issues
* Individual fragility: Yong Sheng Gong represents 75% of core reviews

=== Telemetry ===
Update: 2018-07-25, cdent
* Only two active cores and contributors (from Red Hat), despite [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131443.html continued value].
* Lowish number of commits and reviews, but about what one would expect for a small and stable project
* Effectively in maintenance mode
* Some potential for greater engagement with Monasca
* The features in ceilometer are being shrunk to meet the needs of the people who are making contributions and there is concern that lack of engagement by others will lead to something breaking.

=== Tricircle ===
Reported issues
* Not set up for zuulv3 so cannot land patches that interact with other repositories? http://lists.openstack.org/pipermail/openstack-dev/2018-June/131643.html
* email sent on July 18th 2018 (emilien)

=== TripleO ===
Update: June 13, emilien

* Mainly Red Hat (99% of core reviews). Some contributors from vendors (storage/network plugins)
* Number of contributors / core reviewers always increasing
* Quite healthy, no problem reported so far

=== Trove ===

Reported issues
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No valid PTL volunteer(s) for Stein.]
* During the public cloud issues session at the Rocky Forum someone in the room raised the question of whether Trove is still actively maintained.
** [https://etherpad.openstack.org/p/YVR-forum-missing-features-pc Missing features in OpenStack for public clouds] forum session notes

Update: June 12, ttx

* The team changed leadership in Rocky
* Zhao Chao handles bulk of commits (51%)
* The new team is small, but pretty alive and active. Needs more contributors to be stable.
* Mostly contributors in China (AWCloud, China Telecom, China Mobile)
* Drop in activity in Rocky: 45 commits by Rocky-2, to compare with the 245 commits in Queens
* Organizational diversity: 53% of commits are from AWCloud. Reviews are shared between 23% China Telecom, 19% China Mobile, 19% Awcloud. Last cycle with 41% IBM.
* Regular weekly meetings, well run with clear documentation of outcomes
* Tracks completion of Rocky community goals
* A few ML threads, but mostly to discuss things external to the team (new meeting time, stable maint team composition)
* Missed Rocky-2 milestone, but mostly due to a [http://eavesdrop.openstack.org/meetings/trove/2018/trove.2018-06-06-14.00.log.html#l-95 misunderstanding of release policy].
* No project update in Vancouver, but was discussed in meeting: sadly [http://eavesdrop.openstack.org/meetings/trove/2018/trove.2018-05-16-14.00.log.html#l-20 no team member was present].
* Reached out to PTL by email on June 12 for additional concerns / questions.

=== Upgrade SIG ===
WIP (emilien)

=== Vitrage ===

Reported issues
* Organizational diversity fragility: Nokia represents 80% of core reviews
* Affected by ZTE situation

Update 2018-07-18 (dhellmann)
* Meeting regularly on IRC
* One of their cores who works for ZTE has been absent for a while, but has returned to contributing.
* They usually have a hands-on lab at summits to attract users and potential contributors.
* The next PTG aligns with Jewish New Year, so many of their contributors will not be attending. They intend to have a virtual PTG instead.
* The CFP for the Berlin summit caught them off guard because it was so early, and they found it a bit hard to plan discussions because they don't even know what the next release will hold. They did submit a few talk proposals.
* Vitrage, by its nature, relies heavily on other projects. They have had good success working with other project teams, but do frequently struggle to find accurate and complete developer-oriented documentation for some of them.

=== Watcher ===
Update: 2018-07-10 TheJulia
* PTL inquires if there is any way for the TC to assist with raising awareness of Watcher.
* Actively recruiting and seeking out new contributors, and anticipating to meet community goals. Anticipating to create new roadmap at the PTG.
* Contributions appear mainly from NEC at this time, but history shows a moderately more diverse contributor base.
* PTL indicates core team is critically small, and that they have lost two out of five cores due to the ZTE withdraw due to the conflict with the US Government. Review metrics line up with what would be expected from loss of 40% of the core reviewers.
* Email sent to the PTL to initiate communication on July 2nd

=== Winstackers ===
Reported issues
* Individual fragility: Claudiu Belu represents 100% of core reviews
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]

=== Zaqar ===
Reported issues
* zaqar and zaqar-ui missed the Rocky-2 milestone

=== Zun ===

* PTL and ~25% of commits (in Queens) are from ZTE
* PTL non-responsive to email so far
* Regular meetings happening, mostly chaired by previous PTL (although current PTL has appeared on occasion)
* Healthy-looking pace of development still happening
* Loosened review policy to only require 1 reviewer: http://lists.openstack.org/pipermail/openstack-dev/2018-July/132582.html

OpenStack health tracker

2018-08-06T20:34:21Z

Colleen Murphy: /* Puppet Openstack */

'''This page is a live document and contains notes from TC members working with project teams to ensure they have everything they need and are not running into issues. This information is not necessarily complete.'''

TC members are attached as liaisons to each of the project teams, [https://governance.openstack.org/sigs/ SIGs], or [https://governance.openstack.org/uc/ UC working groups]. The idea is for these liaisons to keep up with the general health of the group, understand any issues they encounter, and help them work with the TC on solutions if necessary. Some TC members may be more active within the group than the basic liaison responsibilities imply, but that is not required.

Liaisons should monitor their groups by:
* reading meeting logs or participating in meetings
* watching summit "project update" videos
* reading relevant messages on the mailing list
* talking with the PTL, chair, and other group members
* checking contribution rates and review turnaround times

== Liaisons ==
=== SIGs ===

{| class="wikitable"
|-
! Group !! TC members
|-
| API
|| mugsie
|-
| First Contact
|| fungi
|-
| K8s
|| dims
|-
| Meta
|| dhellmann
|-
| Resource Management
|| cdent
|-
| Scientific
|| pabelanger
|-
| Security
|| fungi
|-
| Self-healing
|| zaneb
|-
| Upgrade
|| emilien
|}

=== Working Groups ===

{| class="wikitable"
|-
! Group !! TC members
|-
| App Dev Enablement
|| zaneb
|-
| [[Diversity]]
|| fungi
|-
| Enterprise
||
|-
| Fault Genes
||
|-
| [[InteropWG|Interop]]
|| dims, fungi
|-
| LCOO
||
|-
| Large Deployment
|| pabelanger
|-
| Edge/Massively Distributed Clouds
|| ttx
|-
| Operators Telecom/NFV
|| smcginnis
|-
| Ops Tags
|| smcginnis
|-
| Product
||
|-
| [[ProfessionalCertification]]
||
|-
| Public Cloud
|| ttx
|}

=== Project Teams ===

{| class="wikitable"
|-
! Group !! TC members
|-
| Barbican
|| fungi, ttx
|-
| Blazar
|| cmurphy, mnaser
|-
| Chef Openstack
|| pabelanger, mnaser
|-
| Cinder
|| smcginnis, dims
|-
| Cloudkitty
|| ttx, dims
|-
| Congress
|| cdent, fungi
|-
| Cyborg
|| ttx, TheJulia
|-
| Designate
|| cmurphy, cdent
|-
| Documentation
|| dhellmann, pabelanger
|-
| Dragonflow
|| dims, cdent
|-
| Ec2-Api
|| TheJulia, cmurphy
|-
| Freezer
|| ttx, mugsie
|-
| Glance
|| smcginnis, mugsie
|-
| Heat
|| zaneb, emilien
|-
| Horizon
|| cmurphy, smcginnis
|-
| I18n
|| emilien, cdent
|-
| Infrastructure
|| fungi, mnaser
|-
| Ironic
|| mugsie, fungi
|-
| Karbor
|| ttx, mugsie
|-
| Keystone
|| fungi,cmurphy
|-
| Kolla
|| dims, TheJulia
|-
| Kuryr
|| dims, cdent
|-
| Loci
|| pabelanger, dims
|-
| Magnum
|| mnaser, dims
|-
| Manila
|| smcginnis, pabelanger
|-
| Masakari
|| pabelanger, cdent
|-
| Mistral
|| zaneb, cmurphy
|-
| Monasca
|| zaneb, TheJulia
|-
| Murano
|| dhellmann, emilien
|-
| Neutron
|| mugsie, dims
|-
| Nova
|| mnaser, dhellmann
|-
| Octavia
|| mnaser, mugsie
|-
| Openstack Charms
|| ttx, emilien
|-
| Openstack-Helm
|| ttx, dims
|-
| Openstackansible
|| mnaser, smcginnis
|-
| OpenStackClient
|| dhellmann, cmurphy
|-
| Openstacksdk
|| pabelanger, TheJulia
|-
| Oslo
|| dhellmann, mugsie
|-
| Packaging-Rpm
|| cmurphy, zaneb
|-
| Powervmstackers
|| emilien, TheJulia
|-
| Puppet Openstack
|| cmurphy, pabelanger
|-
| Qinling
|| zaneb, TheJulia
|-
| Quality Assurance
|| cdent, fungi
|-
| Rally
|| pabelanger, mnaser
|-
| Refstack
|| fungi, TheJulia
|-
| Release Management
|| dhellmann, smcginnis
|-
| Requirements
|| fungi, dhellmann
|-
| Sahara
|| emilien, pabelanger
|-
| Searchlight
|| mugsie, mnaser
|-
| Security
|| fungi, zaneb
|-
| Senlin
|| zaneb, smcginnis
|-
| Solum
|| zaneb, mnaser
|-
| Stable Branch Maintenance
|| fungi, smcginnis
|-
| Storlets
|| ttx, dhellmann
|-
| Swift
|| smcginnis, mugsie
|-
| Tacker
|| TheJulia, emilien
|-
| Telemetry
|| cdent, dhellmann
|-
| Tricircle
|| emilien, cdent
|-
| Tripleo
|| emilien, cmurphy
|-
| Trove
|| ttx, mugsie
|-
| Vitrage
|| emilien, dhellmann
|-
| Watcher
|| smcginnis, TheJulia
|-
| Winstackers
|| pabelanger, cdent
|-
| Zaqar
|| zaneb, dims
|-
| Zun
|| zaneb, ttx
|}

== Status updates ==

=== Barbican ===

=== Blazar ===
Reported issues
* Organizational diversity fragility: NTT represents 79% of core reviews
* Requested to be listed under project navigator on openstack.org (ttx mentioned that should be taken care of)
* A lot of work seems to be going around updating document linking

=== Chef OpenStack ===
Reported issues
* Individual fragility: Samuel Cassiba represents 75% of commits

=== Cinder ===
Update: June 22, 2018, smcginnis

* Some drop off in participation by some cores, but still active enough not to raise any red flags
* Overall less community involvement
* Project may just be "stable" and doesn't need as much activity as the past
* Still a lot of bug fix work to be done, but no major new features on the roadmap

=== Cloudkitty ===
Updated July 19, 2018 (ttx)

* Currently single-vendor (all cores from ObjectifLibre), failure to retain onboarded people
* Activity is low but stable (33 commits in Rocky so far compared to 57 total in Queens)
* Works to support standalone operation and reusability in a Prometheus-driven stack, good feedback from users on that strategy
* It's mostly in competition with homegrown solutions, which makes it a bit special
* IRC meetings do not appear on eavesdrop.openstack.org -- no regular meeting, focusing on doing some small group meeting for key topics
* Migrated to StoryBoard
* Limited ML engagement (mostly used for team-wide announcements)

=== Congress ===

Update 2018-07-30 by cdent

* Commits somewhat down from Queens (119 in Queens, 69 in Rocky so far)
* Commits and reviews in the hands of a small but diverse group
* Limited engagement on os-dev, but effective: http://lists.openstack.org/pipermail/openstack-dev/2018-May/130180.html
* IRC logged for both channel and meetings, low but steady traffic.
* Working to address step learning curve that new contributors face by refactoring tempest tests and associated documentation.

=== Cyborg ===
Update: 2018-07-10, TheJulia
* Email responded to by PTL on July 4th. PTL has nothing to really report.
* Activity seems to be moderately in-line with the prior cycle, although one of the cores has since become an independent contributor.
* Cyborg does presently hold a weekly meeting on Wednesdays which does appear active, otherwise IRC is quiet.
** There is no calendar entry on eavesdrop.openstack.org for cyborg, TheJulia let the PTL know.
* Email sent to the PTL to initiate communication on July 2nd

=== Designate ===
Last updated 2018-07-23 by cdent

* Low number of reviews, commits, and contributors but it is somewhat steady.
* A significant amount of the code activity is related to aligning with infra/testing/qa related goals and not feature development. "most of our work at the moment is based around fixing the gate / not breaking future versions"
* ML list use is light, but that's always been the case.
* IRC channel is not busy but is responsive.
* Lurking difficulties:
** As of yet, no support for WSGI, which will break things in a pure py3 environment (due to eventlet)
** Low number of reviews means meeting community goals difficult and distracting.
** Feature requesting is not formalized/transparent, people show up asking "why isn't thing X present?"
** Designate is present in many OpenStack distributions but vendors are not providing active contribution support.

Summary: muddling along, but struggling to address feature demands because of lack of incoming flow of people.

=== Diversity ===
Last updated 2018-07-03 by fungi
* The Diversity WG continues to have semi-weekly meetings in their IRC channel with anywhere from 2 to 8 participants (varying week to week)
* Current activities include finalizing the updated diversity survey and following up on feedback to the foundation event coordinators (preferred pronoun stickers for badges, some way to indicate visibly that you don't wish to be photographed, designated alcohol-free areas at official social events)
* Also communicating with the Women of OpenStack group about the possibility of more closely collaborating on sponsored event activities

=== Documentation ===
Update: 2018-07-18, pabelanger
* Revist meeting format at stein PTG
* To early to report on new office hours, but people still seem to as questions at random times.
* review queue is pretty stable
* suggestion in https://review.openstack.org/#/c/579177/, wondering if the TC could help the docs team promote some of the proposed docs guidelines
* could use more designer resources to work on some outstanding tasks wrt docs.o.o that we previously talked about in Dublin. I'm hoping to get some intern time secured from the Foundation in the coming weeks.
* Email send to PTL to initiate communication

=== Dragonflow ===
Reported issues
* Organizational diversity fragility: Huawei represents 100% of core reviews
* The team did not produce a Queens release. Their last release was 4.0.0 on Sept 1, 2017. Should projects that do not prepare releases be considered official? -- dhellmann
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]

=== ec2-api ===
Reported issues
* Individual fragility: Andrey Pavlov represents 100% of core reviews

Update: July 3, 2018 (cmurphy)
* Low activity due to general maturity
* Still actively used by operators, bugs are reported and fixed
* Three cores, all reportedly active
* Being part of OpenStack is still valued
** Operators are still using the project, so better to be coupled with OpenStack
** Depends on other components of OpenStack, so there is value in collaborating together

=== Freezer ===
Reported issues
* Still uses pycrypto [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131103.html]
* freezer and freezer-web-ui missed the Rocky-2 and Rocky-3 milestones
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]

=== Glance ===

=== Heat ===
Update: 2018-06-28, zaneb

* Under active development
* Only 4 active cores, 3 from Red Hat. This is limiting the amount of development that can be done and the velocity of the project.
** Especially struggling with stable reviews (only 1 active core, and the stable-maint team are the gatekeepers for adding more)
* Active on mailing list and IRC
* Regular IRC meetings
* [https://ethercalc.openstack.org/heat-mox-removal Excellent progress] on the (massive) mox-removal goal in Rocky
* The heat-translator sub-project no longer has any team overlap with the rest of the project, and is struggling for core reviewers. It might be time to [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131688.html consider another home for it].

=== Horizon ===
Update: July 20, cmurphy

* Lost several core reviewers recently
* Some promising new contributors, could become cores if they help with reviews more
* Nearly complete with mox goal
* Focus on cross-project plugins and CI coverage
* Lots of participation in weekly meetings
* Concern about getting help with AngularJS work
** Converting more of horizon to AngularJS is still seen as the right technical direction (it provides a better user experience) but community contribution is suffering from it
** Hard to ask devs from other OpenStack projects to add support for new features in non-Python
** Hard in general to attract new JS devs when OpenStack is mostly Python

=== I18n ===
Update: July 04, emilien

Reported issues: none, yet.
The team changed leadership in Queens.

Queens status:
* 87 modules touched (+87%)
* 17 languages supported (+6%)
* 55 active translators (-14%) (TODO, need to check with PTL if it has an impact)
* 7 companies support (-22%)
I18n team previously had team meetings but decided to have office hours instead.
Usually tracks completion of Rocky community goals.
A lot of collaboration with Doc team.
Dedicated mailing-list: openstack-i18n - pretty busy

Rocky:
* <strike>Help is wanted around doc translation. See https://review.openstack.org/#/c/545377 for example.</strike>

=== Infrastructure ===

=== Interop ===
Last updated 2018-07-03 by fungi
* Only a few active members of the Interop WG reviewing and contributing patches to the openstack/interop repository
* Affiliation is fairly diverse, but with so few active that's probably not really relevant
* Mandated to maintain interoperability guidelines in support of official trademark programs, so the board will likely step in if active participants fall below a minimum viable count
* Heavily dependent on the RefStack and QA teams for their tool development

=== Ironic ===

=== Karbor ===

=== Keystone ===
Update July 3, 2018 (cmurphy)
* High pressure due to being a central part of OpenStack
* Focus on "improving the commons" - policy/RBAC work, unified quota management, application development
* 10 cores with varying levels of activity, nearly all are at most part-time
** Concern over possibility of team burnout

=== Kolla ===
Update: 2018-07-30, TheJulia
* Discussion in IRC with the PTL about a week after initial contact in #openstack-tc
* PTL felt that the team was in a good state, that goals had been progressing.
* Slight increase in review activity/commits, overall seems fairly healthy.

Update: 2018-07-10, TheJulia
* No reply received. Follow-up email sent on 2017-07-10 and contact initiated on IRC.
* Email sent to the PTL to initiate communication on July 2nd

=== Kuryr ===
Reported issues
* Organizational diversity fragility: RedHat represents 79% of core reviews

=== Large Deployment ===
Update: 2018-07-14, pabelanger

=== Loci ===

Reported issues
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]

Update: 2018-07-14, pabelanger
* Email send to PTL to initiate communication

=== Magnum ===

=== Manila ===
Update: June 22, 2018, smcginnis

* Project appears to be in good shape
* Focusing on bug fixes and stabilization rather than any big new features
* Drop of in involvement from EU, particularly from HPE and IBM
* Increase of participation from China makes EU drop off not as much of an issue other than time coverage
** Not a lot of involvement on IRC or weekly meeting though
* Lots of good interest downstream, particularly from HPC and telco communities

=== Masakari ===
Reported issues
* Low activity in Rocky for a "new" project
* Organizational diversity fragility: NTT represents 97% of core reviews

=== Mistral ===

=== Monasca ===

=== Murano ===
* murano and murano-dashboard missed the Rocky-2 milestone

Update 13 June 2018, dhellmann

* Recent US government action against ZTE has had an impact on the team, because ZTE employees are key contributors to the project and the core team. It is unclear how much ZTE will be able to continue to contribute in the future. [https://www.nbcnews.com/politics/congress/senate-blocks-zte-deal-rebuke-trump-deal-n882196]
* The murano-core team has members froM AT&T and Mirantis, as well as ZTE.
* emilien sent email on 2018-07-17

Update 6 Aug 2018, dhellmann

* Rong Zhu responded with some hopeful comments about the ZTE situation improving (and it seems to have) and meaning that team members will be more active on IRC again

=== Nova ===

Update 5 July 2018, dhellmann

* melwitt reports "I can't think of any issues we need help with"

=== Octavia ===
* Feeling a small shortage of contributors (contributions & code review)
* OpenStack-wide "interruptions" affect team heavily
* Moving from screen to systemd affected team for ~4 weeks
* WSGI Implementation took time (and changes) and team feels community goals aren't super constructive to project
* Zuul V3 cutovers (and constant restarts) affect productivity and slow down progress
* Sometimes certain things that should be done the "OpenStack" way such as involving PTLs in decisions don't happen
* Storyboard issues: https://etherpad.openstack.org/p/storyboard-issues

=== Openstack Charms ===
Update: June 20, ttx

* Currently single-vendor (all cores from Canonical), but with some external participation
* Steady activity, keeping up with recent evolution (includes Vault and Gnocchi, integrates Designate with Neutron)
* Holds weekly IRC meetings with rotating chair
* Uses Launchpad, and is likely to stay there as it allows sharing tasks with Ubuntu packaging
* Limited ML engagement (thread left dangling at [http://lists.openstack.org/pipermail/openstack-dev/2018-April/129314.html])

=== OpenStack-Helm ===
Update: June 26, ttx

* Currently single-vendor (all cores from AT&T), but with external participation (SKT, 99cloud, Intel...)
* Increasing activity (412 commits in Rocky so far compared to 513 total in Queens)
* Holds weekly IRC meetings, pretty active discussions
* Migrated to StoryBoard
* Limited ML engagement (mostly used for team-wide announcements)
* OpenStack-Helm is release-independent -- it aims to support Newton -> master and track latest all the time. They are waiting until they reach a certain quality level (and stable interface) before declaring a 1.0. See [https://docs.openstack.org/openstack-helm/latest/specs/osh-1.0-requirements.html requirements for 1.0]. This explains lack of releases.

=== OpenStackAnsible ===

=== OpenStackClient ===
Update: 28 June 2018, dhellmann, cmurphy

* uses IRC and the mailing list but no meetings
* the review team is small, but there are several active reviewers not on the core team yet who are candidates
* there is quite a review backlog, but the PTL is optimistic that adding the new reviewers will help with that
* they are still interested in being included on the help wanted list (hence the "orange" status, for now)

=== Openstacksdk ===
Update: 2018-07-02, TheJulia
* Initial communication with PTL, should expect to follow-up with-in the next few days.

=== Oslo ===

Reported issues

* Most of the more active members are employed by Red Hat, so it would be good to bring in more diverse contributors
* oslo.privsep, taskflow, and oslo.service are used in several significant service projects, but are effectively unmaintained.
* oslo.service has some issues with the WSGI service not working under python3. The plan is to encourage all projects to stop using that feature, deprecate, then remove it.
* taskflow is one of several projects that needs to update to a newer version of networkx, but the API changes in networkx mean reworking some of taskflow. Supporting both versions of the APIs may be complicated.

Update: 12 June 2018, dhellmann

* The team is small, but active and working on recruiting.
* Team produces regular and frequent releases for the maintained libraries
* Team meets weekly using IRC
* Team had both onboarding and project update sessions in Vancouver
* The level of activity within each library varies.
* Several of the libraries are reaching a "stable" state in which they may not see many updates beyond bug fixes. This has spurred a discussion of how to treat projects like that, led by the release management team [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131341.html]

=== Packaging-RPM ===
Reported issues
* Organizational diversity fragility: SUSE represents 77% of core reviews
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]

=== Powervmstackers ===

=== Puppet Openstack ===
Update: 2018-08-06 (cmurphy)
Good progress on important features
* Puppet 5 support
* Debian support
Some frustration with spam changes (compounded over multiple modules)
Tripleo moving away from depending on Puppet so maintenance shifting more toward operators

=== Qinling ===

=== Quality Assurance ===

cdent has started, 2018-07-24

=== Rally ===
Reported issues
* Half on GitHub those days, and unwilling to drop direct branching ACLs
* Individual fragility: Andrey Kurilin represents 56% of commits
* Organizational diversity fragility: GoDaddy represents 97% of core reviews
* It looks like the project may be moving out of gerrit to GitHub? https://github.com/xrally and https://xrally.org -- dhellmann

=== Refstack ===

Reported issues
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]

Last updated 2018-07-03 by fungi
* The core review team has only two active members, both funded directly by the OpenStack Foundation (one reaching the end of that internship)
* The bulk of recent contributions to the main refstack deliverable are from the same two individuals
* Most recent outside development interest has been in the python-tempestconf library for tempest.conf generation, which has also produced some sideline support development in the refstack-client deliverable
* The Refstack effort is considered to be reaching feature-complete state in the coming weeks as some final pieces land, and then will likely be put in maintenance mode from a governance perspective
* The refstack and refstack-client deliverables may make sense to get adopted by the Interop WG so the Refstack team itself can be wound down and officially disbanded
* The python-tempestconf deliverable isn't necessarily a good fit for QA team adoption, but may be looking for an adoptive home or may warrant creation of its own official TC-recognized team

=== Release Management ===

Update: 28 June 2018, dhellmann & smcginnis

* The review work has become easier, but there are still only 3 team members. That leaves succession planning for the PTL role a bit up in the air, and also poses challenges with the members travel to conferences all at the same time.
* Working on a reviewers' guide to help with recruiting.
* Completed adjusting ACLs for all official teams to use the reviewable release process for deliverables that are part of the OpenStack release.

=== Requirements Management ===

* need more reviewers, badly, as discussed a joint leadership meeting in Vancouver

Update: 14 June 2018, dhellmann

* team has recently lost several members
* most work is really down to 3 people (Matt, Dirk, Tony)
* they work for 3 separate companies, but the team is so small that the diversity measures are questionable
* the changes this cycle to stop syncing requirements should lower the review burden somewhat, but the move to python 3 is going to take some work
* meets regularly
* accomplishments this cycle
** stopped syncing dependencies between projects
** working on networkx upgrade
** uncapped eventlet
** uncapped sphinx
** added optional lower-constraints test jobs for project teams that want them

=== Resource Management SIG ===

Update 2018-07-10, cdent. Summary: SIG is idling.

Concerns or Issues:
* While the project had some initial planning at [[Res_Mgmt_SIG]], little has happened since.
* This is likely due to the main participants being overbooked to be able to fit things in.
** cdent is one of those main participants and hasn't had a chance to do anything
* Given the desire for these evaluations to not include participants, cdent being the evaluator is probably not ideal

=== Sahara ===
Update: June 13, emilien

Reported issues: none, yet.
* The team changed leadership in Queens
* Last PTG was virtual
* Most commits in Rocky are from Red Hat (92% of core reviews)
* The team is really small, most of commits are done by 2 contributors and 3 contributors are active in reviews
* Latest survey shows that Sahara is used in production by 3% of deployments and 8% in test phase. 25% of users are interested by Sahara
* Following goals and releases
* Email sent to PTL on June 13th

=== Searchlight ===
Reported issues
* searchlight and searchlight-ui missed the Rocky-1 milestone
* Release forced for searchlight and searchlight-ui for the Rocky-2 milestone; also missed the Rocky-3 milestone
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]

=== Scientific ===
Update: July 17, pabelanger

=== Senlin ===

=== Solum ===
Reported issues
* Individual fragility: Zhurong represents 100% of core reviews
* Zhurong is employed by ZTE and recent US government actions might affecting contributions

=== Storlets ===
Reported issues
* Individual fragility: Kota Tsuyuzaki represents 100% of core reviews

=== Swift ===
Update: July 3, smcginnis

* Team has recently lost two very active long time cores
* Activity has gone down, like many OpenStack projects, but there is still a large list of important work to complete
* Changed their policy to only require one +2
** Change in policy is allowing to land more code
** No bad side effects of this change have been encountered so far
* Some recent progress has been made on Python 3 compatibility

=== Tacker ===
Reported issues
* Individual fragility: Yong Sheng Gong represents 75% of core reviews

=== Telemetry ===
Update: 2018-07-25, cdent
* Only two active cores and contributors (from Red Hat), despite [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131443.html continued value].
* Lowish number of commits and reviews, but about what one would expect for a small and stable project
* Effectively in maintenance mode
* Some potential for greater engagement with Monasca
* The features in ceilometer are being shrunk to meet the needs of the people who are making contributions and there is concern that lack of engagement by others will lead to something breaking.

=== Tricircle ===
Reported issues
* Not set up for zuulv3 so cannot land patches that interact with other repositories? http://lists.openstack.org/pipermail/openstack-dev/2018-June/131643.html
* email sent on July 18th 2018 (emilien)

=== TripleO ===
Update: June 13, emilien

* Mainly Red Hat (99% of core reviews). Some contributors from vendors (storage/network plugins)
* Number of contributors / core reviewers always increasing
* Quite healthy, no problem reported so far

=== Trove ===

Reported issues
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No valid PTL volunteer(s) for Stein.]
* During the public cloud issues session at the Rocky Forum someone in the room raised the question of whether Trove is still actively maintained.
** [https://etherpad.openstack.org/p/YVR-forum-missing-features-pc Missing features in OpenStack for public clouds] forum session notes

Update: June 12, ttx

* The team changed leadership in Rocky
* Zhao Chao handles bulk of commits (51%)
* The new team is small, but pretty alive and active. Needs more contributors to be stable.
* Mostly contributors in China (AWCloud, China Telecom, China Mobile)
* Drop in activity in Rocky: 45 commits by Rocky-2, to compare with the 245 commits in Queens
* Organizational diversity: 53% of commits are from AWCloud. Reviews are shared between 23% China Telecom, 19% China Mobile, 19% Awcloud. Last cycle with 41% IBM.
* Regular weekly meetings, well run with clear documentation of outcomes
* Tracks completion of Rocky community goals
* A few ML threads, but mostly to discuss things external to the team (new meeting time, stable maint team composition)
* Missed Rocky-2 milestone, but mostly due to a [http://eavesdrop.openstack.org/meetings/trove/2018/trove.2018-06-06-14.00.log.html#l-95 misunderstanding of release policy].
* No project update in Vancouver, but was discussed in meeting: sadly [http://eavesdrop.openstack.org/meetings/trove/2018/trove.2018-05-16-14.00.log.html#l-20 no team member was present].
* Reached out to PTL by email on June 12 for additional concerns / questions.

=== Upgrade SIG ===
WIP (emilien)

=== Vitrage ===

Reported issues
* Organizational diversity fragility: Nokia represents 80% of core reviews
* Affected by ZTE situation

Update 2018-07-18 (dhellmann)
* Meeting regularly on IRC
* One of their cores who works for ZTE has been absent for a while, but has returned to contributing.
* They usually have a hands-on lab at summits to attract users and potential contributors.
* The next PTG aligns with Jewish New Year, so many of their contributors will not be attending. They intend to have a virtual PTG instead.
* The CFP for the Berlin summit caught them off guard because it was so early, and they found it a bit hard to plan discussions because they don't even know what the next release will hold. They did submit a few talk proposals.
* Vitrage, by its nature, relies heavily on other projects. They have had good success working with other project teams, but do frequently struggle to find accurate and complete developer-oriented documentation for some of them.

=== Watcher ===
Update: 2018-07-10 TheJulia
* PTL inquires if there is any way for the TC to assist with raising awareness of Watcher.
* Actively recruiting and seeking out new contributors, and anticipating to meet community goals. Anticipating to create new roadmap at the PTG.
* Contributions appear mainly from NEC at this time, but history shows a moderately more diverse contributor base.
* PTL indicates core team is critically small, and that they have lost two out of five cores due to the ZTE withdraw due to the conflict with the US Government. Review metrics line up with what would be expected from loss of 40% of the core reviewers.
* Email sent to the PTL to initiate communication on July 2nd

=== Winstackers ===
Reported issues
* Individual fragility: Claudiu Belu represents 100% of core reviews
* [http://lists.openstack.org/pipermail/openstack-dev/2018-August/132690.html No PTL volunteer(s) for Stein.]

=== Zaqar ===
Reported issues
* zaqar and zaqar-ui missed the Rocky-2 milestone

=== Zun ===

* PTL and ~25% of commits (in Queens) are from ZTE
* PTL non-responsive to email so far
* Regular meetings happening, mostly chaired by previous PTL (although current PTL has appeared on occasion)
* Healthy-looking pace of development still happening
* Loosened review policy to only require 1 reviewer: http://lists.openstack.org/pipermail/openstack-dev/2018-July/132582.html

OpenStack health tracker

2018-07-20T08:52:02Z

Colleen Murphy: /* Status updates */

'''This page is a live document and contains notes from TC members working with project teams to ensure they have everything they need and are not running into issues. This information is not necessarily complete.'''

TC members are attached as liaisons to each of the project teams, [https://governance.openstack.org/sigs/ SIGs], or [https://governance.openstack.org/uc/ UC working groups]. The idea is for these liaisons to keep up with the general health of the group, understand any issues they encounter, and help them work with the TC on solutions if necessary. Some TC members may be more active within the group than the basic liaison responsibilities imply, but that is not required.

Liaisons should monitor their groups by:
* reading meeting logs or participating in meetings
* watching summit "project update" videos
* reading relevant messages on the mailing list
* talking with the PTL, chair, and other group members
* checking contribution rates and review turnaround times

== Liaisons ==
=== SIGs ===

{| class="wikitable"
|-
! Group !! TC members
|-
| API
|| mugsie
|-
| First Contact
|| fungi
|-
| K8s
|| dims
|-
| Meta
|| dhellmann
|-
| Resource Management
|| cdent
|-
| Scientific
|| pabelanger
|-
| Security
|| fungi
|-
| Self-healing
|| zaneb
|-
| Upgrade
|| emilien
|}

=== Working Groups ===

{| class="wikitable"
|-
! Group !! TC members
|-
| App Dev Enablement
|| zaneb
|-
| [[Diversity]]
|| fungi
|-
| Enterprise
||
|-
| Fault Genes
||
|-
| [[InteropWG|Interop]]
|| dims, fungi
|-
| LCOO
||
|-
| Large Deployment
|| pabelanger
|-
| Edge/Massively Distributed Clouds
|| ttx
|-
| Operators Telecom/NFV
|| smcginnis
|-
| Ops Tags
|| smcginnis
|-
| Product
||
|-
| [[ProfessionalCertification]]
||
|-
| Public Cloud
|| ttx
|}

=== Project Teams ===

{| class="wikitable"
|-
! Group !! TC members
|-
| Barbican
|| fungi, ttx
|-
| Blazar
|| cmurphy, mnaser
|-
| Chef Openstack
|| pabelanger, mnaser
|-
| Cinder
|| smcginnis, dims
|-
| Cloudkitty
|| ttx, dims
|-
| Congress
|| cdent, fungi
|-
| Cyborg
|| ttx, TheJulia
|-
| Designate
|| cmurphy, cdent
|-
| Documentation
|| dhellmann, pabelanger
|-
| Dragonflow
|| dims, cdent
|-
| Ec2-Api
|| TheJulia, cmurphy
|-
| Freezer
|| ttx, mugsie
|-
| Glance
|| smcginnis, mugsie
|-
| Heat
|| zaneb, emilien
|-
| Horizon
|| cmurphy, smcginnis
|-
| I18n
|| emilien, cdent
|-
| Infrastructure
|| fungi, mnaser
|-
| Ironic
|| mugsie, fungi
|-
| Karbor
|| ttx, mugsie
|-
| Keystone
|| fungi,cmurphy
|-
| Kolla
|| dims, TheJulia
|-
| Kuryr
|| dims, cdent
|-
| Loci
|| pabelanger, dims
|-
| Magnum
|| mnaser, dims
|-
| Manila
|| smcginnis, pabelanger
|-
| Masakari
|| pabelanger, cdent
|-
| Mistral
|| zaneb, cmurphy
|-
| Monasca
|| zaneb, TheJulia
|-
| Murano
|| dhellmann, emilien
|-
| Neutron
|| mugsie, dims
|-
| Nova
|| mnaser, dhellmann
|-
| Octavia
|| mnaser, mugsie
|-
| Openstack Charms
|| ttx, emilien
|-
| Openstack-Helm
|| ttx, dims
|-
| Openstackansible
|| mnaser, smcginnis
|-
| OpenStackClient
|| dhellmann, cmurphy
|-
| Openstacksdk
|| pabelanger, TheJulia
|-
| Oslo
|| dhellmann, mugsie
|-
| Packaging-Rpm
|| cmurphy, zaneb
|-
| Powervmstackers
|| emilien, TheJulia
|-
| Puppet Openstack
|| cmurphy, pabelanger
|-
| Qinling
|| zaneb, TheJulia
|-
| Quality Assurance
|| cdent, fungi
|-
| Rally
|| pabelanger, mnaser
|-
| Refstack
|| fungi, TheJulia
|-
| Release Management
|| dhellmann, smcginnis
|-
| Requirements
|| fungi, dhellmann
|-
| Sahara
|| emilien, pabelanger
|-
| Searchlight
|| mugsie, mnaser
|-
| Security
|| fungi, zaneb
|-
| Senlin
|| zaneb, smcginnis
|-
| Solum
|| zaneb, mnaser
|-
| Stable Branch Maintenance
|| fungi, smcginnis
|-
| Storlets
|| ttx, dhellmann
|-
| Swift
|| smcginnis, mugsie
|-
| Tacker
|| TheJulia, emilien
|-
| Telemetry
|| cdent, dhellmann
|-
| Tricircle
|| emilien, cdent
|-
| Tripleo
|| emilien, cmurphy
|-
| Trove
|| ttx, mugsie
|-
| Vitrage
|| emilien, dhellmann
|-
| Watcher
|| smcginnis, TheJulia
|-
| Winstackers
|| pabelanger, cdent
|-
| Zaqar
|| zaneb, dims
|-
| Zun
|| zaneb, ttx
|}

== Status updates ==

=== Blazar ===
Reported issues
* Organizational diversity fragility: NTT represents 79% of core reviews
* Requested to be listed under project navigator on openstack.org (ttx mentioned that should be taken care of)
* A lot of work seems to be going around updating document linking

=== Chef OpenStack ===
Reported issues
* Individual fragility: Samuel Cassiba represents 75% of commits

=== Cinder ===
Update: June 22, 2018, smcginnis

* Some drop off in participation by some cores, but still active enough not to raise any red flags
* Overall less community involvement
* Project may just be "stable" and doesn't need as much activity as the past
* Still a lot of bug fix work to be done, but no major new features on the roadmap

=== Cloudkitty ===
Updated July 19, 2018 (ttx)

* Currently single-vendor (all cores from ObjectifLibre), failure to retain onboarded people
* Activity is low but stable (33 commits in Rocky so far compared to 57 total in Queens)
* Works to support standalone operation and reusability in a Prometheus-driven stack, good feedback from users on that strategy
* It's mostly in competition with homegrown solutions, which makes it a bit special
* IRC meetings do not appear on eavesdrop.openstack.org -- no regular meeting, focusing on doing some small group meeting for key topics
* Migrated to StoryBoard
* Limited ML engagement (mostly used for team-wide announcements)

=== Congress ===

Update in progress (cdent)

* Email sent to PTL to start conversation
* Commits somewhat down from Queens (119 in Queens, 69 in Rocky so far)
* Commits and reviews in the hands of a small but diverse group
* Limited engagement on os-dev, but effective: http://lists.openstack.org/pipermail/openstack-dev/2018-May/130180.html
* IRC logged for both channel and meetings, low but steady traffic.

=== Cyborg ===
Update: 2018-07-10, TheJulia
* Email responded to by PTL on July 4th. PTL has nothing to really report.
* Activity seems to be moderately in-line with the prior cycle, although one of the cores has since become an independent contributor.
* Cyborg does presently hold a weekly meeting on Wednesdays which does appear active, otherwise IRC is quiet.
** There is no calendar entry on eavesdrop.openstack.org for cyborg, TheJulia let the PTL know.
* Email sent to the PTL to initiate communication on July 2nd

=== Designate ===
Update in progress, cdent

=== Diversity ===
Last updated 2018-07-03 by fungi
* The Diversity WG continues to have semi-weekly meetings in their IRC channel with anywhere from 2 to 8 participants (varying week to week)
* Current activities include finalizing the updated diversity survey and following up on feedback to the foundation event coordinators (preferred pronoun stickers for badges, some way to indicate visibly that you don't wish to be photographed, designated alcohol-free areas at official social events)
* Also communicating with the Women of OpenStack group about the possibility of more closely collaborating on sponsored event activities

=== Documentation ===
Update: 2018-07-18, pabelanger
* Revist meeting format at stein PTG
* To early to report on new office hours, but people still seem to as questions at random times.
* review queue is pretty stable
* suggestion in https://review.openstack.org/#/c/579177/, wondering if the TC could help the docs team promote some of the proposed docs guidelines
* could use more designer resources to work on some outstanding tasks wrt docs.o.o that we previously talked about in Dublin. I'm hoping to get some intern time secured from the Foundation in the coming weeks.
* Email send to PTL to initiate communication

=== Dragonflow ===
Reported issues
* Organizational diversity fragility: Huawei represents 100% of core reviews
* The team did not produce a Queens release. Their last release was 4.0.0 on Sept 1, 2017. Should projects that do not prepare releases be considered official? -- dhellmann

=== ec2-api ===
Reported issues
* Individual fragility: Andrey Pavlov represents 100% of core reviews

Update: July 3, 2018 (cmurphy)
* Low activity due to general maturity
* Still actively used by operators, bugs are reported and fixed
* Three cores, all reportedly active
* Being part of OpenStack is still valued
** Operators are still using the project, so better to be coupled with OpenStack
** Depends on other components of OpenStack, so there is value in collaborating together

=== Freezer ===
Reported issues
* Still uses pycrypto [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131103.html]
* freezer and freezer-web-ui missed the Rocky-2 milestone

=== Heat ===
Update: 2018-06-28, zaneb

* Under active development
* Only 4 active cores, 3 from Red Hat. This is limiting the amount of development that can be done and the velocity of the project.
** Especially struggling with stable reviews (only 1 active core, and the stable-maint team are the gatekeepers for adding more)
* Active on mailing list and IRC
* Regular IRC meetings
* [https://ethercalc.openstack.org/heat-mox-removal Excellent progress] on the (massive) mox-removal goal in Rocky
* The heat-translator sub-project no longer has any team overlap with the rest of the project, and is struggling for core reviewers. It might be time to [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131688.html consider another home for it].

=== Horizon ===
Update: July 20, cmurphy

* Lost several core reviewers recently
* Some promising new contributors, could become cores if they help with reviews more
* Nearly complete with mox goal
* Focus on cross-project plugins and CI coverage
* Lots of participation in weekly meetings
* Concern about getting help with AngularJS work
** Converting more of horizon to AngularJS is still seen as the right technical direction (it provides a better user experience) but community contribution is suffering from it
** Hard to ask devs from other OpenStack projects to add support for new features in non-Python
** Hard in general to attract new JS devs when OpenStack is mostly Python

=== I18n ===
Update: July 04, emilien

Reported issues: none, yet.
The team changed leadership in Queens.

Queens status:
* 87 modules touched (+87%)
* 17 languages supported (+6%)
* 55 active translators (-14%) (TODO, need to check with PTL if it has an impact)
* 7 companies support (-22%)
I18n team previously had team meetings but decided to have office hours instead.
Usually tracks completion of Rocky community goals.
A lot of collaboration with Doc team.
Dedicated mailing-list: openstack-i18n - pretty busy

Rocky:
* <strike>Help is wanted around doc translation. See https://review.openstack.org/#/c/545377 for example.</strike>

=== Interop ===
Last updated 2018-07-03 by fungi
* Only a few active members of the Interop WG reviewing and contributing patches to the openstack/interop repository
* Affiliation is fairly diverse, but with so few active that's probably not really relevant
* Mandated to maintain interoperability guidelines in support of official trademark programs, so the board will likely step in if active participants fall below a minimum viable count
* Heavily dependent on the RefStack and QA teams for their tool development

=== Keystone ===
Update July 3, 2018 (cmurphy)
* High pressure due to being a central part of OpenStack
* Focus on "improving the commons" - policy/RBAC work, unified quota management, application development
* 10 cores with varying levels of activity, nearly all are at most part-time
** Concern over possibility of team burnout

=== Kolla ===
Update: 2018-07-10, TheJulia
* No reply received. Follow-up email sent on 2017-07-10 and contact initiated on IRC.
* Email sent to the PTL to initiate communication on July 2nd

=== Kuryr ===
Reported issues
* Organizational diversity fragility: RedHat represents 79% of core reviews

=== Large Deployment ===
Update: 2018-07-14, pabelanger

=== Loci ===
Update: 2018-07-14, pabelanger
* Email send to PTL to initiate communication

=== Manila ===
Update: June 22, 2018, smcginnis

* Project appears to be in good shape
* Focusing on bug fixes and stabilization rather than any big new features
* Drop of in involvement from EU, particularly from HPE and IBM
* Increase of participation from China makes EU drop off not as much of an issue other than time coverage
** Not a lot of involvement on IRC or weekly meeting though
* Lots of good interest downstream, particularly from HPC and telco communities

=== Masakari ===
Reported issues
* Low activity in Rocky for a "new" project
* Organizational diversity fragility: NTT represents 97% of core reviews

=== Murano ===
* murano and murano-dashboard missed the Rocky-2 milestone

Update 13 June 2018, dhellmann

* Recent US government action against ZTE has had an impact on the team, because ZTE employees are key contributors to the project and the core team. It is unclear how much ZTE will be able to continue to contribute in the future. [https://www.nbcnews.com/politics/congress/senate-blocks-zte-deal-rebuke-trump-deal-n882196]
* The murano-core team has members froM AT&T and Mirantis, as well as ZTE.
* emilien sent email on 2018-07-17

=== Octavia ===
* Feeling a small shortage of contributors (contributions & code review)
* OpenStack-wide "interruptions" affect team heavily
* Moving from screen to systemd affected team for ~4 weeks
* WSGI Implementation took time (and changes) and team feels community goals aren't super constructive to project
* Zuul V3 cutovers (and constant restarts) affect productivity and slow down progress
* Sometimes certain things that should be done the "OpenStack" way such as involving PTLs in decisions don't happen
* Storyboard issues: https://etherpad.openstack.org/p/storyboard-issues

=== Openstack Charms ===
Update: June 20, ttx

* Currently single-vendor (all cores from Canonical), but with some external participation
* Steady activity, keeping up with recent evolution (includes Vault and Gnocchi, integrates Designate with Neutron)
* Holds weekly IRC meetings with rotating chair
* Uses Launchpad, and is likely to stay there as it allows sharing tasks with Ubuntu packaging
* Limited ML engagement (thread left dangling at [http://lists.openstack.org/pipermail/openstack-dev/2018-April/129314.html])

=== OpenStackClient ===
Update: 28 June 2018, dhellmann, cmurphy

* uses IRC and the mailing list but no meetings
* the review team is small, but there are several active reviewers not on the core team yet who are candidates
* there is quite a review backlog, but the PTL is optimistic that adding the new reviewers will help with that
* they are still interested in being included on the help wanted list (hence the "orange" status, for now)

=== Openstacksdk ===
Update: 2018-07-02, TheJulia
* Initial communication with PTL, should expect to follow-up with-in the next few days.

=== OpenStack-Helm ===
Update: June 26, ttx

* Currently single-vendor (all cores from AT&T), but with external participation (SKT, 99cloud, Intel...)
* Increasing activity (412 commits in Rocky so far compared to 513 total in Queens)
* Holds weekly IRC meetings, pretty active discussions
* Migrated to StoryBoard
* Limited ML engagement (mostly used for team-wide announcements)
* OpenStack-Helm is release-independent -- it aims to support Newton -> master and track latest all the time. They are waiting until they reach a certain quality level (and stable interface) before declaring a 1.0. See [https://docs.openstack.org/openstack-helm/latest/specs/osh-1.0-requirements.html requirements for 1.0]. This explains lack of releases.

=== Oslo ===

Reported issues

* Most of the more active members are employed by Red Hat, so it would be good to bring in more diverse contributors
* oslo.privsep, taskflow, and oslo.service are used in several significant service projects, but are effectively unmaintained.
* oslo.service has some issues with the WSGI service not working under python3. The plan is to encourage all projects to stop using that feature, deprecate, then remove it.
* taskflow is one of several projects that needs to update to a newer version of networkx, but the API changes in networkx mean reworking some of taskflow. Supporting both versions of the APIs may be complicated.

Update: 12 June 2018, dhellmann

* The team is small, but active and working on recruiting.
* Team produces regular and frequent releases for the maintained libraries
* Team meets weekly using IRC
* Team had both onboarding and project update sessions in Vancouver
* The level of activity within each library varies.
* Several of the libraries are reaching a "stable" state in which they may not see many updates beyond bug fixes. This has spurred a discussion of how to treat projects like that, led by the release management team [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131341.html]

=== Packaging-RPM ===
Reported issues
* Organizational diversity fragility: SUSE represents 77% of core reviews

=== Puppet Openstack ===
Update: 2018-07-14, pabelanger
* Email send to PTL to initiate communication

=== Rally ===
Reported issues
* Half on GitHub those days, and unwilling to drop direct branching ACLs
* Individual fragility: Andrey Kurilin represents 56% of commits
* Organizational diversity fragility: GoDaddy represents 97% of core reviews
* It looks like the project may be moving out of gerrit to GitHub? https://github.com/xrally and https://xrally.org -- dhellmann

=== Refstack ===
Last updated 2018-07-03 by fungi
* The core review team has only two active members, both funded directly by the OpenStack Foundation (one reaching the end of that internship)
* The bulk of recent contributions to the main refstack deliverable are from the same two individuals
* Most recent outside development interest has been in the python-tempestconf library for tempest.conf generation, which has also produced some sideline support development in the refstack-client deliverable
* The Refstack effort is considered to be reaching feature-complete state in the coming weeks as some final pieces land, and then will likely be put in maintenance mode from a governance perspective
* The refstack and refstack-client deliverables may make sense to get adopted by the Interop WG so the Refstack team itself can be wound down and officially disbanded
* The python-tempestconf deliverable isn't necessarily a good fit for QA team adoption, but may be looking for an adoptive home or may warrant creation of its own official TC-recognized team

=== Release Management ===

Update: 28 June 2018, dhellmann & smcginnis

* The review work has become easier, but there are still only 3 team members. That leaves succession planning for the PTL role a bit up in the air, and also poses challenges with the members travel to conferences all at the same time.
* Working on a reviewers' guide to help with recruiting.
* Completed adjusting ACLs for all official teams to use the reviewable release process for deliverables that are part of the OpenStack release.

=== Requirements Management ===

* need more reviewers, badly, as discussed a joint leadership meeting in Vancouver

Update: 14 June 2018, dhellmann

* team has recently lost several members
* most work is really down to 3 people (Matt, Dirk, Tony)
* they work for 3 separate companies, but the team is so small that the diversity measures are questionable
* the changes this cycle to stop syncing requirements should lower the review burden somewhat, but the move to python 3 is going to take some work
* meets regularly
* accomplishments this cycle
** stopped syncing dependencies between projects
** working on networkx upgrade
** uncapped eventlet
** uncapped sphinx
** added optional lower-constraints test jobs for project teams that want them

=== Resource Management SIG ===

Update 2018-07-10, cdent. Summary: SIG is idling.

Concerns or Issues:
* While the project had some initial planning at [[Res_Mgmt_SIG]], little has happened since.
* This is likely due to the main participants being overbooked to be able to fit things in.
** cdent is one of those main participants and hasn't had a chance to do anything
* Given the desire for these evaluations to not include participants, cdent being the evaluator is probably not ideal

=== Sahara ===
Update: June 13, emilien

Reported issues: none, yet.
* The team changed leadership in Queens
* Last PTG was virtual
* Most commits in Rocky are from Red Hat (92% of core reviews)
* The team is really small, most of commits are done by 2 contributors and 3 contributors are active in reviews
* Latest survey shows that Sahara is used in production by 3% of deployments and 8% in test phase. 25% of users are interested by Sahara
* Following goals and releases
* Email sent to PTL on June 13th

=== Searchlight ===
Reported issues
* searchlight and searchlight-ui missed the Rocky-1 milestone
* Release forced for searchlight and searchlight-ui for the Rocky-2 milestone

=== Scientific ===
Update: July 17, pabelanger

=== Solum ===
Reported issues
* Individual fragility: Zhurong represents 100% of core reviews
* Zhurong is employed by ZTE and recent US government actions might affecting contributions

=== Storlets ===
Reported issues
* Individual fragility: Kota Tsuyuzaki represents 100% of core reviews

=== Swift ===
Update: July 3, smcginnis

* Team has recently lost two very active long time cores
* Activity has gone down, like many OpenStack projects, but there is still a large list of important work to complete
* Changed their policy to only require one +2
** Change in policy is allowing to land more code
** No bad side effects of this change have been encountered so far
* Some recent progress has been made on Python 3 compatibility

=== Tacker ===
Reported issues
* Individual fragility: Yong Sheng Gong represents 75% of core reviews

=== Telemetry ===
Update: June 21, cdent, WIP
* Only two active cores and contributors, despite [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131443.html continued value].
* more to come

=== Tricircle ===
Reported issues
* Not set up for zuulv3 so cannot land patches that interact with other repositories? http://lists.openstack.org/pipermail/openstack-dev/2018-June/131643.html
* email sent on July 18th 2018 (emilien)

=== TripleO ===
Update: June 13, emilien

* Mainly Red Hat (99% of core reviews). Some contributors from vendors (storage/network plugins)
* Number of contributors / core reviewers always increasing
* Quite healthy, no problem reported so far

=== Trove ===
Update: June 12, ttx

* The team changed leadership in Rocky
* Zhao Chao handles bulk of commits (51%)
* The new team is small, but pretty alive and active. Needs more contributors to be stable.
* Mostly contributors in China (AWCloud, China Telecom, China Mobile)
* Drop in activity in Rocky: 45 commits by Rocky-2, to compare with the 245 commits in Queens
* Organizational diversity: 53% of commits are from AWCloud. Reviews are shared between 23% China Telecom, 19% China Mobile, 19% Awcloud. Last cycle with 41% IBM.
* Regular weekly meetings, well run with clear documentation of outcomes
* Tracks completion of Rocky community goals
* A few ML threads, but mostly to discuss things external to the team (new meeting time, stable maint team composition)
* Missed Rocky-2 milestone, but mostly due to a [http://eavesdrop.openstack.org/meetings/trove/2018/trove.2018-06-06-14.00.log.html#l-95 misunderstanding of release policy].
* No project update in Vancouver, but was discussed in meeting: sadly [http://eavesdrop.openstack.org/meetings/trove/2018/trove.2018-05-16-14.00.log.html#l-20 no team member was present].
* Reached out to PTL by email on June 12 for additional concerns / questions.

=== Upgrade SIG ===
WIP (emilien)

=== Vitrage ===

Reported issues
* Organizational diversity fragility: Nokia represents 80% of core reviews
* Affected by ZTE situation

Update 2018-07-18 (dhellmann)
* Meeting regularly on IRC
* One of their cores who works for ZTE has been absent for a while, but has returned to contributing.
* They usually have a hands-on lab at summits to attract users and potential contributors.
* The next PTG aligns with Jewish New Year, so many of their contributors will not be attending. They intend to have a virtual PTG instead.
* The CFP for the Berlin summit caught them off guard because it was so early, and they found it a bit hard to plan discussions because they don't even know what the next release will hold. They did submit a few talk proposals.
* Vitrage, by its nature, relies heavily on other projects. They have had good success working with other project teams, but do frequently struggle to find accurate and complete developer-oriented documentation for some of them.

=== Watcher ===
Update: 2018-07-10 TheJulia
* PTL inquires if there is any way for the TC to assist with raising awareness of Watcher.
* Actively recruiting and seeking out new contributors, and anticipating to meet community goals. Anticipating to create new roadmap at the PTG.
* Contributions appear mainly from NEC at this time, but history shows a moderately more diverse contributor base.
* PTL indicates core team is critically small, and that they have lost two out of five cores due to the ZTE withdraw due to the conflict with the US Government. Review metrics line up with what would be expected from loss of 40% of the core reviewers.
* Email sent to the PTL to initiate communication on July 2nd

=== Winstackers ===
Reported issues
* Individual fragility: Claudiu Belu represents 100% of core reviews

=== Zaqar ===
Reported issues
* zaqar and zaqar-ui missed the Rocky-2 milestone

=== Zun ===

* PTL and ~25% of commits (in Queens) are from ZTE
* PTL non-responsive to email so far
* Regular meetings happening, mostly chaired by previous PTL (although current PTL has appeared on occasion)
* Healthy-looking pace of development still happening

Technical Committee Tracker

2018-07-17T13:30:07Z

Colleen Murphy: /* Scheduling PTL & TC elections for Stein */

The OpenStack Technical Committee is one of the [https://governance.openstack.org governing bodies] of the OpenStack project. You can find more information about it, such as the list of its [https://governance.openstack.org/tc/ current members] or its [https://governance.openstack.org/tc/reference/charter.html governance charter], on the OpenStack TC governance website at https://governance.openstack.org/tc/ .

This page tracks the various governance changes being proposed and the various initiatives the Technical Committee is pursuing. We hold office hours at [https://governance.openstack.org/tc/#office-hours various times] during the week on the [http://eavesdrop.openstack.org/irclogs/%23openstack-tc/ #openstack-tc] IRC channel. Conversation starters for the office hours are [https://etherpad.openstack.org/p/tc-office-hour-conversation-starters here].

Other tasks can be found in [https://storyboard.openstack.org/#!/project/923 the storyboard project].

'''Status last updated: {{REVISIONYEAR}}/{{REVISIONMONTH}}/{{REVISIONDAY2}}'''

== Project team changes ==

== Documentation Changes ==

== Other Initiatives ==

=== Adjutant official project status ===
Drivers: zaneb

Status: Under discussion

The Adjutant team will not be present at the forum, but we will discuss our approach to reviewing team applications in general during the TC session about project "boundaries" [https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21739/official-projects-and-the-boundary-of-what-is-openstack] and Adjutant in particular on Thursday afternoon [https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21752/adjutant-official-project-status]

References
* [https://review.openstack.org/553643 project team application]

=== Allow projects to drop py27 support in the PTI ===
Drivers: mugsie, dhellmann

Status: Under discussion

References
* [https://review.openstack.org/561922 PTI documentation change]
* [https://review.openstack.org/#/c/571011/ governance resolution describing the deprecation timeline] APPROVED
* [https://etherpad.openstack.org/p/YVR-python-2-deprecation-timeline Rocky Forum session notes]
* [http://lists.openstack.org/pipermail/openstack-dev/2018-May/130824.html summary of Rocky Forum discussion]
* [https://review.openstack.org/#/c/575933/ python 3 as default goal]

=== Starting work on constellations ===

Drivers:

Status: Under discussion

References
* [http://lists.openstack.org/pipermail/openstack-dev/2018-May/130068.html openstack-dev mailing list post]
* [http://git.openstack.org/cgit/openstack/constellations/ new git repository to hold the docs]
* [https://review.openstack.org/#/c/565466/ first draft of scientific computing constellation]

=== Clarify new project requirements for affiliation diversity ===
Drivers: zaneb

Status: Under discussion

References
* https://review.openstack.org/567944

=== Adding a key manager to base services ===
Drivers: fungi

Status: Discussing going beyond "castellan-compatible"

References
* https://etherpad.openstack.org/p/BOS-forum-key-management
* ML thread: http://lists.openstack.org/pipermail/openstack-dev/2018-May/130567.html
* https://review.openstack.org/572656 castellan-compatible key store - APPROVED

=== Improving the visibility of status updates and announcements ===
Drivers: dhellmann, cdent, ttx

Status: In progress

We are investigating mailman 3, blogging, and Matrix, among other solutions.

=== Correction to TC member election section of bylaws ===
Drivers: fungi, dhellmann

Status: On hold until the next Foundation vote

This was discussed in the joint leadership meeting in Vancouver. The change requires a member vote, and the Board passed a resolution allowing the Foundation Secretary to propose the bylaws change as part of the next Board election (early 2019). We anticipate other bylaws changes at the same time.

Section [https://www.openstack.org/legal/technical-committee-member-policy/ 3.b.i] reads "An Individual Member is an ATC who has..." but should read "An ATC is an Individual Member who has…"

=== StarlingX ===
Drivers: mnaser, EmilienM

Status: [https://storyboard.openstack.org/#!/story/2002123 In progress]

References
* [http://lists.openstack.org/pipermail/openstack-dev/2018-May/130715.html ML thread following up from summit]
* [http://lists.openstack.org/pipermail/openstack-dev/2018-May/130913.html ML thread post-summit discussions]
* [https://review.openstack.org/#/c/569562/ project-config change to import some of the repositories]

=== Murano Team Status ===
Drivers: dhellmann

Status: On hold

With ZTE's future at question, a Murano team member contacted me about the future of the project. I am currently waiting for the question to be raised in an email thread.

=== Organizational diversity tags ===
Drivers: ttx, mnaser

Status: Under discussion

References
* [http://lists.openstack.org/pipermail/openstack-dev/2018-May/130776.html openstack-dev mailing list thread raising the topic]
* removing the tags: https://review.openstack.org/#/c/579870/
* team "fragility" stats script: https://review.openstack.org/#/c/579142/

=== Clarifying the terms of service for hosted projects ===
Drivers: zaneb

Status: Under discussion

References
* [http://lists.openstack.org/pipermail/openstack-dev/2018-May/130807.html openstack-dev mailing list thread raising the topic]

=== Technical Vision for OpenStack ===
Drivers: zaneb, ttx, cdent

Status: Early

Zane offered to start creating a "technical vision" for OpenStack to help clarify the boundary for where projects fit into OpenStack and where they may not.

References
* [https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21739/official-projects-and-the-boundary-of-what-is-openstack Rocky Forum session]
* https://etherpad.openstack.org/p/tech-vision-2018

=== Stein Series Goals ===
Drivers: smcginnis

Status: Early

Sean organized a session at the Rocky Forum to discuss improving our goal selection process and specific goals for Stein.

References
* [https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21738/s-release-goals Rocky Forum session]

=== Anti-nitpicking Cultural Change ===
Drivers: TheJulia, ttx

Status: In progress

References
* [http://lists.openstack.org/pipermail/openstack-dev/2018-May/130802.html openstack-dev mailing list thread]
* [https://review.openstack.org/#/c/570940/ principle about valuing peer review] APPROVED

=== Trove Project Health ===
Drivers: ttx, theJulia, mugsie?

Status: In progress

During the public cloud issues session at the Rocky Forum someone in the room raised the question of whether Trove is still actively maintained.

ttx looked up Trove as part of the "liaison" duties -- at first glance it appears to be alive and kicking. Will report more when I know more.

References
* [https://etherpad.openstack.org/p/YVR-forum-missing-features-pc Missing features in OpenStack for public clouds] forum session notes

=== tags indicating the upgrade support in deployment tools ===
Drivers: ttx

Status: New

During the FFU session at the Rocky Forum, Dan Smith and David Medberry indicated interest in defining tags to describe what upgrade features deployment tools have.

References
* [https://etherpad.openstack.org/p/YVR-forum-fast-forward-upgrades Rocky Forum session notes]

=== Reviewing the TC Vision ===
Drivers: ttx, EmilienM, fungi

Status: [https://storyboard.openstack.org/#!/story/2002132 In progress]

References
* [https://etherpad.openstack.org/p/YVR-tc-retrospective TC Retrospective Notes from Rocky Forum]

=== Reviewing TC Office Hour Times and Locations ===
Drivers: dhellmann

Status: New

During the retrospective at the Rocky Forum we talked about changing our office hour times or using different tools to make them more accessible.

References
* [https://etherpad.openstack.org/p/YVR-tc-retrospective TC Retrospective Notes from Rocky Forum]

=== Actively Monitoring Teams ===
Drivers: dhellmann

Status: In process

During the retrospective at the Rocky Forum we discussed more actively engaging with project teams and SIGs to anticipate issues we can help resolve.

References
* [https://etherpad.openstack.org/p/YVR-tc-retrospective TC Retrospective Notes from Rocky Forum]
* [[OpenStack_health_tracker]]

=== Status of Electorate ===
Drivers:

Status: New

During the retrospective at the Rocky Forum we discussed the status of the TC electorate, and what is perceived as a low level of engagement. This needs a bit more research to compare recent elections so we can understand how things stand, and then we should talk about ways to improve the situation.

References
* [https://etherpad.openstack.org/p/YVR-tc-retrospective TC Retrospective Notes from Rocky Forum]

=== Improving the help-wanted list ===
Drivers: Sean, Graham, Dims, and Julia

Board support: Allison Randal, Alan Clark, Prakash Ramchandran, Chris Price, and Johan Christenson

Status: New

During the Board/TC/UC meeting at Vancouver, we came up with an idea on what we can put together a better way to ask platinum/gold and other companies in the eco system for help (crossing traditional job descriptions and volunteer/skill match websites)

References
* [https://etherpad.openstack.org/p/job-description-template Sample Job description template]

=== project infrastructure governance proposal ===
Drivers: dhellmann

Status: Under discussion

corvus started a discussion about the relationship between the foundation projects and the infrastructure management team as that team shifts from being governed by the TC to being a foundation-wide project.

References
* http://lists.openstack.org/pipermail/openstack-dev/2018-May/130896.html

=== finding help for the unified CLI team ===
Drivers:

Status: Needs a driver

During the office hours on 7 June we talked about adding OSC to the "help wanted" list. We decided we did not have enough information about what the team needs to write it up yet, so we need someone to gather that information and to propose the addition.

=== Update PTI around project doc translation and PDF ===
Drivers:

Status: Under discussion

References:
* https://review.openstack.org/572559

=== Project team guide: add "technical design tenets" chapter ===

Drivers: ttx

Status: Under discussion

We need a place to explain things like base services (external services you can assume will be around and therefore you don't need to reinvent locally) and other basic design tenets.

References:
https://storyboard.openstack.org/#!/story/2002611

=== Scheduling PTL & TC elections for Stein ===

Drivers: cmurphy

Status: Under discussion

References:

* https://governance.openstack.org/tc/reference/charter.html#election-for-ptl-seats
* https://governance.openstack.org/tc/reference/charter.html#election-for-tc-seats
* election setup: https://review.openstack.org/#/c/582109/
* schedule update: https://review.openstack.org/582831

== Tracking OpenStack team health ==
See [[OpenStack_health_tracker]] for liaison assignment and status updates.

OpenStack health tracker

2018-07-03T12:05:52Z

Colleen Murphy: /* Status updates */

TC members are attached as liaisons to each of the project teams, [https://governance.openstack.org/sigs/ SIGs], or [https://governance.openstack.org/uc/ UC working groups]. The idea is for these liaisons to keep up with the general health of the group, understand any issues they encounter, and help them work with the TC on solutions if necessary. Some TC members may be more active within the group than the basic liaison responsibilities imply, but that is not required.

Liaisons should monitor their groups by:
* reading meeting logs or participating in meetings
* watching summit "project update" videos
* reading relevant messages on the mailing list
* talking with the PTL, chair, and other group members
* checking contribution rates and review turnaround times

== Liaisons ==
=== SIGs ===

{| class="wikitable"
|-
! Group !! TC members
|-
| API
|| mugsie
|-
| First Contact
|| fungi
|-
| K8s
|| dims
|-
| Meta
|| dhellmann
|-
| Resource Management
|| cdent
|-
| Scientific
|| pabelanger
|-
| Security
|| fungi
|-
| Self-healing
|| zaneb
|-
| Upgrade
|| emilien
|}

=== Working Groups ===

{| class="wikitable"
|-
! Group !! TC members
|-
| App Dev Enablement
|| zaneb
|-
| [[Diversity]]
|| fungi
|-
| Enterprise
||
|-
| Fault Genes
||
|-
| [[InteropWG|Interop]]
|| dims, fungi
|-
| LCOO
||
|-
| Large Deployment
|| pabelanger
|-
| Edge/Massively Distributed Clouds
|| ttx
|-
| Operators Telecom/NFV
|| smcginnis
|-
| Ops Tags
|| smcginnis
|-
| Product
||
|-
| [[ProfessionalCertification]]
||
|-
| Public Cloud
|| ttx
|}

=== Project Teams ===

{| class="wikitable"
|-
! Group !! TC members
|-
| Barbican
|| fungi, ttx
|-
| Blazar
|| cmurphy, mnaser
|-
| Chef Openstack
|| pabelanger, mnaser
|-
| Cinder
|| smcginnis, dims
|-
| Cloudkitty
|| ttx, dims
|-
| Congress
|| cdent, fungi
|-
| Cyborg
|| ttx, TheJulia
|-
| Designate
|| cmurphy, cdent
|-
| Documentation
|| dhellmann, pabelanger
|-
| Dragonflow
|| dims, cdent
|-
| Ec2-Api
|| TheJulia, cmurphy
|-
| Freezer
|| ttx, mugsie
|-
| Glance
|| smcginnis, mugsie
|-
| Heat
|| zaneb, emilien
|-
| Horizon
|| cmurphy, smcginnis
|-
| I18n
|| emilien, cdent
|-
| Infrastructure
|| fungi, mnaser
|-
| Ironic
|| mugsie, fungi
|-
| Karbor
|| ttx, mugsie
|-
| Keystone
|| fungi,cmurphy
|-
| Kolla
|| dims, TheJulia
|-
| Kuryr
|| dims, cdent
|-
| Loci
|| pabelanger, dims
|-
| Magnum
|| mnaser, dims
|-
| Manila
|| smcginnis, pabelanger
|-
| Masakari
|| pabelanger, cdent
|-
| Mistral
|| zaneb, cmurphy
|-
| Monasca
|| zaneb, TheJulia
|-
| Murano
|| dhellmann, emilien
|-
| Neutron
|| mugsie, dims
|-
| Nova
|| mnaser, dhellmann
|-
| Octavia
|| mnaser, mugsie
|-
| Openstack Charms
|| ttx, emilien
|-
| Openstack-Helm
|| ttx, dims
|-
| Openstackansible
|| mnaser, smcginnis
|-
| OpenStackClient
|| dhellmann, cmurphy
|-
| Openstacksdk
|| pabelanger, TheJulia
|-
| Oslo
|| dhellmann, mugsie
|-
| Packaging-Rpm
|| cmurphy, zaneb
|-
| Powervmstackers
|| emilien, TheJulia
|-
| Puppet Openstack
|| cmurphy, pabelanger
|-
| Qinling
|| zaneb, TheJulia
|-
| Quality Assurance
|| cdent, fungi
|-
| Rally
|| pabelanger, mnaser
|-
| Refstack
|| fungi, TheJulia
|-
| Release Management
|| dhellmann, smcginnis
|-
| Requirements
|| fungi, dhellmann
|-
| Sahara
|| emilien, pabelanger
|-
| Searchlight
|| mugsie, mnaser
|-
| Security
|| fungi, zaneb
|-
| Senlin
|| zaneb, smcginnis
|-
| Solum
|| zaneb, mnaser
|-
| Stable Branch Maintenance
|| fungi, smcginnis
|-
| Storlets
|| ttx, dhellmann
|-
| Swift
|| smcginnis, mugsie
|-
| Tacker
|| TheJulia, emilien
|-
| Telemetry
|| cdent, dhellmann
|-
| Tricircle
|| emilien, cdent
|-
| Tripleo
|| emilien, cmurphy
|-
| Trove
|| ttx, mugsie
|-
| Vitrage
|| emilien, dhellmann
|-
| Watcher
|| smcginnis, TheJulia
|-
| Winstackers
|| pabelanger, cdent
|-
| Zaqar
|| zaneb, dims
|-
| Zun
|| zaneb, ttx
|}

== Status updates ==

=== Blazar ===
Reported issues
* Organizational diversity fragility: NTT represents 79% of core reviews

=== Chef OpenStack ===
Reported issues
* Individual fragility: Samuel Cassiba represents 75% of commits

=== Cinder ===
[[File:green.png]] Update: June 22, 2018, smcginnis

* Some drop off in participation by some cores, but still active enough not to raise any red flags
* Overall less community involvement
* Project may just be "stable" and doesn't need as much activity as the past
* Still a lot of bug fix work to be done, but no major new features on the roadmap

=== Cloudkitty ===
Reported issues
* Organizational diversity fragility: ObjectifLibre represents 100% of core reviews

=== Cyborg ===
Update: 2018-07-02, TheJulia
* Email sent to the PTL to initiate communication on July 2nd

=== Dragonflow ===
Reported issues
* Organizational diversity fragility: Huawei represents 100% of core reviews

=== ec2-api ===
Reported issues
* Individual fragility: Andrey Pavlov represents 100% of core reviews

Update: July 3, 2018 (cmurphy)
* Low activity due to general maturity
* Still actively used by operators, bugs are reported and fixed
* Three cores, all reportedly active
* Being part of OpenStack is still valued
** Operators are still using the project, so better to be coupled with OpenStack
** Depends on other components of OpenStack, so there is value in collaborating together

=== Freezer ===
Reported issues
* Still uses pycrypto [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131103.html]
* freezer and freezer-web-ui missed the Rocky-2 milestone

=== Heat ===
Update: 2018-06-28, zaneb

* Under active development
* Only 4 active cores, 3 from Red Hat. This is limiting the amount of development that can be done and the velocity of the project.
** Especially struggling with stable reviews (only 1 active core, and the stable-maint team are the gatekeepers for adding more)
* Active on mailing list and IRC
* Regular IRC meetings
* [https://ethercalc.openstack.org/heat-mox-removal Excellent progress] on the (massive) mox-removal goal in Rocky
* The heat-translator sub-project no longer has any team overlap with the rest of the project, and is struggling for core reviewers. It might be time to [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131688.html consider another home for it].

=== I18n ===
Update: June 13, emilien

Reported issues: none, yet.
The team changed leadership in Queens.

Queens status:
* 87 modules touched (+87%)
* 17 languages supported (+6%)
* 55 active translators (-14%) (TODO, need to check with PTL if it has an impact)
* 7 companies support (-22%)
I18n team previously had team meetings but decided to have office hours instead.
Usually tracks completion of Rocky community goals.
A lot of collaboration with Doc team.
Dedicated mailing-list: openstack-i18n - pretty busy

Rocky:
* Help is wanted around doc translation. See https://review.openstack.org/#/c/545377 for example.

=== Keystone ===
Update July 3, 2018 (cmurphy)
* High pressure due to being a central part of OpenStack
* Focus on "improving the commons" - policy/RBAC work, unified quota management, application development
* 10 cores with varying levels of activity, nearly all are at most part-time
** Concern over possibility of team burnout

=== Kolla ===
Update: 2018-07-02, TheJulia
* Email sent to the PTL to initiate communication on July 2nd

=== Kuryr ===
Reported issues
* Organizational diversity fragility: RedHat represents 79% of core reviews

=== Manila ===
[[File:green.png]] Update: June 22, 2018, smcginnis

* Project appears to be in good shape
* Focusing on bug fixes and stabilization rather than any big new features
* Drop of in involvement from EU, particularly from HPE and IBM
* Increase of participation from China makes EU drop off not as much of an issue other than time coverage
** Not a lot of involvement on IRC or weekly meeting though
* Lots of good interest downstream, particularly from HPC and telco communities

=== Masakari ===
Reported issues
* Low activity in Rocky for a "new" project
* Organizational diversity fragility: NTT represents 97% of core reviews

=== Murano ===
* murano and murano-dashboard missed the Rocky-2 milestone

Update 13 June 2018, dhellmann

* Recent US government action against ZTE has had an impact on the team, because ZTE employees are key contributors to the project and the core team. It is unclear how much ZTE will be able to continue to contribute in the future. [https://www.nbcnews.com/politics/congress/senate-blocks-zte-deal-rebuke-trump-deal-n882196]
* The murano-core team has members froM AT&T and Mirantis, as well as ZTE.

=== Openstack Charms ===
[[File:green.png]] Update: June 20, ttx

* Currently single-vendor (all cores from Canonical), but with some external participation
* Steady activity, keeping up with recent evolution (includes Vault and Gnocchi, integrates Designate with Neutron)
* Holds weekly IRC meetings with rotating chair
* Uses Launchpad, and is likely to stay there as it allows sharing tasks with Ubuntu packaging
* Limited ML engagement (thread left dangling at [http://lists.openstack.org/pipermail/openstack-dev/2018-April/129314.html])

=== OpenStackClient ===
[[File:orange.png]] Update: 28 June 2018, dhellmann, cmurphy

* uses IRC and the mailing list but no meetings
* the review team is small, but there are several active reviewers not on the core team yet who are candidates
* there is quite a review backlog, but the PTL is optimistic that adding the new reviewers will help with that
* they are still interested in being included on the help wanted list (hence the "orange" status, for now)

=== Openstacksdk ===
Update: 2018-07-02, TheJulia
* Initial communication with PTL, should expect to follow-up with-in the next few days.

=== OpenStack-Helm ===
[[File:green.png]] Update: June 26, ttx

* Currently single-vendor (all cores from AT&T), but with external participation (SKT, 99cloud, Intel...)
* Increasing activity (412 commits in Rocky so far compared to 513 total in Queens)
* Holds weekly IRC meetings, pretty active discussions
* Migrated to StoryBoard
* Limited ML engagement (mostly used for team-wide announcements)
* OpenStack-Helm is release-independent -- it aims to support Newton -> master and track latest all the time. They are waiting until they reach a certain quality level (and stable interface) before declaring a 1.0. See [https://docs.openstack.org/openstack-helm/latest/specs/osh-1.0-requirements.html requirements for 1.0]. This explains lack of releases.

=== Oslo ===
[[File:orange.png]]

Reported issues

* Most of the more active members are employed by Red Hat, so it would be good to bring in more diverse contributors
* oslo.privsep, taskflow, and oslo.service are used in several significant service projects, but are effectively unmaintained.
* oslo.service has some issues with the WSGI service not working under python3. The plan is to encourage all projects to stop using that feature, deprecate, then remove it.
* taskflow is one of several projects that needs to update to a newer version of networkx, but the API changes in networkx mean reworking some of taskflow. Supporting both versions of the APIs may be complicated.

Update: 12 June 2018, dhellmann

* The team is small, but active and working on recruiting.
* Team produces regular and frequent releases for the maintained libraries
* Team meets weekly using IRC
* Team had both onboarding and project update sessions in Vancouver
* The level of activity within each library varies.
* Several of the libraries are reaching a "stable" state in which they may not see many updates beyond bug fixes. This has spurred a discussion of how to treat projects like that, led by the release management team [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131341.html]

=== Packaging-RPM ===
Reported issues
* Organizational diversity fragility: SUSE represents 77% of core reviews

=== Rally ===
Reported issues
* Half on GitHub those days, and unwilling to drop direct branching ACLs
* Individual fragility: Andrey Kurilin represents 56% of commits
* Organizational diversity fragility: GoDaddy represents 97% of core reviews

=== Release Management ===
[[File:green.png]]

Update: 28 June 2018, dhellmann & smcginnis

* The review work has become easier, but there are still only 3 team members. That leaves succession planning for the PTL role a bit up in the air, and also poses challenges with the members travel to conferences all at the same time.
* Working on a reviewers' guide to help with recruiting.
* Completed adjusting ACLs for all official teams to use the reviewable release process for deliverables that are part of the OpenStack release.

=== Requirements Management ===
[[File:orange.png]]

* need more reviewers, badly, as discussed a joint leadership meeting in Vancouver

Update: 14 June 2018, dhellmann

* team has recently lost several members
* most work is really down to 3 people (Matt, Dirk, Tony)
* they work for 3 separate companies, but the team is so small that the diversity measures are questionable
* the changes this cycle to stop syncing requirements should lower the review burden somewhat, but the move to python 3 is going to take some work
* meets regularly
* accomplishments this cycle
** stopped syncing dependencies between projects
** working on networkx upgrade
** uncapped eventlet
** uncapped sphinx
** added optional lower-constraints test jobs for project teams that want them

=== Sahara ===
Update: June 13, emilien

Reported issues: none, yet.
* The team changed leadership in Queens
* Last PTG was virtual
* Most commits in Rocky are from Red Hat (92% of core reviews)
* The team is really small, most of commits are done by 2 contributors and 3 contributors are active in reviews
* Latest survey shows that Sahara is used in production by 3% of deployments and 8% in test phase. 25% of users are interested by Sahara
* Following goals and releases
* Email sent to PTL on June 13th

=== Searchlight ===
Reported issues
* searchlight and searchlight-ui missed the Rocky-1 milestone
* Release forced for searchlight and searchlight-ui for the Rocky-2 milestone

=== Solum ===
Reported issues
* Individual fragility: Zhurong represents 100% of core reviews

=== Storlets ===
Reported issues
* Individual fragility: Kota Tsuyuzaki represents 100% of core reviews

=== Tacker ===
Reported issues
* Individual fragility: Yong Sheng Gong represents 75% of core reviews

=== Telemetry ===
[[File:orange.png]] Update: June 21, cdent, WIP
* Only two active cores and contributors, despite [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131443.html continued value].
* more to come

=== Tricircle ===
Reported issues
* Not set up for zuulv3 so cannot land patches that interact with other repositories? http://lists.openstack.org/pipermail/openstack-dev/2018-June/131643.html

=== TripleO ===
Update: June 13, emilien

* Mainly Red Hat (99% of core reviews). Some contributors from vendors (storage/network plugins)
* Number of contributors / core reviewers always increasing
* Quite healthy, no problem reported so far

=== Trove ===
[[File:orange.png]] Update: June 12, ttx

* The team changed leadership in Rocky
* Zhao Chao handles bulk of commits (51%)
* The new team is small, but pretty alive and active. Needs more contributors to be stable.
* Mostly contributors in China (AWCloud, China Telecom, China Mobile)
* Drop in activity in Rocky: 45 commits by Rocky-2, to compare with the 245 commits in Queens
* Organizational diversity: 53% of commits are from AWCloud. Reviews are shared between 23% China Telecom, 19% China Mobile, 19% Awcloud. Last cycle with 41% IBM.
* Regular weekly meetings, well run with clear documentation of outcomes
* Tracks completion of Rocky community goals
* A few ML threads, but mostly to discuss things external to the team (new meeting time, stable maint team composition)
* Missed Rocky-2 milestone, but mostly due to a [http://eavesdrop.openstack.org/meetings/trove/2018/trove.2018-06-06-14.00.log.html#l-95 misunderstanding of release policy].
* No project update in Vancouver, but was discussed in meeting: sadly [http://eavesdrop.openstack.org/meetings/trove/2018/trove.2018-05-16-14.00.log.html#l-20 no team member was present].
* Reached out to PTL by email on June 12 for additional concerns / questions.

=== Upgrade SIG ===
WIP (emilien)

=== Vitrage ===
Reported issues
* Organizational diversity fragility: Nokia represents 80% of core reviews

=== Watcher ===
Update: 2018-07-02, TheJulia
* Email sent to the PTL to initiate communication on July 2nd

=== Winstackers ===
Reported issues
* Individual fragility: Claudiu Belu represents 100% of core reviews

=== Zaqar ===
Reported issues
* zaqar and zaqar-ui missed the Rocky-2 milestone

OpenStack health tracker

2018-07-03T11:56:29Z

Colleen Murphy: /* ec2-api */

TC members are attached as liaisons to each of the project teams, [https://governance.openstack.org/sigs/ SIGs], or [https://governance.openstack.org/uc/ UC working groups]. The idea is for these liaisons to keep up with the general health of the group, understand any issues they encounter, and help them work with the TC on solutions if necessary. Some TC members may be more active within the group than the basic liaison responsibilities imply, but that is not required.

Liaisons should monitor their groups by:
* reading meeting logs or participating in meetings
* watching summit "project update" videos
* reading relevant messages on the mailing list
* talking with the PTL, chair, and other group members
* checking contribution rates and review turnaround times

== Liaisons ==
=== SIGs ===

{| class="wikitable"
|-
! Group !! TC members
|-
| API
|| mugsie
|-
| First Contact
|| fungi
|-
| K8s
|| dims
|-
| Meta
|| dhellmann
|-
| Resource Management
|| cdent
|-
| Scientific
|| pabelanger
|-
| Security
|| fungi
|-
| Self-healing
|| zaneb
|-
| Upgrade
|| emilien
|}

=== Working Groups ===

{| class="wikitable"
|-
! Group !! TC members
|-
| App Dev Enablement
|| zaneb
|-
| [[Diversity]]
|| fungi
|-
| Enterprise
||
|-
| Fault Genes
||
|-
| [[InteropWG|Interop]]
|| dims, fungi
|-
| LCOO
||
|-
| Large Deployment
|| pabelanger
|-
| Edge/Massively Distributed Clouds
|| ttx
|-
| Operators Telecom/NFV
|| smcginnis
|-
| Ops Tags
|| smcginnis
|-
| Product
||
|-
| [[ProfessionalCertification]]
||
|-
| Public Cloud
|| ttx
|}

=== Project Teams ===

{| class="wikitable"
|-
! Group !! TC members
|-
| Barbican
|| fungi, ttx
|-
| Blazar
|| cmurphy, mnaser
|-
| Chef Openstack
|| pabelanger, mnaser
|-
| Cinder
|| smcginnis, dims
|-
| Cloudkitty
|| ttx, dims
|-
| Congress
|| cdent, fungi
|-
| Cyborg
|| ttx, TheJulia
|-
| Designate
|| cmurphy, cdent
|-
| Documentation
|| dhellmann, pabelanger
|-
| Dragonflow
|| dims, cdent
|-
| Ec2-Api
|| TheJulia, cmurphy
|-
| Freezer
|| ttx, mugsie
|-
| Glance
|| smcginnis, mugsie
|-
| Heat
|| zaneb, emilien
|-
| Horizon
|| cmurphy, smcginnis
|-
| I18n
|| emilien, cdent
|-
| Infrastructure
|| fungi, mnaser
|-
| Ironic
|| mugsie, fungi
|-
| Karbor
|| ttx, mugsie
|-
| Keystone
|| fungi,cmurphy
|-
| Kolla
|| dims, TheJulia
|-
| Kuryr
|| dims, cdent
|-
| Loci
|| pabelanger, dims
|-
| Magnum
|| mnaser, dims
|-
| Manila
|| smcginnis, pabelanger
|-
| Masakari
|| pabelanger, cdent
|-
| Mistral
|| zaneb, cmurphy
|-
| Monasca
|| zaneb, TheJulia
|-
| Murano
|| dhellmann, emilien
|-
| Neutron
|| mugsie, dims
|-
| Nova
|| mnaser, dhellmann
|-
| Octavia
|| mnaser, mugsie
|-
| Openstack Charms
|| ttx, emilien
|-
| Openstack-Helm
|| ttx, dims
|-
| Openstackansible
|| mnaser, smcginnis
|-
| OpenStackClient
|| dhellmann, cmurphy
|-
| Openstacksdk
|| pabelanger, TheJulia
|-
| Oslo
|| dhellmann, mugsie
|-
| Packaging-Rpm
|| cmurphy, zaneb
|-
| Powervmstackers
|| emilien, TheJulia
|-
| Puppet Openstack
|| cmurphy, pabelanger
|-
| Qinling
|| zaneb, TheJulia
|-
| Quality Assurance
|| cdent, fungi
|-
| Rally
|| pabelanger, mnaser
|-
| Refstack
|| fungi, TheJulia
|-
| Release Management
|| dhellmann, smcginnis
|-
| Requirements
|| fungi, dhellmann
|-
| Sahara
|| emilien, pabelanger
|-
| Searchlight
|| mugsie, mnaser
|-
| Security
|| fungi, zaneb
|-
| Senlin
|| zaneb, smcginnis
|-
| Solum
|| zaneb, mnaser
|-
| Stable Branch Maintenance
|| fungi, smcginnis
|-
| Storlets
|| ttx, dhellmann
|-
| Swift
|| smcginnis, mugsie
|-
| Tacker
|| TheJulia, emilien
|-
| Telemetry
|| cdent, dhellmann
|-
| Tricircle
|| emilien, cdent
|-
| Tripleo
|| emilien, cmurphy
|-
| Trove
|| ttx, mugsie
|-
| Vitrage
|| emilien, dhellmann
|-
| Watcher
|| smcginnis, TheJulia
|-
| Winstackers
|| pabelanger, cdent
|-
| Zaqar
|| zaneb, dims
|-
| Zun
|| zaneb, ttx
|}

== Status updates ==

=== Blazar ===
Reported issues
* Organizational diversity fragility: NTT represents 79% of core reviews

=== Chef OpenStack ===
Reported issues
* Individual fragility: Samuel Cassiba represents 75% of commits

=== Cinder ===
[[File:green.png]] Update: June 22, 2018, smcginnis

* Some drop off in participation by some cores, but still active enough not to raise any red flags
* Overall less community involvement
* Project may just be "stable" and doesn't need as much activity as the past
* Still a lot of bug fix work to be done, but no major new features on the roadmap

=== Cloudkitty ===
Reported issues
* Organizational diversity fragility: ObjectifLibre represents 100% of core reviews

=== Cyborg ===
Update: 2018-07-02, TheJulia
* Email sent to the PTL to initiate communication on July 2nd

=== Dragonflow ===
Reported issues
* Organizational diversity fragility: Huawei represents 100% of core reviews

=== ec2-api ===
Reported issues
* Individual fragility: Andrey Pavlov represents 100% of core reviews

Update: July 3, 2018 (cmurphy)
* Low activity due to general maturity
* Still actively used by operators, bugs are reported and fixed
* Three cores, all reportedly active
* Being part of OpenStack is still valued
** Operators are still using the project, so better to be coupled with OpenStack
** Depends on other components of OpenStack, so there is value in collaborating together

=== Freezer ===
Reported issues
* Still uses pycrypto [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131103.html]
* freezer and freezer-web-ui missed the Rocky-2 milestone

=== Heat ===
Update: 2018-06-28, zaneb

* Under active development
* Only 4 active cores, 3 from Red Hat. This is limiting the amount of development that can be done and the velocity of the project.
** Especially struggling with stable reviews (only 1 active core, and the stable-maint team are the gatekeepers for adding more)
* Active on mailing list and IRC
* Regular IRC meetings
* [https://ethercalc.openstack.org/heat-mox-removal Excellent progress] on the (massive) mox-removal goal in Rocky
* The heat-translator sub-project no longer has any team overlap with the rest of the project, and is struggling for core reviewers. It might be time to [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131688.html consider another home for it].

=== I18n ===
Update: June 13, emilien

Reported issues: none, yet.
The team changed leadership in Queens.

Queens status:
* 87 modules touched (+87%)
* 17 languages supported (+6%)
* 55 active translators (-14%) (TODO, need to check with PTL if it has an impact)
* 7 companies support (-22%)
I18n team previously had team meetings but decided to have office hours instead.
Usually tracks completion of Rocky community goals.
A lot of collaboration with Doc team.
Dedicated mailing-list: openstack-i18n - pretty busy

Rocky:
* Help is wanted around doc translation. See https://review.openstack.org/#/c/545377 for example.

=== Kolla ===
Update: 2018-07-02, TheJulia
* Email sent to the PTL to initiate communication on July 2nd

=== Kuryr ===
Reported issues
* Organizational diversity fragility: RedHat represents 79% of core reviews

=== Manila ===
[[File:green.png]] Update: June 22, 2018, smcginnis

* Project appears to be in good shape
* Focusing on bug fixes and stabilization rather than any big new features
* Drop of in involvement from EU, particularly from HPE and IBM
* Increase of participation from China makes EU drop off not as much of an issue other than time coverage
** Not a lot of involvement on IRC or weekly meeting though
* Lots of good interest downstream, particularly from HPC and telco communities

=== Masakari ===
Reported issues
* Low activity in Rocky for a "new" project
* Organizational diversity fragility: NTT represents 97% of core reviews

=== Murano ===
* murano and murano-dashboard missed the Rocky-2 milestone

Update 13 June 2018, dhellmann

* Recent US government action against ZTE has had an impact on the team, because ZTE employees are key contributors to the project and the core team. It is unclear how much ZTE will be able to continue to contribute in the future. [https://www.nbcnews.com/politics/congress/senate-blocks-zte-deal-rebuke-trump-deal-n882196]
* The murano-core team has members froM AT&T and Mirantis, as well as ZTE.

=== Openstack Charms ===
[[File:green.png]] Update: June 20, ttx

* Currently single-vendor (all cores from Canonical), but with some external participation
* Steady activity, keeping up with recent evolution (includes Vault and Gnocchi, integrates Designate with Neutron)
* Holds weekly IRC meetings with rotating chair
* Uses Launchpad, and is likely to stay there as it allows sharing tasks with Ubuntu packaging
* Limited ML engagement (thread left dangling at [http://lists.openstack.org/pipermail/openstack-dev/2018-April/129314.html])

=== OpenStackClient ===
[[File:orange.png]] Update: 28 June 2018, dhellmann, cmurphy

* uses IRC and the mailing list but no meetings
* the review team is small, but there are several active reviewers not on the core team yet who are candidates
* there is quite a review backlog, but the PTL is optimistic that adding the new reviewers will help with that
* they are still interested in being included on the help wanted list (hence the "orange" status, for now)

=== Openstacksdk ===
Update: 2018-07-02, TheJulia
* Initial communication with PTL, should expect to follow-up with-in the next few days.

=== OpenStack-Helm ===
[[File:green.png]] Update: June 26, ttx

* Currently single-vendor (all cores from AT&T), but with external participation (SKT, 99cloud, Intel...)
* Increasing activity (412 commits in Rocky so far compared to 513 total in Queens)
* Holds weekly IRC meetings, pretty active discussions
* Migrated to StoryBoard
* Limited ML engagement (mostly used for team-wide announcements)
* OpenStack-Helm is release-independent -- it aims to support Newton -> master and track latest all the time. They are waiting until they reach a certain quality level (and stable interface) before declaring a 1.0. See [https://docs.openstack.org/openstack-helm/latest/specs/osh-1.0-requirements.html requirements for 1.0]. This explains lack of releases.

=== Oslo ===
[[File:orange.png]]

Reported issues

* Most of the more active members are employed by Red Hat, so it would be good to bring in more diverse contributors
* oslo.privsep, taskflow, and oslo.service are used in several significant service projects, but are effectively unmaintained.
* oslo.service has some issues with the WSGI service not working under python3. The plan is to encourage all projects to stop using that feature, deprecate, then remove it.
* taskflow is one of several projects that needs to update to a newer version of networkx, but the API changes in networkx mean reworking some of taskflow. Supporting both versions of the APIs may be complicated.

Update: 12 June 2018, dhellmann

* The team is small, but active and working on recruiting.
* Team produces regular and frequent releases for the maintained libraries
* Team meets weekly using IRC
* Team had both onboarding and project update sessions in Vancouver
* The level of activity within each library varies.
* Several of the libraries are reaching a "stable" state in which they may not see many updates beyond bug fixes. This has spurred a discussion of how to treat projects like that, led by the release management team [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131341.html]

=== Packaging-RPM ===
Reported issues
* Organizational diversity fragility: SUSE represents 77% of core reviews

=== Rally ===
Reported issues
* Half on GitHub those days, and unwilling to drop direct branching ACLs
* Individual fragility: Andrey Kurilin represents 56% of commits
* Organizational diversity fragility: GoDaddy represents 97% of core reviews

=== Release Management ===
[[File:green.png]]

Update: 28 June 2018, dhellmann & smcginnis

* The review work has become easier, but there are still only 3 team members. That leaves succession planning for the PTL role a bit up in the air, and also poses challenges with the members travel to conferences all at the same time.
* Working on a reviewers' guide to help with recruiting.
* Completed adjusting ACLs for all official teams to use the reviewable release process for deliverables that are part of the OpenStack release.

=== Requirements Management ===
[[File:orange.png]]

* need more reviewers, badly, as discussed a joint leadership meeting in Vancouver

Update: 14 June 2018, dhellmann

* team has recently lost several members
* most work is really down to 3 people (Matt, Dirk, Tony)
* they work for 3 separate companies, but the team is so small that the diversity measures are questionable
* the changes this cycle to stop syncing requirements should lower the review burden somewhat, but the move to python 3 is going to take some work
* meets regularly
* accomplishments this cycle
** stopped syncing dependencies between projects
** working on networkx upgrade
** uncapped eventlet
** uncapped sphinx
** added optional lower-constraints test jobs for project teams that want them

=== Sahara ===
Update: June 13, emilien

Reported issues: none, yet.
* The team changed leadership in Queens
* Last PTG was virtual
* Most commits in Rocky are from Red Hat (92% of core reviews)
* The team is really small, most of commits are done by 2 contributors and 3 contributors are active in reviews
* Latest survey shows that Sahara is used in production by 3% of deployments and 8% in test phase. 25% of users are interested by Sahara
* Following goals and releases
* Email sent to PTL on June 13th

=== Searchlight ===
Reported issues
* searchlight and searchlight-ui missed the Rocky-1 milestone
* Release forced for searchlight and searchlight-ui for the Rocky-2 milestone

=== Solum ===
Reported issues
* Individual fragility: Zhurong represents 100% of core reviews

=== Storlets ===
Reported issues
* Individual fragility: Kota Tsuyuzaki represents 100% of core reviews

=== Tacker ===
Reported issues
* Individual fragility: Yong Sheng Gong represents 75% of core reviews

=== Telemetry ===
[[File:orange.png]] Update: June 21, cdent, WIP
* Only two active cores and contributors, despite [http://lists.openstack.org/pipermail/openstack-dev/2018-June/131443.html continued value].
* more to come

=== Tricircle ===
Reported issues
* Not set up for zuulv3 so cannot land patches that interact with other repositories? http://lists.openstack.org/pipermail/openstack-dev/2018-June/131643.html

=== TripleO ===
Update: June 13, emilien

* Mainly Red Hat (99% of core reviews). Some contributors from vendors (storage/network plugins)
* Number of contributors / core reviewers always increasing
* Quite healthy, no problem reported so far

=== Trove ===
[[File:orange.png]] Update: June 12, ttx

* The team changed leadership in Rocky
* Zhao Chao handles bulk of commits (51%)
* The new team is small, but pretty alive and active. Needs more contributors to be stable.
* Mostly contributors in China (AWCloud, China Telecom, China Mobile)
* Drop in activity in Rocky: 45 commits by Rocky-2, to compare with the 245 commits in Queens
* Organizational diversity: 53% of commits are from AWCloud. Reviews are shared between 23% China Telecom, 19% China Mobile, 19% Awcloud. Last cycle with 41% IBM.
* Regular weekly meetings, well run with clear documentation of outcomes
* Tracks completion of Rocky community goals
* A few ML threads, but mostly to discuss things external to the team (new meeting time, stable maint team composition)
* Missed Rocky-2 milestone, but mostly due to a [http://eavesdrop.openstack.org/meetings/trove/2018/trove.2018-06-06-14.00.log.html#l-95 misunderstanding of release policy].
* No project update in Vancouver, but was discussed in meeting: sadly [http://eavesdrop.openstack.org/meetings/trove/2018/trove.2018-05-16-14.00.log.html#l-20 no team member was present].
* Reached out to PTL by email on June 12 for additional concerns / questions.

=== Upgrade SIG ===
WIP (emilien)

=== Vitrage ===
Reported issues
* Organizational diversity fragility: Nokia represents 80% of core reviews

=== Watcher ===
Update: 2018-07-02, TheJulia
* Email sent to the PTL to initiate communication on July 2nd

=== Winstackers ===
Reported issues
* Individual fragility: Claudiu Belu represents 100% of core reviews

=== Zaqar ===
Reported issues
* zaqar and zaqar-ui missed the Rocky-2 milestone

Technical Committee Tracker

2018-06-08T10:57:10Z

Colleen Murphy: /* Project Teams */

The OpenStack Technical Committee is one of the [https://governance.openstack.org governing bodies] of the OpenStack project. You can find more information about it, such as the list of its [https://governance.openstack.org/tc/ current members] or its [https://governance.openstack.org/tc/reference/charter.html governance charter], on the OpenStack TC governance website at https://governance.openstack.org/tc/ .

This page tracks the various governance changes being proposed and the various initiatives the Technical Committee is pursuing.

Other tasks can be found in [https://storyboard.openstack.org/#!/project/923 the storyboard project].

'''Status last updated: {{REVISIONYEAR}}/{{REVISIONMONTH}}/{{REVISIONDAY2}}'''

== Project team changes ==
* PowerVMStackers following stable policy https://review.openstack.org/#/c/562591/
** Status: Approved

== Other Initiatives ==

=== Adjutant official project status ===
Drivers: zaneb

Status: Under discussion

The Adjutant team will not be present at the forum, but we will discuss our approach to reviewing team applications in general during the TC session about project "boundaries" [https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21739/official-projects-and-the-boundary-of-what-is-openstack] and Adjutant in particular on Thursday afternoon [https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21752/adjutant-official-project-status]

References
* [https://review.openstack.org/553643 project team application]

=== Allow projects to drop py27 support in the PTI ===
Drivers: mugsie, dhellmann

Status: Under discussion

References
* [https://review.openstack.org/561922 PTI documentation change]
* [https://review.openstack.org/#/c/571011/ governance resolution describing the deprecation timeline]
* [https://etherpad.openstack.org/p/YVR-python-2-deprecation-timeline Rocky Forum session notes]
* [http://lists.openstack.org/pipermail/openstack-dev/2018-May/130824.html summary of Rocky Forum discussion]

=== Starting work on constellations ===

Drivers:

Status: Under discussion

References
* [http://lists.openstack.org/pipermail/openstack-dev/2018-May/130068.html openstack-dev mailing list post]
* [http://git.openstack.org/cgit/openstack/constellations/ new git repository to hold the docs]
* [https://review.openstack.org/#/c/565466/ first draft of scientific computing constellation]

=== Clarify new project requirements for affiliation diversity ===
Drivers: zaneb

Status: Under discussion

References
* https://review.openstack.org/567944

=== Adding a key manager to base services ===
Drivers: fungi

Status: In progress

References
* https://etherpad.openstack.org/p/BOS-forum-key-management
* ML thread: http://lists.openstack.org/pipermail/openstack-dev/2018-May/130567.html

=== Improving the visibility of status updates and announcements ===
Drivers: dhellmann, cdent, ttx

Status: In progress

We are investigating mailman 3, blogging, and Matrix, among other solutions.

=== Correction to TC member election section of bylaws ===
Drivers: fungi, dhellmann

Status: On hold until the next Foundation vote

This was discussed in the joint leadership meeting in Vancouver. The change requires a member vote, and the Board passed a resolution allowing the Foundation Secretary to propose the bylaws change as part of the next Board election (early 2019). We anticipate other bylaws changes at the same time.

Section [https://www.openstack.org/legal/technical-committee-member-policy/ 3.b.i] reads "An Individual Member is an ATC who has..." but should read "An ATC is an Individual Member who has…"

=== How do we track updates to old goals for new projects? ===
Drivers: dhellmann

Status: In progress

References
* See the [https://review.openstack.org/#/c/557863/ Kolla Python 3.5 update] for example.
* [http://lists.openstack.org/pipermail/openstack-dev/2018-May/130236.html openstack-dev mailing list thread]

=== Ownership and publishing for the operations guide ===
Drivers: dhellmann

Status: Resolved, they will start a SIG to own the repository for the guide so it can be published to docs.openstack.org.

References
* Wednesday, May 23, 2018 - session at Vancouver summit
* http://lists.openstack.org/pipermail/openstack-operators/2018-May/015321.html

=== StarlingX ===
Drivers: mnaser, EmilienM

Status: [https://storyboard.openstack.org/#!/story/2002123 In progress]

References
* [http://lists.openstack.org/pipermail/openstack-dev/2018-May/130715.html ML thread following up from summit]
* [http://lists.openstack.org/pipermail/openstack-dev/2018-May/130913.html ML thread post-summit discussions]
* [https://review.openstack.org/#/c/569562/ project-config change to import some of the repositories]

=== Murano Team Status ===
Drivers: dhellmann

Status: On hold

With ZTE's future at question, a Murano team member contacted me about the future of the project. I am currently waiting for the question to be raised in an email thread.

=== Organizational diversity tags ===
Drivers: ttx, mnaser

Status: Under discussion

References
* [http://lists.openstack.org/pipermail/openstack-dev/2018-May/130776.html openstack-dev mailing list thread raising the topic]

=== Clarifying the terms of service for hosted projects ===
Drivers: zaneb

Status: Under discussion

References
* [http://lists.openstack.org/pipermail/openstack-dev/2018-May/130807.html openstack-dev mailing list thread raising the topic]

=== Technical Vision for OpenStack ===
Drivers: zaneb, ttx, cdent

Status: Early

Zane offered to start creating a "technical vision" for OpenStack to help clarify the boundary for where projects fit into OpenStack and where they may not.

References
* [https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21739/official-projects-and-the-boundary-of-what-is-openstack Rocky Forum session]

=== Stein Series Goals ===
Drivers: smcginnis

Status: Early

Sean organized a session at the Rocky Forum to discuss improving our goal selection process and specific goals for Stein.

References
* [https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21738/s-release-goals Rocky Forum session]

=== Anti-nitpicking Cultural Change ===
Drivers: TheJulia, ttx

Status: In progress

References
* [http://lists.openstack.org/pipermail/openstack-dev/2018-May/130802.html openstack-dev mailing list thread]

=== Trove Project Health ===
Drivers: ttx, theJulia

Status: New

During the public cloud issues session at the Rocky Forum someone in the room raised the question of whether Trove is still actively maintained.

References
* [https://etherpad.openstack.org/p/YVR-forum-missing-features-pc Missing features in OpenStack for public clouds] forum session notes

=== tags indicating the upgrade support in deployment tools ===
Drivers: ttx

Status: New

During the FFU session at the Rocky Forum, Dan Smith and David Medberry indicated interest in defining tags to describe what upgrade features deployment tools have.

References
* [https://etherpad.openstack.org/p/YVR-forum-fast-forward-upgrades Rocky Forum session notes]

=== Reviewing the TC Vision ===
Drivers: ttx, EmilienM, fungi

Status: [https://storyboard.openstack.org/#!/story/2002132 In progress]

References
* [https://etherpad.openstack.org/p/YVR-tc-retrospective TC Retrospective Notes from Rocky Forum]

=== Reviewing TC Office Hour Times and Locations ===
Drivers: dhellmann

Status: New

During the retrospective at the Rocky Forum we talked about changing our office hour times or using different tools to make them more accessible.

References
* [https://etherpad.openstack.org/p/YVR-tc-retrospective TC Retrospective Notes from Rocky Forum]

=== Actively Monitoring Teams ===
Drivers: dhellmann

Status: New

During the retrospective at the Rocky Forum we discussed more actively engaging with project teams and SIGs to anticipate issues we can help resolve.

'''Dragonflow''' did not produce a Queens release. Their last release was 4.0.0 on Sept 1, 2017. Should projects that do not prepare releases be considered official? -- dhellmann

'''Rally''' may be moving out to GitHub? https://github.com/xrally and https://xrally.org -- dhellmann

References
* [https://etherpad.openstack.org/p/YVR-tc-retrospective TC Retrospective Notes from Rocky Forum]

=== Status of Electorate ===
Drivers:

Status: New

During the retrospective at the Rocky Forum we discussed the status of the TC electorate, and what is perceived as a low level of engagement. This needs a bit more research to compare recent elections so we can understand how things stand, and then we should talk about ways to improve the situation.

References
* [https://etherpad.openstack.org/p/YVR-tc-retrospective TC Retrospective Notes from Rocky Forum]

=== Improving the help-wanted list ===
Drivers: dims

Status: New

During the Board/TC/UC meeting at Vancouver, we came up with an idea on what we can put together a better way to ask platinum/gold and other companies in the eco system for help (crossing traditional job descriptions and volunteer/skill match websites)

References
* [https://etherpad.openstack.org/p/job-description-template Sample Job description template]

=== project infrastructure governance proposal ===
Drivers: dhellmann

Status: Under discussion

corvus started a discussion about the relationship between the foundation projects and the infrastructure management team as that team shifts from being governed by the TC to being a foundation-wide project.

References
* http://lists.openstack.org/pipermail/openstack-dev/2018-May/130896.html

=== finding help for the unified CLI team ===
Drivers:

Status: Needs a driver

During the office hours on 7 June we talked about adding OSC to the "help wanted" list. We decided we did not have enough information about what the team needs to write it up yet, so we need someone to gather that information and to propose the addition.

== Liaisons ==

This section of the tracker lists the TC members attached as liaisons to each of the project teams, [[OpenStack_SIGs|SIGs]], or [[UserCommittee#Working_Groups_and_Teams|working groups]]. The idea is for these liaisons to keep up with the general health of the group, understand any issues they encounter, and help them work with the TC on solutions if necessary. Some TC members may be more active within the group than the basic liaison responsibilities imply, but that is not required.

Liaisons should monitor their groups by:
* reading meeting logs or participating in meetings
* watching summit "project update" videos
* reading relevant messages on the mailing list
* talking with the PTL, chair, and other group members

=== SIGs ===

{| class="wikitable"
|-
! Group !! TC members
|-
| API
||
|-
| First Contact
|| fungi
|-
| K8s
|| dims
|-
| Resource Management
||
|-
| Scientific
||
|-
| Security
|| fungi
|-
| Self-healing
|| zaneb
|-
| Upgrade
||
|}

=== Working Groups ===

{| class="wikitable"
|-
! Group !! TC members
|-
| App Dev Enablement
|| zaneb
|-
| [[Diversity]]
|| fungi
|-
| Enterprise
||
|-
| Fault Genes
||
|-
| [[InteropWG|Interop]]
|| dims, fungi
|-
| LCOO
||
|-
| Large Deployment
||
|-
| Massively Distributed Clouds
|| ttx
|-
| Ops Tags
|| smcginnis
|-
| Operators Telecom/NFV
|| smcginnis
|-
| Product
||
|-
| [[ProfessionalCertification]]
||
|}

=== Project Teams ===

{| class="wikitable"
|-
! Group !! TC members
|-
| Barbican
|| fungi, ttx
|-
| Blazar
||
|-
| Chef Openstack
||
|-
| Cinder
|| smcginnis
|-
| Cloudkitty
|| ttx
|-
| Congress
||
|-
| Cyborg
|| ttx
|-
| Designate
||
|-
| Documentation
|| dhellmann
|-
| Dragonflow
||
|-
| Ec2-Api
||
|-
| Freezer
|| ttx
|-
| Glance
|| smcginnis
|-
| Heat
|| zaneb
|-
| Horizon
|| cmurphy
|-
| I18n
||
|-
| Infrastructure
|| fungi, mnaser
|-
| Ironic
||
|-
| Karbor
|| ttx
|-
| Keystone
|| fungi,cmurphy
|-
| Kolla
||
|-
| Kuryr
||
|-
| Loci
||
|-
| Magnum
|| mnaser
|-
| Manila
|| smcginnis
|-
| Masakari
||
|-
| Mistral
|| zaneb
|-
| Monasca
||
|-
| Murano
||
|-
| Neutron
||
|-
| Nova
|| mnaser
|-
| Octavia
|| mnaser
|-
| Openstack Charms
|| ttx
|-
| Openstack-Helm
|| ttx
|-
| Openstackansible
|| mnaser
|-
| Openstackclient
|| dhellmann
|-
| Openstacksdk
||
|-
| Oslo
|| dhellmann
|-
| Packaging-Rpm
|| cmurphy
|-
| Powervmstackers
||
|-
| Puppet Openstack
|| cmurphy
|-
| Qinling
|| zaneb
|-
| Quality Assurance
||
|-
| Rally
||
|-
| Refstack
|| fungi
|-
| Release Management
|| dhellmann, smcginnis
|-
| Requirements
|| fungi, dhellmann
|-
| Sahara
||
|-
| Searchlight
||
|-
| Security
|| fungi
|-
| Senlin
|| zaneb
|-
| Solum
||
|-
| Stable Branch Maintenance
|| fungi, smcginnis
|-
| Storlets
|| ttx
|-
| Swift
|| smcginnis
|-
| Tacker
||
|-
| Telemetry
||
|-
| Tricircle
||
|-
| Tripleo
||
|-
| Trove
|| ttx
|-
| Vitrage
||
|-
| Watcher
||
|-
| Winstackers
||
|-
| Zaqar
|| zaneb
|-
| Zun
|| zaneb, ttx
|}

Technical Committee Tracker

2018-06-07T18:45:10Z

Colleen Murphy: /* Project Teams */

The OpenStack Technical Committee is one of the [https://governance.openstack.org governing bodies] of the OpenStack project. You can find more information about it, such as the list of its [https://governance.openstack.org/tc/ current members] or its [https://governance.openstack.org/tc/reference/charter.html governance charter], on the OpenStack TC governance website at https://governance.openstack.org/tc/ .

This page tracks the various governance changes being proposed and the various initiatives the Technical Committee is pursuing.

Other tasks can be found in [https://storyboard.openstack.org/#!/project/923 the storyboard project].

'''Status last updated: {{REVISIONYEAR}}/{{REVISIONMONTH}}/{{REVISIONDAY2}}'''

== Project team changes ==
* PowerVMStackers following stable policy https://review.openstack.org/#/c/562591/
** Status: Approved

== Other Initiatives ==

=== Adjutant official project status ===
Drivers: zaneb

Status: Under discussion

The Adjutant team will not be present at the forum, but we will discuss our approach to reviewing team applications in general during the TC session about project "boundaries" [https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21739/official-projects-and-the-boundary-of-what-is-openstack] and Adjutant in particular on Thursday afternoon [https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21752/adjutant-official-project-status]

References
* [https://review.openstack.org/553643 project team application]

=== Allow projects to drop py27 support in the PTI ===
Drivers: mugsie, dhellmann

Status: Under discussion

References
* [https://review.openstack.org/561922 PTI documentation change]
* [https://review.openstack.org/#/c/571011/ governance resolution describing the deprecation timeline]
* [https://etherpad.openstack.org/p/YVR-python-2-deprecation-timeline Rocky Forum session notes]
* [http://lists.openstack.org/pipermail/openstack-dev/2018-May/130824.html summary of Rocky Forum discussion]

=== Starting work on constellations ===

Drivers:

Status: Under discussion

References
* [http://lists.openstack.org/pipermail/openstack-dev/2018-May/130068.html openstack-dev mailing list post]
* [http://git.openstack.org/cgit/openstack/constellations/ new git repository to hold the docs]
* [https://review.openstack.org/#/c/565466/ first draft of scientific computing constellation]

=== Clarify new project requirements for affiliation diversity ===
Drivers: zaneb

Status: Under discussion

References
* https://review.openstack.org/567944

=== Adding a key manager to base services ===
Drivers: fungi

Status: In progress

References
* https://etherpad.openstack.org/p/BOS-forum-key-management
* ML thread: http://lists.openstack.org/pipermail/openstack-dev/2018-May/130567.html

=== Improving the visibility of status updates and announcements ===
Drivers: dhellmann, cdent, ttx

Status: In progress

We are investigating mailman 3, blogging, and Matrix, among other solutions.

=== Correction to TC member election section of bylaws ===
Drivers: fungi, dhellmann

Status: On hold until the next Foundation vote

This was discussed in the joint leadership meeting in Vancouver. The change requires a member vote, and the Board passed a resolution allowing the Foundation Secretary to propose the bylaws change as part of the next Board election (early 2019). We anticipate other bylaws changes at the same time.

Section [https://www.openstack.org/legal/technical-committee-member-policy/ 3.b.i] reads "An Individual Member is an ATC who has..." but should read "An ATC is an Individual Member who has…"

=== How do we track updates to old goals for new projects? ===
Drivers: dhellmann

Status: In progress

References
* See the [https://review.openstack.org/#/c/557863/ Kolla Python 3.5 update] for example.
* [http://lists.openstack.org/pipermail/openstack-dev/2018-May/130236.html openstack-dev mailing list thread]

=== Ownership and publishing for the operations guide ===
Drivers: dhellmann

Status: Resolved, they will start a SIG to own the repository for the guide so it can be published to docs.openstack.org.

References
* Wednesday, May 23, 2018 - session at Vancouver summit
* http://lists.openstack.org/pipermail/openstack-operators/2018-May/015321.html

=== StarlingX ===
Drivers: mnaser, EmilienM

Status: [https://storyboard.openstack.org/#!/story/2002123 In progress]

References
* [http://lists.openstack.org/pipermail/openstack-dev/2018-May/130715.html ML thread following up from summit]
* [http://lists.openstack.org/pipermail/openstack-dev/2018-May/130913.html ML thread post-summit discussions]
* [https://review.openstack.org/#/c/569562/ project-config change to import some of the repositories]

=== Murano Team Status ===
Drivers: dhellmann

Status: On hold

With ZTE's future at question, a Murano team member contacted me about the future of the project. I am currently waiting for the question to be raised in an email thread.

=== Organizational diversity tags ===
Drivers: ttx, mnaser

Status: Under discussion

References
* [http://lists.openstack.org/pipermail/openstack-dev/2018-May/130776.html openstack-dev mailing list thread raising the topic]

=== Clarifying the terms of service for hosted projects ===
Drivers: zaneb

Status: Under discussion

References
* [http://lists.openstack.org/pipermail/openstack-dev/2018-May/130807.html openstack-dev mailing list thread raising the topic]

=== Technical Vision for OpenStack ===
Drivers: zaneb, ttx, cdent

Status: Early

Zane offered to start creating a "technical vision" for OpenStack to help clarify the boundary for where projects fit into OpenStack and where they may not.

References
* [https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21739/official-projects-and-the-boundary-of-what-is-openstack Rocky Forum session]

=== Stein Series Goals ===
Drivers: smcginnis

Status: Early

Sean organized a session at the Rocky Forum to discuss improving our goal selection process and specific goals for Stein.

References
* [https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21738/s-release-goals Rocky Forum session]

=== Anti-nitpicking Cultural Change ===
Drivers: TheJulia, ttx

Status: In progress

References
* [http://lists.openstack.org/pipermail/openstack-dev/2018-May/130802.html openstack-dev mailing list thread]

=== Trove Project Health ===
Drivers: ttx, theJulia

Status: New

During the public cloud issues session at the Rocky Forum someone in the room raised the question of whether Trove is still actively maintained.

References
* [https://etherpad.openstack.org/p/YVR-forum-missing-features-pc Missing features in OpenStack for public clouds] forum session notes

=== tags indicating the upgrade support in deployment tools ===
Drivers: ttx

Status: New

During the FFU session at the Rocky Forum, Dan Smith and David Medberry indicated interest in defining tags to describe what upgrade features deployment tools have.

References
* [https://etherpad.openstack.org/p/YVR-forum-fast-forward-upgrades Rocky Forum session notes]

=== Reviewing the TC Vision ===
Drivers: ttx, EmilienM, fungi

Status: [https://storyboard.openstack.org/#!/story/2002132 In progress]

References
* [https://etherpad.openstack.org/p/YVR-tc-retrospective TC Retrospective Notes from Rocky Forum]

=== Reviewing TC Office Hour Times and Locations ===
Drivers: dhellmann

Status: New

During the retrospective at the Rocky Forum we talked about changing our office hour times or using different tools to make them more accessible.

References
* [https://etherpad.openstack.org/p/YVR-tc-retrospective TC Retrospective Notes from Rocky Forum]

=== Actively Monitoring Teams ===
Drivers: dhellmann

Status: New

During the retrospective at the Rocky Forum we discussed more actively engaging with project teams and SIGs to anticipate issues we can help resolve.

'''Dragonflow''' did not produce a Queens release. Their last release was 4.0.0 on Sept 1, 2017. Should projects that do not prepare releases be considered official? -- dhellmann

'''Rally''' may be moving out to GitHub? https://github.com/xrally and https://xrally.org -- dhellmann

References
* [https://etherpad.openstack.org/p/YVR-tc-retrospective TC Retrospective Notes from Rocky Forum]

=== Status of Electorate ===
Drivers:

Status: New

During the retrospective at the Rocky Forum we discussed the status of the TC electorate, and what is perceived as a low level of engagement. This needs a bit more research to compare recent elections so we can understand how things stand, and then we should talk about ways to improve the situation.

References
* [https://etherpad.openstack.org/p/YVR-tc-retrospective TC Retrospective Notes from Rocky Forum]

=== Improving the help-wanted list ===
Drivers: dims

Status: New

During the Board/TC/UC meeting at Vancouver, we came up with an idea on what we can put together a better way to ask platinum/gold and other companies in the eco system for help (crossing traditional job descriptions and volunteer/skill match websites)

References
* [https://etherpad.openstack.org/p/job-description-template Sample Job description template]

=== project infrastructure governance proposal ===
Drivers: dhellmann

Status: Under discussion

corvus started a discussion about the relationship between the foundation projects and the infrastructure management team as that team shifts from being governed by the TC to being a foundation-wide project.

References
* http://lists.openstack.org/pipermail/openstack-dev/2018-May/130896.html

=== finding help for the unified CLI team ===
Drivers:

Status: Needs a driver

During the office hours on 7 June we talked about adding OSC to the "help wanted" list. We decided we did not have enough information about what the team needs to write it up yet, so we need someone to gather that information and to propose the addition.

== Liaisons ==

This section of the tracker lists the TC members attached as liaisons to each of the project teams, [[OpenStack_SIGs|SIGs]], or [[UserCommittee#Working_Groups_and_Teams|working groups]]. The idea is for these liaisons to keep up with the general health of the group, understand any issues they encounter, and help them work with the TC on solutions if necessary. Some TC members may be more active within the group than the basic liaison responsibilities imply, but that is not required.

Liaisons should monitor their groups by:
* reading meeting logs or participating in meetings
* watching summit "project update" videos
* reading relevant messages on the mailing list
* talking with the PTL, chair, and other group members

=== SIGs ===

* API
** TC members:
* FEMDC
** TC members:
* First Contact
** TC members: fungi
* K8s
** TC members: dims
* Resource Management
** TC members:
* Scientific
** TC members:
* Security
** TC members: fungi
* Self-healing
** TC members:
* Upgrade
** TC members:

=== Working Groups ===

* App Dev Enablement
** TC members:
* Enterprise
** TC members:
* Fault Genes
** TC members:
* [[InteropWG|Interop]]
** TC members: dims
* LCOO
** TC members:
* Large Deployment
** TC members:
* Massively Distributed Clouds
** TC members:
* Ops Tags
** TC members: smcginnis
* Operators Telecom/NFV
** TC members: smcginnis
* Product
** TC members:

=== Project Teams ===

* Barbican
** TC members: fungi
* Blazar
** TC members:
* Chef Openstack
** TC members:
* Cinder
** TC members: smcginnis
* Cloudkitty
** TC members:
* Congress
** TC members:
* Cyborg
** TC members:
* Designate
** TC members:
* Documentation
** TC members:
* Dragonflow
** TC members:
* Ec2-Api
** TC members:
* Freezer
** TC members:
* Glance
** TC members: smcginnis
* Heat
** TC members:
* Horizon
** TC members:
* I18n
** TC members:
* Infrastructure
** TC members: fungi
* Ironic
** TC members:
* Karbor
** TC members:
* Keystone
** TC members: fungi,cmurphy
* Kolla
** TC members:
* Kuryr
** TC members:
* Loci
** TC members:
* Magnum
** TC members:
* Manila
** TC members: smcginnis
* Masakari
** TC members:
* Mistral
** TC members:
* Monasca
** TC members:
* Murano
** TC members:
* Neutron
** TC members:
* Nova
** TC members:
* Octavia
** TC members:
* Openstack Charms
** TC members:
* Openstack-Helm
** TC members:
* Openstackansible
** TC members:
* Openstackclient
** TC members: dhellmann
* Openstacksdk
** TC members:
* Oslo
** TC members: dhellmann
* Packaging-Rpm
** TC members: cmurphy
* Powervmstackers
** TC members:
* Puppet Openstack
** TC members:
* Qinling
** TC members:
* Quality Assurance
** TC members:
* Rally
** TC members:
* Refstack
** TC members: fungi
* Release Management
** TC members: dhellmann, smcginnis
* Requirements
** TC members: fungi, dhellmann
* Sahara
** TC members:
* Searchlight
** TC members:
* Security
** TC members: fungi
* Senlin
** TC members:
* Solum
** TC members:
* Stable Branch Maintenance
** TC members: fungi, smcginnis
* Storlets
** TC members:
* Swift
** TC members: smcginnis
* Tacker
** TC members:
* Telemetry
** TC members:
* Tricircle
** TC members:
* Tripleo
** TC members:
* Trove
** TC members:
* Vitrage
** TC members:
* Watcher
** TC members:
* Winstackers
** TC members:
* Zaqar
** TC members:
* Zun
** TC members:

First Contact SIG

2018-03-21T09:03:24Z

Colleen Murphy: /* Meeting Agenda */

First Contact SIG

2017-12-01T08:45:31Z

Colleen Murphy: /* First Contact SIG */

==First Contact SIG==

'''Our Mission'''
To provide a place and group of people for new contributors to come to for information and advice. New contributors are the future of OpenStack and the surrounding community. Its important to make sure they feel welcome and give them the tools to succeed.

'''Chairs'''
* Kendall Nelson (diablo_rojo) UTC -8
*

'''Members'''
* Zhipeng Huang (zhipeng)
* Amy Marrich (spotz) UTC-6
* Colleen Murphy (cmurphy) UTC+1

===Helpful Resources===
* [https://www.openstack.org/community/ Contributor Portal]
* [[Mentoring]]
* [[Outreachy]]

Meetings/InfraTeamMeeting

2017-03-21T18:41:56Z

Colleen Murphy: /* Agenda for next meeting */

= Weekly Project Infrastructure team meeting =

The OpenStack Project Infrastructure Team holds public weekly meetings in <code><nowiki>#openstack-meeting</nowiki></code>, Tuesdays at 1900 UTC. Everyone interested in infrastructure and process surrounding automated testing and deployment is encouraged to attend.

Please feel free to add agenda items (and your IRC nick in parenthesis).

== Agenda for next meeting ==

* Announcements

* Actions from last meeting

* Specs approval
** APPROVED: [http://specs.openstack.org/openstack-infra/infra-specs/specs/zuulv3.html#jobs Zuul v3: remove references to swift]
** APPROVED: [http://specs.openstack.org/openstack-infra/infra-specs/specs/zuulv3.html#projects Zuul v3: update job trees to graphs]
* Priority Efforts
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/ansible_puppet_apply.html Ansible Puppet Apply]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/task-tracker.html A Task Tracker for OpenStack]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/zuulv3.html Zuul v3]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/gerrit-2.13.html Gerrit 2.13 Upgrade]

* General topics
** Can we ever get rid of openstack-infra and openstack-dev Git namespaces? (fungi)
** puppet 4? (cmurphy)

* Open discussion

== Upcoming Project Renames ==
(any additions should mention original->new full names and link to the corresponding project-config rename change in Gerrit)

[https://review.openstack.org/433414 DefCore -> Interop Working Group]

== Previous meetings ==
Previous meetings, with their notes and logs, can be found at http://eavesdrop.openstack.org/meetings/infra/ and earlier at http://eavesdrop.openstack.org/meetings/ci/

Meetings/InfraTeamMeeting

2016-06-13T23:08:32Z

Colleen Murphy: /* Agenda for next meeting */

= Weekly Project Infrastructure team meeting =

The OpenStack Project Infrastructure Team holds public weekly meetings in <code><nowiki>#openstack-meeting</nowiki></code>, Tuesdays at 1900 UTC. Everyone interested in infrastructure and process surrounding automated testing and deployment is encouraged to attend.

Please feel free to add agenda items (and your IRC nick in parenthesis).

== Agenda for next meeting ==

* Announcements
* Actions from last meeting
* Specs approval
* Priority Efforts
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/ansible_puppet_apply.html Ansible Puppet Apply]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/dib-nodepool.html Use Diskimage Builder in Nodepool]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/infra-cloud.html Infra-cloud]
*** Upgrade kilo -> mitaka?
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/logs-in-swift.html Store Build Logs in Swift]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/maniphest.html maniphest migration]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/openstackci.html Common OpenStack CI Solution]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/zuulv3.html Zuul v3]
* [https://www.mail-archive.com/openstack-infra@lists.openstack.org/msg04374.html Updated Gerrit GC test results] (zaro)
* Open discussion

== Upcoming Project Renames ==
(any additions should mention original->new full names and link to the corresponding change in Gerrit)

* Fix snafu with the openstack-infra/ansible-puppet rename on June 3 (transparent to users, but we need some Gerrit cleanup for a duplicate project)
* Rename openstack/higgins to openstack/zun: https://review.openstack.org/#/c/326306/

== Previous meetings ==
Previous meetings, with their notes and logs, can be found at http://eavesdrop.openstack.org/meetings/infra/ and earlier at http://eavesdrop.openstack.org/meetings/ci/

Meetings/InfraTeamMeeting

2016-04-19T18:10:45Z

Colleen Murphy: /* Agenda for next meeting */

{{:Header}}

= Weekly Project Infrastructure team meeting =

The OpenStack Project Infrastructure Team holds public weekly meetings in <code><nowiki>#openstack-meeting</nowiki></code>, Tuesdays at 1900 UTC. Everyone interested in infrastructure and process surrounding automated testing and deployment is encouraged to attend.

Please feel free to add agenda items (and your IRC nick in parenthesis).

== Agenda for next meeting ==

* Announcements
* Actions from last meeting
* Specs approval
* Priority Efforts
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/ansible_puppet_apply.html Ansible Puppet Apply]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/dib-nodepool.html Use Diskimage Builder in Nodepool]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/infra-cloud.html Infra-cloud]
*** Houston data center power shutoff (crinkle/yolanda/rcarrillocruz)
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/logs-in-swift.html Store Build Logs in Swift]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/maniphest.html maniphest migration]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/openstackci.html Common OpenStack CI Solution]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/zuulv3.html Zuul v3]
* [https://storyboard.openstack.org/#!/story/2000028 Storyboard needs a dev server] (Zara, pleia2)
* Infra-cloud changes needed with new setup (east/west, network ranges)
* Open discussion

== Upcoming Project Renames ==
(any additions should mention original->new full names and link to the corresponding change in Gerrit)

openstack/openstack-ansible-ironic -> openstack/openstack-ansible-os_ironic https://review.openstack.org/299192

== Previous meetings ==
Previous meetings, with their notes and logs, can be found at http://eavesdrop.openstack.org/meetings/infra/ and earlier at http://eavesdrop.openstack.org/meetings/ci/

Meetings/InfraTeamMeeting

2016-02-09T18:59:16Z

Colleen Murphy: /* Agenda for next meeting */

{{:Header}}

= Weekly Project Infrastructure team meeting =

The OpenStack Project Infrastructure Team holds public weekly meetings in <code><nowiki>#openstack-meeting</nowiki></code>, Tuesdays at 1900 UTC. Everyone interested in infrastructure and process surrounding automated testing and deployment is encouraged to attend.

Please feel free to add agenda items (and your IRC nick in parenthesis).

== Agenda for next meeting ==

* Announcements
* Actions from last meeting
* Specs approval
** APPROVED: [https://review.openstack.org/252678 Unified Mirrors]
** PROPOSED: [https://review.openstack.org/273673 Update unified mirror spec to support AFS] (jeblair)
** PROPOSED: [https://review.openstack.org/276481 Maintenance change to doc publishing spec] (jeblair)
* Priority Efforts
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/ansible_puppet_apply.html Ansible Puppet Apply]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/dib-nodepool.html Use Diskimage Builder in Nodepool]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/infra-cloud.html Infra-cloud]
*** Using USWest region in nodepool
*** open reviews: topic:infra-cloud
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/logs-in-swift.html Store Build Logs in Swift]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/maniphest.html maniphest migration]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/openstackci.html Common OpenStack CI Solution]
** [http://specs.openstack.org/openstack-infra/infra-specs/specs/zuulv3.html Zuul v3]
* Scheduling a Gerrit project rename batch maintenance (SergeyLukjanov)
* [https://wiki.openstack.org/wiki/Sprints/InfraMitakaSprint Infra-cloud Sprint] is under two weeks away, any final logistical details? (pleia2)
* AFS for logs/docs (jeblair)
** We are using AFS for real now and have learned some things.
** Are we ready to seriously consider it for logs/docs? Any other prereqs?
** Specs:
*** https://review.openstack.org/269928
*** https://review.openstack.org/276482
* Open discussion

== Upcoming Project Renames ==
(any additions should mention original->new full names and link to the corresponding change in Gerrit)

* openstack/ceilometer-specs -> openstack/telemetry-specs
** rename patch: https://review.openstack.org/248897
** governance: https://review.openstack.org/240809
* openstack/sahara-scenario -> openstack/sahara-tests
** rename patch: https://review.openstack.org/269815

== Previous meetings ==
Previous meetings, with their notes and logs, can be found at http://eavesdrop.openstack.org/meetings/infra/ and earlier at http://eavesdrop.openstack.org/meetings/ci/