From: Audrius Meskauskas <audriusa@bluewin.ch>
To: Mauve discuss <mauve-discuss@sourceware.org>
Subject: Re: Mauve license: How with COST.OMG.ORG?
Date: Thu, 16 Feb 2006 16:17:00 -0000 [thread overview]
Message-ID: <43F4A580.1080203@bluewin.ch> (raw)
In-Reply-To: <ba76afd90602160755t72a84b31l402af391a5dfe61d@mail.gmail.com>
The packages for testing org.omg classes contain the source code from
the currently the most probably dead cost.omg.org CORBA open source
testing suite that was originally released under LGPL license. To
integrate into Mauve, I of course needed to modify the code (the
original test versions just prints messages to console). This means the
license conversion into GPL. If we change the license, all such tests
should probably be removed, and the Harmony project should also think
about this. Event if they get the alternative CORBA implementation from
somewhere else, it still needs a test suite to prevent degradation due
subsequent develompent. cost.omg.org is written by several serious
companies. I would take for me another year to write such thing from
scratch, it is not much simplier than the implementation itself.
The opponents of GPL license should think if they really want to reject
this valuable resource as well.
Audrius Meskauskas
next prev parent reply other threads:[~2006-02-16 16:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-16 15:55 Mauve license Stuart Ballard
2006-02-16 16:17 ` Audrius Meskauskas [this message]
2006-02-16 16:41 ` 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
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=43F4A580.1080203@bluewin.ch \
--to=audriusa@bluewin.ch \
--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).