GitHub user felixcheung opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/675
[ZEPPELIN-632][DOC] Document steps to contribute a new interpreter
### What is this PR for?
Instead of going through a list of items one by one in PR review, we should
have a checklist of TODOs for a potential interpreter contributor to review and
follow
### What type of PR is it?
Documentation
### Todos
* [x] - Update doc
### Is there a relevant Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-632
### How should this be tested?
N/A
### Screenshots (if appropriate)
N/A
### Questions:
* Does the licenses files need update? No
* Is there breaking changes for older versions? No
* Does this needs documentation? This is.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/felixcheung/incubator-zeppelin
createinterpreterdoc
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-zeppelin/pull/675.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 #675
----
commit 78d912787a03f60779a3c1903f66beee7aa94bb9
Author: Felix Cheung <[email protected]>
Date: 2016-01-26T05:33:10Z
doc update
----
---
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.
---
