Mailing-List: contact log4j-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4J Developers List" <log4j-dev@jakarta.apache.org>
Message-Id: <5.2.0.9.0.20030509193010.02bacae8@mail.qos.ch>
Date: Fri, 09 May 2003 19:36:16 +0200
To: "Log4J Developers List" <log4j-dev@jakarta.apache.org>
From: Ceki =?iso-8859-1?Q?G=FClc=FC?= <ceki@qos.ch>
Subject: Re: License questions
In-Reply-To: <5.1.0.14.0.20030509192350.019d6ec8@mail.jahia.com>
References: <5.2.0.9.0.20030509190349.02bbedc8@mail.qos.ch>
 <5.1.0.14.0.20030509183355.02972e88@mail.jahia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed


At 07:25 PM 5/9/2003 +0200, you wrote:
>Hi Ceki,
>
>Yes absolutely the FAQ answers my question. If I understand correctly all 
>I need to do is acknowledge that I have used ASF code. Is that correct ?

Hmm, not exactly. You must also retain the existing copyright and license.

The license FAQ  is of course located at:

http://www.apache.org/foundation/licence-FAQ.html

Q 11: I've made improvements to the Apache code, may I distribute the
       modified result?

   Absolutely -- subject to the terms of the Apache licence, of
   course. You can give your modified code away for free, or sell it, or
   keep it to yourself, or whatever you like. Just remember that the
   original code is still covered by the Apache licence and you must
   comply with its terms. Even if you change every single line of the
   Apache code you're using, the result is still based on the
   Foundation's licensed code. You may distribute the result under a
   different licence, but you need to acknowledge the use of the
   Foundation's software. To do otherwise would be stealing.

The original code is still covered by the Apache licence and you must
comply with its terms.  For redistributions with source you cannot
remove the existing copyright (that would violate the first term of
the license).

The license is really the only binding document. Just read it. If that
does not help, read it again. :-)

>cheers,
>   Serge Huber.
>
>At 07:08 PM 5/9/2003 +0200, you wrote:
>
>>Hi Serge,
>>
>>Have you looked at the terms of the Apache license?
>>
>>A copy of the license can be found at
>>
>>   http://www.apache.org/LICENSE.txt
>>
>>See also the FAQ
>>
>>http://www.apache.org/LICENSE.txt in particular the answer to question 11.
>>
>>Does this answer your question?
>>
>>At 06:46 PM 5/9/2003 +0200, you wrote:
>>
>>>Hi all,
>>>
>>>First of all congratulations on Log4J and Chainsaw ! They are two great 
>>>tools which have really helped me through a lot of rough debugging times :)
>>>
>>>Anyway, I have developed a small tool that integrates with the JDBC 
>>>logger called P6Spy. It has a module that supports Log4J, and can 
>>>therefore be configured to use the socket appender. My tool uses log 
>>>messages sent by P6Spy containing metrics about SQL statements, and 
>>>builds statistics in order to recommend database index creation (close 
>>>to what MS SQL Profiler does, or MyProfiler, but my tool is not database 
>>>specific).
>>>
>>>As I knew nothing of Swing programming I started out by modifying 
>>>Chainsaw's code. I had to move the classes around a bit, renaming 
>>>packages and changing some others quite significantly because I added a 
>>>tabbed pane that includes my SQL specific views. I want to release my 
>>>tool using a license based on the Apache license (hosted on 
>>>SourceForge), but I am not clear as to how to handle license issues. As 
>>>some classes contain both Chainsaw's original code (I used the source 
>>>code from version 1.2.7 I think) and my own modifications, I am not 
>>>clear as to what the proper course of action is. I have no problem at 
>>>giving credit where it's due, and I am wondering if I could just leave 
>>>the files that have the Apache license headers alone (although I have 
>>>added my own classes and code), and add my Apache-based license on my 
>>>new classes. Or is it ok if I just give the original credit in a 
>>>COPYRIGHT file for all the original authors and code ?
>>>
>>>I don't think this should be commited in Log4J because it is more P6Spy 
>>>specific than Log4J, but as I based this on Chainsaw's code to start 
>>>with, I just want to make sure everybody's cool with the release before 
>>>I do it (I have also talked to the P6Spy team).
>>>
>>>Thanks,
>>>   Serge Huber.
>>>
>>>
>>>- -- --- -----=[ serge.huber at jahia dot com ]=---- --- -- -
>>>Jahia : A collaborative source CMS and Portal Server
>>>www.jahia.org Community and product web site
>>>www.jahia.com Commercial services company
>>>
>>>
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
>>>For additional commands, e-mail: log4j-dev-help@jakarta.apache.org
>>
>>--
>>Ceki  For log4j documentation consider "The complete log4j manual"
>>       http://www.qos.ch/shop/products/clm_t.jsp
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: log4j-dev-help@jakarta.apache.org
>
>- -- --- -----=[ serge.huber at jahia dot com ]=---- --- -- -
>Jahia : A collaborative source CMS and Portal Server
>www.jahia.org Community and product web site
>www.jahia.com Commercial services company
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: log4j-dev-help@jakarta.apache.org
>

--
Ceki  For log4j documentation consider "The complete log4j manual"
       http://www.qos.ch/shop/products/clm_t.jsp 


---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-dev-help@jakarta.apache.org