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

Bug#207699: (forw) Re: Licence on your Apache chroot environment doc in "Securing Debian Manual"



Mr. Ratti has kindly granted dual-licence permission.

----- Forwarded message from Alexandre Ratti <alex@gabuzomeu.net> -----

Date: Fri, 29 Aug 2003 09:39:48 +0200
From: Alexandre Ratti <alex@gabuzomeu.net>
To: Rick Moen <rick@linuxmafia.com>
Subject: Re: Licence on your Apache chroot environment doc in "Securing Debian
 Manual"
X-Spam-Status: No, hits=-6.3 required=5.0
	tests=BAYES_01,EMAIL_ATTRIBUTION,IN_REP_TO,REFERENCES,
	      REPLY_WITH_QUOTES,USER_AGENT_MOZILLA_UA
	version=2.55

Hi Rick,


Rick Moen wrote:

>Hello.  I'm hoping you're the Alexandre Ratti whose kindly consented to
>incorporate his useful work on Apache chroot environments into the
>Securing Debian Manual, as shown at
>http://www.debian.org/doc/manuals/securing-debian-howto/ap-chroot-apache-env.en.html
>.  If not, please let me know, and my apologies.
>
Yes, that's me.

>I'm a sysadmin and Debian GNU/Linux user, who noticed your mention in
>the Apache chrooting docs of GNU FDL 1.2 licence terms for that work,
>which appears to create a minor problem, because the remainder of the
>Securing Debian Manual is under GNU GPLv2 or later -- and the two
>licences conflict.
>
>It's possible that you intended to either (1) grant permission for
>distribution under GPLv2 or later of the Manual's copy of your work
>(i.e., "dual licensing") or (2) grant permission for distribution under
>GNU FDL 1.2 with the additional exception that it may be distributed
>with the Securing Debian Manual (i.e., "licensing exception").  However,
>that is (so far) unclear.
>
>If you're willing to do dual licensing, that would be wonderful, and the
>ideal solution to the problem.
>
No problem. I want my doc to be available to the Debian project, so I'm 
going to dual-license it. You can go ahead and use the howto under the 
GPL/GFDL; I'll update the master copy on my site accordingly.

>Debian management asked me to handle this through their bug-tracking
>system, so I've opened bug #207699, viewable at
>http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=207699 .  You can
>comment directly to the bug report by writing to 207699@bugs.debian.org , 
>or I'll be glad to forward your comments.
>
Please forward them; feel free to get back to me if anything is unclear.


Cheers.

Alexandre





----- End forwarded message -----



Reply to: