Jump to: navigation, search

Difference between revisions of "Meetings/Blazar"

(Agenda for April 11 2017)
(Next meetings)
Line 58: Line 58:
 
* AOB
 
* AOB
 
** create new Blazar_status_2017 page ?
 
** create new Blazar_status_2017 page ?
 
==== Agenda for February 28 2017 ====
 
 
* Summary of PTG
 
** https://etherpad.openstack.org/p/blazar-ptg-pike
 
** https://etherpad.openstack.org/p/Blazar_status_2016
 
* Deprecation rules
 
** details: https://review.openstack.org/#/c/434777/
 
* Remaining Reviews for O
 
 
==== 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
 
  
 
== Meeting code of conduct ==
 
== Meeting code of conduct ==

Revision as of 05:53, 11 April 2017

Blazar weekly meeting

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

Next meetings

Agenda for April 11 2017

Agenda for April 4 2017

  • Pike blueprints status check
  • Boston Summit
  • AOB

Agenda for March 28 2017

  • gate job
  • AOB

Agenda for March 21 2017

  • Ocata (0.2.0) release
  • Boston Summit
  • AOB


Agenda for March 14 2017

  • Action items from last call
  • Ocata (0.2.0) release
  • Pike blueprints
  • Boston Summit
  • AOB

Agenda for March 7 2017

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

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.