Date: 12 November 2018

TSC members

• Attendees
  • Agustin Benito Bethencourt (Codethink) (Representative)
  • Masashi Kudo (Cybertrust)
  • Nobuhiro Iwamatsu (Cybertrust) (Representative)
  • SZ Lin (MOXA) (Representative)
  • Kawai san (Hitachi)
  • Masato Minda (Plat’Home) (Representative)
  • Chris Paterson (Renesas)
  • Patryk Mungai (Renesas)
  • David Donegan (Renesas)
  • Wolfgang Mauerer (Siemens) (Representative) (Voting)
  • Dinesh Kumar (Toshiba)
  • Daniel Sangorrin (Toshiba)
  • Yoshi Kobayashi (Toshiba) (Representative) (Voting) - Chair
  • Jeff ErnstFriedman (The Linux Foundation)

• Non-attendees
  • Takehisa Katayama (Renesas) (Representative) (Voting)
  • Hiroshi Mine (Hitachi)
  • Takuo Koguchi (Hitachi)
  • Yu Kanechika (Renesas)
  • Jan Kiszka (Siemens) (Representative) (Voting)
  • Urs Gleim (Siemens)
  • Kazuhiro Hayashi (Toshiba)

• Agustin proposed on cip-dev creating a public Google calendar for CIP so more Members can publish and manage the calendar events and everybody can see it.
  • https://calendar.google.com/calendar?cid=N3ZrZnYyN210bG43czNoMXI5ajhkaGU2ZmdAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ
  • Does it okay for others? (Approved)
    • Yoshi will send invitations to all members
      • Please request me access permission with an email address for your Google account
  • The above calendar can be used as the following meetings
    • Weekly kernel meeting
    • Other workgroup meetings (Security workgroup, Software update workgroup)

• Yoshi proposes to have dedicated short meetings for each workgroup separately.
  • Kernel team already have a weekly meeting
  • Security workgroup
  • Software update workgroup
  • Testing
  • CIP Core
• Bi-weekly TSC meetings use to share status updates to other members
• Advantage
  • The meeting time easily changed the much suitable time for attendees
  • Easy to focus specific topic to discuss
  • (Can be accelerated each activity)
• Disadvantage
  • More meetings

• https://docs.google.com/presentation/d/1dGME3vAXMc-HVwXIgsG8hHHDPT3N2oWiKa1inLDLrAk/edit?usp=sharing
• Any feedback for the proposed architecture? (slide 5)
• Any opinions/experience with build automation? (Jenkins/GitLab etc.)
• Any plans to add more labs?
• Who needs a LAVA master account?
  • AI all: Email Chris if you want a LAVA account so you can run test jobs.

• How should cip-kernel-tests be structured?
• CIP image storage
  • Apparently, there is an S3 bucket, currently with public write access(?).
  • LF (Ryan) is still trying to find out more details.

• 4.19 is now LTS
  • Nobu will release 4.4 approx monthly basis
  • For 4.19, we currently do not have any patches for this version.
    • CIP may start 4.19 release (development) after 4.22, because of requirements for backporting (CIP has an upstream first policy.)
      • [Agustin] I am glad to hear there has been some evaluation on the effort required to bring part of the current support to the new kernel and the new platforms.
    • Dev branch: https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-4.19.y-cip
    • Patches CIP 4.19 are acceptable to cip-dev mail list
• Kernel review status
  • https://wiki.linuxfoundation.org/civilinfrastructureplatform/linux-4.4.y
• List of patches that failed to apply to 4.4-stable
  • https://wiki.linuxfoundation.org/civilinfrastructureplatform/linux-4.4-failed-patches

• Slides for this workgroup
  • https://docs.google.com/presentation/d/1TTn9ZObZ_XCH1iV4cPsF03LsWXyMtqBGxS8ra6tsfvc/edit?usp=sharing
• Katayama-san will lead this team
• Dinesh joins this workgroup
  • https://lists.cip-project.org/pipermail/cip-dev/2018-November/001645.html

• Daniel: the main goal of this project is to have an update mechanism that can be easily used with CIP core build tools. The main outcome will probably be recipes for the tiny profiles, Debian packages, and guidelines.
• Daniel: I first want to confirm the requirements of each member regarding software updates. I will prepare a short survey with multiple questions for that.