How Plans Progress
- Most of the time the most important activity is being tracked on Next Release. That page has information about progress and schedule on the current release. You can see commits that are progressing the release on our GitHub master branch. Many of the commits will have titles, complete with bug numbers, from Bugzilla that the commit is intended to address.
- Feature Requests give us some numerical indication of features that users would like. However, all developers are volunteers, and what they decide to do is only to an extent influenced by the requests.
- We thrash out details of proposed new features on proposal pages. Often there are experiments in github branches, and screenshots from those are shared on these pages.
- We have many pages about how we decide what to do in this wiki.
To Be Confirmed.
A curated branch (curated by Paul) that contains a mix of Work In Progress for feedback and early adopters. This is a 'feeder branch' into Audacity.
James Crook is running an active project in 2017 to bring more automation into work on Audacity.
- The Automation project page page tracks this work.
- Separately Buanzo is working on Automated Windows builds for Audacity.
Also by James Crook, an ongoing feeder-project into Audacity the brings in new GUI innovations. DarkAudacity was started in June 2016, delivered significant changes to Audacity 2.2.0 and is continuing on in 2017.
- The progress on integration page tracks transfer of work on DarkAudacity into Audacity.
- The changes to the theming feature tracks progress on meeting team requests for theme changes.
Google Summer of Code
Audacity has participated twice in Google Summer of Code. Once in 2008 and once in 2009.
Various odd bits about development projects that don't fit anywhere else.