Re: [ease-dev] Jupyter Kernels

[Christian Pontesegger <christian.pontesegger@xxxxxx>]

Hi Martin,

the current 'community bonding' period is for preparing your GSoC project. It is about collecting necessary information, getting in touch with the eclipse community, doing tutorials and learn the skills required for your assignment. So it is perfectly ok to read jupyter documentation. Please keep in mind to post weekly updates of what you are doing on this list regarding our rules for this year. The first status report is expected this week. Best briefly explain which topics you are investigating.

It is also a good idea to start preparing bug reports for your assignment so we can keep track of all work packages and your progress on bugzilla. Further your project is closely coupled to the work of Jonah, as you might need to work with external interpreters. So close alignment with him on this mailing list will be crucial for your success.

Regarding time scale I would prefer to add tests during the whole assignment as your feature implementations are contributed. Do not start to write tests after your implementation is done. And remember that code reviews take some time, so having the final code ready 2 weeks before 'pencils down' might not be a vast amount of spare time.

cheers
Christian

On 05/02/2016 09:55 AM, Martin Klösch wrote:

Hi,

As some of you might have heard already, I was selected for this year's GSOC program. Congratulations to Varun on being selected as well. I am sure that we can get some great stuff done this summer!

Since my project relies on incremental implementation steps, I am a little hesitant to post exact dates for my milestones. My basic plan looks like this though:

I will use the time until the coding phase starts to read up on more details about Jupyter so I am ready to immediately start implementation once the program starts.

I want to get the basic code execution feature done until the midterm evaluations. This is already a big block of my project and will be a good foundation to continue my work.

I want to have the actual functionality available about 2 weeks before the final submission. This should give us enough time to add some additional tests, check the documentation and deliver a great final result...

I will probably be very busy the last week of June due to university but will always have access to mail should something urgent arise.

The weekly chats seem like a great idea. There might be some points where your feedback would be of great help, especially when it comes to defining interfaces for you to use in modules, etc.. I will let you know on the mailing list about my progress and whenever it seems like your input would be of (even more) help.

Looking forward to another great project,
Best regards,
Martin

_______________________________________________
ease-dev mailing list
ease-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ease-dev