caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: David MENTRE <david.mentre@gmail.com>
To: Jonathan Roewen <jonathan.roewen@gmail.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Licensing questions
Date: Thu, 17 Nov 2005 09:00:41 +0100	[thread overview]
Message-ID: <3d13dcfc0511170000l15a7ffc7j@mail.gmail.com> (raw)
In-Reply-To: <ad8cfe7e0511161703h781d02e0p712ebff6a4e6d263@mail.gmail.com>

Hello Jonathan,

2005/11/17, Jonathan Roewen <jonathan.roewen@gmail.com>:
> I'm not a licensing guru, nor know exactly what all the gobbledegook
> means, and have a few questions about how licensing of various parts
> of ocaml system will affect my operating systems project.

Be careful that license issues are a sensitive topic on this list! ;-)

> I use a customised version of the sources in the following directories:
> byterun
> stdlib
> otherlibs/threads
> otherlibs/bigarray
>
> Do I have to make those components open source?

>From http://camlcvs.inria.fr/cgi-bin/cvsweb/ocaml/LICENSE?rev=1.18 ,
it appears that all those directory are part of the "Library".

"The Library is distributed under the terms of the GNU Library General
Public License version 2 (included below)."

So those compose components *are* Open Source. If you distribute then,
you need to keep them Open Source.

> Also, can DST be
> closed source if I so wish (currently haven't decided on a license)?

Due to the use of LGPL license with a special clause, you can use
those components in a closed source (aka proprietary) software. So you
can use about any license for the remaining part of your software.

That's said and as a personal note, I would *strongly* advise you to
use a free software liense and a well known one, like BSD, LGPL or
GPL. Personally, I would use GNU GPL, because is forces contributers
of your software to give back to you, while still allowing anybody to
use it at will. I'm quite interested by your OS in Caml but the 2nd
reason not to look at it is that it is currently not Free Software.
The first reason being I don't have enough time. As it becoming off
topic for this list, you can ask me in private if you want more
information on those license issues and about Free/Open Source (and
I'm not a lawyer ;-).

Yours,
david


      reply	other threads:[~2005-11-17  8:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-17  1:03 Jonathan Roewen
2005-11-17  8:00 ` David MENTRE [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3d13dcfc0511170000l15a7ffc7j@mail.gmail.com \
    --to=david.mentre@gmail.com \
    --cc=caml-list@yquem.inria.fr \
    --cc=jonathan.roewen@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).