IRC logs for #cip for Thursday, 2019-02-21

*** patersonc21 has joined #cip08:53
*** toscalix_ has joined #cip08:54
*** patersonc21 is now known as patersonc_08:57
*** mungaip has joined #cip08:59
szlin#startmeeting CIP IRC weekly meeting09:00
brloggerMeeting started Thu Feb 21 09:00:09 2019 UTC and is due to finish in 60 minutes.  The chair is szlin. Information about MeetBot at http://wiki.debian.org/MeetBot.09:00
brloggerUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:00
brloggerThe meeting name has been set to 'cip_irc_weekly_meeting'09:00
*** brlogger changes topic to " (Meeting topic: CIP IRC weekly meeting)"09:00
szlin#topic rollcall09:00
*** brlogger changes topic to "rollcall (Meeting topic: CIP IRC weekly meeting)"09:00
szlinplease say hi you're here09:00
patersonc_hi09:00
*** mungaip27 has joined #cip09:00
szlin#topic AI review09:01
*** brlogger changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"09:01
*** mungaip27 has quit IRC09:01
szlin1. Ask Daniel about the timetable of v4.4.171-rt kernel release09:01
szlin-> Done (https://lists.cip-project.org/pipermail/cip-dev/2019-February/001792.html)09:01
szlin2. Fujita will provide the feedback with CIP core tiny profile package list09:01
szlinfujita[m]: Do you have any update on this topic?09:01
patersonc_He sent an email earlier09:01
szlinpatersonc_: should this AI be closed?09:02
patersonc_I think so09:02
szlinpatersonc_: ok, thanks.09:03
szlin3. SZ will provide the feedback with CIP core tiny profile package list09:03
szlinTBD,  I will send the feedback to ci-dev after our internal discussion09:03
szlin#topic Kernel maintenance updates09:03
*** brlogger changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"09:03
szlinDaniel announced the 4.4.171-cip30-rt22 stable release09:03
szlinhttps://lists.cip-project.org/pipermail/cip-dev/2019-February/001792.html09:03
szliniwamatsu: are you around ?09:03
szlinbwh: Do you have any update on this topic?09:03
iwamatsuI dont hava any update.09:04
iwamatsus/hava/have09:04
szliniwamatsu: got it, thanks.09:04
patersonc_iwamatsu, are you reviewing the stable releases from Greg?09:04
iwamatsupatersonc_: I sometime review stable tree, but I have no content to reply to patches.09:06
patersonc_Okay. I think previously this was something that Ben was actively doing on behalf of CIP to help improve the quality of LTS in general (and therefore CIP)09:07
szliniwamatsu: do you have any suggestions for collaboration with stable patch review?09:08
szliniwamatsu: you can reply me after the meeting :)09:09
szlinany comment?09:10
szlin309:10
szlin209:10
szlin109:10
szlin#topic Kernel testing09:10
*** brlogger changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"09:10
iwamatsupatersonc_: Yes, I think that the amount of work is small compared to Ben. I will work so that I can see more work.09:10
iwamatsuszlin: Okay.09:10
patersonc_Thanks iwamatsu. It's good for CIP to be seen as active in the community09:11
szlinpatersonc_: do you have any update with kernel testing?09:12
patersonc_We hope to push some integration tests for the RZ/G1 boards today.09:12
patersonc_Then we plan to integrate Linaro's set of test definitions.09:12
patersonc_I'm also working on some slides etc. for next week's F2F meeting.09:12
szlinpatersonc_: thanks for the update.09:13
szlinI found this interesting tool which is related to kernel testing09:13
szlinhttps://github.com/ruscur/snowpatch09:13
patersonc_Thanks szlin. I'll take a look09:14
szlinany comment?09:14
szlin309:14
szlin209:14
szlin109:14
szlin#topic CIP Core09:14
*** brlogger changes topic to "CIP Core (Meeting topic: CIP IRC weekly meeting)"09:14
szlinany comment?09:15
szlin309:15
szlin209:15
szlin109:15
szlin#topic Software update09:15
*** brlogger changes topic to "Software update (Meeting topic: CIP IRC weekly meeting)"09:15
szlinany comment?09:16
szlin309:16
szlin209:16
szlin109:16
szlin#topic AOB09:16
*** brlogger changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"09:16
szlinI would like to propose to skip next week's IRC meeting.09:17
patersonc_Seconded09:17
szlinwe will have f2f meeting then.09:17
iwamatsu+109:18
szlin#agreed skip next week's IRC meeting09:18
szlinany other point?09:18
szlin309:18
szlin209:18
szlin109:18
szlin#endmeeting09:18
brloggerMeeting ended Thu Feb 21 09:18:37 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:18
brloggerMinutes:        https://irclogs.baserock.org/meetings/cip/2019/02/cip.2019-02-21-09.00.html09:18
brloggerMinutes (text): https://irclogs.baserock.org/meetings/cip/2019/02/cip.2019-02-21-09.00.txt09:18
brloggerLog:            https://irclogs.baserock.org/meetings/cip/2019/02/cip.2019-02-21-09.00.log.html09:18
*** brlogger changes topic to "Civil Infrastructure Platform Project. Find the logs at https://irclogs.baserock.org/cip/"09:18
szlinthank you all09:18
gavinlaithanks : )09:18
iwamatsuthanks09:18
szliniwamatsu: any idea for kernel review collaboration?09:19
szlinso far we have CIP Linux kernel CVE tracker in https://gitlab.com/cip-project/cip-kernel/cip-kernel-sec09:19
szlinand List of patches that failed to apply to 4.4-stable in https://wiki.linuxfoundation.org/civilinfrastructureplatform/linux-4.4-failed-patches09:20
szlinThe last one is Kernel review status in https://wiki.linuxfoundation.org/civilinfrastructureplatform/linux-4.4.y09:20
szliniwamatsu: Do you have a thought on these matters?09:21
iwamatsuszlin: For example,  I think that it is good to manage patches managed by wiki with git.09:21
iwamatsuI think that review results will be easier to manage.09:22
szliniwamatsu: I see, we can have some further discussions in f2f meeting.09:28
iwamatsuszlin: OK. Please tell me what you think is a problem about this. I think I would like to think by F2F.09:30
*** sangorrin has joined #cip09:35
sangorrinsorry, i was too concentrated and forgot about the irc meeting09:35
iwamatsusangorrin : Hi, IRC meeting was finished.09:36
szlinsangorrin: that's fine, do you have any update with swupdate or cip-core?09:39
sangorrinactually, I think that the mailing list is enough for cip-core and swupdate09:39
sangorrinthere we can discuss in depth09:39
szliniwamatsu: no problem with them, I just think we might need to have 2019 roadmap with kernel maintenance.09:41
szlinsangorrin: got it, thanks.09:42
iwamatsuszlin: OK09:44
patersonc_exit09:56
*** patersonc_ has quit IRC09:57
*** mungaip has quit IRC09:57
*** sangorrin has quit IRC10:01
patersoncRZ/G2 press release: https://www.renesas.com/us/en/about/press-center/news/2019/news20190221.html11:37
patersoncHello toscalix_ rajm , are either of you around?14:22
patersoncDo you know why AGPL v3.0 was chosen for B@D?14:23
patersonchttps://gitlab.com/cip-project/cip-testing/board-at-desk-single-dev/blob/master/LICENSE14:23
rajmpatersonc: think I remember the discussion but I no longer have the emails :(14:35
patersoncNo worries :)14:39
toscalix_patersonc:14:54
toscalix_at the beginning AGL and use shared the idea that something like B@D (which had a different name back then) would fit the dev workflow14:56
toscalix_reducing management costs14:57
toscalix_there is also the case in which you want to keep certain tests private14:58
toscalix_cases in which transparency is not the main gain factor14:58
toscalix_or distribution14:58
toscalix_because the tester and the analyzer of the results is the same person14:59
toscalix_then there was also the idea of the high learning curve that lava have, which could be reduced by using it in a controlled environment14:59
toscalix_so the idea of a local test solution where you could share results was shared15:00
toscalix_results, not infra or services15:00
toscalix_it was also an answer to the probable scenario in which devs from big companies would have problems accessing to certain distributed services due to IT policies15:01
toscalix_so they promoted a similar approach but different implementation15:02
*** toscalix_ has quit IRC17:48
*** tpollard has quit IRC18:07

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