Posted by
Ferdinando M. Ametrano-2 on
Jan 08, 2002; 4:03am
URL: http://quantlib.414.s1.nabble.com/new-QuantLib-license-tp9975.html
Hi all
don't hold your breath: no real change here.
I submitted QuantLib License 1.0 (
http://quantlib.org/license.html) for OSD
branding and FSF certified GPL compatibility.
I already obtained the latter from rms.
I'm going to clear any potential issue with license and copyright before I
leave RiskMap for a new job that will start next February 1st.
RiskMap is committed to continue support QuantLib: hey, Luigi, Marco, and
Enrico will stay at RiskMap!
As far as I'm concerned my new job should allow me to dedicate a
significant part of my time to QuantLib.
The QuantLib copyright holder is known as the QuantLib Group. A more
specific per-file copyright will be specified in each file. This means that
the majority of files will be 'copyright RiskMap srl', with all Sad's files
being 'copyright Sadruddin Rejeb' and Nicolas' files 'copyright Nicolas Di
Cesare'.
I will avoid to request copyright assignments from developers. Given the
QuantLib license to actually own the copyright doesn't give any special
privileges, that is as long as the developer contributes the code under the
QuantLib License.
Nicolas: if you are employed to do programming, or have made an agreement
with your
employer that says it owns programs you write, we need a signed piece of
paper from your employer disclaiming rights to the program. It should be
signed by a vice president or general manager of the company. If you
can't get at them, it is almost as good to find someone who signs licenses
for software that is purchased. Here is a sample wording:
Digital Stimulation Corporation hereby disclaims all copyright interest
in the program "blackscholes.cppp" (a program for quantitative finance)
written by Hugh Heffner.
<signature of Ty Coon>, 1 April 1987
Ty Coon, President of Vice, Digital Stimulation Corp.
The description of what the program does is just to make it clearer
what the disclaimer covers.
Sad: the above disclaimer should not apply to your RiskMap involvement
any feedback is welcome
ciao -- Nando