[IPOL discuss] public clone repositories of the IPOL codes?

[Pierre Moulon]

Hi,

Some online repository force to label all the subdirectory under the same
licence.
(code google, sourceforge ...) (not github)
So someone have to check that the "free software licence" is available for
the targeted repository.

Just as information :
GitHub allow creation of an organization (IPOL for example), and add a list
of users under this organization.
It create a link to existing github account to the organization.
Here the example of the MikrosImage organization :
https://github.com/mikrosimage
You will see the organization member and the subproject.

=> A lot of online repository propose the fact to have additionnal download
(it could be useful to release pre-compiled version of the update).
For native version it could be better to link to the original archive that
exist on ipol.im.

Regards



2012/8/22 Nicolas Limare <nicolas.limare at cmla.ens-cachan.fr>

> Hi all,
>
> Switching to PDF was a way to inclease the visibility of the IPOL
> articles. They are quickly indexed in Google Scholar for example, and
> I will work on other things in the coming months (Scopus, Citeseer,
> DBLP, HAL, ...).
>
> But the PDF file is not everything, the software side of IPOL
> articles should be promoted too. But software is not indexed and
> searched like research papers, so we need other solutions.
>
> My idea is to store every code associated to a published IPOL article
> in a public source code hosting service. The first two candidates
> would be
>
> * github -> https://github.com/ipol-im/ipol
>   because it is very active and dynamic
> * coogle code -> http://code.google.com/p/ipol/
>   because this may help appearing in google search results
>   because of their great codesearch tool
> http://code.google.com/searchframe
>
> To be clear, this would not be a service for IPOL authors, not a
> service for software development. It would only be two clones of a
> single repository with all the code published in IPOL[1], only updated
> to add new code. And all that is experimental, and could be changed or
> disappear at any time.
>
> Legally, there is no problem. Every IPOL code is under a free software
> license, so anyone is already allowed to gather all the code and
> publish it on github or anywhere else.
>
> Will it be good for the articles? Maybe, maybe not, so let's try and
> see. By the way, this shows why a proper README.txt file with a
> reference to the article is important in your IPOL code. without this
> reference, people getting the code won't access the article, they
> won't even know the article exists.
>
> I'd like to know if I missed something and if you see an problem with
> this experiement.
>
> Best,
>
> [1] both services offer the possibility to download only a subfolder
> of the repository
>
> --
> Nicolas LIMARE - CMLA - ENS Cachan
> http://limare.perso.math.cnrs.fr/
> IPOL - image processing on line
> http://www.ipol.im/
>
> _______________________________________________
> discuss mailing list
> discuss at list.ipol.im
> https://tools.ipol.im/mailman/listinfo/discuss
>



-- 
Regards/Cordialement,
Pierre M
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tools.ipol.im/mailman/archive/discuss/attachments/20120823/87562186/attachment.html>