On 29/08/14 18:40, Kieran Kunhya wrote: >> The remark you mention there was not a review, but rather a complaint that >> the submitted patch was not easy enough to diff against the FFmpeg version. >> Cleanup by other contributors from libav was squashed in order to have a >> clean version in the history and for review on the ml. I and others >> gladly rescinded any specific authorship attribution for that. > > The author asked specifically to be attributed correctly and this was ignored.
Ronald decided to leave the project well before, the LGPL requires to state the authors (even amended once as per his request) and mention if there had been a change and by who (done as well) and that's it. Nobody presented him with anything, asked for specific input, nor forced him to merge the derivative work here developed. Yet he demanded something quite time consuming, after a good number of iterations. > IANAL but this is very dubious from a copyright perspective > attributing changes that the author didn't approve of to him purely > for the sake of having a "clean version in the history". Your doubt is quite interesting given the tendency of "importing" against my will code from my public trees (that contain work in progress code with known issues more than often). Even if I'm not happy about that, I consider such actions legal and within the boundaries of the license I picked, as long it is stated that I'm the author and that the code had been manipulated/edited/whatever by a third party (if the change or the piece of code is non-trivial). The license states quite clearly that the code is provided w/out any warranty so I do not have concern regarding liabilities. I'm not a lawyer as well so my opinion is as good as yours. Hopefully I can get a professional third party to give some expert insight so we can have this point cleared properly. In case I'm wrong and importing code against the will of the first originator is against some law I'll see how to fix this issue, possibly amicably. Thanks a lot. lu _______________________________________________ libav-devel mailing list libav-devel@libav.org https://lists.libav.org/mailman/listinfo/libav-devel
