Difference between revisions of "For Developers"

From Audacity Wiki
Jump to: navigation, search
(Unitary Project - issue tracking)
(redundant cruft removed)
 
(4 intermediate revisions by 2 users not shown)
Line 53: Line 53:
 
**[https://alphamanual.audacityteam.org/man/scripting Scripting]
 
**[https://alphamanual.audacityteam.org/man/scripting Scripting]
 
*[[Standards and Conventions]]
 
*[[Standards and Conventions]]
 +
**[[CodingStandards|Coding Standards]]
 +
**[[Code Review Triage|Code Review]]
 
*[[The Feature Requests Pipeline]]
 
*[[The Feature Requests Pipeline]]
 
**[[Proposals]]
 
**[[Proposals]]
Line 69: Line 71:
 
** [[Macros discussion page]]
 
** [[Macros discussion page]]
 
===Quality Assurance===
 
===Quality Assurance===
 +
*[[QA Procedures overview]]
 +
*[[Bug testing workbench]]
 
*[[Unitary Project - issue tracking]]
 
*[[Unitary Project - issue tracking]]
−
*[[CodingStandards|Coding Standards]]
+
*[[ToDo:_Unstick_%27Stuck_In_a_Mode%27|Bear Traps]]
−
*[[Code Review Triage|Code Review]]
 
 
*[[Using Bugzilla]]
 
*[[Using Bugzilla]]
 
*[[Bug Lists]]
 
*[[Bug Lists]]
Line 80: Line 83:
 
*[https://alphamanual.audacityteam.org/man/Consistency_in_wording_and_punctuation_in_Audacity '''Wording and punctuation guidelines''']
 
*[https://alphamanual.audacityteam.org/man/Consistency_in_wording_and_punctuation_in_Audacity '''Wording and punctuation guidelines''']
 
**[[Guidelines on capitalization in Audacity dialogs and messages|Capitalization Guidelines]]
 
**[[Guidelines on capitalization in Audacity dialogs and messages|Capitalization Guidelines]]
−
*[[Website ToDo]]
 
−
{{ednote|1=[[Builds for alpha testing]] not listed now}}
 
 
</div><br clear="both"/>
 
</div><br clear="both"/>
 
<div style="clear:both"></div>
 
<div style="clear:both"></div>

Latest revision as of 14:34, 17 September 2021


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=44123"