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

Daniel Kondermann daniel.kondermann at iwr.uni-heidelberg.de
Thu Aug 23 11:38:31 CEST 2012


Sound like a sensible plan.

There also are all these pages such as sourceforge, codeforge and
hundreds of others. I think it's not so easy to access them, but they
are regularly found by google.

Another interesting thing might be to generate redistributables for
package managers, so you can use your command line to call apt-get ipol.
Yet here I don't see a lot of visibility boosts.

Best,
Daniel

Am 22/08/2012 18:47, schrieb Nicolas Limare:
> 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
> 
> 
> 
> _______________________________________________
> discuss mailing list
> discuss at list.ipol.im
> https://tools.ipol.im/mailman/listinfo/discuss
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 552 bytes
Desc: OpenPGP digital signature
URL: <http://tools.ipol.im/mailman/archive/discuss/attachments/20120823/9b259b22/attachment.pgp>


More information about the discuss mailing list