Oh and by the way the title of the article is "Maintaining Permissive-Licensed Files in a GPL-Licensed Project: Guidelines for Developers". I read most of it and I'm under the impression that this is about keeping BSD code inside LGPL code but still allowing the BSD code to be used outside of the project as BSD. What we want to do here is taking BSD code, modifying it and distributing it under the LGPL without actually having to keep the code as BSD. The page discusses quite a lot about keeping the copyright of the original code which is something that we do. We wouldn't alter the original copyright but only the conditions which the code is distributed with. And since we keep all the original conditions and add new ones as per the LGPL, we should be allowed to do this since the BSD license does not say anything about it, as long as the copyright, not the license, remains intact.
On 2 January 2016 at 00:51, Carl Eugen Hoyos <ceho...@ag.or.at> wrote: > Carl Eugen Hoyos <cehoyos <at> ag.or.at> writes: > > [...] > > We were apparently both wrong: > > https://www.softwarefreedom.org/resources/2007/gpl-non-gpl-collaboration.html > > So please place the original (two-clause BSD) license > including the copyright statement under your (new) LGPL > license. > > Sorry for the noise, Carl Eugen > > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > http://ffmpeg.org/mailman/listinfo/ffmpeg-devel > _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
