Basically, it is not so important to us which license will be in headers. We can use license suggested by Diego, or we can use the same license that is used in rest of Libav files and just add developers that worked on those files, or we can use something else.
You can suggest what form of license do you want in files and I will make changes and resubmit patches. - Nedeljko ________________________________________ From: libav-devel-boun...@libav.org [libav-devel-boun...@libav.org] on behalf of Måns Rullgård [m...@mansr.com] Sent: Friday, August 17, 2012 14:36 To: libav development Subject: Re: [libav-devel] [PATCH 2/3] mips/doc: add documentation regarding MIPS optimizations Diego Biurrun <di...@biurrun.de> writes: > On Fri, Aug 17, 2012 at 01:49:46PM +0200, Nedeljko Babic wrote: >> Add doc/mips.txt document with short explanation regarding targeted >> platform for MIPS optimizations and regarding MIPS copyright notice. >> >> --- /dev/null >> +++ b/doc/mips.txt >> @@ -0,0 +1,60 @@ >> + >> +Along with Libav copyright notice, there is MIPS copyright notice in >> +all the files that are created by people from MIPS Technologies. >> + >> +Example of copyright notice: >> +=============================================== >> +/* >> + * Copyright (c) 2012 >> + * MIPS Technologies, Inc., California. >> + * >> + * Redistribution and use in source and binary forms, with or without >> + * modification, are permitted provided that the following conditions >> + * are met: >> + * 1. Redistributions of source code must retain the above copyright >> + * notice, this list of conditions and the following disclaimer. >> + * 2. Redistributions in binary form must reproduce the above copyright >> + * notice, this list of conditions and the following disclaimer in the >> + * documentation and/or other materials provided with the distribution. >> + * 3. Neither the name of the MIPS Technologies, Inc., nor the names of its >> + * contributors may be used to endorse or promote products derived from >> + * this software without specific prior written permission. > > This combined license creates problems for all downstream recipients, which > must now follow both licenses. In this case, add a number of notices to > their documentation. What is the problem with releasing your code under > just one of the two licenses? Also bear in mind that at least some of the assembly code should probably considered derived from the corresponding C code, so changing the copyright statement and licence terms of those parts is plain illegal. -- Måns Rullgård m...@mansr.com _______________________________________________ libav-devel mailing list libav-devel@libav.org https://lists.libav.org/mailman/listinfo/libav-devel _______________________________________________ libav-devel mailing list libav-devel@libav.org https://lists.libav.org/mailman/listinfo/libav-devel
