<@jnsamyak:matrix.org>
16:00:26
!startmeeting RELENG (2024-08-20)
<@meetbot:fedora.im>
16:00:28
Meeting started at 2024-08-20 16:00:26 UTC
<@meetbot:fedora.im>
16:00:29
The Meeting name is 'RELENG (2024-08-20)'
<@jnsamyak:matrix.org>
16:00:35
!info agenda is at https://hackmd.io/vm6biLBcTYKtkQUH5kQkmw
<@jnsamyak:matrix.org>
16:00:35
!meetingname releng
<@jnsamyak:matrix.org>
16:00:35
!chair nirik jednorozec jnsamyak patrikp
<@jnsamyak:matrix.org>
16:00:35
!info Meeting is 60 minutes MAX. At the end of 60, it stops
<@jnsamyak:matrix.org>
16:00:35
!topic init process
<@meetbot:fedora.im>
16:00:36
The Meeting Name is now releng
<@jnsamyak:matrix.org>
16:00:53
Hello folks, how's everyone doing?
<@nirik:matrix.scrye.com>
16:01:00
morning
<@jnsamyak:matrix.org>
16:01:07
Do we have anything for the init? Any blockers, tasks, issues, requests, features that needs releng intervention?
<@nirik:matrix.scrye.com>
16:01:48
not likely for init process, but we should talk about branching and tweaks to the sop/process... overall I think things went much smoother this time, but still a few small things...
<@patrikp:matrix.org>
16:02:15
I had one thing related to the infra & releng hackfest from Flock, not sure if it's best to bring it up now or open floor.
<@jnsamyak:matrix.org>
16:02:20
yes i want to cover that in the next topic
<@jnsamyak:matrix.org>
16:02:44
the release item, so we can move on to that one i guess
<@patrikp:matrix.org>
16:03:07
So now?
<@patrikp:matrix.org>
16:03:17
https://discussion.fedoraproject.org/t/report-from-infra-and-releng-hackfest-at-flock2024/128743
<@patrikp:matrix.org>
16:03:17
Link for reference:
<@jnsamyak:matrix.org>
16:03:36
Go ahead patrikp
<@patrikp:matrix.org>
16:03:55
OpenShift apps deployment info – Did a quick tutorial on how we deploy apps for all those present. Should be folded into the docs above.
<@patrikp:matrix.org>
16:03:55
“Discuss onboarding, what we can do to make it better” – we had a pretty nice discussion on this one, including some folks that are not involved right now with some great perspectives.
<@patrikp:matrix.org>
16:03:55
ACTION: kevin to post outline of docs changes and submit WIP PR for them for people to add to.
<@patrikp:matrix.org>
16:03:55
ACTION: after docs are in better shape, look at marketing to potential contributors
<@patrikp:matrix.org>
16:03:55
ACTION: after each release look at having a ‘Hello’ day where new folks can join and ask questions and learn about the setup.
<@patrikp:matrix.org>
16:03:55
<@patrikp:matrix.org>
16:03:55
I was wondering if Kevin could expand on that a little bit. Were the Server Group folks present as well?
<@nirik:matrix.scrye.com>
16:04:21
on onboarding?
<@patrikp:matrix.org>
16:04:47
It's an open question I suppose. What interests me specifically is:
<@patrikp:matrix.org>
16:04:47
ACTION: kevin to post outline of docs changes and submit WIP PR for them for people to add to.
<@nirik:matrix.scrye.com>
16:05:36
yeah, I need to finish writing that up. Basically we had a outline we made from the flock last year... some things were added/fixed up already, but there's more documents to write up.
<@nirik:matrix.scrye.com>
16:05:54
Also I have some things in progress that I can submit as pr's and get feedback on.
<@nirik:matrix.scrye.com>
16:06:19
I'd like to sync out what I have and stop being a blocker on moving forward with it. ;)
<@patrikp:matrix.org>
16:06:45
So it's a series of separate SOPs? Like a doc revamp?
<@nirik:matrix.scrye.com>
16:07:05
it's revamping our docs.fedoraproject.org infra & releng space...
<@nirik:matrix.scrye.com>
16:07:17
like changing the structure and expanding a bunch for new folks.
<@patrikp:matrix.org>
16:08:04
Sounds great. Reason I was asking about the Server folks was that they want to do the distribution media renaming and it was said in one of their meetings that you would discuss in person at Flock.
<@nirik:matrix.scrye.com>
16:08:10
so we have a nicer, more written out structure for people joining
<@jnsamyak:matrix.org>
16:08:28
that's the goal!
<@nirik:matrix.scrye.com>
16:08:30
ah, sadly I didn't sync up with any of them... too much else going on. ;(
<@patrikp:matrix.org>
16:08:36
Understood!
<@nirik:matrix.scrye.com>
16:08:44
jednorozec may have? not sure.
<@jnsamyak:matrix.org>
16:09:44
Okay then, let's move on to the next item?
<@jnsamyak:matrix.org>
16:10:50
!info Here we list/discuss anything about items that are due to be done in the next week
<@jnsamyak:matrix.org>
16:10:50
!topic scheduled actions coming up in the next week
<@jnsamyak:matrix.org>
16:10:57
<@jnsamyak:matrix.org>
16:11:09
Let's do a quick branching retro first
<@jnsamyak:matrix.org>
16:11:14
!releng 12241
<@zodbot:fedora.im>
16:11:15
● **Opened:** a week ago by jnsamyak
<@zodbot:fedora.im>
16:11:15
● **Assignee:** jnsamyak
<@zodbot:fedora.im>
16:11:15
● **Last Updated:** a week ago
<@zodbot:fedora.im>
16:11:15
**releng #12241** (https://pagure.io/releng/issue/12241):**Fedora 41 Mass Branching Tracker **
<@zodbot:fedora.im>
16:11:15
<@jnsamyak:matrix.org>
16:11:22
I think like last night if we can add notes on the things we missed can lead to a better branching documentation for next time
<@nirik:matrix.scrye.com>
16:11:26
we may want to change that link to https://fedorapeople.org/groups/schedule/f-41/f-41-releng-tasks.html (just as an aside)
<@jnsamyak:matrix.org>
16:11:39
!undo
<@jnsamyak:matrix.org>
16:11:48
idk if that works?
<@jnsamyak:matrix.org>
16:11:50
no
<@nirik:matrix.scrye.com>
16:11:55
it doesn't. ;)
<@jnsamyak:matrix.org>
16:11:58
but I'll change the template
<@nirik:matrix.scrye.com>
16:12:12
yeah, I was going to ask where you wanted issues from branching. I should have been better about adding them as I saw them
<@jnsamyak:matrix.org>
16:12:41
- add rawhide defination and new keys to all the stable fedora-repos
<@jnsamyak:matrix.org>
16:12:41
- creation of new bugzilla component is missing from the docs
<@jnsamyak:matrix.org>
16:12:41
- use of custom ip for external folks
<@jnsamyak:matrix.org>
16:12:57
nirik: like last time the same ticket?
<@nirik:matrix.scrye.com>
16:13:03
One I noticed a while ago but didn't note anywhere yet:
<@jnsamyak:matrix.org>
16:13:08
So we can close this tracker once we have this issues fixed
<@nirik:matrix.scrye.com>
16:13:49
fedora-repos was updated to point to rawhide key and f43 key. Thats not right, it should keep pointing to the previous key until we make the next one (f44) and then we can point it to also f43...
<@nirik:matrix.scrye.com>
16:14:13
ie, we want it to point to rawhide and the previous one so things signed with the old key keep working
<@nirik:matrix.scrye.com>
16:14:23
(at least around branching time)
<@jnsamyak:matrix.org>
16:14:45
i think peter introduced a fix for that
<@jnsamyak:matrix.org>
16:14:47
let me check
<@jnsamyak:matrix.org>
16:14:59
<@nirik:matrix.scrye.com>
16:15:41
I saw that, but I am not sure I like it.
<@jnsamyak:matrix.org>
16:15:44
- use of custom ip for blocking external folks
<@jnsamyak:matrix.org>
16:15:44
- add rawhide defination and new keys to all the stable fedora-repos
<@jnsamyak:matrix.org>
16:15:44
- creation of new bugzilla component is missing from the docs
<@nirik:matrix.scrye.com>
16:15:51
but I haven't looked in depth yet
<@jnsamyak:matrix.org>
16:15:53
- add rawhide defination and new keys to all the stable fedora-repos
<@jnsamyak:matrix.org>
16:15:53
- creation of new bugzilla component is missing from the docs
<@jnsamyak:matrix.org>
16:15:53
- use of custom ip for blocking external folks to submit builds in koji
<@jnsamyak:matrix.org>
16:16:14
okay we can discuss about this more in the pr
<@nirik:matrix.scrye.com>
16:16:37
that looks like it may go to far... but again, I need to wrap my head around it.
<@nirik:matrix.scrye.com>
16:16:50
yeah, if we could hold off merging that for a bit that would be great
<@jnsamyak:matrix.org>
16:18:05
awesome i added a comment
<@jnsamyak:matrix.org>
16:18:07
for that
<@jnsamyak:matrix.org>
16:18:54
regarding branching, i did this cleanup as well
<@jnsamyak:matrix.org>
16:18:59
!releng 12257
<@zodbot:fedora.im>
16:19:00
● **Closed: Fixed** 4 days ago by jnsamyak
<@zodbot:fedora.im>
16:19:00
<@zodbot:fedora.im>
16:19:00
**releng #12257** (https://pagure.io/releng/issue/12257):**make-release-tag (koji script) needs update**
<@zodbot:fedora.im>
16:19:00
● **Assignee:** jnsamyak
<@zodbot:fedora.im>
16:19:00
● **Last Updated:** 4 days ago
<@zodbot:fedora.im>
16:19:00
● **Opened:** 6 days ago by jnsamyak
<@jnsamyak:matrix.org>
16:19:17
yes one more thing
<@jnsamyak:matrix.org>
16:20:04
!releng 122545
<@zodbot:fedora.im>
16:20:05
Issue querying Pagure: Issue not found
<@jnsamyak:matrix.org>
16:20:08
!releng 12255
<@zodbot:fedora.im>
16:20:09
**releng #12255** (https://pagure.io/releng/issue/12255):**kojipkgs.fedoraproject.org/repos/rawhide/latest points to f41-build tag**
<@zodbot:fedora.im>
16:20:09
<@zodbot:fedora.im>
16:20:09
● **Closed: Fixed with Explanation** 6 days ago by kevin
<@zodbot:fedora.im>
16:20:09
● **Opened:** 6 days ago by churchyard
<@zodbot:fedora.im>
16:20:09
● **Last Updated:** 6 days ago
<@zodbot:fedora.im>
16:20:09
● **Assignee:** kevin
<@jnsamyak:matrix.org>
16:20:25
We need to make a note for this as well
<@jnsamyak:matrix.org>
16:20:47
we nissed this that resulted us to wrong pointers
<@jnsamyak:matrix.org>
16:20:54
we missed this that resulted us to wrong pointers
<@jnsamyak:matrix.org>
16:21:36
Anything else, on the top of our heads?
<@nirik:matrix.scrye.com>
16:21:56
yeah, I'd like to propose we move to the newer way to disable koji...
<@jnsamyak:matrix.org>
16:22:02
- https://pagure.io/releng/issue/12255 we need to update the link in /mnt/koji/repos/rawhide/latest
<@jnsamyak:matrix.org>
16:22:02
- add rawhide defination and new keys to all the stable fedora-repos
<@jnsamyak:matrix.org>
16:22:02
- use of custom ip for blocking external folks to submit builds in koji
<@jnsamyak:matrix.org>
16:22:02
<@jnsamyak:matrix.org>
16:22:02
My list so far:
<@jnsamyak:matrix.org>
16:22:02
- creation of new bugzilla component is missing from the docs
<@jnsamyak:matrix.org>
16:22:02
- fedora-repos was updated to point to rawhide key and f43 key. Thats not right, it should keep pointing to the previous key until we make the next one (f44) and then we can point it to also f43... i.e, we want it to point to rawhide and the previous one so things signed with the old key keep working
<@nirik:matrix.scrye.com>
16:22:16
ie, blocking proxy01/10 on koji01/02 (instead of pushing any disable in hub config)
<@nirik:matrix.scrye.com>
16:22:30
yeah, that first point
<@jnsamyak:matrix.org>
16:22:53
I like the way but I'm need to learn more on ips, but what we did should work everytime right? or can you shed more light on that kevin?
<@nirik:matrix.scrye.com>
16:23:18
yeah, now that we fixed the rabbitmq problem, it should work fine...
<@jnsamyak:matrix.org>
16:23:27
thanks
<@patrikp:matrix.org>
16:24:00
What's the "newer way" of disabling Koji in more detail?
<@jnsamyak:matrix.org>
16:24:20
did we forget something about the eln, I remember not making everyone happy that time?
<@nirik:matrix.scrye.com>
16:24:47
Instead of changing anything on koji, we just block proxy01/10 (the proxies that are used by users to access koji), so they get a 'this serice is down' page.
<@nirik:matrix.scrye.com>
16:25:00
we can still get to it fine internally (from compose-x86-01 say)
<@nirik:matrix.scrye.com>
16:25:06
and builders still work, etc.
<@patrikp:matrix.org>
16:25:12
So manually on the systems instead of through PRs?
<@nirik:matrix.scrye.com>
16:25:34
jnsamyak: they wanted to know when they could turn on/off their thing that listens for rawhide builds being tagged in.
<@patrikp:matrix.org>
16:25:55
Ahhhh.
<@jnsamyak:matrix.org>
16:26:05
https://pagure.io/fedora-infra/ansible/c/9465ff33a171401d240f0cf1e53850cf4e42cf2a?branch=main
<@nirik:matrix.scrye.com>
16:26:41
can be in a PR, just should be changing iptables not hub config anymore
<@patrikp:matrix.org>
16:26:49
Yeah I misunderstood the first time.
<@jnsamyak:matrix.org>
16:27:03
aha I think that is already answered or should we make a note about this in the docs as well?
<@nirik:matrix.scrye.com>
16:27:08
oh, can we note/fix the permission issue that prevented things from syncing on the first branched compose?
<@nirik:matrix.scrye.com>
16:27:31
we might ping them and ask if we should notify them and when and add that to the doc?
<@jnsamyak:matrix.org>
16:27:58
that was my bad, i thought i did it but my mind shut off and I just didn't recheck there is a tiny line in the doc about it, I can make it explicit in the form of command
<@jnsamyak:matrix.org>
16:28:25
- check for permission for new compose to sync properly
<@jnsamyak:matrix.org>
16:28:33
- check for directory permission for new compose to sync properly
<@nirik:matrix.scrye.com>
16:28:49
Oh, one other thing we should discuss...
<@jnsamyak:matrix.org>
16:29:17
sure thing i can do that, but i generally mention it on the tracker and ping relevant folks from last two releases
<@nirik:matrix.scrye.com>
16:29:27
perhaps we could use sidetags for the fedora-release/fedora-repos updates and also then update mock-core-configs and distribution-gpg-keys and push them all in one update.
<@jnsamyak:matrix.org>
16:29:38
but adding it to doc also is nice way if someone else is doing for next time
<@nirik:matrix.scrye.com>
16:29:47
would need to talk to maintainers of those packages and make sure they are ok with it.
<@jnsamyak:matrix.org>
16:30:06
yes good thing, i want to ask a very dumb question, how can i submit it one one update
<@jnsamyak:matrix.org>
16:30:35
so we should first create a sidetag, built both there, and then submit a push?
<@nirik:matrix.scrye.com>
16:31:14
yes. well, not both, but all 4 of those if we can
<@nirik:matrix.scrye.com>
16:31:15
https://docs.fedoraproject.org/en-US/package-maintainers/Package_Update_Guide/#_side_tags
<@jnsamyak:matrix.org>
16:31:38
!action releng should talk to maintainers of fedora-repos/releases so check if we can build them in sidetags and push them all in one update.
<@jnsamyak:matrix.org>
16:31:51
!action releng should talk to maintainers of fedora-repos/releases so check if we can build them in sidetags and push them all in one update. (required for branching)
<@nirik:matrix.scrye.com>
16:31:51
That way all of them can be tested by ci at the same time and we can be sure they all got updated, etc
<@nirik:matrix.scrye.com>
16:32:58
we may also want to disable rawhide cron in the branching pr... and make sure we get a branched compose and then push another commit to re-enable rawhide
<@nirik:matrix.scrye.com>
16:34:30
I am not thinking of anything else off hand (should have made more careful notes, but I don't think there was much else)
<@jnsamyak:matrix.org>
16:35:02
<@jnsamyak:matrix.org>
16:35:02
- we may also want to disable rawhide cron in the branching pr... and make sure we get a branched compose and then push another commit to re-enable rawhide
<@jnsamyak:matrix.org>
16:35:02
- perhaps we could use sidetags for the fedora-release/fedora-repos updates and also then update mock-core-configs and distribution-gpg-keys and push them all in one update.
<@jnsamyak:matrix.org>
16:35:02
- check for directory permission for new compose to sync properly
<@jnsamyak:matrix.org>
16:35:02
- https://pagure.io/releng/issue/12255 we need to update the link in /mnt/koji/repos/rawhide/latest
<@jnsamyak:matrix.org>
16:35:02
- fedora-repos was updated to point to rawhide key and f43 key. Thats not right, it should keep pointing to the previous key until we make the next one (f44) and then we can point it to also f43... i.e, we want it to point to rawhide and the previous one so things signed with the old key keep working
<@jnsamyak:matrix.org>
16:35:02
- creation of new bugzilla component is missing from the docs
<@jnsamyak:matrix.org>
16:35:02
- add rawhide defination and new keys to all the stable fedora-repos
<@jnsamyak:matrix.org>
16:35:02
- use of custom ip for blocking external folks to submit builds in koji
<@jnsamyak:matrix.org>
16:35:02
My list so far (these are things we did for the first time, things we can do better the next time, and things that we missed this time):
<@jnsamyak:matrix.org>
16:35:10
how does that look?
<@nirik:matrix.scrye.com>
16:35:34
👍
<@jnsamyak:matrix.org>
16:35:37
I'll try to update docs based on this and maybe continue to discuss more about that there?
<@jnsamyak:matrix.org>
16:36:07
@nirik awesome thank you so much with your help at branching
<@jnsamyak:matrix.org>
16:37:20
What do we have schedule for next week?
<@bittin:matrix.org>
16:37:32
Beta Freeze?
<@jnsamyak:matrix.org>
16:37:49
Correct!
<@jnsamyak:matrix.org>
16:37:51
!info Bodhi updates-testing activation point and Beta Freeze is schedule for Tue 2024-08-27
<@nirik:matrix.scrye.com>
16:37:55
yep.
<@jnsamyak:matrix.org>
16:38:23
Anything else for release process, or can we jump off to next topic of the night?
<@jnsamyak:matrix.org>
16:39:31
!topic Tickets needing attention
<@jnsamyak:matrix.org>
16:39:35
!info this is the time where you can bring releng tickets to discuss if there are blockers etc
<@jnsamyak:matrix.org>
16:39:50
we can use !releng <issue_number>
<@jnsamyak:matrix.org>
16:39:50
in case we need to discuss on issue related to releng tracker
<@jnsamyak:matrix.org>
16:39:58
Any tickets that folks want to bring up?
<@bittin:matrix.org>
16:40:33
have not really looked, still on summer vacation a bit from Open Source things until September
<@patrikp:matrix.org>
16:40:41
We have a new one.
<@patrikp:matrix.org>
16:40:48
!releng 12275
<@zodbot:fedora.im>
16:40:49
● **Last Updated:** 35 minutes ago
<@zodbot:fedora.im>
16:40:49
● **Opened:** 36 minutes ago by jkonecny
<@zodbot:fedora.im>
16:40:49
● **Assignee:** Not Assigned
<@zodbot:fedora.im>
16:40:49
**releng #12275** (https://pagure.io/releng/issue/12275):**The `openh264` package fails to install because of the GPG key**
<@zodbot:fedora.im>
16:40:49
<@jnsamyak:matrix.org>
16:41:20
👀
<@jnsamyak:matrix.org>
16:41:37
i think i updated the robosignatory for this
<@nirik:matrix.scrye.com>
16:41:42
yeah, so if we had f42 key listed in fedora-rawhide.repo this would still just work... ;( but since we don't....
<@nirik:matrix.scrye.com>
16:42:13
so I guess we need to see if there's going to be a new build soon, and if not, just resign it and make a new repo and ship it to cisco
<@nirik:matrix.scrye.com>
16:42:25
and... on top of all that:
<@nirik:matrix.scrye.com>
16:42:55
!ticket 12112
<@zodbot:fedora.im>
16:42:56
● **Assignee:** Not Assigned
<@zodbot:fedora.im>
16:42:56
● **Opened:** 2 weeks ago by abompard
<@zodbot:fedora.im>
16:42:56
● **Last Updated:** a week ago
<@zodbot:fedora.im>
16:42:56
<@zodbot:fedora.im>
16:42:56
**fedora-infrastructure #12112** (https://pagure.io/fedora-infrastructure/issue/12112):**The process to update the OpenH264 repos is broken**
<@nirik:matrix.scrye.com>
16:43:24
so, lots to figure out here. ;)
<@jnsamyak:matrix.org>
16:43:25
you mean here? Did we miss it? I'm not sure i captured the full idea
<@jnsamyak:matrix.org>
16:43:25
https://src.fedoraproject.org/rpms/fedora-repos/blob/rawhide/f/fedora-rawhide.repo
<@jnsamyak:matrix.org>
16:43:25
<@jnsamyak:matrix.org>
16:43:45
:/
<@nirik:matrix.scrye.com>
16:44:14
yes, right now that looks like:
<@nirik:matrix.scrye.com>
16:44:16
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-rawhide-$basearch file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-43-$basearch
<@nirik:matrix.scrye.com>
16:44:42
but the previous cisco h264 repo is signed by the f41 key, not the f42/f43 ones
<@nirik:matrix.scrye.com>
16:44:56
if that was f41 there the packages should validate
<@jnsamyak:matrix.org>
16:45:01
so we added f43 keys in hurry?
<@jnsamyak:matrix.org>
16:45:09
we should have added it post branching?
<@nirik:matrix.scrye.com>
16:45:49
yeah. we should have f41 now, and then when we branch next time we should change it to f42 (it should be a release behind)
<@nirik:matrix.scrye.com>
16:46:12
this may be related to that pr... like I said I haven't looked closely at it yet
<@jnsamyak:matrix.org>
16:46:50
but from the ticket i remember we want us to add that the rawhide+1+1 (before branching) keys to the repos
<@jnsamyak:matrix.org>
16:47:17
aha i also need to look at things in more depth
<@nirik:matrix.scrye.com>
16:47:34
anyhow. I guess we could push a fedora-repos update with f41 in there to 'fix' this, or we could just sort through what it would take to get a properly f42 signed packages out
<@nirik:matrix.scrye.com>
16:50:37
sounds good. I can try and look too.
<@patrikp:matrix.org>
16:52:33
/home/fedora/patrikp/odcs/openh264-2.4.1
<@patrikp:matrix.org>
16:52:33
Btw, regarding the OpenH composes, if you need the composes (or tarballs that were sent to Cisco) for whatever reason they are in my home directory on batcave.
<@patrikp:matrix.org>
16:52:33
$ pwd
<@nirik:matrix.scrye.com>
16:54:02
yeah, which reminds me another thing: we need to figure out how best to do those without odcs. Since we are trying really hard to retire it.
<@nirik:matrix.scrye.com>
16:54:45
we may have to do some simple local pungi config or something.
<@patrikp:matrix.org>
16:56:21
Can't Cisco grant the legal rights? It's vague so I don't understand the intricacies.
<@patrikp:matrix.org>
16:56:21
<@patrikp:matrix.org>
16:56:21
"We do not have all the appropriate legal rights to distribute these packages, so we need to be extra carefull to make sure they are never distributed via our build system or websites"
<@patrikp:matrix.org>
16:56:21
Perhaps a naive question but the SOP says:
<@patrikp:matrix.org>
16:56:28
https://docs.fedoraproject.org/en-US/infra/releng_misc_guide/sop_generating_openh264_composes/
<@jnsamyak:matrix.org>
16:56:52
since we are in last 4 mins, i have one quick things to choose next chair
<@jnsamyak:matrix.org>
16:57:16
patrikp: can you do it next week?
<@nirik:matrix.scrye.com>
16:57:22
It's patents. They pay to be able to distribute it, we cannot
<@nirik:matrix.scrye.com>
16:57:41
they cannot allow us to, they don't have all the patents
<@bittin:matrix.org>
16:57:43
will try to attend next week if i am not too tired after the first day at dayjob, after the summer vacation
<@patrikp:matrix.org>
16:57:54
I can chair it. 👍️
<@jnsamyak:matrix.org>
16:58:02
awesome
<@jnsamyak:matrix.org>
16:58:13
!info next chair Aug 27 - Patrick
<@nirik:matrix.scrye.com>
16:58:19
https://en.wikipedia.org/wiki/Advanced_Video_Coding
<@nirik:matrix.scrye.com>
16:58:53
anyhow... yeah, it's pretty sad
<@patrikp:matrix.org>
16:59:05
Right, different patent holder than Cisco... :-/
<@bittin:matrix.org>
17:00:07
so guess that was it for this week then
<@jnsamyak:matrix.org>
17:00:36
we are almost on time
<@jnsamyak:matrix.org>
17:00:38
!info Thank you all for coming.
<@bittin:matrix.org>
17:00:38
gonna head off and watch the Gamescom 2024 Online day: https://www.gamescom.global/en from Cologne and continue to pack to travel from England back to Sweden
<@bittin:matrix.org>
17:00:51
cya next week, if i am not too tired after working again
<@jnsamyak:matrix.org>
17:00:51
we can take this to the releng channel
<@jnsamyak:matrix.org>
17:00:53
!endmeeting