Hey guys, excellent!
Indeed, I quietly started something and put it in google code. It would be great to have some help with it, though originally I planned on getting some kind of basic skeleton finished before asking other ppls to join in. Of course, if you want to help with that as well, you are very much welcome.
About the licensing, I would specifically want this to be a part of scipy in the future. The code should thus be released under a BSD license (I put it like that in Google Code). I'm not quite sure how this licensing stuff works. The algorithms are all public domain afaik, Octave made some implementation of them in C++. The class structure of this toolbox will be totally different, it's even written in a whole other language. Is it forbidden for us to look at how they implemented it without going to GPL? Not too big of a problem because it can be done without, but it's always nice to have some kind of reference.
So far it's all original.. :) Tonight I'll restructure some, and put up the last version. Ofcourse, I barely started, so a LOT still has to be done.
Greetz,
Jasper
On Sun, Mar 2, 2008 at 2:05 PM, Gael Varoquaux <
gael.varoquaux@normalesup.org> wrote:
I haven't been following this very closely, but can you remind me if we
are talking about a scikit which could be released under the GPL, or
something that would be released under a BSD license. The reason I ask
this question is that Octave is GPL, and to write BSD-license coded
inspired by their code I think you would need either to do some white
room engineering, or ask for special permission to the authors. Don't
trust my opinion too much, I am license expert, but I just wanted to
point out this eventual snag.
Cheers,
Gaël