Want to help the Audacity project? Here are some suggestions:
- Creating your own Plug-in - Audacity Plug-ins can be a good place to start developing extensions to Audacity.
- SummerOfCode_Planning - Help us get ready for Google Summer of code 2008.
Help us by removing spam links from the wiki. Improve pages by making the writing clearer and correcting spelling and grammar.
Audacity Help Documentation
We often link to pages in the 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 e.g. the Manual up-to-date and relevant.
Audacity is translated into many languages. We need translators for other languages. We'd also like to make the process of translation more streamlined.
Forums and Help
It's a great help to have people answering Audacity questions on the forums and help mailing list. People who help like this also manage the FAQ and have very important input into development decisions.
We need graphics for Audacity itself and for the website. Someone with graphics skills could help us unify the program and website. 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:
- Google Summer of Code 2008
- Audacity language learning
Testers. Test coordinators. Test script writers. Quality system designers and managers. Yay. We need you all.
We always need more developers! Here is a proposed 'Audacity Needs You!' page for the main Audacity website. The intention is to put it in a high traffic area.
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 .