caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Dave Berry" <Dave@kal.com>
To: "Sven LUTHER" <luther@dpt-info.u-strasbg.fr>
Cc: <reig@dcs.gla.ac.uk>, <caml-list@inria.fr>
Subject: RE: [Caml-list] CDK license
Date: Wed, 6 Jun 2001 11:24:57 +0100	[thread overview]
Message-ID: <8E31D6933A2FE64F8AE3CC1381EEDCE704C231@NT.kal.com> (raw)

> -----Original Message-----
> From: Sven LUTHER [mailto:luther@dpt-info.u-strasbg.fr]
> > I would encourage people to use an X/BSD-like license for code
whereever
> > possible. It saves you all this hassle with determining what is and
is
> > not allowed, and which code may be linked or distributed with which
> > other code.
> 
> Yes, including taking all your code, doing some modification 
> to it, and giving nothing back.

Yes.  If someone wishes to do that, they can.  Most people will choose
to make changes available, because it benefits them if the open source
library grows.  And if they don't, at least they are still using OCaml
libraries, and increasing the usage of OCaml.  To me, this far outweighs
any disadvantage.

> If someone wants to take my code, and not contribute back any 
> changes they do, then by all means, they can pay me for a commercial 
> licenced version.

This is unlikely to happen, although it depends on the terms you offer.
For one thing, the extra expense in negotiating the contract will put
many people off.  If you require a run-time, per-installation, license,
the extra cost may prevent someone from using the code.  This actually
happened with MLWorks -- the license of SML/TK required a run-time cost
that we simply couldn't afford.

For the CDK, the situation is even more complex.  There are many
authors, of many separate packages.  Negotiation and license
arrangements could be hideously complex.  This could encourage people to
develop their own counterparts, which would be a Bad Thing.

If your main aim is to protect your code from unwanted use, then go
ahead and use the GPL or LGPL.  If your main aim is to get your code
used as widely as possible, use a less restrictive license.  Surely the
aim of the CDK is to promote wide use, rather than to restrict it?

Dave.
-------------------
To unsubscribe, mail caml-list-request@inria.fr.  Archives: http://caml.inria.fr


             reply	other threads:[~2001-06-06 10:26 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-06 10:24 Dave Berry [this message]
2001-06-06 16:24 ` Brian Rogoff
2001-06-08 13:27   ` Sven LUTHER
2001-06-08 15:35     ` Brian Rogoff
2001-06-08 13:24 ` Sven LUTHER
  -- strict thread matches above, loose matches on Subject: below --
2001-06-06  9:44 Dave Berry
2001-06-06 10:04 ` Sven LUTHER
2001-06-06 15:44 ` Stefan Monnier
2001-06-07  1:25   ` Jacques Garrigue
2001-06-08 12:59     ` Sven LUTHER
2001-06-07  9:03   ` Joerg Czeranski
2001-05-30 19:06 Brian Rogoff
2001-05-31  1:05 ` rbw3
2001-06-06  7:05   ` Sven LUTHER
2001-06-06  7:42     ` Sven LUTHER
2001-05-31  2:27 ` Jacques Garrigue
2001-05-31  3:11   ` Brian Rogoff
2001-05-31  7:46     ` Fabrice Le Fessant
2001-06-06  7:40     ` Sven LUTHER
2001-06-06  8:36       ` reig
2001-06-06  8:51         ` Sven LUTHER
2001-05-31 22:05 ` John Max Skaller

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=8E31D6933A2FE64F8AE3CC1381EEDCE704C231@NT.kal.com \
    --to=dave@kal.com \
    --cc=caml-list@inria.fr \
    --cc=luther@dpt-info.u-strasbg.fr \
    --cc=reig@dcs.gla.ac.uk \
    /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).