search

RWilton / Arioc

Arioc: GPU-accelerated DNA short-read alignment
BSD 3-Clause "New" or "Revised" License
55 stars 8 forks source link

Consider putting source code under version control #5

Closed standage closed 5 years ago

standage commented 5 years ago

First I want to say thanks for publishing this project, for making the source code for stable releases available, and for your engagement on this issue tracker.

I'm curious if the decision to keep the source code out of version control is deliberate. I'm sure you're aware of the some of the convenient tools Github provides: browsing source code, viewing diffs between commits, commenting on source code or on commits/edits to the source code, supporting patch submissions, etc. If there were concerns about privacy or access control I would assume the source code for each release wouldn't be public. Are there other concerns about putting Arioc's source code under version control?

RWilton commented 5 years ago

The Arioc sources are public because we wrote journal articles about the software.

The source code is indeed under version control "internally" along with other related software projects. We chose not to use github for versioning primarily because there has been very little public interest in modifying the code apart from getting it to build in various incarnations of Linux.

standage commented 5 years ago

Understood. It may be ambitious to expect that this would become a booming open source project, but on the other hand there’s probably nothing to lose by including the source code in the public-facing repo. #shrug

In any case, good work!

antonkulaga commented 5 years ago

@RWilton why cannot you just mirror it to github? Even for those people who do not have time to contribute there is sometimes a need to build from master as some nasty bugs can be fixed between releases

standage commented 5 years ago

Another benefit is that I would have been able to link directly to the lines in question in this comment.