[FFmpeg-devel] [PATCH] ffmpeg.org shame issue links
tempn at twmi.rr.com
Tue Apr 5 16:40:17 CEST 2011
On Tue, 5 Apr 2011 14:58:11 +0200, Michael Niedermayer wrote:
>On Tue, Apr 05, 2011 at 07:32:47AM -0400, compn wrote:
>> On Tue, 5 Apr 2011 11:23:14 +0200, Michael Niedermayer wrote:
>> >On Mon, Apr 04, 2011 at 08:50:11PM -0800, Lou Logan wrote:
>> >> * Fixes "issue tracker entry" links
>> >> * Removed "Our issue tracker also contains a list of license violations"
>> >> shame | 128 ++++++++++++++++++++++++++++++++----------------------------------
>> >> 1 file changed, 63 insertions(+), 65 deletions(-)
>> >> cb53d363faa7dd66de993fa54ed909cf175ac699 ffmpegorg_shame_issues.patch
>> its kind of strange having two trackers for license issues.
>> i'm not sure the best solution.
>> it doesnt make sense to do this then?
>iam against this patch, the page first would have to be worded in a
>fork neutral way to be shareable.
>Also the people that have write access to this page cannot _legally_
>declare ffmpeg copyright violations to be resolved, only the ffmpeg
>authors can do that. And i see no trace that any of us is being asked
>about changes there. Thus they casn just decalre the libav side of
>things as resolved
>Or worded clearer:
>To resolve a copyright violation about someones code one needs a
>agreement with that someone.
>Theres no way anyone else can do that without agreement of that someone.
>Or even clearer:
>If a company violates the (L)GPL and by that looses its rights under
>the license. They CANNOT get the rights back without my ok, diego and
>ronald do not have this power.
>Now lucky iam not planing to be evil here but iam very strongly oposed
>to be locked out of the process. As main author of ffmpeg (and thus
>libav). I expect to have a say in these negotiations.
right, whomever owns the copyright(s) in the files have to all agree
about it. its a difficult thing to solve. probably this is all
discussed on -legal? i was just trying to make this more simple.
e.g. have all gpl license issues on one tracker. but i think i'm not
going to try anymore.
More information about the ffmpeg-devel