On 1/18/2019 9:17 AM, Christofer Dutz wrote:
> Hi all,
>
> as I was setting up things so Jenkins will build the project, I noticed that 
> you have some strange plugin in the build that enforces headers quite 
> strictly.
> I don’t have any objections to that, however it marked my usual ASF headers 
> as invalid because they didn’t have the first line in them.
>
> Currently your header looks like this:
>
> Copyright © 2019 Apache IoTDB(incubating) ([email protected])
>
> Licensed to the Apache Software Foundation (ASF) under one
> or more contributor license agreements.  See the NOTICE file
> distributed with this work for additional information
> regarding copyright ownership.  The ASF licenses this file
> to you under the Apache License, Version 2.0 (the
> "License"); you may not use this file except in compliance
> with the License.  You may obtain a copy of the License at
>
>     http://www.apache.org/licenses/LICENSE-2.0
>
> Unless required by applicable law or agreed to in writing, software
> distributed under the License is distributed on an "AS IS" BASIS,
> WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> See the License for the specific language governing permissions and
> limitations under the License.
>
> I would strongly suggest to remove the first line. It’s equivalent can be 
> automatically generated by a maven plugin and the way it is, I think it would 
> require changing each file in the repo every year. I doubt this is what you 
> want to do.
>
> What do you others think? (Especially the other mentors)
>
> Chris

I would defer to VP Legal to see what they say. 

At my firm, we always use 4 elements:
    The Copyright Symbol
    The Year of the Creation
    The Name of the Author
    A Rights Statement

For example, Copyright © 1997-2019 Peregrine Computer Consultants
Corporation.
All Rights Reserved.

Regards,

KAM

-- 
Kevin A. McGrail
VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171

Reply via email to