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=-1.0 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS 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 D0C20C072B5 for ; Fri, 24 May 2019 15:13:11 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 85ACF2075D for ; Fri, 24 May 2019 15:13:11 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=pobox.com header.i=@pobox.com header.b="LrZYfEVo"; dkim=fail reason="key not found in DNS" (0-bit key) header.d=lohutok.net header.i=@lohutok.net header.b="ZF49MaDm" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2389154AbfEXPNL (ORCPT ); Fri, 24 May 2019 11:13:11 -0400 Received: from pb-smtp1.pobox.com ([64.147.108.70]:55755 "EHLO pb-smtp1.pobox.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2389149AbfEXPNL (ORCPT ); Fri, 24 May 2019 11:13:11 -0400 Received: from pb-smtp1.pobox.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id BC4AE15222B; Fri, 24 May 2019 11:13:10 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=subject:to :references:cc:from:message-id:date:mime-version:in-reply-to :content-type:content-transfer-encoding; s=sasl; bh=6G1y9CYPxPt2 cKkL7F8LHakLns0=; b=LrZYfEVoSAx2e0T6w6dGkWRQsQvqm5lEoXlqpTv+R1Bi mKaUiXXiB7Bq/yhyByRXKSC37JhoQf7Le0mWRv9m9Hy8yCXfRL6CzWpNBh3bNymt 5WEgn+C9x6h9sjbzXQYu2nQ2LIWaw4/Og1iovoyxHNiOIGrc2RqpUU2sbcvslrQ= Received: from pb-smtp1.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id B409915222A; Fri, 24 May 2019 11:13:10 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=lohutok.net; h=subject:to:references:cc:from:message-id:date:mime-version:in-reply-to:content-type:content-transfer-encoding; s=2018-11.pbsmtp; bh=aAhggKKzklzeMuTGsCaTFyiiq5hFtp0pgq8SmSG309I=; b=ZF49MaDmjUEBxJ9wEYIHypsUrK0nVoxL37pI80GEF8/hpN+bChGWg/J3Um6UUT3XTCuULV25GfHDz+bSCD7Hun/rOelW50NtY/RpzEKvGBCqpqUqwmxjGHSdQXmVuTM/cCctyKrDLzcNsZ4q0m2X8S0pxqL+Pyzh6S9inHQv+2o= Received: from [10.0.0.75] (unknown [24.47.52.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pb-smtp1.pobox.com (Postfix) with ESMTPSA id E5E76152229; Fri, 24 May 2019 11:13:09 -0400 (EDT) Subject: Re: Implement SPDX-Copyright To: Max Mehl References: <1558706708.m0wpla3nbm.2220@fsfe.org> Cc: linux-spdx@vger.kernel.org From: Allison Randal Message-ID: Date: Fri, 24 May 2019 11:13:09 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1 MIME-Version: 1.0 In-Reply-To: <1558706708.m0wpla3nbm.2220@fsfe.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Pobox-Relay-ID: 70F6FABC-7E36-11E9-A277-46F8B7964D18-44123303!pb-smtp1.pobox.com Sender: linux-spdx-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-spdx@vger.kernel.org On 5/24/19 10:22 AM, Max Mehl wrote: > > 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. [...] > What do you think? Would someone see issues with realising this > technically rather simple change in the same course of action? Since it is still under discussion, we should wait until that discussion settles out before considering a massive application. Allison