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.

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.

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.

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:

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

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.

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

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.

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.

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.

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.

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