From: "Radcliffe, Mark" <Mark.Radcliffe@dlapiper.com>
To: "bitcoin-dev@lists.linuxfoundation.org"
<bitcoin-dev@lists.linuxfoundation.org>
Cc: "Roay, Leslie" <Leslie.Roay@dlapiper.com>
Subject: [bitcoin-dev] Bitcoin Assistance
Date: Mon, 25 Sep 2017 21:53:40 +0000 [thread overview]
Message-ID: <E682AA2FC88ADD4589420BFC6BE3A92141FC460F@SANDMBX01v.piper.root.local> (raw)
[-- Attachment #1: Type: text/plain, Size: 2436 bytes --]
My apologies if this post has been answered, but I am new to the list. I am lawyer trying to understand the licensing of the Bitcoin core and I will be presenting in a webinar with Black Duck Software on Blockchain on September 28 (in case you are not familiar with them, Black Duck Software assists companies in managing their open source software resources). They have scanned the Bitcoin Core code for the open source licenses used in the codebase. I am enclosing a summary of the findings. I would be interested in communicating with the individuals who manage this codebase and can provide insight about the project manages contributions because the codebase includes projects with inconsistent licenses (for example, code licensed under the Apache Software License version 2 and GPLv2 cannot work together in some situations). Thanks in advance.
According to the scan, the code base includes code licensed under the following licenses:
Apache License 2.0
Boost Software License 1.0
BSD 2-clause "Simplified" License
BSD 3-clause "New" or "Revised" License
Creative Commons Attribution Share Alike 3.0
Expat License
GNU General Public License v2.0 or later
GNU General Public License v3.0 or later
GNU Lesser General Public License v2.1 or later
License for A fast alternative to the modulo reduction
License for atomic by Timm Kosse
MIT License
Public Domain
University of Illinois/NCSA Open Source License
Mark Radcliffe
Partner
T +1 650.833.2266
F +1 650.687.1222
M +1 650.521.5039
E mark.radcliffe@dlapiper.com <mailto:mark.radcliffe@dlapiper.com>
[DLA Piper Logo]
DLA Piper LLP (US)
2000 University Avenue
East Palo Alto, California 94303-2215
United States
www.dlapiper.com <http://www.dlapiper.com>
Please consider the environment before printing this email.
The information contained in this email may be confidential and/or legally privileged. It has been sent for the sole use of the intended recipient(s). If the reader of this message is not an intended recipient, you are hereby notified that any unauthorized review, use, disclosure, dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please reply to the sender and destroy all copies of the message. To contact us directly, send to postmaster@dlapiper.com. Thank you.
[-- Attachment #2: Type: text/html, Size: 14645 bytes --]
next reply other threads:[~2017-09-25 21:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 21:53 Radcliffe, Mark [this message]
2017-09-26 13:12 ` [bitcoin-dev] Bitcoin Assistance Omar Shibli
2017-09-27 21:20 ` Cory Fields
2017-09-27 21:54 ` Tim Ruffing
2017-09-27 22:21 ` Gregory Maxwell
2017-09-27 22:41 ` Tim Ruffing
2017-09-27 22:06 ` Gregory Maxwell
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=E682AA2FC88ADD4589420BFC6BE3A92141FC460F@SANDMBX01v.piper.root.local \
--to=mark.radcliffe@dlapiper.com \
--cc=Leslie.Roay@dlapiper.com \
--cc=bitcoin-dev@lists.linuxfoundation.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