You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zeppelin.apache.org by AhyoungRyu <gi...@git.apache.org> on 2017/03/29 07:58:27 UTC

[GitHub] zeppelin pull request #2202: [Minor][ZEPPELIN-2328] Separate Helium related ...

GitHub user AhyoungRyu opened a pull request:

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

    [Minor][ZEPPELIN-2328] Separate Helium related docs from 'Contribution' section

    ### What is this PR for?
    Actually writing "Visualization", "Spell" or "Application" type of Helium package is not a direct contribution to Zeppelin. So i created "Helium Framework" section and moved "Writing Zeppelin Visualization", "Writing Zeppelin Spell", and "Writing Zeppelin Application" under "Helium Framework" from "Contribution".
    
    ### What type of PR is it?
    Documentation
    
    ### What is the Jira issue?
    [ZEPPELIN-2328](https://issues.apache.org/jira/browse/ZEPPELIN-2328)
    
    ### Screenshots (if appropriate)
     - Before 
    <img src="https://cloud.githubusercontent.com/assets/10060731/24444171/743d8c7e-14a0-11e7-8a10-ec02596d2a19.png" width="300px">
    
     - After 
    <img src="https://cloud.githubusercontent.com/assets/10060731/24444245/aecfe274-14a0-11e7-8488-99086b1db415.png" width="300px">
    
    ### 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/AhyoungRyu/zeppelin ZEPPELIN-2328

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

    https://github.com/apache/zeppelin/pull/2202.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 #2202
    
----
commit 6185fcd45c47ade3f0f36fd7918a56c80bd774eb
Author: AhyoungRyu <fb...@hanmail.net>
Date:   2017-03-29T07:50:32Z

    Separate Helium related docs from 'Contribution' section

----


---
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.
---

[GitHub] zeppelin issue #2202: [Minor][ZEPPELIN-2328] Separate Helium related docs fr...

Posted by AhyoungRyu <gi...@git.apache.org>.
Github user AhyoungRyu commented on the issue:

    https://github.com/apache/zeppelin/pull/2202
  
    Thanks @1ambda for the confirmation!
    Merge into master if there are no more comments on this. 


---
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.
---

[GitHub] zeppelin pull request #2202: [Minor][ZEPPELIN-2328] Separate Helium related ...

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

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


---
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.
---

[GitHub] zeppelin issue #2202: [Minor][ZEPPELIN-2328] Separate Helium related docs fr...

Posted by 1ambda <gi...@git.apache.org>.
Github user 1ambda commented on the issue:

    https://github.com/apache/zeppelin/pull/2202
  
    Great!


---
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.
---