Using Mauve for Our Project

Using Mauve for Our Project

[PureNative Software]

I am presently involved with the NewJ Library for C++, a cleanroom
implementation of the Java API in 100% native C++, for C++ environments. It
uses natural C++ like CNI does, but it does not require any VM at all and
works with regular ANSI C++ compilers (like gcc and VC++) without requiring
extensions. We have been using Mauve internally for some time now and are
really benefiting from it. In fact, we have converted the entire Mauve
project to native C++. We are wishing to make this native C++ version of
Mauve available as open source to the public. However, the NewJ Library for
C++ just like Sun's Java Platform is based on open standards but is not open
source. Thus, compiling our C++ version of Mauve requires our NewJ Library
header files and static library, which are not open source. (The Trial
Edition is available as a free download from our Web site at
http://www.pure-native.com.) Is it permissible for us to distribute our C++
version of Mauve to the public without the underlying library being open
source? This seems partially covered by the FAQ but we wish to have some
clarification before proceeding. Thank you in advance.

Regards,
Vargas
PureNative Software

Re: Using Mauve for Our Project

[Brian Jones]

PureNative Software <info@pure-native.com> writes:

> We have been using Mauve internally for some time now and are really
> benefiting from it. In fact, we have converted the entire Mauve
> project to native C++. We are wishing to make this native C++
> version of Mauve available as open source to the public. However,
> ... compiling our C++ version of Mauve requires our NewJ Library
> header files and static library, which are not open source.  Is it
> permissible for us to distribute our C++ version of Mauve to the
> public without the underlying library being open source?

Your question is more appropriate for a lawyer.  While I don't have a
use for it, having more Mauve goodness open to the public is a plus in
my book, for what it's worth.

Brian
-- 
Brian Jones <cbj@gnu.org>

Re: Using Mauve for Our Project

[Stephen Crawley]

Vargas,

You wrote:
> I am presently involved with the NewJ Library for C++, a cleanroom
> implementation of the Java API in 100% native C++, for C++ environments. It
> uses natural C++ like CNI does, but it does not require any VM at all and
> works with regular ANSI C++ compilers (like gcc and VC++) without requiring
> extensions. We have been using Mauve internally for some time now and are
> really benefiting from it. In fact, we have converted the entire Mauve
> project to native C++. We are wishing to make this native C++ version of
> Mauve available as open source to the public. However, the NewJ Library for
> C++ just like Sun's Java Platform is based on open standards but is not open
> source. Thus, compiling our C++ version of Mauve requires our NewJ Library
> header files and static library, which are not open source. (The Trial
> Edition is available as a free download from our Web site at
> http://www.pure-native.com.) Is it permissible for us to distribute our C++
> version of Mauve to the public without the underlying library being open
> source? This seems partially covered by the FAQ but we wish to have some
> clarification before proceeding. Thank you in advance.

Don't make any decisions based on your interpretation of the Mauve FAQ. 

The Mauve software is covered by the terms of the GNU Public License.
For more information, refer here:

  http://www.gnu.org/licenses/licenses.html

You would also be advised to talk to a lawyer.

-- Steve