[issue534] Cooliris License Violation
Diego Biurrun di...@biurrun.de added the comment: On Fri, Dec 19, 2008 at 01:45:38AM +, Andy Taylor wrote: Andy Taylor a...@cooliris.com added the comment: We've made the following addition to our EULA regarding reverse engineering to comply with section 6 of the LGPL: (i) Decompile, reverse engineer, disassemble, modify, rent, lease, loan, distribute, or create derivative works (as defined by the U.S. Copyright Act) or improvements (as defined by U.S. patent law) based upon the Cooliris Software or any portion thereof, unless this is strictly for personal use or to debug such modifications; That's better. You'll also notice that we now display an Open Source Software notice with full credit and a link to download the original FFmpeg source (revision 12758 with no code modifications) directly from our site. This is to comply with section 4 of the LGPL. Good. This should comply fully with the LGPL. Thank you for your time and diligence. I quickly looked at your EULA found at http://www.cooliris.com/legal/terms/ Without even bothering to read it fully I noticed two things: 1) You do not seem to have read it yourselves. Otherwise it would not have escaped your notice that some paragraphs are duplicated. 2) There is still a section that is incompatible with our copyrights: (ii) Incorporate the Cooliris Software or any portion thereof into any computer chip or the firmware of a computing device manufactured by or for you; You have no business forbidding people what to do with FFmpeg, which is a portion of your software. It took me less than five minutes to discover. While you are surely closer to compliance than before, more diligence is still needed. The holes are still quite obvious without even looking at the software itself. Diego __ FFmpeg issue tracker ffmpeg_iss...@live.polito.it https://roundup.mplayerhq.hu/roundup/ffmpeg/issue534 __
[issue534] Cooliris License Violation
Andy Taylor a...@cooliris.com added the comment: Hello FFmpeg team, We've been working on this extensively, and I wanted to give you an update on this issue. We've made the following addition to our EULA regarding reverse engineering to comply with section 6 of the LGPL: (i) Decompile, reverse engineer, disassemble, modify, rent, lease, loan, distribute, or create derivative works (as defined by the U.S. Copyright Act) or improvements (as defined by U.S. patent law) based upon the Cooliris Software or any portion thereof, unless this is strictly for personal use or to debug such modifications; http://www.cooliris.com/legal/license/ You'll also notice that we now display an Open Source Software notice with full credit and a link to download the original FFmpeg source (revision 12758 with no code modifications) directly from our site. This is to comply with section 4 of the LGPL. This should comply fully with the LGPL. Thank you for your time and diligence. __ FFmpeg issue tracker ffmpeg_iss...@live.polito.it https://roundup.mplayerhq.hu/roundup/ffmpeg/issue534 __
[issue534] Cooliris License Violation
Diego Biurrun [EMAIL PROTECTED] added the comment: On Mon, Oct 27, 2008 at 05:27:20PM +, Andy Taylor wrote: Andy Taylor [EMAIL PROTECTED] added the comment: As a follow up - I wanted to include the modified link: http://www.cooliris.com/legal/license/ Modified in what regard? We are making use of the LGPL license in a non-derivative work by linking to the shared libraries. From Wikipedia (and Free Software Foundation): This is an unsourced statement and thus worthless. A standalone executable that dynamically links to a library is generally accepted as not being a derivative work. It would be considered a work that uses the library and paragraph 5 of the LGPL applies. A program that contains no derivative of any portion of the Library, but is designed to work with the Library by being compiled or linked with it, is called a work that uses the Library. Such a work, in isolation, is not a derivative work of the Library, and therefore falls outside the scope of this License. To the best of my knowledge this is not the position of the FSF. But commenting on a piece of text that you write in a random email is pointless anyway. If there is something I am missing, definitely please let me know, and I can make the appropriate changes on our end. What I miss most is precise information and proof. Your word is not good enough, we want hard facts. So far you have not stated a single thing you have done apart from it's all fine and dandy now. Also, I have not seen you address a single comment in this issue report. Diego __ FFmpeg issue tracker [EMAIL PROTECTED] https://roundup.mplayerhq.hu/roundup/ffmpeg/issue534 __
[issue534] Cooliris License Violation
Diego Biurrun [EMAIL PROTECTED] added the comment: On Mon, Oct 27, 2008 at 07:25:22PM +, Andy Taylor wrote: Andy Taylor [EMAIL PROTECTED] added the comment: Hello all - we would love to work with you further, however you should be aware of two points. 1) We are using an unmodified build of the FFmpeg trunk, so there are no patches to publish, and of course you can download the source we are using at any time from: svn://svn.mplayerhq.hu/ffmpeg/trunk May I suggest that you reread the portions of the LGPL concerning binary distribution (§4)? You are not complying with its terms in any way. 2) The EULA quoted in msg 3529 does not apply to FFmpeg - it is the EULA for the Cooliris product, not its dependent libraries, which are covered by the LGPL and Apache 2.0 licenses included with the distribution. May I suggest that you reread the portions of the LGPL concerning reverse engineering (§6)? You are not complying with its terms. If you still have any concerns, we would be happy to address them. I am concernded that you have not read the LGPL and are trying your best to get a free lunch from us. You will not be excused from the terms of the license. Read and understand the LGPL, fix the issues, then come back to us with results. Diego __ FFmpeg issue tracker [EMAIL PROTECTED] https://roundup.mplayerhq.hu/roundup/ffmpeg/issue534 __
[issue534] Cooliris License Violation
Karim [EMAIL PROTECTED] added the comment: Some update : http://dolphy-tech.net/log/?p=39 __ FFmpeg issue tracker [EMAIL PROTECTED] https://roundup.mplayerhq.hu/roundup/ffmpeg/issue534 __
[issue534] Cooliris License Violation
New submission from Glenn H. [EMAIL PROTECTED]: Cooliris, Inc. (cooliris.com) makes a browser addon for Firefox, IE, Flock and Safari named Piclens which allows image/video browsing of RSS feeds in a manner similar to Apple's CoverFlow. The Firefox extension (haven't checked the others) makes use of FFMPEG DLLs and I cannot find any reference to FFMPEG, the GPL or the FFMPEG source code on piclens.com, cooliris.com or within the addon itself. Steps to reproduce: 1.) Download Piclens for Firefox at piclens.com 2.) Rename the file's extension from .xpi file to .zip 3.) Extract the files with an unzip utility 4.) Notice the following files within the libs path: a.) avcodec-51.dll b.) avformat-52.dll c.) avutil-49.dll -- messages: 2473 nosy: Stilgar priority: normal status: new substatus: new title: Cooliris License Violation topic: (L)GPL violation __ FFmpeg issue tracker [EMAIL PROTECTED] https://roundup.mplayerhq.hu/roundup/ffmpeg/issue534 __
[issue534] Cooliris License Violation
Carl Eugen Hoyos [EMAIL PROTECTED] added the comment: Confirmed with http://www.piclens.com/firefox/download/piclens-win-ff2-release-1.7.0.3457.xpi size 1850536, md5sum e412afb86c945ec16fbf7059ed9e91a1 I'm not sure if they are using GPL or LGPL version (no amr at least). -- status: new - open substatus: new - reproduced __ FFmpeg issue tracker [EMAIL PROTECTED] https://roundup.mplayerhq.hu/roundup/ffmpeg/issue534 __
