From: Stuart Ballard <stuart.a.ballard@gmail.com>
To: Archie Cobbs <archie@dellroad.org>
Cc: GNU Classpath <classpath@gnu.org>, mauve-discuss@sourceware.org
Subject: Re: Mauve license
Date: Thu, 16 Feb 2006 17:51:00 -0000 [thread overview]
Message-ID: <ba76afd90602160951w41ae85eev11f74a93d08277d6@mail.gmail.com> (raw)
In-Reply-To: <43F4B90E.9030209@dellroad.org>
On 2/16/06, Archie Cobbs <archie@dellroad.org> wrote:
> This can make sense if the Harmony tests are Harmony-specific.
Some are, some aren't. They plan to have a separation between the two
though. So Classpath will be able to use the non-specific part of
Harmony's testsuite.
> Otherwise I don't see what the point is.
The point is that, for whatever reasons (rational or irrational), some
people simply won't contribute to a GPL-licensed project. Some of
those people are Harmony contributors. If those people want to
contribute to a Java testsuite, which they do, it won't be Mauve as
long as Mauve is GPL.
> There may be no real reason it should be GPL, but in any case it is...
> so.. what's the problem with that? I mean, from a practical standpoint.
From a practical standpoint it's deterring a fairly large body of
potential contributors...
> But you seem also to be asking the religious question "why GPL"?
Not at all. I like the GPL. I think the GPL-with-exception license of
Classpath is the perfect license for what Classpath does. I use the
GPL on almost all my own code (although I prefer the LGPL for things
that are designed to be used as libraries).
Even RMS points out that using non-copyleft licenses can be beneficial
when it's a net gain for Free Software as a whole (eg Ogg).
And in this case I think there is such a gain, because the GPL is
buying us nothing (since there's no practical reason why anyone would
*want* to take Mauve proprietary) but costing us contributors.
I seem to be in a minority though, so I'll drop the issue I guess.
Stuart.
--
http://sab39.dev.netreach.com/
next prev parent reply other threads:[~2006-02-16 17:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-16 15:55 Stuart Ballard
2006-02-16 16:17 ` Mauve license: How with COST.OMG.ORG? Audrius Meskauskas
2006-02-16 16:41 ` Mauve license David Gilbert
2006-02-16 17:34 ` Stuart Ballard
2006-02-16 16:52 ` Andrew Haley
2006-02-16 17:14 ` Archie Cobbs
2006-02-16 17:25 ` Stuart Ballard
2006-02-16 17:35 ` Andrew Haley
2006-02-16 17:40 ` Archie Cobbs
2006-02-16 17:51 ` Stuart Ballard [this message]
2006-02-16 17:59 ` Andrew Haley
2006-02-16 18:01 ` Archie Cobbs
2006-02-16 18:19 ` Stuart Ballard
2006-02-16 18:00 ` Robert Schuster
2006-02-21 0:09 ` Tom Tromey
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=ba76afd90602160951w41ae85eev11f74a93d08277d6@mail.gmail.com \
--to=stuart.a.ballard@gmail.com \
--cc=archie@dellroad.org \
--cc=classpath@gnu.org \
--cc=mauve-discuss@sourceware.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).