In the past I've used a DOI service to make my code able to be cited by others (and myself). This makes sure the code is a "snapshot" of a given point in time, so that even if you later make modifications to your code, someone else can exactly reproduce your results (assuming the same input data). Of course, you can also maintain an updated "fork" of your code elsewhere.
For example,
http://dx.doi.org/10.5281/zenodo.20043 points to
https://github.com/MPagel/readseq/tree/v2.02, but I've made one additional modification to my main branch at github.../readseq/
(so zenodo is the DOI-issuer)
================
Matthew D. Pagel
Database Manager
Core Array: California Fish Tracking Consortium
Biotelemetry Lab
University of California, Davis
1331(*) Academic Surge Building
UCD Department of Wildlife, Fish and Conservation Biology
One Shields Ave
Davis, CA 95616
Office* Ph:
530 752-5372
Lab Ph:
530 752-1156
http://cftc.metro.ucdavis.edu/news/
*new information effective 2016-09-13
> --
> Check out our R resources at
http://d-rug.github.io/
> ---
> You received this message because you are subscribed to the Google Groups "Davis R Users' Group" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
davis-rug+...@googlegroups.com <mailto:
davis-rug+...@googlegroups.com>.
> Visit this group at
https://groups.google.com/group/davis-rug.
> For more options, visit
https://groups.google.com/d/optout.