chemistry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nick Burch <nick.bu...@alfresco.com>
Subject Re: Validation of release packages (was: Fwd: [jira] Commented: (CMIS-224) Improve legal/standard aspects of the release process / packaging)
Date Wed, 08 Sep 2010 13:59:31 GMT
On Wed, 1 Sep 2010, Gabriele Columbro wrote:
> One question to conclude: referring to Nick's comments at [4], do you 
> think we should have anything else in NOTICE for all packages? In other 
> words, which of the licenses mentioned in the various DEPENDENCIES files 
> actually require a NOTICE?

The NOTICE file should contain as little as possible. Everything else 
should go in DEPENDENCIES, a readme, the website etc

The reason for this is that every downstream user has to include 
everything in our NOTICE file in their own notices. So, we want it to 
include all the required notices of our upstream dependencies, along with 
our own notice. However, we don't want to full the NOTICE file up with 
things that aren't required, as we don't want to burden our users!

To review the NOTICE files, take a look at what's in there, and compare 
that to the dependencies list (which is hopefully correct, since maven 
generated it!). The notice file should have our notice in it, and after 
that any dependency ones. If a dependency is under a license that requires 
a notice, it should be there. (If not, it shouldn't. The main apache 3rd 
party licenses page may give some help on this)

Does this make sense to everyone?

Nick

Mime
View raw message