Difference between revisions of "Meetings/Horizon"
< Meetings
m (→Agenda for next meeting (Sep 9)) |
m (→Agenda for next meeting (Sep 9)) |
||
Line 14: | Line 14: | ||
** 1 potential -- needs support | ** 1 potential -- needs support | ||
*** https://blueprints.launchpad.net/horizon/+spec/cinder-qos-specs | *** https://blueprints.launchpad.net/horizon/+spec/cinder-qos-specs | ||
+ | * django-openstack-auth | ||
+ | ** new release for Juno? | ||
* 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). |
Revision as of 15:08, 9 September 2014
The OpenStack Horizon Team holds public meetings in #openstack-meeting-3. Everyone is encouraged to attend.
- Tuesdays at 16:00 UTC
Apologies for absence
- jpich (Sept 9)
Agenda for next meeting (Sep 9)
- Release Timelines
- FFEs
- 2 have already landed
- IPv6 status -- fully complete? -- Completed (amotoki)
- 1 more covers 3 blueprints
- 1 potential -- needs support
- 2 have already landed
- django-openstack-auth
- new release for Juno?
- 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