Gyan (12019-01-13): > One angle that I haven't seen brought up is legal encumbrance. > > When someone submits a patch, it is implicit, unless stated otherwise, that > it is of their own initiative (and their own work), and thus they are free > to assign copyright. When work is performed for hire, the copyright may > belong to the employer. Such sponsored work cannot be 'donated' to the > project unless the employer agrees to it - it is not for the patch submitter > to decide. In such a scenario, the project should know who holds the > copyright and under what terms are they willing to submit a patch.
Thanks, I had not thought of that. I added this in the commit message: * This information is sometimes necessary to determine exactly who owns the copyright for the new code. Regards, -- Nicolas George
signature.asc
Description: PGP signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
