<html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> Hi all, thanks Nicolas for these guidelines and Pascal for the careful reading. I don't have much too add to Pascal's comments, just a few remarks regarding version 2 (<a href="http://tools.ipol.im/wiki/author/code/software_guidelines/sw-guidelines_tmp20111107.html">http://tools.ipol.im/wiki/author/code/software_guidelines/sw-guidelines_tmp20111107.html</a>): 1) typo (already remarked by Pascal): "the quality of these comments is more important than the quality", the second "quality" must be "quantity" 2) typo: "The line termionation SHOULD" 3) In the License section, when referring to patented algorithms, I think the following sentences are confusing: First, it is said that: "The license MUST be mentioned after the copyright attribution line (and patent warning for algorithms potentially linked to a patent)." But later it says: "When a file can be linked to a patented algorithm, GPL licenses MUST NOT be used because they might conflict with patents or are somehow unclear. BSD licenses can be used but some of their terms may be restricted by patent jurisdictions." Since GPL MUST NOT be used and BSD CAN be used, I think that including the license for a patented algorithm is optional. I propose: "For algorithms not linked to a patent the license MUST be mentioned after the copyright attribution line." ... "When a file can be linked to a patented algorithm, GPL licenses MUST NOT be used because they might conflict with patents or are somehow unclear. BSD licenses can be used but some of their terms may be restricted by patent jurisdictions. (...)" José Luis El 06/11/2011 2:31, Nicolas Limare escribió: <blockquote cite="mid:20111106013108.GH3421@nashi.hw.39mm.net" type="cite"> <pre wrap="">Hi, Because of recent misunderstandings on the meaning of the IPOL source code requirements, and other things I wanted to correct, I wrote a first draft of the IPOL Software Guidelines, version 1. -> <a class="moz-txt-link-freetext" href="http://tools.ipol.im/wiki/author/code/software_guidelines/">http://tools.ipol.im/wiki/author/code/software_guidelines/</a> This document incorporates, extends and will replace the current Implementation Manual and Copyright and Patent Policy. -> <a class="moz-txt-link-freetext" href="http://www.ipol.im/meta/submission/manual/#implementation">http://www.ipol.im/meta/submission/manual/#implementation</a> -> <a class="moz-txt-link-freetext" href="http://tools.ipol.im/wiki/author/code/copyright_and_patents/">http://tools.ipol.im/wiki/author/code/copyright_and_patents/</a> It should describe all the requirements an IPOL software must fullfill to be acceptable for IPOL. Now I need your comments, to correct and improve this draft and obtain an official version. Please post your comments on this list, I will prepare a second draft after 2 weeks. I am interested in any comment, but particularly in * imprecisions and ambiguity * disagreements about a requirement/recommandation * ununderstandable requirement/recommendation * requirements hard to attain for some of the authors or algorithms * proofreading by native English speakers PS: read and check the guidelines, because once it is they are adopted you will have to follow them! </pre> <fieldset class="mimeAttachmentHeader"></fieldset> <pre wrap="">_______________________________________________ discuss mailing list <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/mailman/listinfo/discuss">http://tools.ipol.im/mailman/listinfo/discuss</a></pre> </blockquote> </body> </html>