Date: 06 August, 2018

TSC members

• Attendees
  • Agustin Benito Bethencourt (Codethink) (Representative)
  • Masashi Kudo (Cybertrust)
  • HIroshi Mine (Hitachi)
  • Hidehiro Kawai (Hitachi) (Representative) (Voting)
  • Masato Minda (Plat’Home) (Representative)
  • Takehisa Katayama (Renesas) (Representative) (Voting)
  • Dinesh Kumar (Toshiba India)
  • Daniel Sangorrin (Toshiba)
  • Yoshi Kobayashi (Toshiba) (Representative) (Voting) - Chair

• Reproducible builds
  • See below
• Kernel development for next CIP kernel
  • (On going) MOXA: Send the board support package to upstream
    • SZ: Working in progress
• Spectre/Meltdown
  • Arm vulnerability list: https://developer.arm.com/support/arm-security-updates/speculative-processor-vulnerability
  • AI: tidy up this information
    • Discussion with partners internally
    • May be in the next meeting
• Kernel maintainer
  • AI(Yoshi): Arrange a F2F meeting at DebConf with Ben, Wolfgang, Iwamatsu-san. (DONE)
• CIP Core package list
  • AI(Daniel.S): Send to public mail list to get feedback from Ben. (DONE)
    • [cip-dev] [CIP Core] Criteria for prioritizing security fixes in Debian LTS
    • https://lists.cip-project.org/pipermail/cip-dev/2018-July/001398.htm
    • Already submitted to Reproducible builds
  • Agustin sent the link to the spreadsheet and the internal thread about the topic to Ben H. so he can get some background.
• DebConf: DONE
• WhitePaper
  • Still not available

• See above

• Work towards finalising selection?
• Minimal, optimal or others?
• Discussion: Which package list will be submitted to Debian LTS?
• Daniel S. has interesting ideas about how to prioritise the list of packages we have collected.
  • These ideas, based on prioritising the list through security related criteria will be explained in the cip-dev mailing list.
  • Ben H. will evaluate these criteria and its impact before attending to DebConf.
  • Based on Ben H. feedback, CIP will decide to contact the Freexian leads before the DebConf or not.
  • AI(Daniel.S): Send to public mail list to get feedback. (DONE)
  • (On going. See above)
• Comments
  • LTS: We should send package list with source packages
  • AI(Daniel S.): Ask to Raphael for the package list format.
  • Initial reference implementation with meta-debian however, we need to decide if we are going to use other build system (e.g. ISAR) for reference implementation and include more packages in the base layer.

• Discussed at DebConf to decide the structure of CIP kernel team
• CIP kernel team will focus both 4.4 and next CIP (4.20 or 5.0)
• CIP kernel team will structured with
  • 1 mentor (Ben H.)
  • 2 maintainers for CIP kernel (Iwamatsu-san), 1 maintainer for CIP-RT (Daniel. W)
  • Other members from each company such as MOXA and Toshiba (Daniel S.)
  • AI(Kernel team members): Define milestone for next CIP kernel
• Kernel configuration
  • Initial blacklist has already prepared by Ben
  • RT will be clarified by Daniel W.
  • Config vs. Board
    • To be discussed
• AI(Wolfgang): Contact to Daniel W. to become next CIP-RT maintainer
• AI(SZ): Ask to have weekly kernel team meeting at 5pm(JST) (Need to check time for other timezones)

US-West US-East UK DE TW JP

01:00   04:00   09:00   10:00   16:00   17:00

• Nothing out of DebConf 2018

• Containerization of B@D in progress.

• Trying to run Docker on CIP Core.
  • (Yoshi) Toshiba has an experience to install it but not sure for me how to do it. ;(
• Success to run Docker with CIP Core
• Next: Try to run EdgeX demo on the filesystem