caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Issac Trotts <ijtrotts@ucdavis.edu>
To: OCaml List <caml-list@inria.fr>
Subject: Re: [Caml-list] User library license
Date: Mon, 24 Feb 2003 10:52:25 -0800	[thread overview]
Message-ID: <3E5A69E9.4010306@ucdavis.edu> (raw)
In-Reply-To: <20030224092404.GB826@iliana>

Sven Luther wrote:

>On Mon, Feb 24, 2003 at 10:45:34AM +0900, Nicolas Cannasse wrote:
>  
>
>>>>>Regarding license ... I suppose LGPL could be fine.
>>>>>          
>>>>>
>>>>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 kernel 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.
>
It would be more accurate to say that they "copied" the BSD kernel. 
 "Taking"
usually means that the one who had it no longer has it.  Why should it 
matter
if they use information so long as they don't take away other people's 
freedom
to use it?  

Issac Trotts



-------------------
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


  parent reply	other threads:[~2003-02-24 18:46 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
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 [this message]
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=3E5A69E9.4010306@ucdavis.edu \
    --to=ijtrotts@ucdavis.edu \
    --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).