From: agustin.benito@codethink.co.uk (Agustin Benito Bethencourt)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Introduction
Date: Thu, 15 Sep 2016 10:30:59 +0200 [thread overview]
Message-ID: <57DA5C43.5010001@codethink.co.uk> (raw)
In-Reply-To: <005e01d20f1d$64afb270$2e0f1750$@toshiba.co.jp>
Hi,
On 15/09/16 08:50, Daniel Sangorrin wrote:
> Hi Ben,
>
>> I've been asked to introduce myself to the list, before getting into
>> discussions. So here's a very brief summary.
>>
>> 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.
>>
>> Ben.
>
> 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.
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.
Best Regards
Agustin
>
> Best regards,
> Daniel
>
> --
> IoT Technology center
> Toshiba Corp. Industrial ICT solutions,
> Daniel SANGORRIN
>
>
>>
>> --
>> Ben Hutchings
>> Software Developer, Codethink Ltd.
>>
>>
>> _______________________________________________
>> cip-dev mailing list
>> cip-dev at lists.cip-project.org
>> https://lists.cip-project.org/mailman/listinfo/cip-dev
>
>
> _______________________________________________
> cip-dev mailing list
> cip-dev at lists.cip-project.org
> https://lists.cip-project.org/mailman/listinfo/cip-dev
>
--
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink
agustin.benito at codethink.co.uk
next prev parent reply other threads:[~2016-09-15 8:30 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 [this message]
2016-09-15 10:05 ` Domenico Andreoli
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=57DA5C43.5010001@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