Difference between revisions of "Meetings/Horizon"

Revision as of 15:06, 22 May 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

Notices
Action items from the previous meeting
Release Priorities
- https://etherpad.openstack.org/p/horizon-release-priorities
Open Discussion
- ini-based-configuration (amotoki)
  - The planning document needs to be reviewed first. Other
  - how can I move this forward without a ton of rebase?

@@ 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 ==
-amotoki won't attend the meeting Dec 20 though he added some topics.
 * Notices
+* Action items from the previous meeting
+* Release Priorities
+** https://etherpad.openstack.org/p/horizon-release-priorities
 * Open Discussion
+** ini-based-configuration (amotoki)
-* keystone policy: is_cloud_admin and is_domain are broken with the latest policy from keystone repo)
+*** The planning document needs to be reviewed first. Other
-** https://bugs.launchpad.net/horizon/+bug/1739108
+*** how can I move this forward without a ton of rebase?
-** amotoki thinks it is critical.
-** What is the way we go?
-** Who can take care of it? Needs volunteer.
-* Supported Django versions?
-** [notice] Horizon works with Django 2.0. (but you see UnhashbleWarning and we need a volunteer to investigate it) I don't know it lands in Queens as I am the author. I have less time until Jan 15 2018 from now on.
-** The installation document needs to be updated, but it needs a volunteer. It is beyond the bandwidth of amotoki.
-** Should Django 2.0 support be experimental in Queens? Even if horizon works with Django 2.0, there is no enough time for horizon plugins to support Django 2.0 in Queens. Perhaps, Debian only works with horizon and does not work with horizon plugins. Adding a new supported Django version in milestone-3 is not fair. "horizon" is an ecosystem with horizon core and plugins, so a sudden requirement should be avoided.
-** What Django version would we like to support as primary version(s)? LTS(s) of course need to be supported. What for non-LTS versions? Does the horizon team support non-LTS Django versions aggressively (as a project plan)? Or do we accept a patch to support non-LTS Django versions if someone works on it? (it means we don't reject a work but it is optional.) This depends on distributors' opinions. Anyway I think it is time to document it (considering the project human resources).