Difference between revisions of "Contribute"

From Audacity Wiki
Jump to: navigation, search
(Link to GSoC 2008 changed.)
(Tweak text and add intro panel)
Line 1: Line 1:
Want to help the Audacity project? Here are some suggestions:
+
{{Intro|1=''Want to help the Audacity project?''   Here are some suggestions:
 +
* '''We need help completing and translating our [http://www.audacityteam.org/manual/index.php?title=Main_Page Beta Manual].''' The current Beta is the basis of our next 1.4 Stable release. 
 +
* '''[[Audacity Needs You|We need more developers]].''' We're planning a recruitment drive around the release of Audacity 1.4.
 +
* '''Help us plan for [[GSoC Planning|Google Summer of Code 2009]].'''
 +
* '''[[Creating your own Plug-in|Creating Plug-in modules]]''' can help extend Audacity's  capabilities.|2=}}
  
* [[Creating your own Plug-in]] - Audacity Plug-ins can be a good place to start developing extensions to Audacity.
 
* [[GSoC Planning|Summer of Code Planning]] - Help us get ready for Google Summer of Code 2009.
 
* '''[[Audacity Needs You|We need more developers]]''' - We're planning a recruitment drive around the release of version 1.4.
 
  
=Wiki Gnomes=
+
==Wiki Gnomes==
 +
 
 
Help us by removing spam links from the Wiki.  Improve pages by making the writing clearer and correcting spelling and grammar.
 
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.
 
  
=Translators=
+
== Documentation Writers ==
Audacity is translated into many languagesWe need translators for other languages.  We'd also like to make the process of translation more streamlined.
+
 
 +
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 updatingScreenshots on the Wiki need updating tooThe 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 [http://www.audacityteam.org/manual/index.php?title=Main_Page Beta Manual] up-to-date and relevant.
 +
 
  
=Forums and Help=
+
==Translators==
It's a great help to have people answering Audacity questions on the forums and help mailing list.  People who help like this provide valuable input for the website Frequently Asked Questions and to the wider task of making development decisions.
 
  
=Website text=
+
The Audacity software and web site is translated into many languages. We need [http://audacity.sourceforge.net/community/translation translators] for other languages.  
The website 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 while keeping the site easy to use and free of "typos". There is a list of pending suggested website changes [[Pending website changes|here]].  
 
  
=Graphics=
+
Our officially released documentation has never been translated. We welcome offers of help to work on translating our [http://www.audacityteam.org/manual/index.php?title=Main_Page Beta Manual].
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.
+
 
 +
Suggestions on improving/streamlining the way we translate are welcome too.
 +
 
 +
 
 +
==Forums ==
 +
 
 +
The main way we help users who need personal support with Audacity is on our [http://audacityteam.org/forum/index.php 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 [http://audacity.sourceforge.net/help/faq Frequently Asked Questions] and influences the wider task of making development decisions.
 +
 
 +
 
 +
==Web site text==
 +
 
 +
The main [http://audacity.sourceforge.net/ 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 website changes|pending web site changes]] and we welcome [[Talk:Pending website changes|comments about our web site]].
 +
 
 +
 
 +
==Graphics==
 +
 
 +
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.
 +
 
 +
 
 +
==Campaigns==
  
=Campaigns=
 
 
We need help with campaigns:
 
We need help with campaigns:
 
* Google [[GSoC Planning|Summer of Code 2009]]
 
* Google [[GSoC Planning|Summer of Code 2009]]
 
* Audacity language learning
 
* Audacity language learning
  
=Quality=
 
Testers.  Test coordinators.  Test script writers.  [[Quality]] system designers and managers.  Yay.  We need you all.
 
  
=Developers=
+
==Quality==
'''We always need more developers!'''  Here is a proposed '[[Audacity_Needs_You|Audacity Needs You!]]' page for the main Audacity website.  The intention is to put it in a high traffic area.  Better developer documentation would also help us.  Our [[Developer_Guide#Platform_Specific_Guides|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.
+
Testers.  Test coordinators.  Test script writers.  [[Quality]] system designers and managers.  We need you all.
 +
 
 +
 
 +
==Developers==
 +
 
 +
'''We always need more developers!'''  Here is a proposed "[[Audacity_Needs_You|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 [[Developer_Guide#Platform_Specific_Guides|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?==
  
=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 {{external|[http://lists.sourceforge.net/lists/listinfo/audacity-devel  join our friendly developers' mailing list]}}.
 
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 {{external|[http://lists.sourceforge.net/lists/listinfo/audacity-devel  join our friendly developers' mailing list]}}.
  
  
 
[[Category:Participation]]
 
[[Category:Participation]]

Revision as of 19:07, 21 September 2008

Want to help the Audacity project?   Here are some suggestions:


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.


Translators

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.


Forums

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.


Graphics

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.


Campaigns

We need help with campaigns:


Quality

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


Developers

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 .