Developers

Ohloh has statistics on the value of Audacity development. The Ohloh "badge" at the bottom of each page on this site shows updated summary values. We set up the Ohloh pages about Audacity so the statistics show only the values of Audacity-specific development, excluding the third-party code libraries Audacity uses. The Code tab on the Ohloh site shows the progress of code development.

Mailing Lists

Join the audacity-devel mailing list to discuss current and future development, or to get help building and modifying the Audacity source code.

CVS

You can get the latest Audacity stable or development code from our CVS repository.

• Browse the source code online sorted by file name or date.

• Type this at the command line to check out the latest stable source code from CVS: (1.2)

  cvs -d:pserver:anonymous@audacity.cvs.sourceforge.net:/cvsroot/audacity checkout -r AUDACITY_1_2 audacity

• Or type this at the command line to check out the latest beta/development source code from CVS: (1.3)

  cvs -d:pserver:anonymous@audacity.cvs.sourceforge.net:/cvsroot/audacity checkout audacity

For more information, read the SourceForge CVS instructions. If using an interface CVS tool such as TortoiseCVS or WinCVS, use the command instructed in the tool's documentation.

See the source code page for compilation instructions.

Bug Tracking

The Audacity developers now use Release Checklist on the Wiki to keep track of confirmed bugs. Check the list of Release Issues on that page if you are looking for something to work on.

Note: This Checklist is for development use only. If you are a user reporting new bugs, please use our Forum or e-mail us instead.

Submitting Patches

We welcome patches from developers. Please see our Submitting Patches page on the Wiki.