User Tools

Site Tools


civilinfrastructureplatform:tsc-meetings:tsc_mm_oct162017

CIP Technical Steering Committee Meeting

Date: 16 October, 2017

Roll Call

  • Agustin Benito Bethencourt (Codethink)
  • Annie Fisher (LF)
  • Noriaki Fukuyasu (LF)
  • Hiroshi Mine (Hitachi)
  • Hidehiko Kawai (Hitachi)
  • Masato Minda (Plat’Home)
  • Takehisa Katayama (Renesas)
  • Chris Paterson (Renesas)
  • Wolfgang Mauerer(Siemens)
  • Daniel Sangorrin (Toshiba)
  • Yoshi Kobayashi (Toshiba)

Agenda

  • Roll Call
  • Action items
  • CIP core project launch approval
  • Agenda discussion for F2F meeting in Prague

CIP Core project launch approval

  • GB approved to use MIT license for CIP core
  • To move forward, TSC chair request for approval to TSC voting members
    • MOTION: “CIP TSC approves to launch CIP core as a new official project.”
    • Move: Yoshi
    • Second: Wolfgang
    • Motion is hereby passed.
  • Actions:
    • Move to repo to the CIP Project and rename it to CIP Core
    • Press Announcement: Laura will double check with Mae if this will be a press announcement or just blog post.
    • Updating document to replace “Project X” with “CIP Core”.

Agenda discussion for F2F meeting

  • Functional safety (45 minutes)
    • Koguchi-san will invite a person
  • LTS discussion with Greg KH (30-45 minutes)
  • CIP Core
  • Yocto discussion
  • CIP Testing project next steps
    • Revision of current strategy
    • B@D development
    • Potential alternatives based on the strategy.
    • Other topics
  • Next topic to be focused
  • The following topics will be discussed separately
    • Y2038 (Monday 11:45-12:45) @ (ROOM) : 15 people appx
  • [Action items]
    • Nori invite Greg KH to TSC meeting.
    • Nori prepare slides for functional safety.
    • Yoshi makes time table of TSC meeting.

Updates and Discussions

Y2038

  • [Agustin] Meeting with Arnd during ELCE closed.
    • Y2038 (Monday 11:45-12:45) @ (ROOM) : 15 people appx
    • Confirmed Arnd presence.
    • Call for agenda topics.
      • Depending on the agenda Arnd and Agustin are willing to invite further experts.
    • Siemens and Renesas, Toshiba has confirmed the presence.
    • Should we invite people interested from other LF group
    • [AI] Members should should ask developers within the companies if they would have any questions to Agustin and Arnd prior to the meeting.
      • [Agustin] No further agenda points proposal received.

CIP Core update 1/2

CIP Core update 2/2

Yocto Distribution

  • [YOSHI] This topic will be discussed in TSC F2F meeting.
  • Sean Hudson started a conversation on cip-dev with regards to creating a meta-cip layer to work with OpenEmbedded.
  • Does the CIP project want to start work on this officially? Or leave it to those outside of the project to come up with their own implementation?
    • [YOSHI] This is not decided yet. I replied to Sean as he follows:
      • The goal here is to see if we can actually build file system based on CIP base-layer and Yocto layers by using Poky. Do the same thing as the Project X does but using CIP kernel and limited number of Debian source code AND OE layers. To make it a bit clearer, I assume the combination as the follows for the goal: CIP base-layer (Kernel + limited number of long-term supported OSS packages from Debian) + Poky + OE-layers But the following combination might be a good at starting point. CIP kernel + Poky + OE-layer
  • Originally it was the aim of the project to support both Debian and Yocto distributions.
    • [YOSHI] This is not exactly correct. Originally, Project X focus to make minimal deployable file system image by using Bitbake or Debian build system and Debian source code with CIP kernel. It was not aim to support Yocto distribution itself, because we are difficult to support two code base.
  • Options to add Yocto support:
    • a) Create a new project like Project-X (Project-Y?)
      • This would keep both distributions completely separate
    • b) Enhance Project-X (CIP-Core) with a meta-cip layer
      • This would allow both distributions to be “CIP-Core”, but I’m not sure how such an implementation would work.
        • Kas project could be an option to implement both in one.

LTS to be supported for 6 years?

Kernel Maintenance

  • Report from week 40 and 41 sent to cip-dev ML. Please review it
    • Focus on merging the latest patches and releasing the new kernel.

CIP Testing

Board @ Desk

  • Report from week 40 and 41 sent to cip-dev ML. Please review it
  • Release this Wednesday Oct 18th at 12:00 UTC

ELC-E preparation

    • Please sign up for booth management (2 persons for each time slot).
    • Action: Annie will send out the spreadsheet via email this week to remind members to sign-up for a shift.
    • Tom Pollard joined to help the current team with the preparations, specially the setup of the environment and supporting Renesas board
  • CIP kernel maintenance meeting. (CIP private/internal)
    • Proposal: if a slot in the afternoon is needed, we can merge this meeting with the kernel Q&A at 17:30
    • Driven by Daniel W. and Ben H.
    • Meanwhile Robert and I will work on the room set up if needed.
    • At 17:30 led by Ben H.
    • Open meeting. Content will be announced this week.
      • It will about going through the ongoing tasks that Ben H. is going over. Nothing fancy here but interesting for future CIP kernel maintainers.
    • Open meeting to bring new people to CIP and answer questions about our current activities and future plans.
    • [ToDo] Announce this meeting at the CIP talk
    • Announced.
      • When: Tuesday October 24th from 13:00 to 14:00 hours
      • Where: Liben Room, Mezzanine Level al ELCE venue in Prague CZ.
    • Need to announce it during the CIP talk which is immediately before.
  • Demo @ booth
civilinfrastructureplatform/tsc-meetings/tsc_mm_oct162017.txt · Last modified: 2017/10/30 07:32 by yoshi