Apparently, Theo is upset with the new Apache license. I haven't investigated it, but it might mean that the OpenBSD distro will fork a copy of Apache. Interesting.
update: I found a live archive of the thread. Still not very clear about the issues.
This is quite a serious issue (especially considering that the licence for Perl 6 / Parrot is yet to be definitively clarified). I haven't read yet a clear summary of what are the problems with the Apache 2 license -- I know it's OSS-approved, and GPL-incompatible, and not much more.
Recalling the whole "ipf" vs "pf" fiasco (which actually resulted in the really cool "pf" being created), I suspect the argument is with these two paragraphs:
* 4. The names "Apache" and "Apache Software Foundation" must * not be used to endorse or promote products derived from this * software without prior written permission. For written * permission, please contact apache@apache.org. * * 5. Products derived from this software may not be called "Apache", *
I was under the impression was with the patent clause; which I quote:
"If You institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work or a
Contribution incorporated within the Work constitutes direct or
contributory patent infringement, then any patent licenses granted to
You under this License for that Work shall terminate as of the date such
litigation is filed."
I also wonder what are the license compatibility issues (notably for mod_pe
IIRC, the "ipf" incident hinged on whether or not its license gave one permission to modify the source and redistribute a derivative work. Darren Reed said it didn't. Theo pulled "ipf" from OpenBSD-CURRENT, and the rest is history (the less than cordial exchanges between the two notwithstanding).
Interestingly, the aforementioned paragraphs you cited look like the opposite of the infamous "advertising clause". Be that as it may, I guess Theo et al could stick with the version of Apache before the license ch
IANAL-retentive (Score:2)
Re:IANAL-retentive (Score:2)
Re:IANAL-retentive (Score:2)
I also wonder what are the license compatibility issues (notably for mod_pe
Re:IANAL-retentive (Score:1)
IIRC, the "ipf" incident hinged on whether or not its license gave one permission to modify the source and redistribute a derivative work. Darren Reed said it didn't. Theo pulled "ipf" from OpenBSD-CURRENT, and the rest is history (the less than cordial exchanges between the two notwithstanding).
Interestingly, the aforementioned paragraphs you cited look like the opposite of the infamous "advertising clause". Be that as it may, I guess Theo et al could stick with the version of Apache before the license ch
Buck