DPDK community structure changes
 help / color / mirror / Atom feed
From: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
To: Dave Neary <dneary@redhat.com>,
	Michael Dolan <mdolan@linuxfoundation.org>,
	"moving@dpdk.org" <moving@dpdk.org>
Subject: Re: [dpdk-moving] Minutes from "Moving DPDK to Linux Foundation" call, November 29th
Date: Thu, 1 Dec 2016 20:33:06 +0000	[thread overview]
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BA676278FB@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <58406EC0.7000904@redhat.com>

> From: Dave Neary [mailto:dneary@redhat.com]
> Sent: Thursday, December 1, 2016 6:41 PM
> To: O'Driscoll, Tim <tim.odriscoll@intel.com>; Michael Dolan
> <mdolan@linuxfoundation.org>; moving@dpdk.org
> Subject: Re: [dpdk-moving] Minutes from "Moving DPDK to Linux
> Foundation" call, November 29th
> Hi,
> On 12/01/2016 12:40 PM, O'Driscoll, Tim wrote:
> > Thanks Mike. I realise you can’t say too much in public about what is
> essentially a legal issue.
> >
> > To summarise, these are the options we seem to have:
> >
> > 1. Continue with BSD license and DCO:
> > Advantages: Easy (nothing changes). This combination has worked well
> for several years with many companies contributing to the project and
> deploying DPDK-based solutions. No CLA required.
> > Disadvantages: Some Linaro members may not be able to contribute
> and/or deploy DPDK-based solutions.
> >
> > 2. Use Apache 2 for new contributions:
> > Advantages: It’s a fairly easy change. Provides patent protection for
> new contributions. No CLA required.
> > Disadvantages: Doesn’t cover the existing DPDK code so the actual
> benefit of this is very small.
> >
> > 3. Use Apache 2 and re-license existing code:
> > Advantages: Patent protection for everything. No CLA required.
> > Disadvantage: We need to re-license everything. I suspect that’s a big
> effort and it will be very difficult to get agreement from everybody
> who's contributed. We would also need to consider DPDK code that’s dual-
> licensed. We have some code that’s dual BSD-GPLv2. IANAL, and I'm far
> from an expert on SW licensing, but I think Apache 2 is not compatible
> with GPLv2, so this might need to become Apache 2/GPLv3.
> This might be a smaller task that you might think.
> We get to 99%+ with 7-8 companies. Each company will probably want to do
> a patent review on code they are contributing to see what they are
> licensing (and this can be a lengthy task, but for some of the bigger
> participants, this may already be an ongoing activity, or an acceptable
> level of risk). You only need agreement from copyright holders, and it
> is entirely possible that most participants work for companies that
> retain the copyright to contributions.

I did a quick scan of the copyright lines in the DPDK repo. It was only a quick look so this isn't an exhaustive list, it was just to get an idea of scale. Purely based on who has asserted copyright in the file headers, the people who would need to agree to re-licensing or applying a retrospective CLA include:

Vladimir Medvedkin
Akamai Technologies
Cavium Networks
Neil Horman
Freescale Semiconductor
Netronome Systems
John Linville
Ethan Zhuang
Hannes Frederic Sowa
Nuova Systems

      parent reply	other threads:[~2016-12-01 20:33 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-30 16:01 O'Driscoll, Tim
2016-11-30 17:10 ` Thomas Monjalon
2016-11-30 22:08   ` O'Driscoll, Tim
2016-12-01  9:20     ` Thomas Monjalon
2016-12-01  9:40       ` O'Driscoll, Tim
2016-11-30 17:39 ` Michael Dolan
2016-11-30 20:55   ` Dave Neary
2016-12-01 17:40   ` O'Driscoll, Tim
2016-12-01 17:46     ` Ed Warnicke
2016-12-01 18:01     ` Michael Dolan
2016-12-01 18:41     ` Dave Neary
2016-12-01 18:50       ` Dave Neary
2016-12-01 19:09         ` Francois Ozog
2016-12-01 19:44           ` Michael Dolan
2016-12-01 20:20             ` O'Driscoll, Tim
2016-12-01 20:47               ` Wiles, Keith
2016-12-01 21:33           ` O'Driscoll, Tim
2016-12-02  9:00             ` Francois Ozog
2016-12-01 20:33       ` O'Driscoll, Tim [this message]

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=26FA93C7ED1EAA44AB77D62FBE1D27BA676278FB@IRSMSX108.ger.corp.intel.com \
    --to=tim.odriscoll@intel.com \
    --cc=dneary@redhat.com \
    --cc=mdolan@linuxfoundation.org \
    --cc=moving@dpdk.org \


* 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).