GitHub user corneadoug opened a pull request:

    https://github.com/apache/zeppelin/pull/1406

    [ZEPPELIN-1414] Remove CONTRIBUTING.md files

    ### What is this PR for?
    Following the PR #1356, we now have the contribution documentation to on 
Apache Zeppelin Website.
    
    We can now remove the contributing files from the repository, and replace 
the links to that documentation.
    
    
    ### What type of PR is it?
    Documentation
    
    ### What is the Jira issue?
    https://issues.apache.org/jira/browse/ZEPPELIN-1414
    
    ### How should this be tested?
    Just check if there is other CONTRIBUTING.md files and if there is other 
links to replace
    
    ### Questions:
    * Does the licenses files need update? No
    * Is there breaking changes for older versions? No
    * Does this needs documentation? No


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

    $ git pull https://github.com/corneadoug/incubator-zeppelin ZEPPELIN-1414

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

    https://github.com/apache/zeppelin/pull/1406.patch

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

    This closes #1406
    
----
commit 194fe846df391c684314a43cf39a8654367b6211
Author: Damien CORNEAU <[email protected]>
Date:   2016-09-06T06:32:00Z

    Remove contributing files

commit 1168a898ae26b2234af399f4227bafb19a77838d
Author: Damien CORNEAU <[email protected]>
Date:   2016-09-06T06:32:23Z

    Remove contributing files from RAT

commit 3271d54dd45a0588b780101d06f6e041296efc30
Author: Damien CORNEAU <[email protected]>
Date:   2016-09-06T06:33:15Z

    Make links to contribution material point to the website

----


---
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 [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to