CrossProjectLiaisons
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.
Contents
Oslo
There are far more projects consuming code from Oslo libraries than we have Oslo contributors. That means it is not possible for the Oslo team to keep track of how every project is using Oslo code. We are asking for one person from each project to serve as a liaison between the project and Oslo, to let us know when they are having issues with a library, and to assist with work like migrating off deprecated features.
- The liaison should be active in the project and familiar with the project-specific requirements for having patches accepted, but does not need to be a core reviewer or the PTL.
- The liaison should be prepared to assist with writing and reviewing patches in their project as libraries are adopted, and with discussions of API changes to the libraries to make them easier to use within the project.
- Liaisons should pay attention to [Oslo] tagged messages on the openstack-dev mailing list.
- It is also useful for liaisons to be able to attend the Oslo team meeting (Meetings/Oslo) to participate in discussions and raise issues for real-time discussion.
| Project | Liaison | IRC Handle |
|---|---|---|
| Barbican | Douglas Mendizábal | dmendiza[m] |
| Ceilometer | Julien Danjou | jd__ |
| Cinder | Jay Bryant | jungleboyj |
| Cloudkitty | Christophe Sauthier | huats |
| Congress | Eric Kao | ekcs |
| Cue | Min Pae | sputnik13 |
| Cyborg | Shaohe Feng | shaohe_feng |
| Designate | Michael Johnson | johnsom |
| Freezer | Saad Zaher | szaher |
| Glance | Abhishek Kekane | akekane |
| Heat | Thomas Herve | therve |
| Horizon | Ivan Kolodyazhny | e0ne |
| I18n | Frank Kloeker | eumel8 |
| Ironic | ||
| Keystone | Douglas Mendizábal | dmendiza[m] |
| Manila | Thomas Bechtold | toabctl |
| Mistral | Dougal Matthews | d0ugal |
| Murano | Rong Zhu | zhurong |
| Neutron | Bernard Cafarelli | bcafarel |
| Nova | Stephen Finucane | stephenfin |
| Octavia | Michael Johnson | johnsom |
| Placement | Chris Dent | cdent |
| Qinling | Lingxian Kong | kong |
| Rally | Andrey Kurilin | andreykurilin |
| Sahara | Telles Nobrega, Shu Yingya | tellesnobrega, shuyingya |
| Senlin | Yanyan Hu | Yanyanhu |
| Swift | ||
| Tricircle | Chaoyi Huang | joehuang |
| TripleO | Ben Nemec | bnemec |
| Trove | Lingxian Kong | lxkong |
| Zaqar | Flavio Percoco | flaper87 |
| Zun | Hongbin Lu | hongbin |
Release management
The Release Management Liaison is responsible for communication with the Release Management team. Its tasks are described in the project team guide: http://docs.openstack.org/project-team-guide/release-management.html . That task has been traditionally filled by the PTL, but they may now delegate this task if they wish.
- By default, the liaison will be the PTL.
- The liaison may further delegate work to other subject matter experts
The liaisons list is now being maintained in the release's repo here. If you want to add/update liaison info, please submit a patch to the releases repository.
QA
There are now more projects that are being tested by Tempest, and Grenade or a part deployable by Devstack than we have QA contributors. That means we are going to need your help to keep on top of everything. We are asking for one person from each project to serve as a liaison between the project and QA, and to assist with integrating changes as we move forward.
The liaison should be a core reviewer for the project, but does not need to be the PTL. The liaison should be prepared to assist with writing and reviewing patches that interact with their project, and with discussions of changes to the QA projects to make them easier to use within the project.
| Project | Liaison | IRC Handle |
|---|---|---|
| Barbican | Douglas Mendizábal | dmendiza[m] |
| Ceilometer | Chris Dent | cdent |
| Cinder | Scott DAngelo and Ivan Kolodyazhny | scottda and e0ne |
| Congress | Eric Kao | ekcs |
| Cyborg | Chenke | chenker |
| Freezer | Guillermo Garcia | m3mo |
| Glance | Abhishek Kekane | abhishekk |
| Heat | Steve Baker | stevebaker |
| Horizon | Ivan Kolodyazhny | e0ne |
| Ironic | ||
| Keystone | Douglas Mendizábal | dmendiza[m] |
| Manila | Dustin Schoenbrun | dustins |
| Murano | Rong Zhu | zhurong |
| Neutron | Slawek Kaplonski | slaweq |
| Nova | Ghanshyam Mann | gmann |
| Oslo | Davanum Srinivas | dims |
| Qinling | Lingxian Kong | kong |
| Sahara | Luigi Toscano | tosky |
| Senlin | Haiwei Xu | haiwei-xu |
| Swift | Thiago da Silva | tdasilva |
| Trove | Lingxian Kong | lxkong |
| Zaqar | Fei Long Wang | flwang |
| Zun | Hongbin Lu | hongbin |
Documentation
The OpenStack Documentation is centralized on docs.openstack.org but often there's a need for specialty information when reviewing patches or triaging doc bugs. A doc liaison should be available to triage doc bugs when the docs team members don't know enough to triage accurately, and be added to doc reviews that affect your project. You'd be notified through email when you're added either to a doc bug or a doc review. We also would appreciate attendance at the weekly doc team meeting, We meet weekly in #openstack-meeting every Wednesday at alternating times for different timezones:
| Project | Liaison | IRC Handle |
|---|---|---|
| Barbican | Douglas Mendizábal | dmendiza[m] |
| Ceilometer | Ildiko Vancsa | ildikov |
| Cinder | Jay Bryant | jungleboyj |
| Congress | Aimee Ukasick | aimeeu |
| Cyborg | Yumeng Bao | Yumeng |
| Designate | Omer Schwartz | oschwart |
| Freezer | Guillermo Garcia | m3mo |
| Heat | Rabi Mishra | ramishra |
| Horizon | Ivan Kolodyazhny | e0ne |
| I18n | Frank Kloeker | eumel8 |
| Ironic | Julia Kreger | TheJulia |
| Keystone | Douglas Mendizábal | dmendiza[m] |
| Kolla | Michal Nasiadka | nasiadka |
| Magnum | Dale Smith | dalees |
| Manila | Tom Barron | tbarron |
| Mistral | Dougal Matthews | d0ugal |
| Murano | Rong Zhu | zhurong |
| Neutron | Akihiro Motoki | amotoki |
| Nova | Stephen Finucane | stephenfin |
| Octavia | Michael Johnson | johnsom |
| OpenStack-Ansible | Amy Marrich | spotz |
| Ops | Robert Starmer | |
| Oslo | Stephen Finucane | stephenfin |
| Puppet OpenStack | Emilien Macchi | EmilienM |
| Qinling | Lingxian Kong | kong |
| Rally | Boris Pavlovic | boris-42 |
| Sahara | Telles Nobrega and Luigi Toscano | tellesnobrega, tosky |
| Senlin | Cindia Blue | lixinhui |
| Swift | John Dickinson | notmyname |
| Tripleo | Steven Hardy | shardy |
| Trove | Lingxian Kong | lxkong |
| Watcher | Prudhvi Rao Shedimbi | pshedimb |
| Zaqar | Fei Long Wang | flwang |
| Zun | Hongbin Lu | hongbin |
Stable Branch
The Stable Branch Liaison is responsible for making sure backports are proposed for critical issues in their project, and make sure proposed backports are reviewed. They are also the contact point for stable branch release managers around point release times.
- By default, the liaison will be the PTL.
- The Stable Branch Liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in its PTL election.
- The liaison may further delegate work to other subject matter experts
| Project | Liaison | IRC Handle |
|---|---|---|
| Barbican | Douglas Mendizábal | dmendiza[m] |
| Ceilometer | Eoghan Glynn | eglynn |
| Cinder | Jay Bryant | jungleboyj |
| Congress | Masahito Muroi | masahito |
| Cyborg | Yumeng Bao | Yumeng |
| Freezer | Saad Zaher | szaher |
| Glance | ||
| Heat | Zane Bitter | zaneb |
| Horizon | Akihiro Motoki | amotoki |
| Ironic | Dmitry Tantsur | dtantsur |
| Keystone | Douglas Mendizábal | dmendiza[m] |
| Manila | Goutham Pacha Ravi | gouthamr |
| Mistral | Dougal Matthews | d0ugal |
| Murano | Rong Zhu | zhurong |
| Neutron | Brian Haley | haleyb |
| Nova | Lee Yarwood | lyarwood |
| Octavia | Michael Johnson | johnsom |
| Placement | Matt Riedemann | mriedem |
| Qinling | Lingxian Kong | kong |
| Sahara | Telles Nobrega | tellesnobrega |
| Senlin | Qiming Teng | Qiming |
| Swift | Matthew Oliver | mattoliverau |
| Trove | Lingxian Kong | lxkong |
| Watcher | David Tardivel | dtardivel |
| Zaqar | Fei Long Wang | flwang |
| Zun | Hongbin Lu | hongbin |
Vulnerability management
The Vulnerability Management Team needs domain specialists to help assessing the impact of reported issues, coordinate the development of patches, review proposed patches and propose backports. The liaison should be familiar with the Vulnerability Management process and embargo rules, and have a good grasp of security issues in software design.
- The liaison should be a core reviewer for the project, but does not need to be the PTL.
- By default, the liaison will be the PTL unless explicitly listed.
- The liaison is the first line of contact for the Vulnerability Management team members
- The liaison is considered a contributor to the Release Cycle Management Program and therefore is allowed to vote in election its PTL
- The liaison may further delegate work to other subject matter experts
- The liaison maintains the members of the project's core security review team in Launchpad or StoryBoard (reviewers who will be given access to embargoed vulnerabilities by the VMT)
- If the project has multiple core security review teams for different deliverables they should be listed together in the appropriate column.
| Project | Liaison | IRC Handle | Security Team |
|---|---|---|---|
| Barbican | Grzegorz Grasza | xek | all deliverables: barbican-coresec (LP) |
| Cinder | Brian Rosmaita | rosmaita | all deliverables: cinder-coresec (LP) |
| Glance | Brian Rosmaita | rosmaita | all deliverables: glance-coresec (LP) |
| Heat | Steve Hardy | shardy | all deliverables: openstack-heat-security (SB) |
| Horizon | Akihiro Motoki | amotoki | all deliverables: horizon-coresec (LP) |
| Keystone | Grzegorz Grasza | xek | all deliverables: keystone-coresec (LP) |
| Neutron | Miguel Lavalle | mlavalle | all deliverables: neutron-coresec (LP) |
| Nova | Michael Still | mikal | all deliverables: nova-coresec (LP) |
| Oslo | DPL | all deliverables: oslo-coresec (LP) | |
| Sahara | Telles Nobrega | tellesnobrega | all deliverables: openstack-sahara-security (SB) |
| Swift | all deliverables: swift-coresec (LP) | ||
| Trove | Lingxian Kong | lxkong | all deliverables: openstack-trove-security (SB) |
| OpenStack Technical Committee | Goutham Pacha Ravi | gouthamr | TC Liaison for escalations |
| OpenStack Technical Committee | Sylvain Bauzas | bauzas | TC Liaison for escalations |
| QA | Ghanshyam Maan | gmaan | QA related work/changes |
API-SIG
The API-SIG seeks API subject matter experts for each project to communicate plans for API updates, review API guidelines with their project's view in mind, and review the API-SIG guidelines as they are drafted. The liaison should be familiar with the project's REST API design and future planning for changes to it.
The members of the API-SIG Cross-Project Liaisons are maintained in our repo. If you want to read the entire list of CPLs or add/remove yourself from the list, you'll need to update the 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 Log Working Group seeks experts for each project to assist with making the logging in projects match the new Logging Guidelines
| Project | Liaison | IRC Handle |
|---|---|---|
| Ironic | ||
| Oslo | Doug Hellmann | dhellmann |
| Nova | John Garbutt | johnthetubaguy |
| Murano | Rong Zhu | zhurong |
| Sahara | Telles Nobrega | tellesnobrega |
Infra
These are the project specific groups of people that Infra will look to ACK changes to that project's test configuration. Changes to project-config and devstack-gate should be +1'd by these groups when they are related to their project. Note that in an emergency this may not always be possible and Infra will ask for forgiveness but generally we should look for these +1s.
| 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 | Brian Rosmaita | rosmaita |
| I18n | Frank Kloeker | eumel8 |
| Ironic | Dmitry Tantsur | dtantsur |
| Kolla | Any Kolla Core Reviewer may ack an infra change on behalf of the PTL | mnasiadka, bbezak, frickler |
| Neutron | Slawek Kaplonski, YAMAMOTO Takashi | slaweq, yamamoto |
| Documentation | Andreas Jaeger | AJaeger |
| Trove | Lingxian Kong | lxkong |
| Murano | Rong Zhu | zhurong |
| Sahara | Telles Nobrega and Luigi Toscano | tellesnobrega, tosky |
| Fuel | Aleksandra Fedorova, Igor Belikov | bookwar, igorbelikov |
| OpenStack-Ansible | Jean-Philippe Evrard, Jesse Pretorius | evrardjp, odyssey4me |
| Puppet OpenStack | Emilien Macchi, Alex Schultz | EmilienM, mwhahaha |
| TripleO | Emilien Macchi | EmilienM |
| Airship | Matt McEuen | mattmceuen |
I18n
I18n team is responsible for making OpenStack ubiquitously accessible to people of all language backgrounds. The team have translators from all over the world to translate OpenStack into different languages.
If you want to communicate with translators in I18n team, send email to [email protected].
- 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.
| Project | Liaison | IRC Handle |
|---|---|---|
| Barbican | ||
| Cinder | Brian Rosmaita | rosmaita |
| Designate | Graham Hayes | mugsie |
| Glance | Abhishek Kekane | akekane |
| Heat | ||
| Horizon | Akihiro Motoki | amotoki |
| Ironic | ||
| Keystone | ||
| Magnum | Shu Muto | shu-mutou |
| Manila | ||
| Monasca | ||
| Murano | ||
| Neutron | Akihiro Motoki | amotoki |
| Nova | ||
| Oslo | ||
| Sahara | Luigi Toscano, Jeremy Freudberg | tosky, jeremyfreudberg |
| Senlin | ||
| Swift | ||
| Tacker | ||
| Telemetry | ||
| TripleO | ||
| Trove | ||
| Watcher | Yumeng Bao | Yumeng |
| Zaqar |
First Contact SIG
First Contact SIG aims to provide a place for new contributors to come for information and advice. This group will also analyze and document successful contribution models while seeking out and providing information to new members of the community. First Contact SIG project liaisons are important that they are connected with someone who can get them up to speed on a project.
By default, the liaison will be the PTL. More than one liaison covering different TZ is recommended.
| Name | IRC | Timezone | Project | |
|---|---|---|---|---|
| Masahito Muroi | masahito | [email protected] | Blazar | |
| Samuel Cassiba | scas | [email protected] | UTC-7 | Chef OpenStack |
| Jay Bryant | jungleboyj | [email protected] | UTC-6 | Cinder |
| Ivan Kolodyazhny | e0ne | [email protected] | UTC+3 | Cinder |
| Luka Peschke | peschk_l | [email protected] | CEST (UTC+2) | Cloudkitty |
| Eric Kao | ekcs | [email protected] | UTC-8 | Congress |
| Ivan Kolodyazhny | e0ne | [email protected] | UTC+3 | Horizon |
| Howard Huang | zhipeng | [email protected] | UTC+8 | Cyborg |
| Graham Hayes | mugsie | [email protected] | UTC +1 | Designate |
| Petr Kovar | pkovar | [email protected] | UTC +1 | Documentation |
| Andrey Pavlov | andrey-mp | [email protected] | ec2-API | |
| Saad Zaher | szaher | [email protected] | Freezer | |
| Glance | ||||
| Rico Lin | ricolin | [email protected] | UTC+8 | Heat |
| Frank Kloeker | eumel8 | [email protected] | UTC+1 | I18n |
| Clark Boylan | clarkb | [email protected] | UTC+8 | Infrastructure |
| Julia Kreger | TheJulia | [email protected] | UTC+8 | Ironic |
| Ying Chen | chenying | [email protected] | Karbor | |
| Mark Goddard | mgoddard | [email protected] | UTC | Kayobe |
| Kristi Nikolla | knikolla | [email protected] | UTC-4 | Keystone |
| Sam Yaple | SamYaple | [email protected] | LOCI | |
| Spyros Trigazis | strigazi | [email protected] | Magnum | |
| Sampath Priyankara | samP | [email protected] | Masakari | |
| Stefano Canepa | sc | [email protected] | UTC | Monasca |
| Rong Zhu | zhurong | [email protected] | UTC+8 | Murano |
| Miguel Lavalle | mlavalle | [email protected] | UTC-6 | Neutron |
| Slawek Kaplonski | slaweq | [email protected] | UTC+1 | Neutron |
| Eric Fried | efried | [email protected] | UTC-6 | Nova |
| Alex Xu | alex_xu | [email protected] | UTC+8 | Nova |
| Michael Johnson | johnsom | [email protected] | UTC-8 | Octavia |
| James Page | jamespage | [email protected] | OpenStack Charms | |
| Jean-Philippe Evrard | evrardjp | [email protected] | UTC+2 | OpenStack-Ansible |
| Matt McEuen | mattmceuen | [email protected] | UTC-6 | OpenStack-Helm |
| Chason Chan (chenxing) | chason | [email protected] | UTC+8 | OpenStack-Manuals |
| Dean Troyer | dtroyer | [email protected] | OpenStackClient | |
| Ben Nemec | bnemec | [email protected] | UTC-6 | Oslo |
| Javier Peña | jpena | [email protected] | Packaging-rpm | |
| Ed Leafe | edleafe | [email protected] | UTC-6 | Placement |
| Matthew Edmonds | edmondsw | [email protected] | UTC-5 | PowerVMStackers |
| Ghanshyam Mann | gmann | [email protected] | UTC-6 | QA |
| Andrey Kurilin | andreykurilin | [email protected] | Rally | |
| Chris Hoge | hogepodge | [email protected] | Refstack | |
| Sean McGinnis | smcginnis | [email protected] | UTC-6 | Release Management |
| Matthew Thode | prometheanfire | [email protected] | Requirements | |
| Telles Mota Vidal Nobrega | tellesnobrega | [email protected] | Sahara | |
| Trinh Nguyen | dangtrinhnt | [email protected] | UTC+9 | Searchlight |
| Duc Truong | dtruong | [email protected] | UTC-8 | Senlin |
| Rong Zhu | zhurong | [email protected] | UTC+8 | Solum |
| Tony Breeds | tonyb | [email protected] | UTC +10 | Stable Branch Maintenance |
| Kota Tsuyuzaki | kota_ | [email protected] | Storlets | |
| Matt Oliver | mattolverau | [email protected] | UTC+10 | Swift |
| John Dickinson | notmyname | [email protected] | UTC-8 | Swift |
| Yong Sheng Gong | gongysh | [email protected] | Tacker | |
| Trinh Nguyen | dangtrinhnt | [email protected] | Telemetry | |
| Zhiyuan Cai | zhiyuan | [email protected] | Tricircle | |
| Alex Schultz | mwhahaha | [email protected] | TripleO | |
| Lingxian Kong | lxkong | [email protected] | UTC+12 | Trove |
| Alexander Chadin | alexchadin | [email protected] | UTC+3 | Watcher |
| Claudiu Belu | claudiub | [email protected] | Winstackers | |
| Wang Hao | wanghao | [email protected] | Zaqar | |
| Hongbin Lu | hongbin | [email protected] | UTC-5 | Zun |
| Victoria Martinez de la Cruz | vkmc | [email protected] | UTC-3 | Manila |
| Dougal Matthews | d0ugal | [email protected] | UTC+0 | Mistral |
| Renat Akhmerov | rakhmerov | [email protected] | UTC+7 | Mistral |
| Omer Anson | oanson | [email protected] | UTC+2 | DragonFlow |
| Surya Prakash Singh | spsurya | [email protected] | UTC+9 | Kolla |
| Daniel Mellado | dmellado | [email protected] | UTC+1 | Kuryr |
| Irena Berezovsky | irenab | [email protected] | UTC+2 | Kuryr |
| Mohammed Naser | mnaser | [email protected] | UTC-5 | Puppet OpenStack |
| Ghanshyam Mann | gmann | [email protected] | UTC-6 | Nova |
| Dharmendra Kushwaha | dkushwaha | [email protected] | UTC+5:30 | Tacker |
| Jeffrey Zhang | Jeffrey4l | [email protected] | UTC+8 | Kolla |
| Canwei Li | licanwei | [email protected] | UTC+8 | Watcher |
| Ade Lee | alee | [email protected] | UTC-4 | Barbican |
| Lingxian Kong | lxkong | [email protected] | UTC+12 | Qinling |
| Ifat Afek | ifat_afek | [email protected] | UTC+3 | Vitrage |
| Michal Nasiadka | mnasiadka | [email protected] | UTC | Kolla |
Inter-project Liaisons
In some cases, it is useful to have liaisons between projects. 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.
| Projects | Name | IRC Handle | Role |
|---|---|---|---|
| Nova / Neutron | |||
| Sean K. Mooney | sean-k-mooney | Neutron liaison for Nova | |
| Nova / Cinder | |||
| Ildiko Vancsa | ildikov | Cinder liaison for Nova | |
| Matt Riedemann | mriedem | Nova liason for Cinder | |
| Nova / Ironic | |||
| Dmitry Tantsur | dtantsur | Ironic liaison for Nova | |
| Neutron / Ironic | |||
| Sukhdev Kapur | sukhdev | Neutron liaison for Ironic | |
| Sam Betts | sambetts | Ironic liaison for Neutron | |
| Horizon / i18n | |||
| Akihiro Motoki | amotoki | Horizon liaison for i18n | |
| TBD | Heat liaison for Sahara | ||
| Fuel / Puppet | |||
| Alex Schultz | mwhahaha | Fuel liaison for Puppet | |
| Fuel / Ironic | |||
| Evgeny L | evgenyl | Fuel liaison for Ironic | |
| Bareon / Ironic | |||
| Evgeny L | evgenyl | Bareon liaison for Ironic | |
| Magnum / Kuryr | |||
| Ton Ngo | tango | Magnum liaison for Kuryr | |
| Fawad Khaliq | fawadkhaliq | Kuryr liaison for Magnum | |
| TripleO / Ironic | |||
| Dmitry Tantsur | dtantsur | Ironic liaison for TripleO | |
| Nova / Watcher | |||
| Ed Leafe | edleafe | Nova liaison for Watcher |
Etherpads
The following is a list of etherpads that are used for inter-project liaisons, and are continuously updated.
Nova - Neutron: https://etherpad.openstack.org/p/nova-neutron
