[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Axiom-developer] PLOS Rules for documenting scientific software

From: William Sit
Subject: Re: [Axiom-developer] PLOS Rules for documenting scientific software
Date: Sun, 23 Dec 2018 02:32:33 +0000



William Sit
Professor Emeritus
Department of Mathematics
The City College of The City University of New York
New York, NY 10031

From: Axiom-developer <address@hidden> on behalf of Tim Daly <address@hidden>
Sent: Saturday, December 22, 2018 3:41 PM
To: axiom-dev
Subject: [Axiom-developer] PLOS Rules for documenting scientific software

1) Write comments as you code
2) Include examples and lots of them
3) Include a quickstart guide
4) Include a README file with basic information
5) Include a help command for command line interfaces
6) Version control your documentation
7) Fully document your application program interface
8) Use automated documentation tools
9) Write error messages that provide solutions or point to the documentation
10) Tell people how to cite your software

Axiom-developer mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]