In my opion, it's better to keep author info for respect.
Just think sometimes other guys copy your codes.



KimmKing(kimmk...@163.com)
 == In me the tiger sniffs the rose. ==

 
发件人: Wang Xin
发送时间: 2018-03-13 22:02
收件人: dev@dubbo.apache.org
主题: Re: How to add Apache license head to the files of hessian-lite sub project
Should the author info be removed?  @author Scott Ferguson
 
Xin Wang
lovep...@hotmail.com<mailto:lovep...@hotmail.com>
 
 
 
在 2018年3月13日,下午7:50,Mark Thomas <ma...@apache.org<mailto:ma...@apache.org>> 写道:
 
On 13/03/18 06:03, Ian Luo wrote:
+1 to keep original license info since it’s Apache License 1.0.
 
Mentors, would you mind to guide us on this particular problem?
 
Leave the ALv1.1 headers (with the copyright) in place.
 
The text from section 3 should appear in the NOTICE file.
 
Mark
 
 
 
Thanks,
-Ian.
 
On 12 Mar 2018, at 7:02 PM, Kimm King 
<kimmk...@163.com<mailto:kimmk...@163.com>> wrote:
 
I think keeping the notice is awesome.
 
 
 
KimmKing(kimmk...@163.com<mailto:kimmk...@163.com>)
== In me the tiger sniffs the rose. ==
 
 
发件人: Wang Xin
发送时间: 2018-03-12 18:01
收件人: dev@dubbo.apache.org<mailto:dev@dubbo.apache.org>
主题: How to add Apache license head to the files of hessian-lite sub project
Hi,all
     Now I’m adding Apache license head to the Dubbo project.  I find that ,the 
hessian-lite sub project is totally  copied from hessian project 
(http://hessian.caucho.com/) , it’s package is modified and maintained here.
The hessian project complies with Apache license 1.1. The license head in each 
file is as the following:
    What should I do with it?
 
/*
* Copyright (c) 2001-2004 Caucho Technology, Inc.  All rights reserved.
*
* The Apache Software License, Version 1.1
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
*
* 1. Redistributions of source code must retain the above copyright
*    notice, this list of conditions and the following disclaimer.
*
* 2. Redistributions in binary form must reproduce the above copyright
*    notice, this list of conditions and the following disclaimer in
*    the documentation and/or other materials provided with the
*    distribution.
*
* 3. The end-user documentation included with the redistribution, if
*    any, must include the following acknowlegement:
*       "This product includes software developed by the
*        Caucho Technology (http://www.caucho.com/)."
*    Alternately, this acknowlegement may appear in the software itself,
*    if and wherever such third-party acknowlegements normally appear.
*
* 4. The names "Burlap", "Resin", and "Caucho" must not be used to
*    endorse or promote products derived from this software without prior
*    written permission. For written permission, please contact
*    i...@caucho.com<mailto:i...@caucho.com><mailto:i...@caucho.com>.
*
* 5. Products derived from this software may not be called "Resin"
*    nor may "Resin" appear in their names without prior written
*    permission of Caucho Technology.
*
* THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED
* WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
* OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
* DISCLAIMED.  IN NO EVENT SHALL CAUCHO TECHNOLOGY OR ITS CONTRIBUTORS
* BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY,
* OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT
* OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
* BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
* WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
* OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN
* IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*
* @author Scott Ferguson
*/
 
 
Xin Wang
lovep...@hotmail.com<mailto:lovep...@hotmail.com><mailto:lovep...@hotmail.com>
 
 
 
 
 
 

Reply via email to