From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26868 invoked by alias); 16 Feb 2006 18:19:00 -0000 Received: (qmail 26852 invoked by uid 22791); 16 Feb 2006 18:18:59 -0000 X-Spam-Check-By: sourceware.org Received: from xproxy.gmail.com (HELO xproxy.gmail.com) (66.249.82.207) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 16 Feb 2006 18:18:57 +0000 Received: by xproxy.gmail.com with SMTP id s9so123850wxc for ; Thu, 16 Feb 2006 10:18:55 -0800 (PST) Received: by 10.70.103.18 with SMTP id a18mr1457494wxc; Thu, 16 Feb 2006 10:18:49 -0800 (PST) Received: by 10.70.109.9 with HTTP; Thu, 16 Feb 2006 10:18:48 -0800 (PST) Message-ID: Date: Thu, 16 Feb 2006 18:19:00 -0000 From: Stuart Ballard To: Archie Cobbs Subject: Re: Mauve license Cc: GNU Classpath , mauve-discuss@sourceware.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <43F4B2F9.9090801@dellroad.org> <43F4B90E.9030209@dellroad.org> Mailing-List: contact mauve-discuss-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: mauve-discuss-owner@sourceware.org X-SW-Source: 2006-q1/txt/msg00039.txt.bz2 (this is going to show up in the wrong place in the thread - for some reason I can see mails showing up in the archives but I'm not receiving them myself till much later, so I don't have this one myself to respond to yet) Andrew Haley wrote: > > 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? There are quite a few reasons, some logical, some not, why people won't contribute to GPL projects. Some corporations have policies prohibiting employees from looking at GPL code. I don't believe there's any *good* reason for an organization to have such a policy, but some do. It appears there's at least one contributor on the Harmony list who is unable to look at Classpath code for this reason. Some corporations may have weaker policies that would still prohibit employees from actually writing GPL code on company time. Some people see the GPL as an endorsement of a political position they don't agree with and won't work on software licensed under it for that reason. Some people philosophically oppose the idea of copyleft and don't want their work under such a license. The Apache organization has policies against distributing GPL code and I believe also against requiring it as a dependency. (Even if everyone at Apache could be persuaded that changing this was a good idea, their procedures for doing so seem to take a while). A test suite isn't strictly a dependency but I think they'd at least have strong reservations against making it official policy that if you're writing tests for Harmony that test public APIs they should go in this GPL project. Another reason I feel test suites shouldn't be copyleft is similar to RMS's reasoning about Ogg: the greatest benefit to Free Software is obtained by having all implementations be compatible and compatible with the existing proprietary solution to help people escape the trap. The best way to achieve that is by getting good tests as widely disseminated and used as possible (analagous to getting Ogg support as widely used as possible to help people escape the mp3 trap). (another email I'm seeing in the archives but haven't received myself - Andrius's point about the OMG tests. I believe it should be possible to convert the license back to LGPL if we have permission from the copyright holders of all the code that was changed since, which would then mean that as long as the OMG tests are self-contained, they could be linked happily with a non-copyleft Mauve even if they themselves are still copyleft). Stuart. -- http://sab39.dev.netreach.com/