OpenStack - User contributions [en]

PTG/Rocky/Etherpads

2018-02-26T12:03:05Z

Szaher:

__NOTOC__

This is the list of etherpads for the Projects Team Gathering in Dublin. 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].

Sign up for [https://docs.google.com/spreadsheets/d/1MK7rCgYXCQZP1AgQ0RUiuc-cEXIzW5RuRzz5BWhV4nQ/edit#gid=0 team video interviews].

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

'''Projects:'''
* Blazar - https://etherpad.openstack.org/p/blazar-ptg-rocky
* Cinder - https://etherpad.openstack.org/p/cinder-ptg-rocky
* Designate - https://etherpad.openstack.org/p/designate-ptg-rocky
* Cyborg - https://etherpad.openstack.org/p/cyborg-ptg-rocky
* Docs/I18n - https://etherpad.openstack.org/p/docs-i18n-ptg-rocky
* Freezer - https://etherpad.openstack.org/p/freezer-ptg-rocky
* Glance - https://etherpad.openstack.org/p/glance-rocky-ptg-planning
* Heat - https://etherpad.openstack.org/p/heat-rocky-ptg
* Horizon - https://etherpad.openstack.org/p/horizon-ptg-rocky
* Infra - https://etherpad.openstack.org/p/infra-rocky-ptg
* Ironic - https://etherpad.openstack.org/p/ironic-rocky-ptg
* Keystone - https://etherpad.openstack.org/p/keystone-rocky-ptg
* Kolla - https://etherpad.openstack.org/p/kolla-rocky-ptg-planning
* Kuryr - https://etherpad.openstack.org/p/kuryr-ptg-rocky
* Magnum - https://etherpad.openstack.org/p/magnum-ptg-rocky
* Manila - https://etherpad.openstack.org/p/manila-rocky-ptg
* Mistral - https://etherpad.openstack.org/p/mistral-ptg-rocky
* Monasca - https://etherpad.openstack.org/p/monasca-ptg-rocky
* Neutron - https://etherpad.openstack.org/p/neutron-ptg-rocky
* Nova - https://etherpad.openstack.org/p/nova-ptg-rocky
* Octavia - https://etherpad.openstack.org/p/octavia-ptg-rocky
* Openstack-Ansible - https://etherpad.openstack.org/p/osa-rocky-ptg
* OpenStack-Charms - https://etherpad.openstack.org/p/DUB-charms-devroom
* OpenStack-Helm - https://etherpad.openstack.org/p/openstack-helm-ptg-rocky
* Oslo - https://etherpad.openstack.org/p/oslo-ptg-rocky
* QA - https://etherpad.openstack.org/p/qa-rocky-ptg
* RelMgt - https://etherpad.openstack.org/p/relmgt-ptg-rocky
* Requirements - https://etherpad.openstack.org/p/rocky-PTG-requirements
* Sahara - https://etherpad.openstack.org/p/sahara-rocky-ptg
* Swift - https://etherpad.openstack.org/p/Dublin_PTG_Swift
* TripleO - https://etherpad.openstack.org/p/tripleo-ptg-rocky
* Vitrage - https://etherpad.openstack.org/p/vitrage-ptg-rocky
* Watcher - https://etherpad.openstack.org/p/rocky-watcher-ptg

'''SIG/Theme/Other:'''
* API SIG - https://etherpad.openstack.org/p/api-sig-ptg-rocky
* Edge/FEMDC - https://etherpad.openstack.org/p/edge-ptg-dublin
* Cross-project identity integration (Monday & Tuesday) - https://etherpad.openstack.org/p/baremetal-vm-rocky-ptg
* Fast-forward Upgrades - https://etherpad.openstack.org/p/ffu-ptg-rocky
* First Contact SIG - https://etherpad.openstack.org/p/FC_SIG_Rocky_PTG
* K8s SIG - https://etherpad.openstack.org/p/sig-k8s-2018-dublin-ptg
* OpenStack Upstream Institute (OUI): https://etherpad.openstack.org/p/OUI-Rocky-PTG
* Public Cloud WG - https://etherpad.openstack.org/p/publiccloud-wg-ptg-rocky
* Release cycles and downstream consumption models - https://etherpad.openstack.org/p/release-cycles-ptg-rocky
* RefStack / Interop WG - https://etherpad.openstack.org/p/InteropDublin2018PTG
* Scientific SIG - https://etherpad.openstack.org/p/scientific-sig-ptg-rocky
* Security SIG - https://etherpad.openstack.org/p/security-ptg-rocky
* Self-healing SIG: https://etherpad.openstack.org/p/self-healing-ptg-rocky
* StoryBoard: https://etherpad.openstack.org/p/StoryBoard-Rocky-PTG
* TC (Friday) - https://etherpad.openstack.org/p/PTG-Dublin-TC-topics
* UC (Tuesday) - https://etherpad.openstack.org/p/UC-Rocky-PTG

Release Naming/R Proposals

2017-03-24T11:34:03Z

Szaher: /* Proposed Names */

== R Release Naming ==

According to the [http://governance.openstack.org/reference/release-naming.html Release Naming Process], this page will contain a list of nominated names for the R release of OpenStack. We will accept nominations until 2017-03-29 23:59:59 UTC.

=== Release Name Criteria ===

* Each release name must start with the letter of the ISO basic Latin alphabet following the initial letter of the previous release, starting with the initial release of "Austin". After "Z", the next name should start with "A" again.
* The name must be composed only of the 26 characters of the ISO basic Latin alphabet. Names which can be transliterated into this character set are also acceptable.
* The name must refer to the physical or human geography of the region encompassing the location of the OpenStack design summit for the corresponding release. The exact boundaries of the geographic region under consideration must be declared before the opening of nominations, as part of the initiation of the selection process.
* The name must be a single word with a maximum of 10 characters. Words that describe the feature should not be included, so "Foo City" or "Foo Peak" would both be eligible as "Foo".

Names which do not meet these criteria but otherwise sound really cool
should be added to a separate section of the wiki page and the TC may
make an exception for one or more of them to be considered in the
Condorcet poll. The naming official is responsible for presenting the
list of exceptional names for consideration to the TC before the poll
opens.

=== Exact Geographic Region ===

The Geographic Region from where names for the R release will come is [https://en.wikipedia.org/wiki/British_Columbia British Columbia]

=== Proposed Names ===

* [https://en.wikipedia.org/wiki/Radium_Hot_Springs Radium]
* [https://en.wikipedia.org/wiki/Revelstoke,_British_Columbia Revelstoke (City - Columbia)]
* [https://en.wikipedia.org/wiki/Richmond,_British_Columbia Richmond (City - Vancouver)]
* [https://en.wikipedia.org/wiki/Rocky_Mountains Rocky (Mountains)]
* [https://en.wikipedia.org/wiki/Rossland,_British_Columbia Rossland (City - Kootenay Boundary)]
* [https://goo.gl/maps/a7sj9aw2SMH2 Rupert]
* [https://en.wikipedia.org/wiki/Razorback_Mountain_(British_Columbia) Razorback (Mountain)]
* [https://en.wikipedia.org/wiki/Rambler_Peak Rambler (Peak)]
* [https://en.wikipedia.org/wiki/Roderick_Island Roderick (Island)]
* [https://en.wikipedia.org/wiki/Raspberry,_British_Columbia Raspberry]
* [https://en.wikipedia.org/wiki/Mount_Root Root (Mount Root)]
* [https://en.wikipedia.org/wiki/Ray_Lake Ray (Lake)]
* [https://en.wikipedia.org/wiki/Rock_Creek_(British_Columbia) Rock (Creek)]
* [https://www.ukclimbing.com/logbook/c.php?i=230240 Rambles] (A classic rock climb on the Squamish chief)
* [https://www.lonelyplanet.com/canada/vancouver/attractions/railspur-alley/a/poi-sig/1161243/361261 Railspur] (Railspur Alley in Granville Island, Vancouver - a place to meet makers and buy their goods from wood and metals to sake and silks)
* [https://en.wikipedia.org/wiki/Canadian_Rockies Rockies]
* [https://en.wikipedia.org/wiki/Rosswood,_British_Columbia Rosswood]

=== Proposed Names that do not meet the criteria ===

* [https://en.wikipedia.org/wiki/Roundabout Roundabout]
* [https://en.wikipedia.org/wiki/Roustabout Roustabout]

CrossProjectLiaisons

2017-03-14T23:04:59Z

Szaher: /* Product Working Group */

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

== Oslo ==

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

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

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Barbican || Douglas Mendizábal || redrobot
|-
| Ceilometer || Julien Danjou || jd__
|-
| Cinder || Jay Bryant || jungleboyj
|-
| Congress || Eric Kao || ekcs
|-
| Cue || Min Pae || sputnik13
|-
| Designate || ||
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Flavio Percoco || flaper87
|-
| Heat || Thomas Herve || therve
|-
| Horizon || Kirill Zaitsev || kzaitsev_
|-
| Ironic || ||
|-
| Keystone || Brant Knudson || bknudson
|-
| Manila || Thomas Bechtold || toabctl
|-
| Mistral || Renat Akhmerov || rakhmerov
|-
| Murano || ||
|-
| Neutron || Victor Morales || electrocucaracha
|-
| Nova || ||
|-
| [[Octavia]] || Michael Johnson || johnsom
|-
| Sahara || Telles Nobrega, Shu Yingya || tellesnobrega, shuyingya
|-
| Senlin || Yanyan Hu || Yanyanhu
|-

| Swift || ||
|-
| TripleO || Ben Nemec || bnemec
|-
| Trove || Amrith Kumar || amrith
|-
| Zaqar || Flavio Percoco || flaper87
|-
|}

== Release management ==

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

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

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Barbican || Dave McCowan || dave-mccowan
|-
| Ceilometer || gordon chung || gordc
|-
| Cinder || Sean McGinnis || smcginnis
|-
| Congress || Eric Kao || ekcs
|-
| Designate || Graham Hayes || mugsie
|-
| Documentation || Mariia Zlatkova & Brian Moss || ?? & bmoss
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Ian Cordasco || sigmavirus
|-
| Heat || Thomas Herve || therve
|-
| Horizon || Rob Cresswell || robcresswell
|-
| I18n || Ian Y. Choi || ianychoi
|-
| Ironic || Jim Rollenhagen || jroll
|-
| Keystone || Lance Bragstad || lbragstad
|-
| Kolla || Jeffrey Zhang || Jeffrey4l
|-
| Magnum || Adrian Otto || adrian_otto
|-
| Manila || Ben Swartzlander || bswartz
|-
| Mistral || Lingxian Kong || kong
|-
| Monasca || Witek Bedyk || witek
|-
| Murano ||Kirill Zaitsev || kzaitsev_
|-
| Neutron || Dariusz Smigiel || dasm
|-
| Nova || Sylvain Bauza || bauzas
|-
| OpenStack-Ansible || Jean-Philippe Evrard || evrardjp
|-
| Oslo || ChangBo Guo || gcb
|-
| PuppetOpenStack || Alex Schultz || mwhahaha
|-
| Sahara || Telles Nobrega || tenobreg/tellesnobrega
|-
| Searchlight || Steve McLellan || sjmc7
|-
| Senlin || Qiming Teng || Qiming
|-
| Solum || Devdatta Kulkarni/ZhuRong || devkulkarni/zhurong
|-
| Storlets || Eran Rom || eranrom
|-
| Swift || John Dickinson || notmyname
|-
| TripleO || Emilien Macchi || EmilienM
|-
| Trove || Amrith Kumar || amrith
|-
| Watcher || Alexander Chadin || alexchadin
|-
| Winstackers || Claudiu Belu || claudiub
|-
| Zaqar || Fei Long Wang || flwang
|}

== QA ==

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

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

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

== 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 || Sean Mcginnis || smcginnis
|-
| Congress || Aimee Ukasick || aimeeu
|-
| Designate || Graham Hayes || mugsie
|-
| Freezer || Guillermo Garcia || m3mo
|-
| Glance || Alexander Bashmakov || abashmak
|-
| Heat || Rabi Mishra || ramishra
|-
| Horizon || Richard Jones || r1chardj0n3s
|-
| I18n || KATO Tomoyuki || katomo
|-
| Ironic || Jay Faulkner || JayF
|-
| Keystone || Richard Avelar || ravelar
|-
| Kolla || Sayantani Goswami || sayantani01
|-
| Magnum || Spyros Trigazis || strigazi
|-
| Manila || Ben Swartzlander || bswartz
|-
| Mistral || Dougal Matthews || d0ugal
|-
| Murano || Kirill Zaitsev || kzaitsev_
|-
| Neutron || John Davidge || john-davidge
|-
| Nova || Zhenyu Zheng, Nicolas Bock || Kevin_Zheng, nicolasbock
|-
| OpenStack-Ansible || Amy Marrich || spotz
|-
| Ops || Robert Starmer ||
|-
| Oslo || Doug Hellmann || dhellmann
|-
| Puppet OpenStack || Emilien Macchi || EmilienM
|-
| Rally || Boris Pavlovic || boris-42
|-
| Sahara || Telles Nobrega and Elise Gafford || tellesnobrega egafford
|-
| Senlin || Cindia Blue || lixinhui
|-
| Swift || John Dickinson || notmyname
|-
| Tripleo || Steven Hardy || shardy
|-
| Trove || Trevor McCasland || trevormc
|-
| Watcher || Prudhvi Rao Shedimbi || pshedimb
|-
| Zaqar || Fei Long Wang || flwang
|}

== Stable Branch ==

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

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

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Barbican || Dave McCowan || dave-mccowan
|-
| Ceilometer || Eoghan Glynn || eglynn
|-
| Cinder || Jay Bryant || jungleboyj
|-
| Congress || Masahito Muroi || masahito
|-
| Freezer || Saad Zaher || szaher
|-
| Heat || Zane Bitter || zaneb
|-
| Horizon || Matthias Runge || mrunge
|-
| Ironic || Dmitry Tantsur || dtantsur
|-
| Keystone || Dolph Mathews || dolphm
|-
| Mistral || Renat Akhmerov || rakhmerov
|-
| Murano || Kirill Zaitsev || kzaitsev_
|-
| Neutron || Ihar Hrachyshka || ihrachys
|-
| Nova || Matt Riedemann || mriedem
|-
| Sahara || Vitaly Gridnev || vgridnev
|-
| Senlin|| Qiming Teng || Qiming
|-
| Swift || Matthew Oliver || mattoliverau
|-
| Trove || Amrith Kumar || amrith
|-
| Watcher || David Tardivel || dtardivel
|-
| Zaqar || Fei Long Wang || flwang
|-
|}

== Vulnerability management ==

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

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

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Barbican || Douglas Mendizábal or Charles Neill || redrobot / ccneill
|-
| Ceilometer || Lianhao Lu or Gordon Chung || llu/gordc
|-
| Cinder || ||
|-
| Congress || Masahito Muroi || masahito
|-
| Freezer || Saad Zaher or Pierre Mathieu || szaher or slashme
|-
| Glance || Hemanth Makkapati or Nikhil Komawar || hemanthm or nikhil
|-
| Heat || Steve Hardy || shardy
|-
| Horizon || Rob Cresswell || robcresswell
|-
| Ironic || Jay Faulkner || JayF
|-
| Keystone || Dolph Mathews || dolphm
|-
| Kolla || Michal Jastrzebski || inc0
|-
| Manila || Tom Barron || tbarron
|-
| Murano || Victor Ryzhenkin || freerunner
|-
| Neutron || Kevin Benton || kevinbenton
|-
| Nova || Michael Still || mikal
|-
| Sahara || Telles Nobrega || tellesnobrega
|-
| Searchlight || Travis Tripp or Steve McLellan || TravT or sjmc7
|-
| Senlin || Qiming Teng || Qiming
|-
| Swift || ||
|-
| Trove || Amrith Kumar, Craig Vyvial or Nikhil Manchanda || amrith, cp16net or SlickNik
|-
| Zaqar || Fei Long Wang || flwang
|-
|}

== API Working Group ==

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

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

== Logging Working Group ==

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

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

== Infra ==

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

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Congress || Any Congress core reviewer may ACK: Anusha Ramineni, Eric Kao, Tim Hinrichs, Masahito Muroi || ramineni, ekcs, thinrichs, masahito
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Flavio Percoco|| flaper87
|-
| Ironic || Dmitry Tantsur, Jim Rollenhagen, Vasyl Saienko || dtantsur, jroll, vsaienko
|-
| Kolla || Any Kolla Core Reviewer may ack an infra change on behalf of the PTL || inc0, jeffrey4l, kfox1111, pbourke, sdake are primary contacts
|-
| Neutron || Anindita Das, Dariusz Smigiel, Ihar Hrachyshka, Armando Migliaccio || dasanind, dasm, ihrachys, armax
|-
| Documentation || Andreas Jaeger|| AJaeger

|-
| Trove || Amrith Kumar, Nikhil Manchanda || amrith, SlickNik

|-
| Murano || Victor Ryzhenkin || freerunner

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

|-
| Fuel || Aleksandra Fedorova, Igor Belikov || bookwar, igorbelikov

|-
| Puppet OpenStack || Emilien Macchi || EmilienM

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

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

More information about the team can be found on the [[ProductTeam|Product WG wiki]].

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Ceilometer ||Krish Ragurham ||
|-
| Cinder || Shamail Tahir || shamail
|-
| Congress || Eric Kao || ekcs
|-
| Freezer || Pierre Mathieu || slashme
|-
| Glance || - || -
|-
| Horizon || Carol Barrett || carolbarrett
|-
| Ironic || Yih Leong Sun || leong
|-
| Keystone || Megan Rossetti, Krish Raguram|| MeganR, KrishR
|-
| Kolla || Yih Leong Sun || leong
|-
| Magnum || Steve Gordon || sgordon
|-
| Manila ||Pete Chadwick || pchadwick
|-
| Neutron || Mike Cohen, Duane DeCapite || DuaneDeC7
|-
| Nova || Hugh Blemings || hughhalf
|-
| OSClient || Megan Rossetti || MeganR
|-
| Stable Release|| Rochelle Grober || rockig
|-
| QA || Arkady Kanevsky || arkady_kanevsky
|-
| Rally || Arkady Kanevsky || arkady_kanevsky
|-
| Sahara || Elise Gafford || egafford
|-
| Senlin || Qiming Teng || Qiming
|-
| Swift || Phil Williams || philipw
|-
| Tempest || Arkady Kanevsky || arkady_kanevsky
|-
| Trove || Amrith Kumar || amrith
|-
| Watcher || Megan Rossetti || MeganR
|-
|}

== 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
|-
| Astara || ||
|-
| Barbican || ||
|-
| Cinder || ||
|-
| Designate || Graham Hayes || mugsie
|-
| Glance || ||
|-
| Heat || ||
|-
| Horizon || Akihiro Motoki || amotoki
|-
| Ironic || ||
|-
| Keystone || ||
|-
| Magnum || Shu Muto || shu-mutou
|-
| Manila || ||
|-
| Monasca || ||
|-
| Murano || ||
|-
| Neutron || Akihiro Motoki || amotoki
|-
| Nova || Augustina Ragwitz || auggy
|-
| Oslo || ||
|-
| Sahara || Luigi Toscano, Jeremy Freudberg || tosky, jeremyfreudberg
|-
| Senlin || ||
|-
| Swift || ||
|-
| Tacker || ||
|-
| Telemetry || ||
|-
| TripleO || Julie Pichon || jpich
|-
| Trove || ||
|-
| Sahara || Chad Roberts || crobertsrh
|-
| Watcher || Yumeng Bao || Yumeng
|-
| Zaqar || ||
|-
|}

== Inter-project Liaisons ==

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

{| class="wikitable"
|-
! Projects !! Name !! IRC Handle !! Role
|-
| Nova / Neutron || || ||
|-
| || Kevin Benton || kevinbenton || Neutron liaison for Nova
|-
| Nova / Glance || || ||
|-
| || Flavio Percoco, Mike Fedosin || flaper87, mfedosin || Glance liaison for Nova
|-
| || Jay Pipes || jaypipes || Nova liaison for Glance
|-
| Nova / Cinder || || ||
|-
| || Scott DAngelo || scottda || Cinder liaison for Nova
|-
| || Matt Riedemann || mriedem || Nova liason for Cinder
|-
| Nova / Ironic || || ||
|-
| || Jim Rollenhagen || jroll || Ironic liaison for Nova
|-
| Neutron / Ironic || || ||
|-
| || Sukhdev Kapur || sukhdev || Neutron liaison for Ironic
|-
| || Sam Betts || sambetts || Ironic liaison for Neutron
|-
| Murano / Glance || || ||
|-
| || Alexander Tivelkov || ativelkov || Glance liaison for Murano, Murano liaison for Glance
|-
| Horizon / i18n || || ||
|-
| || Doug Fish || doug-fish || Horizon liaison for i18n
|-
| || TBD || || Heat liaison for Sahara
|-
| Fuel / Puppet || || ||
|-
| || Alex Schultz || mwhahaha || Fuel liaison for Puppet
|-
| Fuel / Ironic || || ||
|-
| || Evgeny L || evgenyl || Fuel liaison for Ironic
|-
| Bareon / Ironic || || ||
|-
| || Evgeny L || evgenyl || Bareon liaison for Ironic
|-
| Magnum / Kuryr || || ||
|-
| || Ton Ngo || tango || Magnum liaison for Kuryr
|-
| || Fawad Khaliq || fawadkhaliq || Kuryr liaison for Magnum
|-
| TripleO / Ironic || || ||
|-
| || Dmitry Tantsur || dtantsur || Ironic liaison for TripleO
|-
| Nova / Watcher || || ||
|-
| || Ed Leafe || edleafe || Nova liaison for Watcher
|}

=== Etherpads ===

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

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

== Cross-Project Spec Liaisons ==

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

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

|}

CrossProjectLiaisons

2017-03-14T23:04:13Z

Szaher: /* Infra */

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

== Oslo ==

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

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

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Barbican || Douglas Mendizábal || redrobot
|-
| Ceilometer || Julien Danjou || jd__
|-
| Cinder || Jay Bryant || jungleboyj
|-
| Congress || Eric Kao || ekcs
|-
| Cue || Min Pae || sputnik13
|-
| Designate || ||
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Flavio Percoco || flaper87
|-
| Heat || Thomas Herve || therve
|-
| Horizon || Kirill Zaitsev || kzaitsev_
|-
| Ironic || ||
|-
| Keystone || Brant Knudson || bknudson
|-
| Manila || Thomas Bechtold || toabctl
|-
| Mistral || Renat Akhmerov || rakhmerov
|-
| Murano || ||
|-
| Neutron || Victor Morales || electrocucaracha
|-
| Nova || ||
|-
| [[Octavia]] || Michael Johnson || johnsom
|-
| Sahara || Telles Nobrega, Shu Yingya || tellesnobrega, shuyingya
|-
| Senlin || Yanyan Hu || Yanyanhu
|-

| Swift || ||
|-
| TripleO || Ben Nemec || bnemec
|-
| Trove || Amrith Kumar || amrith
|-
| Zaqar || Flavio Percoco || flaper87
|-
|}

== Release management ==

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

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

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Barbican || Dave McCowan || dave-mccowan
|-
| Ceilometer || gordon chung || gordc
|-
| Cinder || Sean McGinnis || smcginnis
|-
| Congress || Eric Kao || ekcs
|-
| Designate || Graham Hayes || mugsie
|-
| Documentation || Mariia Zlatkova & Brian Moss || ?? & bmoss
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Ian Cordasco || sigmavirus
|-
| Heat || Thomas Herve || therve
|-
| Horizon || Rob Cresswell || robcresswell
|-
| I18n || Ian Y. Choi || ianychoi
|-
| Ironic || Jim Rollenhagen || jroll
|-
| Keystone || Lance Bragstad || lbragstad
|-
| Kolla || Jeffrey Zhang || Jeffrey4l
|-
| Magnum || Adrian Otto || adrian_otto
|-
| Manila || Ben Swartzlander || bswartz
|-
| Mistral || Lingxian Kong || kong
|-
| Monasca || Witek Bedyk || witek
|-
| Murano ||Kirill Zaitsev || kzaitsev_
|-
| Neutron || Dariusz Smigiel || dasm
|-
| Nova || Sylvain Bauza || bauzas
|-
| OpenStack-Ansible || Jean-Philippe Evrard || evrardjp
|-
| Oslo || ChangBo Guo || gcb
|-
| PuppetOpenStack || Alex Schultz || mwhahaha
|-
| Sahara || Telles Nobrega || tenobreg/tellesnobrega
|-
| Searchlight || Steve McLellan || sjmc7
|-
| Senlin || Qiming Teng || Qiming
|-
| Solum || Devdatta Kulkarni/ZhuRong || devkulkarni/zhurong
|-
| Storlets || Eran Rom || eranrom
|-
| Swift || John Dickinson || notmyname
|-
| TripleO || Emilien Macchi || EmilienM
|-
| Trove || Amrith Kumar || amrith
|-
| Watcher || Alexander Chadin || alexchadin
|-
| Winstackers || Claudiu Belu || claudiub
|-
| Zaqar || Fei Long Wang || flwang
|}

== QA ==

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

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

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

== 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 || Sean Mcginnis || smcginnis
|-
| Congress || Aimee Ukasick || aimeeu
|-
| Designate || Graham Hayes || mugsie
|-
| Freezer || Guillermo Garcia || m3mo
|-
| Glance || Alexander Bashmakov || abashmak
|-
| Heat || Rabi Mishra || ramishra
|-
| Horizon || Richard Jones || r1chardj0n3s
|-
| I18n || KATO Tomoyuki || katomo
|-
| Ironic || Jay Faulkner || JayF
|-
| Keystone || Richard Avelar || ravelar
|-
| Kolla || Sayantani Goswami || sayantani01
|-
| Magnum || Spyros Trigazis || strigazi
|-
| Manila || Ben Swartzlander || bswartz
|-
| Mistral || Dougal Matthews || d0ugal
|-
| Murano || Kirill Zaitsev || kzaitsev_
|-
| Neutron || John Davidge || john-davidge
|-
| Nova || Zhenyu Zheng, Nicolas Bock || Kevin_Zheng, nicolasbock
|-
| OpenStack-Ansible || Amy Marrich || spotz
|-
| Ops || Robert Starmer ||
|-
| Oslo || Doug Hellmann || dhellmann
|-
| Puppet OpenStack || Emilien Macchi || EmilienM
|-
| Rally || Boris Pavlovic || boris-42
|-
| Sahara || Telles Nobrega and Elise Gafford || tellesnobrega egafford
|-
| Senlin || Cindia Blue || lixinhui
|-
| Swift || John Dickinson || notmyname
|-
| Tripleo || Steven Hardy || shardy
|-
| Trove || Trevor McCasland || trevormc
|-
| Watcher || Prudhvi Rao Shedimbi || pshedimb
|-
| Zaqar || Fei Long Wang || flwang
|}

== Stable Branch ==

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

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

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Barbican || Dave McCowan || dave-mccowan
|-
| Ceilometer || Eoghan Glynn || eglynn
|-
| Cinder || Jay Bryant || jungleboyj
|-
| Congress || Masahito Muroi || masahito
|-
| Freezer || Saad Zaher || szaher
|-
| Heat || Zane Bitter || zaneb
|-
| Horizon || Matthias Runge || mrunge
|-
| Ironic || Dmitry Tantsur || dtantsur
|-
| Keystone || Dolph Mathews || dolphm
|-
| Mistral || Renat Akhmerov || rakhmerov
|-
| Murano || Kirill Zaitsev || kzaitsev_
|-
| Neutron || Ihar Hrachyshka || ihrachys
|-
| Nova || Matt Riedemann || mriedem
|-
| Sahara || Vitaly Gridnev || vgridnev
|-
| Senlin|| Qiming Teng || Qiming
|-
| Swift || Matthew Oliver || mattoliverau
|-
| Trove || Amrith Kumar || amrith
|-
| Watcher || David Tardivel || dtardivel
|-
| Zaqar || Fei Long Wang || flwang
|-
|}

== Vulnerability management ==

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

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

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Barbican || Douglas Mendizábal or Charles Neill || redrobot / ccneill
|-
| Ceilometer || Lianhao Lu or Gordon Chung || llu/gordc
|-
| Cinder || ||
|-
| Congress || Masahito Muroi || masahito
|-
| Freezer || Saad Zaher or Pierre Mathieu || szaher or slashme
|-
| Glance || Hemanth Makkapati or Nikhil Komawar || hemanthm or nikhil
|-
| Heat || Steve Hardy || shardy
|-
| Horizon || Rob Cresswell || robcresswell
|-
| Ironic || Jay Faulkner || JayF
|-
| Keystone || Dolph Mathews || dolphm
|-
| Kolla || Michal Jastrzebski || inc0
|-
| Manila || Tom Barron || tbarron
|-
| Murano || Victor Ryzhenkin || freerunner
|-
| Neutron || Kevin Benton || kevinbenton
|-
| Nova || Michael Still || mikal
|-
| Sahara || Telles Nobrega || tellesnobrega
|-
| Searchlight || Travis Tripp or Steve McLellan || TravT or sjmc7
|-
| Senlin || Qiming Teng || Qiming
|-
| Swift || ||
|-
| Trove || Amrith Kumar, Craig Vyvial or Nikhil Manchanda || amrith, cp16net or SlickNik
|-
| Zaqar || Fei Long Wang || flwang
|-
|}

== API Working Group ==

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

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

== Logging Working Group ==

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

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

== Infra ==

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

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Congress || Any Congress core reviewer may ACK: Anusha Ramineni, Eric Kao, Tim Hinrichs, Masahito Muroi || ramineni, ekcs, thinrichs, masahito
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Flavio Percoco|| flaper87
|-
| Ironic || Dmitry Tantsur, Jim Rollenhagen, Vasyl Saienko || dtantsur, jroll, vsaienko
|-
| Kolla || Any Kolla Core Reviewer may ack an infra change on behalf of the PTL || inc0, jeffrey4l, kfox1111, pbourke, sdake are primary contacts
|-
| Neutron || Anindita Das, Dariusz Smigiel, Ihar Hrachyshka, Armando Migliaccio || dasanind, dasm, ihrachys, armax
|-
| Documentation || Andreas Jaeger|| AJaeger

|-
| Trove || Amrith Kumar, Nikhil Manchanda || amrith, SlickNik

|-
| Murano || Victor Ryzhenkin || freerunner

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

|-
| Fuel || Aleksandra Fedorova, Igor Belikov || bookwar, igorbelikov

|-
| Puppet OpenStack || Emilien Macchi || EmilienM

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

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

More information about the team can be found on the [[ProductTeam|Product WG wiki]].

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Ceilometer ||Krish Ragurham ||
|-
| Cinder || Shamail Tahir || shamail
|-
| Congress || Eric Kao || ekcs
|-
| Glance || - || -
|-
| Horizon || Carol Barrett || carolbarrett
|-
| Ironic || Yih Leong Sun || leong
|-
| Keystone || Megan Rossetti, Krish Raguram|| MeganR, KrishR
|-
| Kolla || Yih Leong Sun || leong
|-
| Magnum || Steve Gordon || sgordon
|-
| Manila ||Pete Chadwick || pchadwick
|-
| Neutron || Mike Cohen, Duane DeCapite || DuaneDeC7
|-
| Nova || Hugh Blemings || hughhalf
|-
| OSClient || Megan Rossetti || MeganR
|-
| Stable Release|| Rochelle Grober || rockig
|-
| QA || Arkady Kanevsky || arkady_kanevsky
|-
| Rally || Arkady Kanevsky || arkady_kanevsky
|-
| Sahara || Elise Gafford || egafford
|-
| Senlin || Qiming Teng || Qiming
|-
| Swift || Phil Williams || philipw
|-
| Tempest || Arkady Kanevsky || arkady_kanevsky
|-
| Trove || Amrith Kumar || amrith
|-
| Watcher || Megan Rossetti || MeganR
|-
|}

== 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
|-
| Astara || ||
|-
| Barbican || ||
|-
| Cinder || ||
|-
| Designate || Graham Hayes || mugsie
|-
| Glance || ||
|-
| Heat || ||
|-
| Horizon || Akihiro Motoki || amotoki
|-
| Ironic || ||
|-
| Keystone || ||
|-
| Magnum || Shu Muto || shu-mutou
|-
| Manila || ||
|-
| Monasca || ||
|-
| Murano || ||
|-
| Neutron || Akihiro Motoki || amotoki
|-
| Nova || Augustina Ragwitz || auggy
|-
| Oslo || ||
|-
| Sahara || Luigi Toscano, Jeremy Freudberg || tosky, jeremyfreudberg
|-
| Senlin || ||
|-
| Swift || ||
|-
| Tacker || ||
|-
| Telemetry || ||
|-
| TripleO || Julie Pichon || jpich
|-
| Trove || ||
|-
| Sahara || Chad Roberts || crobertsrh
|-
| Watcher || Yumeng Bao || Yumeng
|-
| Zaqar || ||
|-
|}

== Inter-project Liaisons ==

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

{| class="wikitable"
|-
! Projects !! Name !! IRC Handle !! Role
|-
| Nova / Neutron || || ||
|-
| || Kevin Benton || kevinbenton || Neutron liaison for Nova
|-
| Nova / Glance || || ||
|-
| || Flavio Percoco, Mike Fedosin || flaper87, mfedosin || Glance liaison for Nova
|-
| || Jay Pipes || jaypipes || Nova liaison for Glance
|-
| Nova / Cinder || || ||
|-
| || Scott DAngelo || scottda || Cinder liaison for Nova
|-
| || Matt Riedemann || mriedem || Nova liason for Cinder
|-
| Nova / Ironic || || ||
|-
| || Jim Rollenhagen || jroll || Ironic liaison for Nova
|-
| Neutron / Ironic || || ||
|-
| || Sukhdev Kapur || sukhdev || Neutron liaison for Ironic
|-
| || Sam Betts || sambetts || Ironic liaison for Neutron
|-
| Murano / Glance || || ||
|-
| || Alexander Tivelkov || ativelkov || Glance liaison for Murano, Murano liaison for Glance
|-
| Horizon / i18n || || ||
|-
| || Doug Fish || doug-fish || Horizon liaison for i18n
|-
| || TBD || || Heat liaison for Sahara
|-
| Fuel / Puppet || || ||
|-
| || Alex Schultz || mwhahaha || Fuel liaison for Puppet
|-
| Fuel / Ironic || || ||
|-
| || Evgeny L || evgenyl || Fuel liaison for Ironic
|-
| Bareon / Ironic || || ||
|-
| || Evgeny L || evgenyl || Bareon liaison for Ironic
|-
| Magnum / Kuryr || || ||
|-
| || Ton Ngo || tango || Magnum liaison for Kuryr
|-
| || Fawad Khaliq || fawadkhaliq || Kuryr liaison for Magnum
|-
| TripleO / Ironic || || ||
|-
| || Dmitry Tantsur || dtantsur || Ironic liaison for TripleO
|-
| Nova / Watcher || || ||
|-
| || Ed Leafe || edleafe || Nova liaison for Watcher
|}

=== Etherpads ===

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

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

== Cross-Project Spec Liaisons ==

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

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

|}

CrossProjectLiaisons

2017-03-14T23:01:46Z

Szaher: /* Vulnerability management */

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

== Oslo ==

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

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

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Barbican || Douglas Mendizábal || redrobot
|-
| Ceilometer || Julien Danjou || jd__
|-
| Cinder || Jay Bryant || jungleboyj
|-
| Congress || Eric Kao || ekcs
|-
| Cue || Min Pae || sputnik13
|-
| Designate || ||
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Flavio Percoco || flaper87
|-
| Heat || Thomas Herve || therve
|-
| Horizon || Kirill Zaitsev || kzaitsev_
|-
| Ironic || ||
|-
| Keystone || Brant Knudson || bknudson
|-
| Manila || Thomas Bechtold || toabctl
|-
| Mistral || Renat Akhmerov || rakhmerov
|-
| Murano || ||
|-
| Neutron || Victor Morales || electrocucaracha
|-
| Nova || ||
|-
| [[Octavia]] || Michael Johnson || johnsom
|-
| Sahara || Telles Nobrega, Shu Yingya || tellesnobrega, shuyingya
|-
| Senlin || Yanyan Hu || Yanyanhu
|-

| Swift || ||
|-
| TripleO || Ben Nemec || bnemec
|-
| Trove || Amrith Kumar || amrith
|-
| Zaqar || Flavio Percoco || flaper87
|-
|}

== Release management ==

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

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

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Barbican || Dave McCowan || dave-mccowan
|-
| Ceilometer || gordon chung || gordc
|-
| Cinder || Sean McGinnis || smcginnis
|-
| Congress || Eric Kao || ekcs
|-
| Designate || Graham Hayes || mugsie
|-
| Documentation || Mariia Zlatkova & Brian Moss || ?? & bmoss
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Ian Cordasco || sigmavirus
|-
| Heat || Thomas Herve || therve
|-
| Horizon || Rob Cresswell || robcresswell
|-
| I18n || Ian Y. Choi || ianychoi
|-
| Ironic || Jim Rollenhagen || jroll
|-
| Keystone || Lance Bragstad || lbragstad
|-
| Kolla || Jeffrey Zhang || Jeffrey4l
|-
| Magnum || Adrian Otto || adrian_otto
|-
| Manila || Ben Swartzlander || bswartz
|-
| Mistral || Lingxian Kong || kong
|-
| Monasca || Witek Bedyk || witek
|-
| Murano ||Kirill Zaitsev || kzaitsev_
|-
| Neutron || Dariusz Smigiel || dasm
|-
| Nova || Sylvain Bauza || bauzas
|-
| OpenStack-Ansible || Jean-Philippe Evrard || evrardjp
|-
| Oslo || ChangBo Guo || gcb
|-
| PuppetOpenStack || Alex Schultz || mwhahaha
|-
| Sahara || Telles Nobrega || tenobreg/tellesnobrega
|-
| Searchlight || Steve McLellan || sjmc7
|-
| Senlin || Qiming Teng || Qiming
|-
| Solum || Devdatta Kulkarni/ZhuRong || devkulkarni/zhurong
|-
| Storlets || Eran Rom || eranrom
|-
| Swift || John Dickinson || notmyname
|-
| TripleO || Emilien Macchi || EmilienM
|-
| Trove || Amrith Kumar || amrith
|-
| Watcher || Alexander Chadin || alexchadin
|-
| Winstackers || Claudiu Belu || claudiub
|-
| Zaqar || Fei Long Wang || flwang
|}

== QA ==

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

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

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

== 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 || Sean Mcginnis || smcginnis
|-
| Congress || Aimee Ukasick || aimeeu
|-
| Designate || Graham Hayes || mugsie
|-
| Freezer || Guillermo Garcia || m3mo
|-
| Glance || Alexander Bashmakov || abashmak
|-
| Heat || Rabi Mishra || ramishra
|-
| Horizon || Richard Jones || r1chardj0n3s
|-
| I18n || KATO Tomoyuki || katomo
|-
| Ironic || Jay Faulkner || JayF
|-
| Keystone || Richard Avelar || ravelar
|-
| Kolla || Sayantani Goswami || sayantani01
|-
| Magnum || Spyros Trigazis || strigazi
|-
| Manila || Ben Swartzlander || bswartz
|-
| Mistral || Dougal Matthews || d0ugal
|-
| Murano || Kirill Zaitsev || kzaitsev_
|-
| Neutron || John Davidge || john-davidge
|-
| Nova || Zhenyu Zheng, Nicolas Bock || Kevin_Zheng, nicolasbock
|-
| OpenStack-Ansible || Amy Marrich || spotz
|-
| Ops || Robert Starmer ||
|-
| Oslo || Doug Hellmann || dhellmann
|-
| Puppet OpenStack || Emilien Macchi || EmilienM
|-
| Rally || Boris Pavlovic || boris-42
|-
| Sahara || Telles Nobrega and Elise Gafford || tellesnobrega egafford
|-
| Senlin || Cindia Blue || lixinhui
|-
| Swift || John Dickinson || notmyname
|-
| Tripleo || Steven Hardy || shardy
|-
| Trove || Trevor McCasland || trevormc
|-
| Watcher || Prudhvi Rao Shedimbi || pshedimb
|-
| Zaqar || Fei Long Wang || flwang
|}

== Stable Branch ==

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

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

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Barbican || Dave McCowan || dave-mccowan
|-
| Ceilometer || Eoghan Glynn || eglynn
|-
| Cinder || Jay Bryant || jungleboyj
|-
| Congress || Masahito Muroi || masahito
|-
| Freezer || Saad Zaher || szaher
|-
| Heat || Zane Bitter || zaneb
|-
| Horizon || Matthias Runge || mrunge
|-
| Ironic || Dmitry Tantsur || dtantsur
|-
| Keystone || Dolph Mathews || dolphm
|-
| Mistral || Renat Akhmerov || rakhmerov
|-
| Murano || Kirill Zaitsev || kzaitsev_
|-
| Neutron || Ihar Hrachyshka || ihrachys
|-
| Nova || Matt Riedemann || mriedem
|-
| Sahara || Vitaly Gridnev || vgridnev
|-
| Senlin|| Qiming Teng || Qiming
|-
| Swift || Matthew Oliver || mattoliverau
|-
| Trove || Amrith Kumar || amrith
|-
| Watcher || David Tardivel || dtardivel
|-
| Zaqar || Fei Long Wang || flwang
|-
|}

== Vulnerability management ==

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

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

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Barbican || Douglas Mendizábal or Charles Neill || redrobot / ccneill
|-
| Ceilometer || Lianhao Lu or Gordon Chung || llu/gordc
|-
| Cinder || ||
|-
| Congress || Masahito Muroi || masahito
|-
| Freezer || Saad Zaher or Pierre Mathieu || szaher or slashme
|-
| Glance || Hemanth Makkapati or Nikhil Komawar || hemanthm or nikhil
|-
| Heat || Steve Hardy || shardy
|-
| Horizon || Rob Cresswell || robcresswell
|-
| Ironic || Jay Faulkner || JayF
|-
| Keystone || Dolph Mathews || dolphm
|-
| Kolla || Michal Jastrzebski || inc0
|-
| Manila || Tom Barron || tbarron
|-
| Murano || Victor Ryzhenkin || freerunner
|-
| Neutron || Kevin Benton || kevinbenton
|-
| Nova || Michael Still || mikal
|-
| Sahara || Telles Nobrega || tellesnobrega
|-
| Searchlight || Travis Tripp or Steve McLellan || TravT or sjmc7
|-
| Senlin || Qiming Teng || Qiming
|-
| Swift || ||
|-
| Trove || Amrith Kumar, Craig Vyvial or Nikhil Manchanda || amrith, cp16net or SlickNik
|-
| Zaqar || Fei Long Wang || flwang
|-
|}

== API Working Group ==

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

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

== Logging Working Group ==

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

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

== Infra ==

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

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Congress || Any Congress core reviewer may ACK: Anusha Ramineni, Eric Kao, Tim Hinrichs, Masahito Muroi || ramineni, ekcs, thinrichs, masahito
|-
| Glance || Flavio Percoco|| flaper87
|-
| Ironic || Dmitry Tantsur, Jim Rollenhagen, Vasyl Saienko || dtantsur, jroll, vsaienko
|-
| Kolla || Any Kolla Core Reviewer may ack an infra change on behalf of the PTL || inc0, jeffrey4l, kfox1111, pbourke, sdake are primary contacts
|-
| Neutron || Anindita Das, Dariusz Smigiel, Ihar Hrachyshka, Armando Migliaccio || dasanind, dasm, ihrachys, armax
|-
| Documentation || Andreas Jaeger|| AJaeger

|-
| Trove || Amrith Kumar, Nikhil Manchanda || amrith, SlickNik

|-
| Murano || Victor Ryzhenkin || freerunner

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

|-
| Fuel || Aleksandra Fedorova, Igor Belikov || bookwar, igorbelikov

|-
| Puppet OpenStack || Emilien Macchi || EmilienM

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

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

More information about the team can be found on the [[ProductTeam|Product WG wiki]].

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Ceilometer ||Krish Ragurham ||
|-
| Cinder || Shamail Tahir || shamail
|-
| Congress || Eric Kao || ekcs
|-
| Glance || - || -
|-
| Horizon || Carol Barrett || carolbarrett
|-
| Ironic || Yih Leong Sun || leong
|-
| Keystone || Megan Rossetti, Krish Raguram|| MeganR, KrishR
|-
| Kolla || Yih Leong Sun || leong
|-
| Magnum || Steve Gordon || sgordon
|-
| Manila ||Pete Chadwick || pchadwick
|-
| Neutron || Mike Cohen, Duane DeCapite || DuaneDeC7
|-
| Nova || Hugh Blemings || hughhalf
|-
| OSClient || Megan Rossetti || MeganR
|-
| Stable Release|| Rochelle Grober || rockig
|-
| QA || Arkady Kanevsky || arkady_kanevsky
|-
| Rally || Arkady Kanevsky || arkady_kanevsky
|-
| Sahara || Elise Gafford || egafford
|-
| Senlin || Qiming Teng || Qiming
|-
| Swift || Phil Williams || philipw
|-
| Tempest || Arkady Kanevsky || arkady_kanevsky
|-
| Trove || Amrith Kumar || amrith
|-
| Watcher || Megan Rossetti || MeganR
|-
|}

== 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
|-
| Astara || ||
|-
| Barbican || ||
|-
| Cinder || ||
|-
| Designate || Graham Hayes || mugsie
|-
| Glance || ||
|-
| Heat || ||
|-
| Horizon || Akihiro Motoki || amotoki
|-
| Ironic || ||
|-
| Keystone || ||
|-
| Magnum || Shu Muto || shu-mutou
|-
| Manila || ||
|-
| Monasca || ||
|-
| Murano || ||
|-
| Neutron || Akihiro Motoki || amotoki
|-
| Nova || Augustina Ragwitz || auggy
|-
| Oslo || ||
|-
| Sahara || Luigi Toscano, Jeremy Freudberg || tosky, jeremyfreudberg
|-
| Senlin || ||
|-
| Swift || ||
|-
| Tacker || ||
|-
| Telemetry || ||
|-
| TripleO || Julie Pichon || jpich
|-
| Trove || ||
|-
| Sahara || Chad Roberts || crobertsrh
|-
| Watcher || Yumeng Bao || Yumeng
|-
| Zaqar || ||
|-
|}

== Inter-project Liaisons ==

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

{| class="wikitable"
|-
! Projects !! Name !! IRC Handle !! Role
|-
| Nova / Neutron || || ||
|-
| || Kevin Benton || kevinbenton || Neutron liaison for Nova
|-
| Nova / Glance || || ||
|-
| || Flavio Percoco, Mike Fedosin || flaper87, mfedosin || Glance liaison for Nova
|-
| || Jay Pipes || jaypipes || Nova liaison for Glance
|-
| Nova / Cinder || || ||
|-
| || Scott DAngelo || scottda || Cinder liaison for Nova
|-
| || Matt Riedemann || mriedem || Nova liason for Cinder
|-
| Nova / Ironic || || ||
|-
| || Jim Rollenhagen || jroll || Ironic liaison for Nova
|-
| Neutron / Ironic || || ||
|-
| || Sukhdev Kapur || sukhdev || Neutron liaison for Ironic
|-
| || Sam Betts || sambetts || Ironic liaison for Neutron
|-
| Murano / Glance || || ||
|-
| || Alexander Tivelkov || ativelkov || Glance liaison for Murano, Murano liaison for Glance
|-
| Horizon / i18n || || ||
|-
| || Doug Fish || doug-fish || Horizon liaison for i18n
|-
| || TBD || || Heat liaison for Sahara
|-
| Fuel / Puppet || || ||
|-
| || Alex Schultz || mwhahaha || Fuel liaison for Puppet
|-
| Fuel / Ironic || || ||
|-
| || Evgeny L || evgenyl || Fuel liaison for Ironic
|-
| Bareon / Ironic || || ||
|-
| || Evgeny L || evgenyl || Bareon liaison for Ironic
|-
| Magnum / Kuryr || || ||
|-
| || Ton Ngo || tango || Magnum liaison for Kuryr
|-
| || Fawad Khaliq || fawadkhaliq || Kuryr liaison for Magnum
|-
| TripleO / Ironic || || ||
|-
| || Dmitry Tantsur || dtantsur || Ironic liaison for TripleO
|-
| Nova / Watcher || || ||
|-
| || Ed Leafe || edleafe || Nova liaison for Watcher
|}

=== Etherpads ===

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

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

== Cross-Project Spec Liaisons ==

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

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

|}

CrossProjectLiaisons

2017-03-14T23:00:04Z

Szaher: /* 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 now more projects consuming code from the Oslo incubator than we have Oslo contributors. That means we are going to need your help to make these migrations happen. We are asking for one person from each project to serve as a liaison between the project and Oslo, and to assist with integrating changes as we move code out of the incubator into libraries.

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

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Barbican || Douglas Mendizábal || redrobot
|-
| Ceilometer || Julien Danjou || jd__
|-
| Cinder || Jay Bryant || jungleboyj
|-
| Congress || Eric Kao || ekcs
|-
| Cue || Min Pae || sputnik13
|-
| Designate || ||
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Flavio Percoco || flaper87
|-
| Heat || Thomas Herve || therve
|-
| Horizon || Kirill Zaitsev || kzaitsev_
|-
| Ironic || ||
|-
| Keystone || Brant Knudson || bknudson
|-
| Manila || Thomas Bechtold || toabctl
|-
| Mistral || Renat Akhmerov || rakhmerov
|-
| Murano || ||
|-
| Neutron || Victor Morales || electrocucaracha
|-
| Nova || ||
|-
| [[Octavia]] || Michael Johnson || johnsom
|-
| Sahara || Telles Nobrega, Shu Yingya || tellesnobrega, shuyingya
|-
| Senlin || Yanyan Hu || Yanyanhu
|-

| Swift || ||
|-
| TripleO || Ben Nemec || bnemec
|-
| Trove || Amrith Kumar || amrith
|-
| Zaqar || Flavio Percoco || flaper87
|-
|}

== Release management ==

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

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

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Barbican || Dave McCowan || dave-mccowan
|-
| Ceilometer || gordon chung || gordc
|-
| Cinder || Sean McGinnis || smcginnis
|-
| Congress || Eric Kao || ekcs
|-
| Designate || Graham Hayes || mugsie
|-
| Documentation || Mariia Zlatkova & Brian Moss || ?? & bmoss
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Ian Cordasco || sigmavirus
|-
| Heat || Thomas Herve || therve
|-
| Horizon || Rob Cresswell || robcresswell
|-
| I18n || Ian Y. Choi || ianychoi
|-
| Ironic || Jim Rollenhagen || jroll
|-
| Keystone || Lance Bragstad || lbragstad
|-
| Kolla || Jeffrey Zhang || Jeffrey4l
|-
| Magnum || Adrian Otto || adrian_otto
|-
| Manila || Ben Swartzlander || bswartz
|-
| Mistral || Lingxian Kong || kong
|-
| Monasca || Witek Bedyk || witek
|-
| Murano ||Kirill Zaitsev || kzaitsev_
|-
| Neutron || Dariusz Smigiel || dasm
|-
| Nova || Sylvain Bauza || bauzas
|-
| OpenStack-Ansible || Jean-Philippe Evrard || evrardjp
|-
| Oslo || ChangBo Guo || gcb
|-
| PuppetOpenStack || Alex Schultz || mwhahaha
|-
| Sahara || Telles Nobrega || tenobreg/tellesnobrega
|-
| Searchlight || Steve McLellan || sjmc7
|-
| Senlin || Qiming Teng || Qiming
|-
| Solum || Devdatta Kulkarni/ZhuRong || devkulkarni/zhurong
|-
| Storlets || Eran Rom || eranrom
|-
| Swift || John Dickinson || notmyname
|-
| TripleO || Emilien Macchi || EmilienM
|-
| Trove || Amrith Kumar || amrith
|-
| Watcher || Alexander Chadin || alexchadin
|-
| Winstackers || Claudiu Belu || claudiub
|-
| Zaqar || Fei Long Wang || flwang
|}

== QA ==

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

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

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

== 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 || Sean Mcginnis || smcginnis
|-
| Congress || Aimee Ukasick || aimeeu
|-
| Designate || Graham Hayes || mugsie
|-
| Freezer || Guillermo Garcia || m3mo
|-
| Glance || Alexander Bashmakov || abashmak
|-
| Heat || Rabi Mishra || ramishra
|-
| Horizon || Richard Jones || r1chardj0n3s
|-
| I18n || KATO Tomoyuki || katomo
|-
| Ironic || Jay Faulkner || JayF
|-
| Keystone || Richard Avelar || ravelar
|-
| Kolla || Sayantani Goswami || sayantani01
|-
| Magnum || Spyros Trigazis || strigazi
|-
| Manila || Ben Swartzlander || bswartz
|-
| Mistral || Dougal Matthews || d0ugal
|-
| Murano || Kirill Zaitsev || kzaitsev_
|-
| Neutron || John Davidge || john-davidge
|-
| Nova || Zhenyu Zheng, Nicolas Bock || Kevin_Zheng, nicolasbock
|-
| OpenStack-Ansible || Amy Marrich || spotz
|-
| Ops || Robert Starmer ||
|-
| Oslo || Doug Hellmann || dhellmann
|-
| Puppet OpenStack || Emilien Macchi || EmilienM
|-
| Rally || Boris Pavlovic || boris-42
|-
| Sahara || Telles Nobrega and Elise Gafford || tellesnobrega egafford
|-
| Senlin || Cindia Blue || lixinhui
|-
| Swift || John Dickinson || notmyname
|-
| Tripleo || Steven Hardy || shardy
|-
| Trove || Trevor McCasland || trevormc
|-
| Watcher || Prudhvi Rao Shedimbi || pshedimb
|-
| Zaqar || Fei Long Wang || flwang
|}

== Stable Branch ==

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

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

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Barbican || Dave McCowan || dave-mccowan
|-
| Ceilometer || Eoghan Glynn || eglynn
|-
| Cinder || Jay Bryant || jungleboyj
|-
| Congress || Masahito Muroi || masahito
|-
| Freezer || Saad Zaher || szaher
|-
| Heat || Zane Bitter || zaneb
|-
| Horizon || Matthias Runge || mrunge
|-
| Ironic || Dmitry Tantsur || dtantsur
|-
| Keystone || Dolph Mathews || dolphm
|-
| Mistral || Renat Akhmerov || rakhmerov
|-
| Murano || Kirill Zaitsev || kzaitsev_
|-
| Neutron || Ihar Hrachyshka || ihrachys
|-
| Nova || Matt Riedemann || mriedem
|-
| Sahara || Vitaly Gridnev || vgridnev
|-
| Senlin|| Qiming Teng || Qiming
|-
| Swift || Matthew Oliver || mattoliverau
|-
| Trove || Amrith Kumar || amrith
|-
| 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
|-
| Glance || Hemanth Makkapati or Nikhil Komawar || hemanthm or nikhil
|-
| Heat || Steve Hardy || shardy
|-
| Horizon || Rob Cresswell || robcresswell
|-
| Ironic || Jay Faulkner || JayF
|-
| Keystone || Dolph Mathews || dolphm
|-
| Kolla || Michal Jastrzebski || inc0
|-
| Manila || Tom Barron || tbarron
|-
| Murano || Victor Ryzhenkin || freerunner
|-
| Neutron || Kevin Benton || kevinbenton
|-
| Nova || Michael Still || mikal
|-
| Sahara || Telles Nobrega || tellesnobrega
|-
| Searchlight || Travis Tripp or Steve McLellan || TravT or sjmc7
|-
| Senlin || Qiming Teng || Qiming
|-
| Swift || ||
|-
| Trove || Amrith Kumar, Craig Vyvial or Nikhil Manchanda || amrith, cp16net or SlickNik
|-
| Zaqar || Fei Long Wang || flwang
|-
|}

== API Working Group ==

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

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

== Logging Working Group ==

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

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

== Infra ==

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

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Congress || Any Congress core reviewer may ACK: Anusha Ramineni, Eric Kao, Tim Hinrichs, Masahito Muroi || ramineni, ekcs, thinrichs, masahito
|-
| Glance || Flavio Percoco|| flaper87
|-
| Ironic || Dmitry Tantsur, Jim Rollenhagen, Vasyl Saienko || dtantsur, jroll, vsaienko
|-
| Kolla || Any Kolla Core Reviewer may ack an infra change on behalf of the PTL || inc0, jeffrey4l, kfox1111, pbourke, sdake are primary contacts
|-
| Neutron || Anindita Das, Dariusz Smigiel, Ihar Hrachyshka, Armando Migliaccio || dasanind, dasm, ihrachys, armax
|-
| Documentation || Andreas Jaeger|| AJaeger

|-
| Trove || Amrith Kumar, Nikhil Manchanda || amrith, SlickNik

|-
| Murano || Victor Ryzhenkin || freerunner

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

|-
| Fuel || Aleksandra Fedorova, Igor Belikov || bookwar, igorbelikov

|-
| Puppet OpenStack || Emilien Macchi || EmilienM

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

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

More information about the team can be found on the [[ProductTeam|Product WG wiki]].

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Ceilometer ||Krish Ragurham ||
|-
| Cinder || Shamail Tahir || shamail
|-
| Congress || Eric Kao || ekcs
|-
| Glance || - || -
|-
| Horizon || Carol Barrett || carolbarrett
|-
| Ironic || Yih Leong Sun || leong
|-
| Keystone || Megan Rossetti, Krish Raguram|| MeganR, KrishR
|-
| Kolla || Yih Leong Sun || leong
|-
| Magnum || Steve Gordon || sgordon
|-
| Manila ||Pete Chadwick || pchadwick
|-
| Neutron || Mike Cohen, Duane DeCapite || DuaneDeC7
|-
| Nova || Hugh Blemings || hughhalf
|-
| OSClient || Megan Rossetti || MeganR
|-
| Stable Release|| Rochelle Grober || rockig
|-
| QA || Arkady Kanevsky || arkady_kanevsky
|-
| Rally || Arkady Kanevsky || arkady_kanevsky
|-
| Sahara || Elise Gafford || egafford
|-
| Senlin || Qiming Teng || Qiming
|-
| Swift || Phil Williams || philipw
|-
| Tempest || Arkady Kanevsky || arkady_kanevsky
|-
| Trove || Amrith Kumar || amrith
|-
| Watcher || Megan Rossetti || MeganR
|-
|}

== 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
|-
| Astara || ||
|-
| Barbican || ||
|-
| Cinder || ||
|-
| Designate || Graham Hayes || mugsie
|-
| Glance || ||
|-
| Heat || ||
|-
| Horizon || Akihiro Motoki || amotoki
|-
| Ironic || ||
|-
| Keystone || ||
|-
| Magnum || Shu Muto || shu-mutou
|-
| Manila || ||
|-
| Monasca || ||
|-
| Murano || ||
|-
| Neutron || Akihiro Motoki || amotoki
|-
| Nova || Augustina Ragwitz || auggy
|-
| Oslo || ||
|-
| Sahara || Luigi Toscano, Jeremy Freudberg || tosky, jeremyfreudberg
|-
| Senlin || ||
|-
| Swift || ||
|-
| Tacker || ||
|-
| Telemetry || ||
|-
| TripleO || Julie Pichon || jpich
|-
| Trove || ||
|-
| Sahara || Chad Roberts || crobertsrh
|-
| Watcher || Yumeng Bao || Yumeng
|-
| Zaqar || ||
|-
|}

== Inter-project Liaisons ==

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

{| class="wikitable"
|-
! Projects !! Name !! IRC Handle !! Role
|-
| Nova / Neutron || || ||
|-
| || Kevin Benton || kevinbenton || Neutron liaison for Nova
|-
| Nova / Glance || || ||
|-
| || Flavio Percoco, Mike Fedosin || flaper87, mfedosin || Glance liaison for Nova
|-
| || Jay Pipes || jaypipes || Nova liaison for Glance
|-
| Nova / Cinder || || ||
|-
| || Scott DAngelo || scottda || Cinder liaison for Nova
|-
| || Matt Riedemann || mriedem || Nova liason for Cinder
|-
| Nova / Ironic || || ||
|-
| || Jim Rollenhagen || jroll || Ironic liaison for Nova
|-
| Neutron / Ironic || || ||
|-
| || Sukhdev Kapur || sukhdev || Neutron liaison for Ironic
|-
| || Sam Betts || sambetts || Ironic liaison for Neutron
|-
| Murano / Glance || || ||
|-
| || Alexander Tivelkov || ativelkov || Glance liaison for Murano, Murano liaison for Glance
|-
| Horizon / i18n || || ||
|-
| || Doug Fish || doug-fish || Horizon liaison for i18n
|-
| || TBD || || Heat liaison for Sahara
|-
| Fuel / Puppet || || ||
|-
| || Alex Schultz || mwhahaha || Fuel liaison for Puppet
|-
| Fuel / Ironic || || ||
|-
| || Evgeny L || evgenyl || Fuel liaison for Ironic
|-
| Bareon / Ironic || || ||
|-
| || Evgeny L || evgenyl || Bareon liaison for Ironic
|-
| Magnum / Kuryr || || ||
|-
| || Ton Ngo || tango || Magnum liaison for Kuryr
|-
| || Fawad Khaliq || fawadkhaliq || Kuryr liaison for Magnum
|-
| TripleO / Ironic || || ||
|-
| || Dmitry Tantsur || dtantsur || Ironic liaison for TripleO
|-
| Nova / Watcher || || ||
|-
| || Ed Leafe || edleafe || Nova liaison for Watcher
|}

=== Etherpads ===

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

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

== Cross-Project Spec Liaisons ==

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

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

|}

CrossProjectLiaisons

2017-03-14T22:59:10Z

Szaher: /* Release management */

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

== Oslo ==

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

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

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Barbican || Douglas Mendizábal || redrobot
|-
| Ceilometer || Julien Danjou || jd__
|-
| Cinder || Jay Bryant || jungleboyj
|-
| Congress || Eric Kao || ekcs
|-
| Cue || Min Pae || sputnik13
|-
| Designate || ||
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Flavio Percoco || flaper87
|-
| Heat || Thomas Herve || therve
|-
| Horizon || Kirill Zaitsev || kzaitsev_
|-
| Ironic || ||
|-
| Keystone || Brant Knudson || bknudson
|-
| Manila || Thomas Bechtold || toabctl
|-
| Mistral || Renat Akhmerov || rakhmerov
|-
| Murano || ||
|-
| Neutron || Victor Morales || electrocucaracha
|-
| Nova || ||
|-
| [[Octavia]] || Michael Johnson || johnsom
|-
| Sahara || Telles Nobrega, Shu Yingya || tellesnobrega, shuyingya
|-
| Senlin || Yanyan Hu || Yanyanhu
|-

| Swift || ||
|-
| TripleO || Ben Nemec || bnemec
|-
| Trove || Amrith Kumar || amrith
|-
| Zaqar || Flavio Percoco || flaper87
|-
|}

== Release management ==

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

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

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Barbican || Dave McCowan || dave-mccowan
|-
| Ceilometer || gordon chung || gordc
|-
| Cinder || Sean McGinnis || smcginnis
|-
| Congress || Eric Kao || ekcs
|-
| Designate || Graham Hayes || mugsie
|-
| Documentation || Mariia Zlatkova & Brian Moss || ?? & bmoss
|-
| Freezer || Saad Zaher || szaher
|-
| Glance || Ian Cordasco || sigmavirus
|-
| Heat || Thomas Herve || therve
|-
| Horizon || Rob Cresswell || robcresswell
|-
| I18n || Ian Y. Choi || ianychoi
|-
| Ironic || Jim Rollenhagen || jroll
|-
| Keystone || Lance Bragstad || lbragstad
|-
| Kolla || Jeffrey Zhang || Jeffrey4l
|-
| Magnum || Adrian Otto || adrian_otto
|-
| Manila || Ben Swartzlander || bswartz
|-
| Mistral || Lingxian Kong || kong
|-
| Monasca || Witek Bedyk || witek
|-
| Murano ||Kirill Zaitsev || kzaitsev_
|-
| Neutron || Dariusz Smigiel || dasm
|-
| Nova || Sylvain Bauza || bauzas
|-
| OpenStack-Ansible || Jean-Philippe Evrard || evrardjp
|-
| Oslo || ChangBo Guo || gcb
|-
| PuppetOpenStack || Alex Schultz || mwhahaha
|-
| Sahara || Telles Nobrega || tenobreg/tellesnobrega
|-
| Searchlight || Steve McLellan || sjmc7
|-
| Senlin || Qiming Teng || Qiming
|-
| Solum || Devdatta Kulkarni/ZhuRong || devkulkarni/zhurong
|-
| Storlets || Eran Rom || eranrom
|-
| Swift || John Dickinson || notmyname
|-
| TripleO || Emilien Macchi || EmilienM
|-
| Trove || Amrith Kumar || amrith
|-
| Watcher || Alexander Chadin || alexchadin
|-
| Winstackers || Claudiu Belu || claudiub
|-
| Zaqar || Fei Long Wang || flwang
|}

== QA ==

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

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

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

== 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 || Sean Mcginnis || smcginnis
|-
| Congress || Aimee Ukasick || aimeeu
|-
| Designate || Graham Hayes || mugsie
|-
| Freezer || Guillermo Garcia || m3mo
|-
| Glance || Alexander Bashmakov || abashmak
|-
| Heat || Rabi Mishra || ramishra
|-
| Horizon || Richard Jones || r1chardj0n3s
|-
| I18n || KATO Tomoyuki || katomo
|-
| Ironic || Jay Faulkner || JayF
|-
| Keystone || Richard Avelar || ravelar
|-
| Kolla || Sayantani Goswami || sayantani01
|-
| Magnum || Spyros Trigazis || strigazi
|-
| Manila || Ben Swartzlander || bswartz
|-
| Mistral || Dougal Matthews || d0ugal
|-
| Murano || Kirill Zaitsev || kzaitsev_
|-
| Neutron || John Davidge || john-davidge
|-
| Nova || Zhenyu Zheng, Nicolas Bock || Kevin_Zheng, nicolasbock
|-
| OpenStack-Ansible || Amy Marrich || spotz
|-
| Ops || Robert Starmer ||
|-
| Oslo || Doug Hellmann || dhellmann
|-
| Puppet OpenStack || Emilien Macchi || EmilienM
|-
| Rally || Boris Pavlovic || boris-42
|-
| Sahara || Telles Nobrega and Elise Gafford || tellesnobrega egafford
|-
| Senlin || Cindia Blue || lixinhui
|-
| Swift || John Dickinson || notmyname
|-
| Tripleo || Steven Hardy || shardy
|-
| Trove || Trevor McCasland || trevormc
|-
| Watcher || Prudhvi Rao Shedimbi || pshedimb
|-
| Zaqar || Fei Long Wang || flwang
|}

== Stable Branch ==

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

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

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Barbican || Dave McCowan || dave-mccowan
|-
| Ceilometer || Eoghan Glynn || eglynn
|-
| Cinder || Jay Bryant || jungleboyj
|-
| Congress || Masahito Muroi || masahito
|-
| Freezer || Pierre Mathieu || slashme
|-
| Heat || Zane Bitter || zaneb
|-
| Horizon || Matthias Runge || mrunge
|-
| Ironic || Dmitry Tantsur || dtantsur
|-
| Keystone || Dolph Mathews || dolphm
|-
| Mistral || Renat Akhmerov || rakhmerov
|-
| Murano || Kirill Zaitsev || kzaitsev_
|-
| Neutron || Ihar Hrachyshka || ihrachys
|-
| Nova || Matt Riedemann || mriedem
|-
| Sahara || Vitaly Gridnev || vgridnev
|-
| Senlin|| Qiming Teng || Qiming
|-
| Swift || Matthew Oliver || mattoliverau
|-
| Trove || Amrith Kumar || amrith
|-
| 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
|-
| Glance || Hemanth Makkapati or Nikhil Komawar || hemanthm or nikhil
|-
| Heat || Steve Hardy || shardy
|-
| Horizon || Rob Cresswell || robcresswell
|-
| Ironic || Jay Faulkner || JayF
|-
| Keystone || Dolph Mathews || dolphm
|-
| Kolla || Michal Jastrzebski || inc0
|-
| Manila || Tom Barron || tbarron
|-
| Murano || Victor Ryzhenkin || freerunner
|-
| Neutron || Kevin Benton || kevinbenton
|-
| Nova || Michael Still || mikal
|-
| Sahara || Telles Nobrega || tellesnobrega
|-
| Searchlight || Travis Tripp or Steve McLellan || TravT or sjmc7
|-
| Senlin || Qiming Teng || Qiming
|-
| Swift || ||
|-
| Trove || Amrith Kumar, Craig Vyvial or Nikhil Manchanda || amrith, cp16net or SlickNik
|-
| Zaqar || Fei Long Wang || flwang
|-
|}

== API Working Group ==

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

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

== Logging Working Group ==

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

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

== Infra ==

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

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Congress || Any Congress core reviewer may ACK: Anusha Ramineni, Eric Kao, Tim Hinrichs, Masahito Muroi || ramineni, ekcs, thinrichs, masahito
|-
| Glance || Flavio Percoco|| flaper87
|-
| Ironic || Dmitry Tantsur, Jim Rollenhagen, Vasyl Saienko || dtantsur, jroll, vsaienko
|-
| Kolla || Any Kolla Core Reviewer may ack an infra change on behalf of the PTL || inc0, jeffrey4l, kfox1111, pbourke, sdake are primary contacts
|-
| Neutron || Anindita Das, Dariusz Smigiel, Ihar Hrachyshka, Armando Migliaccio || dasanind, dasm, ihrachys, armax
|-
| Documentation || Andreas Jaeger|| AJaeger

|-
| Trove || Amrith Kumar, Nikhil Manchanda || amrith, SlickNik

|-
| Murano || Victor Ryzhenkin || freerunner

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

|-
| Fuel || Aleksandra Fedorova, Igor Belikov || bookwar, igorbelikov

|-
| Puppet OpenStack || Emilien Macchi || EmilienM

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

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

More information about the team can be found on the [[ProductTeam|Product WG wiki]].

{| class="wikitable"
|-
! Project !! Liaison !! IRC Handle
|-
| Ceilometer ||Krish Ragurham ||
|-
| Cinder || Shamail Tahir || shamail
|-
| Congress || Eric Kao || ekcs
|-
| Glance || - || -
|-
| Horizon || Carol Barrett || carolbarrett
|-
| Ironic || Yih Leong Sun || leong
|-
| Keystone || Megan Rossetti, Krish Raguram|| MeganR, KrishR
|-
| Kolla || Yih Leong Sun || leong
|-
| Magnum || Steve Gordon || sgordon
|-
| Manila ||Pete Chadwick || pchadwick
|-
| Neutron || Mike Cohen, Duane DeCapite || DuaneDeC7
|-
| Nova || Hugh Blemings || hughhalf
|-
| OSClient || Megan Rossetti || MeganR
|-
| Stable Release|| Rochelle Grober || rockig
|-
| QA || Arkady Kanevsky || arkady_kanevsky
|-
| Rally || Arkady Kanevsky || arkady_kanevsky
|-
| Sahara || Elise Gafford || egafford
|-
| Senlin || Qiming Teng || Qiming
|-
| Swift || Phil Williams || philipw
|-
| Tempest || Arkady Kanevsky || arkady_kanevsky
|-
| Trove || Amrith Kumar || amrith
|-
| Watcher || Megan Rossetti || MeganR
|-
|}

== 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
|-
| Astara || ||
|-
| Barbican || ||
|-
| Cinder || ||
|-
| Designate || Graham Hayes || mugsie
|-
| Glance || ||
|-
| Heat || ||
|-
| Horizon || Akihiro Motoki || amotoki
|-
| Ironic || ||
|-
| Keystone || ||
|-
| Magnum || Shu Muto || shu-mutou
|-
| Manila || ||
|-
| Monasca || ||
|-
| Murano || ||
|-
| Neutron || Akihiro Motoki || amotoki
|-
| Nova || Augustina Ragwitz || auggy
|-
| Oslo || ||
|-
| Sahara || Luigi Toscano, Jeremy Freudberg || tosky, jeremyfreudberg
|-
| Senlin || ||
|-
| Swift || ||
|-
| Tacker || ||
|-
| Telemetry || ||
|-
| TripleO || Julie Pichon || jpich
|-
| Trove || ||
|-
| Sahara || Chad Roberts || crobertsrh
|-
| Watcher || Yumeng Bao || Yumeng
|-
| Zaqar || ||
|-
|}

== Inter-project Liaisons ==

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

{| class="wikitable"
|-
! Projects !! Name !! IRC Handle !! Role
|-
| Nova / Neutron || || ||
|-
| || Kevin Benton || kevinbenton || Neutron liaison for Nova
|-
| Nova / Glance || || ||
|-
| || Flavio Percoco, Mike Fedosin || flaper87, mfedosin || Glance liaison for Nova
|-
| || Jay Pipes || jaypipes || Nova liaison for Glance
|-
| Nova / Cinder || || ||
|-
| || Scott DAngelo || scottda || Cinder liaison for Nova
|-
| || Matt Riedemann || mriedem || Nova liason for Cinder
|-
| Nova / Ironic || || ||
|-
| || Jim Rollenhagen || jroll || Ironic liaison for Nova
|-
| Neutron / Ironic || || ||
|-
| || Sukhdev Kapur || sukhdev || Neutron liaison for Ironic
|-
| || Sam Betts || sambetts || Ironic liaison for Neutron
|-
| Murano / Glance || || ||
|-
| || Alexander Tivelkov || ativelkov || Glance liaison for Murano, Murano liaison for Glance
|-
| Horizon / i18n || || ||
|-
| || Doug Fish || doug-fish || Horizon liaison for i18n
|-
| || TBD || || Heat liaison for Sahara
|-
| Fuel / Puppet || || ||
|-
| || Alex Schultz || mwhahaha || Fuel liaison for Puppet
|-
| Fuel / Ironic || || ||
|-
| || Evgeny L || evgenyl || Fuel liaison for Ironic
|-
| Bareon / Ironic || || ||
|-
| || Evgeny L || evgenyl || Bareon liaison for Ironic
|-
| Magnum / Kuryr || || ||
|-
| || Ton Ngo || tango || Magnum liaison for Kuryr
|-
| || Fawad Khaliq || fawadkhaliq || Kuryr liaison for Magnum
|-
| TripleO / Ironic || || ||
|-
| || Dmitry Tantsur || dtantsur || Ironic liaison for TripleO
|-
| Nova / Watcher || || ||
|-
| || Ed Leafe || edleafe || Nova liaison for Watcher
|}

=== Etherpads ===

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

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

== Cross-Project Spec Liaisons ==

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

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

|}

Forum/Boston2017

2017-03-14T22:36:07Z

Szaher: /* Project Teams */

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

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

==Project Teams==

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

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

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

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

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

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

==UC Working Groups ==

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

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

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

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

==Other Working Groups==

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

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

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

Freezer

2017-02-24T21:50:54Z

Szaher: /* Core Team */

[[File:SmallTransparent.png|thumbnail|none|]]

Freezer is a distributed backup restore and disaster recovery as a service platform. It is designed to be multi OS (Linux, Windows, OSX, *BSD), focused on providing efficiency and flexibility for block based backups, file based incremental backups, point-in-time actions, jobs synchronization (i.e. backup synchronization over multiple nodes) and many other features. It is aimed at being useful for all environments, including large ephemeral Clouds. Documentation and Code can be found at the following locations:

* [http://git.openstack.org/cgit/openstack/freezer/ freezer-agent and scheduler Source Code]
* [http://git.openstack.org/cgit/openstack/freezer-api/ freezer-api API Source Code]
* [http://git.openstack.org/cgit/openstack/freezer-dr/ Freezer Disaster Recovery]
* [http://git.openstack.org/cgit/openstack/freezer-web-ui/ Freezer Horizon Web UI Source Code]
* [https://launchpad.net/freezer Launchpad]

== Core Team ==

* Deklan Dieterly (ddieterly)
* Fabrizio Vanni (vannif)
* Fausto Marzi (daemontool)
* Guillermo Garcia (m3m0)
* Jonas Pfannschmidt (jonaspf)
* Pierre-Arthur Mathieu (slashme)
* '''[PTL]''' Saad Zaher (szaher)
* Yang Yapeng (yangyapeng)

== Resources ==

{| border="1" cellpadding="2" cellspacing="0"
| Meetings
| https://etherpad.openstack.org/p/freezer_meetings Chairman: m3m0 or ddieterly
|-
| IRC
| #openstack-freezer on Freenode
|-
| Mailing List
| [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev OpenStack dev] list, prefix with [freezer]
|-
| Milestones
| https://launchpad.net/freezer/+milestones
|-
| Integration
| [[Freezer/Integration]] - Coming soon
|-
| Bug tracker
| https://bugs.launchpad.net/freezer
|-
| Blueprints
| https://blueprints.launchpad.net/freezer
|}

== Getting Started ==

* [https://wiki.openstack.org/wiki/Freezer-getting-started Getting Started]
* [https://wiki.openstack.org/wiki/Freezer-installation Installation]
* [https://wiki.openstack.org/wiki/FreezerDevStack Running Freezer via DevStack - Coming soon]

== Documentation ==

* [https://wiki.openstack.org/wiki/Freezer-getting-started-with-freezer Getting Started with Freezer]
* [https://wiki.openstack.org/wiki/Freezer-concepts Freezer Concepts]
* [https://wiki.openstack.org/wiki/Freezer-installation Installing Freezer]
* [https://wiki.openstack.org/wiki/Freezer-docs Using Freezer]
* [https://wiki.openstack.org/wiki/Freezer-backup-restore Backup and Restore your data]
* [https://wiki.openstack.org/wiki/Freezer-admin Administrator tasks for freezer]
* [https://wiki.openstack.org/wiki/Freezer-api Freezer API]
* [https://wiki.openstack.org/wiki/Freezer-web-ui Freezer Web UI]
* [https://wiki.openstack.org/wiki/Python-freezerclient Python Freezer Client]
* [https://wiki.openstack.org/wiki/freezer-troubleshooting Freezer Troubleshooting]

== Contributing ==

A good place to start is by reading at the [[How_To_Contribute]] to OpenStack page. For information on contributing to Freezer specifically see the [http://docs.openstack.org/developer/freezer/contribute/getting_involved.html Getting Involved] page in the developer documentation.

== Discussions / Etherpads ==
* [https://etherpad.openstack.org/p/freezer_meetings Weekly meetings notes]

'''Every Thursday there's a weekly meeting starting from 3:00 p.m. UTC on IRC room: openstack-meeting-alt'''

== Automation Details ==

* [https://wiki.openstack.org/wiki/FreezerAutomation Freezer Automation (Chef) - Coming soon]

== Technical Details ==

* [https://github.com/openstack/freezer/blob/master/README.rst Architecture]
* [https://wiki.openstack.org/wiki/FreezerFeatures Detailed features list]

== Presentations ==

* https://www.openstack.org/summit/vancouver-2015/summit-videos/presentation/freezer-the-openstack-back-up-as-a-service-platform

== Roadmap ==
* [https://wiki.openstack.org/wiki/FreezerRoadmap Freezer Roadmap]
[[category: Backup]]

== miscellaneous ==
* [https://wiki.openstack.org/wiki/FreezerLogo Logo]

Freezer

2016-05-12T13:48:56Z

Szaher:

[[File:SmallTransparent.png|thumbnail|none|]]

Freezer is a distributed backup restore and disaster recovery as a service platform. It is designed to be multi OS (Linux, Windows, OSX, *BSD), focused on providing efficiency and flexibility for block based backups, file based incremental backups, point-in-time actions, jobs synchronization (i.e. backup synchronization over multiple nodes) and many other features. It is aimed at being useful for all environments, including large ephemeral Clouds. Documentation and Code can be found at the following locations:

* [http://git.openstack.org/cgit/openstack/freezer/ freezer-agent and scheduler Source Code]
* [http://git.openstack.org/cgit/openstack/freezer-api/ freezer-api API Source Code]
* [http://git.openstack.org/cgit/openstack/freezer-dr/ Freezer Disaster Recovery]
* [http://git.openstack.org/cgit/openstack/freezer-web-ui/ Freezer Horizon Web UI Source Code]
* [https://launchpad.net/freezer Launchpad]

== Core Team ==

* Fausto Marzi (daemontool)
* Fabrizio Fresco (felipe)
* Guillermo Garcia (m3m0)
* '''[PTL]''' Pierre-Arthur Mathieu (slashme)
* Eldar Nugaev (reldan)
* Fabrizio Vanni (vannif)
* Jonas Pfannschmidt (jonaspf)
* Saad Zaher (szaher)

== Resources ==

{| border="1" cellpadding="2" cellspacing="0"
| Meetings
| https://etherpad.openstack.org/p/freezer_meetings Chairman: m3m0 or ddieterly
|-
| IRC
| #openstack-freezer on Freenode
|-
| Mailing List
| [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev OpenStack dev] list, prefix with [freezer]
|-
| Milestones
| https://launchpad.net/freezer/+milestones
|-
| Integration
| [[Freezer/Integration]] - Coming soon
|-
| Bug tracker
| https://bugs.launchpad.net/freezer
|-
| Blueprints
| https://blueprints.launchpad.net/freezer
|}

== Getting Started ==

* [https://github.com/openstack/freezer/blob/master/README.rst Getting Started]
* [https://wiki.openstack.org/wiki/FreezerDevStack Running Freezer via DevStack - Coming soon]

== Contributing ==

A good place to start is by reading at the [[How_To_Contribute]] to OpenStack page. For information on contributing to Freezer specifically see the [http://docs.openstack.org/developer/freezer/contribute/getting_involved.html Getting Involved] page in the developer documentation.

== Discussions / Etherpads ==
* [https://etherpad.openstack.org/p/freezer_meetings Weekly meetings notes]
* [[Freezer/Liberty]]
* [[Freezer/Kilo]]

'''Every Thursday there's a weekly meeting starting from 3:00 p.m. UTC on IRC room: openstack-meeting-alt'''

== Automation Details ==

* [https://wiki.openstack.org/wiki/FreezerAutomation Freezer Automation (Chef) - Coming soon]

== Technical Details ==

* [https://github.com/openstack/freezer/blob/master/README.rst Architecture]
* [https://wiki.openstack.org/wiki/FreezerFeatures Detailed features list]

== Presentations ==

* https://www.openstack.org/summit/vancouver-2015/summit-videos/presentation/freezer-the-openstack-back-up-as-a-service-platform

== Roadmap ==
* [https://wiki.openstack.org/wiki/FreezerRoadmap Freezer Roadmap]
[[category: Backup]]

== miscellaneous ==
* [https://wiki.openstack.org/wiki/FreezerLogo Logo]

Freezer

2016-04-22T13:36:48Z

Szaher:

[[File:SmallTransparent.png|thumbnail|none|]]

Freezer is a distributed backup restore and disaster recovery as a service platform. It is designed to be multi OS (Linux, Windows, OSX, *BSD), focused on providing efficiency and flexibility for block based backups, file based incremental backups, point-in-time actions, jobs synchronization (i.e. backup synchronization over multiple nodes) and many other features. It is aimed at being useful for all environments, including large ephemeral Clouds. Documentation and Code can be found at the following locations:

* [http://git.openstack.org/cgit/openstack/freezer/ freezer-agent and scheduler Source Code]
* [http://git.openstack.org/cgit/openstack/freezer-api/ freezer-api API Source Code]
* [http://git.openstack.org/cgit/openstack/freezer-web-ui/ Freezer Horizon Web UI Source Code]
* [https://launchpad.net/freezer Launchpad]

== Core Team ==

* Fausto Marzi (daemontool)
* Fabrizio Fresco (felipe)
* Guillermo Garcia (m3m0)
* '''[PTL]''' Pierre-Arthur Mathieu (slashme)
* Eldar Nugaev (reldan)
* Fabrizio Vanni (vannif)
* Jonas Pfannschmidt (jonaspf)
* Saad Zaher (szaher)

== Resources ==

{| border="1" cellpadding="2" cellspacing="0"
| Meetings
| https://etherpad.openstack.org/p/freezer_meetings Chairman: m3m0 or ddieterly
|-
| IRC
| #openstack-freezer on Freenode
|-
| Mailing List
| [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev OpenStack dev] list, prefix with [freezer]
|-
| Milestones
| https://launchpad.net/freezer/+milestones
|-
| Integration
| [[Freezer/Integration]] - Coming soon
|-
| Bug tracker
| https://bugs.launchpad.net/freezer
|-
| Blueprints
| https://blueprints.launchpad.net/freezer
|}

== Getting Started ==

* [https://github.com/openstack/freezer/blob/master/README.rst Getting Started]
* [https://wiki.openstack.org/wiki/FreezerDevStack Running Freezer via DevStack - Coming soon]

== Contributing ==

A good place to start is by reading at the [[How_To_Contribute]] to OpenStack page. For information on contributing to Freezer specifically see the [http://docs.openstack.org/developer/freezer/contribute/getting_involved.html Getting Involved] page in the developer documentation.

== Discussions / Etherpads ==
* [https://etherpad.openstack.org/p/freezer_meetings Weekly meetings notes]
* [[Freezer/Liberty]]
* [[Freezer/Kilo]]

'''Every Thursday there's a weekly meeting starting from 3:00 p.m. UTC on IRC room: openstack-meeting-alt'''

== Automation Details ==

* [https://wiki.openstack.org/wiki/FreezerAutomation Freezer Automation (Chef) - Coming soon]

== Technical Details ==

* [https://github.com/openstack/freezer/blob/master/README.rst Architecture]
* [https://wiki.openstack.org/wiki/FreezerFeatures Detailed features list]

== Presentations ==

* https://www.openstack.org/summit/vancouver-2015/summit-videos/presentation/freezer-the-openstack-back-up-as-a-service-platform

== Roadmap ==
* [https://wiki.openstack.org/wiki/FreezerRoadmap Freezer Roadmap]
[[category: Backup]]

== miscellaneous ==
* [https://wiki.openstack.org/wiki/FreezerLogo Logo]

Freezer

2016-04-22T13:36:03Z

Szaher:

[[File:SmallTransparent.png|thumbnail|none|]]

Freezer is a distributed backup restore and disaster recovery as a service platform. It is designed to be multi OS (Linux, Windows, OSX, *BSD), focused on providing efficiency and flexibility for block based backups, file based incremental backups, point-in-time actions, jobs synchronization (i.e. backup synchronization over multiple nodes) and many other features. It is aimed at being useful for all environments, including large ephemeral Clouds. Documentation and Code can be found at the following locations:

* [http://git.openstack.org/cgit/openstack/freezer/ freezer-agent and scheduler Source Code]
* [http://git.openstack.org/cgit/openstack/freezer-api/ freezer-api API Source Code]
* [http://git.openstack.org/cgit/openstack/freezer-web-ui/ Freezer Horizon Web UI Source Code]
* [https://launchpad.net/freezer Launchpad]

== Core Team ==

* Fausto Marzi (daemontool)
* Fabrizio Fresco (felipe)
* Guillermo Garcia (m3m0)
* [PTL] Pierre-Arthur Mathieu (slashme)
* Eldar Nugaev (reldan)
* Fabrizio Vanni (vannif)
* Jonas Pfannschmidt (jonaspf)
* Saad Zaher (szaher)

== Resources ==

{| border="1" cellpadding="2" cellspacing="0"
| Meetings
| https://etherpad.openstack.org/p/freezer_meetings Chairman: m3m0 or ddieterly
|-
| IRC
| #openstack-freezer on Freenode
|-
| Mailing List
| [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev OpenStack dev] list, prefix with [freezer]
|-
| Milestones
| https://launchpad.net/freezer/+milestones
|-
| Integration
| [[Freezer/Integration]] - Coming soon
|-
| Bug tracker
| https://bugs.launchpad.net/freezer
|-
| Blueprints
| https://blueprints.launchpad.net/freezer
|}

== Getting Started ==

* [https://github.com/openstack/freezer/blob/master/README.rst Getting Started]
* [https://wiki.openstack.org/wiki/FreezerDevStack Running Freezer via DevStack - Coming soon]

== Contributing ==

A good place to start is by reading at the [[How_To_Contribute]] to OpenStack page. For information on contributing to Freezer specifically see the [http://docs.openstack.org/developer/freezer/contribute/getting_involved.html Getting Involved] page in the developer documentation.

== Discussions / Etherpads ==
* [https://etherpad.openstack.org/p/freezer_meetings Weekly meetings notes]
* [[Freezer/Liberty]]
* [[Freezer/Kilo]]

'''Every Thursday there's a weekly meeting starting from 3:00 p.m. UTC on IRC room: openstack-meeting-alt'''

== Automation Details ==

* [https://wiki.openstack.org/wiki/FreezerAutomation Freezer Automation (Chef) - Coming soon]

== Technical Details ==

* [https://github.com/openstack/freezer/blob/master/README.rst Architecture]
* [https://wiki.openstack.org/wiki/FreezerFeatures Detailed features list]

== Presentations ==

* https://www.openstack.org/summit/vancouver-2015/summit-videos/presentation/freezer-the-openstack-back-up-as-a-service-platform

== Roadmap ==
* [https://wiki.openstack.org/wiki/FreezerRoadmap Freezer Roadmap]
[[category: Backup]]

== miscellaneous ==
* [https://wiki.openstack.org/wiki/FreezerLogo Logo]

Freezer

2016-04-22T13:35:34Z

Szaher:

[[File:SmallTransparent.png|thumbnail|none|]]

Freezer is a distributed backup restore and disaster recovery as a service platform. It is designed to be multi OS (Linux, Windows, OSX, *BSD), focused on providing efficiency and flexibility for block based backups, file based incremental backups, point-in-time actions, jobs synchronization (i.e. backup synchronization over multiple nodes) and many other features. It is aimed at being useful for all environments, including large ephemeral Clouds. Documentation and Code can be found at the following locations:

* [http://git.openstack.org/cgit/openstack/freezer/ freezer-agent and scheduler Source Code]
* [http://git.openstack.org/cgit/openstack/freezer-api/ freezer-api API Source Code]
* [http://git.openstack.org/cgit/openstack/freezer-web-ui/ Freezer Horizon Web UI Source Code]
* [https://launchpad.net/freezer Launchpad]

== Core Team ==

* [PTL] Fausto Marzi (daemontool)
* Fabrizio Fresco (felipe)
* Guillermo Garcia (m3m0)
* Pierre-Arthur Mathieu (slashme)
* Eldar Nugaev (reldan)
* Fabrizio Vanni (vannif)
* Jonas Pfannschmidt (jonaspf)
* Saad Zaher (szaher)

== Resources ==

{| border="1" cellpadding="2" cellspacing="0"
| Meetings
| https://etherpad.openstack.org/p/freezer_meetings Chairman: m3m0 or ddieterly
|-
| IRC
| #openstack-freezer on Freenode
|-
| Mailing List
| [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev OpenStack dev] list, prefix with [freezer]
|-
| Milestones
| https://launchpad.net/freezer/+milestones
|-
| Integration
| [[Freezer/Integration]] - Coming soon
|-
| Bug tracker
| https://bugs.launchpad.net/freezer
|-
| Blueprints
| https://blueprints.launchpad.net/freezer
|}

== Getting Started ==

* [https://github.com/openstack/freezer/blob/master/README.rst Getting Started]
* [https://wiki.openstack.org/wiki/FreezerDevStack Running Freezer via DevStack - Coming soon]

== Contributing ==

A good place to start is by reading at the [[How_To_Contribute]] to OpenStack page. For information on contributing to Freezer specifically see the [http://docs.openstack.org/developer/freezer/contribute/getting_involved.html Getting Involved] page in the developer documentation.

== Discussions / Etherpads ==
* [https://etherpad.openstack.org/p/freezer_meetings Weekly meetings notes]
* [[Freezer/Liberty]]
* [[Freezer/Kilo]]

'''Every Thursday there's a weekly meeting starting from 3:00 p.m. UTC on IRC room: openstack-meeting-alt'''

== Automation Details ==

* [https://wiki.openstack.org/wiki/FreezerAutomation Freezer Automation (Chef) - Coming soon]

== Technical Details ==

* [https://github.com/openstack/freezer/blob/master/README.rst Architecture]
* [https://wiki.openstack.org/wiki/FreezerFeatures Detailed features list]

== Presentations ==

* https://www.openstack.org/summit/vancouver-2015/summit-videos/presentation/freezer-the-openstack-back-up-as-a-service-platform

== Roadmap ==
* [https://wiki.openstack.org/wiki/FreezerRoadmap Freezer Roadmap]
[[category: Backup]]

== miscellaneous ==
* [https://wiki.openstack.org/wiki/FreezerLogo Logo]