Re: MySQL FOSS Exception

On Fri, 23 Jul 2004 16:49:32 +0200, Francesco P. Lovergine wrote: > http://www.mysql.com/products/licensing/foss-exception.html > > A few programs link currently the old non-GPL libmysqlclient10 in order > to retain compatibility with other free licenses which have known > problems and require ex

Re: SRP

On Mon, 26 Jul 2004 19:11:26 -0700, Russ Allbery wrote: > MiguelGea <[EMAIL PROTECTED]> writes: > >> Hello debian-legal, >> I'm thinking about packaging SRP for debian. > >> Question 1: I'm not sure if there are any problem on packaging it. What >> do you think about? > > Please note that SRP

Re: MySQL FOSS Exception

On Mon, 26 Jul 2004 13:30:24 +0200, Francesco P. Lovergine wrote: > On Sun, Jul 25, 2004 at 12:20:22PM +, Andreas Metzler wrote: >> Francesco Paolo Lovergine debian.org> writes: [...] >> >> http://zak.greant.com:/licensing/rlog?f=licensing/FLOSS-exception.txt >> cu andreas >

Re: SRP

On Mon, 02 Aug 2004 09:23:07 +0100, Edmund GRIMLEY EVANS wrote: > Andres Salomon <[EMAIL PROTECTED]>: > >> I'm not sure how to interpret this; I'm not familiar enough w/ SRP-Z. Is >> this a different algorithm, such that the source would need to be >> si

[Fwd: Upgrade of MySQL FLOSS License Exception]

FYI.. -- Andres Salomon <[EMAIL PROTECTED]> --- Begin Message --- Greetings All, Version 0.2 of the MySQL FLOSS License Exception has been released. The MySQL FLOSS License Exception is an extension to the terms and conditions of the GNU General Public License (GPL) that increas

turck-mmcache license violation?

It would appear that turck-mmcache is covered under the GPL. However, it links against php4, whose license is incompatible w/ the GPL. Is there some sort of exception clause that was left out of the copyright file, or are we violating the turck-mmcache license?

Re: turck-mmcache license violation?

On Thu, 11 Nov 2004 20:12:42 -0200, cascardo wrote: > One could claim that php4 is part of the operating system, just like > they do with OpenSSL. That is nuts! One could claim anything. However, most people don't consider php4 part of the OS. > > Sorry for introducing a reason for a flame. >

qlogic firmware license

Hi, QLogic just emailed me the wording of their new license for qla2xxx firmware. Please let me know if anyone sees problems with this. Copyright (C) 2003 –2005 QLogic Corporation [QLA2x00] This program includes a device driver for Linux 2.6.x that is distributed with QLogic hardware specific

Re: qlogic firmware license

On Thu, 07 Jul 2005 15:13:47 -0400, Andres Salomon wrote: > Hi, > > QLogic just emailed me the wording of their new license for qla2xxx > firmware. Please let me know if anyone sees problems with this. > > > Copyright (C) 2003 –2005 QLogic Corporation [QLA2x00] > &

Re: qlogic firmware license

On Fri, 08 Jul 2005 01:59:25 +0200, Francesco Poli wrote: > On Thu, 07 Jul 2005 15:13:47 -0400 Andres Salomon wrote: > >> Hi, >> >> QLogic just emailed me the wording of their new license for qla2xxx >> firmware. > > Good, thanks for dealing with this is

Re: qlogic firmware license

On Sat, 09 Jul 2005 01:11:46 +0200, Francesco Poli wrote: > On Fri, 08 Jul 2005 12:01:14 -0400 Andres Salomon wrote: > >> On Fri, 08 Jul 2005 01:59:25 +0200, Francesco Poli wrote: [...] >> >> The reason for the dual licensing is because they have OEMs that would >>

mysql license update

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Interestingly enough, I just stumbled upon the following: http://www.mysql.com/products/opensource-license.html It appears that the mysql folks now provide an exception for derivative works linked against php. Hopefully (assuming debian-legal is ok

Re: MySQL Licensing Issues

On Fri, 20 Feb 2004 10:09:38 +0100, Zak Greant wrote: > Greetings All, > > We have set up a list for discussing MySQL community issues. If anyone is > interested in joining, please send a blank message to > [EMAIL PROTECTED] > > The main topic of discussion for the short term will be licensing.

Re: The MySQL FOSS Exception v0.1

(CC'ing debian-legal for any suggestions they may have, as well) On Fri, 2004-03-12 at 06:40, Zak Greant wrote: > On Thursday, March 11th at 22:58 CET, the MySQL team become the proud > parent of a brand new baby license exception. Birth occurred much > sooner than the estimated deliver date of

ASL2 and artistic compatibility

It would appear that the new upstream release of libapache2-mod-perl2 has been relicensed; from the ASL 1.1 to the ASL 2.0. As has already been discussed, the ASL (both 1.1 and 2.0) and GPL are incompatible (at least, the FSF claims they are). What has previously been used w/ modperl (1 and 2, un

updated mysql exception clause draft

The mysql folks are preparing 0.2 of their FLOSS exception. The current draft can be seen here: http://zak.greant.com:/licensing/getfile/licensing/FLOSS-exception.txt?v=1.4 The most notable differences are the addition of some licenses, and the removal of the derived-work-may-not-bundle-mysq

Re: non-free firmware in kernel modules, aggregation and unclear copyright notice.

On Tue, 05 Apr 2005 11:39:02 +0200, Christoph Hellwig wrote: > On Tue, Apr 05, 2005 at 11:36:58AM +0200, Arjan van de Ven wrote: >> One of the options is to even ship the firmware in the kernel tarbal but >> from a separate directory with a clear license clarification text in it. > > I think that

kernel firmware status

I created a wiki page that contains a list of all drivers that are currently considered undistributable by Debian, the available license information we have for them, and various other comments: http://wiki.debian.net/?KernelFirmwareLicensing I would appreciate feedback from d-l about the various

Re: kernel firmware status

On Wed, 06 Apr 2005 08:56:56 -0300, Humberto Massa wrote: > > Andrew Suffield wrote: > [...] > > >>> The firmware contained herein as keyspan_*.h is > >>> ... > >>> Permission is hereby granted for the distribution of > >>> this firmware image as part of a Linux or other

more kernel firmware stuff

Hi, Regarding , I've been discussing firmware licensing w/ various hardware vendors. Here a quote from my discussions with QLogic: > On Wed, 2005-05-11 at 10:22 -0700, David Wagner wrote: > > Andres, > > > > The firmware files mentioned, run enti

Re: broadcom proposed firmware licence, please comment ...

On Sun, 29 May 2005 05:48:55 -0400, Nathanael Nerode wrote: [...] > Great! This license is totally distributable. I'm not sure, unfortunately, > what counts as "equivalent" to hexadecimal. I think that's the only problem. > > If it was just "permission to distribute, unmodified, in any form"

Re: more kernel firmware stuff

On Wed, 25 May 2005 11:36:43 -0400, Andres Salomon wrote: [...] > > > And so on. QLogic wants to have a conference call w/ me and their legal > dept, as they have questions on BSD vs GPL licensing. I think it would be > good to have someone from d-l on the call as well. Any v

Re: broadcom proposed firmware licence, please comment ...

On Tue, 31 May 2005 22:32:30 -0400, Nathanael Nerode wrote: > Andres Salomon wrote: >> As I remember, upstream (jgarzik/davem) was not overly interested in such >> a patch to tg3. Is this still the case, or are they amenable to such >> changes? > > Upstream was not i

Re: CS00003271 - Please review your case update - (Assigned)

On Wed, 25 May 2005 11:24:27 -0700, NIC Technology Support wrote: > Below is a response to your case number CS3271 submitted to Broadcom NIC > Technology Support. > > Case Title: GPLed driver and binary-only firmware blobs. > > Response from Broadcom: Can you please check with your Legal te

Re: CS00003271 - Please review your case update - (Assigned)

On Mon, 2005-06-06 at 13:03 +0900, Horms wrote: > On Wed, Jun 01, 2005 at 02:14:02PM -0400, Andres Salomon wrote: > > On Wed, 25 May 2005 11:24:27 -0700, NIC Technology Support wrote: > > > > > Below is a response to your case number CS3271 submitted to Broadcom >

Re: Copyright concerns regarding Seafile

So, just to make things even less clear (because I'm interested in seafile-server getting into debian).. While Libzdb is currently licensed under GPLv3, it used to have a exception file allowing linking with GPLv2 code: