Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: neutral (hermes.apache.org: local policy)
Date: Sat, 5 Feb 2005 08:21:20 -0800
From: Justin Erenkrantz <justin@erenkrantz.com>
To: Nick Kew <nick@webthing.com>
Cc: dev@apr.apache.org
Subject: Re: Licensing for apr_dbd and MySQL
Message-ID: <20050205162120.GD10529@scotch.ics.uci.edu>
Mail-Followup-To: Justin Erenkrantz <justin@erenkrantz.com>,
	Nick Kew <nick@webthing.com>, dev@apr.apache.org
References: <200502051107.23310.nick@webthing.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200502051107.23310.nick@webthing.com>
User-Agent: Mutt/1.5.6i

On Sat, Feb 05, 2005 at 11:07:20AM +0000, Nick Kew wrote:
> I don't know if MySQL's exception for open source projects would cover us.
> I'm not really happy with it: it looks to me like a potential torpedo under
> the whole of MySQL's GPL licensing.  It also raises ugly questions over 
> whether it might impose unacceptable additional constraints on closed-source
> users of the APR - i.e. does it give them an exception to the GPL too?

Right: the problem isn't for us as we'd be covered by their open-source
exception, but the problem would be for our downstream repackagers.  The ASF
policy is not to include any licensing restrictions that prevent closed source
applications on the code that we ship.

MySQL has a special exception for PHP that allows derivative works to not fall
under the GPL.  Such a clause might work, but in reading the text of that
exception, I'm not so sure it holds up either.

Also, their FLOSS License Exception doesn't seem to be quite what we want:

http://www.mysql.com/company/legal/licensing/foss-exception.html

I'll also note that there is legal-discuss@apache.org which has a number of
lawyers and such - they may also be able to provide some (non-binding) advice.

HTH.  -- justin