License header question

[Reto Bachmann-Gmür <me...@farewellutopia.com>]

Hi Bertrand

Thanks for the info and your pointers. Running RAT I was wondering if
adding an additional apache license headerr to code which already has
a category A license is the right thing to do.

That's how rat suggest the file header to be:

/*
 *
 * 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.
 *
*/

/*
Copyright (c) 2009, Yahoo! Inc. All rights reserved.
Code licensed under the BSD License:
http://developer.yahoo.net/yui/license.txt
version: 3.0.0
build: 1549
*/

Cheers,
Reto

On Tue, Jul 12, 2011 at 10:39 AM, Bertrand Delacretaz
<bd...@apache.org> wrote:
> Hi Reto,
>
> On Tue, Jul 12, 2011 at 2:40 AM, Reto Bachmann-Gmür <re...@apache.org> wrote:
>> ...I suggest we release clerezza parent and all the modules in the
>> release profile as per svn revision 1145401....
>
> That's not how it works - Apache releases consist of (usually .tar.gz)
> archives of source code, so you (or whoever's taking the role of the
> release manager) have to prepare those archives for the Clerezza PPMC
> and Incubator PMC to vote on them.
>
> See
> http://www.apache.org/dev/release.html
> http://incubator.apache.org/guides/releasemanagement.html
> http://sling.apache.org/site/release-management.html (as an example of
> how we do it in Sling)
>
> You could for example put the suggested artifacts (created from an svn
> tag) under http://people.apache.org/~reto/something and post their
> URLs and md5 or other digests here so that we can check them and vote.
>
> It's also a good idea to run RAT [1] on the tagged svn source code,
> and keep track of this in a JIRA issue where Incubator PMC members can
> check the results.
>
> -Bertrand
>
> [1] http://incubator.apache.org/rat/
>

Re: License header question

[Bertrand Delacretaz <bd...@apache.org>]

Hi Reto,

On Tue, Jul 12, 2011 at 2:08 PM, Reto Bachmann-Gmür
<me...@farewellutopia.com> wrote:
> ...Thanks for the info and your pointers. Running RAT I was wondering if
> adding an additional apache license headerr to code which already has
> a category A license is the right thing to do....

I don't think so, in your example I'd keep just the existing BSD license header.

Then, indicate somewhere (in the JIRA that has the RAT results
probably) why RAT's complaining is ok for those files.

-Bertrand