tags:

views:

138

answers:

4

Hi, I'm having problems in interpreting the license of Typolight (A CMS released under LGPL license).

The project owner has made it mandatory to print a comment in the homepage of the frontend of the site which mentions the use of Typolight CMS - http://www.typolight.org/forum/topic/8283.html

Can anyone please throw some light on this?

AFAIK, even the GPL doesn't force you to print that kind of message in the frontend (WordPress, Joomla, Drupal). Only a credit in the source files is required (php files).

I'm looking to create a work derived from this script, but adding a copyright notice like this in the frontend homepage won't be possible for me.

+3  A: 

Based on the blog entry at the link you provided, it sounds like people have been removing the copyright notice from the software before using it, so the author has now written the software in such a way that it forces the copyright notice into the home page.

Generally speaking, if a software user can't respect the wishes of the developer, they should look elsewhere for their software.

Robert Harvey
No. If the developer can't stand people modifying his software he shouldn't release it as (L)GPL. If the developer releases it as GPL the users are free to change the software how they need, also if it doesn't fit the original developers vision. That's kind of the point of the GPL.
sth
+4  A: 

The creator of the original work is allowed to add their own provisions to the licensing terms. Using the GPL doesn't mean that you lose control over your own code. For instance, you can issue commercial licenses (provided all contributors have agreed).

As a consumer in a free market it is your right to choose to use someone's software. But if you choose to use it then you need to abide by all of the terms set forth by the copyright owner.

envalid
In that case, it really isn't LGPL is it? If there are such restrictions in the script, it is a custom license based on LGPL?
Amit
@Amit: You can call the license whatever you want to. The author has apparently made his wishes clear.
Robert Harvey
Robert: You should not call it LGPL if it isn't the LGPL.
ammoQ
Technically if you include any javascript from the project it would need the copyright intact. If it isn't in the .js file itself it would need to be in the parent document. You could also argue for the markup/widgets, but that is stretching it a tad bit. Unfortunately licensing isn't something that will always be 100% clear as it would have to be interpreted by a judge, not a machine. If it was easy then lawyers would be out of business, they wouldn't run annoying ads on TV, and the world would be a better place.
envalid
A: 

From the thread linked by you:

If you have created custom page layouts (templates) with the invisible copyright notice, your are officially allowed to remove it after you have updated to version 2.6.2, so the notice does not appear twice in the page source.

Now I am not sure if "it" refers to the invisible o the visible copyright - maybe you should ask for clarification. Intention of the post seems "the visible one" - i.e. forcing people to comply with the licence, which seems ok for you.

peterchen
A: 

IANAL, but it seems that the creators of Typolight want to use the (L)GPL license (to promote their product) but they do not live in the spirit of free software. It makes no fscking sense to say "Users of the free (LGPL) version must include a copyright notice but users of the paid-for version don't have to". Because this means that either the copyright notice is not really necessary, but a way to force people to use the commercial version; or alternatively, it means that the commercial version is not copyrighted.

ammoQ
IANAL either, but... the lack of a copyright notice does NOT mean a version is not copyrighted. See the Berne Convention (http://en.wikipedia.org/wiki/Berne_Convention_for_the_Protection_of_Literary_and_Artistic_Works)
Oddthinking

related questions