You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Joseph Witt (JIRA)" <ji...@apache.org> on 2015/01/29 13:01:34 UTC

[jira] [Updated] (NIFI-291) Address findings from 0.0.1 release process

     [ https://issues.apache.org/jira/browse/NIFI-291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joseph Witt updated NIFI-291:
-----------------------------
    Description: 
Josh Elser:

- Readme.txt should have License Header
- nbactions.xml is odd in rat exclusions: perhaps we can comment why it is there (for netbeans users)

Andrew Purtell:
- Organizations is wrong in pom.  It says 
<url>http://nifi.incubating.apache.org/</url>
but should be:
<url>http://nifi.incubator.apache.org/</url>

Billie Rinaldi:
The nar and war files deployed in the
orgapachenifi-1022 repository seem to have default LICENSE files that don't
have license info for their bundled dependencies, but they do all have
DEPENDENCIES files listing this information.  I haven't worked with these
dependencies files before.  Are they sufficient for communicating license
information?

Justin Mclean:
Some suggestions:
- Consider having separate licence and notice file for the binary release
- The NOTICE file is a little odd in that while it mentions what licenses effect notice it
doesn't list the software, but they are listed in the license file. Perhaps take a look at
what other projects have done.
As per [1] the source LICENSE should only mention what's bundled in the source bundle and
the binary LICENSE should only mention what's bundled in the binary release.

I think you have the content right (hence my +1)  just that there's no need to mention the
binary parts in the source release LICENSE. Having extra content in license is not as bad
than having missing licences. 

I'd suggest (and it's only a suggestion) having two files (eg LICENSE.src and LICENSE.bin)
in version control and put in right one into each bundle (and rename to LICENSE) as part of
your release process. There are other approaches ie construct each LICENSE file from parts,
but this seems the simplest way to me.

Thanks,
Justin

1. http://www.apache.org/dev/licensing-howto.html#guiding-principle
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org

Jan I:
I am a bit confused about the mangling of license/notice files in respect
of the source/binary releases.
Can I please ask you to make a clear distinction between source and binary
(which is not official ASF release) in the next release.


  was:
Josh Elser:

- Readme.txt should have License Header
- nbactions.xml is odd in rat exclusions: perhaps we can comment why it is there (for netbeans users)

Andrew Purtell:
- Organizations is wrong in pom.  It says 
<url>http://nifi.incubating.apache.org/</url>
but should be:
<url>http://nifi.incubator.apache.org/</url>





> Address findings from 0.0.1 release process
> -------------------------------------------
>
>                 Key: NIFI-291
>                 URL: https://issues.apache.org/jira/browse/NIFI-291
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Tools and Build
>            Reporter: Joseph Witt
>            Assignee: Joseph Witt
>            Priority: Minor
>
> Josh Elser:
> - Readme.txt should have License Header
> - nbactions.xml is odd in rat exclusions: perhaps we can comment why it is there (for netbeans users)
> Andrew Purtell:
> - Organizations is wrong in pom.  It says 
> <url>http://nifi.incubating.apache.org/</url>
> but should be:
> <url>http://nifi.incubator.apache.org/</url>
> Billie Rinaldi:
> The nar and war files deployed in the
> orgapachenifi-1022 repository seem to have default LICENSE files that don't
> have license info for their bundled dependencies, but they do all have
> DEPENDENCIES files listing this information.  I haven't worked with these
> dependencies files before.  Are they sufficient for communicating license
> information?
> Justin Mclean:
> Some suggestions:
> - Consider having separate licence and notice file for the binary release
> - The NOTICE file is a little odd in that while it mentions what licenses effect notice it
> doesn't list the software, but they are listed in the license file. Perhaps take a look at
> what other projects have done.
> As per [1] the source LICENSE should only mention what's bundled in the source bundle and
> the binary LICENSE should only mention what's bundled in the binary release.
> I think you have the content right (hence my +1)  just that there's no need to mention the
> binary parts in the source release LICENSE. Having extra content in license is not as bad
> than having missing licences. 
> I'd suggest (and it's only a suggestion) having two files (eg LICENSE.src and LICENSE.bin)
> in version control and put in right one into each bundle (and rename to LICENSE) as part of
> your release process. There are other approaches ie construct each LICENSE file from parts,
> but this seems the simplest way to me.
> Thanks,
> Justin
> 1. http://www.apache.org/dev/licensing-howto.html#guiding-principle
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
> Jan I:
> I am a bit confused about the mangling of license/notice files in respect
> of the source/binary releases.
> Can I please ask you to make a clear distinction between source and binary
> (which is not official ASF release) in the next release.



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