Possible routes to kernel on GPLv3
Posted Jan 27, 2007 22:21 UTC (Sat) by grouch
In reply to: Possible routes to kernel on GPLv3
Parent article: GPL 3: An Open-Source Earthquake? (CRN)
Why would something like this not work for creating a community-agreeable license?
Law is not C code. I can fiddle around with the kernel, determine the value of the output within the time it takes to compile and boot, and nobody will get sued as a result. If I fiddle around with a software license, the output may not be noticed for years and could very well be the cause of severe hardship for lots of people.
My opinion regarding some new patch in the kernel might be useful to the developers, if I can present some logical basis for my opinion or some real-world experience to back up that opinion. My opinion regarding whether or not the word "convey" needs to be in GPLv3 is of no importance to anyone, because I don't have a clue about the legal jurisdictions in which it holds significance.
The effect of "return 1;" is not something that will change if you compile the kernel in the U.S. one day and Libya the next. Anyone might demonstrate the effects of changing such lines of code. The effects of using "convey" versus "propagate" versus "copy" are not so easily and universally demonstrated. Anyone can suggest an intended or hoped-for effect, but how to achieve that effect in a license is not something one can determine by reading a man page or some source code.
to post comments)