You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by Serge Huber <sh...@jahia.com> on 2003/05/09 18:46:22 UTC
License questions
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
Re: License questions & Chainsaw
Posted by Serge Huber2 <sh...@jahia.com>.
Hi Ceki,
Thank you very much for your detailed clarifications. I am very grateful. I
will therefore add my Apache-based (Apache license with the references to
the foundation replaced with my own) to ONLY my new files, and make sure
that all the original ASF files feature the appropriate ASF headers (as
they currently do since I haven't touched the headers, only the code).
Anyway I plan to give the appropriate credits in a CREDITS file attached to
my project (and taking full blame for all the bugs introduced :)), because
I always intended to make sure that everyone get the recognition they
deserve, and that I might contribute my little bit in the process. Of
course if this work is interesting to the ASF I am completely open to
contributing it, but I think it needs to "incubate" a little first, as it
is very young (everything was coded last week :)).
If my modifications to Chainsaw are interesting to anybody here, don't
hesitate to check the code once it'll be available (I'm waiting on
SourceForge's approval for the project), but I saw that there was a lot of
work in the CVS for a new version of Chainsaw (version 2 ?) that probably
goes far beyond what I've done.
Thanks for all the help,
Serge Huber.
At 00:06 10.05.2003 +0200, you wrote:
>Contrary to GPL, the Apache Software License is not viral. The ASL
>applies only to the parts of the software that were already ASLed. The
>ASL makes no claims on any additional code.
>
>Let class A be a Java class licensed under the ASL. If you write a new
>class B which derives from A, than you are free to license B under
>your preferred license as long as you do not remove the ASL and Apache
>copyright from A.
>
>Now, if you modify A itself, then the modified parts are yours and the
>original parts of A must remain APLed. You cannot just remove the
>Apache copyright from A, even if modified. This is required by the 1st
>clause of the ASL as well as basic honesty.
>
>One could painstakingly try to delimit the parts which are ASLed and the
>other parts which are under a different license (within the same
>file).
>
>A simpler approach would be to license the whole of the modified file
>under the ASL. However, this is not always possible. For example, the
>FSF says that the ASL is not compatible with the GPL. So it would be
>impossible to abide by the terms of the ASL (i.e. not remove the
>license) and at the same time follow FSF recommendations.
>
>Anyway, for the case of chainsaw, there is a LGPLed version on
>sourceforge that you can use.
>
>HTH,
>
>At 07:51 PM 5/9/2003 +0200, you wrote:
>
>>Well, the ambiguity I'm was having with is : "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."
>>
>>But now if I understand this correctly does this apply to the whole code
>>or just the original classes ?
>>
>> * 1. Redistributions of source code must retain the above copyright
>> * notice, this list of conditions and the following disclaimer.
>> *
>>
>>I understand that the source code I've used must retain the copyright
>>notice, but would about the source code I've added ? In the GPL I have to
>>commit it under the GPL license, but under the Apache license I'm not
>>clear about this.
>>
>>Sorry for being a little slow about this :)
>>
>>Regards,
>> Serge Huber.
>>
>>At 07:36 PM 5/9/2003 +0200, you wrote:
>>
>>>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
>>
>>- -- --- -----=[ 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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-dev-help@jakarta.apache.org
Re: License questions
Posted by Ceki Gülcü <ce...@qos.ch>.
Contrary to GPL, the Apache Software License is not viral. The ASL
applies only to the parts of the software that were already ASLed. The
ASL makes no claims on any additional code.
Let class A be a Java class licensed under the ASL. If you write a new
class B which derives from A, than you are free to license B under
your preferred license as long as you do not remove the ASL and Apache
copyright from A.
Now, if you modify A itself, then the modified parts are yours and the
original parts of A must remain APLed. You cannot just remove the
Apache copyright from A, even if modified. This is required by the 1st
clause of the ASL as well as basic honesty.
One could painstakingly try to delimit the parts which are ASLed and the
other parts which are under a different license (within the same
file).
A simpler approach would be to license the whole of the modified file
under the ASL. However, this is not always possible. For example, the
FSF says that the ASL is not compatible with the GPL. So it would be
impossible to abide by the terms of the ASL (i.e. not remove the
license) and at the same time follow FSF recommendations.
Anyway, for the case of chainsaw, there is a LGPLed version on
sourceforge that you can use.
HTH,
At 07:51 PM 5/9/2003 +0200, you wrote:
>Well, the ambiguity I'm was having with is : "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."
>
>But now if I understand this correctly does this apply to the whole code
>or just the original classes ?
>
> * 1. Redistributions of source code must retain the above copyright
> * notice, this list of conditions and the following disclaimer.
> *
>
>I understand that the source code I've used must retain the copyright
>notice, but would about the source code I've added ? In the GPL I have to
>commit it under the GPL license, but under the Apache license I'm not
>clear about this.
>
>Sorry for being a little slow about this :)
>
>Regards,
> Serge Huber.
>
>At 07:36 PM 5/9/2003 +0200, you wrote:
>
>>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
>
>- -- --- -----=[ 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
Re: License questions
Posted by Serge Huber <sh...@jahia.com>.
Well, the ambiguity I'm was having with is : "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."
But now if I understand this correctly does this apply to the whole code or
just the original classes ?
* 1. Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
*
I understand that the source code I've used must retain the copyright
notice, but would about the source code I've added ? In the GPL I have to
commit it under the GPL license, but under the Apache license I'm not clear
about this.
Sorry for being a little slow about this :)
Regards,
Serge Huber.
At 07:36 PM 5/9/2003 +0200, you wrote:
>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
>
- -- --- -----=[ 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
Re: License questions
Posted by Ceki Gülcü <ce...@qos.ch>.
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
Re: License questions
Posted by Serge Huber <sh...@jahia.com>.
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 ?
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
Re: License questions
Posted by Ceki Gülcü <ce...@qos.ch>.
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