CIP Technical Steering Committee Meeting

Date: 30 April, 2018

TSC members

• Members
  • Agustin Benito Bethencourt (Codethink) (Representative)
  • Chris Paterson (Renesas)
  • SZ Lin (MOXA) (Representative)
  • Masato Minda (Plat’Home) (Representative)
  • Jan Kiszka (Siemens)
  • Yoshi Kobayashi (Toshiba) (Representative) (Voting) - Chair
  • Jeff ErnstFriedman (The Linux Foundation)

• Contract with Thorsten Alteholz has been countersigned by the Linux Foundation regarding Debian Bug Report: 817286.
• AI (Yoshi): Contact to Shibata-san to coordinate a f2f meeting with Greg Kroah-Hartman at OSS Japan
• AI (CIP Testing): Renesas will setup the LAVA slave once the master is setup.
  • Renesas are currently gathering the required hardware.
• AI (CIP Core)(all): Making a list of packages (Due date: 31st March, 2018)
• AI (IEC62443): Request members ask business units for what documentation and best practices they can share with the rest of CIP, preferably in English to be shared with CIP.

Kernel maintenance and Testing

• Please check the report sent last week (weeks 14-17) to cip-dev
  • It includes the link to the last cip-dev meeting log
  • New CIP kernel released: 4.4.126-cip22
  • B@D supports Renesas board. Documentation published.
  • Test reports sent regularly to cip-testing-results ML

• Agreement among team members on sending the patch reviews first to cip-dev for Ben H. to evaluate. Once reviewed, send to LTS ML.
• Ben H. made available the mails. Waiting for the initial reviews from MOXA developers.
  • Moxa developers are reviewing patches of 4.4.129
    • The reviewing results will be sent out with problematic and non-problematic patches

• Learn LTS maintenance policy
• Need to decide which subsystem need to be maintained
• Next Thursday, they have a meeting with ben and Agustin
  • 4/12 irc:chat.freenode.net:6667/cip
  • Open to everyone
  • AI: Please join!

• How to review kernel patches in the team?
  • The current plan is to maintain the same plan via the LTS team. And take any platform specific needs into consideration
  • Either schedule to coincide with Ben’s trip to Japan or a person travel to Manchester
  • <NOTE>If you want to join Kernel maintenance team join the above IRC meeting.

• SZ posted a document to the cip-dev mail list.
• What and how to start with this topic
  • Might be focus to CRT and FSA (In EDSA 2.0, this is different name)
  • Testing
• This standard modifies every year.

• Base condition
  • Debian-LTS team maintain Debian packages which are categorized to “main”
  • CIP can submit a package list to Debian-LTS team to prioritize package
• Codethink does not have products so they will not submit a package list. They will participate in the process like everybody else though.