flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rmetzger <...@git.apache.org>
Subject [GitHub] incubator-flink pull request: Distinguish licenses between source ...
Date Wed, 06 Aug 2014 11:32:57 GMT
GitHub user rmetzger opened a pull request:


    Distinguish licenses between source and binary release

    From this guide: http://www.apache.org/dev/licensing-howto.html
    I understood that we have to do the following changes:
    - Distinguish between the NOTICE / LICENSE file for source releases (top level directory)
and binary releases ( flink-dist/src/main/flink-bin/).
    - The general rule is: There has to be a NOTICE / LICENSE - entry for each bit shipped.
    - I removed most of the contents of the top level NOTICE / LICENSE file, because the source
release does not contain anything from most of the code mentioned (for example Netty, Hadoop,
etc.). The only notices I left inside are for the JavaScript files, that are also contained
in the source release). 
    (This change assumes that we don't have to explicitly state the license/copyright of our
source dependencies. I also assume that we don't have to mention Apache Hadoop or Apache Spark,
from which we copied code into our codebase)
    - I removed the "APPENDIX: How to apply the Apache License to your work." sections from
our LICENSE file.
    This pull request is meant as a suggestion that is up for discussion.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/rmetzger/incubator-flink notice06

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #89
commit cb262ebf808294a1f11f2b27b7d0925cf64f644a
Author: Robert Metzger <rmetzger@apache.org>
Date:   2014-08-06T10:47:21Z

    Distinguish licenses between source and binary release
    [ci skip]


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.

View raw message