From: Sam S. <sd...@gn...> - 2004-08-19 13:21:08
|
> * Goffioul Michael <tbssvbhy@vzrp.or> [2004-08-19 09:50:24 +0200]: > > Note that the code I developed is not about a MATLAB module for CLISP, > but about a MEX file making a bridge to be able to call LISP statements > from MATLAB. I'm not against the idea of putting the code in the CVS > repository of CLISP, but this raises some issues: > 1) is this the right place? as I said, it's not a module for CLISP OK, we could put it into the contrib directory instead. > 2) does the MATLAB license permit this? I mean that the code was > written using the MATLAB MEX API under a commercial-licensed > MATLAB. Can it be release under GPL? since you are not distributing any of their code (or libraries), you are obviously not infringing on their copyright. > 3) I wrote the MEX file in the context of my official job, hence I'm > not the "real" owner of the code, I've to check if I may release the > code (note that this code is written for internal purpose and not > intended to be released, so it's not incompatible with GPL); however, > I guess there shouldn't be a problem here as there's no real IP stuff > in that code, it's just a bridge, anybody can write it. RMS requires copyright releases from the employer. we don't. you might want to talk to your boss. -- Sam Steingold (http://www.podval.org/~sds) running w2k <http://www.camera.org> <http://www.iris.org.il> <http://www.memri.org/> <http://www.mideasttruth.com/> <http://www.honestreporting.com> Oh Lord, give me the source code of the Universe and a good debugger! |