Steffen Nurpmeso <stef...@sdaoden.eu> wrote:
>  |    Replace license with just SPDX BSD-2-Clause
> 
> That is very interesting!  And .. are you really sure this is
> right with BSD etc licenses which explicitly require that the
> license text is included?
> So i looked and found [1] which says

I checked with one of our IP lawyers who said just the SPDX tag "should"
suffice, but best to remove the verbage that conflicts.

>   SPDX IDs are intending to express information about
>   licenses. Copyright notices ‐ statements about who owns the
>   copyright in a file or project ‐ are outside the scope of SPDX
>   short-form IDs.
>   Therefore, you should not remove or modify existing copyright
>   notices in files when adding an SPDX ID.

Except that in this case the verbage I removed is sufficiently different
from the text of https://spdx.org/licenses/BSD-2-Clause.html
as to potentially trigger arguments - so better safe that sorry,
and I hate the idea of a file which is 90% license, which is why I had
that abbreviated version in the first place.

If the lawyer says I can get away with just the tag, that works for me.

> However i am sure you do not do something like this "just like
> that", and would be very interested -- it would be nice to be able
> to vaporise the file header -- i always have that pitfall moment
> when i look into Plan9 / 9front source code, which then simply
> starts off (and very often with "#include <u.h>", just like that).

ISTR the original BSD convention was to not waste space on copyrights in
tiny files, I was forced into putting licenses on everything by some of
my consulting clients back in the '90s

HTH
--sjg

Reply via email to