Plugin licensing

I would like to know if it is possible to release plugins under other than GPL license.

What I am interested in, is can plugin be considered as derivative work. The GPL FAQ ( www.gnu.org/licenses/gpl-faq.html#GPLAndPlugins ) and also this www.fsf.org/licensing/licenses/gpl-faq.html#MereAggregation state that CB plugins as well as Joomla components would need to be release with GPL compatible licensing.

Does anyone here know if these things really do hold, that is, can you (legally) publish a plugin that integrates with non GPL code?

mikko

mikko wrote:

I would like to know if it is possible to release plugins under other than GPL license.

What I am interested in, is can plugin be considered as derivative work. The GPL FAQ ( www.gnu.org/licenses/gpl-faq.html#GPLAndPlugins ) and also this www.fsf.org/licensing/licenses/gpl-faq.html#MereAggregation state that CB plugins as well as Joomla components would need to be release with GPL compatible licensing.

Does anyone here know if these things really do hold, that is, can you (legally) publish a plugin that integrates with non GPL code?

mikko

1. I'm not a lawyer
2. It may depend on country

But generally the limit is as follows:

If you write GPL code using publicly available information which is not protected by patents, then you are generally ok.

If you need to look into a database structure or code, which is proprietary and not public, and your code reveals those partially, then you are not ok, without the permission of the rights-holder.

That said, the rights-holder might even be interested in supporting your work as it could broaden their customer base. Just don't be afraid to talk with them first in any case.

DISCLAIMER: This is not a legal advice, and is given without any warranty implied or explicit, etc. etc. bla bla bla.