From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/6] python-mwscrape: use documented license abbreviation
Date: Wed, 22 Mar 2017 21:39:00 +0100 [thread overview]
Message-ID: <20170322213900.3ace3cc4@free-electrons.com> (raw)
In-Reply-To: <1490204935-13172-4-git-send-email-rahul.bedarkar@imgtec.com>
Hello,
On Wed, 22 Mar 2017 23:18:53 +0530, Rahul Bedarkar wrote:
> PYTHON_MWSCRAPE_VERSION = 6a58d7801eb1e884fd0516f1adbedbd4481c10e6
> PYTHON_MWSCRAPE_SITE = $(call github,itkach,mwscrape,$(PYTHON_MWSCRAPE_VERSION))
> -PYTHON_MWSCRAPE_LICENSE = MPL-2.0
> +PYTHON_MWSCRAPE_LICENSE = MPLv2.0
Well, our idea was to use the SPDX license codes as much as possible,
and MPL-2.0 is the correct SPDX license code for this license. However,
it is true we haven't used SPDX from the beginning, so we're using
GPLv2 everywhere, while SPDX uses GPL-2.0.
See:
https://spdx.org/licenses/
I think our idea was to keep using GPLv2/LGPLv2.1/GPLv3, but for all
other licenses, use the SPDX code as much as possible.
Maybe we should bite the bullet, and migrate all packages to use SPDX
license codes?
Arnout, Yann, Peter?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-03-22 20:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 17:48 [Buildroot] [PATCH 1/6] dbus-glib: fix legal info Rahul Bedarkar
2017-03-22 17:48 ` [Buildroot] [PATCH 2/6] dbus-triggerd: add license file Rahul Bedarkar
2017-03-31 7:08 ` Peter Korsgaard
2017-03-22 17:48 ` [Buildroot] [PATCH 3/6] taglib: fix legal info Rahul Bedarkar
2017-03-31 7:08 ` Peter Korsgaard
2017-03-22 17:48 ` [Buildroot] [PATCH 4/6] python-mwscrape: use documented license abbreviation Rahul Bedarkar
2017-03-22 20:39 ` Thomas Petazzoni [this message]
2017-03-22 22:32 ` Yann E. MORIN
2017-03-23 8:25 ` Arnout Vandecappelle
2017-03-23 9:00 ` Thomas Petazzoni
2017-03-23 18:01 ` Rahul Bedarkar
2017-03-28 6:44 ` Peter Korsgaard
2017-03-22 17:48 ` [Buildroot] [PATCH 5/6] python-certifi: " Rahul Bedarkar
2017-03-22 17:48 ` [Buildroot] [PATCH 6/6] perl-encode-detect: " Rahul Bedarkar
2017-03-26 20:51 ` [Buildroot] [PATCH 1/6] dbus-glib: fix legal info Thomas Petazzoni
2017-03-31 7:07 ` Peter Korsgaard
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=20170322213900.3ace3cc4@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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