Hi,<div><br></div><div>Some online repository force to label all the subdirectory under the same licence.</div><div>(code google, sourceforge ...) (not github)</div><div>So someone have to check that the "free software licence" is available for the targeted repository.</div>
<div><br></div><div>Just as information :</div><div>GitHub allow creation of an organization (IPOL for example), and add a list of users under this organization.</div><div>It create a link to existing github account to the organization.</div>
<div>Here the example of the MikrosImage organization : <a href="https://github.com/mikrosimage">https://github.com/mikrosimage</a></div><div>You will see the organization member and the subproject.</div><div><br></div><div>
=> A lot of online repository propose the fact to have additionnal download (it could be useful to release pre-compiled version of the update).</div><div>For native version it could be better to link to the original archive that exist on <a href="http://ipol.im">ipol.im</a>.</div>
<div><br></div><div>Regards</div><div><br></div><div><br><br><div class="gmail_quote">2012/8/22 Nicolas Limare <span dir="ltr"><<a href="mailto:nicolas.limare@cmla.ens-cachan.fr" target="_blank">nicolas.limare@cmla.ens-cachan.fr</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br>
<br>
Switching to PDF was a way to inclease the visibility of the IPOL<br>
articles. They are quickly indexed in Google Scholar for example, and<br>
I will work on other things in the coming months (Scopus, Citeseer,<br>
DBLP, HAL, ...).<br>
<br>
But the PDF file is not everything, the software side of IPOL<br>
articles should be promoted too. But software is not indexed and<br>
searched like research papers, so we need other solutions.<br>
<br>
My idea is to store every code associated to a published IPOL article<br>
in a public source code hosting service. The first two candidates<br>
would be<br>
<br>
* github -> <a href="https://github.com/ipol-im/ipol" target="_blank">https://github.com/ipol-im/ipol</a><br>
because it is very active and dynamic<br>
* coogle code -> <a href="http://code.google.com/p/ipol/" target="_blank">http://code.google.com/p/ipol/</a><br>
because this may help appearing in google search results<br>
because of their great codesearch tool <a href="http://code.google.com/searchframe" target="_blank">http://code.google.com/searchframe</a><br>
<br>
To be clear, this would not be a service for IPOL authors, not a<br>
service for software development. It would only be two clones of a<br>
single repository with all the code published in IPOL[1], only updated<br>
to add new code. And all that is experimental, and could be changed or<br>
disappear at any time.<br>
<br>
Legally, there is no problem. Every IPOL code is under a free software<br>
license, so anyone is already allowed to gather all the code and<br>
publish it on github or anywhere else.<br>
<br>
Will it be good for the articles? Maybe, maybe not, so let's try and<br>
see. By the way, this shows why a proper README.txt file with a<br>
reference to the article is important in your IPOL code. without this<br>
reference, people getting the code won't access the article, they<br>
won't even know the article exists.<br>
<br>
I'd like to know if I missed something and if you see an problem with<br>
this experiement.<br>
<br>
Best,<br>
<br>
[1] both services offer the possibility to download only a subfolder<br>
of the repository<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Nicolas LIMARE - CMLA - ENS Cachan <a href="http://limare.perso.math.cnrs.fr/" target="_blank">http://limare.perso.math.cnrs.fr/</a><br>
IPOL - image processing on line <a href="http://www.ipol.im/" target="_blank">http://www.ipol.im/</a><br>
</font></span><br>_______________________________________________<br>
discuss mailing list<br>
<a href="mailto:discuss@list.ipol.im">discuss@list.ipol.im</a><br>
<a href="https://tools.ipol.im/mailman/listinfo/discuss" target="_blank">https://tools.ipol.im/mailman/listinfo/discuss</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div><font>Regards/Cordialement,</font></div>
<div><font>Pierre M</font></div><br>
</div>