From: agustin.benito@codethink.co.uk (Agustin Benito Bethencourt)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Use cases behind CIP story
Date: Thu, 15 Sep 2016 15:39:50 +0200 [thread overview]
Message-ID: <57DAA4A6.8090807@codethink.co.uk> (raw)
Hi,
CIP is doing a significant effort to be present in many events to
explain what are the motivations and goals of the group. The technical
activity is about to start so there is very little to show and it will
be the case for some time.
What can we focus on the coming months from the communication point of view?
I think there is a huge value in advertising the use cases that justify
the commitment from companies like Toshiba, Hitachi and Siemens in CIP.
Some of those use cases are completely unknown for a wide range of
developers, even many of those who are "Open Source veterans".
By exposing some of the challenges involved in those use cases CIP would
not just provide a meaningful inside about our environment but also the
opportunity to have a fruitful conversation with many of those engineers
who might think that CIP idea of a Super Long Term Support kernel
(system) is "anti-cultural".
So I would like to encourage CIP main drivers to provide and advertise
some of those unique use cases. I find them extremely interesting. I
hope many others will too.
Best Regards
--
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink
agustin.benito at codethink.co.uk
next reply other threads:[~2016-09-15 13:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-15 13:39 Agustin Benito Bethencourt [this message]
2016-09-15 15:23 ` [cip-dev] Use cases behind CIP story Noriaki Fukuyasu
2016-09-15 15:44 ` Paul Sherwood
2016-09-15 17:36 ` Agustin Benito Bethencourt
2016-09-16 8:04 ` KOBAYASHI Yoshitake
2016-09-16 10:30 ` Agustin Benito Bethencourt
2016-09-24 13:49 ` Gleim, Urs
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=57DAA4A6.8090807@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