You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@apr.apache.org by Joachim Zobel <jz...@heute-morgen.de> on 2007/07/30 21:52:30 UTC
Will apr_dbd_mysql be distributed with apr?
Hi.
Since niq has dual licensed it, with one license being Apache 2, this
should be possible.
If this is not yet planned it should be considered, since the fact that
it is missing has caused problems for lots of people.
Sincerely,
Joachim
Re: Will apr_dbd_mysql be distributed with apr?
Posted by "William A. Rowe, Jr." <wr...@rowe-clan.net>.
Nick Kew wrote:
> And indeed we have *exactly* such a deal. Whatever doubt there may
> be over the applicability of the GPL or the FOSS Exception to us,
> MySQL has helpfully published Appendix A to their FOSS exception,
> *explicitly* permitting APR/APU to be distributed under ASL.
> That is a clear and unambiguous yes.
We do? Reread the appendix; I believe their appendix is (paraphrasing)
your OSS license, when distributed as *source*.
> I think there remains one concession here. The build should default
> to --without-mysql, so that people don't link it unintentionally.
+1 - because of the with-source copyleft encumberance.
We aught to ask MySQL to interpret; if they don't consider it a derived work
due to binding (especially when we link 2, e.g. sqlite + mysql) then I hope
to proceed
Re: Will apr_dbd_mysql be distributed with apr?
Posted by Bojan Smojver <bo...@rexursive.com>.
On Wed, 2007-08-08 at 10:04 +0100, Nick Kew wrote:
> Whoa! ASF is flat. Noone is senior or junior.
I meant that as an sign of respect for people that built ASF.
> And indeed we have *exactly* such a deal.
FOSS exception applies when ASF ships the driver, no doubt at all.
> Nope. Folks shipping APU are bound by the ASL, and can do what the
> ASL permits. GPL is not relevant to that.
Actually, that's what the problem was (as I remember it). GPL is
relevant, because when these other people distributing APU change the
licence to something other than ASL (i.e. proprietary) and compile to
include the driver, they do not fall under FOSS exception any more.
Sure, they have to broker themselves a deal with MySQL AB in order to
ship (i.e. get a commercial licence).
I think that was the risk that ASF was reluctant to expose its licensees
to, because other software from ASF doesn't have such restrictions when
being redistributed (e.g. Oracle client licence even allows: "(b) you
may also distribute the programs with your applications;"). GPL is a bit
unique (some would say viral :-) there, I believe, as it even has
problems with dynamic linking to the GPL licensed programs.
But, as I said before, my memory could be bad there. And I would sure
like to see the driver in APU. All I wanted to do is make sure people
notice the issue has been raised. If it is not an issue, all the better.
--
Bojan
Re: Will apr_dbd_mysql be distributed with apr?
Posted by Nick Kew <ni...@webthing.com>.
On Wed, 08 Aug 2007 10:03:56 +1000
Bojan Smojver <bo...@rexursive.com> wrote:
> On Wed, 2007-08-08 at 00:18 +0100, Nick Kew wrote:
>
> > And I
> > think it means we're excused having to think through every
> > usage scenario.
>
> I kind of remember this discussion from awhile ago (the issue was
> raised by some senior ASF folks, I think).
Whoa! ASF is flat. Noone is senior or junior.
Though we do have different interests and roles.
> Even dynamic linking, according to FSF, is a no-no:
>
> http://www.fsf.org/licensing/licenses/gpl-faq.html#LinkingWithGPL
> http://www.fsf.org/licensing/licenses/gpl-faq.html#GPLPluginsInNF
APR is not linking to it. We're making that an option, but absolutely
not a requirement, even for apr_dbd. MySQL is no more linked than is
Oracle (and just consider the implications if we shipped a "derived
work" of Oracle)!
But that's an argument that could be said to be a grey area.
Fortunately, I don't think it's even relevant any more.
> So, when our MySQL driver dynamically links MySQL library, which is
> under the GPL, we have to either:
>
> - fall under MySQL FOSS exception
> - be GPL ourselves
Suppose our project was not FOSS, and that it did depend absolutely
on MySQL. Does that mean we can't distribute it? Nope, it just
means we'd have to negotiate a deal with MySQL permitting us to
distribute it on our own terms - whatever they may be.
And indeed we have *exactly* such a deal. Whatever doubt there may
be over the applicability of the GPL or the FOSS Exception to us,
MySQL has helpfully published Appendix A to their FOSS exception,
*explicitly* permitting APR/APU to be distributed under ASL.
That is a clear and unambiguous yes.
> Obviously, all the folks out there that are shipping APU with the
> driver included under the ASL licence are just fine (MySQL AB
> considers them under FOSS exception). However, folks shipping APU
> under a proprietary licence must buy a commercial MySQL licence or
> not distribute the driver.
Nope. Folks shipping APU are bound by the ASL, and can do what the
ASL permits. GPL is not relevant to that.
I think there remains one concession here. The build should default
to --without-mysql, so that people don't link it unintentionally.
--
Nick Kew
Application Development with Apache - the Apache Modules Book
http://www.apachetutor.org/
Re: Will apr_dbd_mysql be distributed with apr?
Posted by Bojan Smojver <bo...@rexursive.com>.
On Wed, 2007-08-08 at 00:18 +0100, Nick Kew wrote:
> And I
> think it means we're excused having to think through every
> usage scenario.
I kind of remember this discussion from awhile ago (the issue was raised
by some senior ASF folks, I think). But, I don't have a link to point to
unfortunately (getting old, memory fading etc. :-). In any event, if ASF
is cool with this, even better!
> - If they use only the apr_dbd API, then their work has no MySQL
> dependency. No problem.
Even dynamic linking, according to FSF, is a no-no:
http://www.fsf.org/licensing/licenses/gpl-faq.html#LinkingWithGPL
http://www.fsf.org/licensing/licenses/gpl-faq.html#GPLPluginsInNF
So, when our MySQL driver dynamically links MySQL library, which is
under the GPL, we have to either:
- fall under MySQL FOSS exception
- be GPL ourselves
Obviously, all the folks out there that are shipping APU with the driver
included under the ASL licence are just fine (MySQL AB considers them
under FOSS exception). However, folks shipping APU under a proprietary
licence must buy a commercial MySQL licence or not distribute the
driver.
Now, whether that's something ASF is still worried about, I don't know
(I _wish_ we could ship). That's why I asked. Maybe someone can ask ASF
legal if this is an issue or not.
--
Bojan
Re: Will apr_dbd_mysql be distributed with apr?
Posted by Nick Kew <ni...@webthing.com>.
On Wed, 08 Aug 2007 07:47:39 +1000
Bojan Smojver <bo...@rexursive.com> wrote:
> On Tue, 2007-08-07 at 21:09 +0100, Nick Kew wrote:
>
> > I recollect the ASF in the past being unable to include it due
> > to the GPL.
>
> Wasn't the other problem the fact that if this driver got included,
> people that decided to redistribute APR-util under a non-FOSS licence
> (i.e. proprietary) could be doing so illegally (unbeknown to them), as
> their software would then link against MySQL, for which they would
> need a commercial MySQL licence and ASF wasn't cool with exposing its
> licensees to such a risk with the software it ships?
MySQL has explicitly said we can distribute it under ASL.
That means our users are bound (only) by the ASL. And I
think it means we're excused having to think through every
usage scenario. But let's give it a try: suppose someone
distributes a non-FOSS product that uses MySQL through APR
(or a customised APR variant):
- If they use only the apr_dbd API, then their work has no MySQL
dependency. No problem.
- If they extend the apr_dbd API into MySQL-specific functionality,
then they - not us - are creating what might be considered a
derived work. Not our problem.
- If they bundle MySQL in a binary, then they know they need to
abide by the GPL. Just as if they bundle Oracle, they know
they need a license.
- If notwithstanding the above, they distribute a work derived
from APR that circumvents the GPL, that's MySQL's problem,
not ours. MySQL has accepted that APR-UTIL including the
MySQL driver should be distributed under the ASL, and
therefore users abiding by the ASL are in the clear.
--
Nick Kew
Application Development with Apache - the Apache Modules Book
http://www.apachetutor.org/
Re: Will apr_dbd_mysql be distributed with apr?
Posted by Bojan Smojver <bo...@rexursive.com>.
On Tue, 2007-08-07 at 21:09 +0100, Nick Kew wrote:
> I recollect the ASF in the past being unable to include it due
> to the GPL.
Wasn't the other problem the fact that if this driver got included,
people that decided to redistribute APR-util under a non-FOSS licence
(i.e. proprietary) could be doing so illegally (unbeknown to them), as
their software would then link against MySQL, for which they would need
a commercial MySQL licence and ASF wasn't cool with exposing its
licensees to such a risk with the software it ships?
PS. I personally would like to see the driver in APR-util.
--
Bojan
Re: Will apr_dbd_mysql be distributed with apr?
Posted by Nick Kew <ni...@webthing.com>.
On Tue, 7 Aug 2007 14:04:46 -0700
"Roy T. Fielding" <fi...@gbiv.com> wrote:
> According to
>
> http://www.mysql.com/company/legal/licensing/foss-exception.html
>
> 1. You obey the GPL in all respects for the Program and the
> Derivative Work, except for identifiable sections of the
> Derivative Work which are not derived from the Program, and
> which can reasonably be considered independent and separate
> works in themselves,
>
> Is apr_dbd_mysql an independent work or a Derived Work in relation
> to mysql? I am pretty certain RMS would say it is a Derived Work.
> I don't know what MySQL thinks, but their copyright may not apply
> if all you are doing is using the published client API.
Looking at the GPL, I can't see a basis for considering it a derived
work. The strongest argument for it can be taken from a paragraph
of the LGPL's introductory waffle, where it speaks of the distinction
between the GPL and LGPL:
"The reason we have a separate public license for some libraries is
that they blur the distinction we usually make between modifying or
adding to a program and simply using it. Linking a program with a
library, without changing the library, is in some sense simply using
the library, and is analogous to running a utility program or
application program. However, in a textual and legal sense, the
linked executable is a combined work, a derivative of the original
library, and the ordinary General Public License treats it as such."
That only refers to "the linked executable", which is not something
we're contemplating distributing. APR/APU work just fine, and even
provide the full apr_dbd API, without any requirement to link MySQL.
So any third-party user of APR should presumably be in the clear too,
unless *they* make something into a MySQL derived work.
We can include apr_dbd_oracle without our users requiring an Oracle
license. It's hard to justify MySQL being more restrictive.
> In other words, if it is an independent work (in the eyes of MySQL)
> then we can distribute it under the Apache License and, assuming
> we don't link in MySQL by default for binaries, there is no viral
> effect. However, if it is considered to be a Derived Work, then the
> MySQL exception is only saying that we can distribute both of them
> together if and only if the GPL is applied to apr_dbd_mysql
> (regardless of your decision as copyright owner). The exception
> therefore only protects the rest of APR from the viral clause,
> and we still can't redistribute it in our package
MySQL's view from their FOSS exception page:
"Derivative Work means a derivative work under copyright law."
It's hard to see how that would apply to a work that merely uses
their published API. And in my view, their Appendix A clinches
it: they're happy for APR to be distributed, including MySQL
support, under ASL 2.0.
> My opinion is that apr_dbd_mysql is an independent work that merely
> uses the published MySQL interfaces, and therefore okay for us to
> include in the distribution. That would be confirmed if MySQL said
> it was okay to license apr_dbd_mysql as under AL2. If all they said
> was that APR could include apr_dbd_mysql under the exception, then
> that doesn't say much of anything.
Indeed.
--
Nick Kew
Application Development with Apache - the Apache Modules Book
http://www.apachetutor.org/
Re: Will apr_dbd_mysql be distributed with apr?
Posted by "Roy T. Fielding" <fi...@gbiv.com>.
On Aug 7, 2007, at 1:09 PM, Nick Kew wrote:
> On Mon, 30 Jul 2007 21:52:30 +0200
> Joachim Zobel <jz...@heute-morgen.de> wrote:
>
>> Hi.
>>
>> Since niq has dual licensed it, with one license being Apache 2, this
>> should be possible.
>>
>> If this is not yet planned it should be considered, since the fact
>> that it is missing has caused problems for lots of people.
>
> Sorry, should've followed up to this straight away.
>
> I relicensed the apr_dbd_mysql driver six months ago. Basically
> (1) MySQL have explicitly excepted it from the GPL requirement.
> (2) Debian had raised it as an issue, so I resolved it with them.
> See http://bahumbug.wordpress.com/2007/01/09/re-licensing-
> apr_dbd_mysql/
>
> I recollect the ASF in the past being unable to include it due
> to the GPL. But Joachim pinged me before posting, and suggested that
> the problem should no longer apply after the license update.
> And I couldn't fault his argument: it's no longer clear to me that
> there's any problem with including it.
According to
http://www.mysql.com/company/legal/licensing/foss-exception.html
1. You obey the GPL in all respects for the Program and the
Derivative Work, except for identifiable sections of the
Derivative Work which are not derived from the Program, and
which can reasonably be considered independent and separate
works in themselves,
Is apr_dbd_mysql an independent work or a Derived Work in relation
to mysql? I am pretty certain RMS would say it is a Derived Work.
I don't know what MySQL thinks, but their copyright may not apply
if all you are doing is using the published client API.
In other words, if it is an independent work (in the eyes of MySQL)
then we can distribute it under the Apache License and, assuming
we don't link in MySQL by default for binaries, there is no viral
effect. However, if it is considered to be a Derived Work, then the
MySQL exception is only saying that we can distribute both of them
together if and only if the GPL is applied to apr_dbd_mysql
(regardless of your decision as copyright owner). The exception
therefore only protects the rest of APR from the viral clause,
and we still can't redistribute it in our package
My opinion is that apr_dbd_mysql is an independent work that merely
uses the published MySQL interfaces, and therefore okay for us to
include in the distribution. That would be confirmed if MySQL said
it was okay to license apr_dbd_mysql as under AL2. If all they said
was that APR could include apr_dbd_mysql under the exception, then
that doesn't say much of anything.
....Roy
Re: Will apr_dbd_mysql be distributed with apr?
Posted by Nick Kew <ni...@webthing.com>.
On Mon, 30 Jul 2007 21:52:30 +0200
Joachim Zobel <jz...@heute-morgen.de> wrote:
> Hi.
>
> Since niq has dual licensed it, with one license being Apache 2, this
> should be possible.
>
> If this is not yet planned it should be considered, since the fact
> that it is missing has caused problems for lots of people.
Sorry, should've followed up to this straight away.
I relicensed the apr_dbd_mysql driver six months ago. Basically
(1) MySQL have explicitly excepted it from the GPL requirement.
(2) Debian had raised it as an issue, so I resolved it with them.
See http://bahumbug.wordpress.com/2007/01/09/re-licensing-apr_dbd_mysql/
I recollect the ASF in the past being unable to include it due
to the GPL. But Joachim pinged me before posting, and suggested that
the problem should no longer apply after the license update.
And I couldn't fault his argument: it's no longer clear to me that
there's any problem with including it.
For the record, I'm happy to assign ownership to the ASF
and I'd like to see it included. I could reiterate here that
I'm totally flexible - as I said to Debian (recorded in
http://bahumbug.wordpress.com/2006/12/18/apacheaprmysql-packaging/ )
and that led to the license change they needed.
--
Nick Kew
Application Development with Apache - the Apache Modules Book
http://www.apachetutor.org/