IRC logs for #cip for Thursday, 2018-08-09

szlinI won't be able to attend IRC meeting today since I have a meeting with company guest this afternoon.03:00
szlingavin will be my backup.04:41
*** rajm has joined #cip07:28
*** toscalix has joined #cip07:51
* rajm ran a successful healthcheck on BBB with an email to the list07:53
*** patersonc has joined #cip07:56
*** iwamatsu_ has joined #cip07:58
toscalixbwh is on vacation07:59
gavinlaiso will we have a meeting today ?08:00
patersoncI have a couple of questions :)08:00
patersoncBut no need for a formal meeting if you don't want one :)08:01
*** yoshi has joined #cip08:02
iwamatsu_hi, all08:02
yoshihello08:02
patersoncMornin08:02
*** yoshi is now known as Guest9636908:02
Guest96369I'm still on the other meeting08:03
Guest96369oops. I am Yoshi08:03
*** Guest96369 has quit IRC08:04
*** yoshitake has joined #cip08:05
*** moxavictor has joined #cip08:07
toscalix#startmeeting08:08
toscalixsorry for the delay08:08
toscalixplease say hi08:08
yoshitakeHi08:08
moxavictorhi08:08
gavinlaihi08:08
patersonchi08:08
toscalix#topic new time for this meeting08:08
toscalixwe will have this meeting at this time from now on08:09
iwamatsu_hi08:09
toscalixso people from JST can join08:09
toscalixany objection?08:09
toscalix308:10
toscalix208:10
toscalix108:10
yoshitakefine with me08:10
patersoncThis time slot is fine with me08:10
moxavictoris ok for me08:10
toscalix#agreed the time for this meeting will be 8:00 UTC08:11
toscalixfor UK it will too early in winter, I am afraid08:11
toscalixbut we will propose a change then08:11
toscalix#topic AOB08:11
toscalixany question?08:12
patersoncHas a decision been made by Debian about their next Kernel version yet?08:12
toscalixit seems nobody has confirmation08:13
iwamatsu_I have not heard of it from Ben.08:13
patersoncOkay08:14
toscalixwill ask him08:14
patersoncThank you08:14
patersoncIs there a schedule for the first CIP-next Kernel release? (LTS 2018)08:14
toscalix#action ask ben hutchings about the confirmation of the next debian kernel. When will it happen?08:14
yoshitakeduring debconf, Ben mentioned to pick up next debian kernel version from next lts is reasonable. but not confirmed I think08:15
toscalixtoo early I think. The picture in the kernel community needs to be clearer before downstream takes decisions08:16
toscalixmy guess anyway08:16
patersoncOkay08:17
toscalixpatersonc: wouldn't be a good topic for the TSC?08:17
toscalixThis meeting should be moer about technical stuff, right?08:17
patersoncPerhaps, but perhaps the schedule should be lead by the maintainers08:17
toscalixyou have a point there08:18
toscalixYou are not being very lucky today with your questions08:18
patersonc:)08:19
toscalixyou will need to inisist08:19
toscalix:-)08:19
toscalixany other question?08:19
toscalixo/08:20
toscalixszlin: and I can add people to the caleendar event of this meeting so you get a notification08:20
toscalixszlin: at this new time, I cannot ensure I will be able to attend everytime08:20
toscalixcan you become by default the chair of this meeting08:21
toscalix?08:21
gavinlaiI will be his backup if he can not attend the meeting08:21
toscalixgavinlai: thanks. If you are not familiar with the debian meet bot, please read this: https://wiki.debian.org/MeetBot08:22
toscalixI haven't been consistant in sending the logs to the cip-dev mailing list adter the meeting08:22
toscalixyou can find them here: https://irclogs.baserock.org/cip/08:22
toscalixI will try to see if we can apply the debian meet bot08:23
toscalixto the channel08:23
toscalixwe are using the syntax anyway to search through logs08:23
toscalixmeetbot syntax08:23
gavinlaithat would be great : )08:23
toscalix#action apply the meetbot to this channel08:24
toscalix#agreed gavinlai will backup szlin as chair. toscalix steps back as chair08:24
toscalix_o_08:25
toscalixany other point to raise?08:25
toscalix_o/08:25
toscalix#topic DebConf 201808:26
toscalixany outcome from the meetings at DebConf 2018 you want to share in this forum?08:26
toscalix308:27
toscalix208:28
toscalix108:28
toscalixno other point from my side08:28
yoshitakenothing from my side for technical topics08:28
toscalixanybody?08:28
moxavictorno08:28
gavinlaiI'm currently working on script to check (not) support list for kernel configs08:29
gavinlaibwh provided a list as an example in YAML format: https://paste.baserock.org/noqafihoqa08:29
gavinlaiI put the not support list to list/4.4/not_support_list.yaml08:29
gavinlaiin this repo: https://gitlab.com/cip-project/cip-kernel/cip-kernel-config08:29
gavinlaiI assume we may have different (not) support list in different version08:30
gavinlaiIs my assumption is right?08:30
toscalixgavinlai: if you want to add a new list, create a MR. If you are not a member of gitlab, request it and I will add you08:30
toscalixgavinlai: that is the results of the configs sent by members some time ago08:31
toscalixthere might be more, yes08:31
gavinlaiI will create a MR for review process : )08:31
toscalixbased on those configs....ben tood decisions about some features to be supported or not08:32
toscalixs/tood/took08:32
toscalixgavinlai: new maintainers should be now in charge of these repos08:32
toscalixthe idea is that somebody else always needs to review the MR08:32
toscalixbut that is a policy maintainers should decide in this forum08:33
toscalixI am just informing about what it has been done up to now08:33
toscalixbut since we had only one person.... we did not applied for this repo08:33
gavinlaigot it08:34
toscalixany other point?08:34
toscalix308:35
toscalix208:35
toscalix108:35
toscalix#endmeeting08:35
toscalixbye08:35
moxavictorbye08:35
gavinlaiThanks08:35
moxavictorquit08:35
*** moxavictor has quit IRC08:35
iwamatsu_thanks08:35
patersoncThanks08:35
*** yoshitake has quit IRC09:01
toscalixiwamatsu_: somebody gave you maintainer access to the whole cip-project group in gitlab09:09
toscalixI assume you should have maintainer access in the kernel subgroup09:10
toscalixI changed it. If my assumption is incorrect, please let me know09:10
toscalixand will revert it09:10
iwamatsu_toscalix: thanks09:22
toscalixah, there are other people in the same case you are09:27
toscalixsent a proposal to cip-dev to manage permissions. We are growing so we need a policy, in my opinion09:28
*** toscalix has quit IRC09:30
*** toscalix has joined #cip09:30
*** toscalix has quit IRC13:30
* rajm updates #192 outlining necessary changes (discovered so far)13:32
*** toscalix has joined #cip14:03
*** toscalix has quit IRC14:03
*** toscalix has joined #cip14:03
*** toscalix has quit IRC14:04
*** rajm has quit IRC15:43
*** toscalix has joined #cip15:52
*** toscalix has quit IRC15:52
*** toscalix has joined #cip15:52
*** patersonc has quit IRC16:11
*** toscalix has quit IRC16:45
*** alicef[m] has joined #cip23:32

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