Jump to: navigation, search

CrossProjectLiaisons

Revision as of 15:51, 21 January 2016 by Travis Tripp (talk | contribs) (Cross-Project Spec Liaisons)

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.
Project Liaison IRC Handle
Barbican Douglas Mendizábal redrobot
Ceilometer Julien Danjou jd__
Cinder Jay Bryant jungleboyj
Congress Tim Hinrichs thinrichs
Cue Min Pae sputnik13
Designate
Glance Flavio Percoco flaper87
Heat Thomas Herve therve
Horizon Kirill Zaitsev kzaitsev_
Ironic Lin Tan lintan
Keystone Brant Knudson bknudson
Manila Thomas Bechtold toabctl
Murano Kirill Zaitsev kzaitsev_
Neutron Ihar Hrachyshka ihrachyshka
Nova ChangBo Guo <glongwave@gmail.com> gcb
Octavia Michael Johnson johnsom
Sahara Sergey Reshetnyak sreshetnyak
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, attending the weekly 1:1 syncs in #openstack-relmgr-office, keeping milestone plans up to date, and signing off milestone and release tags. 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 Release Management 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
Barbican Douglas Mendizábal redrobot
Ceilometer gordon chung gordc
Cinder Sean McGinnis smcginnis
Congress Tim Hinrichs thinrichs
Designate Graham Hayes mugsie
Glance Flavio Percoco flaper87
Heat Sergey Kraynev skraynev
Horizon David Lyle david-lyle
Ironic Jim Rollenhagen (Dmitry Tantsur for inspector deliverables) jroll (dtantsur)
Keystone Steve Martinelli stevemar
Manila Ben Swartzlander bswartz
Mistral Lingxian Kong lane_kong
Murano Kirill Zaitsev kzaitsev_
Neutron Kyle Mestery mestery
Nova Sylvain Bauza bauzas
Oslo Davanum Srinivas dims
Sahara Sergey Lukjanov SergeyLukjanov
Searchlight Travis Tripp TravT
Senlin Qiming Teng Qiming
Swift John Dickinson notmyname
Trove Craig Vyvial or Nikhil Manchanda cp16net or SlickNik
Zaqar

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 Steve Heyman hockeynut
Ceilometer Chris Dent cdent
Cinder
Glance Nikhil Komawar nikhil_k
Heat Steve Baker stevebaker
Horizon
Ironic John Villalovos jlvillal
Keystone David Stanek dstanek
Manila Valeriy Ponomaryov vponomaryov
Neutron Salvatore Orlando salv-orlando
Nova Matt Riedemann mriedem
Oslo Davanum Srinivas dims
Sahara Luigi Toscano and Sergey Lukjanov tosky and SergeyLukjanov
Senlin Haiwei Xu haiwei-xu
Swift
Trove Craig Vyvial and Nirav Shah cp16net and nshah
Zaqar

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 Constanze Kratel constanze
Ceilometer Ildiko Vancsa ildikov
Cinder Mike Perez thingee
Congress
Designate
Glance Brian Rosmaita rosmaita
Heat Randall Burt randallburt
Horizon Rob Cresswell robcresswell
Ironic Mitsuhiro SHIGEMATSU pshige
Keystone Lance Bragstad lbragstad
Magnum
Manila
Mistral
Murano Ekaterina Chernova katyafervent
Neutron Edgar Magana emagana
Nova Joe Gordon or Michael Still Jog0 or mikal
Oslo Doug Hellmann dhellmann
Rally
Sahara Chad Roberts crobertsrh
Senlin Cindia Blue lixinhui
Swift
Tripleo
Trove Laurel Michaels laurelm
Zaqar

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 Eoghan Glynn eglynn
Cinder Jay Bryant jungleboyj
Glance Erno Kuvaja jokke_
Heat Zane Bitter zaneb
Horizon Matthias Runge mrunge
Ironic
Keystone Dolph Mathews dolphm
Murano Kirill Zaitsev kzaitsev_
Neutron Ihar Hrachyshka ihrachys
Nova Matt Riedemann mriedem
Sahara Sergey Lukjanov SergeyLukjanov
Senlin Qiming Teng Qiming
Swift
Trove Amrith Kumar amrith

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
Barbican Douglas Mendizábal or Charles Neill redrobot / ccneill
Ceilometer Lianhao Lu or Gordon Chung llu/gordc
Cinder
Glance Stuart McLaren or Nikhil Komawar mclaren or nikhil_k
Heat Steve Hardy shardy
Horizon Lin Hua Cheng lhcheng
Ironic Jim Rollenhagen jroll
Keystone Dolph Mathews dolphm
Neutron Salvatore Orlando salv-orlando
Nova Michael Still mikal
Sahara Michael McCune or Sergey Lukjanov elmiko or SergeyLukjanov
Senlin Qiming Teng Qiming
Swift
Trove Craig Vyvial or Nikhil Manchanda cp16net or SlickNik

API Working Group

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 members of the 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 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
Glance Erno Kuvaja jokke_
Oslo Doug Hellmann dhellmann
Nova John Garbutt johnthetubaguy
Murano Nikolay Starodubtsev Nikolay_St

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
Glance Flavio Percoco, Nikhil Komawar flaper87, nikhil_k
Neutron Kyle Mestery, Armando Migliaccio, Doug Wiegley mestery, armax, dougwig
Documentation Andreas Jaeger AJaeger
Trove Nikhil Manchanda SlickNik

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 Product WG wiki.

Project Liaison IRC Handle
Ceilometer Krish Ragurham
Cinder Shamail Tahir shamail
Glance Nate Ziemann nate_zman
Horizon Carol Barrett barrett1
Keystone Sheena Gregson
Kolla Carol Barrett barrett1
Magnum Steve Gordon sgordon
Manilla Pete Chadwick
Neutron Mike Cohen, Duane DeCapite DuaneDeC7
Nova Hugh Blemings hughhalf
OSClient Megan Rossetti MeganR
Stable Release Rochelle Grober rockyg
Senlin Qiming Teng Qiming
Swift Phil Willains philipw
Tempest Arkady Kanevsky arkady_kanevsky

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 M. Collins sc68cal Neutron liaison for Nova
Brent Eagles beagles Nova liaison for Neutron
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 John Villalovos jlvillal Ironic liaison for Nova
Michael Davies mrda Ironic liaison for Nova
Neutron / Ironic
Sukhdev Kapur sukhdev Neutron liaison for Ironic
Mitsuhiro SHIGEMATSU and Jim Rollenhagen pshige and jroll 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

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

Project Liaison IRC Handle
Barbican
Ceilometer
Cinder Kendall Nelson diablo_rojo
Congress
Designate
Glance Nikhil Komawar nikhil
Heat Rico Lin ricolin
Horizon
Infrastructure Matthew Wagoner olaph
Ironic
Keystone Samuel de Medeiros Queiroz samueldmq
Manila Ben Swartzlander bswartz
Mistral
Murano
Neutron Armando Migliaccio armax
Nova Chris Dent cdent
Oslo Davanum Srinivas dims
Sahara Michael McCune or Sergey Lukjanov elmiko or SergeyLukjanov
Searchlight Travis Tripp TravT
Senlin Qiming Teng Qiming
Swift
Trove
Zaqar