From: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
To: Michael Dolan <mdolan@linuxfoundation.org>,
Francois Ozog <francois.ozog@linaro.org>
Cc: Dave Neary <dneary@redhat.com>, "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:20:46 +0000 [thread overview]
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BA676278D4@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <CAFV=PSF3jGoz8cmuf1_3_HVZRk4ovCNr2yK6EpFFkC_c0MSNAw@mail.gmail.com>
> From: Michael Dolan [mailto:mdolan@linuxfoundation.org]
> Sent: Thursday, December 1, 2016 7:45 PM
> To: Francois Ozog <francois.ozog@linaro.org>
> Cc: Dave Neary <dneary@redhat.com>; O'Driscoll, Tim <tim.odriscoll@intel.com>; moving@dpdk.org
> Subject: Re: [dpdk-moving] Minutes from "Moving DPDK to Linux Foundation" call, November 29th
>
> Can we setup a call next week with the counsel for the major contributors? If it's 7-9 companies this shouldn't be difficult to resolve. I hate to be difficult but this topic will not be resolved on a public mailing list unless everyone is willing to punt on the issue until there is a governing board to make the decision.
>
> I am willing to schedule and host the call. I just need the names and emails of your counsel. Please email me directly and not on the list.
We could do that, but I suspect that if we do we're heading into months of legal debate. The intent of the initiative to move the project to LF was to do so with minimal changes. The adoption of a CLA and/or a licensing change clearly doesn't fall into that category.
You have a valid point that this is a significant issue and we shouldn't rush into a decision on it, or make one without fully considering the legal implications. So, my preference would be to use the charter to document the current process (BSD license and DCO). Then, when we have a governing board in place, anybody that wants to can propose a change and it can be dealt with by the board.
What do others think?
next prev parent reply other threads:[~2016-12-01 20:20 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 [this message]
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=26FA93C7ED1EAA44AB77D62FBE1D27BA676278D4@IRSMSX108.ger.corp.intel.com \
--to=tim.odriscoll@intel.com \
--cc=dneary@redhat.com \
--cc=francois.ozog@linaro.org \
--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).