<html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body text="#000000" bgcolor="#FFFFFF"> <div class="moz-cite-prefix">Le 20/06/2013 16:31, Nicolas Limare a écrit : </div> <blockquote cite="mid:20130620143143.GK9379@nashi.hw.39mm.net" type="cite"> <pre wrap="">Hi all, A few recent events suggest that using the GPL license for code published in IPOL is a good choice. * Two companies want to use include algorithms published in IPOL by reusing the code published here too. This code is under the GPL license and these companies do not want to be bound by the license terms, so they proposed to buy the rights to reuse this code under different conditions.</pre> </blockquote> Does it mean that, once the company will buy the rights to reuse the code, then the still available code on the ipol site, will have its licence changed and will not be free anymore, or does it mean that the company will not be bound by the actual licence by buying the rights but the very code on ipol will continue to be free and reusable ? <blockquote cite="mid:20130620143143.GK9379@nashi.hw.39mm.net" type="cite"> <pre wrap=""> * One company is selling a photo enlargement software (without the source code) that includes one code published in IPOL. This IPOL code is published under the BSD license and the photo software mentions it, so the story stops here. But their software also includes another non-IPOL code, under GPL this time, so there is a license infringement and some people are trying to have the software company release their code (or pay for a license agreement) with the Free Software Foundation legal team. * Moreover, one company is supporting the work done by an IPOL author by funding a PhD and is not objecting to the publication of this work under GPL as long as they also have the code internally under BSD license (they paid for it!). I think these examples show that by using GPL, authors can share their research work with other researchers and collaborators and benefit from its commercial value. Therefore I recommend that this license is used for every non-trivial piece of code published in IPOL. PS: In short, non-legal words, the GPL license says that anyone can use your source code for any purpose, but if a program using your source code is distributed, then - your contribution must be mentioned; - all the source code used is under the GPL license; - all the source code must be publicly available. PPS: The copyright of the code published in IPOL is owned by you (or your employer), not by IPOL. The copyright owner decides which license is used. </pre> <fieldset class="mimeAttachmentHeader"></fieldset> <pre wrap="">-- IPOL - Image Processing On Line - <a class="moz-txt-link-freetext" href="http://ipol.im/">http://ipol.im/</a> contact <a class="moz-txt-link-abbreviated" href="mailto:edit@ipol.im">edit@ipol.im</a> - <a class="moz-txt-link-freetext" href="http://www.ipol.im/meta/contact/">http://www.ipol.im/meta/contact/</a> news+feeds twitter @IPOL_journal - <a class="moz-txt-link-freetext" href="http://www.ipol.im/meta/feeds/">http://www.ipol.im/meta/feeds/</a> announces <a class="moz-txt-link-abbreviated" href="mailto:announce@list.ipol.im">announce@list.ipol.im</a> - <a class="moz-txt-link-freetext" href="http://tools.ipol.im/mm/announce/">http://tools.ipol.im/mm/announce/</a> discussions <a class="moz-txt-link-abbreviated" href="mailto:discuss@list.ipol.im">discuss@list.ipol.im</a> - <a class="moz-txt-link-freetext" href="http://tools.ipol.im/mm/discuss/">http://tools.ipol.im/mm/discuss/</a> </pre> </blockquote> </body> </html>