public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Archie Cobbs <archie@dellroad.org>
To: Stuart Ballard <stuart.a.ballard@gmail.com>
Cc: GNU Classpath <classpath@gnu.org>, mauve-discuss@sourceware.org
Subject: Re: Mauve license
Date: Thu, 16 Feb 2006 17:40:00 -0000	[thread overview]
Message-ID: <43F4B90E.9030209@dellroad.org> (raw)
In-Reply-To: <ba76afd90602160925r6e3e2d4fj52ad5025b2842f80@mail.gmail.com>

Stuart Ballard wrote:
> But as I understand it their current plan is to use Mauve *in addition
> to* (and secondary to) their own test suite and only develop their own
> tests in their own repository.
> 
> So we end up with two test suites being developed by two disjoint
> groups, both of whom are free to (and likely to) *run* the other
> group's suite against their own implementation, but still no actual
> cooperation.

This can make sense if the Harmony tests are Harmony-specific.
Otherwise I don't see what the point is.

> Basically, I just don't see why Mauve *should* be GPL. There's
> absolutely no benefit in claiming copyleft on it and a considerable
> benefit from not doing so. Other than the issue of finding copyright
> holders, why *shouldn't* it be X11 or modified-BSD licensed so that
> anyone can use it as they see fit?

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.

But you seem also to be asking the religious question "why GPL"?
Like most religious questions that one has no objective "answer"..

If you really want to hear an "answer" then you can read the "official"
one in the GPL FAQ...

-Archie

__________________________________________________________________________
Archie Cobbs      *        CTO, Awarix        *      http://www.awarix.com

  parent reply	other threads:[~2006-02-16 17:40 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 [this message]
2006-02-16 17:51       ` Stuart Ballard
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=43F4B90E.9030209@dellroad.org \
    --to=archie@dellroad.org \
    --cc=classpath@gnu.org \
    --cc=mauve-discuss@sourceware.org \
    --cc=stuart.a.ballard@gmail.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 read-only IMAP folder(s) and NNTP newsgroup(s).