From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: Francois Ozog <francois.ozog@linaro.org>,
"moving@dpdk.org" <moving@dpdk.org>
Subject: Re: [dpdk-moving] [legal]
Date: Wed, 26 Oct 2016 15:49:51 +0000 [thread overview]
Message-ID: <3EB4FA525960D640B5BDFFD6A3D8912647AA187F@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <CAHFG_=WC9XGPKJJTiourVY0NO46Xrr7K+hJ3DCn6Q81KFu0vxA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1685 bytes --]
Hi Francois- Frederic,
A few questions to clarify my confusion:
· Is every DPDK contributor expected to sign one of these forms before being allowed to contribute code?
· Is every DPDK contributor expected to sign this form only once at the time of joining DPDK community or once for every patch its submits?
· What is wrong with the current DPDK.org signoff process which is the mechanism that certifies the origin of the code and the applicable license? Maybe we just need to expand the description on dpdk.org/dev a bit?
Before sending a patch, be sure that there is no licensing issue. The commit log must have a Signed-off-by line (--signoff option). It certifies that you wrote it and/or have the right to send it.
For a longer explanation, see the Developer's Certificate of Origin in Linux guidelines<http://www.kernel.org/doc/Documentation/SubmittingPatches>.
Regards,
Cristian
From: moving [mailto:moving-bounces@dpdk.org] On Behalf Of Francois Ozog
Sent: Wednesday, October 26, 2016 4:03 PM
To: moving@dpdk.org
Subject: [dpdk-moving] [legal]
As part of the legal work, here is the CLA that we use at Linaro and passed lawyers from many networking organizations (Cisco, Ericsson, Nokia, Huawei, ZTE, Broadcom, TI, Cavium, NXP, ENEA, WindRiver, Monta Vista, ARM)
https://drive.google.com/file/d/0B8xTReYFXqNtR0wwRUhqUEpwTUE/preview
I think this can be a good base for DPDK.
FF
--
[Linaro]<http://www.linaro.org/>
François-Frédéric Ozog | Director Linaro Networking Group
T: +33.67221.6485<tel:%2B33.67221.6485>
francois.ozog@linaro.org<mailto:francois.ozog@linaro.org> | Skype: ffozog
[-- Attachment #2: Type: text/html, Size: 12006 bytes --]
next prev parent reply other threads:[~2016-10-26 15:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 15:03 Francois Ozog
2016-10-26 15:49 ` Dumitrescu, Cristian [this message]
2016-10-26 16:47 ` Francois Ozog
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=3EB4FA525960D640B5BDFFD6A3D8912647AA187F@IRSMSX108.ger.corp.intel.com \
--to=cristian.dumitrescu@intel.com \
--cc=francois.ozog@linaro.org \
--cc=moving@dpdk.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;
as well as URLs for NNTP newsgroup(s).