DPDK community structure changes
 help / color / mirror / Atom feed
From: Michael Dolan <mdolan@linuxfoundation.org>
To: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
Cc: "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 13:01:16 -0500
Message-ID: <CAFV=PSE1LHNGMCzpze8fPjMfj49h8+ntp4piumUoumLivch_pA@mail.gmail.com> (raw)
In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA676277F4@IRSMSX108.ger.corp.intel.com>

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

> ...
> Note that I’m assuming that the combination of Apache 2 and a CLA isn't an
> option because this seems redundant as both include patent protection.
> Maybe there are other reasons that would make this a valid combination
> though.
> ...
>

Tim, I think this is a perfect example of why I'm suggesting we get all of
your counsel on a call together to discuss. The default for Apache 2 was to
use a CLA in combination. That's precisely why the Apache CCLA and ICLA
agreements exist.

The issue I think some are missing is not all CLAs are the same and have
very different purposes. Node.js under Joyent's stewardship tried to patch
over the BSD license with a CLA and it caused a lot of issues and they
ultimately abandoned the CLA entirely - but now they don't have the
protections offered by the CLA going forward and have to figure out what to
do.

The best path forward IMO is to have everyone on a call with their counsel
and we can discuss how to move forward. I don't have confidence everyone
here understands the full implications of what their being asked to decide
- this isn't a trivial detail to change things. Relaying to counsel and
coming back with an answer is also not ideal as those who are entrusted to
provide legal guidance are not at the table of discussion and may not
understand the full context.

A further option is to have the Governing Board resolve this later. We'll
know who the decision makers are and can work with their counsel to figure
this out if it's an issue the GB thinks needs addressed.

-- Mike


>
> Tim
>
> > From: Michael Dolan [mailto:mdolan@linuxfoundation.org]
> > Sent: Wednesday, November 30, 2016 5:39 PM
> > To: O'Driscoll, Tim <tim.odriscoll@intel.com>
> > Cc: moving@dpdk.org
> > Subject: Re: [dpdk-moving] Minutes from "Moving DPDK to Linux
> Foundation" call, November 29th
> >
> > Hi Tim, sorry I couldn't make it with a LF Board meeting conflict
> yesterday. As for 1), most/all of our projects facing this issue decide to
> go Apache 2. A CLA is less preferably particularly with the BSD license.
> Where we do use a CLA on a project it's usually the same as the Apache
> CCLA/ICLA and that combined with the BSD license will I'm fairly certain
> not achieve what Linaro legal is probably concerned about.
> >
> > My guess is the members here are 90% or more of the contributors and a
> relicensing effort could be done within a reasonable timeframe. The project
> could also start under the LF with all new contributions under the Apache 2
> license which is compatible with all prior BSD contributions. Or you could
> just required Apache 2 on any future contributions and keep the prior BSD
> if the relicensing is not agreeable to others.
> >
> > Just some thoughts on how other projects tackled this question. It would
> probably be best if we push any further discussion on this to a small group
> of your legal counsel as the various levers have different implications and
> I'm uncomfortable continuing this discussion without your counsel being
> involved.
> >
> > Thanks,
> >
> > Mike
> >
>

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

  parent reply	other threads:[~2016-12-01 18:01 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 [this message]
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

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='CAFV=PSE1LHNGMCzpze8fPjMfj49h8+ntp4piumUoumLivch_pA@mail.gmail.com' \
    --to=mdolan@linuxfoundation.org \
    --cc=moving@dpdk.org \
    --cc=tim.odriscoll@intel.com \
    /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

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 \
		moving@dpdk.org
	public-inbox-index moving

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.moving


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