Jump to: navigation, search

Difference between revisions of "Meetings/Blazar"

(Next meetings)
(Agenda for March 7 2017)
Line 11: Line 11:
 
* Action items from last call
 
* Action items from last call
  
* ...
+
* Ocata (0.2.0) release
 +
 
 +
* Pike blueprints
 +
** [Discussion] Add options for on_end action: config vs. request parameter (https://blueprints.launchpad.net/blazar/+spec/on-end-options)
  
 
* AOB
 
* AOB
** create new Blazar_status_2017 page ?  
+
** create new Blazar_status_2017 page ?
  
 
==== Agenda for February 28 2017 ====
 
==== Agenda for February 28 2017 ====

Revision as of 06:13, 6 March 2017

Blazar weekly meeting

The Blazar project team holds a weekly team meeting in #openstack-meeting-alt:

Next meetings

Agenda for March 7 2017

  • Action items from last call
  • Ocata (0.2.0) release
  • AOB
    • create new Blazar_status_2017 page ?

Agenda for February 28 2017

Agenda for February 14 2017

  • Action items from last call
  • Load to Ocata release
  • Next weekly meeting
  • +1 or +2 at Code Review
  • Pike cycle discussion

Agenda for February 7 2017

  • Action items from last call
  • Release versioning and date
  • Pike cycle discussion

Agenda for January 31 2017

  • Action items from last call
  • CFP of the Boston Summit (deadline: 0800 UTC, FEBRUARY 6)
  • Tempest
  • Status Update


See Etherpad for more details: https://etherpad.openstack.org/p/Blazar_status_2016

Previous meetings

Agenda for Jun 27 2014

  • Action items from the last meeting + reviews queries
  • Climate -> Blazar renaming status
  • Blueprints status
  • Open discussion

Meeting code of conduct

  • Amend the agenda before the meeting is starting, not after
  • We can leave an open discussion topic at the end of the meeting
  • People having reviews in progress should attend the meeting. If they can't, the ideal would be to briefly catch-up on the status before the meeting.