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

Stefan Seelmann commented on DIRKRB-412:
----------------------------------------

Hi Jiajia,

I remeber that I raised that issue during a vote last year, but recently during 
the Fortress release I digged a bit deeper into the legal files requirements 
(see 
https://mail-archives.apache.org/mod_mbox/directory-dev/201603.mbox/%[email protected]%3E).

I think the very same applies to Kerby, so here are my suggestions:
* LICENSE and NOTICE files in the root folder should only contain the AL2.0 and 
standard notice (without any attributions), because they are used for the 
source release package and I assume that the Kerby source code doesn't include 
any 3rd party source code.
* Minor: the NOTICE file should use the bare form without the ".txt" extension
* Also for the distributed Maven jars no attributions are required because they 
only contain the compiled sources but no 3rd party dependencies are bundled.
* Only if we plan to distribute a binary package that includes 3rd party 
bundles (e.g. kdc-dist with gson, netty, slf4j) then only that package must 
contain the additional licenses and attributens. If that is planned I'd be 
happy to assist.

HTH,
Stefan


> Update NOTICE file with required attributions of used dependencies
> ------------------------------------------------------------------
>
>                 Key: DIRKRB-412
>                 URL: https://issues.apache.org/jira/browse/DIRKRB-412
>             Project: Directory Kerberos
>          Issue Type: Improvement
>    Affects Versions: 1.0.0-RC2
>            Reporter: Xu Yaning
>            Assignee: Jiajia Li
>
> As is reported by Stefan, we should update the NOTICE file with the required 
> attributions of used dependencies (slf4j, netty, gson). That is required as 
> soon as we publish a binary package that includes the dependencies.



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

Reply via email to