Developer introduction

Developers willing to contribute to the QuantLib project may contact either project administrators (Nando <nando at users.sourceforge.net> or Luigi <luigi.ballabio at gmail.com>) and describe their experience and interests. You might want to specify an area of the library you are particularly interested to, or which would be most useful to you. Asking the administrators to choose a task for you is ok, but it might take time to get an answer and it increases the odds that the chosen task will bore you or otherwise discourage you from completing it.

Should you want to review a list of needed tasks, the project overview (http://quantlib.org/reference/overview.html) contains a list of generic to-do items; a more low-level list is available at http://quantlib.org/reference/todo.html. We also suggest that you take a look at our QuantLib Enhancement Proposals http://quantlib.org/quep.shtml): if you plan some large contribution you may want to write one before you start coding. It will be a very useful effort since it will be re-cycled as documentation when you actually implement your ideas.

Feel free to post to quantlib-dev@lists.sourceforge.net your development ideas, contribution and sample code (you will need to subscribe to the list first; http://quantlib.org/mailinglists.shtml.) Submitting a patch would be the easiest way to get your contribution into the QuantLib code tree; see the FAQ (http://quantlib.org/reference/faq.html) for details.

To keep up with the QuantLib development - so that your contribution will apply to the latest source code tree - you will need to familiarize with CVS: see <a href=" http://quantlib.org/cvs.shtml"><http://quantlib.org/cvs.shtml> for an introduction.

After having established yourself as a trusted contributor, you might be granted write access to the CVS tree. In that case, you will need a SourceForge^? account; see <a href=" http://sourceforge.net"><http://sourceforge.net>. You might also need a few developer tools besides CVS: please read the Developer FAQ (<a href=" http://quantlib.org/developerFAQ.shtml">http://quantlib.org/developerFAQ.shtml.)

We might need to ask for a disclaimer from your employer stating that your contribution can be released under the QuantLib license; such disclaimer shouldn't be necessary if you own the copyright of the code.

Finally, note that the above is a list of suggestion, not requirements. The QuantLib team can help you on any issue; don't let details stop you.