Guest blog post from Dr Karthik Ram (KR) and Dr C. Titus Brown (CTB) who have been working with BioMed Central on our recently announced collaboration with the social coding repository, GitHub.
We live in an increasingly collaborative era, where the Internet enables distance collaboration almost trivially – not just with e-mail and videoconferencing, but with collaborative realtime document editing and networked transmission of data and analyses. These tools allow us to collectively leverage many resources to rapidly solve problems and ultimately accelerate scientific discovery. While these tools and technologies are fundamentally changing how we collaborate on science, there is still considerable room for improvement in how we are using them.
Programmers, and especially the world of open source software development, have developed a number of tools that enable easy distance collaboration and sharing of data and code. One of the most important is version control – tracking of changes and authorship – which, in programming, is largely used for writing and sharing code, tracking and annotating contributions, and resolving changes to the same section of a program. In recent years a wide variety of version control software has become readily and freely available, including Subversion, git, and Mercurial.
Motivated by much the same problems as programmers – how do I track changes and authorship, and resolve conflicting changes? – scientists have increasingly begun using these version control systems not only for software but for paper and grant writing, and even for tracking data and metadata. In particular, CTB and others have argued that version control should be a required “good practice” for all computational science in practice. This increased interest in versioning for science has led to a realization that, collectively, we are lacking in workflows and practices that take advantage of version control. This is especially true for git and Mercurial, both decentralized version control systems that enable many different modes of collaboration.
One of us, KR, has just published a paper showing how “git can facilitate greater reproducibility and increased transparency in science.” Occasioned in part by this first paper, a group of us is working to document and demonstrate the many uses to which we have put git. These include software development and dissemination, paper and grant writing, paper and grant feedback, contributions to Wiki-like community documentation sites, and sharing of data analysis “notebooks” and executable papers.
In tandem with git and Mercurial, two commercial Web sites have appeared, GitHub and BitBucket. These sites serve as central “hubs” through which code and other electronic artifacts can be communicated, shared, and collaborated upon.
We believe that KR’s paper in Source Code for Biology and Medicine is a solid first step in showing how git and sites like GitHub can be used for versioning, collaboration, and feedback on research. Separately, CTB’s group and others have explored git’s use for publishing reproducible notebooks and enabling community documentation.
Git and Mercurial, and the sites that support public hosting of git and Mercurial repositories such as GitHub and BitBucket, do provide an excellent solution to the problem of posting code from published modeling and data analysis efforts. Rather than such code being hosted on university Web sites that languish unmaintained, or deposited in hard-to-find journal supplements, GitHub and BitBucket (among other sites) provide stable hosting for code. Moreover, since these sites are widely used outside the research community – most especially in the open source community – the likelihood that they will disappear with loss of funding body interest is low.
One of the most interesting potential uses for git and Mercurial is in supporting the “forking”, or copying and modification, of data analysis pipelines, to enable field-wide reuse of the analysis pipeline provided in a published paper. Unlike more centralized systems such as Subversion, git and Mercurial both readily support diverging development of software starting from a common base by other groups. This kind of branching enables remixing of research software, while retaining all provenance information. Because projects can easily be made available for branching upon publication by using GitHub and BitBucket for post-publication development and dissemination, many barriers to remixing and reuse of software are significantly lowered.
Git and Mercurial, and the GitHub and BitBucket sites, are not perfect fits for the scientific process. While free public and private repositories are available to academics on both sites, neither site is archival, and so sites such as figshare or field-specific archives may be needed to provide a lasting home for published software and data.
We have only begun to understand and detail the many uses of distributed version control in conducting research, but already it offers many exciting opportunities to improve on existing workflows. We look forward to exploring this area in the future and building a real community of practice.
Our next steps in this area are to gather further examples of the use of version control for scientific research; develop tutorials, handbooks, and training materials; survey more scientific users on their current and planned practices; and ultimately publish additional works on how version control is being used and how it could be used to improve scientific practice and efficiency.
For me, one of the other interesting features of a site like GitHub is the ability to generate permalinks referring to specific commit IDs. This would be for situations such as the version of the software which is used to generate the results in an associated paper.
For instance, you might choose to designate the “source” version of Karthik’s revised paper that was accepted by SCFBM as: https://github.com/karthikram/smb_git/tree/3e42ece1a6ecbea07e3397b5a26f335fa61dd0ba
Which would also correspond to the deposited version in Figshare with DOI: https://dx.doi.org/10.6084/m9.figshare.155613
The question then becomes – is it appropriate to mint a DOI to the permalink GitHub identifier directly?
This is great work, and is complementary to Jason Priem and Heather Piwowar’s work via ImpactStory to understand the “natural” analogies for things such as citation (forking?) for software: https://blog.impactstory.org/2013/01/18/github/
“collectively, we are lacking in workflows and practices that take advantage of version control.”
THIS – this is the problem with science right now. DropBox has almost revolutionized what passes for “workflow” in my lab, even though it’s clearly an imperfect solution to the (spectrum of) problems.
‘Course if I used the phrase “work flow” I doubt anyone would know what I was talking about …
Great article, guys… BTW, this is my take on a ‘git for scientists’ tutorial that I wrote after teaching a SWC workshop and iterating on the feedback we got plus my own notes: https://nbviewer.ipython.org/urls/github.com/fperez/reprosw/raw/master/Version%2520Control.ipynb. I’ve taught off of this a few times already and I’m reasonably happy with the results.