Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[ease-dev] GSoC 2017

Hi students,

student application just opened for this year. As there is quite some interest in EASE projects I would like to clarify the proceedings from my side. Although we have multiple proposals open on the ideas site, I will only have time to mentor one student, so it might not be sufficient to be the only one interested in a topic, but also to provide the strongest appearance from all applicants for EASE topics.

To help you a little bit I would like to provide some guidelines and requirements:

* next to your proposal you need to have successfully fixed a bug in EASE. This requires to cehck out the sources, sign up on bugzilla, raise a bug, fix it and contribute the patch via gerrit. I do not care much about what you fix. Might be a typo in some javadocs. The main reason to do this is to prove that you know how to work with the required tools.

* provide a clear idea what you are going to deliver/implement and what not. Stating what can be expected helps both of us when it comes to evaluations.

* provide timelines when content shall be ready. I suggest to provide milestones for your deliverables. Have at max periods of 2 weeks to finish work packages. To move your stuff to the master branch topics should be consistent and working. We cannot push unfinished/broken parts of code to the master branch!

* have your task completed 2 weeks before the final evaluation. This gives you a small buffer in case things get more complicated than you think. Even if you are willing to finish topics after the final evaluation they will not be counted!

* you need to file a short summary of your work each week on this list.

* remember that I might not be responsive on the instant, so plan your work accordingly and try to raise questions some time before you have to start implementing solutions.

* code is not everything. You are expected to deliver unit tests and documentation (mainly javadoc) for your code.


if you have questions to these guidelines, please let me know

happy coding
Christian



Back to the top