Hi,
Thanks for sharing this.
I'am wondering who should use the tool?
In my opinion it can only be used by the copyright holders of the single files
where the standard license header shall be replaced and not by any other person.
It might be picky and you might say, hey that is something equivalent, but the
GPL-2.0 for example says in chapter 1:
..."keep intact all the notices that refer to this License and to the absence
of any warranty; and give any other recipients of the Program a copy of this
License
along with the Program."...
If you as a "non copyright holder" of a OSS package replace the standard
GPL-2.0 header by (let's say) "this is licensed under GPL-2.0" In my opinion
you have violated the GPL, because of the chapter 1.
You can argue "that there is no violation because it is just another notice for
the same thing", _but_ at least you have removed the phrase:
" This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details."
Which is an element for the standard GPL-2.0 header, and this is for sure a GPL
violation because of "keep intact all the notices ... to the absence of any
warranty". I do not want to violate the GPL, you?
Or did I miss something? If yes please correct me
Ciao
Oliver
-----Ursprüngliche Nachricht-----
Von: [email protected] [mailto:[email protected]]
Im Auftrag von Eric S. Raymond
Gesendet: Montag, 23. November 2015 16:10
An: Philippe Ombredanne
Cc: [email protected]; J Lovejoy
Betreff: Re: Prototype spdxify codewalker
Philippe Ombredanne <[email protected]>:
> On Sat, Nov 21, 2015 at 11:11 PM, Eric S. Raymond <[email protected]> wrote:
> > I've enclosed a copy of a proof-of-concept program in Python that
> > walks a code tree replacing inline license headers with SPDX tags.
> > It can be tested as a filter - feed a source file to its stdin, get
> > back the SPDXified version on stdout.
>
> Erirc:
> I think the code is not enclosed
>
> > Can we cooperate on making this a production-quality tool?
>
> I am game. FWIW, I maintain the scancode-toolkit that does scan and
> detects licenses in code and that could be useful.
> And it is also coded in Python ;)
>
> --
> Cordially
> Philippe Ombredanne
Ooops. Sorry. Here it is...
--
<a href="http://www.catb.org/~esr/";>Eric S. Raymond</a>
_______________________________________________
Spdx-tech mailing list
[email protected]
https://lists.spdx.org/mailman/listinfo/spdx-tech
