Ten Simple Rules for the Open Development of Scientific Software

Open Access

Andreas Prlić ,

* E-mail: andreas.prlic@gmail.com

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

People with similar or related research interests who discover the project will find that they have more to gain from collaborating than from competing with the original developers
http://ploscompbiol.org/article/info:doi/10.1371/journal.pcbi.1002802#article1.body1.sec5.p1

If the project is well organized, and transparent this should be the case. I like the quote from here [1]:

"Making important decisions in private is like spraying contributor repellant on your project."

Ahh...

[1] http://producingoss.com/en/setting-tone.html#avoid-private-discussions

No competing interests declared.

Open source software
Is the Subject Area "Open source software" applicable to this article?

Thanks for your feedback.
Computer software
Is the Subject Area "Computer software" applicable to this article?

Thanks for your feedback.
Scientists
Is the Subject Area "Scientists" applicable to this article?

Thanks for your feedback.
Eyes
Is the Subject Area "Eyes" applicable to this article?

Thanks for your feedback.
Software tools
Is the Subject Area "Software tools" applicable to this article?

Thanks for your feedback.
Source code
Is the Subject Area "Source code" applicable to this article?

Thanks for your feedback.
Research funding
Is the Subject Area "Research funding" applicable to this article?

Thanks for your feedback.
Sustainability science
Is the Subject Area "Sustainability science" applicable to this article?

Thanks for your feedback.