From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 00/34] License updates
Date: Wed, 29 May 2019 11:38:45 +0200 [thread overview]
Message-ID: <20190529093845.icn4efnvwqbtkrsv@pengutronix.de> (raw)
In-Reply-To: <20190510092434.15019-1-ada@thorsis.com>
Hi,
Thanks for this series. I've looked at all of the patches now and I've done
some checking that this makes sense. I've had comments for some of them.
I'm currently running build tests for the rest (this is mostly to check
that the md5sums are ok).
These should hit master soon. I hope I got all of them, but you should
probably rebase your brach once I've pushed the initial batch.
Michael
On Fri, May 10, 2019 at 11:24:00AM +0200, Alexander Dahl wrote:
> I reviewed lots of packages for licensing issues and this patch series
> is the outcome. There are basically three types of patches:
>
> 1) Add license information where it was missing
> 2) Add license file hashes for otherwise already correct packages
> 3) Fix license information where the given licenses are/became wrong
> 4) Combinations of the above
>
> When mistakes were traceable to specific changesets, I added Fixes:
> lines and the original author in Cc. This is not meant to offend
> anyone, but to get a second opinion or review. This legal stuff is
> hard, I get headaches from this. This is also why some commit messages
> are longer than others.
>
> Please review these patches carefully, I'm no lawyer. Some small
> upstream projects make it easy to check each file, some would require
> to inspect over 100 source files, if you want to do it right. Almost
> none so far uses those still quite new SPDX license identifiers in the
> file headers (sudo does in a version not yet available in ptxdist).
>
> Some patches contain additional notes with remarks or questions.
>
> Thanks to Roland Hieber for his SPDX matching tool [1], which made all
> this a lot easier. You should however not solely depend on that tool,
> but have a look into the current SPDX license list [3] and exceptions
> [4].
>
> Also helpful was the Debian project. They carry detailed copyright
> information with their packages (well, most of them), e.g.:
>
> https://metadata.ftp-master.debian.org/changelogs//main/u/util-linux/util-linux_2.33.1-0.1_copyright
>
> And I also had a look on the license information the buildroot project
> [2] has in its packages. Maybe someone wants to send them patches as
> well. ;-)
>
> Some additional notes on which packages should be reviewed and
> probably updated:
>
> * U-Boot
> * util-linux-ng
>
> Let me know, if I should reorder or change or squash something, but I
> would also be happy, if just a subset would be applied.
>
> Greets
> Alex
>
> P.S.: For people enjoying a long read about this whole license mess,
> here you go: https://invisible-island.net/ncurses/ncurses-license.html
>
> P.P.S.: If you did not already know, the FSFE started the REUSE
> initiative to make all this somewhat easier, so if you're an upstream
> developer, have a look: https://reuse.software/
>
> [1] https://github.com/rohieb/spdx-license-match
> [2] https://buildroot.org/
> [3] https://spdx.org/licenses/
> [4] https://spdx.org/licenses/exceptions-index.html
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2019-05-29 9:38 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 9:24 Alexander Dahl
2019-05-10 9:24 ` [ptxdist] [PATCH 01/34] at: Add license identifiers and hashes Alexander Dahl
2019-05-10 9:24 ` [ptxdist] [PATCH 02/34] at91bootstrap: Add license information Alexander Dahl
2019-05-10 9:24 ` [ptxdist] [PATCH 03/34] boost: Add license file hash Alexander Dahl
2019-05-10 9:24 ` [ptxdist] [PATCH 04/34] busybox: " Alexander Dahl
2019-05-10 9:24 ` [ptxdist] [PATCH 05/34] libnl3: Fix license and add license hash Alexander Dahl
2019-05-28 21:43 ` Roland Hieber
2019-05-29 7:12 ` Michael Olbrich
2019-06-06 13:40 ` Alexander Dahl
2019-05-10 9:24 ` [ptxdist] [PATCH 06/34] dropbear: Add license information Alexander Dahl
2019-05-13 9:42 ` Roland Hieber
2019-05-29 7:49 ` Michael Olbrich
2019-05-29 8:00 ` Alexander Dahl
2019-05-29 9:12 ` Michael Olbrich
2019-05-29 9:31 ` Roland Hieber
2019-05-29 9:40 ` Michael Olbrich
2020-03-10 14:23 ` Alexander Dahl
2020-03-10 14:31 ` Roland Hieber
2019-05-10 9:24 ` [ptxdist] [PATCH 07/34] figlet: Fix license and add license file hashes Alexander Dahl
2019-05-13 9:41 ` Roland Hieber
2019-05-13 10:20 ` Alexander Dahl
2019-05-22 11:56 ` Roland Hieber
2019-05-29 7:29 ` Michael Olbrich
2019-05-10 9:24 ` [ptxdist] [PATCH 08/34] flex: Fix license and add license file hash Alexander Dahl
2019-05-28 21:07 ` Roland Hieber
2019-05-29 7:03 ` Michael Olbrich
2019-05-29 9:35 ` Roland Hieber
2019-05-10 9:24 ` [ptxdist] [PATCH 09/34] json-c: Add " Alexander Dahl
2019-05-10 9:24 ` [ptxdist] [PATCH 10/34] coreutils: " Alexander Dahl
2019-05-29 7:53 ` Michael Olbrich
2019-05-10 9:24 ` [ptxdist] [PATCH 11/34] libarchive: " Alexander Dahl
2019-05-29 7:56 ` Michael Olbrich
2019-05-10 9:24 ` [ptxdist] [PATCH 12/34] libfaketime: " Alexander Dahl
2019-05-10 9:24 ` [ptxdist] [PATCH 13/34] libgmp: Fix license Alexander Dahl
2019-05-10 9:24 ` [ptxdist] [PATCH 14/34] libgmp: Add license file hashes Alexander Dahl
2019-05-10 9:24 ` [ptxdist] [PATCH 15/34] libmnl: Fix license and add " Alexander Dahl
2019-05-10 9:24 ` [ptxdist] [PATCH 16/34] libmodbus3: " Alexander Dahl
2019-05-29 8:04 ` Michael Olbrich
2019-05-29 8:13 ` Alexander Dahl
2019-05-10 9:24 ` [ptxdist] [PATCH 17/34] libnet: Add license information Alexander Dahl
2019-05-29 8:10 ` Michael Olbrich
2019-05-10 9:24 ` [ptxdist] [PATCH 18/34] libnftnl: Fix license and add license file hash Alexander Dahl
2019-05-10 9:24 ` [ptxdist] [PATCH 19/34] libpcap: " Alexander Dahl
2019-05-29 8:22 ` Michael Olbrich
2019-05-10 9:24 ` [ptxdist] [PATCH 20/34] libpopt: Add " Alexander Dahl
2019-05-10 9:24 ` [ptxdist] [PATCH 21/34] libxml2: Fix license and add " Alexander Dahl
2019-05-29 8:28 ` Michael Olbrich
2019-05-10 9:24 ` [ptxdist] [PATCH 22/34] lighttpd: Fix licenses and add more license file hashes Alexander Dahl
2019-05-10 9:24 ` [ptxdist] [PATCH 23/34] lm_sensors: Add " Alexander Dahl
2019-05-10 9:24 ` [ptxdist] [PATCH 24/34] log4cplus: Fix licenses and add license file hash Alexander Dahl
2019-05-29 9:09 ` Michael Olbrich
2019-05-10 9:24 ` [ptxdist] [PATCH 25/34] mtd-utils: Add " Alexander Dahl
2019-05-10 9:24 ` [ptxdist] [PATCH 26/34] ncurses: Use 'COPYING' for " Alexander Dahl
2019-05-10 9:24 ` [ptxdist] [PATCH 27/34] net-snmp: Fix licenses and add " Alexander Dahl
2019-05-10 9:24 ` [ptxdist] [PATCH 28/34] nftables: Add " Alexander Dahl
2019-05-10 9:24 ` [ptxdist] [PATCH 29/34] opkg: " Alexander Dahl
2019-05-10 9:24 ` [ptxdist] [PATCH 30/34] readline: " Alexander Dahl
2019-05-10 9:24 ` [ptxdist] [PATCH 31/34] rt-tests: Fix licenses and add " Alexander Dahl
2019-05-10 9:24 ` [ptxdist] [PATCH 32/34] sudo: " Alexander Dahl
2019-05-10 9:24 ` [ptxdist] [PATCH 33/34] tree: Fix licenses and add license file hashes Alexander Dahl
2019-05-10 9:24 ` [ptxdist] [PATCH 34/34] u-boot-tools: " Alexander Dahl
2019-05-29 9:38 ` Michael Olbrich [this message]
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=20190529093845.icn4efnvwqbtkrsv@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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