[Zeppelin-684][GSoC - 2016] Proposal First Draft

2016-03-07 Thread anish singh
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

Re: [Zeppelin-684][GSoC - 2016] Proposal First Draft

2016-03-07 Thread Alexander Bezzubov
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

Re: [Zeppelin-684][GSoC - 2016] Proposal First Draft

2016-03-07 Thread anish singh
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 pa

Re: [Zeppelin-684][GSoC - 2016] Proposal First Draft

2016-03-08 Thread Alexander Bezzubov
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 go

Re: [Zeppelin-684][GSoC - 2016] Proposal First Draft

2016-03-08 Thread anish singh
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 allow

Re: [Zeppelin-684][GSoC - 2016] Proposal First Draft

2016-03-08 Thread Alexander Bezzubov
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] - plea

Re: [Zeppelin-684][GSoC - 2016] Proposal First Draft

2016-03-08 Thread anish singh
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 wrote: > Hi Anish, > > you are right, keeping discussion thre

Re: [Zeppelin-684][GSoC - 2016] Proposal First Draft

2016-03-15 Thread Alexander Bezzubov
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,

Re: [Zeppelin-684][GSoC - 2016] Proposal First Draft

2016-03-19 Thread anish singh
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 T

Re: [Zeppelin-684][GSoC - 2016] Proposal First Draft

2016-03-19 Thread moon soo Lee
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 p

Re: [Zeppelin-684][GSoC - 2016] Proposal First Draft

2016-03-19 Thread Alexander Bezzubov
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 req

Re: [Zeppelin-684][GSoC - 2016] Proposal First Draft

2016-03-20 Thread anish singh
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 wrote: > Hi Anish, > > your proposal looks great, but we need to add a few details,

Re: [Zeppelin-684][GSoC - 2016] Proposal First Draft

2016-03-22 Thread anish singh
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 a

Re: [Zeppelin-684][GSoC - 2016] Proposal First Draft

2016-03-23 Thread Alexander Bezzubov
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-tim

Re: [Zeppelin-684][GSoC - 2016] Proposal First Draft

2016-03-23 Thread anish singh
Hello, Thanks for the suggestions. I have mentioned in the proposal that creation of four notebooks is not an upper bound, definitely I will create more notebooks than just the 4 mentioned once I get familiar with the work in the starting days. I will try my best to fulfill the expectations of 7-8

Re: [Zeppelin-684][GSoC - 2016] Proposal First Draft

2016-04-23 Thread anish singh
Hello, I am extremely thankful to the community for selecting me for the project [Zeppelin Notebooks]. I will work as hard as possible to accomplish the terms laid down in my proposal. Thanks, Anish. On Thu, Mar 24, 2016 at 8:23 AM, anish singh wrote: > Hello, > > Thanks for the suggestions. I