From: agustin.benito@codethink.co.uk (Agustin Benito Bethencourt)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Some outcome of the OSSJ event
Date: Wed, 14 Jun 2017 15:33:35 +0200 [thread overview]
Message-ID: <59413B2F.7000703@codethink.co.uk> (raw)
Hi,
1.- During the Open Source Summit Japan two blog post were published on
the CIP website apart from the B at D release announcement.
The first one was written by Nori:
https://www.cip-project.org/blog/2017/06/07/event-report-open-source-summit-japan-2017
I wrote the second one:
https://www.cip-project.org/blog/2017/06/01/board-at-desk-bd-and-forthcoming-challenges
You can follow these and other updates through our brand new twitter
account: @cip_project
2.- I was glad to see Renesas showing B at D at the CIP booth with their
RZ/G1M board. As I have mentioned before, CIP booth was one of the top
ones. I mean it. Congratulations to Hitachi, Toshiba, Plat'Home and
Renesas crew for the effort and the results.
3.- Check the slides from Yoshi's talk at OSSJ about CIP:
https://wiki.linuxfoundation.org/civilinfrastructureplatform/cipconferences
It was well attended.
4.- I really liked Wolfgang's talk providing an overview of Real Time
OSs. It required more time than he had but still was worth it. Let's
wait for the videos.
5.- The CIP TSC meeting was intense. Check the minutes:
https://wiki.linuxfoundation.org/civilinfrastructureplatform/tsc-meetings/tsc_mm_may302017
6.- Any feedback from the open workshop? I would like to hear what you
have to hear before providing mine :-)
Best Regards
--
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink
agustin.benito at codethink.co.uk
next reply other threads:[~2017-06-14 13:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 13:33 Agustin Benito Bethencourt [this message]
2017-06-14 13:48 ` [cip-dev] Some outcome of the OSSJ event Agustin Benito Bethencourt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=59413B2F.7000703@codethink.co.uk \
--to=agustin.benito@codethink.co.uk \
--cc=cip-dev@lists.cip-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox