On Thu, Jul 23, 2015 at 5:50 PM, Neil Chue Hong (SSI) <[email protected]> wrote: > ... > > The one thing that I'm not sure about is the cloning of code into a > journal-specific GitHub repository (e.g. > https://github.com/ElsevierSoftwareX). > > If the software is already being developed on GitHub, it seems to me > that it doesn't add anything either in terms of preservation (why not > just point to the original GitHub repo?), or in terms of > improving community ...
I believe would be a snapshot of the repository at the time of publication, which ensures the Journal can keep this as a long term archive. Right now it is very easy for a developer to delete their own GitHub content completely (or more subtly, rewrite history). So it does actually add something tangible in terms of preservation. See also archiving a snapshot of your GitHub repository with Zenodo to get a nice citable DOI: https://guides.github.com/activities/citable-code/ Peter _______________________________________________ Discuss mailing list [email protected] http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
