mailarchive of the pengutronix oss-tools mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Roland Hieber <rhi@pengutronix.de>
Cc: oss-tools@pengutronix.de,
	"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Subject: Re: [OSS-Tools] [PATCH dt-utils 1/4] treewide: add SPDX identifiers to files with GPL-2.0-or-later license
Date: Tue, 30 Mar 2021 19:31:24 +0200	[thread overview]
Message-ID: <3286977b-06a6-539d-f36f-35385671acca@pengutronix.de> (raw)
In-Reply-To: <20210330155357.ubi6qfqi7uyy2c4j@pengutronix.de>

Hello Roland,

On 30.03.21 17:53, Roland Hieber wrote:
> On Tue, Mar 30, 2021 at 03:50:19PM +0200, Ahmad Fatoum wrote:
>> Hello,
>>
>> On 30.03.21 15:30, Uwe Kleine-König wrote:
>>> Hello,
>>>
>>> On Tue, Mar 30, 2021 at 01:22:26PM +0200, Ahmad Fatoum wrote:
>>>> On 30.03.21 13:08, Roland Hieber wrote:
>>>>> Uwe, could I get a Reviewed-by from you for these four patches? :-)
>>>>
>>>> We must still carry the full license texts in the project (cf. Linux
>>>> LICENSES/). This is missing here, no?
>>>
>>> well, it depends on what you want to achieve. If you want to become SPDX
>>> conformant this is indeed necessary. IMHO the conversion from several
>>> different boilerplate license specifications to a single line is
>>> beneficial even if the full licenses are not (yet) in the project.
>>
>> If the code says that the license terms need to be distributed along
>> with the software, you are violating the license terms, if you don't
>> abide by this. This is unrelated to SPDX-Conformance.
> 
> Nothing in the license headers or in the GPL or in the Zlib license says
> that we have to distribute the license text along with the source code.
> On the contrary, there are even some versions of GPL license headers
> that have a clause "if you didn't a license text along with the
> software, write to the FSF at $ADDRESS".

If Zlib says "This notice may not be removed or altered from any
source distribution.", I interpret this as meaning that we need to ship
the full text as part of the source distribution and only a
SPDX-License-Identifier that can be looked up on a website somewhere doesn't
suffice.

> But it is needed for REUSE [1] compliance, so I intend to move COPYING
> into LICENSES/ nevertheless, and add the Zlib too. Thanks for catching
> this.

:)

Cheers,
Ahmad

> 
> [1]: https://reuse.software/
> 
>  - Roland
> 
>>> So I don't regret having given my Review-tags.
>>
>> Reviewing is fine, but before applying license text removal, the full
>> license texts need to be located in full somewhere in the source tree.
>>
>> Cheers,
>> Ahmad
>>
>>>
>>> Best regards
>>> Uwe
>>>
>>
>> -- 
>> Pengutronix e.K.                           |                             |
>> Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
>> 31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
>> Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |
>>
> 

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
OSS-Tools mailing list
OSS-Tools@pengutronix.de

  reply	other threads:[~2021-03-30 17:31 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-26 21:06 Roland Hieber
2021-03-26 21:06 ` [OSS-Tools] [PATCH dt-utils 2/4] treewide: add SPDX identifiers to files with GPL-2.0-only license Roland Hieber
2021-03-30 12:50   ` Uwe Kleine-König
2021-03-26 21:06 ` [OSS-Tools] [PATCH dt-utils 3/4] treewide: add SPDX identifier to files with Zlib license Roland Hieber
2021-03-30 12:55   ` Uwe Kleine-König
2021-03-26 21:06 ` [OSS-Tools] [PATCH dt-utils 4/4] treewide: add SPDX identifiers to files without license Roland Hieber
2021-03-30 11:08 ` [OSS-Tools] [PATCH dt-utils 1/4] treewide: add SPDX identifiers to files with GPL-2.0-or-later license Roland Hieber
2021-03-30 11:22   ` Ahmad Fatoum
2021-03-30 13:30     ` Uwe Kleine-König
2021-03-30 13:50       ` Ahmad Fatoum
2021-03-30 14:00         ` Uwe Kleine-König
2021-03-30 14:04           ` Ahmad Fatoum
2021-03-30 15:53         ` Roland Hieber
2021-03-30 17:31           ` Ahmad Fatoum [this message]
2021-03-31 10:03             ` Roland Hieber
2021-03-31 10:10               ` Roland Hieber
2021-03-30 12:49 ` Uwe Kleine-König
2023-08-01 10:10 ` Roland Hieber
2023-08-01 10:12   ` Roland Hieber

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=3286977b-06a6-539d-f36f-35385671acca@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=oss-tools@pengutronix.de \
    --cc=rhi@pengutronix.de \
    --cc=u.kleine-koenig@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