From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.8 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 55DC4C28CC3 for ; Fri, 31 May 2019 00:26:24 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 2FE2F2634D for ; Fri, 31 May 2019 00:26:24 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="key not found in DNS" (0-bit key) header.d=jilayne.com header.i=@jilayne.com header.b="sYcQHB9j" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726045AbfEaA0X (ORCPT ); Thu, 30 May 2019 20:26:23 -0400 Received: from mx2-c1.supremebox.com ([198.23.53.234]:33052 "EHLO mx1.supremebox.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726708AbfEaA0X (ORCPT ); Thu, 30 May 2019 20:26:23 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=jilayne.com ; s=default; h=To:References:Message-Id:Content-Transfer-Encoding:Cc:Date: In-Reply-To:From:Subject:Mime-Version:Content-Type:Sender:Reply-To:Content-ID :Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To: Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe :List-Post:List-Owner:List-Archive; bh=eJo+aizooULArT1voRG97kIgwpc5oXgWTeHxnPNDwRU=; b=sYcQHB9jl1f8SqJaqQFZcVFTnq zJK448jsP2WHGnMtysfLXGke+Gi2QEZ1EUqVpZEShACgY1wSKSaaThwSq7eTPMK363aPENKNWJ1FL 038mzC8XL1vWgFGnufrgm7pl/wdh/QIvjLYYhG/c3vuLwCq2WavQY3mBk2rDyB3CTnbk=; Received: from [67.164.173.226] (helo=[10.0.0.21]) by mx1.supremebox.com with esmtpa (Exim 4.89) (envelope-from ) id 1hWVNG-0002Zf-DI; Fri, 31 May 2019 00:26:22 +0000 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: Implement SPDX-Copyright From: J Lovejoy In-Reply-To: Date: Thu, 30 May 2019 18:26:21 -0600 Cc: linux-spdx@vger.kernel.org Content-Transfer-Encoding: quoted-printable Message-Id: <0BA4D54F-F42D-40B1-9D4E-71AFB5672D76@jilayne.com> References: <1558706708.m0wpla3nbm.2220@fsfe.org> To: Max Mehl X-Mailer: Apple Mail (2.3445.104.11) X-Sender-Ident-agJab5osgicCis: opensource@jilayne.com Sender: linux-spdx-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-spdx@vger.kernel.org Hi Max, Thanks for all the effort on REUSE and I hope I can find some time to = review the work going on there in the near future. Regarding the copyright tag - I just wanted to note that I have yet to = see this topic raised on the SPDX legal team. While I think there are = some SPDX folks commenting on the REUSE docs, it would really be best if = discussion of any SPDX-Copyright tag occurred on the project mailing = list and calls. While certainly the tech team folks should be involved = due to the tooling connection, I think the legal team needs to weigh in = as well. Feel free to raise this on the mailing list here (you=E2=80=99ll need to = join first, if you have not already): = https://lists.spdx.org/g/spdx-legal In the meantime, I suspect the kernel folks here have their hands full = with getting the license identifiers into the kernel, which also = involves being able to confidently identify the licensing info for each = and every file - no small feat! Anything with copyright notices maybe = can wait for another time? Thanks, Jilayne SPDX legal team co-lead > On May 24, 2019, at 8:22 AM, Max Mehl wrote: >=20 > Dear all, >=20 > Great to see such a big effort going on so smoothly thanks to the > excellent collaboration here! I would like to make a small suggestion > for further improvement while we are already touching so many files in > Linux. >=20 > Currently, the REUSE and SPDX team are discussing the official > introduction of the *SPDX-Copyright* tag [^1] [^2], perhaps for SPDX = 2.2 > and REUSE 3.0.=20 >=20 > The benefit is that tools can easily detect the correct line which = holds > the copyright/author/year information. As of now, there are files = which > contain multiple occurrences of the word "Copyright", "=C2=A9" or = "(c)", > which then requires the usage of error-prone logics and patterns. >=20 > Let me give a concrete example. The following header from one of the > first patches sent around here: >=20 >=20 > // SPDX-License-Identifier: GPL-2.0-or-later > /* > * Copyright (C) 2013 Pavel Machek > * Copyright (C) 2013-2014 Aaro Koskinen >=20 >=20 > could become: >=20 >=20 > // SPDX-License-Identifier: GPL-2.0-or-later > /* > * SPDX-Copyright: (C) 2013 Pavel Machek > * SPDX-Copyright: (C) 2013-2014 Aaro Koskinen >=20 >=20 > The usage of (C) or any other copyright symbols would probably be up = to > personal style or legal requirements. All this tag intends to achieve = is > to make automatic tooling more robust. >=20 > What do you think? Would someone see issues with realising this > technically rather simple change in the same course of action? >=20 > Best, > Max >=20 >=20 > [^1]: https://github.com/fsfe/reuse-docs/pull/23 >=20 > [^2]: https://github.com/spdx/spdx-spec/issues/122 >=20 > --=20 > Max Mehl - Programme Manager - Free Software Foundation Europe > Contact and information: https://fsfe.org/about/mehl | @mxmehl > Become a supporter of software freedom: https://fsfe.org/join