Thanks for the feedback. 1) What do we expect to have on each page?
I expect each interpreter have their own descriptions about how they work, how to configure, how to use, examples and tips. 2) This looks like we are moving more and more to include all interpreters in the core of zeppelin, is this is where we want to go. I vote +1 for a smaller distribution with optional plugin support. most users will not use all of these backend interpreters together. This is out of this PR's scope. but I think each interpreter page can have information about externally managed interpreter, how to find, how to install them, etc. So at least it can be helpful. Best, moon On Sun, Aug 9, 2015 at 5:20 AM IT CTO <[email protected]> wrote: > +1 for angular documentation, did not test the code but the docs looks > informative. > As for the interpreter docs - > 1) What do we expect to have on each page? > 2) This looks like we are moving more and more to include all interpreters > in the core of zeppelin, is this is where we want to go. I vote +1 for a > smaller distribution with optional plugin support. most users will not use > all of these backend interpreters together. > > Eran > > On Sun, Aug 9, 2015 at 11:01 AM tzolov <[email protected]> wrote: > > > Github user tzolov commented on the pull request: > > > > > > > https://github.com/apache/incubator-zeppelin/pull/188#issuecomment-129132861 > > > > +1 > > > > > > --- > > 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. > > --- > > >
