Closed benmarwick closed 9 years ago
Thanks Ben; references added.
Let's see what comes up -- I agree that an email list may be seen as "lowest tech" and hence easiest for people to use. I've just committed to join that SE site.
http://academia.stackexchange.com/questions/tagged/reproducible-research
might be an alternative location that a colleague mentioned. The 'open-science' one has just reached 200 committed, so should be going into beta soon, but probably won't be ready any-time soon.
Yes, that academia one probably the most suitable of the stackexchange suite of sites, and quite active too.
That reminded me of this email list https://groups.google.com/forum/m/#!forum/reproducible-research
Perhaps we could include a list of something like 'community forums' that include all of these to show where people can engage more?
Relating to #2 I'd like to add these references:
Boettiger, C. (2015). An introduction to docker for reproducible research. SIGOPS Oper. Syst. Rev., 49(1), 71–79
Kahneman, Daniel 2014. A new etiquette for replication. Social Psychology, Vol 45(4), 2014, 310-311.
Ram, K. (2013). Git can facilitate greater reproducibility and increased transparency in science. Source Code for Biology and Medicine,
Stodden, V. (2009). The legal framework for reproducible scientific research: Licensing and copyright. Computing in Science Engineering, 11(1), 35–40. doi:10.1109/MCSE.2009.19 8(1), 7.
Vihinen, M. (2015). No more hidden solutions in bioinformatics. Nature, 521(7552), 261–261. doi:10.1038/521261a
On the question of an online forum where people can ask questions to a community to get help with issues surrounding code sharing, I think it GitHub org is a great idea to enable code review, testing and collaboration, but do you think we might also consider an email list? That's a simple communication method that we can expect anyone to be comfortable with. Using a GitHub issue tracker assumes some familiarity with that, which could be a barrier to someone who has questions on getting started, or who isn't using GitHub to share their code. It might get a bit awkward having conversations in parallel on email and an issue tracker though (I see on the software carpentry email list they are frequently diverting email threads to issue trackers to reduce list traffic). This Q&A could be a suitable place, but doesn't seem ready yet: http://area51.stackexchange.com/proposals/65426/open-science