From: Francois Berenger <berenger@riken.jp>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Licensing Camel and related Projects Under a Permissive License
Date: Wed, 04 Dec 2013 15:14:26 +0900 [thread overview]
Message-ID: <529EC842.7080702@riken.jp> (raw)
In-Reply-To: <CAAfFNYHGTNZy8NYjatmQoXWd9pjTscQRcrH0DnnR-xBUi-TmEw@mail.gmail.com>
On 12/04/2013 02:30 PM, Suminda Dharmasena wrote:
> Hi,
>
> Many of the major tools and implementation (tools within the
> implementation also) have different licensing like QPL, GPL, LGPL.
>
> I am wondering if you community can discuss about perhaps using more
> permissive licensing and come to a consensus on licensing guideline.
> (Ultimately is it up to the IP holder how they license.) But some
> discussion of re licensing would be beneficial to bring the many
> projects under a permissive license.
Maybe related to what you are asking: members of the Caml Consortium
benefit from a special license. Cf.
http://caml.inria.fr/consortium/license.en.html
and
http://caml.inria.fr/consortium/
--
Best regards,
Francois Berenger.
prev parent reply other threads:[~2013-12-04 6:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-04 5:30 Suminda Dharmasena
2013-12-04 6:14 ` Francois Berenger [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=529EC842.7080702@riken.jp \
--to=berenger@riken.jp \
--cc=caml-list@inria.fr \
/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).