[ 
https://issues.apache.org/jira/browse/RANGER-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382107#comment-15382107
 ] 

Velmurugan Periasamy edited comment on RANGER-1109 at 7/18/16 11:33 AM:
------------------------------------------------------------------------

Raised by Joe Witt.

Commentary: 

[Minor - for next release - might not be true] In source LICENSE. "This product 
includes json2.js (https://github.com/douglascrockford/JSON-js - Public Domain 
license) by Douglas Crockford". Should be in notice. This doesn't alter the 
LICENSE but is worth referencing in the NOTICE as per attribution guidance in 
http://www.apache.org/legal/resolved.html#can-works-placed-in-the-public-domain-be-included-in-apache-products
 which refers to http://www.apache.org/legal/resolved.html#category-a  

[Minor - for next release - might not be true] In source LICENSE. "This product 
includes Font Awesome 3.2.1 (http://fontawesome.io/ - SIL Open Font License 
(OFL) licensee) by Dave Gandy" This should be in the NOTICE and not LICENSE. 
Such a dependency (Category B) should only be a binary dependency unless in 
source release it meets this exception "small amounts of source that is 
directly consumed by the ASF product at runtime in source form, and for which 
that source is unmodified and unlikely to be changed anyway (say, by virtue of 
being specified by a standard), inclusion of appropriately labeled source is 
also permitted" as stated in 
http://www.apache.org/legal/resolved.html#category-b  

[Minor - for next release] In source license several references are made to ASL 
V2 items. These references belong in NOTICE and only if there is information 
worth carrying forward. The Copyright is good to include so those belong in 
NOTICE.  

[Minor - for next release] In source LICENSE. The 'visualsearch license' is 
referenced. This should say something like "This product bundles 
'VisualSearch.js 0.4.0' which is available under an MIT style license." then 
include license text w/copyright. Or just put it up in the already present MIT 
license listing you have.  

[Minor - for next release] In source license. The requires-handlebar-plugin. As 
per text at bottom of readme 
(https://github.com/SlexAxton/require-handlebars-plugin) Nice job catching the 
'handlebars.js' listing and putting under MIT licenses (with proper copyright) 
and the 'require.js'. But, it appears the require.js listing under MIT licenses 
has incorrect copyright. It should be "Copyright (c) 2010-2012, The Dojo 
Foundation All Rights Reserved." as found in 
(./security-admin/target/security-admin-web-0.6.0/libs/bower/requirejs/js/require.js)
 for example.


was (Author: vperiasamy):
Raised by Joe Witt.

Commentary: [Minor - for next release - might not be true] In source LICENSE. 
"This product includes json2.js (https://github.com/douglascrockford/JSON-js - 
Public Domain license) by Douglas Crockford". Should be in notice. This doesn't 
alter the LICENSE but is worth referencing in the NOTICE as per attribution 
guidance in 
http://www.apache.org/legal/resolved.html#can-works-placed-in-the-public-domain-be-included-in-apache-products
 which refers to http://www.apache.org/legal/resolved.html#category-a  [Minor - 
for next release - might not be true] In source LICENSE. "This product includes 
Font Awesome 3.2.1 (http://fontawesome.io/ - SIL Open Font License (OFL) 
licensee) by Dave Gandy" This should be in the NOTICE and not LICENSE. Such a 
dependency (Category B) should only be a binary dependency unless in source 
release it meets this exception "small amounts of source that is directly 
consumed by the ASF product at runtime in source form, and for which that 
source is unmodified and unlikely to be changed anyway (say, by virtue of being 
specified by a standard), inclusion of appropriately labeled source is also 
permitted" as stated in http://www.apache.org/legal/resolved.html#category-b  
[Minor - for next release] In source license several references are made to ASL 
V2 items. These references belong in NOTICE and only if there is information 
worth carrying forward. The Copyright is good to include so those belong in 
NOTICE.  [Minor - for next release] In source LICENSE. The 'visualsearch 
license' is referenced. This should say something like "This product bundles 
'VisualSearch.js 0.4.0' which is available under an MIT style license." then 
include license text w/copyright. Or just put it up in the already present MIT 
license listing you have.  [Minor - for next release] In source license. The 
requires-handlebar-plugin. As per text at bottom of readme 
(https://github.com/SlexAxton/require-handlebars-plugin) Nice job catching the 
'handlebars.js' listing and putting under MIT licenses (with proper copyright) 
and the 'require.js'. But, it appears the require.js listing under MIT licenses 
has incorrect copyright. It should be "Copyright (c) 2010-2012, The Dojo 
Foundation All Rights Reserved." as found in 
(./security-admin/target/security-admin-web-0.6.0/libs/bower/requirejs/js/require.js)
 for example.

> Address IPMC feedback raised during Ranger 0.6.0 release
> --------------------------------------------------------
>
>                 Key: RANGER-1109
>                 URL: https://issues.apache.org/jira/browse/RANGER-1109
>             Project: Ranger
>          Issue Type: Bug
>            Reporter: Velmurugan Periasamy
>
> Address suggestions raised during Ranger 0.6.0 IPMC vote.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to