Difference between revisions of "Contribute"

From Audacity Wiki
Jump to: navigation, search
m (Reverted edits by Denny123 (Talk) to last revision by James)
(P1 downgraded to P2)
(36 intermediate revisions by 7 users not shown)
Line 1: Line 1:
{{Intro|1='''November 6th 2009:''' We are getting ready for our first stable release of Audacity in about two years!|2=}}
+
{{ednote|[[ToDo-2]] The section on Graphics needs an update}}
 +
{{Intro|Audacity is the result of work by volunteers developing, translating, documenting and helping users.|Here are some of the ways you can keep Audacity moving forward as a high quality application with great support and documentation.}}
  
 +
<hr style="height=1px;">
  
 
+
{|style="width:100%;"
==Help Us With 2.0==
+
|style="width:20%;"|[[File:Feedback.png|110px|link=Give Feedback]]
 
+
|style="width:20%;"|[[File:Develop.png|110px|link=For Developers]]
* We would love '''''[[Nightly_Builds|help with testing]]'''''.
+
|style="width:20%;"|[[File:Translate.png|110px|link=For Translators]]
* Help us with completing or translating the '''''[http://manual.audacityteam.org/index.php?title=Main_Page manual]''''' for 2.0, which is in its own wiki.
+
|style="width:20%;"|[[File:Support.png|110px|link=Support other Users]]
* We also need translators for the '''''[[Translating_Audacity|program]]'''''.
+
|-
* 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 tackleFor 2.0 we're particularly keen to hear from people developing on Windows 7 or ensuring Audacity works well on upcoming Ubuntu releases.
+
|style="width:20%;"|[[Give Feedback|Feedback]] <br> &nbsp;
 
+
|style="width:20%;" valign="top"|[[For Developers|Develop]]
 
+
|style="width:20%;"|[[For Translators|Translate]]
==Other Ways To Help==
+
|style="width:20%;"|[[Support other Users]]
 
+
|- style="vertical-align: top;"
* Help us with this wiki and ideas for '''''[[Wiki Development Checklist|onward development]]'''''.
+
|
* Help out on the '''''[http://forum.audacityteam.org/ Forum]''''' by answering our users' questions.
+
* We have [[Preview Versions]] of Audacity, which you can sign up for, to get early access to the new features.
* Add features that you care about to our '''''[[Feature Requests]]''''' page, and/or vote there.
+
* If you want to get more involved, subscribe to our [http://lists.sourceforge.net/lists/listinfo/audacity-quality audacity-quality] mailing list and get involved with improving design and quality.
* If you're a student and interested in '''''[[GSoC_FAQ|GSoC]]''''' in 2010, start planning for it now.
+
<!-- [[Reporting bugs|Report bugs]] --->
 +
<!--* If you're a student and interested in '''''[[GSoC_FAQ|GSoC]]''''' in 2012, start planning for it now.--->
 +
|
 +
* If you're a programmer, check out the '''''[[Developer_Guide|developer guide]]''''' and subscribe to the [http://lists.sourceforge.net/lists/listinfo/audacity-devel audacity-devel] mailing list
 +
* If you are already compiling Audacity, great.  If not tell us where our instructions for doing so suck.
 +
|
 +
* Help by translating the user interface into your language.  Sign up to our [http://lists.sourceforge.net/lists/listinfo/audacity-translation audacity-translation] mailing list.   
 +
* We currently need someone to bring the French translation up from 73% complete to 100%.
 +
|
 +
* Help out on the '''''[https://forum.audacityteam.org/ Forum]''''' by answering our users' questions. We especially need people to answer questions in other than English.  
 +
* Help us improve our [[Support other Users|documentation]].
 +
|}
  
  
 +
<hr style="height=1px;">
  
 
__TOC__
 
__TOC__
  
  
'''In more detail...'''
+
==Those Links Again...==
  
==Quality==
+
* [[Give Feedback|Feedback]]
 +
* [[For Developers|Develop]]
 +
* [[For Translators|Translate]]
 +
* [[Support other Users]]
  
Testers.  Test coordinators.  Test script writers. [[Quality]] system designers and managers.   We need you all.
+
Other ways you can contribute...
  
  
== Documentation Writers (The 2.0 Manual) ==
+
== Graphics ==
  
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.'''   
+
In the longer term future we may need an update to graphics for Audacity itself, and for our main website and wikis.  Someone with graphics skills could help us achieve [[Visual Consistency|visual consistency]] across the application and our sites. We would need a graphic designer with an eye for the whole picture who can help with improving Audacity's graphics in a systematic way.
  
 
+
== Campaigns ==
==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!
 
 
 
 
 
==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 [[:Category:Tutorial|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 [http://audacity.sourceforge.net/community/translation translators] for other languages.
 
 
 
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].
 
 
 
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 [http://forum.audacityteam.org/ 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 [http://audacity.sourceforge.net/help/faq 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 [https://lists.sourceforge.net/lists/listinfo/audacity-users 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 [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==
 
  
 
We need help with campaigns:
 
We need help with campaigns:
 
* 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.
 
* 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/2009-10/ GHOP] (Google Highly Open Participation) Contest
+
* We're considering being part of the next [http://google-opensource.blogspot.com/2010/11/announcing-accepted-organizations-for.html Google Code-in] Contest (an open source development and outreach contest targeted at 13-18 year old students around the world).
 
* 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.
  
 +
* We had a go at campaigns to bring in more developers.  As you probably can see, we could have done better :-)
 +
** Here is a proposed "[[Audacity_Needs_You|Audacity Needs You!]]" page for the main Audacity website.  The intention was to put it in a high traffic area - but it seemed a bit too gung-ho. 
 +
** There was also a landing page, "[[Audacity Sounds Great]]" for free developer recruitment FLOSS adverts provided by [http://stackoverflow.com/ stackoverflow]. 
 +
** We also thought 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.
  
== Ideas? Want to Contact Us?==
+
{{ContactFooter}}
 
 
Didn't find what you were looking for?  Here are various ways to '''''[[Community|contact us]]'''''.
 
 
 
 
 
 
 
[[Category:Participation]]
 

Revision as of 11:56, 10 February 2021

ToDo-2 The section on Graphics needs an update
Audacity is the result of work by volunteers developing, translating, documenting and helping users.
Here are some of the ways you can keep Audacity moving forward as a high quality application with great support and documentation.

Feedback.png Develop.png Translate.png Support.png
Feedback
 
Develop Translate Support other Users
  • We have Preview Versions of Audacity, which you can sign up for, to get early access to the new features.
  • If you want to get more involved, subscribe to our audacity-quality mailing list and get involved with improving design and quality.
  • If you're a programmer, check out the developer guide and subscribe to the audacity-devel mailing list
  • If you are already compiling Audacity, great. If not tell us where our instructions for doing so suck.
  • Help by translating the user interface into your language. Sign up to our audacity-translation mailing list.
  • We currently need someone to bring the French translation up from 73% complete to 100%.
  • Help out on the Forum by answering our users' questions. We especially need people to answer questions in other than English.
  • Help us improve our documentation.




Those Links Again...

Other ways you can contribute...


Graphics

In the longer term future we may need an update to graphics for Audacity itself, and for our main website and wikis. Someone with graphics skills could help us achieve visual consistency across the application and our sites. We would 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 Google Code-in Contest (an open source development and outreach contest targeted at 13-18 year old students around the world).
  • 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.
  • We had a go at campaigns to bring in more developers. As you probably can see, we could have done better :-)
    • Here is a proposed "Audacity Needs You!" page for the main Audacity website. The intention was to put it in a high traffic area - but it seemed a bit too gung-ho.
    • There was also a landing page, "Audacity Sounds Great" for free developer recruitment FLOSS adverts provided by stackoverflow.
    • We also thought 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.


Ideas? Want to Contact Us?

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