Joomla! extension licensing
29 views
Skip to first unread message
Chris Burgess
Aug 29, 2011, 2:35:05 AM8/29/11
to Joomla! General Development
Hi all.
I'm new to Joomla! development, and I'm trying to work through how to
manage my licensing issues. I know Joomla! is GPL, and all extensions
need to be GPL to be listed at the JED, however...
The issue I'm having is that I'm not just developing for Joomla!. I've
created a jQuery plugin (i.e. javascript code) and a css file, which
is a stand-alone product, which I'll also be selling. I've packaged
this into a Joomla! module for sale also (so people can choose which
package suits them, I may package into extensions/plugins for other
CMS's at some point also). My issue is that I'd prefer to prevent this
core javascript/css from being re-distributed (or worse, re-sold) by
others, which obviously the GPL doesn't prevent. I've read through
http://docs.joomla.org/JED_Entries_License_Checklist, and it appears
to me that to include non-GPL files like this is ok, as long as it's a
stand-alone product, which it is, and the fact that the extension
relies on non-GPL content is clearly stated, which I will do.
Firstly, I'd like some assurance that my understanding of this is
correct (or not, whichever the case may be). Secondly, I'd like some
advice from other Joomla! extension developers about what you think of
this approach. Whether you think this is a good idea, or whether you
completely disagree and it's better to just make it all GPL. The
license I would like to apply to the core javascript/css isn't going
to be a highly restrictive one (I don't wish to be completely
unreasonable about it). I'll probably be including unobfuscated
source, so people can make custom modifications for themselves if they
want/need to, so that wont be a concern. It's just the re-distribution
of the code I'd like to prevent.
Thoughts?
I'm new to Joomla! development, and I'm trying to work through how to
manage my licensing issues. I know Joomla! is GPL, and all extensions
need to be GPL to be listed at the JED, however...
The issue I'm having is that I'm not just developing for Joomla!. I've
created a jQuery plugin (i.e. javascript code) and a css file, which
is a stand-alone product, which I'll also be selling. I've packaged
this into a Joomla! module for sale also (so people can choose which
package suits them, I may package into extensions/plugins for other
CMS's at some point also). My issue is that I'd prefer to prevent this
core javascript/css from being re-distributed (or worse, re-sold) by
others, which obviously the GPL doesn't prevent. I've read through
http://docs.joomla.org/JED_Entries_License_Checklist, and it appears
to me that to include non-GPL files like this is ok, as long as it's a
stand-alone product, which it is, and the fact that the extension
relies on non-GPL content is clearly stated, which I will do.
Firstly, I'd like some assurance that my understanding of this is
correct (or not, whichever the case may be). Secondly, I'd like some
advice from other Joomla! extension developers about what you think of
this approach. Whether you think this is a good idea, or whether you
completely disagree and it's better to just make it all GPL. The
license I would like to apply to the core javascript/css isn't going
to be a highly restrictive one (I don't wish to be completely
unreasonable about it). I'll probably be including unobfuscated
source, so people can make custom modifications for themselves if they
want/need to, so that wont be a concern. It's just the re-distribution
of the code I'd like to prevent.
Thoughts?
Chad Windnagle
Aug 29, 2011, 10:00:33 AM8/29/11
to Joomla! General Development
From what I understand, JS libraries are 'media files' and can be
included as encrypted files and distributed under a non-GPL license
but included in your GPL extension. I've seen quite a few extensions
in the JED do similar things with only the JS files.
-Chad
On Aug 29, 2:35 am, Chris Burgess <chris.burgess.ac...@gmail.com>
wrote:
included as encrypted files and distributed under a non-GPL license
but included in your GPL extension. I've seen quite a few extensions
in the JED do similar things with only the JS files.
-Chad
On Aug 29, 2:35 am, Chris Burgess <chris.burgess.ac...@gmail.com>
wrote:
> Hi all.
>
> I'm new to Joomla! development, and I'm trying to work through how to
> manage my licensing issues. I know Joomla! is GPL, and all extensions
> need to be GPL to be listed at the JED, however...
>
> The issue I'm having is that I'm not just developing for Joomla!. I've
> created a jQuery plugin (i.e. javascript code) and a css file, which
> is a stand-alone product, which I'll also be selling. I've packaged
> this into a Joomla! module for sale also (so people can choose which
> package suits them, I may package into extensions/plugins for other
> CMS's at some point also). My issue is that I'd prefer to prevent this
> core javascript/css from being re-distributed (or worse, re-sold) by
> others, which obviously the GPL doesn't prevent. I've read throughhttp://docs.joomla.org/JED_Entries_License_Checklist, and it appears
>
> I'm new to Joomla! development, and I'm trying to work through how to
> manage my licensing issues. I know Joomla! is GPL, and all extensions
> need to be GPL to be listed at the JED, however...
>
> The issue I'm having is that I'm not just developing for Joomla!. I've
> created a jQuery plugin (i.e. javascript code) and a css file, which
> is a stand-alone product, which I'll also be selling. I've packaged
> this into a Joomla! module for sale also (so people can choose which
> package suits them, I may package into extensions/plugins for other
> CMS's at some point also). My issue is that I'd prefer to prevent this
> core javascript/css from being re-distributed (or worse, re-sold) by
Chris Burgess
Aug 30, 2011, 4:03:10 AM8/30/11
to Joomla! General Development
What if the non-GPL content has restrictions that quite fundamentally
contravene the GPL for the rest of the extension, and the advice
listed on the JED entries checklist I linked to in my first post. For
example, restricting use of the non-GPL javascript to a certain number
of domains. That would effectively restrict the extension to a certain
number of domains too, as it's useless without the javascript. Is that
sort of thing allowable?
BTW, I'm not necessarily going to do that. I'm just curious as to what
the options are at this point.
contravene the GPL for the rest of the extension, and the advice
listed on the JED entries checklist I linked to in my first post. For
example, restricting use of the non-GPL javascript to a certain number
of domains. That would effectively restrict the extension to a certain
number of domains too, as it's useless without the javascript. Is that
sort of thing allowable?
BTW, I'm not necessarily going to do that. I'm just curious as to what
the options are at this point.
SpiralScripts
Aug 30, 2011, 8:12:40 AM8/30/11
to Joomla! General Development
It is certainly my understanding that the GPL license is only required
for the PHP code. How you license other types of code such as
javascript, css etc is entirely up to you. You could restrict the
javascript to a certain number of domains if you wanted to. It might
seem slightly illogical, but that is the way that it works, I guess it
is impossible to have a system that is completely logical.
I think that the motivation for this is that requiring all code and
media included with an extension may not be practical. Eg, what would
you do with Flash swf files, which by their nature are compiled? You
might require the extension developer to make Flash source available,
but it is easy to think of cases where this would not be reasonable or
even possible.
On Aug 30, 9:03 am, Chris Burgess <chris.burgess.ac...@gmail.com>
for the PHP code. How you license other types of code such as
javascript, css etc is entirely up to you. You could restrict the
javascript to a certain number of domains if you wanted to. It might
seem slightly illogical, but that is the way that it works, I guess it
is impossible to have a system that is completely logical.
I think that the motivation for this is that requiring all code and
media included with an extension may not be practical. Eg, what would
you do with Flash swf files, which by their nature are compiled? You
might require the extension developer to make Flash source available,
but it is easy to think of cases where this would not be reasonable or
even possible.
On Aug 30, 9:03 am, Chris Burgess <chris.burgess.ac...@gmail.com>
elin
Aug 30, 2011, 8:54:18 AM8/30/11
to joomla-de...@googlegroups.com
The very short version is that you can do whatever you want with the media files because you could render the exact same files with a plain html page.
What makes sense for your business is a different question (i.e. how many customers you lose by restricting domains) which you have to think about but it has nothing to do with Joomla except to the extent that you potential customers have made a decision to use an open source solution for their CMS and therefore may prefer open source solutions throughout.
Elin
Chris Burgess
Aug 30, 2011, 8:31:44 PM8/30/11
to Joomla! General Development
Thanks for the answers. The line between what needs to be GPL and what
doesn't has to be drawn somewhere, I just wanted to be a little
clearer on where that line was. Makes as much sense as anything is
likely to.
Certainly, there is a big difference between what's legal and what's
sensible business-wise. Firstly, I just wanted to check the legal side
of things, and domain restricting was just an obvious example of a
potential legal issue, not something I would necessarily do. I'm a
software customer myself, and a Joomla! user, so I understand that
perspective also. As ever, just trying to find the right balance
between protecting my work (I do need to make an income from it,
otherwise it's not viable and wont exist at all), and not placing too
many restrictions on the customer.
doesn't has to be drawn somewhere, I just wanted to be a little
clearer on where that line was. Makes as much sense as anything is
likely to.
Certainly, there is a big difference between what's legal and what's
sensible business-wise. Firstly, I just wanted to check the legal side
of things, and domain restricting was just an obvious example of a
potential legal issue, not something I would necessarily do. I'm a
software customer myself, and a Joomla! user, so I understand that
perspective also. As ever, just trying to find the right balance
between protecting my work (I do need to make an income from it,
otherwise it's not viable and wont exist at all), and not placing too
many restrictions on the customer.
David Barrett
Aug 31, 2011, 6:19:33 AM8/31/11
to joomla-de...@googlegroups.com
If your interest is to cover your costs (make a living) from open source,
then there are various ways to do this. I only charge for one of my plugins
(not that I have written many), but the charge is a subscription to my
website that gives access to all the documentation and also the download
pages. This subscription is for one year. The plugin itself is completely
GPL and the source code (whether JavaScript or otherwise) not obfuscated at
all. I also don't put any other limitations (e.g. domain, etc.).
then there are various ways to do this. I only charge for one of my plugins
(not that I have written many), but the charge is a subscription to my
website that gives access to all the documentation and also the download
pages. This subscription is for one year. The plugin itself is completely
GPL and the source code (whether JavaScript or otherwise) not obfuscated at
all. I also don't put any other limitations (e.g. domain, etc.).
In my experience this has been a good model. I have made enough to cover
the time I spend on the plugin, and keep it updated. In actual fact, when I
first started charging I was amazed by the take-up. If you choose a
reasonable fee people seem very inclined to support the developer.
Regards,
Dave Barrett MCSA
Office: 01962 658999
Mobile: 07799 411974
http://www.cedit.biz
http://www.outlookrulesmanager.com - sorting your inbox so you don't have to
http://www.registrationvalidator.com - protect your Joomla! site from bots
and spammers
http://blogs.msdn.com/b/emeamsgdev- Microsoft Messaging Developer Blog
--
You received this message because you are subscribed to the Google Groups
"Joomla! General Development" group.
To post to this group, send an email to joomla-de...@googlegroups.com.
To unsubscribe from this group, send email to
joomla-dev-gene...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/joomla-dev-general?hl=en-GB.
Reply all
Reply to author
Forward
0 new messages