Ten Simple Rules for the Open Development of Scientific Software

  • Andreas Prlić mail,

    Affiliation: San Diego Supercomputer Center, University of California San Diego, La Jolla, California, United States of America

  • James B. Procter

    Affiliation: School of Life Sciences Research, College of Life Sciences, University of Dundee, Dundee, Scotland, United Kingdom


Reader Comments (3)

Post a new comment on this article

State your licensing terms clearly

Posted by simon_guest on 16 Jan 2013 at 02:06 GMT

Too much software is just posted on SourceForge or GitHub with no license at all, which makes it essentially unusable. An explicit license is necessary if you want others to pick up your software and do interesting things with it (like package it for other users).

No competing interests declared.