ant elder wrote:
Reviewing the legal files for the M5 release and there is lots of
stuff in the NOTICE file which I think we don't actually need and
having it there makes it hard to see through all the noise to verify
that we do have what is need. Past practice has been to add a
copyright statement to the NOTICE file from any dependency license
which included one but that is not what the ASF policy is and this has
been clarified in varrious discussion around the ASF including this
from VP of Legal -
http://apache.markmail.org/message/u66o5ucyfquxjl7i. Looking at whats
there I can't see many that we really do need so I'd like to remove
all the unnecessary ones to make it clearer what the required notices
really are and that we do actually include them.
...ant
+1.
I'd like to get these changes into the NOTICES files for the travel sample
if possible. However the RC is imminent and I don't want to delay it for this.
When creating the NOTICES file for the travel sample I carried everything over
from the NOTICES in the Tuscany SCA distribution because I noticed that the
wording in there was
"This product includes/uses xxxx"
The travel sample uses most of what's in the Tuscany binary distro but it
doesn't include any of those things. Does the new guidance require notices
(where applicable) for things that are used by code in the distro, or only
for things that are included in the distro?
Simon
