[wp-hackers] Re: Removal Of Over 200 Themes?
wordpress at santosj.name
Sat Dec 13 02:13:12 GMT 2008
Actually, I'll take it that the HTTP API inherits the GPLv2 from the
parent, WordPress, since no license is given. I'm unsure if the API
would have been considered if it was anything other than GPLv2. However,
I would rather like that people use it outside of WordPress, but the
license might be too restrictive for some projects. Well, the Zend
Framework also implements a lot of what the HTTP API does, so really you
could use the Zend Framework under its New BSD license.
Doug Stewart wrote:
> On Fri, Dec 12, 2008 at 8:51 PM, Jacob Santos <wordpress at santosj.name>wrote:
>> What is the technical definition of a derivative work in layman's terms?
>> Why is a theme considered a derivative work of WordPress, if it is released
>> separately, but dependent on WordPress?
>> People keep saying GPLv2, but why couldn't I release my code new BSD?
>> I do release my code new BSD, the HTTP API would also be new BSD, if I had
>> caught it quick enough. I suppose the issue now is that I would need
>> permission from Ryan and DD32 + plus a couple of others in order to change
>> the license. The HTTP API can be used separately from WordPress, with a few
>> modifications to remove the wp_option code.
>> (Talk to me like I'm an idiot, because I know nothing)
> What version of the BSD license do you use? The old one is GPL-incompatible
> ( http://www.gnu.org/licenses/gpl-faq.html#OrigBSD).
> I'm assuming you're using the revised BSD, which is okay, since it removes
> the advertising clause.
More information about the wp-hackers