Difference between revisions of "Meetings/Horizon"

Latest revision as of 03:45, 17 October 2019

The OpenStack Horizon Team holds public meetings in #openstack-meeting-alt, weekly on Wednesdays at 1500 UTC.

See http://eavesdrop.openstack.org/#Horizon_Team_Meeting for recordings of previous meetings and the upcoming meeting schedule.

Everyone is encouraged to attend!

Agenda for Next Meeting

We maintain the meeting topics in the etherpad https://etherpad.openstack.org/p/horizon-release-priorities

See "Weekly meeting" section around the top of the etherpad.

@@ Line 1: / Line 1: @@
-The [[OpenStack]] [[Horizon]] Team holds public meetings in #openstack-meeting-3, weekly on Wednesdays at 2000 UTC.
+The [[OpenStack]] [[Horizon]] Team holds public meetings in #openstack-meeting-alt, weekly on Wednesdays at 1500 UTC.
 See http://eavesdrop.openstack.org/#Horizon_Team_Meeting for recordings of previous meetings and the upcoming meeting schedule.
@@ Line 6: / Line 6: @@
 == Agenda for Next Meeting ==
-* Notices
-* Priority bugs - mention 'em if you've got 'em!
+We maintain the meeting topics in the etherpad https://etherpad.openstack.org/p/horizon-release-priorities
-* Open Discussion
-** dropping nova network (amotoki) -- note that I cannot attend a meeting due to the meeting time --
+See "Weekly meeting" section around the top of the etherpad.
-*** Do we drop nova-network support '''in Pike''' or just deprecates it? https://blueprints.launchpad.net/horizon/+spec/drop-nova-network
-*** novaclient 8.0.0 dropped nova-network supports and horizon depends on python binding provided by novaclient. Do we drop it in this release? We haven't explicitly deprecate it as horizon. Does it sound reasonable to drop it now (from technical point of view and/or from the point of governance deprecation policy)?
-** horizon feature deprecation policy (amotoki)
-*** nova-network and novaclient discussion raises me a question on what horizon feature deprecation policy should be.
-*** Can we say "A feature deprecated in a back-end project is automatically deprecated in Horizon and a feature in horizon will be dropped if a corresponding support is dropped in a back-end project and/or its support library (like python bindings)" ?
-*** Or do we always want to deprecate something explicitly?
-*** Of course, horizon can provide extended supports.