caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jeremy Bem <jeremy1@gmail.com>
To: caml-list List <caml-list@yquem.inria.fr>
Subject: Caml Light license in 2010
Date: Tue, 13 Jul 2010 09:18:21 -0400	[thread overview]
Message-ID: <AANLkTikPjEzoVdo4lf8TD22_0tntIfuVVmNy_2Vd-DvT@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1223 bytes --]

Hello,

I'd like to use the Caml Light codebase as a jumping-off point for a new
(language-level) functional programming project.  Also, I like to use public
hosting (Google Code) for my projects.  The problem however is the QPL
license which means I need to maintain patchfiles rather than actual
sources.  This is awkward for version control and such.

Suggestions?  I see that Moscow ML is a fork of Caml Light, however they
forked the 0.61 version (1993) which didn't yet have the QPL-style clause
prohibiting the direct distribution of modified sources.

My ideas:
- I could also fork the 0.61 version (I actually tried to compile it,
encountered some minor issues but I'm sure they could be worked around)
- I could perhaps join the Caml Consortium, but 3000 Euro seems like a lot
for this -- especially at this stage.
- Is there still an active desire to restrict use of Caml Light 0.7x in this
way?  And would the 0.61 workaround be going against the spirit of things,
if not the letter?
- Is there a better jumping-off point for my project?  My own feeling is
that this code has probably aged rather well (although i have no wish to
spend time re-fixing the pre-1998 bugs).

Thanks in advance for any help,
Jeremy

[-- Attachment #2: Type: text/html, Size: 1405 bytes --]

             reply	other threads:[~2010-07-13 13:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-13 13:18 Jeremy Bem [this message]
2010-07-14  0:23 ` Michael Ekstrand
2010-07-14 13:08   ` [Caml-list] " Stéphane Glondu

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=AANLkTikPjEzoVdo4lf8TD22_0tntIfuVVmNy_2Vd-DvT@mail.gmail.com \
    --to=jeremy1@gmail.com \
    --cc=caml-list@yquem.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).