www-legal-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Legal Wiki] Update of "3party/notice" by SebastianBazley
Date Mon, 25 Feb 2008 15:33:04 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Legal Wiki" for change notification.

The following page has been changed by SebastianBazley:

The comment on the change is:
Comments asking for clarification

    * Additional restrictions that may be relevant to select audiences are to be noted in
a README.  [https://svn.apache.org/repos/asf/httpd/httpd/trunk/README example] contains a
Cryptographic Software Notice.
+ [Sebb] Comments
+  * I assume that NOTICE files don't need to itemise Apache projects, e.g. if Apache Foo
includes Apache Bar in the distribution, this does not need to be mentioned, as Apache Bar
is covered by the paragraph: "This product includes software developed at The Apache Software
+  * Where do the LICENSE, NOTICE and README files need to appear? eg.
+    * In every independently distributed artefact, e.g. source/binary archives, binary jars
+    * In source code repositories? If so, where?
+    * If an archive includes nested archives or Java jars, I assume these also need N&L
files - is this correct?
+  * I assume that the LICENSE NOTICE and README files are only supposed to contain details
of items that are actually '''included''' in a distribution.
+    * Is this correct? 
+    * Or should they ever include references to external dependencies? If so, when?
+    * Where an Apache project has multiple modules which are also distributed in separate
files, do the N&L files need to be tailored for the individual items, or can the same
N&L files be used for all modules? For example, there may be some code in module A that
requires an attribution, but module B does not have the code: can module B use the same N&L

DISCLAIMER: Discussions on this list are informational and educational
only.  Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF.  See <http://www.apache.org/licenses/> for
official ASF policies and documents.
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org

View raw message