You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Venkatesh Seetharam (JIRA)" <ji...@apache.org> on 2014/05/27 22:47:03 UTC
[jira] [Created] (FALCON-453) possible LICENSE/NOTICE issues
Venkatesh Seetharam created FALCON-453:
------------------------------------------
Summary: possible LICENSE/NOTICE issues
Key: FALCON-453
URL: https://issues.apache.org/jira/browse/FALCON-453
Project: Falcon
Issue Type: Sub-task
Affects Versions: 0.5
Reporter: Venkatesh Seetharam
Fix For: 0.5
What external code has been bundled with the source? To me it look like the NOTICE file may be referring to a binary release not the source release? For example it mentions antlr in the NOTICE file but I can't find any antlr code in the source release. As antlr is BSD does it even need to be in NOTICE file? It's may be that all source files have had their headers changed to ALv2?
I also not the use of some fonts (from http://glyphicons.com?) and while they are included in the NOTICE but I'm not sure how they have been licensed. If it the free version and if so have the terms of the license met? [1]
NOTICE file is incorrect; it must not have the following header:
=========================================================================
== NOTICE file corresponding to the section 4 d of ==
== the Apache License, Version 2.0, ==
== in this case for the Apache Falcon distribution. ==
=========================================================================
Also the NOTICE file must ONLY contain required notices for files that
are actually in the enclosing distribution.
As such, the entries headed "This product includes/uses" are wrong;
only *included* bits are relevant when determining what must go in the
NOTICE file.
The LICENSE file should specify the versions of the included software,
because licenses may change between versions.
Again, only included code should be referenced.
--
This message was sent by Atlassian JIRA
(v6.2#6252)