Contributions
Locked
 
|
Hi all,
as you've noticed by my delay in answering posts on the mailing lists, I'm not being able to allocate much time for QuantLib. Which is more the pity, since we've received quite a few contributions I'd like to look at and include in the library. Moreover, I'd like to put out a release in the next couple of months. Putting this all together---what would you say about creating a ql/contrib folder in the library where I would add contributions just as they are? The main points would be: (+) contributions would go in without much effort; we'd just have to check that they compile against the current code; (+) they would be out earlier, thus receiving more feedback; (-) their interfaces wouldn't be considered stable; based on feedback, they could be reworked so that they fit preferred usage and the design of the rest of the library. In time, we'd look at them more carefully and move them to the regular folder hierarchy. And now that I think of it, we don't even need a ql/contrib folder---we can use the existing ql/experimental instead. What do you think? Luigi -- There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies. -- C. A. R. Hoare ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ QuantLib-dev mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/quantlib-dev |
|
|
Hi Luigi, Whilst I'd love to see what many other people are working on, I'm not sure how this would work... a lot of contributions change the existing codebase - so you'd either have duplicate code in the ql/contrib folder or it would be purely for new classes. If there isn't time for you to test the code - why not have a different branch of the library which includes the contributions. Effectively two releases: a full release and a beta version of the next. Alternatively, you could accept all contributions which compile and don't break the test-suite...? Admittedly, this might mean that some of the interfaces change between releases - which can be a pain, unless the important interfaces are in the test-suite. Cheers, Simon -----Original Message----- From: Luigi Ballabio [mailto:[hidden email]] Sent: 07 May 2008 16:54 To: QuantLib developers; QuantLib users Cc: [hidden email]; [hidden email]; [hidden email]; [hidden email]; [hidden email]; [hidden email]; Simon Ibbotson - Straumur Subject: Contributions Hi all, as you've noticed by my delay in answering posts on the mailing lists, I'm not being able to allocate much time for QuantLib. Which is more the pity, since we've received quite a few contributions I'd like to look at and include in the library. Moreover, I'd like to put out a release in the next couple of months. Putting this all together---what would you say about creating a ql/contrib folder in the library where I would add contributions just as they are? The main points would be: (+) contributions would go in without much effort; we'd just have to check that they compile against the current code; (+) they would be out earlier, thus receiving more feedback; (-) their interfaces wouldn't be considered stable; based on feedback, they could be reworked so that they fit preferred usage and the design of the rest of the library. In time, we'd look at them more carefully and move them to the regular folder hierarchy. And now that I think of it, we don't even need a ql/contrib folder---we can use the existing ql/experimental instead. What do you think? Luigi -- There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies. -- C. A. R. Hoare ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ QuantLib-dev mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/quantlib-dev |
|
|
On Thu, 2008-05-08 at 15:08 +0000, Simon Ibbotson - Straumur wrote:
> Whilst I'd love to see what many other people are working on, I'm not > sure how this would work... a lot of contributions change the existing > codebase - so you'd either have duplicate code in the ql/contrib folder > or it would be purely for new classes. True, it wouldn't work if contributions change the existing classes. Those (or part of them) would have to be integrated with the main library. However, most contributions I received were new classes. I was thinking of those as going into the experimental folder. Luigi -- Newton's Law of Gravitation: What goes up must come down. But don't expect it to come down where you can find it. Murphy's Law applies to Newton's. ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ QuantLib-dev mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/quantlib-dev |
|
|
I think we may be overlooking a pretty obvious solution here: http://puppetmastertrading.com/images/ObviousSolutionToQuantlibDevBottleneck.jpg Luigi Ballabio <[hidden email]> wrote: On Thu, 2008-05-08 at 15:08 +0000, Simon Ibbotson - Straumur wrote: ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ QuantLib-dev mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/quantlib-dev |
|
|
On Thu, 2008-05-08 at 12:27 -0700, Tito Ingargiola wrote:
> > I think we may be overlooking a pretty obvious solution here: > > http://puppetmastertrading.com/images/ObviousSolutionToQuantlibDevBottleneck.jpg No, this turned out bad in pretty much every movie I saw... Luigi -- Grabel's Law: 2 is not equal to 3 -- not even for large values of 2. ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ QuantLib-dev mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/quantlib-dev |
|
|
In reply to this post by Luigi Ballabio
What about the dog...? :-)
> -----Original Message----- > From: [hidden email] > [mailto:[hidden email]] On Behalf > Of Luigi Ballabio > Sent: venerdì 9 maggio 2008 09.33 > To: Tito Ingargiola > Cc: Simon Ibbotson - Straumur; [hidden email] > Subject: Re: [Quantlib-dev] Contributions > > > On Thu, 2008-05-08 at 12:27 -0700, Tito Ingargiola wrote: > > > > I think we may be overlooking a pretty obvious solution here: > > > > > http://puppetmastertrading.com/images/ObviousSolutionToQuantli No, this turned out bad in pretty much every movie I saw... Luigi -- Grabel's Law: 2 is not equal to 3 -- not even for large values of 2. ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ QuantLib-dev mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/quantlib-dev ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ QuantLib-dev mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/quantlib-dev |
«
Return to quantlib-dev
|
1 view|%1 views
| Free forum by Nabble | Edit this page |