Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: Edgar Friendly <thelema314@gmail.com>
Cc: caml list <caml-list@inria.fr>
Subject: Re: [Caml-list] License question - QPL vs. SCM
Date: Wed, 09 Apr 2008 17:21:00 +0200	[thread overview]
Message-ID: <47FCDEDC.7000602@inria.fr> (raw)
In-Reply-To: <47F9A346.4060900@gmail.com>

> My question for INRIA's lawyers (or anyone else in some official
> capacity to answer) involves using a Source Code Manager (SCM) whose
> distribution method has structure: source + patch1 + patch2 + ....  The
> SCM would do the lifting of combining the two into the final tree, just
> as a script could easily wget an original source file and a list of
> patches and combine them into the final tree.
>
> Would using such a SCM to organize and distribute compiler source
> violate OCaml's license?
>
> Would using such a SCM make the Gods of OCaml angry?  :)  I don't intend
> to slip through a legal crack, I just want to work efficiently, and
> trying to manage patches without such a system seems like madness, like
> Linux kernel development before BitKeeper (I imagine).

The QPL talks only about distribution of derived software.  To
organize your work and that of your co-developers, everything goes.

If you wish to stick to the letter of the QPL, you can always not give
public access to your SCM repository, and do your public distribution
as a patch against the original Caml sources.  Your SCM will very
conveniently generate this patch.  It's no more work than distributing
tarballs.

This said, I believe the spirit of the QPL is that anyone can easily
see what parts of your derived work are original work and what parts
are unchanged from the OCaml sources.  In this view, as mentioned
earlier in this thread, modified sources + original sources is
just as good as original sources + patch.

However, a public SCM repository is more than just a set of (original
sources, modified sources) pairs.  In particular, if your repository
contains several versions of the original OCaml sources (because you
track our releases), it might not be clear which version of the
original sources correspond to which version of your modified
sources. So, some changes that we have made may appear like you made
them, which isn't quite in the spirit of the QPL.

So, you're in a gray area.  I don't think anyone will be upset to the
point of bothering you about your public repository.  I certainly won't.
But if I were you I'd just stick to the letter of the QPL, just to
have one less thing to worry about.

- Xavier Leroy


  parent reply	other threads:[~2008-04-09 15:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-07  4:29 Edgar Friendly
2008-04-07 19:10 ` [Caml-list] " Peng Zang
2008-04-07 19:17   ` Adrien
2008-04-07 19:54   ` Dario Teixeira
2008-04-07 20:00     ` Sylvain Le Gall
2008-04-07 20:09       ` [Caml-list] " Edgar Friendly
2008-04-07 20:14     ` [Caml-list] " Peng Zang
2008-04-09 15:21 ` Xavier Leroy [this message]
2008-04-09 16:24   ` Edgar Friendly

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=47FCDEDC.7000602@inria.fr \
    --to=xavier.leroy@inria.fr \
    --cc=caml-list@inria.fr \
    --cc=thelema314@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