Difference between revisions of "Meetings/Blazar"
< Meetings
(→Agenda for February 2017) |
(→Next meetings) |
||
Line 6: | Line 6: | ||
== Next meetings == | == Next meetings == | ||
+ | |||
+ | ==== Agenda for February 14 2017 ==== | ||
+ | |||
+ | * Action items from last call | ||
+ | * Load to Ocata release | ||
+ | * Next weekly meeting | ||
+ | * Pike cycle discussion | ||
==== Agenda for February 7 2017 ==== | ==== Agenda for February 7 2017 ==== | ||
Line 40: | Line 47: | ||
* Status Updates | * Status Updates | ||
** https://etherpad.openstack.org/p/Blazar_status_2016 | ** https://etherpad.openstack.org/p/Blazar_status_2016 | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
Revision as of 08:03, 14 February 2017
Contents
Blazar weekly meeting
The Blazar project team holds a weekly team meeting in #openstack-meeting-alt
:
- Tuesdays at 09:00 UTC
Next meetings
Agenda for February 14 2017
- Action items from last call
- Load to Ocata release
- Next weekly meeting
- 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
Agenda for January 24 2017
- Action items from last call
- CFP of the Boston Summit (deadline: 0800 UTC, FEBRUARY 6)
- oslo conversion
- devstack
- Ocata release
- Status Update
- PTG
- Pike PTL
Agenda for January 17 2017
- Action items from last call
- CFP of the Boston Summit (deadline: 0800 UTC, FEBRUARY 6)
- Pike PTL election
- Status Updates
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
- 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.