====== CIP Technical Steering Committee Meeting ======

Date: 17 April, 2017

===== Roll Call =====

  * Noriaki Fukuyasu (The Linux Foundation)
  * Annie Fisher (The Linux Foundation)
  * Hiroshi Mine (Hitachi)
  * Hidehiro Kawai (Hitachi)
  * Takehisa Katayama (Renesas)
  * Yoshi Kobayashi (Toshiba)
  * Daniel Sangorrin (Toshiba)
  * Agustin Benito Bethencourt (Codethink) 
  * Masato Minda (Plat’Home)

===== Agenda =====

  * Roll Call
  * Updates and Discussions
    * Whitepaper Status
    * OSSJ preparation
    * Preparation for CIP workshop on 30th May
    * DebConf
    * Board @desk - Single dev. first release 
    * ProjectX

===== Updates and Discussions =====

==== White Paper Status ====

  * Wolfgang has finished to write a short version (4 pages instead of 7).
    * All processes were also finished.
    * Version for print will be provided on Tue after easter holidays
    * Nori’s staff will provide a Japanese translation for OSSJ
  * **AI: Publish it. When: It will take around a week after the print-ready version of the whitepaper.**
  * **AI: Blog post and Twitter promotion on Whitepapers. Nori will ask Wolfgang to write up something for the blog post.**

==== OSSJ preparation ====

  * Booth and demo preparation.
    * Call for Demo
      * __Requirements:  All Demo should run with CIP kernel.__
      * (minmin) I will prepare the IoT demo. But if I don't have enough time, it will be same as ELC Portland. 
      * (Toshiba) asking to have a same demo (PP simulator with CIP kernel)
      * Codethink will try to somehow demo the cip kernel being tested.
      * **AI(ALL): Propose ideas for demo booth.**
  * (Wolfgang) We should announce the CIP member talks on our public channels (blog, twitter etc.), AFAIK, Yoshi and Wolfgang will give talks related to CIP topics. Anyone else?
    * **AI(LF): Tweet on CIP speeches and demo showcase.**

==== Preparation for CIP meeting on 30th May ====

  * Place: Tokyo Conference Center Ariake 
  * Schedule
    * 9:00-11:00   Board member meeting
    * 11:00-17:00 TSC meeting (CIP workshop)
    * 17:00-18:00 CIP Booth setup

==== DebConf ====

  * **(AI: Yoshi) Submit a talk to Debconf  (Deadline: 3rd June)**

==== CIP Kernel Development ====

  * Kernel security tracker
    * Ben H. wrote a template and implemented importers
  * Kernel feature support
    * Ben collected and began reviewing members' configurations
    * AI: Continue to provide kernel config(s) to mailing list for further discussion
      * Plat’Home send a config
        * [[https://lists.cip-project.org/pipermail/cip-dev/2017-April/000205.html|https://lists.cip-project.org/pipermail/cip-dev/2017-April/000205.html]]
      * Jan send more configs
        * [[https://lists.cip-project.org/pipermail/cip-dev/2017-April/000204.html|https://lists.cip-project.org/pipermail/cip-dev/2017-April/000204.html]] 
    * AI: Ben will send out some more questions about the specific features.
      * Agustin: WIP
  * Ben reviewed changes for Linux 4.4.60 for next release

==== Board @ Desk status ====

  * Trying to adapt the upstream updated KernelCI. 
    * Some of the upstream changes impacted to Board at Desk.
  * Please refer the latest report at [[https://lists.cip-project.org/pipermail/cip-dev/2017-April/000200.html|https://lists.cip-project.org/pipermail/cip-dev/2017-April/000200.html]]
    * Update:
      * the last issue related with kernelci update has been fixed.
      * We are back to the point previous to the update with some improvements.
      * We have created a VM  that includes the latest fixes: [[http://download.cip-project.org/bad-sd/bad-sd_0_9_beta_2017_04_12.box|http://download.cip-project.org/bad-sd/bad-sd_0_9_beta_2017_04_12.box]] 
        * We want to properly configure the download service (S3) before spreading the link. We want to support https, at least.
      * Improvements in the deployment of the VM.

==== ProjectX ====

  * Koguchi-san already provided the Kernel recipe for BBB and Cyclone-V
  * Now, Project X works on x86_64, BBB, Altera Cyclone-V.
    * But it includes limited features, like a template.
  * What’s next?
    * Have a rootfs for testing?
    * Create a Debian’s binary based rootfs?

[[.|Back to the parent page]]