Difference between revisions of "Meetings/Horizon"

Revision as of 13:07, 16 May 2018

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
Community Goals
- mox => mock migration
- Current status: https://etherpad.openstack.org/p/horizon-unittest-mock-migration
horizon release model: cycle-with-milestone vs cycle-with-intermediary
- The infra change (zuulv3 configuration change) [1] now forces horizon plugin developers to handle horizon dependencies in a tricky way.
  - The OpenStack CI installs horizon master (based on tox-siblings) and it works well, but local testing will fail because it installs horizon queens.
  - This problem is based on a horizon version published to PyPI.
  - horizon is a kind of library from perspective of horizon plugins. from this point, it is reasonable to publish horizon with cycle-with-intermediary.
  - If so, the version of horizon would follow semantic versioning. It would help horizon plugin developers.
  - However, the versioning might be surprising for horizon consumers like operators/users.
- horizon-lib again might be a good candidate on this problem.
- [1] http://lists.openstack.org/pipermail/openstack-dev/2018-March/128310.html
Improve Horizon Testing
- Blueprint https://blueprints.launchpad.net/horizon/+spec/improve-horizon-testing
- Getting rid of Nose test runner
- Open patches:
  - https://review.openstack.org/#/q/status:open+branch:master+topic:bp/improve-horizon-testing
- Cross-project CI jobs to test plugins
Django 2 support
- https://etherpad.openstack.org/p/django20-support
- http://lists.openstack.org/pipermail/openstack-dev/2018-May/130261.html
Horizon feature gap
- https://etherpad.openstack.org/p/horizon-feature-gap
Review priority
- https://etherpad.openstack.org/p/horizon-reviews-priority
- Feel free to add your patches to the etherpad above
Open Discussion

@@ Line 9: / Line 9: @@
 * Notices
 * Action items from the previous meeting
-** horizon release model: cycle-with-milestone vs cycle-with-intermediary
+* Community Goals
-*** The infra change (zuulv3 configuration change) [1] now forces horizon plugin developers to handle horizon dependencies in a tricky way.
+** mox => mock migration
-**** The OpenStack CI installs horizon master (based on tox-siblings) and it works well, but local testing will fail because it installs horizon queens.
+** Current status: https://etherpad.openstack.org/p/horizon-unittest-mock-migration
-**** This problem is based on a horizon version published to PyPI.
+* horizon release model: cycle-with-milestone vs cycle-with-intermediary
-**** horizon is a kind of library from perspective of horizon plugins. from this point, it is reasonable to publish horizon with cycle-with-intermediary.
+** The infra change (zuulv3 configuration change) [1] now forces horizon plugin developers to handle horizon dependencies in a tricky way.
-**** If so, the version of horizon would follow semantic versioning. It would help horizon plugin developers.
+*** The OpenStack CI installs horizon master (based on tox-siblings) and it works well, but local testing will fail because it installs horizon queens.
-**** However, the versioning might be surprising for horizon consumers like operators/users.
+*** This problem is based on a horizon version published to PyPI.
-*** horizon-lib again might be a good candidate on this problem.
+*** horizon is a kind of library from perspective of horizon plugins. from this point, it is reasonable to publish horizon with cycle-with-intermediary.
-*** [1] http://lists.openstack.org/pipermail/openstack-dev/2018-March/128310.html
+*** If so, the version of horizon would follow semantic versioning. It would help horizon plugin developers.
+*** However, the versioning might be surprising for horizon consumers like operators/users.
+** horizon-lib again might be a good candidate on this problem.
+** [1] http://lists.openstack.org/pipermail/openstack-dev/2018-March/128310.html
+* Improve Horizon Testing
+** Blueprint https://blueprints.launchpad.net/horizon/+spec/improve-horizon-testing
+** Getting rid of Nose test runner
+** Open patches:
+*** https://review.openstack.org/#/q/status:open+branch:master+topic:bp/improve-horizon-testing
+** Cross-project CI jobs to test plugins
+* Django 2 support
+** https://etherpad.openstack.org/p/django20-support
+** http://lists.openstack.org/pipermail/openstack-dev/2018-May/130261.html
+* Horizon feature gap
+** https://etherpad.openstack.org/p/horizon-feature-gap
+* Review priority
+** https://etherpad.openstack.org/p/horizon-reviews-priority
+** Feel free to add your patches to the etherpad above
 * Open Discussion
-** Don't we discuss horizon release and versioning model any more? I see the topic was dropped from the meeting agenda... I don't want to add it for every meeting. (amotoki)