3 ms·

Is there a niche out there for the GitHub of science? My cofounder (mikeknoop on HN) puts a lot of his scholarly research code stuffs on GitHub, but perhaps a m

by bryanh 15y ago

Is there a niche out there for the GitHub of science? My cofounder (mikeknoop on HN) puts a lot of his scholarly research code stuffs on GitHub, but perhaps a more specialized place with emphasis on peer review would be more appropriate.

patrickod 15y ago
I would have thought things like the Issues and Pull requests features of GitHub would be perfect for such discussion of projects. What in GitHub is lacking that you think would merit a different site?
- RK 15y ago
  A general project wiki would be nice. I might be missing where the equivalent feature is because I am not a very heavy github user.
  - patrickod 15y ago
    GH has wiki pages but having not used them myself I'm not sure if you can have them open for public edits.
bbgm 15y ago
There are many scientific groups where even today, no form of version control is used, even for internal work, so Github is way ahead of what is current practice in many places. There is a lot of good scientific code in various repositories and I don't see why anything special is required. As computation becomes even more important across many scientific areas, there is a lot of need for discipline. If scientists learn how to use version control and repositories just by default, that will go a long way towards reproducibility. The Galaxy project does a great job of trying to foster such an environment: http://genomebiology.com/2010/11/8/R86 http://genomebiology.com/2010/11/8/R86 http://galaxy.psu.edu/ http://galaxy.psu.edu/ https://bitbucket.org/galaxy https://bitbucket.org/galaxy http://wiki.g2.bx.psu.edu/Tool%20Shed http://wiki.g2.bx.psu.edu/Tool%20Shed
- kaarlo_n 15y ago
  > There are many scientific groups where even today, no form of version control is used, even for internal work ... Where I work (government research lab) people think of Subversion as a sporadic backup target, typically doing a commit every month or so, despite making frequent changes to operational code. Paradoxically, one scientist I spoke to was scared about overwriting code if he did an incorrect commit, but he's perfectly happy to have mycode.py, mycode2.py, mycode_this_one_works.py, mycode_this_one_works3.py, ...

by bryanh 15y ago

patrickod 15y ago

I would have thought things like the Issues and Pull requests features of GitHub would be perfect for such discussion of projects. What in GitHub is lacking that you think would merit a different site?

RK 15y ago
A general project wiki would be nice. I might be missing where the equivalent feature is because I am not a very heavy github user.
- patrickod 15y ago
  GH has wiki pages but having not used them myself I'm not sure if you can have them open for public edits.

bbgm 15y ago

There are many scientific groups where even today, no form of version control is used, even for internal work, so Github is way ahead of what is current practice in many places. There is a lot of good scientific code in various repositories and I don't see why anything special is required. As computation becomes even more important across many scientific areas, there is a lot of need for discipline. If scientists learn how to use version control and repositories just by default, that will go a long way towards reproducibility. The Galaxy project does a great job of trying to foster such an environment: http://genomebiology.com/2010/11/8/R86 http://genomebiology.com/2010/11/8/R86 http://galaxy.psu.edu/ http://galaxy.psu.edu/ https://bitbucket.org/galaxy https://bitbucket.org/galaxy http://wiki.g2.bx.psu.edu/Tool%20Shed http://wiki.g2.bx.psu.edu/Tool%20Shed

kaarlo_n 15y ago
> There are many scientific groups where even today, no form of version control is used, even for internal work ... Where I work (government research lab) people think of Subversion as a sporadic backup target, typically doing a commit every month or so, despite making frequent changes to operational code. Paradoxically, one scientist I spoke to was scared about overwriting code if he did an incorrect commit, but he's perfectly happy to have mycode.py, mycode2.py, mycode_this_one_works.py, mycode_this_one_works3.py, ...