13:01:13 <jki> #startmeeting CIP IRC weekly meeting
13:01:13 <brlogger> Meeting started Thu Nov 11 13:01:13 2021 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:01:13 <brlogger> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:01:13 <brlogger> The meeting name has been set to 'cip_irc_weekly_meeting'
13:01:18 <jki> Hi all!
13:01:28 <pave1> Hi!
13:01:29 <uli> hello
13:01:30 <patersonc[m]> ay up
13:01:31 <masami> hello
13:01:44 <iwamatsu> hi
13:02:01 <alicef> hi
13:03:03 <jki> #topic AI review
13:03:13 <jki> 1. Combine root filesystem with kselftest binary - iwamatsu & alicef
13:03:46 <alicef> The cip-core-image-kernelci got released in KernelCI production. KernelCI sent a tweet about this https://twitter.com/kernelci/status/1458073694702653444
13:04:13 <alicef> would be nice if cip tweet account could retweet this tweet
13:04:26 <patersonc[m]> alicef: I've asked the CIP PR people
13:04:57 <alicef> currently is still only basic test but we are working on adding the kselftest test soon
13:05:45 <alicef> we already had many interest around the image and some people point out difference on the lava testing board enviroment
13:07:02 <jki> great news!
13:07:32 <jki> alicef: will you send the patches soon?
13:08:04 <alicef> jki: yes working on that
13:08:57 <alicef> I was writing the cover mail today and I will send the patch soon
13:09:47 <jki> 2. Look into S3 artifact upload issues - patersonc
13:10:20 <patersonc[m]> Sorry, still no progress on this
13:11:02 <jki> 3. Propose review coordination workflow via wiki - iwamatsu
13:11:30 <jki> email was sent - anything else to discuss/clarify on this?
13:12:13 <pav3l> We may want to use format which allows reviewing 5.10 & 4.19 & 4.4 at the same time.
13:12:19 <pav3l> I'll send a proposal via email.
13:12:44 <iwamatsu> pav3l: ok, thanks.
13:14:41 <jki> 4. Update AOSP tracking - iwamatsu
13:15:09 <iwamatsu> I sent a patch via gitlab.
13:15:28 <masami> I merged iwamatsu-san's merge request.
13:15:44 <iwamatsu> it already merged.
13:15:49 <jki> perfect
13:16:11 <iwamatsu> masami: thanks for merge.
13:16:28 <jki> any other AIs?
13:16:54 <jki> 3
13:16:57 <jki> 2
13:17:00 <jki> 1
13:17:03 <jki> #topic Kernel maintenance updates
13:17:19 <pav3l> I have reviewed patches queued for 5.10.78 and 5.10.79
13:17:26 <uli> finished with 5.10.77
13:17:38 <masami> There is 4 new CVEs in this week. they are not serious issue.
13:17:41 <iwamatsu> I reviewed 5.10.78
13:20:53 <jki> anything else to exchange/discuss?
13:21:12 <jki> 3
13:21:15 <jki> 2
13:21:18 <jki> 1
13:21:21 <jki> #topic Kernel testing
13:21:48 <patersonc[m]> I don't really have anything to share other then the work Alice has already reported
13:22:13 <jki> ok
13:22:26 <jki> #topic AOB
13:25:11 <jki> I would have one: would it make sense to have a team-internal permanent irc channel for chat, non-logged?
13:26:33 <alicef> internal to what ? and what kind of team ?
13:26:44 <jki> kernel team
13:27:44 <uli> i'm used to that from other places i work/used to work at
13:27:47 <jki> internal in the sense that it's not publicly logged
13:28:00 <alicef> maybe just use this channel for whatever topic outside of the meeting, similar to other projects are doing ?
13:28:29 <alicef> this is not publicly logged, only during meeting is logged
13:29:16 <alicef> if you mean secure the channel, can be a possibility. like put the channel on some strict mode
13:31:29 <alicef> currently we have the standard mode lock +nt-lk
13:32:16 <iwamatsu> This channel has already been an IRC channel as an OSS community, so if we want to make it closed, we may need to be created separately.
13:33:03 <jki> yep, I would not suggest changing the rules for this one
13:33:15 <alicef> we want to make a closed channel ?
13:34:22 <alicef> sorry, secure channel for me is different than closed channel. sure we can make a closed channel
13:35:17 <alicef> is it needed ?
13:35:18 <patersonc[m]> Are there things that need to be discussed privately? Or are you just trying to avoid flooding this channel?
13:35:36 <patersonc[m]> Because this channel has very low usage
13:35:47 <iwamatsu> I see, I have not understood correctly....
13:35:50 <alicef> yep +1 patersonc[m]
13:36:39 <alicef> iwamatsu: np
13:37:04 <jki> well, eventually, we may need to discuss sensitive security topics e.g.
13:37:40 <alicef> like for example one option would be to add +r for make join only registered users
13:37:58 <alicef> jki: remember to add strict ssl for that
13:37:59 <patersonc[m]> There is a cip-security channel I think :)
13:38:42 <alicef> jki: currently you are not using a secure connection
13:40:10 <jki> thanks, will update that for the next meeeting ;)
13:40:58 <alicef> jki: https://libera.chat/guides/connect#accessing-liberachat-via-tls
13:41:02 <masami> If we want to talk about security like linux-distros, private channel would be nice, I think.
13:42:35 <alicef> jki: remember to add +Z to the channel flags or closing it is not adding security
13:44:29 <jki> ok, seems we have not a strong opinion on this, do we?
13:45:54 <alicef> if we have topic that are not about a already open CVE could be a option to consider
13:46:08 <alicef> s/in the future
13:46:31 <jki> then let's keep this in mind for now
13:46:38 <jki> any other topics?
13:47:41 <jki> 3
13:47:44 <jki> 2
13:47:47 <jki> 1
13:47:49 <jki> #endmeeting