Hi :-) søn, 19 09 2010 kl. 20:09 +0200, skrev Juan Pablo Carbajal: > Regarding licensing. If i use code from other people, what license > should they use so I can add it to octave? For example, code under > BSD(LGPL, QGPL) is usable in packages for octave or not? (I am a > complete rookie regarding licenses). (I was trying to port some algos > from CGAL...for example)
Depends... If you want your code to be part of Octave, then it needs to be GPL v3 or later. If you want your code to be part of Octave-Forge, i.e. distributed as a package, then the license depends on implementation details. m-files can be distributed via Octave-Forge under any Free Software license (I think), but oct-files needs to be GPL v3 compatible. Usually, I would recommend GPL v3 or later for all your code, but in the end, this is your choice. > Also, For somebody learning from scratch to do packages, which one > would you suggest as a good example to follow? (So, what is the best > structured package out there?) I guess that depends on your needs. I guess you will want to include oct-files in your package? Then, I would look at the 'image' package and see how things are done their (I just picked this package because I know that one fairly well; other packages follow similar structures, so they could also be studied). Hope that helps, Søren ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Octave-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/octave-dev
