Timeline for How to link code to publications
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:53 | history | edited | CommunityBot |
replaced http://scicomp.stackexchange.com/ with https://scicomp.stackexchange.com/
|
|
| Oct 10, 2012 at 22:37 | comment | added | cboettig | @stali recall that github also supports custom webpages for repositories through gh-pages and downloadable tarballs from downloads. But neither Google nor Github provide a separate DOI for the code, nor address the archival longevity beyond the life of the company afaik. | |
| Oct 10, 2012 at 20:55 | comment | added | stali | Google code might be slightly better for the wider audience as you can have a nicer webpage with summary, images, DOI link, higher visibility in search etc. You should definitely put a tgz in the Download section and provide a link on the front page. Remember that majority of non-developers are not even familiar with version control let alone git/hg. Subversion is as far as I would go for a broader audience. | |
| Oct 10, 2012 at 18:09 | comment | added | cboettig | Yeah, great point about the licenses still being somewhat problematic, particularly for more fully developed software. For scripts to replicate an analysis I could see CC0 being more appropriate. | |
| Oct 10, 2012 at 17:50 | comment | added | Aron Ahmadia | figshare is a great step forward, though the CC-BY license is not a software license, and I don't know how many scientists are willing to release their code under CC0, so this is an issue to address. I do appreciate that they use DOI and CLOCKSS, though, that is great. | |
| Oct 10, 2012 at 17:13 | history | answered | cboettig | CC BY-SA 3.0 |