From: mgushee@havenrock.com
To: caml-list@pauillac.inria.fr
Subject: Re: [Caml-list] User library license
Date: Sun, 23 Feb 2003 10:35:50 -0700 [thread overview]
Message-ID: <3E58A406.22073.804D795@localhost> (raw)
In-Reply-To: <dc14ed605f867256cf0f9eb7ee329a35@cypherpunks.to>
On 23 Feb 2003 at 7:30, Anonymous via the Cypherpunks Tonga Remai
wrote:
> GPL eliminates commercial usage.
Well, you'd better let Red Hat Software know about that. They have
this bizarre notion that you can build a whole business around GPL'ed
software. Fools.
Or did you mean to say something a little different?
> The best choices would be either the Academic Free
> License or the Mozilla Public License. The Academic
> Free License is modern 'best practice' and was drafted
> by OSI lawyers. The MPL came about through extensive
> user discussions over a long period of time
I wonder what sort of users you're referring to? Personally, I find
the MPL a monstrosity of legal jargon. Anyway, if you're going to
assert that certain licenses are "best," your readers would
appreciate it if you explained how you think those licenses benefit
software authors and/or the community. The fact that a certain
license was carefully designed (a claim that, I think, could be made
for most open source licenses) doesn't by itself make the license
good in general, or appropriate for any given project.
> See also the "Fallacy of GNU" -
> http://www.osopinion.com/perl/story/13420.html
Hmph. Takes a potentially interesting point and butchers it. The
author's thesis is essentially: the GPL depends on copyright;
copyrighted materials are subject to fair use; since the GPL hasn't
been tested in court, fair use may undermine its supposed
protections without our knowing it. Could be. But he spends 90% of
the article illustrating general points that may or may not be
relevant.
--
Matt Gushee
Englewood, CO USA
-------------------
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
next prev parent reply other threads:[~2003-02-23 17:35 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
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 [this message]
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=3E58A406.22073.804D795@localhost \
--to=mgushee@havenrock.com \
--cc=caml-list@pauillac.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