caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Joerg Czeranski <jc@joerch.org>
To: caml-list@inria.fr
Subject: Re: [Caml-list] CDK license
Date: Thu, 7 Jun 2001 11:03:26 +0200 (CEST)	[thread overview]
Message-ID: <200106070903.LAA09171@kiste.thiemo.net> (raw)
In-Reply-To: <5lpuchy5of.fsf@rum.cs.yale.edu>

Stefan Monnier wrote:
> >>>>> "Dave" == Dave Berry <Dave@kal.com> writes:
> > I would encourage people to use an X/BSD-like license for code
> > whereever possible.  This license allows anyone to do anything whatsoever
> > with the code, provided that they keep the copyright notice and NO
> > WARRANTY notice.  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.
>
> You seem to be talking about the original BSD license.  Note that in that
> license, the requirement to keep the copyright notice makes it incompatible
> with the GPL license (which is why there is a revised BSD license which
> does away with the "keep the copyright notice" part).

No, the "revised" BSD license (BSD license without advertising clause)
removes the condition that you have to state "this product contains
source code of Stefan Monnier".  Especially for huge software products
like the *BSD operating systems this clause became unweildy.

Keeping the copyright/license notice is probably the only thing that's
required by all licenses.

(I might have misunderstood you though, but I'd like to make this point
clear for the benefit of those who don't know the BSD license.)

> This goes to show that using the old BSD license does not really save you
> ``from determining what is and is not allowed, and which code may be linked
> or distributed with which other code.''

That's certainly true, you always have to read licenses and understand
their legal implications.  It's just much easier to read and understand
the 20 lines of the BSD license than the endless pages of the GPL or
the LGPL.

jörg

P.S.: I also don't like the ideology behind the GPL, but that's
      a different matter.
-------------------
To unsubscribe, mail caml-list-request@inria.fr.  Archives: http://caml.inria.fr


  parent reply	other threads:[~2001-06-07  9:03 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-06-06 10:24 Dave Berry
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
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=200106070903.LAA09171@kiste.thiemo.net \
    --to=jc@joerch.org \
    --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).