Quote:
Originally Posted by CyberSEO
Once again. It does not uses any WP code. It interacts with WP via API in a same way as any application interacts with the operating system. As logs as the application/script does not contain the GPL code directly, it does not have to be the GPL product.
Yes it's not. It interacts with the environment via API in a same way like your browser interacts with the operating system (displays windows, buttons etc), but does not contain any proprietary m$ code.
Yes, it's an external product. Read above.
Actually I don't see any reason to discuss this, because the WP team has stated it very clear: there could be GPL and non-GPL extensions, and they do not recommend the non-GPL ones. My Simple FLV plugin is a good example. Try to submit it into the WP repository and it will be rejected as a non-GPL one. The mentioned plugin also does interacts with WP API, but this fact dose not make it a GPL product. The same applies to the CyberSEO plugin which explicitly contains a non-GPL proprietary code itself. If someone will try to distribute it under the GPL license, it will be a direct violation of GPL itself and a violation of the proprietary license under which it was released.
So what exactly we are discussing here? I believe it was explained in the WP freedom declaration too (please re-read my previous post carefully).
|
actually by being activated its gpl.
since you have to wordpress header code.
as soon as you have this added, its considered gpl.
Code:
<?php
/*
Plugin Name: Name Of The Plugin
Plugin URI: http://URI_Of_Page_Describing_Plugin_and_Updates
Description: A brief description of the Plugin.
Version: The Plugin's Version Number, e.g.: 1.0
Author: Name Of The Plugin Author
Author URI: http://URI_Of_The_Plugin_Author
License: A "Slug" license name e.g. GPL2
*/
?>
since you have this in your plugin file, which is needed or it wont be activated, it becomes gpl.