public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: agustin.benito@codethink.co.uk (Agustin Benito Bethencourt)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Applying for CIP work
Date: Fri, 17 Nov 2017 12:36:57 +0100	[thread overview]
Message-ID: <5A0EC9D9.5070708@codethink.co.uk> (raw)
In-Reply-To: <DM5PR0501MB37344E0B91EF88799DA1A27BC52F0@DM5PR0501MB3734.namprd05.prod.outlook.com>

Hi Tiejun Chen,

On 17/11/17 08:05, Tiejun Chen wrote:
> Hi,
>
> I'm very interest in participating in CIP.
>
> Name: Tiejun Chen
> Company: VMware
> Position/Role: Staff Engineer/Technical Leader
> Why you are interested on: I'm working on some industrial IoT projects and explorations at VMware. It involves Linux development like trimming down/Paravirtualizing Preempt-RT Linux as Guest OS. And I'm also working on my personal Unikernel project, UniLinux, Unilernelize Linux. And,  I ever was responsible of Wind River Linux Kernel/BSP development including Preempt-RT kernel. After that I also working on enabling HW feature to KVM/Xen/Qemu at Intel OTC. So I'd like to continue this kind of job. Especially, I totally agree that we need this industrial grade Linux.

nice to meet you. Thanks for your kind offering.

Please check the following links in case you see something you might be 
interested on or call your attention:
* CIP kernel maintenance: 
https://wiki.linuxfoundation.org/civilinfrastructureplatform/cipkernelmaintenance

Maybe you can start by checking the kernel. Feel free to ask questions 
through this list. Ben Hutchings and Daniel Wagner are the maintainers. 
is the

* CIP Testing project: 
https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptesting

Maybe you can check the latest version and downloading B at D v1.0 if you 
are interested in kernel testing.

* CIP Core: 
https://wiki.linuxfoundation.org/civilinfrastructureplatform/cip-core

We released a few days ago a first attempt of what should become CIP 
base system. Feel free to check it out and let us know what you think 
about it.

Maybe you already have something else in mind where you can contribute 
to. In such case, please let us know. It would be great to find an area 
of interest for you that makes an impact in the project. This is 
frequently the hardest part about joining a project. Let's try to find 
it together.

By the way, is your unikernel project open? It would be interesting if 
you can provide us some links. It sounds interesting.

Best Regards


-- 
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink
agustin.benito at codethink.co.uk

  parent reply	other threads:[~2017-11-17 11:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-17  7:05 [cip-dev] Applying for CIP work Tiejun Chen
2017-11-17 11:35 ` Noriaki Fukuyasu
2017-11-18  6:47   ` Tiejun Chen
2017-11-23 11:23     ` Agustin Benito Bethencourt
2017-11-17 11:36 ` Agustin Benito Bethencourt [this message]
2017-11-18  7:01   ` Tiejun Chen
     [not found]     ` <DM5PR0501MB37344B4DBE0E2873078D6A47C5220@DM5PR0501MB3734.namprd05.prod.outlook.com>
2017-11-20 15:10       ` Agustin Benito Bethencourt
2017-11-20 16:44         ` Agustin Benito Bethencourt
2017-11-23 11:34     ` Agustin Benito Bethencourt
2017-11-24  8:48       ` Daniel Wagner

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=5A0EC9D9.5070708@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