Thursday, 2026-04-23

*** prabhakalad <prabhakalad!~prabhakar@97e54365.skybroadband.com> has quit IRC (Ping timeout: 255 seconds)01:06
*** prabhakalad <prabhakalad!~prabhakar@97e54365.skybroadband.com> has joined #cip01:06
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has joined #cip05:57
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has quit IRC (Ping timeout: 248 seconds)06:02
*** tmerciai1 <tmerciai1!~tmerciai@net-188-217-32-146.cust.vodafonedsl.it> has quit IRC (Remote host closed the connection)06:12
*** tmerciai2 <tmerciai2!~tmerciai@net-188-217-32-146.cust.vodafonedsl.it> has joined #cip06:26
*** frieder <frieder!~frieder@i59F664FD.versanet.de> has joined #cip07:21
*** tmerciai2 <tmerciai2!~tmerciai@net-188-217-32-146.cust.vodafonedsl.it> has quit IRC (Ping timeout: 245 seconds)07:35
*** tmerciai1 <tmerciai1!~tmerciai@net-188-217-32-146.cust.vodafonedsl.it> has joined #cip07:35
*** tmerciai1 <tmerciai1!~tmerciai@net-188-217-32-146.cust.vodafonedsl.it> has quit IRC (Ping timeout: 246 seconds)07:42
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has joined #cip08:45
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has quit IRC (Ping timeout: 248 seconds)08:58
*** tmerciai <tmerciai!~tmerciai@net-188-217-32-146.cust.vodafonedsl.it> has joined #cip09:50
*** tmerciai <tmerciai!~tmerciai@net-188-217-32-146.cust.vodafonedsl.it> has quit IRC (Ping timeout: 245 seconds)10:21
*** amadaluzia <amadaluzia!2cbc58d702@user/amadaluzia> has joined #cip10:48
*** masami <masami!~masami@FL1-125-195-92-229.tky.mesh.ad.jp> has joined #cip11:58
*** jki <jki!~jki@62.156.206.40> has joined #cip11:58
jkihi all11:59
uli_hello12:00
masamihi12:00
iwamatsuhello12:00
pave1hi12:00
patersoncHey12:00
jki#startmeeting CIP IRC weekly meeting12:00
collab-meetbotMeeting started Thu Apr 23 12:00:47 2026 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.12:00
collab-meetbotUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:00
collab-meetbotThe meeting name has been set to 'cip_irc_weekly_meeting'12:00
*** collab-meetbot changes topic to " (Meeting topic: CIP IRC weekly meeting)"12:00
jki#topic AI review12:00
*** collab-meetbot changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"12:00
jkino Action Items (we will come to other AI later ;))12:01
jki512:01
jki412:01
jki312:01
jki212:01
jki112:01
jki#topic Kernel maintenance updates12:01
*** collab-meetbot changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"12:01
uli_i've been working on 4.412:01
masamiThis week reported 102 new CVEs and 132 updated CVEs.12:01
iwamatsuI reviewed 6.12.80.12:02
pave1I am reviewing 6.12.82 and 8312:02
jkianything to add?12:03
jki512:03
jki412:03
jki312:03
jki212:03
jki112:03
jki#topic Kernel release status12:04
*** collab-meetbot changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)"12:04
jki4.4 is now quite late but almost done, right?12:04
uli_reviews are in, so i expect to be able to push it tomorrow12:04
jkiwas there a particular reason for the delay?12:04
uli_more backports than expected. many things went into 4.19 cleanly but had to be backported for 4.412:05
uli_usually that is not the case, or at least to a much lower extent12:05
jkiok, please speak up early if it repeats12:05
uli_ok12:06
jkiif workload grows, we need to flag that12:06
jkibefore being boiled alive ;)12:06
uli_it varies between releases, sometimes dramatically12:06
uli_can't really predict that12:07
jkisure, but in that case one question would be if there is chance to scale out the work12:07
jkihave more hands when needed12:07
uli_not sure. for the last release, 4.4 was very little effort, iirc i released it on the same day as 4.19 or something like that12:08
jkianyway, let's just monitor carefully12:09
jkianything else?12:09
jki512:10
jki412:10
jki312:10
jki212:10
jki112:10
jki#topic Kernel testing12:10
*** collab-meetbot changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"12:10
patersoncNot much from me.12:11
arisutnot much from me, applied kernel testing and dependability MC for LPC 202612:11
patersonciwamatsu: your lab is currently offline, could you take a look when you get a chance?12:11
iwamatsupatersonc: I will check after this meeting.12:11
patersoncThanks12:11
jkijust reminded Pasquale of the prague lab state...12:12
patersoncThanks12:13
jkimore testing topics?12:14
jki512:14
jki412:15
jki312:15
jki212:15
jki112:15
jki#topic AOB12:15
*** collab-meetbot changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"12:15
jkiGlasswing topics from kernel and testing perspective - just a reminder for my email12:15
jkiif you have anything to discuss here already, go ahead12:16
jkitimeline is still unclear, though12:16
pave1Just be sure thete is human sending issues to us12:16
pave1so we can tell him to stop.12:17
pave1We already have source of low quality issues12:17
jkimight be me in the end - you may even shout then ;)12:17
uli_+1. i use llms extensively, but that's me controlling the ai. if somebody else sent me false positives, i'd become very annoyed very quickly.12:17
pave1- CVE.12:18
pave1Yeah, I seen you volunteering.12:18
pave1Just make sure there's human on12:18
jkiI would expect to 2-phase process: learn based on few examples what it can do, then scale up, or down12:18
pave1the other end, too.12:18
jkiGlasswing access is apparently always operated by one individual, human, per participating LF project12:19
jkithey told us this is by design, to have many projects benefiting, rather than few with more bandwidth12:20
pave1So no human oversight at the other end?12:20
jkithe humans in there are LF project representatives12:21
jkithe give prompts and (pre-)process the results, then decide what to do with them (simplified)12:22
jkiI haven't seen any written conditions yet, remains a bit speculation12:22
pave1I'd ask someone on AI side to do at least pre-processing.12:23
uli_that would be a massive manual effort; i'm sure they will leave that to us...12:24
jkithey (Anthropic) just to the operation and safety supervision here - again only my current understanding12:24
jkiyep12:24
jkibut it will remain fully up to us as project to which degree we make use of it, or can do that if we are limited in time/hands12:25
jkiso, representative depth first, then discuss if/how to go wide12:26
jkiif you have done past experiments with moderate success, those could be retried e.g.12:26
jkiif you have harder questions to ask that were not possible so far (or too expensive), let's try one of them12:27
jkietc...12:27
jkiother topics for today?12:29
jki512:30
jki412:30
jki312:30
jki212:30
jki112:30
jki#endmeeting12:30
collab-meetbotMeeting ended Thu Apr 23 12:30:16 2026 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)12:30
collab-meetbotMinutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/04/cip.2026-04-23-12.00.html12:30
collab-meetbotMinutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/04/cip.2026-04-23-12.00.txt12:30
collab-meetbotLog:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/04/cip.2026-04-23-12.00.log.html12:30
*** collab-meetbot changes topic to "Civil Infrastructure Platform Project. CIP mailing list at https://lists.cip-project.org/g/cip-dev | CIP kernel meeting every Thursday at 13:00 UTC | Find the meeting logs at https://ircbot.wl.linuxfoundation.org/meetings/cip/ and chat logs at https://ircbot.wl.linuxfoundation.org/logs/%23cip/"12:30
jkithanks all!12:30
uli_thanks12:30
iwamatsuThank you12:30
masamithank you12:30
pave1thanks!12:30
*** masami <masami!~masami@FL1-125-195-92-229.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)12:30
*** jki <jki!~jki@62.156.206.40> has quit IRC (Quit: Leaving)12:40
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has joined #cip13:23
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has quit IRC (Ping timeout: 248 seconds)14:04
*** frieder <frieder!~frieder@i59F664FD.versanet.de> has quit IRC (Remote host closed the connection)17:47

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!