savannah-hackers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Savannah-hackers] submission of PostFix LDAP Administration - savan


From: Jonathan Gonzalez V.
Subject: Re: [Savannah-hackers] submission of PostFix LDAP Administration - savannah.nongnu.org
Date: Wed, 22 Dec 2004 22:21:12 -0300
User-agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3 (gnu/linux)

Bruno Pelaia <address@hidden> writes:

Hi Bruno,

> The JaMM project is licensed under GPL, so there are no problems.
> (You can verify it at http://sourceforge.net/projects/jamm/)
>
> My only doubt is about QMail.schema due to the fact that QMail-ldap
> patch is released under BSD license.
> (You can verify it at http://www.qmail-ldap.org/qmail/QLDAPINSTALL)
> Reading the BSD License I cannot see anything wrong: I used the a piece
> of source code (qmail.schema) which is not modified. Indeed, I think
> that the only thing which can cause some problem is that in the file
> itself there is no reference to the BSD license.

I check the JaMM project, and the schema is under GPL, so there's no
problem with it. The real problem is with the qmail.schema the file is
licensed under the original BSD license which is a GPL-Incompatible,
is policy of Savannah do not accept files or dependencies licensed
under a GPL-Incompatible license.

>> I reviewed your new tarball and all files are ok with the exception of
>> the files under schema/. 
> Generally speaking about schemas ... I don't think amavis.schema nor
> jamm.schema are a problem: they both include a License notice (I'm going
> to write Keith and Dave about the license notice in jamm.schema, but it
> is already GPL'ed so there is no problem as I gave them the copyright
> since the beginning of the progect in the 2002).
>
> So let me ask you a question to speed up your check. About qmail.schema,
> which is under BSD license, assuming that I cannot leave it unmodified
> due to the lack of the explicit copyright and license in it ... do you
> think it is better to write down a note in a README whenever remove the
> file and give the user a link to download it?

It is not the idea give to the user an URL to download the file,
because you still having a dependence that is licensed under a
GPL-Incompatible license. There's two possible solution for this, one
is ask to the author to change the BSD license for the Modified BSD
license(mBSD) which is GPL-Compatible and the other is drop the
dependence itself and write another (possible better) solution to
replace this file.

You can see the mBSD license here:

    http://www.xfree86.org/3.3.6/COPYRIGHT2.html#5


> P.S. I never thought about licenses so much, let me say it is something
> interesting to discuss about and I have to learn a lot. Thank you!

If you want to learn more about license, I can recommend you to read
this:

        http://www.gnu.org/licenses/

It's a good page to start.

Regards,

-- 
"Emacs the only editor which has its own church"

Attachment: pgpqoVMn_Y4CY.pgp
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]