15:00:20 <amotoki> #startmeeting horizon
15:00:21 <openstack> Meeting started Wed Dec  4 15:00:20 2019 UTC and is due to finish in 60 minutes.  The chair is amotoki. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:22 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:24 <openstack> The meeting name has been set to 'horizon'
15:00:40 <vishalmanchanda> amotoki: hi
15:01:32 <amotoki> vishalmanchanda: hi
15:02:00 <rdopiera> hi
15:02:52 <tmazur> \o
15:03:23 <amotoki> tmazur: rdopiera: hi
15:04:13 <amotoki> tmazur: I am happy that you are back to horizon
15:04:56 <amotoki> let's start
15:05:23 <amotoki> the agenda is collected in https://etherpad.openstack.org/p/horizon-release-priorities ("Weekly meeting" section)
15:05:34 <amotoki> #topic notices
15:06:22 <amotoki> milestone-1 is next week, but it does not affect much to us.
15:06:35 <amotoki> is there any announcement or what to share?
15:07:10 <vishalmanchanda> none from my side.
15:07:18 <rdopiera> nothing
15:07:40 <amotoki> moving on
15:07:52 <amotoki> #topic General Priorities
15:07:56 <e0ne> hi
15:08:09 <amotoki> e0ne: hi
15:09:01 <amotoki> last week I requested to put your name to the etherpad "General Priorities" section in https://etherpad.openstack.org/p/horizon-release-priorities if you can volunteer.
15:09:31 <amotoki> rdopiera and I put our name already.
15:09:58 <amotoki> I think vishalmanchanda already volunteer for Django versions and error msg
15:10:01 <e0ne> I was unable to work upstream last week due to the personal reasons. will continue my contributions soon
15:10:24 <e0ne> amotoki: I'll take a look on the list in the etherpad after the meeting
15:10:37 <amotoki> e0ne: no worries. thanks
15:10:45 <rdopiera> you only have the Chinese translation letf :D
15:11:40 <e0ne> rdopiera: it's on the top of my priorities with mox removal
15:11:51 <amotoki> e0ne: i think you broke down the plan on Chinese translation topic with the i18n team in Shanghai. hopefully you can guide the plan.
15:12:07 <amotoki> I haven't figured out the real plan yet.
15:12:53 <amotoki> I can move it forward but I first need to know the plan and what was the discussion.
15:14:41 <e0ne> amotoki: I need to refresh my memory. I'll add notes to the etherpad
15:15:26 <amotoki> e0ne: thanks. it would be nice if you can send the summary to the list so that the i18n team including Ian can check it.
15:15:36 <e0ne> ok, will do it
15:16:07 <amotoki> thanks a lot
15:16:54 <amotoki> #topic Community Goals
15:17:13 <amotoki> no update from my side this week
15:17:43 <e0ne> nothing from me too :(
15:19:05 <amotoki> I believe the community goals in Ussuri are easy to achieve :)
15:19:15 <amotoki> I have no concern on them
15:19:42 <amotoki> #topic Django 2.2 in horizon plugins
15:20:02 <amotoki> the last piece of UT updates has been merged
15:20:11 <vishalmanchanda> yeah.
15:20:17 <amotoki> I requesed masakari PTL and he merged it.
15:20:25 <vishalmanchanda> amotoki: thanks.
15:21:16 <e0ne> vishalmanchanda: thanks for the working on it!
15:21:17 <vishalmanchanda> Now most probably i will send a mail to open-discuss about the next plan.
15:21:31 <vishalmanchanda> e0ne: np.
15:22:01 <vishalmanchanda> by this week.
15:22:13 <amotoki> vishalmanchanda shared his draft of the mail to e0ne and me. I thikn it is ready to go.
15:22:44 <vishalmanchanda> ok.
15:22:59 <vishalmanchanda> then I will send it after the meeting.
15:23:09 <amotoki> one thing I would like to note is we need "call for testing" to individual teams explicitly or implicitly after bumping the Django version
15:23:52 <e0ne> +1
15:24:08 <amotoki> a possible worst case is that individual teams do not care their horizon plugins till release and it turns out some plugins are broken after the release.
15:25:04 <amotoki> anyway bumping the default version around milestone-1 is a good plan :)
15:25:53 <vishalmanchanda> I have some doubts in bumping the django version.
15:26:00 <vishalmanchanda> Could you guys help.
15:26:13 <amotoki> what kind of doubt?
15:26:43 <vishalmanchanda> There are many django version are used in openstack/requirements.
15:26:56 <vishalmanchanda> https://github.com/openstack/requirements/blob/master/upper-constraints.txt#L511-L515
15:27:59 <amotoki> what's the problem?
15:28:06 <vishalmanchanda> Should I remove the entry for py3.4 and py3.5 in the same patch.
15:28:19 <vishalmanchanda> as they are longer used in openstack.
15:28:26 <amotoki> I think they are generated by a script in the requirements repo based on https://github.com/openstack/requirements/blob/master/global-requirements.txt#L41-L42
15:28:58 <amotoki> upper-constraints.txt is usually (always?) touched by a script.
15:29:45 <vishalmanchanda> ok.
15:30:16 <vishalmanchanda> then I have to bump django vesrion here only
15:30:17 <vishalmanchanda> https://github.com/openstack/requirements/blob/master/global-requirements.txt#L42
15:30:50 <amotoki> vishalmanchanda: have you read README of the requirements repo? IIRC there is a detail document.
15:30:51 <vishalmanchanda> and changed this to Django<=2.2;python_version>='3.6'  # BSD
15:31:49 <vishalmanchanda> amotoki: not yet. I will read README after the meeting.
15:31:54 <amotoki> I am not an expert of the requirements repo, so I cannot answer all to you.
15:32:12 <vishalmanchanda> amotoki: ok. np
15:32:19 <amotoki> I usually ask in #-requirements channel if I have questions on them.
15:32:28 <amotoki> they are very helpful.
15:33:15 <vishalmanchanda> I will purpose a patch for django bump and I hope requirement team will help me in that.
15:33:45 <amotoki> let's see what happens :)
15:33:56 <e0ne> :)
15:33:58 <vishalmanchanda> yeah:)
15:34:32 <amotoki> next topic
15:34:37 <amotoki> #topic bugs and reviews
15:34:59 <amotoki> is there any bugs or reviews which need attentions?
15:35:53 <amotoki> nggettext patch and change-password patch are in my queue
15:36:09 <vishalmanchanda> yeah exactly.
15:36:12 <vishalmanchanda> https://review.opendev.org/#/c/692945/
15:36:30 <vishalmanchanda> It would be nice to merge it fast.
15:37:03 <vishalmanchanda> waiting for Ivan reply on my comments.
15:37:28 <e0ne> vishalmanchanda: will to it tonight or tomorrow morning
15:37:37 <vishalmanchanda> e0ne: thanks.
15:39:13 <amotoki> #topic Horizon plugin wide topics/reviews/bugs
15:39:26 <amotoki> I see vishalmanchanda added a heat-dashboard patch here.
15:39:33 <vishalmanchanda> yeah.
15:39:44 <amotoki> I am not sure the horizon team is responsible for heat team community goal or not.
15:41:00 <amotoki> we are responsible for maintenance of heat dashboard as horizon framework POV but more than that is a work as heat(-dashboard) team.
15:41:09 <e0ne> +2
15:41:13 <vishalmanchanda> I have just added it as no-one reviewed it.
15:41:42 <vishalmanchanda> amotoki: +1.
15:41:55 <amotoki> perhaps heat team is the right contact for your question.
15:43:04 <vishalmanchanda> okay i will ask heat team to review it.
15:43:44 <vishalmanchanda> but no heat Core is active in heat-dashboard.
15:44:03 <amotoki> you can ask heat PTL on the community goal.
15:44:29 <amotoki> if they are not interested in it, that's the heat team decision.
15:44:44 <vishalmanchanda> yeah.
15:45:31 <amotoki> note that this section is for horizon pluign-WIDE
15:46:12 <amotoki> it is not a place to discuss a topic specific to a pluign. it is the place to discuss things which affect many/mutiple horizon plugins
15:47:01 <amotoki> #topic On-Demand Agenda
15:47:37 <amotoki> I have a topic on older stable branches in the extended maintenace phase.
15:47:55 <amotoki> currently ocata, pike and queens are in the EM phase.
15:48:18 <amotoki> do you have interests to watch them?
15:49:49 <e0ne> I'm OK to mark ocata and as end-of-life
15:50:02 <e0ne> what other teams do with queens?
15:50:20 <rdopiera> we still support Queens in RH
15:50:30 <amotoki> we can keep EM branches as long as their gate is healthy
15:50:34 <e0ne> the same for our distro
15:51:49 <amotoki> I think we should setup periodic jobs and check their healthiness periodically (perhaps by folks who are interested in those branches).
15:52:07 <amotoki> otherwise we cannot notice gate failure itself.
15:52:29 <tmazur> +1
15:52:36 <amotoki> the similar discussion happened for cinder EM branches recently
15:54:25 <amotoki> as summary: RH  needs queens. What about your case, e0ne?
15:54:41 <e0ne> amotoki: we supports queens too
15:54:55 <amotoki> how about pike?
15:55:36 <rdopiera> we don't support pike anymore
15:56:18 <rdopiera> newton support ends this month, and then it's just queens+
15:56:43 <amotoki> fine
15:57:37 <amotoki> we can setup periodic jobs and if their gate failure is detected we can ask the mailing list on whether anyone is interested in maintaining it.
15:57:59 <amotoki> I will add it to my todo list :)
15:58:19 <e0ne> great!
15:59:04 <amotoki> anything to discuss?
15:59:45 <amotoki> thanks for joining, everyone!
15:59:52 <amotoki> #endmeeting