From: domenico.andreoli@linux.com (Domenico Andreoli)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Introduction
Date: Thu, 15 Sep 2016 12:05:18 +0200 [thread overview]
Message-ID: <20160915100517.GA4650@localhost> (raw)
In-Reply-To: <57DA5C43.5010001@codethink.co.uk>
Hi all,
On Thu, Sep 15, 2016 at 10:30:59AM +0200, Agustin Benito Bethencourt wrote:
> On 15/09/16 08:50, Daniel Sangorrin wrote:
> >Hi Ben,
> >
> >>I've been working on the Linux kernel for about 10 years, including
> >>co-maintenance of Debian's kernel package for most of that time. Debian
> >>provides security support for each stable release for 5 years, and in
> >>support of that I backported many fixes to 2.6.32-longterm and took on
> >>maintenance of the 3.2-longterm and 3.16-longterm branches.
> >>
> >>I'm now adding another part-time role as lead kernel maintainer for the
> >>CIP. I look forward to working with you all to establish a project and
> >>process that can extend the support lifetime even further.
> >
> >Welcome to the CIP project. It's great to have such an experienced maintainer
> >in the project. Looking forward to working with you too!
>
> Daniel, can you tell us a little about yourself?
>
> My name is Agust?n Benito Bethencourt. I represent Codethink at CIP. I've
> managed teams-programs-projects for some years ago, the last in the open.
My name is Domenico Andreoli, I've been using Linux since 1995 and
actively contributed to Debian for about a decade. I've always worked
with Linux, on Linux, for Linux, thanks to Linux, mainly in the embedded
context but I learned that without the necessary shared values, Linux
is not fun at all.
Although I'm not really active nowdays, my FOSS imprinting imposes me
to at least observe and keep me informed. So I'm here, just representing
myself, with bags full of 2 cents.
> I am looking forward to find out how we are going to deal with this
> outstanding challenge, keeping a Linux system alive and healthy for many
> years in mission critical environments. I think it is an exciting one.
Yes, very exciting.
Do we recognize that big irons and small IoT leaves are in the same
need also here?
Kind regards,
Domenico
--
3B10 0CA1 8674 ACBA B4FE FCD2 CE5B CF17 9960 DE13
next prev parent reply other threads:[~2016-09-15 10:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 11:10 [cip-dev] Introduction Ben Hutchings
2016-09-15 6:50 ` Daniel Sangorrin
2016-09-15 8:30 ` Agustin Benito Bethencourt
2016-09-15 10:05 ` Domenico Andreoli [this message]
2016-09-15 16:17 ` Paul Sherwood
2016-09-15 16:44 ` Paul Sherwood
2016-09-15 22:31 ` Ben Hutchings
2016-09-16 5:03 ` Jan Kiszka
2016-09-16 5:15 ` Daniel Sangorrin
2016-09-16 7:40 ` Paul Sherwood
2016-09-16 9:24 ` Daniel Sangorrin
2016-09-16 0:45 ` Daniel Sangorrin
2016-09-16 7:53 ` KOBAYASHI Yoshitake
2016-09-24 12:50 ` Gleim, Urs
2016-09-15 12:12 ` Noriaki Fukuyasu
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=20160915100517.GA4650@localhost \
--to=domenico.andreoli@linux.com \
--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