[wp-hackers] anyone looked at Chameleon closely?

David Chait davebytes at comcast.net
Tue Jun 6 21:05:20 GMT 2006

What'll really cook your noodle is when you imagine a plugin that calls some 
third piece of code.  The plugin obviously knows WP enough to call 
'add_action/add_filter' (note that another system could use those same 
function names, and same mechanisms, so that isn't necessarily WP-unique!), 
and has to know how to call into the 'third piece of code' (call is 'alien 
code').  But the alien code knows nothing of WP, nor the plugin.  Okay. 
NOW, is the plugin GPL?  The alien code is non-GPL, so the plugin can't 
possible 'pass on' GPL-ness to it by virtue of 'knowledge'.

Fun.  And gee, most of my plugins are structured just like the above 
example... ;)

----- Original Message ----- 
From: "Aaron Brazell" <emmensetech at gmail.com>
To: <wp-hackers at lists.automattic.com>
Sent: Tuesday, June 06, 2006 4:38 PM
Subject: Re: [wp-hackers] anyone looked at Chameleon closely?

| On 6/6/06, Brian Layman <Brian at thecodecave.com> wrote:
| >
| > How it is distributed, does not really matter.
| > Assuming Matt's team of lawyers don't disagree. ;)  That section means
| > that
| > unless the plug-ins contain code originally contained in WordPress, they
| > don't have to be GPL.
| >
| > IMHO, licensing is up to the individual plug-in author UNLESS the 
| > includes a WP unit.  If  the plug-in pulls in ANY WP code, /then/ it in
| > part
| > contains a GPL licensed product and therefore must be GPL'd.
| >
| I wonder if the WordPress API functions and add_filter()s and such would
| code originally contained in WordPress?
| _______________________________________________
| wp-hackers mailing list
| wp-hackers at lists.automattic.com
| http://lists.automattic.com/mailman/listinfo/wp-hackers

More information about the wp-hackers mailing list