Stefan Mainz wrote:
IANAL either. My understanding matches Stefan's above. If you include the current license by reference, the ASF appears to be well protected, but you may not be achieving what you want. People who make use of the code you produce may some day be surprised to find that the only thing they actually have permission to make use of is the LICENSE FILE itself, subject of course to the terms contained therein.Ceki G�lc� wrote:Propably i am not the right person to answer this (not being a lawyer), but:I do not understand what Roy means by "the scope of what was covered beyond 'this file'" Copyright law only protects the expression of an idea, so I am baffled by what is meant by the scope beyond the file, that is the written expression of the software developer. How can copyright law apply to anything beyond the file?
If you refer to a file which includes the license and the license says
_this file_ the license applies to the license file, not the onw which referes to the file.
The next license is intended to fix this.
- Sam Ruby
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
