DPDK community structure changes
 help / color / mirror / Atom feed
From: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
To: Michael Dolan <mdolan@linuxfoundation.org>
Cc: "moving@dpdk.org" <moving@dpdk.org>
Subject: [dpdk-moving] How do other BSD-licensed projects handle patent issues?
Date: Wed, 30 Nov 2016 16:21:18 +0000	[thread overview]
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BA67626B59@IRSMSX108.ger.corp.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1198 bytes --]

Mike,

At yesterday's call on moving DPDK to the Linux Foundation we had a discussion on the need for a CLA. The concern from some Linaro members with the current process (DCO and BSD license) is the lack of patent protection. We agreed on the call to check with you to see if the Linux Foundation have any guidance on whether this has been an issue with other BSD-licensed projects, and if so on how they dealt with it.

The majority opinion on the call was against a CLA because of the extra overhead required for contributors to get the CLA reviewed/approved by their legal teams before they can contribute to the project. An alternative solution if we do need patent protection would be to move to the Apache 2.0 license for new contributions. Both solutions (CLA and Apache 2.0) would only give partial coverage though, as neither would apply to the existing DPDK code base (trying to apply either retrospectively would be a big effort).

I realize this question may involve a legal opinion on software licensing, so it may be difficult to answer publically, but we agreed to check with you to see if the LF have any guidance which might help us to reach a conclusion on this.


Tim

[-- Attachment #2: Type: text/html, Size: 3138 bytes --]

                 reply	other threads:[~2016-11-30 16:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=26FA93C7ED1EAA44AB77D62FBE1D27BA67626B59@IRSMSX108.ger.corp.intel.com \
    --to=tim.odriscoll@intel.com \
    --cc=mdolan@linuxfoundation.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).