IRC logs for #cip for Thursday, 2020-01-30

*** toscalix has joined #cip06:50
*** toscalix_ has joined #cip07:02
*** toscalix has quit IRC07:03
*** rajm has joined #cip07:04
*** toscalix_ has quit IRC07:25
*** toscalix has joined #cip07:27
patersoncI've just sent an update on CIP testing activities to cip-dev as I'm not going to be able to make today's meeting.07:36
*** therisen has joined #cip07:42
*** toscalix has quit IRC07:51
*** masashi910 has joined #cip08:02
*** fujita3 has joined #cip08:57
*** suzuki has joined #cip08:58
*** pave1 has joined #cip08:58
masashi910#startmeeting CIP IRC weekly meeting09:00
brlogger`Meeting started Thu Jan 30 09:00:01 2020 UTC and is due to finish in 60 minutes.  The chair is masashi910. Information about MeetBot at http://wiki.debian.org/MeetBot.09:00
brlogger`Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:00
brlogger`The meeting name has been set to 'cip_irc_weekly_meeting'09:00
*** brlogger` changes topic to " (Meeting topic: CIP IRC weekly meeting)"09:00
masashi910#topic rollcall09:00
*** brlogger` changes topic to "rollcall (Meeting topic: CIP IRC weekly meeting)"09:00
masashi910please say hi if you're around09:00
pave1hi09:00
suzukihi09:00
fujita3hi09:00
masashi910Thanks for joining!09:00
masashi910#topic AI review09:00
*** brlogger` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"09:00
masashi9101. Combine rootfilesystem with kselftest binary - Iwamatsu-san09:01
masashi910Iwamatsu-san, are you around?09:01
*** kazu has joined #cip09:01
szlinhi09:01
kazuhi09:01
masashi910OK, let me come back later.09:01
masashi9102. Document a process on how to add tests to the CIP test setup - patersonc09:01
masashi910Quote from patersonc "No progress from me."09:02
masashi9103. Arrangement of F2F Kernel Meeting in Nuremberg - masashi91009:02
masashi910https://doodle.com/poll/73if9spavecwqrh5ge3809:02
masashi910As I mentioned at the IRC meeting last week, I requested Yoshi-san to allocate 3PM to 5PM on 27th for our F2F meeting.09:02
masashi910I have not gotten his confirmation yet. I will poke him later.09:02
masashi910pave1: sorry about that.09:02
masashi910Till the arrangement is done, I keep this AI open.09:02
pave1masashi910: Thanks for the effort :-).09:03
masashi910So, let's move to next.09:03
masashi910#topic kernel maintenance updates09:03
*** brlogger` changes topic to "kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"09:03
pave1I did reviews on 4.19.98, 4.19.99 and 4.19.100.09:04
masashi910pave1: Thanks for your note that 4.19.99 is a big series.09:04
pave1masashi910: Yes, that one is huge (and not done yet).09:05
masashi910pave1: Thanks for your efforts!09:05
masashi910SZ-san, I know you are still in a vacation. But just in case, let me ask. Do you have updates?09:06
masashi910So, any other topics?09:08
szlinno09:08
masashi910szlin: Thanks!09:08
masashi910309:09
masashi910209:09
masashi910109:09
masashi910#topic Kernel testing09:09
*** brlogger` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"09:09
masashi910== Quote from patersonc ==09:09
masashi910Not much to report this week:09:09
masashi910* I switched the remote PDUs in the Renesas LAVA lab with new (hopefully) reliable ones. This should improve uptime.09:09
masashi910* In the last week for cip we've tested the 4.19.98-cip19 release, and the latest commits to the 4.4 and 4.19 branches.09:09
masashi910  * https://gitlab.com/cip-project/cip-kernel/linux-cip/pipelines09:09
masashi910* In the last week for linux-stable we've built/tested 4.4.211, 4.4.212, 4.19.99, 4.19.100 and many variants of the release candidates.09:09
masashi910  * https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/commits/linux-4.4.y09:09
masashi910  * https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/commits/linux-4.19.y09:09
masashi910====09:09
masashi910any other topics?09:09
masashi910309:10
masashi910209:10
masashi910109:10
masashi910#topic CIP Core09:10
*** brlogger` changes topic to "CIP Core (Meeting topic: CIP IRC weekly meeting)"09:10
masashi910kazu: the floor is yours09:10
kazuhello09:10
kazunot so many updates from me, but09:10
kazu1. Package review for Debian minimal base system is still on going09:10
kazuwaiting for replies from two members, it will be decided soon, i hope :)09:11
kazu2. Revewing details of security packages from security WG09:11
kazuWe need to share requrement about security features and information about target platform like HW, network ,etc.09:12
kazuWe'd like to accelerate this discussion09:12
kazuThat's all09:12
masashi910kazu: Thanks.09:12
wenssorry I'm late again :(09:12
masashi910kazu: I have a question. As I recall correctly, you once mentioned about a plan to have a mirror for CIP core packages. Is it correct?09:12
masashi910wens: Hi!09:13
kazumasashi910 Yes, we have discussed this topic, but no big updates at the moment...09:13
kazuInternally, we are discussing about this kind of topic09:13
masashi910kazu: I see. Is it a budget issue?09:14
kazumasashi910 I don't think so, we just need to more details about background, requirements of IEC 62443-4-109:14
masashi910kazu: I see. The reason I asked is about the discussion with Certification Bodies.09:15
masashi910kazu: Anyway, thanks for this information!09:15
kazuThank you for reminding this :)09:16
masashi910wens: We have done the Kernel Maintenance Updates, but do you have any updates? I think you are in a holiday.09:16
wensmasashi910: I reviewed a cip-kernel-sec MR from Ben, and also sent a follow-up09:17
wensone new CVE, fixed already09:17
masashi910wens: Oh, thanks so much for your updates!09:17
masashi910any other topics?09:17
wensalso have a pending MR for classify-failed-patches. nothing critical09:17
masashi910309:17
masashi910wens: Thanks for your works!09:18
masashi910any other topics?09:19
masashi910309:19
masashi910209:19
masashi910109:19
masashi910#topic Software update09:19
*** brlogger` changes topic to "Software update (Meeting topic: CIP IRC weekly meeting)"09:19
masashi910Suzuki-san, the floor is yours09:19
suzukihello09:19
suzukiI've submitted 3 proposals regarding SW Updates WG to cip-members ML.09:19
suzukihttps://lists.cip-project.org/mailman/private/cip-members/2020-January/002406.html09:20
suzukiI'm waiting for the proposals to be approved.09:20
suzukiAnd also I'm preparing our WG's 3rd iteration items.09:20
suzukiThat's all from me.09:20
masashi910suzuki: Thanks for your updates!09:20
masashi910Does anybody have any questions on his proposals?09:21
masashi910any other topics?09:21
masashi910309:22
masashi910209:22
masashi910109:22
masashi910#topic AOB09:22
*** brlogger` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"09:22
masashi910Are there any business matters to discuss?09:22
masashi910309:22
masashi910209:22
masashi910109:22
masashi910#endmeeting09:22
brlogger`Meeting ended Thu Jan 30 09:22:50 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:22
brlogger`Minutes:        https://irclogs.baserock.org/meetings/cip/2020/01/cip.2020-01-30-09.00.html09:22
brlogger`Minutes (text): https://irclogs.baserock.org/meetings/cip/2020/01/cip.2020-01-30-09.00.txt09:22
brlogger`Log:            https://irclogs.baserock.org/meetings/cip/2020/01/cip.2020-01-30-09.00.log.html09:22
*** brlogger` changes topic to "Civil Infrastructure Platform Project. Find the logs at https://irclogs.baserock.org/cip/"09:22
masashi910Thanks very much! See you next week!09:22
pave1Thank you!09:23
wensthank you!09:23
kazuThank you09:23
fujita3thank you!09:23
suzukiThank you!09:23
*** suzuki has quit IRC09:23
*** fujita3 has quit IRC09:24
szlinmasashi910: thank you!09:24
kazu@masa09:25
kazumasashi910 Do you know anyone want to know the progress about CIP core package mirror?09:25
kazuFrom discussions in security WG?09:26
masashi910kazu: Sorry  for my late response.09:27
masashi910kazu: Yes, the security members would like to know.09:27
masashi910The reason is that this is one of the queries from CB.09:28
kazumasashi910 OK, thank you for the information!09:28
masashi910Their question is whether the repos are under our control or not.09:28
masashi910If we have a mirror, then, we can say that it is under our control.09:29
kazuOK, but I guess they may ask about "how" we are controlling mirror or other resources related to the process09:30
masashi910That is also correct.09:30
kazuAnyway, it seems to be high priority discussion, I will join soon09:30
masashi910That's great!!!!!09:30
masashi910Thank you!09:31
masashi910I will let the Security WG members know about your comment!09:31
kazuPlease note that CIP may need some formal decision to have our mirror though09:31
masashi910Yes. I know!09:32
kazuIt would be nice to have some places to share common issues among multiple CIP WGs (like GitLab issue)09:34
masashi910Yes. In some way, we may raise issues to the TSC telecon and decide how to discuss?09:35
kazugood idea :)09:36
kazuOr, should we join the discussion in security WG's GitLab issue?09:36
kazuI saw several discussions being updated09:36
kazuOnce concern is that is a private place...09:37
masashi910Yes, if you can join the security WG telecon, that would be great!09:37
kazumasashi910 Thank you, let me check :)09:37
kazusorry I need to leave today, see you next discussion!09:38
masashi910That is private, because IEC62443 specifications are confidential/private.09:38
masashi910But Toshiba has a right to talk about them.09:38
masashi910See you!09:38
*** kazu has quit IRC09:43
*** rajm has quit IRC10:10
*** pave1 has quit IRC11:19
*** kimmoli has joined #cip12:29
*** tpollard has quit IRC12:51
*** tpollard has joined #cip12:53
*** tpollard has quit IRC14:13
*** masashi910 has quit IRC14:15
*** tpollard has joined #cip14:16
*** therisen has quit IRC16:10
*** tpollard has quit IRC16:13
*** tpollard has joined #cip16:14
*** tpollard has quit IRC17:15
*** mungaip[m] has quit IRC20:35

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!