Editing Feature Requests

From Audacity Wiki
Revision as of 21:00, 24 February 2008 by James (talk | contribs) (Moved related pages down in the instructions.)
Jump to: navigation, search

These are instructions for editing the Feature Requests page. Sorry they are so long! We get a lot of feature requests and are trying hard to keep them organised.

If instead you have suggestions about the Wiki, please click here. To comment about the main Audacity website  , please click here.


Instructions for adding new Audacity Feature Requests:


Before adding a new Feature Request to this page, please read all these points!

  1. Check the page to see if your idea has already been suggested. Try the "Find" facility in your browser to make this easier.
  2. Check our Completed Features page to see if your idea has already been implemented.
  3. If the feature uses a proprietary format, check if it is one of the Features We Can't Implement because of restrictions placed on us by other copyright holders. Examples include 'Rewire' support, ASIO and WMA.
  4. If you have many related changes for a particular use of Audacity, such as wildlife recording or Theatre, go to the Use Cases page instead.
  5. Please try to keep requests as short as possible so that it's easy to quickly scan the whole list. If a long description of the feature is unavoidable, please add it here for now.
  6. Please look at the existing page sections for an appropriate category to put your new request in. Then click either the "Edit" link at the top of the page or to the right of the section,and add your request prefixed by a * , so that it goes on a new indented line.
  7. If you're sure your feature request hasn't already been asked for, is not one we're prohibited from implementing, and does not fit a category on this page, please click here to add a new request to the "Other" section of the Unclassified Feature Requests page.

Point 3 about Use Cases makes a huge difference for us. It helps us to see why a particular feature is useful and makes it easier to progress a number of feature requests at the same time. We may be able to interest a new developer or Google Summer of Code student in progressing a Use Case. The developers would welcome help from the community in organising groups of related feature requests into a well thought-out GSoC Project Idea. It could help us to get those features into Audacity as part of Google Summer of Code.



Instructions for voting for an existing suggestion:
  1. Please use either the "Edit" link at the top of the page or to the right of the section, and increase the number of votes next to the feature by one.
  2. You may also re-sort the list, for example to group together related requests within a section.
  3. Please vote for no more than your 10 most desired features, so that the list reflects items that are really important to users. However, once a feature has been completed, you can vote for another one next time you visit!

While we always consider the best and most often mentioned requests for inclusion in Audacity, we cannot undertake to implement any particular request made here.


Related Pages:
We have several other pages concerned with Feature Planning. If you browse some of these, you'll get more idea of how feature requests progress to actual implementation.


Interested in sponsoring a feature? Please contact us for information if you want to contribute money in order to have your most desired feature implemented sooner.