Editing Feature Requests

From Audacity Wiki
Revision as of 19:05, 8 October 2016 by Galeandrews (talk | contribs) (Clarify you must be logged in to edit pages)
Jump to: navigation, search
These are instructions for editing the Audacity Feature Requests page. Sorry they are long! We get many requests and are trying to keep them organised.

You must be logged in to edit Wiki pages. You can vote without a Wiki account by e-mailing our feedback address.

New Requests

Before adding a new Feature Request, 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. If your idea is already there, see the instructions on voting for an existing suggestion.
  2. Check our Completed Features page to see if your idea has already been implemented.
  3. If the feature uses a proprietary technology, 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 the "Edit" link at the top of the page or to the right of the section, scroll down to the edit window 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 an existing category, please click here to add a new request to the "Other" section of the Unclassified Feature Requests page.

Value of Use Cases:

Point 4 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/commenting on an existing suggestion:
  1. Please use either the Edit link at the top of the page or the one to the right of each section, scroll down to the edit window, and increase the number of votes to right of the request by one.
  2. To add a comment to the request (with or without voting for it), hit ENTER at the end of the request and add your comment prefaced by two *'s (**) . This will indent the comment underneath the request.
  3. You may re-sort the list, for example to group together related requests within a section, or to move individual requests with ten votes or more to the "Highest-rated" section.
  4. Please vote for no more than your ten 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!

We can't do everything:

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

< Back to Feature Requests