Difference between revisions of "Contribute"

From Audacity Wiki
Jump to: navigation, search
(mention audacity-users list, other tweaks)
(Summary at start.)
Line 1: Line 1:
{{Intro|1=''Want to help the Audacity project?''   Here are some suggestions:
+
{{Intro|1='''November 6th 2009:''' We are getting ready for our first stable release of Audacity in about two years!|2=}}
* '''We need you to test our latest [[Nightly Builds|Development Builds]]''' so we can progress our code to readiness for a new 2.0 Stable release
+
 
* '''We need help completing and translating our [http://www.audacityteam.org/manual/index.php?title=Main_Page Beta Manual]''' so it is ready for that Stable release
+
 
* '''[[Audacity Needs You|We need more developers]]'''  -  we're considering a recruitment drive around the release of Audacity 2.0
+
 
* '''[[Creating your own Plug-in|Creating Plug-in modules]]''' can help extend Audacity's  capabilities.|2=}}
+
==Help Us With 2.0==
 +
 
 +
* We would love '''''[[Nightly_Builds|help with testing]]'''''.
 +
* Help us with '''''[http://manual.audacityteam.org/index.php?title=Main_Page the manual]''''' for 2.0, which is in its own wiki.
 +
* If you're a programmer, check out the '''''[[Developer_Guide|developer guide]]''''', subscribe to '''''[[Community|audacity-devel]]''''' and when you've got audacity compiling, tell us if there's anything on the '''''[[Release_Checklist|release checklist]]''''' you'd like to tackle.  For 2.0 we're particularly keen to hear from people developing on Windows 7 or ensuring Audacity works well on upcoming Ubuntu releases.
 +
* We need translators for wiki-manual and the '''''[[Translating_Audacity|program]]'''''.
 +
 
 +
 
 +
==Other Ways To Help==
 +
 
 +
* Help us with this wiki and ideas for '''''[[Wiki Development Checklist|onward development]]'''''.
 +
* Help out on the '''''[http://forum.audacityteam.org/ forum]''''' by answering user's questions.
 +
* Add features that you care about to our '''''[[Feature Requests]]''''' page, and/or vote there.
 +
* If you're a student and interested in '''''[[GSoC_FAQ|GSoC]]''''' in 2010, start planning for it now.
 +
 
 +
 
 +
 
 +
__TOC__
 +
 
 +
 
 +
'''In more detail...'''
 +
 
 +
==Quality==
 +
 
 +
Testers.  Test coordinators.  Test script writers.  [[Quality]] system designers and managers.  We need you all.
 +
 
 +
 
 +
== Documentation Writers (The 2.0 Manual) ==
 +
 
 +
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. '''We need help bringing this Manual forward to readiness for the next 2.0 Stable release.'''   
 +
 
 +
 
 +
==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 users getting involved in the development process. Join our [http://lists.sourceforge.net/lists/listinfo/audacity-devel developers' mailing list] and introduce yourself!
  
  
Line 11: Line 45:
  
  
== Documentation Writers ==
+
== Documentation Writers (This Wiki) ==
  
 
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 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 [http://www.audacityteam.org/manual/index.php?title=Main_Page Beta Manual] up-to-date and relevant. '''We need help bringing this Manual forward to readiness for the next 2.0 Stable release.'''   
 
  
  
Line 47: Line 80:
  
 
We need help with campaigns:
 
We need help with campaigns:
* Audacity took part in [[:Category:GSoC|GSoC]] (Google Summer of Code) in 2008 and is again mentoring students in 2009. We always need help planning for future participation.  
+
* Audacity took part in [[:Category:GSoC|GSoC]] (Google Summer of Code) in 2008 and 2009. We always need help planning for future participation, from getting ready to run a GSoC, to alerting potential students to the opportunity, to co-ordinating development during GSoC itself.
* We're considering being part of the next [http://code.google.com/opensource/ghop/2007-8/ GHOP] (Google Highly Open Participation) Contest
+
* We're considering being part of the next [http://code.google.com/opensource/ghop/2009-10/ GHOP] (Google Highly Open Participation) Contest
 
* Audacity language learning initiative.  This is a plan to develop an ecosystem of language learning tools around Audacity.  Part of the plan involves building better links with the [http://www.rockbox.org rockbox] project so that Audacity can author audio in structured formats that assists language learners.  This was talked about briefly at the 2008 GSoC mentor summit, but has not progressed beyond that.
 
* Audacity language learning initiative.  This is a plan to develop an ecosystem of language learning tools around Audacity.  Part of the plan involves building better links with the [http://www.rockbox.org rockbox] project so that Audacity can author audio in structured formats that assists language learners.  This was talked about briefly at the 2008 GSoC mentor summit, but has not progressed beyond that.
  
  
==Quality==
+
== Ideas? Want to Contact Us?==
Testers.  Test coordinators.  Test script writers.  [[Quality]] system designers and managers.  We need you all.
 
  
 +
Didn't find what you were looking for?  Here are various ways to '''''[[Community|contact us]]'''''.
  
==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 users getting involved in the development process. Join our [http://lists.sourceforge.net/lists/listinfo/audacity-devel developers' mailing list] and introduce yourself!
 
 
 
== Ideas? Want to Contact Us?==
 
 
Are we missing something? Have you been inspired by any of the above? If so, [http://audacity.sourceforge.net/contact/#feedback get in touch with us] and let us know how you can help.
 
  
  
 
[[Category:Participation]]
 
[[Category:Participation]]

Revision as of 18:12, 6 November 2009

November 6th 2009: We are getting ready for our first stable release of Audacity in about two years!


Help Us With 2.0

  • We would love help with testing.
  • Help us with the manual for 2.0, which is in its own wiki.
  • If you're a programmer, check out the developer guide, subscribe to audacity-devel and when you've got audacity compiling, tell us if there's anything on the release checklist you'd like to tackle. For 2.0 we're particularly keen to hear from people developing on Windows 7 or ensuring Audacity works well on upcoming Ubuntu releases.
  • We need translators for wiki-manual and the program.


Other Ways To Help

  • Help us with this wiki and ideas for onward development.
  • Help out on the forum by answering user's questions.
  • Add features that you care about to our Feature Requests page, and/or vote there.
  • If you're a student and interested in GSoC in 2010, start planning for it now.



In more detail...

Quality

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


Documentation Writers (The 2.0 Manual)

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.


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 users getting involved in the development process. Join our developers' mailing list and introduce yourself!


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 (This Wiki)

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.


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.


Forum and -users mailing list

The main way we help users who need personal support with Audacity is on our Forum. 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.

An alternative way Audacity users help each other and learn about our program is the audacity-users mailing list. This is a subscription-only mailing list where messages to the list are sent out directly by e-mail. Feel free to join audacity-users and give a hand to new users!


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:

  • Audacity took part in GSoC (Google Summer of Code) in 2008 and 2009. We always need help planning for future participation, from getting ready to run a GSoC, to alerting potential students to the opportunity, to co-ordinating development during GSoC itself.
  • We're considering being part of the next GHOP (Google Highly Open Participation) Contest
  • Audacity language learning initiative. This is a plan to develop an ecosystem of language learning tools around Audacity. Part of the plan involves building better links with the rockbox project so that Audacity can author audio in structured formats that assists language learners. This was talked about briefly at the 2008 GSoC mentor summit, but has not progressed beyond that.


Ideas? Want to Contact Us?

Didn't find what you were looking for? Here are various ways to contact us.