Hoping itll get added in the next release
Chances: 0-2%
If you have an idea and dont tell anybody, what're the chances of it crawling out your head and into a developers head?
Ask a developer via MSN/IRC/Lobby
Chances: 0-10%
Developers are busy people in short supply, who're likely to be fixing bugs. If you tell them something this way they're likely to just forget it as other people come along and grab their attention.
Start a thread asking for it
Chances: 5-30%
Depending on how popular and how simple the request is, a developer could pick it up, however the more time consuming and complex the request becomes the less likely its done.
File a feature Request in Mantis
Chances: 2-40%
Feature requests arent usually filed into the bugtracker, and when they are they serve as a constant reminder to developers. However they arent the best place for discussion of features and they tend to get sidelined by bug reports.
Start a thread and plan how it would be implemented
Chances: 25-70%
Aswell as making developers aware of the request your suggesting methods of actually doing it. This way its easier for a developer to see what your proposing, and you involve the community. Another community member or an itnerested developer may implement your idea. The discussion also shows that your serious about the request making it a more serious contender.
Create a design document and discuss the feature in depth
Chances: 2-100%
Depending on how in depth the design becomes this can be a good solid method, however it is time consuming and gives the impression that you yourself are intending to implement the feature. This method is best if you intend to lead a community effort to create an external program or tool. Developers should also use this method when planning major overhauls/restructuring of code or designing external APIs.
Start work on a feature with the intention that someone else helps finish it
Chances: 40-60%
This can get the ball rolling but it depends how complex the feature is and how far you push it. If there arent enough itnerested people you may end up doing ti all by yourself and loosing momentum.
Create an SVN patch implementing the feature
Chances: 80-100%
Depending on how well your code is written there is a high chance that feature will be put in the next release. Because you've written a patch the developers dont need to create the feature, its a simple review and commit process. If you create enough patches of a high quality you will be granted svn access and will be able to directly commit changes upping your chances to 98-100%.
The best ways to get that Feature Request
Moderator: Moderators
Additional Methods
Recruiting Uninvolved Coders/Visionaries To Do It
Chances: 0-20%
People are, in general, lazy and uninterested in experimentation. This method rests on your social skills, and if you're playing Spring, you may have a problem with social skills. However, sometimes, you come across a gem in the wide world of undergraduates and hobbyists.
Start A Thread, Plan Implementation, Put Up Design Document, Spam Relational Data In Associated Threads
Chances: 5-85%
Immerse them in the idea.
Chances: 0-20%
People are, in general, lazy and uninterested in experimentation. This method rests on your social skills, and if you're playing Spring, you may have a problem with social skills. However, sometimes, you come across a gem in the wide world of undergraduates and hobbyists.
Start A Thread, Plan Implementation, Put Up Design Document, Spam Relational Data In Associated Threads
Chances: 5-85%
Immerse them in the idea.