DPDK community structure changes
 help / color / mirror / Atom feed
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
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>.


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)


I think this can be a good base for DPDK.



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 --]

  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:

* 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 \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DPDK community structure changes

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://inbox.dpdk.org/moving/0 moving/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 moving moving/ http://inbox.dpdk.org/moving \
	public-inbox-index moving

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git