| opendevreview | chenker proposed openstack/governance master: Appoint Ke Chen as PTL for Watcher https://review.opendev.org/c/openstack/governance/+/932419 | 14:23 |
|---|---|---|
| opendevreview | chenker proposed openstack/governance master: Appoint Ke Chen as PTL for Watcher https://review.opendev.org/c/openstack/governance/+/932419 | 14:27 |
| *** bauzas_ is now known as bauzas | 15:24 | |
| bauzas | reminder: nova meeting in 12 mins here | 15:48 |
| bauzas | #startmeeting nova | 16:00 |
| opendevmeet | Meeting started Tue Oct 15 16:00:34 2024 UTC and is due to finish in 60 minutes. The chair is bauzas. Information about MeetBot at http://wiki.debian.org/MeetBot. | 16:00 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 16:00 |
| opendevmeet | The meeting name has been set to 'nova' | 16:00 |
| bauzas | hey folks | 16:00 |
| bauzas | #link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting | 16:00 |
| bauzas | who's around ? | 16:00 |
| bauzas | tick tock | 16:01 |
| bauzas | oh shit | 16:02 |
| bauzas | wrong chan | 16:02 |
| * bauzas facepalms | 16:02 | |
| bauzas | #undo | 16:02 |
| opendevmeet | Removing item from minutes: #link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting | 16:02 |
| bauzas | #undo | 16:02 |
| bauzas | #endmeeting | 16:02 |
| opendevmeet | Meeting ended Tue Oct 15 16:02:57 2024 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:02 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/nova/2024/nova.2024-10-15-16.00.html | 16:02 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/nova/2024/nova.2024-10-15-16.00.txt | 16:02 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/nova/2024/nova.2024-10-15-16.00.log.html | 16:02 |
| noonedeadpunk | :D | 16:04 |
| noonedeadpunk | yeah, too early :D | 16:05 |
| bauzas | nah, rather too late for our nova meeting :) | 16:16 |
| bauzas | one IRC chan to rule them all, mwahahaha | 16:16 |
| * gouthamr thought this was a takeover attempt in his absence | 17:00 | |
| noonedeadpunk | tc-members: gentle reminder that we're meeting here in an hour | 17:02 |
| gmann | tc-members: kuryr-kubernetes and its tempest plugin are ready to retired now https://review.opendev.org/c/openstack/kuryr-kubernetes/+/923074 https://review.opendev.org/c/openstack/governance/+/922507 | 17:27 |
| noonedeadpunk | #startmeeting tc | 18:00 |
| opendevmeet | Meeting started Tue Oct 15 18:00:22 2024 UTC and is due to finish in 60 minutes. The chair is noonedeadpunk. Information about MeetBot at http://wiki.debian.org/MeetBot. | 18:00 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 18:00 |
| opendevmeet | The meeting name has been set to 'tc' | 18:00 |
| noonedeadpunk | Welcome to the weekly meeting of the OpenStack Technical Committee. A reminder that this meeting is held under the OpenInfra Code of Conduct available at https://openinfra.dev/legal/code-of-conduct. | 18:00 |
| noonedeadpunk | #topic Roll Call | 18:00 |
| noonedeadpunk | o/ | 18:00 |
| noonedeadpunk | #chair gouthamr | 18:00 |
| opendevmeet | Current chairs: gouthamr noonedeadpunk | 18:00 |
| bauzas | o/ | 18:01 |
| gmann | o/ | 18:01 |
| cardoe | \o | 18:01 |
| noonedeadpunk | there're 3 absences that are on a record | 18:02 |
| slaweq | hi, do we have meeting today? | 18:03 |
| noonedeadpunk | we do if we get qourum and right now on a rollcall :) | 18:03 |
| slaweq | ahh, ok, sorry for being late | 18:04 |
| gmann | you are on right time :) | 18:04 |
| noonedeadpunk | gtema seems to be not on the channel | 18:04 |
| noonedeadpunk | but we have 5 ppl in there, so technically - it's a quorum | 18:05 |
| bauzas | when will be the DST for the US ? | 18:05 |
| bauzas | this weekend ? | 18:05 |
| gmann | Nov 3rd | 18:05 |
| noonedeadpunk | I was thinking about next one though | 18:05 |
| noonedeadpunk | but yeah | 18:06 |
| gtema | Hey, I am on PTO this unavailable | 18:06 |
| noonedeadpunk | ack | 18:06 |
| cardoe | So no quorum then? | 18:06 |
| bauzas | gmann: ack | 18:06 |
| noonedeadpunk | we have 5 ppl exactly | 18:06 |
| gmann | yeah, we have quorum | 18:07 |
| noonedeadpunk | given slaweq has checked in :) | 18:07 |
| noonedeadpunk | #topic Last Week's AIs | 18:07 |
| noonedeadpunk | first action point was on gmann regarding proposing changes to increase coverage for requirements | 18:07 |
| noonedeadpunk | any updates on this one? | 18:08 |
| gmann | I proposed it but there are soem failure regarding quota which I need to debug | 18:08 |
| gmann | #link https://review.opendev.org/c/openstack/python-openstackclient/+/931858 | 18:08 |
| gmann | need to check if those are related to adding new jobs or something else | 18:08 |
| gmann | this is for osc, I still need to add greande job for requirement though | 18:09 |
| noonedeadpunk | it does not look intermitent to me right now | 18:09 |
| noonedeadpunk | as failures are exactly same in 2 jobs | 18:10 |
| gmann | yeah, maybe some race on quota tests from multiple jobs but need to debug it | 18:10 |
| noonedeadpunk | yeah, ok, but patch is around, which is good. | 18:11 |
| noonedeadpunk | going next | 18:11 |
| noonedeadpunk | gouthamr needed to confirm PTG sessions for TC. | 18:12 |
| noonedeadpunk | and this has been done and written down in etherpad | 18:12 |
| noonedeadpunk | PTG is a topic on itself, so let's get the ball rolling | 18:12 |
| noonedeadpunk | #topic TC PTG | 18:12 |
| noonedeadpunk | there are 2 sessions which were booked | 18:13 |
| noonedeadpunk | #link https://etherpad.opendev.org/p/oct2024-ptg-os-tc | 18:13 |
| noonedeadpunk | So we do have a session on Monday, Oct 21 from 14UTC to 16 UTC | 18:14 |
| noonedeadpunk | I believe this is designated for interaction with community and other projects | 18:14 |
| * bauzas notes | 18:14 | |
| noonedeadpunk | And then also Friday, Oct 18 from 15 to 16 UTC to sum-up passed PTG | 18:15 |
| noonedeadpunk | ptg schedule is available as usual at | 18:15 |
| noonedeadpunk | #link https://ptg.opendev.org/ptg.html | 18:15 |
| gmann | Oct 18 15 to 17 UTC , 2 hrs right? | 18:15 |
| gmann | got it. ++ | 18:15 |
| noonedeadpunk | Oh, yes, sorry | 18:15 |
| bauzas | that's what I can see indeed | 18:15 |
| noonedeadpunk | my bad, I was metioning slots :D | 18:16 |
| noonedeadpunk | correcting myself | 18:16 |
| noonedeadpunk | Monday, Oct 21 from 14UTC to 17 UTC | 18:16 |
| noonedeadpunk | Friday, Oct 18 from 15 to 17 UTC | 18:16 |
| noonedeadpunk | also correct timing was mentioned in etherpad linked above | 18:17 |
| noonedeadpunk | thanks for correcting gmann | 18:17 |
| noonedeadpunk | With that I think we should also cancel our regular IRC meeting on Tuesday next week | 18:17 |
| slaweq | ++ | 18:18 |
| gmann | ++ | 18:18 |
| noonedeadpunk | should I create a poll for that or... | 18:18 |
| gmann | I do not think we need poll, you can just ask if any objection | 18:18 |
| bauzas | ++ | 18:19 |
| noonedeadpunk | ok, I assume no objections here then. | 18:20 |
| noonedeadpunk | I will send an email with notification about IRC meeting being cancelled next week | 18:20 |
| noonedeadpunk | #topic Leaderless projects | 18:21 |
| noonedeadpunk | First - Watcher. | 18:22 |
| noonedeadpunk | I see they have pushed a patch as was discussed in a ML | 18:22 |
| noonedeadpunk | #link https://review.opendev.org/c/openstack/governance/+/932419 | 18:22 |
| bauzas | thanks gmann for the review | 18:23 |
| noonedeadpunk | it's quite a new one - was pushed just today. | 18:23 |
| noonedeadpunk | ++ thanks indeed! | 18:23 |
| noonedeadpunk | a good catch | 18:24 |
| gmann | I hope they are planning for PTG also and not blocked due to PTL appointment | 18:24 |
| noonedeadpunk | And next project is Mistral, we still did not got any response in the patch | 18:24 |
| noonedeadpunk | #link https://review.opendev.org/c/openstack/governance/+/927962 | 18:24 |
| noonedeadpunk | I think it was on me to write a ML to brng attention in case they've missed comments | 18:25 |
| noonedeadpunk | but failed so far :( | 18:25 |
| gmann | I think there was one email about it | 18:26 |
| noonedeadpunk | #action noonedeadpunk to write email about Mistral PTL appointment patch needing attention | 18:26 |
| bauzas | ack | 18:26 |
| noonedeadpunk | yeah, but it was before appointment patch | 18:26 |
| gmann | ohk, I see | 18:26 |
| noonedeadpunk | I will bump the thread | 18:26 |
| noonedeadpunk | iirc | 18:26 |
| gmann | ++ thanks | 18:26 |
| noonedeadpunk | #topic A check on gate health | 18:27 |
| noonedeadpunk | Anything on that?:) | 18:27 |
| gmann | for greande things, enabling global venv there and there are few project failing(catching at least for projects we have job in grenade gate) | 18:28 |
| gmann | #link https://review.opendev.org/c/openstack/grenade/+/930507/12 | 18:28 |
| gmann | octavia is fixed but ironic, heat jobs failing | 18:28 |
| cardoe | I believe JayF | 18:29 |
| gmann | I am getting less time to debug it last and this week but I will continue on this | 18:29 |
| cardoe | typing fail... I believe JayF had some patches pending for that for Ironic | 18:29 |
| gmann | ohk, I will check | 18:29 |
| JayF | Ironic has not supported global venv, ever | 18:29 |
| JayF | I had a patch up to support that among a fix for other things | 18:29 |
| gmann | #link https://review.opendev.org/c/openstack/ironic/+/932016 | 18:29 |
| gmann | this is change i have up but we need more change i think | 18:29 |
| JayF | er, whatever the change is, the per-proj-venv | 18:30 |
| gmann | k | 18:30 |
| gmann | #link https://review.opendev.org/c/openstack/ironic/+/930776 | 18:30 |
| gmann | JayF: ^^ this one? | 18:30 |
| JayF | yeah, I'm trying to do two things at once with that, one of them is the piece you care about :D | 18:31 |
| gmann | yeah, can you split those so that we can proceed for the grenade things | 18:32 |
| JayF | I'm more wondering how, in the future, this can be planned as a migration to let folks know so it's not an emergency for ironic | 18:32 |
| JayF | it's only a coincidence I had this half-done | 18:32 |
| JayF | Did I miss a post to the mailing list about the change in grenade? | 18:33 |
| gmann | I have not posted yet as I wanted to see existing jobs passing first and let other project if they are impacted | 18:33 |
| gmann | this is needed because greande current master setting were failing | 18:33 |
| gmann | #link https://review.opendev.org/c/openstack/grenade/+/932017/1 | 18:34 |
| bauzas | yeah this is explained in the commit msg | 18:34 |
| gmann | and moving to venv is the one we need as first | 18:34 |
| bauzas | now devstack defaults to a global venv | 18:34 |
| gmann | yes | 18:34 |
| JayF | My question is simply how/when was that going to be communicated to other teams? | 18:34 |
| JayF | Is this that communication? | 18:35 |
| bauzas | I'd say projects need some liaison | 18:35 |
| gmann | I will post on ML soon but I am waiting if octavia, ironic, heat can be fixed and we know how fixes looks like which can be used a ref to other projects | 18:35 |
| cardoe | I think we should have at least had a ML announcement. | 18:35 |
| JayF | That's basically ^ all I'm asking for, with a week or two heads up | 18:36 |
| cardoe | What if the effort to change Ironic was large an invasive and took months to complete? | 18:36 |
| gmann | it was in draft state and experimental to know how things working | 18:36 |
| gmann | cardoe: is this that big change to ironic ? | 18:36 |
| JayF | I'm happy to fix and understand this may not be the first domino in the chain of events, I just feel like the teacher is asking for us to turn in homework that was never assigned :D | 18:37 |
| gmann | anyways I think I can post it on ML if that is blocking the ironic change to proceed | 18:37 |
| cardoe | It's not blocking the change to proceed. But it's certainly not been on our radar to work on it or try to review these items. | 18:37 |
| JayF | I'm saying I would prefer a post to the mailing list so it doesn't instantly fall to the one or two Ironic contributors who pay attention to the TC meeting :) | 18:37 |
| gmann | that is easy and less time consuming than explaining about importance of change to merge | 18:37 |
| gmann | well, I was not finished the change yet that is why did not ask for review #link https://review.opendev.org/c/openstack/ironic/+/932016 | 18:38 |
| gmann | anyways I will post it on ML | 18:39 |
| cardoe | Just asking in the future post something so there's awareness. I'll try to prioritize it in the coming week. | 18:39 |
| JayF | 016 is passing grenade, the failure is apparently unrelated | 18:39 |
| JayF | I'll also split the global venv part of my ironic change; that should be easy enough | 18:40 |
| cardoe | I added gmann's change to the weekly prio. | 18:41 |
| noonedeadpunk | ok, I think we've done with the topic for now | 18:43 |
| noonedeadpunk | moving next | 18:43 |
| noonedeadpunk | #topic TC Tracker | 18:43 |
| noonedeadpunk | we do have an etherpad with topics which I believe we also gonna raise during the ptg | 18:44 |
| noonedeadpunk | #link https://review.opendev.org/c/openstack/neutron/+/931495 | 18:44 |
| noonedeadpunk | oops, wrong link :) | 18:45 |
| noonedeadpunk | #link https://etherpad.opendev.org/p/tc-2025.1-tracker | 18:45 |
| bauzas | heh | 18:45 |
| bauzas | at least you sent it to the right channel :p | 18:45 |
| noonedeadpunk | hehe | 18:45 |
| gmann | :) | 18:45 |
| noonedeadpunk | it was wrong buffer eventually | 18:45 |
| noonedeadpunk | I don't have much input on TC tracker topic to be frank | 18:46 |
| bauzas | given the outcome of the i18n session, I could lead a tracker for the translations | 18:46 |
| noonedeadpunk | ++ that would be much appreciated | 18:47 |
| noonedeadpunk | I am also quite interested in translations activity, though lacking time dramatically to catch up with it | 18:48 |
| bauzas | ditto here, but if I can help, I'll do it :) | 18:49 |
| noonedeadpunk | And I'm very lost where we are with tooling migration and if it's actually a blocker for onboarding new ppl or not | 18:50 |
| cardoe | I'm not sure what's left to discuss on tracker? | 18:50 |
| noonedeadpunk | #topic open discussion | 18:50 |
| noonedeadpunk | we have around 10 minutes to raise smth that wasn't in agenda | 18:51 |
| cardoe | I have two semi-related items if no one else has any open items. | 18:51 |
| noonedeadpunk | go on I guess :) | 18:51 |
| bauzas | shoot | 18:51 |
| cardoe | So the first is around release blobs. clarkb will probably be better able to express this. At least I think it was clarkb was talking about it. | 18:52 |
| cardoe | We've got two projects building container images and as such what's our support policy around those. Or even security posture. | 18:53 |
| cardoe | If the underlying OS distro has a CVE for that what does that mean to rebuilding the container. | 18:53 |
| noonedeadpunk | well, it's a good one, as eventually what I recall, projects officially produce only pip packages | 18:54 |
| cardoe | It dovetails a little bit into releases being on PyPi because you could arguably "pip install nova" but that's not a recommended approach. | 18:54 |
| noonedeadpunk | I personally do not also agree about ^ but I'm in minority here obviously | 18:54 |
| cardoe | Well there's more than Python projects though. There's kolla which is building containers and loci. | 18:54 |
| cardoe | You do not agree with which part? | 18:55 |
| bauzas | not sure I understand the concern with release blobs | 18:55 |
| noonedeadpunk | that "pip install nova" should not be recommended. as that's the only thing that nova officially delivers/produces | 18:55 |
| noonedeadpunk | Well, again, I would assume, that kolla does build certain layers only? | 18:56 |
| noonedeadpunk | as layering of container images is actually the way to distribute responsibility for CVE's, isn't it? | 18:57 |
| cardoe | They build the layers atop an existing OS image and then publish those containers with Zuul to Docker Hub under the OpenStack name. | 18:57 |
| noonedeadpunk | so when you're pulling image it should consist of plenty things, right? | 18:58 |
| bauzas | https://docs.openstack.org/nova/latest/contributor/project-scope.html#deployment-and-packaging if that helps to understand the nova deliverables | 18:58 |
| cardoe | My comments are around the fact that if there is no security promise or effort to maintain this, there's no such clear policy in the places it's published. So the OpenStack name / brand is out there and associated with insecure published containers. | 18:58 |
| noonedeadpunk | bauzas: I think you still package Nova as python package? | 18:58 |
| bauzas | well, | 18:59 |
| bauzas | our deliverable is technically a git commit | 18:59 |
| cardoe | So that's the case for the nova project, bauzas. But kolla is taking nova and publishing a nova container under the OpenStack banner. | 18:59 |
| bauzas | then the release management team ships it into a python build that's sent to pypi fwiw | 18:59 |
| cardoe | Similarly for loci. | 18:59 |
| noonedeadpunk | so you don't care about setup.py or pyproject.toml? | 18:59 |
| bauzas | noonedeadpunk: see the above link I sent | 19:00 |
| bauzas | we care about the CI | 19:00 |
| bauzas | how nova is productized out of the blue is not in our scope | 19:00 |
| bauzas | (upstream for sure) | 19:00 |
| cardoe | It's not the nova project's scope, which is fine. | 19:01 |
| cardoe | But I'm talking about an official OpenStack project that then further packages it. | 19:01 |
| noonedeadpunk | it's veeery vague border.... so like - for CI you can copy/paste content under /usr/lib/python3/site-packages technically/// | 19:01 |
| bauzas | okay, so we're talking of deployment services | 19:01 |
| bauzas | not service projects | 19:01 |
| bauzas | I just wanted to clarify the scope of that discussion | 19:01 |
| noonedeadpunk | cardoe: yeah, that is a very good point. I somehow thought though ,that containers layers could be updated separately from each other | 19:01 |
| noonedeadpunk | so if published container image is layered, kolla should be responsible only for their thing | 19:02 |
| noonedeadpunk | not for underlying ones they depend on | 19:02 |
| noonedeadpunk | oops, and we are overtime. | 19:02 |
| cardoe | layers are like git commits. They depend on the layer under them. | 19:02 |
| noonedeadpunk | I suggest to add that discussion to the PTG, as it is totally a valid one from my prespective | 19:02 |
| noonedeadpunk | #endmeeting | 19:03 |
| opendevmeet | Meeting ended Tue Oct 15 19:03:07 2024 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 19:03 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/tc/2024/tc.2024-10-15-18.00.html | 19:03 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/tc/2024/tc.2024-10-15-18.00.txt | 19:03 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/tc/2024/tc.2024-10-15-18.00.log.html | 19:03 |
| slaweq | o/ | 19:03 |
| noonedeadpunk | good morning :) | 19:03 |
| bauzas | thanks | 19:03 |
| noonedeadpunk | thanks everyone for attending! | 19:03 |
| gmann | quick one to review kuryr-kubernetes repo content removal https://review.opendev.org/q/topic:%22retire-kuryr-kubernetes%22+status:open | 19:04 |
| gmann | if 2nd reviewer can check and merge it and we can proceed on governance change | 19:04 |
| gmann | thanks | 19:04 |
| noonedeadpunk | done | 19:05 |
| cardoe | do it again :( | 19:06 |
| gmann | thanks again | 19:06 |
| noonedeadpunk | cardoe: ok, yeah, I was somehow under full impression that it's way easier to swap update container as interally was promoted a lot some way of doing so. But reading docs now, I feel being wrong | 19:09 |
| cardoe | So the two projects provide scripts to repackage your own. | 19:09 |
| noonedeadpunk | eventually, I think we have kinda simmilar thing with ansible collections and terraform provider | 19:10 |
| cardoe | Unfortunately loci/openstack-helm-images has some hardcoded IPs and docker configuration that's locked away in some openinfra zuul magic repo and makes doing so impossible. | 19:10 |
| noonedeadpunk | where thinkgs being published under openstack name as a SIG | 19:10 |
| cardoe | So ya either use the provided ones or write your own build mechanism like vexxhost has. | 19:11 |
| cardoe | Which interestingly uses zuul. | 19:11 |
| noonedeadpunk | which does fall of governance, and openstack-infra does not have access to these namespaces, afaik | 19:11 |
| noonedeadpunk | they are managed by indviduals who are member of sig | 19:12 |
| cardoe | But my concern here is that things are published at https://tarballs.openstack.org or docker hub or quay (the later two using the OpenStack logo) | 19:12 |
| cardoe | So it seems "semi-official" | 19:12 |
| noonedeadpunk | only https://tarballs.openstack.org does kinda | 19:12 |
| noonedeadpunk | docker hub or quay for me very much alike to galaxy.ansible.com | 19:13 |
| cardoe | To a random person on the street who Google searches "OpenStack nova container" and lands at Docker Hub or Quay at an Organization called "OpenStack" with the official OpenStack logo.... that's going to seem official to them. | 19:13 |
| noonedeadpunk | I'm not saying you're wrong | 19:14 |
| cardoe | And when they have a bad experience with it. They're gonna say "openstack sucks!" | 19:14 |
| noonedeadpunk | I'm not sure there's a good solution to that though. Except to move ready images publishing to some kind of SIG | 19:15 |
| noonedeadpunk | or be more explicit that OpenStack owns only things on pypi.org which would also corner any rust initiatives, for instance | 19:16 |
| cardoe | We've got an official Rust initiative? | 19:17 |
| noonedeadpunk | there're talks around client-side of things at least | 19:17 |
| cardoe | I'd certainly be interested if you know those folks. | 19:18 |
| noonedeadpunk | you should talk to gtema then | 19:18 |
| cardoe | My other topic was around projects that use tooling but give off bad user experiences because they fly in the face of those tools best practices or common conventions. | 19:21 |
| cardoe | So interestingly crates.io has "openstack" and "openstack_sdk". The former is owned by dtantsur and the later is owned by gtema. Unfortunate there was no collaboration to have just 1. | 19:22 |
| noonedeadpunk | "bad user experiences" can be hardly measured, imo. and "best practices or common conventions" are usually unrelated to UX, as end-users hardly care about backend style practises | 19:23 |
| noonedeadpunk | and neither of them are official despite having `openstack` on them | 19:24 |
| cardoe | Not saying they're official just making a note of the possible collab miss. | 19:25 |
| noonedeadpunk | I kinda wonder what olso-policy is there for | 19:26 |
| cardoe | My tooling best practices comment can be best summed up by a project making a release 0.3.16 back in July and publishing it to tarballs.openstack.org But that depends on a number of other dependencies, some are internal to the project (living in other repos on opendev.org). It turns out that the release is rebuilt on every commit to the child dependencies as well. That rebuilt package then overwrites the tarball. | 19:26 |
| cardoe | The result is a change in any of the child dependencies gets rolled out into the latest release. | 19:27 |
| cardoe | The response to the bug? The PTL tells you the project is a framework. If you care about stable releases then you should build them yourselves. | 19:27 |
| cardoe | But that's once again not expressed in the project's documentation. | 19:28 |
| cardoe | And all the docs suggest using tarballs.openstack.org | 19:28 |
| noonedeadpunk | My personal prespective on that is such kind of things are to be sorted with the project | 19:28 |
| noonedeadpunk | And that's why there're elections of PTLs | 19:29 |
| noonedeadpunk | So I guess I would try to communicate with the community around the project and raise their awareness as well. And propose changes to approaches, or run for PTL of that's in my direct zone of interest. | 19:32 |
| gouthamr | noonedeadpunk++ thank you for chairing :) | 19:37 |
| noonedeadpunk | gouthamr did amazing job of prepearing everything, so it was a pleasure | 19:37 |
| *** elodilles is now known as elodilles_pto | 19:41 | |
| spotz[m] | Shoot forgot to put me as absent as I’m at NA | 20:31 |
| *** bauzas_ is now known as bauzas | 21:51 | |
| *** bauzas- is now known as bauzas | 22:04 | |
| *** bauzas- is now known as bauzas | 22:12 | |
| *** bauzas_ is now known as bauzas | 23:33 | |
| *** bauzas_ is now known as bauzas | 23:44 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!