Am 27.08.2012 22:12, schrieb Dan Dennedy: > On Mon, Aug 27, 2012 at 12:14 PM, Patrick Matthäi <[email protected]> > wrote: >> Am 27.08.2012 20:58, schrieb Murthy Avanithsa: >>> Thank you very much for the quick response. >>> >>> We only need some of the utilities not all. If we compile the code using >>> LGPL.. >>> >> >>> 4) If we use MLT framework, do we need to display MLT framework some >>> where on our media player or editor? >> >> No, but you are not allowed to remove copyright/license marks done by >> the author. > > Actually, yes, you do. From section 6 of LGPL 2.1: "You must give > prominent notice with each copy of the work that the Library is used > in it and that the Library and its use are covered by this License." > and "If the work during execution displays copyright notices, you must > include the copyright notice for the Library among them...."
This is already done if you keep all copyright/license information from the source in your copy, also additional files like COPYING e.g. are good examples for it and with my sentence I just wanted to say this. From project to project and license to license this could be different, some AGPL variants e.g.: - webapplication foo exists under the terms of the agpl xyz (different versions different requirements, do not know exactly now the version numbers) - version 1.0 requires, that you display in the footer or in the html source code, that it is also copyrighted by bla bla in year foo - version 2.0 also requires, that you offer a tarball of the whole source code of the webapp which is displayed to the user Removing such license/copyright foo is always critical and not free. > There is no single point of contact regarding the copyright for all of > the code in MLT. The framework, core module, and some other modules > are all copyright Ushodaya Enterprises Limited, but we no longer have > a direct contact with them. Other modules have a variety of > copyrights. And then there are the various dependencies that need > consideration. So, a lawyer is definitely good advice if you need to > make something proprietary. Copyright != license Copyrights are much more complicated and uglier. Also each (applied) patch submitter earns copyrights with most free licenses (which also prevents license changes), but that is too much for this thread :) -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: [email protected] [email protected] */
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________ Mlt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mlt-devel
