caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Brian Hurt <brian.hurt@qlogic.com>
To: Matt Gushee <mgushee@havenrock.com>
Cc: Ocaml Mailing List <caml-list@inria.fr>
Subject: Re: License wars (was Re: [Caml-list] ANN: ChartPak - a data visualization library for the web)
Date: Mon, 20 Jan 2003 11:22:54 -0600 (CST)	[thread overview]
Message-ID: <Pine.LNX.4.33.0301201108220.2036-100000@eagle.ancor.com> (raw)
In-Reply-To: <20030120164653.GA6351@swordfish>

On Mon, 20 Jan 2003, Matt Gushee wrote:

> But quite apart from wanting to keep open (for myself) the option of
> using my code in a proprietary app, 

IANAL, but I do hang out with an IP lawyer, and as I understand it if it's
100% your code you can do whatever the heck with it you like.  You own the
copyright.  Everyone else is bound to the GPL (unless you decide to
release it under another license), but *you* are not.

Mind you, this only applies if it's 100% your code.  If you accept a patch 
from me, for example, then I own part of the copyright as well, and you 
have to get my agreement to change the license on my code/patch.  For 
large projects with lots of involved people (like Linux) it becomes 
effectively impossible to change the license.

I generally perfer the GPL, *because* I'm a professional programmer.  As 
the saying goes, I have to put food on the table as well.  If you want to 
use my code, pay me for it- either money (code for hire), or payment in 
kind.  Which is basically what the GPL is.  The payment to use (modify) my 
code is that I get some of your code.  Don't like the deal?  Don't use the 
code.  Write your own code.

But I'm not religous about it.  I strongly beleive that the guy writting
the code- the guy putting the sweat equity in to create the value- gets to
decide what sort of license it goes under.  Note that by choosing to
extend, and thereby reuse most of, GPL licensed code you are choosing you
license.  This can be viewed both as an advantage (everyone else has to
play under the same rules you play under) and as a disadvantage (you have
to play under the same rules everyone else plays under).  Note the same
can be said about the BSD license- it's both an advantage and a
disadvantage.  It is, however, your choice.

And compared to some of the EULAs that various commercial companies are 
foisting off, there's almost no difference.

Brian

-------------------
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-01-20 17:14 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-16 10:30 [Caml-list] ANN: ChartPak - a data visualization library for the web Matt Gushee
2003-01-16 12:30 ` Mattias Waldau
2003-01-16 12:45   ` Alessandro Baretta
2003-01-16 12:51   ` Jérôme Marant
2003-01-20 13:55   ` Fabrice Le Fessant
2003-01-20 16:46     ` License wars (was Re: [Caml-list] ANN: ChartPak - a data visualization library for the web) Matt Gushee
2003-01-20 17:22       ` Brian Hurt [this message]
2003-01-22 16:57       ` [Caml-list] Re: License wars Michaël Grünewald
2003-01-23 10:43         ` Alessandro Baretta
2003-01-24 15:31           ` John Max Skaller
2003-01-20 19:49     ` [Caml-list] ANN: ChartPak - a data visualization library for the web Mattias Waldau
2003-01-20 20:37       ` Brian Hurt
2003-01-24  4:19         ` [Caml-list] Baby Steps (was: ChartPak - a data visualization library for the web) Oleg
2003-01-24 10:59           ` Michal Moskal
     [not found]             ` <Pine.LNX.4.33.0301241322390.2036-100000@eagle.ancor.com>
2003-01-24 20:54               ` Michal Moskal
2003-01-24  5:33 ` [Caml-list] Re: License wars Matt Gushee
2003-01-24  8:46   ` Sven Luther
2003-01-24 11:16     ` Dmitry Bely
2003-01-24 11:28       ` Sven Luther
2003-01-24 11:31       ` Alessandro Baretta
2003-01-24 16:16         ` John Max Skaller
2003-01-24 15:49     ` John Max Skaller
2003-01-25  9:54   ` Michaël Grünewald

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=Pine.LNX.4.33.0301201108220.2036-100000@eagle.ancor.com \
    --to=brian.hurt@qlogic.com \
    --cc=caml-list@inria.fr \
    --cc=mgushee@havenrock.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;
as well as URLs for NNTP newsgroup(s).