View source for HowTo:POV-Ray Feature Requests

We all want to see POV-Ray improved, and from time to time it may occur to us that there's a feature that we would like to see, or something we'd like to see improved. The proper place for "feature wishlists" is the bugtracking and feature-request system on [http://bugs.povray.org/ Bugtracker], as that's ''the'' primary place where the developers will look for them.

To see a list of current feature requests, whether open or closed, visit [http://bugs.povray.org/index.php?string=&project=2&search_name=&type%5B%5D=2&sev%5B%5D=&pri%5B%5D=&due%5B%5D=&reported%5B%5D=&cat%5B%5D=&status%5B%5D=&percent%5B%5D=&opened=&dev=&closed=&duedatefrom=&duedateto=&changedfrom=&changedto=&openedfrom=&openedto=&closedfrom=&closedto=&do=index this link]. The bugtracker also provides a means for users to vote on bugs or features they deem particularly important to address. 

When ''making'' feature requests, a word of advice:

Please ''do'' read [[HowTo:Make A Bug Report]] and [http://www.chiark.greenend.org.uk/~sgtatham/bugs.html How to Report Bugs Effectively] before submitting any entries to the bugtracker, and ''do'' heed the advice presented there. There is a reason the first is referenced at the top of each and every bugtracker page, and the second in turn is referenced in by the first: By following those rules - or at least keeping them in mind as you file bug reports - you make life a lot easier for the people you expect to fix the issues.

Some other points raised in [http://news.povray.org/povray.advanced-users/thread/%3C4c1d52c5%241%40news.povray.org%3E/] and [http://news.povray.org/povray.general/thread/%3C4c09591e%241%40news.povray.org%3E/]:

* If discussion of a feature request has resulted in a summary or conclusion that differs from the original request, a new feature request should not be made. Instead, the existing one should be changed. This implies contributing ideas to the feature request discussion, and then coming up with a single coherent idea, not leaving it at two half-finished ideas.
* Closely-related feature requests should be grouped together; e.g. requests for Windows UI enhancements with respect to the editor could such as "Delete", "Reload" and "Rename" commands could reasonably be put into a single request (all at once or via editing a bug later).
* There is a feature to allow other users and/or developers to comment on bugs & feature requests on bugtracker, but this is primarily intended for providing additional information, or feedback on the current status. For proper discussions, it lacks the necessary publicity. (When was the last time anyone just browsed the bugtracker just to see if there was some interesting discussion going on in some of the entries?) The POV-Ray community is strongest in the newsgroups. That said, the problem with ''discussions'' about feature requests is that they tend to have ''no'' clear-cut result whatsoever, as they tend do be free brainstorming sessions - unless there's someone with the necessary will and authority (e.g. because he has started the discussion in the first place) "driving" the discussion to a proper conclusion (ideally by summarizing the discussion and result in a proper place). In this situation, bugtracker excels.
* A sensible rule for opening a new feature request would then be that it must be discussed in the newsgroups first, to weed out crackpot ideas and to refine ideas by feedback from what users actually need. After discussion, the request should only be entered if a member of the POV-Ray team deems the request reasonable (note that a request should not be deemed unreasonable at this point just because it would be too much effort to implement right now).