From Audacity Wiki
Revision as of 20:22, 30 May 2009 by Galeandrews (talk | contribs) (GSoC 2009 no longer at planning stage; mention GHOP (what is the "Audacity language learning" campaign)?)
Jump to: navigation, search
Want to help the Audacity project?   Here are some suggestions:
  • We need you to test our latest Development Builds so we can progress our code to readiness for a new 2.0 Stable release
  • We need help completing and translating our Beta Manual so it is ready for that Stable release
  • We need more developers - we're considering a recruitment drive around the release of Audacity 2.0
  • Creating Plug-in modules can help extend Audacity's capabilities.

Wiki Gnomes

Help us by removing spam links from the Wiki. Improve pages by making the writing clearer and correcting spelling and grammar.

Documentation Writers

We often link to pages in this Wiki when answering questions from users. Help us keep these pages including the Tutorials up-to-date. As the program changes, these pages need updating. Screenshots on the Wiki need updating too. The Beta build of Audacity makes capturing the screenshots easier.

We also want to hear from any highly experienced users who can help with keeping our officially released documentation such as the online Beta Manual up-to-date and relevant. We need help bringing this Manual forward to readiness for the next 2.0 Stable release.


The Audacity software and web site is translated into many languages. We need translators for other languages.

Our officially released documentation has never been translated. We welcome offers of help to work on translating our Beta Manual.

Suggestions on improving/streamlining the way we translate are welcome too.


The main way we help users who need personal support with Audacity is on our Forums. If you are an experienced user, you can perform a great service for Audacity by helping to answer Forum questions. Monitoring the questions and issues that arise provides valuable input for our Frequently Asked Questions and influences the wider task of making development decisions.

Web site text

The main web site needs to be kept up-to-date not only so that Frequently Asked Questions are relevant, but so that other information is added when necessary. Of course we also want to keep the site easy to use and free of "typos". We have a list of pending web site changes and we welcome comments about our web site.


We need graphics for Audacity itself, and for our main web site and Wikis. Someone with graphics skills could help us unify the program and our sites. We need a graphic designer with an eye for the whole picture who can help with improving Audacity's graphics in a systematic way.


We need help with campaigns:

  • Audacity took part in GSoC (Google Summer of Code) in 2008 and is again mentoring students in 2009. We always need help planning for future participation.
  • We're considering being part of the next GHOP (Google Highly Open Participation) Contest
  • Audacity language learning


Testers. Test coordinators. Test script writers. Quality system designers and managers. We need you all.


We always need more developers! Here is a proposed "Audacity Needs You!" page for the main Audacity web site. The intention is to put it in a high traffic area. Better developer documentation would also help us. Our guides for compiling Audacity could do with streamlining. The relative difficulty of compiling Audacity on Mac and Windows is one barrier to more getting more users involved in the development process.

Ideas? Want to Contact Us?

Are we missing something? Have you been inspired by any of the above? If so, get in touch with us and let us know how you can help. Simply join our friendly developers' mailing list .