Jump to: navigation, search

Meetings/CrossProjectMeeting

The whole OpenStack leadership holds a public weekly cross-project meeting in #openstack-meeting, Tuesdays at 2100 UTC.

All PTLs and CPLs are encouraged to attend, and everyone interested in the discussed topics can join.

Any cross-team issue is on-topic for this meeting. We'll discuss key release cycle events, common processes, QA and infra changes, news on the documentation front, stable branch issues, hot threads on the mailing-list... Agenda will be closed by the meeting chair one day before the meeting and announced on the openstack-dev mailing-list. If there is nothing to discuss at that point, the meeting will be cancelled.


Next meeting

  • Date: June 30th, 21:00 UTC
  • Chair: Anne Gentle (annegentle)


Proposed agenda

  • Team announcements (horizontal, vertical, diagonal)
  • Translation for non user facing messages (yamamoto)
    • a question: messages like the following should be translated or not, where the exception is merely a part of internal api and will never reach users?
      • raise ValueError("message")
    • a concern marking such messages with _LE() etc might impose unnecessary burden on translators
    • otoh, marking all of them, regardless of user-visibility, might be better for maintainability and consistency
    • cf. https://review.openstack.org/#/c/185300/
  • API WG spec review: Clarifications on state-conflicting requests [1]
  • Return request ID to caller (tpatil): Spec review [2]
  • Add your topic here !
  • Open discussion

Agenda backlog

  • tbd


Previous meetings

This meeting has existed in OpenStack since the very beginning, and changed names and focus over the years. You'll find previous meetings logs there:


Chair rotation

For Liberty, we're organizing a chair rotation so that everyone get a chance to feel how that meeting works and can ultimately suggest evolutions to the format. TC members and PTLs are encouraged to apply, just put your name on this rotation schedule if you are interested. Here is the list of Liberty meeting chairs:

  • May 26 - ttx
  • June 2 - dhellmann
  • June 9 - markmcclain
  • June 16 - ttx
  • June 23 - slicknik
  • June 30 - annegentle
  • July 7 - markmcclain
  • July 14 - nikhil_k
  • July 21 - ?
  • July 28 - ?
  • August 4 - markmcclain
  • August 11 -?
  • August 18 - ?
  • August 25 - ?
  • September 1 - ?
  • Sept 8 - ?
  • Sept 15 - ?
  • Sept 22 - ?
  • Sept 29 - ?
  • Oct 6 - ?
  • Oct 13 - ?


Meeting chair guide

  • Thanks for volunteering! it will all go well. As you probably already know, we use this meeting as a venue for cross-project communication and discussion. Horizontal projects and vertical project teams get a soap box, anyone can raise a discussoin topics, and we openly discuss cross-project specs there too.
  • The day before the meeting, please review the agenda at the top of this page. If there aren't that many topics proposed, you should consider adding one or two cross-project specs for discussion. Look up the list of open cross-project specs and see which ones haven't been discussed in a meeting yet (looking at the previous meetings logs can help).
  • At least 12 hours before the meeting, send a meeting reminder with the final agenda. You can use the following model, or come up with your own words :)
  • To start the meeting, use #startmeeting crossproject
  • Next, send courtesy pings to the PTLs to remind them of the meeting starting. You can use a tool like https://review.openstack.org/190238 and paste the output into your IRC client.
  • Then, publish the link to the agenda for the meeting (this page).
  • During the meeting, you'll be responsible for pushing the various topics, trying to keep the discussion on topic and actionable, and keeping an eye on the clock. Use #topic to mark each topic change.
  • You can find the near-full list of Meetbot commands here. Instructions for voting (which can be useful for a quick show of hands) live here.
  • During the meeting, don't forget to liberally use #info, #agreed, #action or #link to make sure the critical discussion points will be highlighted in the meeting log. You can encourage other attendees to use those Meetbot keywords as well.
  • To end the meeting, use #endmeeting