public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
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:25:00 -0000	[thread overview]
Message-ID: <ba76afd90602160925r6e3e2d4fj52ad5025b2842f80@mail.gmail.com> (raw)
In-Reply-To: <43F4B2F9.9090801@dellroad.org>

On 2/16/06, Archie Cobbs <archie@dellroad.org> wrote:
> This Apache/Harmony thing vs. Claspath/GPL debate is just so tempting.. :-)

Heh.

> But let's talk practicalities.. here's a simple thing I don't understand.
>
> What exactly prevents Harmony from using Mauve as a test suite?

Nothing, and in fact I think they plan to do just that.

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.

> So then if Apache only wants to run Mauve tests, what impact does Mauve
> being GPL have? Why can Apache folks just download Mauve and run it,
> the same way Classpath hackers do? Mauve is its own self-contained project.

They can, but the Classpath hackers don't just run it, they write it too.

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?

I'm a GPL supporter in general but using it on a testsuite seems
really wrong to me.

> As to the issue of converting Mauve to JUnit, that's surely a lot of work
> any way you slice it, and in any case that seems like an orthogonal issue.

Yes, at this moment I'm only concerned with political issues.
Technical issues are so much easier that they can be deferred for now
;)

Stuart.

--
http://sab39.dev.netreach.com/

  reply	other threads:[~2006-02-16 17:25 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 [this message]
2006-02-16 17:35     ` Andrew Haley
2006-02-16 17:40     ` Archie Cobbs
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=ba76afd90602160925r6e3e2d4fj52ad5025b2842f80@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).