Jump to: navigation, search

Difference between revisions of "Meetings/Horizon"

(Agenda for next meeting (Sep 9))
(Agenda for next meeting (Sep 2))
Line 7: Line 7:
  
 
== Agenda for next meeting (Sep 9) ==
 
== Agenda for next meeting (Sep 9) ==
 
+
* Release Timelines
 +
* FFEs
 +
** 2 have already landed
 +
*** IPv6 status -- fully complete?
 +
** 1 more covers 3 blueprints
 +
** 1 potential -- needs support
 +
*** https://blueprints.launchpad.net/horizon/+spec/cinder-qos-specs
 
* Allow translators to translate BatchActions https://review.openstack.org/#/c/91338/ (amotoki, Doug Fish?)
 
* Allow translators to translate BatchActions https://review.openstack.org/#/c/91338/ (amotoki, Doug Fish?)
 
** From my experience of translations for Juno, it seems useful regardless of pain for developers. I would like to discuss the direction in Juno (and more).
 
** From my experience of translations for Juno, it seems useful regardless of pain for developers. I would like to discuss the direction in Juno (and more).
 
+
* Summit Format Changes
== Agenda for next meeting (Sep 2) ==
+
** Cross-Project
* Making calls to APIs on every request (rdopieralski)
+
** 4-5 scheduled sessions
** Checking which panels to display
+
*** Topic proposal will be etherpad based rather than the previous proposal tool
** Mocking it properly
+
** 1/2 day of unscheduled time
 +
* Discuss potential changes to the blueprint process
 +
** Level of detail
 +
** Approval process
 +
** Number per cycle
  
 
== Previous meetings ==
 
== Previous meetings ==
  
 
http://eavesdrop.openstack.org/meetings/horizon/
 
http://eavesdrop.openstack.org/meetings/horizon/

Revision as of 14:55, 9 September 2014

The OpenStack Horizon Team holds public meetings in #openstack-meeting-3. Everyone is encouraged to attend.

Apologies for absence

  • jpich (Sept 9)

Agenda for next meeting (Sep 9)

  • Release Timelines
  • FFEs
  • Allow translators to translate BatchActions https://review.openstack.org/#/c/91338/ (amotoki, Doug Fish?)
    • From my experience of translations for Juno, it seems useful regardless of pain for developers. I would like to discuss the direction in Juno (and more).
  • Summit Format Changes
    • Cross-Project
    • 4-5 scheduled sessions
      • Topic proposal will be etherpad based rather than the previous proposal tool
    • 1/2 day of unscheduled time
  • Discuss potential changes to the blueprint process
    • Level of detail
    • Approval process
    • Number per cycle

Previous meetings

http://eavesdrop.openstack.org/meetings/horizon/