SPDX License Identifier Only and Full Copy?

[Gedare Bloom]

On Tue, Feb 18, 2020 at 6:07 AM Joel Sherrill <joel at rtems.org> wrote:
>
>
>
> On Tue, Feb 18, 2020, 3:08 AM Sebastian Huber <sebastian.huber at embedded-brains.de> wrote:
>>
>> On 06/12/2019 07:15, Sebastian Huber wrote:
>> > Hello,
>> >
>> > should we use only the SPDX License Identifier and the list of
>> > copyrights for new or license converted files, e.g.
>> >
>> > /*
>> >   * SPDX-License-Identifier: BSD-2-Clause
>> >   *
>> >   * Copyright (C) <FIRST YEAR>, <LAST YEAR> <COPYRIGHT HOLDER>
>> >   */
>> >
>> > or should we append in addition the full BSD-2-Clause text to the file
>> > headers?
>> >
>> > /*
>> >   * SPDX-License-Identifier: BSD-2-Clause
>> >   *
>> >   * Copyright (C) <FIRST YEAR>, <LAST YEAR> <COPYRIGHT HOLDER>
>> >   *
>> >   * Redistribution and use in source and binary forms, with or without
>> >   * modification, are permitted provided that the following conditions
>> >   * are met:
>> >   * 1. Redistributions of source code must retain the above copyright
>> >   *    notice, this list of conditions and the following disclaimer.
>> >   * 2. Redistributions in binary form must reproduce the above copyright
>> >   *    notice, this list of conditions and the following disclaimer in the
>> >   *    documentation and/or other materials provided with the distribution.
>> >   *
>> >   * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
>> > "AS IS"
>> >   * AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
>> > TO, THE
>> >   * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
>> > PURPOSE
>> >   * ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR
>> > CONTRIBUTORS BE
>> >   * LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
>> >   * CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
>> >   * SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
>> > BUSINESS
>> >   * INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
>> >   * CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
>> >   * ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
>> > OF THE
>> >   * POSSIBILITY OF SUCH DAMAGE.
>> >   */
>> >
>> > I suggest to use a master COPYING file and use file headers without the
>> > full license text.
>> >
>> > https://lists.rtems.org/pipermail/devel/2018-December/024198.html
>>
>> It would be nice to get some feedback here.
>
>
> I'm generally ok with just the spdx and copyright statements.
>

I'm also fine with the master COPYING, spdx-tag, and individual
copyrights in files.

I should make a note to take a pass over "my" files to relicense them.
Does anyone have any script/tools for making that easy?

>>
>> --
>> Sebastian Huber, embedded brains GmbH
>>
>> Address : Dornierstr. 4, D-82178 Puchheim, Germany
>> Phone   : +49 89 189 47 41-16
>> Fax     : +49 89 189 47 41-09
>> E-Mail  : sebastian.huber at embedded-brains.de
>> PGP     : Public key available on request.
>>
>> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
>> _______________________________________________
>> devel mailing list
>> devel at rtems.org
>> http://lists.rtems.org/mailman/listinfo/devel
>
> _______________________________________________
> devel mailing list
> devel at rtems.org
> http://lists.rtems.org/mailman/listinfo/devel