Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/6] python-mwscrape: use documented license abbreviation
Date: Thu, 23 Mar 2017 10:00:41 +0100	[thread overview]
Message-ID: <20170323100041.45149296@free-electrons.com> (raw)
In-Reply-To: <3e6647c5-8b47-d1c1-a0fa-3cbf120759ec@mind.be>

Hello,

On Thu, 23 Mar 2017 09:25:11 +0100, Arnout Vandecappelle wrote:

> >> 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?  
> > 
> > That would have my approval, yes.  
> 
>  Indeed, I've been thinking about doing this.

OK, so let's just do it :)

The only thing that we might consider is the impact of this change for
our users. Are people parsing the CSV output, and checking if there is
no GPLv3 for example? Such checks would no longer match.

But longer term, I believe we will give our users a much more
logical/stable situation if we use SPDX codes everywhere rather than
the clunky mix we have today.

>  Now we just have to find a volunteer to construct the necessary sed magic :-)
> 
>  BTW I would propose to do this in one mega-patch that does mechanical
> substitution in all the .mk files (make sure the commit log contains the
> scriptlet that does it), and a second patch to fix the documentation. If it
> makes things easier, the mega-patch could be split up into separate patches for
> the different versions.

One patch for each license change would be nice IMO.

>  Oh, and for the documentation update: perhaps we should remove the list of
> licenses from our documentation, and instead refer only to spdx.org? I just
> notice now: we currently don't refer to SPDX at all in the documentation! That
> would explain Rahul's confusion about the proper license string...

Agreed.

>  Oh, and scancpan and scanpypi have to be updated as well.

Agreed.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-03-23  9:00 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
2017-03-22 22:32     ` Yann E. MORIN
2017-03-23  8:25       ` Arnout Vandecappelle
2017-03-23  9:00         ` Thomas Petazzoni [this message]
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=20170323100041.45149296@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