Jump to: navigation, search

Difference between revisions of "Meetings/Blazar"

(Next meetings)
(Blazar weekly meeting)
Line 6: Line 6:
  
 
== Next meetings ==
 
== Next meetings ==
 +
 +
==== Agenda for March 21 2017 ====
 +
 +
* gate job
 +
* AOB
  
 
==== Agenda for March 21 2017 ====
 
==== Agenda for March 21 2017 ====
Line 51: Line 56:
 
* +1 or +2 at Code Review
 
* +1 or +2 at Code Review
 
* Pike cycle discussion
 
* 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 ==
 
 
* Historically, the Blazar project team held a weekly team meeting in #openstack-meeting on Fridays at 15:00 UTC
 
* Minutes before 30 May 2014 can be found here : http://eavesdrop.openstack.org/meetings/climate
 
* Minutes after 30 May 2014 can be found here : http://eavesdrop.openstack.org/meetings/blazar
 
 
==== 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 ==
 
== Meeting code of conduct ==

Revision as of 08:41, 28 March 2017

Blazar weekly meeting

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

Next meetings

Agenda for March 21 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 ?

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

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.