Hi Anish,

thank you for sharing, it looks great!

I have only 2 main concerns now:
 - number of notebooks in the plan
 - outreach activities

As far as I understood, you plan for the whole summer includes 4 notebooks
total, ~15 days for each. As all students are expected to have GSoC as a
full-time commitment for the 3 summer months, ~8h a day I would say plan of
creating just 4 notebooks does not immediately sound very ambitious and
challenging. On a very rough estimate: 3 moths = 12 week, so from the top
of my head I would expect a full 40h week per single notebook is kind or
reasonable to start with, and then add some time to get started, etc, etc
so overall at least about 7-8 notebooks is an expectation that I had in
mind and we could discuss.
Please let me know what you think here!

Also, as I mentioned before, as this project is not immediate code
contributions to Zeppelin itself, but more of the outreach project - the
expectations are the you will at least create a blog posts, documenting
your progress along the way.
May be it's worth mentioning in the proposal as well?

P.S please do not forget to submit your proposal to google before the
deadline!

--
Alex

On Wed, Mar 23, 2016 at 12:40 PM, anish singh <anish18...@gmail.com> wrote:

> Hello,
>
> I have added the suggestions to the proposal, please suggest further
> improvements. The common crawl dataset and the Warcbase project were very
> good.
>
> With regard to Helium, as far as I have studied and found, it is meant for
> collaboration where users can download the packaged code and run as an
> application inside Zeppelin. Please consider the fact that I will be
> working alone on the datasets for the project, there will be no
> collaborators. So I think, Helium can be used by writing Helium
> applications on my machine or by using existing Helium applications for the
> notebooks to be created, to add custom visualizations and custom features
> to the notebooks. Please correct me if I'm wrong.
>
> Meanwhile, I'm trying to run Helium sample applications inside Zeppelin
> notebooks.
>
> Thanks,
> Anish.
>
>
> On Mon, Mar 21, 2016 at 9:04 AM, anish singh <anish18...@gmail.com> wrote:
>
> > Hello,
> >
> > Thanks Alex for all the suggestions, I will add them to the proposal and
> > have it ready for a second review.
> > Sorry for the late response.
> >
> > Thanks,
> > Anish.
> >
> > On Sat, Mar 19, 2016 at 8:37 PM, Alexander Bezzubov <b...@apache.org>
> > wrote:
> >
> >> Hi Anish,
> >>
> >> your proposal looks great, but we need to add a few details, in order to
> >> make it awesome.
> >>
> >> I.e you do not mention which interpreters would be used for the notebook
> >> implementations? Two most obvious candidates would be Spark, which you
> >> already is familiar with and a Flink, which might require you to plan
> for
> >> a
> >> few extra days to get started with.
> >>
> >> With each of them (i.e Spark) there are advanced features like GraphX
> and
> >> MLlib that might be interesting to showcase in those notebooks as wll,
> so
> >> having few words about your plans for that matter would be nice.
> >>
> >> Showcasing Helium capabilities would be very valuable addition to your
> >> propo
> >> sal as well, so please check the Moon's explanation carefully and do not
> >> hesitate to ask further questions about it here, in a separate thread.
> >>
> >> I have posted comments in the proposal doc on wiki, please feel free to
> >> remove and address each of them and then post back here in this thread
> for
> >> another round of reviews!
> >>
> >> --
> >> Alex
> >>
> >>
> >> On Fri, Mar 18, 2016 at 1:59 AM, moon soo Lee <m...@apache.org> wrote:
> >>
> >> > Hi Anish,
> >> >
> >> > Apologies for late response.
> >> > Regarding Helium functionality, it's about pluggable module of
> Zeppelin
> >> and
> >> > loading them on the fly.
> >> >
> >> > Initial helium proposal [1] tried to make any user code packaged and
> >> runs
> >> > on notebook. Just like we import library and run it. Implementation is
> >> > working in progress here [2].
> >> > [3] is umbrella issue for Helium, which is includes package registry.
> >> Also
> >> > extends original proposal so Interpreter and NotebookRepo can be
> >> > distributed and installed from this package registry.
> >> >
> >> > Let me know if you have any more questions.
> >> >
> >> > Thanks,
> >> > moon
> >> >
> >> > [1]
> >> https://cwiki.apache.org/confluence/display/ZEPPELIN/Helium+proposal
> >> > [2] https://issues.apache.org/jira/browse/ZEPPELIN-732
> >> > [3] https://issues.apache.org/jira/browse/ZEPPELIN-533
> >> >
> >> >
> >> >
> >> > On Thu, Mar 17, 2016 at 9:39 AM anish singh <anish18...@gmail.com>
> >> wrote:
> >> >
> >> > > Hello,
> >> > >
> >> > > Please suggest improvements in the proposal draft at [0]. Also, any
> >> > > references/hints about how to use Helium functionality in the
> project
> >> and
> >> > > links to any documentation about Helium would be very helpful.
> >> > >
> >> > > 0.
> >> > >
> >> > >
> >> >
> >>
> https://cwiki.apache.org/confluence/display/ZEPPELIN/Google+Summer+Of+Code+2016
> >> > >
> >> > > Thanks,
> >> > > Anish.
> >> > >
> >> > > On Wed, Mar 16, 2016 at 8:07 AM, Alexander Bezzubov <b...@apache.org
> >
> >> > > wrote:
> >> > >
> >> > > > Hi Anish,
> >> > > >
> >> > > > I did a quick glance your proposal last week and it looks good,
> but
> >> I
> >> > > will
> >> > > > do another pass today and let you know.
> >> > > >
> >> > > > Meanwhile, Moon, could you please provide more information and
> >> answer
> >> > the
> >> > > > question about Helium? I feel like the more further project
> >> features it
> >> > > > touches\have incorporated, like Helium, the stronger the proposal
> >> would
> >> > > be.
> >> > > >
> >> > > > --
> >> > > > Alex.
> >> > > >
> >> > > > On Tue, Mar 8, 2016 at 11:14 PM, anish singh <
> anish18...@gmail.com>
> >> > > wrote:
> >> > > >
> >> > > > > Hello,
> >> > > > >
> >> > > > > I have written the text proposal on [0]. Please review and
> suggest
> >> > > > changes.
> >> > > > >
> >> > > > > 0.
> >> > > > >
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
> https://cwiki.apache.org/confluence/display/ZEPPELIN/Google+Summer+Of+Code+2016
> >> > > > >
> >> > > > > Thanks,
> >> > > > > Anish.
> >> > > > >
> >> > > > > On Tue, Mar 8, 2016 at 7:36 PM, Alexander Bezzubov <
> >> b...@apache.org>
> >> > > > wrote:
> >> > > > >
> >> > > > > > Hi Anish,
> >> > > > > >
> >> > > > > > you are right, keeping discussion threaded and focused around
> >> one
> >> > > > subject
> >> > > > > > is crucial for productive usage of mailing lists, including
> >> search
> >> > > > > through
> >> > > > > > archives, etc.
> >> > > > > >
> >> > > > > > I have just granted you the permissions, updated GSoC wiki
> page
> >> [0]
> >> > > and
> >> > > > > > added a sub-page for your proposal draft [1] - please feel
> free
> >> to
> >> > > edit
> >> > > > > it
> >> > > > > > by posting your proposal text there.
> >> > > > > > Hope in the same way we can keep track of all other
> >> > > > participants\proposal
> >> > > > > > drafts in [0].
> >> > > > > >
> >> > > > > >
> >> > > > > >  0.
> >> > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
> https://cwiki.apache.org/confluence/display/ZEPPELIN/Google+Summer+Of+Code+2016
> >> > > > > >  1.
> >> > > > > >
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=62686678
> >> > > > > >
> >> > > > > > --
> >> > > > > > Alex
> >> > > > > >
> >> > > > > >
> >> > > > > > On Tue, Mar 8, 2016 at 8:24 PM, anish singh <
> >> anish18...@gmail.com>
> >> > > > > wrote:
> >> > > > > >
> >> > > > > > > Hello,
> >> > > > > > >
> >> > > > > > > My(Anish) user name on the cwiki is : anish18sun
> >> > > > > > >
> >> > > > > > > I realize I should have sent the user name in this thread,
> >> > instead
> >> > > > of a
> >> > > > > > > separate mail that I earlier wrote.
> >> > > > > > >
> >> > > > > > > Thanks for the suggestion about the format, I will abide by
> >> it. I
> >> > > > guess
> >> > > > > > if
> >> > > > > > > I'm allowed the edit rights at the cwiki, I will be allowed
> to
> >> > > > > > write/upload
> >> > > > > > > a plain editable text file at [0].
> >> > > > > > >
> >> > > > > > > Also, google docs may make it inconvenient for someone to
> >> click a
> >> > > > link
> >> > > > > > and
> >> > > > > > > go to a separate page.
> >> > > > > > >
> >> > > > > > > 0.
> >> > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
> https://cwiki.apache.org/confluence/display/ZEPPELIN/Google+Summer+Of+Code+2016
> >> > > > > > >
> >> > > > > > > Thanks,
> >> > > > > > > Anish.
> >> > > > > > >
> >> > > > > > > On Tue, Mar 8, 2016 at 2:13 PM, Alexander Bezzubov <
> >> > b...@apache.org
> >> > > >
> >> > > > > > wrote:
> >> > > > > > >
> >> > > > > > > > Hi Anish,
> >> > > > > > > >
> >> > > > > > > > what is your wiki username?
> >> > > > > > > >
> >> > > > > > > > Also how do you think, would it make sense to post the
> first
> >> > > > propasal
> >> > > > > > > draft
> >> > > > > > > > in the format that is easy to change/collaborate on,
> >> instead of
> >> > > > pdf?
> >> > > > > > > >
> >> > > > > > > > Initial suggestion of having it in plain-text wiki was
> >> exactly
> >> > > for
> >> > > > > that
> >> > > > > > > > purpose.
> >> > > > > > > >
> >> > > > > > > > Another good option could be google docs with permissions
> >> set
> >> > up
> >> > > so
> >> > > > > > > anyone
> >> > > > > > > > with the link can comment/"suggest an edit". Then we could
> >> just
> >> > > > post
> >> > > > > a
> >> > > > > > > link
> >> > > > > > > > on the wiki.
> >> > > > > > > >
> >> > > > > > > > Please let me know what you think.
> >> > > > > > > >
> >> > > > > > > > --
> >> > > > > > > > Alex
> >> > > > > > > >
> >> > > > > > > > On Tue, Mar 8, 2016, 15:57 anish singh <
> >> anish18...@gmail.com>
> >> > > > wrote:
> >> > > > > > > >
> >> > > > > > > > Hello,
> >> > > > > > > >
> >> > > > > > > > Kindly let me know if I've been granted the edit rights on
> >> [0].
> >> > > > > > > >
> >> > > > > > > > I opened
> >> > > > > > > > [0] and tried to upload the proposal pdf file but the page
> >> > asked
> >> > > me
> >> > > > > to
> >> > > > > > > take
> >> > > > > > > > permission first and no upload happened. I also found an
> >> option
> >> > > to
> >> > > > > edit
> >> > > > > > > > labels but I didn't create one because it was mentioned in
> >> the
> >> > > help
> >> > > > > > pages
> >> > > > > > > > that labels were created as references to attachments,
> >> blogs or
> >> > > > other
> >> > > > > > > > pages, so it would be pointless to create a label without
> >> any
> >> > > file
> >> > > > to
> >> > > > > > be
> >> > > > > > > > referenced.
> >> > > > > > > >
> >> > > > > > > > 0.
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
> https://cwiki.apache.org/confluence/display/ZEPPELIN/Google+Summer+Of+Code+2016
> >> > > > > > > >
> >> > > > > > > > Thanks,
> >> > > > > > > > Anish.
> >> > > > > > > >
> >> > > > > > > > On Mon, Mar 7, 2016 at 7:33 PM, Alexander Bezzubov <
> >> > > b...@apache.org
> >> > > > >
> >> > > > > > > wrote:
> >> > > > > > > >
> >> > > > > > > > > Hi Anish,
> >> > > > > > > > >
> >> > > > > > > > > that sounds great. You are right, notebooks at the end
> are
> >> > just
> >> > > > > .json
> >> > > > > > > > files
> >> > > > > > > > >
> >> > > > > > > > > A very quick feedback - apache mailing list do not
> >> tolerate
> >> > > > > > > attachments,
> >> > > > > > > > so
> >> > > > > > > > > if you could let me know your username on a wiki [0]
> I'll
> >> be
> >> > > glad
> >> > > > > to
> >> > > > > > > > grant
> >> > > > > > > > > you edit rights, so you could post your proposal draft
> >> there
> >> > > [1].
> >> > > > > > > > >
> >> > > > > > > > >  0.
> >> > > > > >
> >> https://cwiki.apache.org/confluence/display/ZEPPELIN/Zeppelin+Home
> >> > > > > > > > >  1.
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
> https://cwiki.apache.org/confluence/display/ZEPPELIN/Google+Summer+Of+Code+2016
> >> > > > > > > > >
> >> > > > > > > > > --
> >> > > > > > > > > Alex
> >> > > > > > > > >
> >> > > > > > > > > On Mon, Mar 7, 2016 at 9:54 PM, anish singh <
> >> > > > anish18...@gmail.com>
> >> > > > > > > > wrote:
> >> > > > > > > > >
> >> > > > > > > > > > Hello,
> >> > > > > > > > > > Attached is a first draft of proposal for Zeppelin-684
> >> > > > (creating
> >> > > > > > > > > > notebooks). Please review and suggest changes.
> >> > > > > > > > > >
> >> > > > > > > > > > Zeppelin is up and running on my machine. As far as I
> >> have
> >> > > > > grasped,
> >> > > > > > > the
> >> > > > > > > > > > changes in the different notebooks for the various
> >> datasets
> >> > > > will
> >> > > > > be
> >> > > > > > > at
> >> > > > > > > > > the
> >> > > > > > > > > > json level. I have gained a fair understanding of
> >> Zeppelin
> >> > > from
> >> > > > > the
> >> > > > > > > > > > internet resources and read about Helium as well.
> >> > References
> >> > > to
> >> > > > > > more
> >> > > > > > > > > > resources about Zeppelin and about how we might
> include
> >> > > Helium
> >> > > > in
> >> > > > > > > > > creating
> >> > > > > > > > > > the notebooks would be appreciated.
> >> > > > > > > > > >
> >> > > > > > > > > > It would be a great help if I could be provided with
> >> more
> >> > > > > resources
> >> > > > > > > > about
> >> > > > > > > > > > Helium, other than the general description and the
> demo
> >> > > videos,
> >> > > > > so
> >> > > > > > > that
> >> > > > > > > > I
> >> > > > > > > > > > may understanding its integration with the project in
> >> > > general.
> >> > > > > > > > > >
> >> > > > > > > > > > Presently, I will do more of json and attempt to
> create
> >> a
> >> > > > sample
> >> > > > > > > > > notebook.
> >> > > > > > > > > >
> >> > > > > > > > > > Thanks,
> >> > > > > > > > > > Anish.
> >> > > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
> >
> >
>

Reply via email to