| gmann | tc-members: need one more review on the election results https://review.opendev.org/c/openstack/governance/+/874042 | 01:59 |
|---|---|---|
| JayF | gmann: lgtm | 02:11 |
| gmann | JayF: thanks | 02:17 |
| opendevreview | Merged openstack/governance master: Update with 2023.2 Election results. https://review.opendev.org/c/openstack/governance/+/874042 | 02:35 |
| gmann | ^^ Welcome jamespage for newly elected TC and all the returning tc-members (knikolla[m] spotz slaweq rosmaita ) for continuing the next term | 02:36 |
| gmann | and thanks arne_wiebalck for all your work and contribution in TC | 02:37 |
| gmann | jamespage: I have shared the TC onboarding email to you but in case you have any query, feel free to ping us in this channel | 02:37 |
| jamespage | gmann: thanks :) on my read list this AM | 08:25 |
| ralonsoh | gmann, hello! qq: should I start sending the mail to the pypi mantainers? | 09:24 |
| ralonsoh | --> https://etherpad.opendev.org/p/openstack-pypi-maintainers-cleanup-email-template | 09:24 |
| ralonsoh | I'm not sure if that was decided or not (sorry) | 09:24 |
| bauzas | noonedeadpunk: I didn't really wanted to formalize One WSGI server to Rule them All you know | 10:13 |
| bauzas | noonedeadpunk: but my point is, we have devstack that runs it heavily | 10:13 |
| bauzas | and the uswsgi migration we had in the past is still in ringing in my brain | 10:13 |
| bauzas | so we should somehow do kind of an audit from a cross-project pov and see what needs to be done if any | 10:14 |
| noonedeadpunk | bauzas: the thing is, that users tend to pick software stack that is used in devstack as source of truth | 10:14 |
| bauzas | -ish but I don't disagree | 10:14 |
| bauzas | the wsgi stack is somehow a prescriber I agree | 10:14 |
| bauzas | gunicorn seems indeed a good competitor, but before rushing into a conclusion, I'd just hope that we would arrive to some agreement before | 10:15 |
| noonedeadpunk | But yes, uwsgi migration was not really neat and it still having it's issues in some projects | 10:15 |
| bauzas | which can be : | 10:15 |
| bauzas | 1/ say this isn't a problem and leave as it is | 10:16 |
| noonedeadpunk | And yeah, I'm not sure why uwsgi was picked at the first place as it always had awful performance | 10:16 |
| bauzas | 2/ consider uswgi critical to the projects and then take the maintainance burden on our shoulders | 10:16 |
| bauzas | 3/ identify some other competitor where benefits overweight the migration and then do a migration plan | 10:17 |
| bauzas | I don't know yet which of the three options seems the best :) | 10:17 |
| noonedeadpunk | Eventually, I assume that most of services that are run with uwsgi should not be an issue to migrate, as it's kind of standard? | 10:18 |
| bauzas | so the goal I was referring to was the cross-project effort of talking to each others and do the decision :;) | 10:18 |
| noonedeadpunk | I don't like second for sure :) | 10:18 |
| bauzas | we had precedents of projects we took under our umbrella | 10:18 |
| noonedeadpunk | But yeah, I totally agree with you here | 10:18 |
| noonedeadpunk | Well, I'm not feeling we have resources for that? | 10:19 |
| noonedeadpunk | I might be wrong though | 10:19 |
| bauzas | good call | 10:19 |
| bauzas | which can't be answered until we have this epiphanic brainstorm | 10:19 |
| noonedeadpunk | Which is likely more a PTG thing | 10:20 |
| noonedeadpunk | We likely can easily postpone that even to in-person PTG | 10:20 |
| noonedeadpunk | uwsgi is in this state for a year already and they had even a bugfix release during that period | 10:21 |
| noonedeadpunk | So it's not really urgent thing, but I'd prefer coming out with plan at least of what we're gonna do | 10:21 |
| bauzas | and we are on a non-slurp release, remember ;) | 10:22 |
| noonedeadpunk | As for deployment projects or packagers it would be tricky to do last minute changes | 10:22 |
| bauzas | that's a lovely timing for a preparatory work, not a migration | 10:22 |
| bauzas | despite I don't know how much of the slurpriness is tied devstack | 10:22 |
| noonedeadpunk | To be frank I still need couple of minutes to think when changes should be made not to ruin everything | 10:23 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/governance master: Exclusive management of projects by openstackci https://review.opendev.org/c/openstack/governance/+/874787 | 10:58 |
| coreycb | hello tc, I have a question on stable branch naming for 2023.1 antelope. would a deployment project such as the charms be required to switch to stable/2023.1 or could the project stick with stable/antelope if they chose to? | 16:05 |
| fungi | i can't speak to tc policy, but zuul looks for matching branch names across projects when integrating them in jobs, so for example constraints lists from the requirements repo won't be applied correctly without some additional manual mapping in job definitions | 16:16 |
| coreycb | fungi: that's a good point, thanks for sharing | 16:17 |
| gmann | coreycb: we need to be consistent across all the OpenStack projects with stable/2023.1. Not just from zuul perspective but also user/developers and many other tooling also. | 18:25 |
| gmann | ralonsoh: yes please. QA team has done that and finish the cleanup. | 18:26 |
| coreycb | gmann: ok, I'll relay this back to the rest of the tam. thanks for getting back to me. | 18:30 |
| gmann | +1. thanks | 18:31 |
| opendevreview | Merged openstack/governance master: Define 2023 upstream investment opportunities https://review.opendev.org/c/openstack/governance/+/872233 | 19:05 |
| opendevreview | Ghanshyam proposed openstack/governance master: Adding mailto link in upstream opportunities doc https://review.opendev.org/c/openstack/governance/+/874968 | 22:55 |
| opendevreview | Ghanshyam proposed openstack/governance master: Appoint Liu as Senlin PTL https://review.opendev.org/c/openstack/governance/+/874969 | 23:10 |
| opendevreview | Ian Y. Choi proposed openstack/election master: Bobcat Election Results (TC/PTL) https://review.opendev.org/c/openstack/election/+/874970 | 23:19 |
| opendevreview | Ghanshyam proposed openstack/governance master: Appoint Felipe Reyes as OpenStack_Charms PTL https://review.opendev.org/c/openstack/governance/+/874971 | 23:20 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!