When "free" isn't
Posted: Sun Jun 03, 2007 9:43 am
Hi
I am seeing an increasing number of extensions listed as "Other open source / Free license" when in fact they are not.
The most common example is where the developer lists a single extension that comes in two versions (e.g. Lite and Pro). In these cases, the lite is free, foss, gnu/gpl etc, but the pro is not.
Surely extension developers should be required to list the two versions separately (like many do anyway)?
The second example, which REALLY bugs me is where the extension is free, but only for non-commercial sites. The reason this bugs me is that often you only find out that you can't use the extension when you get to the licence agreement for the download.
As I don't have an extension listed, I don't know if these two situations are adequately covered by licence descriptions available when listing.
If not, surely we need a more fine-tuned list of options?
Regards
Brendon
I am seeing an increasing number of extensions listed as "Other open source / Free license" when in fact they are not.
The most common example is where the developer lists a single extension that comes in two versions (e.g. Lite and Pro). In these cases, the lite is free, foss, gnu/gpl etc, but the pro is not.
Surely extension developers should be required to list the two versions separately (like many do anyway)?
The second example, which REALLY bugs me is where the extension is free, but only for non-commercial sites. The reason this bugs me is that often you only find out that you can't use the extension when you get to the licence agreement for the download.
As I don't have an extension listed, I don't know if these two situations are adequately covered by licence descriptions available when listing.
If not, surely we need a more fine-tuned list of options?
Regards
Brendon