From: Andrew Haley <aph@redhat.com>
To: Stuart Ballard <stuart.a.ballard@gmail.com>
Cc: Archie Cobbs <archie@dellroad.org>,
GNU Classpath <classpath@gnu.org>,
mauve-discuss@sourceware.org
Subject: Re: Mauve license
Date: Thu, 16 Feb 2006 17:59:00 -0000 [thread overview]
Message-ID: <17396.48600.174009.756765@zapata.pink> (raw)
In-Reply-To: <ba76afd90602160951w41ae85eev11f74a93d08277d6@mail.gmail.com>
Stuart Ballard writes:
>
> Even RMS points out that using non-copyleft licenses can be beneficial
> when it's a net gain for Free Software as a whole (eg Ogg).
>
> And in this case I think there is such a gain, because the GPL is
> buying us nothing (since there's no practical reason why anyone would
> *want* to take Mauve proprietary)
Oh, I see your meaning.
> but costing us contributors.
This part is the mystery. If, as you say, there's no practical reason
why anyone would *want* to take Mauve proprietary, why does it matter
that Mauve is GPL?
> I seem to be in a minority though, so I'll drop the issue I guess.
It's not that. I just don't understand.
Andrew.
next prev parent reply other threads:[~2006-02-16 17:59 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
2006-02-16 17:51 ` Stuart Ballard
2006-02-16 17:59 ` Andrew Haley [this message]
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=17396.48600.174009.756765@zapata.pink \
--to=aph@redhat.com \
--cc=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).