15:01:34 <e0ne> #startmeeting horizon
15:01:35 <openstack> Meeting started Wed Oct  7 15:01:34 2020 UTC and is due to finish in 60 minutes.  The chair is e0ne. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:01:36 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:01:38 <openstack> The meeting name has been set to 'horizon'
15:01:49 <vishalmanchanda> hi
15:01:51 <e0ne> hi
15:03:06 <rdopiera> hi
15:04:34 <amotoki> hi
15:05:44 <e0ne> let's start
15:05:54 <e0ne> #topic Notices
15:07:09 <e0ne> TC election started
15:07:43 <e0ne> you can find a mail from Jeremy Stanley <civs@cs.cornell.edu> to get a link for the poll
15:07:49 <e0ne> subject: Poll: OpenStack Wallaby Cycle Technical Committee Election Poll
15:08:25 <e0ne> every link is unique, so it was sent personally each contributor
15:09:54 <e0ne> OpenStack Victoria will be released next week https://releases.openstack.org/victoria/schedule.html #link
15:10:12 <e0ne> nothing special for horizon, just for you info.
15:10:15 <fungi> feel free to let me know if you have any questions too
15:10:23 <amotoki> e0ne: will you cut another horizon release this week to include the latest translation?
15:11:05 <e0ne> amotoki: do we need to do it this week?
15:11:35 <e0ne> IMO, it's better to do it early next week (Mon or Tue)
15:11:45 <amotoki> e0ne: we usually did it, so I asked it.
15:11:54 <amotoki> I haven't checked when was our last release.
15:12:05 <amotoki> did it happen last week?
15:12:42 <e0ne> it was done 12 days ago
15:13:20 <e0ne> tomorrow is Hard StringFreeze, that's why my proposal is to wait a bit more for translations
15:14:32 <amotoki> but this week is for the last release.
15:14:50 <amotoki> next week is for the release team and it is not recommended to cut a release next week.
15:15:53 <amotoki> According to the schedule, HardStringFreeze was the week of Sep 25
15:16:17 <amotoki> this week is "Final RCs and intermediary releases"
15:16:33 <e0ne> amotoki: I mixed up everything:(
15:16:59 <e0ne> amotoki: you're right, let's cut a new release tomorrow
15:17:06 <amotoki> +1
15:18:52 <amotoki> the version would be 18.6.1
15:18:57 <e0ne> it would be good to have this https://review.opendev.org/#/c/756452/ merged too, but it's not merged in master yet
15:19:22 <e0ne> but it's not a release blocker for sure
15:21:39 <e0ne> do we have anything else Victoria-specific?
15:23:38 <amotoki> nothing from me
15:23:54 <vishalmanchanda> nothing from my side.
15:24:15 <e0ne> ok, let's move to the next topic
15:24:34 <e0ne> #topic Open Discussion
15:24:48 <e0ne> does anybody want talk about something?
15:25:09 <vishalmanchanda> I have a topic to discuss
15:26:07 <vishalmanchanda> I was just going through our feature-gap etherpad and selecting which feature I can target for next cycle.
15:26:09 <e0ne> vishalmanchanda: go ahaed
15:26:47 <vishalmanchanda> I have shortlisted a few like quotas per volume type https://review.opendev.org/#/c/660567( I will review it)
15:27:06 <vishalmanchanda> 2. multi-backend support or glance(Experimental ATM in glance)
15:27:23 <vishalmanchanda> 3. floating IP port forwarding(neutron)
15:27:45 <vishalmanchanda> 4. backups management for admin(easy and good to have it from operator POV)
15:28:27 <vishalmanchanda> I want to know your opinion.
15:28:48 <vishalmanchanda> Is it worth?
15:29:18 <vishalmanchanda> https://etherpad.opendev.org/p/horizon-feature-gap
15:29:48 <e0ne> I'll be happy with any new feature
15:30:23 <vishalmanchanda> If anyone have some other good feature that good to have in horizon I also want to hear about them as well.
15:30:41 <amotoki> I am happy with any new features but I have no opinion on them at the moment because I haven't identified how many common topics which are more important than them we have.
15:32:15 <e0ne> amotoki: +1
15:32:45 <vishalmanchanda> hmm.
15:33:07 <amotoki> generally speaking, user-facing features are preferred.
15:33:23 <e0ne> +2
15:33:36 <amotoki> admin/operators tend to script or automate their tasks rather than GUI.
15:33:38 <e0ne> that's the whole idea of horizon :)
15:34:23 <vishalmanchanda> yeah.
15:35:32 <amotoki> before discussing which one/two should be selected, don't we need to check and refersh the etherpad?
15:35:55 <amotoki> I am not sure all listed there match the current status.
15:36:30 <vishalmanchanda> yeah because many of them already completed
15:36:31 <amotoki> personally we should close feature gaps in Angular Launch Instance form
15:36:53 <amotoki> it is not a good idea to manitain two types of the launch instance form for long.
15:37:07 <e0ne> #action team to check https://etherpad.opendev.org/p/horizon-feature-gap and update it if needed
15:37:13 <e0ne> #link https://etherpad.opendev.org/p/horizon-feature-gap
15:40:01 <vishalmanchanda> amotoki: Ok I will check if I can pick any of  feature from Angular Launch Instance form.
15:40:29 <e0ne> vishalmanchanda: thanks
15:40:41 <amotoki> vishalmanchanda: I believe tmazur can help closing them too.
15:41:00 <tmazur> I can help, yes
15:41:18 <vishalmanchanda> amotoki: yeah because I haven't explore that part of code so much.
15:41:46 <vishalmanchanda> amotoki: Also last time when I checked it's low priority for horizon.
15:41:55 <vishalmanchanda> tmazur: thanks:)
15:41:58 <amotoki> vishalmanchanda: it would be a good chance to explore such areas.
15:42:43 <amotoki> vishalmanchanda: regarding the priority, Angular Laucnh instance form is our default so it should be prioritized.
15:43:14 <amotoki> vishalmanchanda: what we discussed is about the priorities of new migrations to Angular.
15:43:25 <amotoki> vishalmanchanda: hope it clarifies the situation
15:44:04 <vishalmanchanda> amotoki: +1.
15:45:15 <vishalmanchanda> that's all from my side.
15:45:26 <e0ne> I've got one more topic to dicsuss
15:45:42 <e0ne> and I'm sure 15 minutes is not enough for it
15:46:02 <e0ne> but I would like to talk about mypy in horizon
15:46:16 <e0ne> #link http://mypy-lang.org/
15:46:38 <e0ne> since we don't support python2 anymore, we. can go forward with it
15:47:06 <e0ne> I don't want to propose dozens of patches with it
15:47:40 <e0ne> but I think it would be useful for our internal and public,plugin-related, APIs
15:49:08 <amotoki> generally speaking, it would be useful
15:49:43 <e0ne> my idea is do it step-by-step with other code changes
15:50:31 <e0ne> at least, we need some infrastructure for it: tox env, config, job
15:50:57 <e0ne> if nobody argues on it, I'll propose patches soon
15:51:09 <e0ne> and we can discus them in gerrit and/or PTG
15:51:10 <tmazur> let's discuss it at PTG maybe?
15:51:32 <vishalmanchanda> I can see other project also using it like nova.
15:51:42 <amotoki> e0ne: what is the difference between mypy and type hints in python native https://docs.python.org/3/library/typing.html
15:51:43 <amotoki> ?
15:52:04 <tmazur> amotoki: +1
15:52:17 <e0ne> amotoki: frankly speaking eking, we need  type hits
15:52:45 <e0ne> mypy was introduced before type hints were merged into the python core
15:53:02 <e0ne> but people still uses 'mypy' naming more widly
15:53:10 <e0ne> at least people I know
15:53:57 <amotoki> type hints is just a hint and python runtime does not enforce it.
15:54:10 <e0ne> yep
15:54:12 <amotoki> does mypy provide static check?
15:54:27 <e0ne> it's used on CI and durine development
15:54:31 <amotoki> if so it is an additional merit.
15:55:53 <e0ne> yes, nothing changes in a runtime
15:56:07 <e0ne> #link https://www.python.org/dev/peps/pep-0484/
15:56:17 <e0ne> "The proposal is strongly inspired by mypy [mypy]."
15:56:40 <e0ne> mypy woks for python 2, but I really don't care on it
15:56:56 <e0ne> and I do understand that backports will be more complicated
15:58:52 <amotoki> we will have two releases with python3 only, so it might be a good timing to start this kind of discussions.
15:59:05 <amotoki> I mean Ussuri and Victoria.
15:59:26 <e0ne> that's why I didn't propose to do it in Victoria
15:59:34 <amotoki> :)
15:59:41 <amotoki> I have one thing to share before closing the meeting.
15:59:44 <amotoki> I have one thing to share before closing the meeting. I added "Feature Removals" in Wallaby to our etherpad https://etherpad.opendev.org/p/horizon-release-priorities  Feel free to add any if you have/notice.
16:00:27 <e0ne> amotoki: good idea! it will help us with releases and release notes
16:00:36 <amotoki> I would like to have such changes in the first release for Wallaby.
16:00:43 <e0ne> +1
16:02:12 <e0ne> we're out of time
16:02:21 <e0ne> thanks for your contributions!
16:02:34 <e0ne> we can continue our discussion in #openstack-horizon
16:02:37 <e0ne> #endmeeting