15:00:10 <vishalmanchanda> #startmeeting horizon
15:00:10 <opendevmeet> Meeting started Wed Jan 18 15:00:10 2023 UTC and is due to finish in 60 minutes.  The chair is vishalmanchanda. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:10 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:10 <opendevmeet> The meeting name has been set to 'horizon'
15:00:28 <rdopiera> o/
15:01:02 <vishalmanchanda> Hello everyone
15:01:36 <amotoki> hi
15:02:21 <tmazur> o/
15:02:58 <vishalmanchanda> There is no topic added in our agenda etherpad for today's meeting https://etherpad.opendev.org/p/horizon-release-priorities#L34
15:03:22 <vishalmanchanda> I also have no update to share for this week.
15:04:22 <vishalmanchanda> So directly going to open-discussion
15:04:32 <vishalmanchanda> #topic open-discussion
15:04:58 <vishalmanchanda> if anyone have some topic to discuss, please go ahead.
15:05:56 <rdopiera> so I talked with the MoinMoin developers about the xstatic packages
15:06:56 <rdopiera> we agreed that two of the packages that are currently under the openstack org should be maintained by the moinmoin project instead
15:07:13 <rdopiera> the discussion is here: https://github.com/moinwiki/moin/issues/1326
15:07:57 <rdopiera> so the next step would be to basically remove xstatic-font-awesome and xstatic-jquery.tablesorter from the opendstack org
15:08:38 <vishalmanchanda> if someone don't know what radomir is discussing please go through the logs of last weekly meeting https://meetings.opendev.org/irclogs/%23openstack-horizon/%23openstack-horizon.2023-01-11.log.html#t2023-01-11T15:24:31
15:08:42 <rdopiera> I'm not sure who has the power to actually do that, I was planning to write an e-mail on the mailing list about it
15:08:54 <amotoki> one question: do they accept xstatic-font-awesome update even when they have no need for update (from POV of moinmoin)?
15:09:07 <rdopiera> yes
15:09:22 <rdopiera> they have accepted updates for jquery previously
15:09:38 <rdopiera> and several other packages under their care
15:10:13 <rdopiera> related to this, we should probably pin all versions of our xstatic packages
15:11:12 <amotoki> because these PyPI packages are now external, right?
15:11:23 <rdopiera> only those two
15:11:33 <rdopiera> we keep all the rest
15:11:57 <amotoki> thanks. same as my understanidng
15:13:58 <vishalmanchanda> I can purpose a patch to pin all versions of our xstatic packages.
15:14:38 <amotoki> can't we depend on upper-constraints instead of pinning them?
15:15:17 <amotoki> if some new package breaks horizon, we can block it. I think it is what we usually do.
15:16:42 <vishalmanchanda> amotoki: that is also fine.
15:16:51 <vishalmanchanda> I noticed one more thing.
15:18:52 <vishalmanchanda> upper-constraint for any xstatic package will not be bumped in openstack/requirements until we done a release for that
15:19:44 <vishalmanchanda> For e.g. we updated xstatic-angular https://review.opendev.org/c/openstack/xstatic-angular/+/843342 and then done a release for the same https://review.opendev.org/c/openstack/releases/+/843670
15:20:14 <amotoki> vishalmanchanda: if a library is our (i.e. openstack) deliverable, u-c is only updated when a release is cut.
15:20:39 <vishalmanchanda> after that it is updated here https://review.opendev.org/c/openstack/requirements/+/844099
15:20:40 <amotoki> if a library is external, a periodic job checks it and propose an update of u-c file
15:21:17 <vishalmanchanda> but then why xstatic-font-awesome latest version is used?
15:21:32 <vishalmanchanda> https://pypi.org/project/XStatic-Font-Awesome/
15:22:28 <vishalmanchanda> it is still using older version https://github.com/openstack/requirements/blob/master/upper-constraints.txt#L68
15:23:10 <amotoki> vishalmanchanda: where is the new xstatic-font-awesome used?
15:23:39 <vishalmanchanda> I mean we are not using new version
15:25:27 <amotoki> so, what is a problem?
15:27:00 <rdopiera> the original problem was that the TC was concerned that a release was made of the font awesome without following the openstack release process
15:27:13 <rdopiera> despite the fact that it was hosted on opendev
15:28:28 <rdopiera> turns out that when we adopted all those xstatic packages into opendev, we mistakenly took those two packages which were actually being maintained by moinmoin, thinking they are unmaintained
15:29:28 <rdopiera> (note that like all open source projects, the moinmoin wiki project had a bit of worse years lately)
15:31:35 <gmann> and if xstatic-font-awesome is not maintained by external maintainer (non-openstack) then it is fine to handover to them and horizon can be one of the user? unless they want to come and contribute/maintain as pert of openstack ?
15:31:47 <amotoki> I think I understand the original problem above
15:32:21 <gmann> because currently xstatic-font-awesome is one of the Horizon deliverables https://governance.openstack.org/tc/reference/projects/horizon.html#deliverables
15:32:30 <amotoki> what I don't understand is vishalmanchanda noticed that u-c was not updated and I am not what is a prbolem
15:32:32 <rdopiera> gmann: they are happy to maintain those two packages, they find the opendev/openstack process to be too heavy and slow for themn
15:32:51 <vishalmanchanda> amotoki: sorry for confusion.
15:32:54 <amotoki> * I am not sure what is a problem
15:32:54 <gmann> rdopiera: I see, I can understand that.
15:33:00 <gmann> amotoki: ohk
15:34:32 <vishalmanchanda> rdopiera: for removing static-font-awesome and xstatic-jquery.tablesorter from the opendstack org, we have to follow the same process we did for django-openstack-auth
15:34:32 <gmann> I think if they are happy and horizon team also ok then we can proceed to move them out from horizon deliverables and use as they are maintained outside like any other deps
15:34:43 <vishalmanchanda> rdopiera: see https://review.opendev.org/c/openstack/governance/+/800471
15:35:56 <vishalmanchanda> https://review.opendev.org/q/topic:retire-django-openstack-auth
15:36:42 <gmann> it seems they are and will maintain it in https://github.com/FortAwesome/Font-Awesome ? and not in https://github.com/openstack/xstatic-font-awesome ?
15:37:16 <amotoki> gmann: the github repo you mentioned is the upstream of font-awesome
15:37:17 <gmann> former is the location in PyPi  page "repository" https://pypi.org/project/XStatic-Font-Awesome/
15:37:39 <amotoki> there is no repo for xstatic-font-awesome after we drop our xstaic-font-awesome repo
15:38:12 <gmann> amotoki: ohk, that is linked in PyPi page which seems incorrect
15:38:35 <amotoki> gmann: this is what I would like to ask too
15:38:56 <rdopiera> gmann: they are going to be kept either in https://github.com/xstatic-py or https://github.com/python-xstatic, depending on which one they decide is going to be the canonical one (right now some are in one and some are in the other)
15:39:08 <gmann> ohk
15:39:21 <rdopiera> gmann: the repository ulr on pypi is the link to the original project being packaged, not the xstatic repo
15:39:31 <rdopiera> I suggested it should be made more clear too
15:39:32 <gmann> yeah
15:39:37 <gmann> I think in any case, we can do the retirement which will reflect in opendev repo as well as in https://github.com/openstack/xstatic-font-awesome
15:39:53 <rdopiera> we should probably update our pypi links as well
15:39:56 <amotoki> rdopiera: great. that's what I would like to ask :-)
15:40:02 <gmann> +1
15:40:05 <rdopiera> we should probably update our pypi links as well
15:40:24 <rdopiera> sorry, double message
15:40:31 <amotoki> np
15:41:07 <gmann> if we go with the retirement process then same will reflect in README.rst for  opendev repo as well as in https://github.com/openstack/xstatic-font-awesome
15:41:22 <gmann> and we can mention the location they are maintaining it in case anyone want to help them
15:41:38 <amotoki> gmann: +1
15:42:01 <amotoki> vishalmanchanda: a governance patch is not a thing we need to do. let's follow the retirement process documented in the project team guide.
15:42:15 <amotoki> * is not an only thing *
15:42:25 <vishalmanchanda> amotoki: sure.
15:42:28 <gmann> +1 on complete retirement process.
15:43:06 <gmann> amotoki: thanks for pointing that, otherwise we left with many cleanup for retired repo :)
15:43:20 <amotoki> :-)
15:43:31 <amotoki> besides xstatic-font-awesome, is it better that we check the current maintainers of other xstatic packages hosted by openstack?
15:43:49 <amotoki> i mean maintainers of PyPI packages
15:43:52 <rdopiera> yes, we should remove rob at least
15:44:04 <vishalmanchanda> agreed
15:44:10 <gmann> +1, that is next question/audit TC would like every project to ask as part of the PyPi maintainer cleanup
15:44:15 <gmann> please do
15:44:27 <rdopiera> probably remove me as well, so it's not repeated when I don't work on openstack anymore
15:44:41 <gmann> TC is planning to keep only 'openstackci' only in PyPi maintainer list
15:44:50 <rdopiera> that's sane
15:44:52 <vishalmanchanda> gmann: +1.
15:45:04 <rdopiera> not sure I can remove myself
15:45:12 <rdopiera> I will try
15:45:47 <gmann> rdopiera: thanks, or I think any existing member can do addition/remove but let me know. TC will reach to opendev admin to do those cleanup for many other repo too.
15:48:50 <vishalmanchanda> I will start the retirement process as mentioned here https://docs.openstack.org/project-team-guide/repository.html#retiring-a-repository once rdopiera send the mail that we are retiring these project from openstack tree.
15:49:52 <gmann> thanks amotoki vishalmanchanda rdopiera for discussing and handling it.
15:50:07 <amotoki> gmann: you too
15:52:14 <vishalmanchanda> Does anyone have any other topic to discuss?
15:52:53 <amotoki> I have a topic on a sec bug about agnular in older branches
15:53:07 <amotoki> but it is a sec issue so I will send a mail to you
15:53:24 <vishalmanchanda> amotoki: I was also looking at same bug...
15:53:40 <vishalmanchanda> amotoki: sure let's discuss it on mail.
15:54:50 <vishalmanchanda> if no other topic to discuss, let's end this meeting and triage some bugs.
15:55:04 <vishalmanchanda> Thanks everyone for joining, see you next week.
15:55:31 <amotoki> o/
15:55:39 <vishalmanchanda> #endmeeting