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:14:00 -0000 [thread overview]
Message-ID: <43F4B2F9.9090801@dellroad.org> (raw)
In-Reply-To: <ba76afd90602160755t72a84b31l402af391a5dfe61d@mail.gmail.com>
Stuart Ballard wrote:
> Harmony hackers get to see that Classpath hackers aren't inflexible
> GPL-zealots, and both groups of hackers get used to working together
> on a project that benefits both.
This Apache/Harmony thing vs. Claspath/GPL debate is just so tempting.. :-)
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?
Would Apache want to create it's own copy of Mauve and check that
into SVN? That seems like a bad idea -- i.e, creating a "code fork".
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.
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.
-Archie
__________________________________________________________________________
Archie Cobbs * CTO, Awarix * http://www.awarix.com
next prev parent reply other threads:[~2006-02-16 17:14 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 [this message]
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
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=43F4B2F9.9090801@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).