licensing concerns with cocci patches
Quoted 6 lines · Eitan Adler
Quoted 5 lines · Julia Lawall
Quoted 3 lines
My understanding is that the output of a semantic patch should not be GPL. But I am not an expert. In any case, that is the intent. We would certainly be happy that the scripts be part of BSD.
Quoted 6 lines
Quoted 2 lines
Awesome. Hopefully I will be able to start gathering a set of useful scripts soon.
So... We should talk a bit more :) Also I'd love to help iron out any FUD over licensing issues given that it seems the intent expressed is not to enforce requirement of output being GPL derivative.
Hello,
I apologize for not replying in-thread, but I'm only an occasional user of coccinelle, so I wasn't subscribed to the list.
The concept that the GPL would apply to the output of spatch, just because spatch itself is under the GPL is well beyond far-fetched. By the same logic, it could as well apply to the results of a search-and-replace in emacs :)
The FSF claims that this is not even legally possible, let alone a requirement of the GPL. That goes for any version of the GPL, but I'll just link to the GPLv2 FAQ, as that's what coccinelle uses:
https://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#GPLOutput
Coccinelle itself does not produce any code, it transforms code according to supplied rules. If the rules are under the GPL, again there is no requirement about the result of the transformation whatsoever. There are numerous clauses in the GPLv2 to support this statement, but I'll just quote the 0th one:
"The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program)"
As a general rule of thumb, one should keep in mind that the the GPL is concerned with preventing the GPL code itself from becoming proprietary and does NOT try to force people to open up their code.
I'm happy that coccinelle is around, I like having it in my toolbox and I would like it if even more projects used it (and more semantic patches became available). I would not want to see its adoption hindered based on some unfounded misconception, nor would I want to see this misconception spread to the coccinelle community :)
FWIW, the DragonFlyBSD project (to which I occasionally contribute) has been happily using coccinelle semantic patches with good results for a while now and I'm glad to hear FreeBSD is going to embrace it further.
Hope this helps,
Aggelos
Quoted 15 lines · Angelos Oikonomopoulos
Quoted 8 lines
Quoted 6 lines · Eitan Adler
Quoted 4 lines · Julia Lawall
My understanding is that the output of a semantic patch should not be GPL.
But I am not an expert. In any case, that is the intent. We would certainly be happy that the scripts be part of BSD.Quoted 6 lines
Quoted 2 lines
Awesome. Hopefully I will be able to start gathering a set of useful scripts soon.
So... We should talk a bit more :) Also I'd love to help iron out any FUD over licensing issues given that it seems the intent expressed is not to enforce requirement of output being GPL derivative.
Quoted 8 lines
Hello,
I apologize for not replying in-thread, but I'm only an occasional user of coccinelle, so I wasn't subscribed to the list.
The concept that the GPL would apply to the output of spatch, just because spatch itself is under the GPL is well beyond far-fetched. By the same logic, it could as well apply to the results of a search-and-replace in emacs :)
Not quite. Because thre is no GPL on the replace. The user writes the replace himself. What is being discussed is semantic patches that are GPL'd, not the fact that Coccinelle itself is GPL'd.
Quoted 25 lines
The FSF claims that this is not even legally possible, let alone a requirement of the GPL. That goes for any version of the GPL, but I'll just link to the GPLv2 FAQ, as that's what coccinelle uses:
https://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#GPLOutput
Coccinelle itself does not produce any code, it transforms code according to supplied rules. If the rules are under the GPL, again there is no requirement about the result of the transformation whatsoever. There are numerous clauses in the GPLv2 to support this statement, but I'll just quote the 0th one:
"The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program)"
As a general rule of thumb, one should keep in mind that the the GPL is concerned with preventing the GPL code itself from becoming proprietary and does NOT try to force people to open up their code.
I'm happy that coccinelle is around, I like having it in my toolbox and I would like it if even more projects used it (and more semantic patches became available). I would not want to see its adoption hindered based on some unfounded misconception, nor would I want to see this misconception spread to the coccinelle community :)
Quoted 3 lines
FWIW, the DragonFlyBSD project (to which I occasionally contribute) has been happily using coccinelle semantic patches with good results for a while now and I'm glad to hear FreeBSD is going to embrace it further.
Thanks for the input. It is clearly an issue that needs to be understood better.
julia
Quoted 1 line · Julia Lawall
On Tue, 23 Oct 2012, Angelos Oikonomopoulos wrote:
[...]
Quoted 8 lines
Quoted 4 lines
The concept that the GPL would apply to the output of spatch, just because spatch itself is under the GPL is well beyond far-fetched. By the same logic, it could as well apply to the results of a search-and-replace in emacs :)
Not quite. Because thre is no GPL on the replace. The user writes the replace himself. What is being discussed is semantic patches that are GPL'd, not the fact that Coccinelle itself is GPL'd.
Oh, I misunderstood the issue in question then, sorry for my careless reading.
I hope everyone agrees that patches that merely report potential issues are fine. In the case that a semantic patch adds significant amounts of original code, it does sound that the authors of the semantic patches might need to grant an explicit exception. I seriously doubt that the output of patches like andand.cocci (or any search-and-replace-style transformation) is copyrightable, however :)
BTW, you might also consider asking the SFLC for pro-bono advice on this
https://www.softwarefreedom.org/about/contact/
HTH,
Aggelos