Difference between revisions of "For Developers"

From Audacity Wiki
Jump to: navigation, search
(Somewhat more chatty instructions.)
Line 6: Line 6:
  
 
{|
 
{|
−
Audacity aims to be a '''simple to use''' but '''powerful audio editor'''.
+
 
−
* We have ''[[Design Topics|design guidelines]]'' to make the user interface consistent and more discoverable.
+
'''Code we Like!'''<br clear=all> <br clear=all>
−
* We have ''[[CodingStandards|coding standards]]'' to improve consistency in how we code.
+
 
−
* We have a vibrant ''[[Community|community]]'' beyond the developers who support users, get feedback, test and document Audacity.
+
 
 +
Audacity aims to be a '''simple to use''' but '''powerful audio editor'''.  We're open to exciting new features, bugfixes (yes please!) and new ideas, and at the same time, we need to do things a certain way.
 +
 
 +
* We want to avoid making Audacity over complex.  The majority of our users are newish to audio editing.  The simple things ought to be easy to do for them.  The more advanced things can be there, but should not 'get in the way'.  Many of our users do not read the manual. Follow our ''[[Design Topics|design guidelines]]'' to make the user interface consistent and more discoverable.
 +
* We don't know that you will stay around after you have contributed code, so new code should follow our ''[[CodingStandards|coding standards]]'' so that it is more maintainable by us.
 +
* To get the best from contributing to open source, you should become aware of the ''[[Community|community]]'' beyond the developers who support users, get feedback, test and document Audacity.  The experience they have can often help what you write be better, and save you time too.
 
|}
 
|}
  
Line 18: Line 23:
 
| &nbsp; &nbsp;
 
| &nbsp; &nbsp;
 
| style="vertical-align:top;" |
 
| style="vertical-align:top;" |
−
* 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]''
+
'''Guides and Connecting'''
−
* If you are already compiling Audacity, great.  If not tell us where our instructions for doing so suck.
+
 
−
<br clear="all">
+
* Check out the ''[[Developer_Guide|developer guide]]'' and subscribe to the ''[http://lists.sourceforge.net/lists/listinfo/audacity-devel audacity-devel mailing list]''
  
−
'''We ''always'' need more developers!'''  
+
Why subscribe?  We have found time and again that good programmers are overly reluctant to ask for actual help.  It is usually our fault, not yours, if you can't compile.  Our instructions and guides are not always good and up to date.  Especially if you have difficulty compiling Audacity, reach out to one of us on the mailing list, and talk us through how far you get. Together we can work to fix it, and to fix the compiling instructions, so that other people have an easier time in future.
  
−
* Rather than just post a pull request to our GitHub repo, join our ''[http://lists.sourceforge.net/lists/listinfo/audacity-devel developers' mailing list]'' and introduce yourself!  You'll have a far better chance of your proposed changes being adapted and accepted.  You don't have to have a pull request already.  We're very happy to have lurkers on the list.  If you are keen to interact, you are welcome to:
 
−
** tell us about any ''[[:Category:Feature Planning|new or improved features]]'' you are working on.
 
−
** tell us if you've hit a ''[[Bug Lists|bug]]'' and are working on it.
 
−
** if you'd like to help with code reviews of GitHub pull requests, tell us.
 
 
|}
 
|}
 
<div id="links"></div>
 
<div id="links"></div>
Line 38: Line 39:
 
*[[Developer_Guide#Platform_Specific_Guides|Building Audacity from Source]]
 
*[[Developer_Guide#Platform_Specific_Guides|Building Audacity from Source]]
 
-->
 
-->
 +
*[[Developer Guide|Guide for New Audacity Developers]]
 +
**[[Theming HowTo]]
 +
**[[Nyquist|Nyquist plug-ins HowTo]]
 +
**[https://alphamanual.audacityteam.org/man/scripting Scripting]
 
*[[The Feature Requests Pipeline]]
 
*[[The Feature Requests Pipeline]]
 
**[[Proposals]]
 
**[[Proposals]]
 
**[[Feature Requests]]
 
**[[Feature Requests]]
 
*[[ArchitecturalDesign|Audacity Architecture]]
 
*[[ArchitecturalDesign|Audacity Architecture]]
−
*[[Developer Guide|Guide for New Audacity Developers]]
 
−
**[[Theming HowTo]]
 
−
**[[Nyquist|Nyquist plug-ins HowTo]]
 
−
**[https://alphamanual.audacityteam.org/man/scripting Scripting]
 
 
*[[Making Audacity Translatable]]
 
*[[Making Audacity Translatable]]
 
*[[Making Audacity Doxygenable]]
 
*[[Making Audacity Doxygenable]]
−
*[https://doxy.audacityteam.org/annotated.html Doxygenated class list]
+
**[https://doxy.audacityteam.org/annotated.html Doxygenated class list]
 
===Development Activity===
 
===Development Activity===
 
*[[Next Release]] that we are working on
 
*[[Next Release]] that we are working on
Line 58: Line 59:
 
<div style="width:50%;float:left;">
 
<div style="width:50%;float:left;">
 
===Building===
 
===Building===
 +
*[https://github.com/audacity/audacity Our code on GitHub]
 
*[[Building On Windows]]
 
*[[Building On Windows]]
 
*[[Building On Linux]]
 
*[[Building On Linux]]
 
*[[Building On Mac]]
 
*[[Building On Mac]]
−
*[[Building On Cygwin]]
+
*[[Building On Cygwin]] (Deprecated/Not Maintained)
 
*[[Building The Manual]]
 
*[[Building The Manual]]
−
*[https://github.com/audacity/audacity Our code on GitHub]
+
 
 
===Quality Assurance===
 
===Quality Assurance===
 
*[[CodingStandards|Coding Standards]]
 
*[[CodingStandards|Coding Standards]]

Revision as of 13:02, 8 November 2019


Code we Like!

Audacity aims to be a simple to use but powerful audio editor. We're open to exciting new features, bugfixes (yes please!) and new ideas, and at the same time, we need to do things a certain way.
  • We want to avoid making Audacity over complex. The majority of our users are newish to audio editing. The simple things ought to be easy to do for them. The more advanced things can be there, but should not 'get in the way'. Many of our users do not read the manual. Follow our design guidelines to make the user interface consistent and more discoverable.
  • We don't know that you will stay around after you have contributed code, so new code should follow our coding standards so that it is more maintainable by us.
  • To get the best from contributing to open source, you should become aware of the community beyond the developers who support users, get feedback, test and document Audacity. The experience they have can often help what you write be better, and save you time too.

Develop.png

This is how we get from ideas to new releases of Audacity
Feature Requests   -->   Proposals   -->   Projects   -->   Releases
   

Guides and Connecting

Why subscribe? We have found time and again that good programmers are overly reluctant to ask for actual help. It is usually our fault, not yours, if you can't compile. Our instructions and guides are not always good and up to date. Especially if you have difficulty compiling Audacity, reach out to one of us on the mailing list, and talk us through how far you get. Together we can work to fix it, and to fix the compiling instructions, so that other people have an easier time in future.

Topics for Developers



Ideas? Want to Contact Us?

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

Retrieved from "https://wiki.audacityteam.org/w/index.php?title=For_Developers&oldid=39225"