Jump to: navigation, search

Difference between revisions of "CrossProjectLiaisons"

(Communication channels)
Line 226: Line 226:
 
== API Guidelines ==
 
== API Guidelines ==
  
The [https://wiki.openstack.org/wiki/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 [[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 liaison should be a core reviewer for the project, but does not need to be the PTL.
 
* 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.
 
* By default, the liaison will be the PTL.
* The liaison is the first line of contact for the [https://wiki.openstack.org/wiki/API_Working_Group API Working Group] team members
+
* The liaison is the first line of contact for the API Working Group team members
 
* The liaison may further delegate work to other subject matter experts
 
* The liaison may further delegate work to other subject matter experts
 +
* The liaison should be aware of and engaged in the API Working Group [[API_Working_Group#Communication|Communication channels]]
  
 
{| class="wikitable"
 
{| class="wikitable"

Revision as of 15:48, 14 November 2014

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 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 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
Ceilometer Julien Danjou jd__
Cinder Jay Bryant jungleboyj
Designate
Glance Zhi Yan Liu zhiyan
Heat Steve Hardy shardy
Horizon Akihiro Motoki amotoki
Ironic Ghe Rivero GheRivero
Keystone Brant Knudson bknudson
Manila
Neutron Ihar Hrachyshka (not a core!) ihrachyshka
Nova Joe Gordon jogo
Octavia Doug Wiegley dougwig
Sahara Sergey Reshetnyak sreshetnyak
Swift
TripleO Ben Nemec bnemec
Trove
Zaqar Flavio Percoco flaper87

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
Nova Matt Riedemann mriedem
Cinder
Swift
Neutron Salvatore Orlando salv-orlando
Keystone David Stanek dstanek
Horizon
Glance
Ceilometer Dina Belova DinaBelova
Heat Steve Baker stevebaker
Oslo Davanum Srinivas dims
Trove
Sahara Luigi Toscano and Sergey Lukjanov tosky and SergeyLukjanov
Ironic
Zaqar
Barbican
Manila Valeriy Ponomaryov vponomaryov

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:

1st Wednesday, 03:00:00 UTC #openstack-meeting (APAC)

2nd Wednesday, 14:00:00 UTC #openstack-meeting (US)

3rd Wednesday, 03:00:00 UTC #openstack-meeting (APAC)

4th Wednesday, 14:00:00 UTC #openstack-meeting (US)

Project Liaison IRC Handle
Nova Joe Gordon or Michael Still Jog0 or mikal
Cinder Mike Perez thingee
Swift Atul Jha or Chuck Thier koolhead or creight
Neutron Edgar Magana emagana
Keystone Adam Young ayoung
Horizon Julie Pichon jpich
Glance Brian Rosmaita rosmaita
Ceilometer Ildiko Vancsa ildikov
Heat Randall Burt?
Oslo
Trove Laurel Michaels laurelm
Sahara Chad Roberts crobertsrh
Ironic
Zaqar
Barbican Constanze Kratel constanze
Manila

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 election its PTL.
  • The liaison may further delegate work to other subject matter experts
Project Liaison IRC Handle
Ceilometer
Cinder
Glance
Heat
Horizon
Ironic
Keystone
Neutron
Nova
Sahara
Swift
Trove

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.
  • 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)
Project Liaison IRC Handle
Ceilometer
Cinder
Glance Stuart McLaren or Nikhil Komawar mclaren or nikhil_k
Heat
Horizon Lin Hua Cheng lhcheng
Ironic
Keystone Dolph Mathews dolphm
Neutron Salvatore Orlando salv-orlando
Nova Andrew Laski alaski
Sahara Michael McCune or Sergey Lukjanov elmiko or SergeyLukjanov
Swift
Trove

API Guidelines

The 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 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 API Working Group team members
  • The liaison may further delegate work to other subject matter experts
  • The liaison should be aware of and engaged in the API Working Group Communication channels
Project Liaison IRC Handle
Ceilometer
Cinder Mike Perez thingee
Glance Stuart McLaren or Nikhil Komawar mclaren or nikhil_k
Heat
Horizon
Ironic Lucas Alvares Gomes lucasagomes
Keystone Dolph Mathews dolphm
Neutron Salvatore Orlando salvorlando
Nova Christopher Yeoh cyeoh
Sahara Michael McCune and Sergey Lukjanov elmiko and SergeyLukjanov
Swift John Dickenson notmyname
Trove