caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Sven Luther <luther@dpt-info.u-strasbg.fr>
To: Nicolas Cannasse <warplayer@free.fr>
Cc: Sven Luther <luther@dpt-info.u-strasbg.fr>, caml-list@inria.fr
Subject: Re: [Caml-list] User library license
Date: Mon, 24 Feb 2003 11:00:32 +0100	[thread overview]
Message-ID: <20030224100032.GA1889@iliana> (raw)
In-Reply-To: <003d01c2dbe9$b14a88b0$2713f9ca@WARP>

On Mon, Feb 24, 2003 at 06:47:06PM +0900, Nicolas Cannasse wrote:
> > > > > The new "user code library" is a good idea, but GPL
> > > > > and LGPL are both bad ideas.
> > > >
> > > > The best idea is to use the same licence the ocaml runtime currently
> > > > uses :
> > > >
> > > > The Library is distributed under the terms of the GNU Library General
> > > > Public License version 2 (found in /usr/share/common-licenses/LGPL-2
> > > > on debian systems).
> > >
> > > And what about a "do anything you want with it, including compiling,
> > > modifiying, inserting bugs" license ?
> > > I mean, this kind of collaborative work shouldn't even be (c)
> > > (although it's fair to maintain a list of contributors somewhere in the
> > > distribution)
> >
> > The problem with that is that anyone can take your work, modify it, and
> > don't give anything back, look at apple for example, they took the BSD
> > kernel, and don't give anything back. I think licencing is the main
> > reason they choose a BSD krernel over a linux one back then. I suppose
> > some people (including me) would not be willing to contribute code under
> > these circunstances, so i don't think it would be best for the project,
> > since the aim is to put in common the code.
> 
> Uhm, perhaps I'm not paranoid enough, but whe're just talking about an
> extension to the Standard OCaml Library...
> The goal here is to provide to every caml developper all the data structures
> he will ever want to use - and corresponding algorithms. Who is going to
> steal it ? and for what purpose ?

Sure, sure, but still if nobody has plans to steal it, it should be ok
writing a licence that ensures that and nobody should complain.

> If tomorrow Apple steal it and start developping serious software in OCaml,
> I think it would be a good thing for the whole community since you'll be
> able to tell your boss that "ocaml is great : Apple is using it" , or to the
> guy who's hiring you " i'm writing such good code that Apple itself can't
> help stealing it " :)

Sure, but the problem is that it will not be apple which will do it,
and your argument will have a lot less impact if you give your boss the
name of some obscure little company he knows nothing about.

> As a programmer, I'm proud to licence software that I'm developping, but
> this is gonna be a big common melt in the first times, I keep my pride away
> and give my code for the sake of the community.

sure, but you do not say under what licence you are licencing it.

> > Also, the main argument, is that it gains you nothing more, since you
> > have to link with the ocaml runtime anyway, which is licenced as LGPL +
> > exception.
> 
> You gain a clear license for users not familiar with the LGPL :  I think
> that the "GPL" part in "LGPL" can sometimes be mistaken by frilous users.

Most people don't even read the licences, just the name of them. Sure
the LGPL is similar to the GPL in name, but there is no reason to be
afraid of that until you have hidden agendas. And anyway, i think the
best way to do this, is to start the licence thingy by "We use the same
licence as the ocaml runtime, ...", and nobody will have problems with
that. Again, there was a huge thread some time back, just read it. Also,
maybe the ocaml team should have named their licence, so this would not
be a problem. It would be the ORPL (Ocaml Runtime Public Licence), and
everyone would be happy with it, the people not reading licences would
know it is the licence used by the ocaml runtime, and the people readin
licences would notice it is just the LGPL and be happy.

Friendly,

Sven Luther
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


  reply	other threads:[~2003-02-24 10:04 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-23  6:30 Anonymous via the Cypherpunks Tonga Remailer
2003-02-23 17:00 ` Sven Luther
2003-02-23 19:57   ` Brian Hurt
2003-02-24  9:18     ` Sven Luther
2003-02-24  1:45   ` Nicolas Cannasse
2003-02-24  2:43     ` Brian Hurt
2003-02-24  9:26       ` Sven Luther
2003-02-24  9:37         ` Alessandro Baretta
2003-02-24 18:01           ` Blair Zajac
2003-02-24 13:43       ` John Max Skaller
2003-02-24  9:24     ` Sven Luther
2003-02-24  9:47       ` Nicolas Cannasse
2003-02-24 10:00         ` Sven Luther [this message]
2003-02-24 13:51           ` John Max Skaller
2003-02-24 18:00       ` Blair Zajac
2003-02-25  6:18         ` John Max Skaller
2003-02-25  9:12           ` Markus Mottl
2003-02-25 17:25             ` John Max Skaller
2003-02-24 18:52       ` Issac Trotts
2003-02-24 20:22         ` [Caml-list] off-topic: apple and bsd (was Re: User library license) james woodyatt
2003-02-24 21:18       ` [Caml-list] User library license Damien Doligez
2003-02-25 10:27         ` Sven Luther
2003-02-23 17:35 ` mgushee
2003-02-23 19:52 ` Brian Hurt
2003-02-24  9:35   ` Sven Luther

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=20030224100032.GA1889@iliana \
    --to=luther@dpt-info.u-strasbg.fr \
    --cc=caml-list@inria.fr \
    --cc=warplayer@free.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).