Google Summer of Code 2016
08 Mar 2016MDAnalysis has been accepted as a sub-org of the Python software foundation, PSF, for Google Summer of Code 2016. If you are interested in working with us this summer as a student read the advice and links below and write to us on the mailing list.
We are looking forward to all applications from interested students (undergraduates and graduates).
The application window deadline is March 25, 2016 at 12:00 (MST). As part of the application process you must complete all the steps listed under Information for Students and familiarize yourself with Google Summer of Code 2016. Apply as soon as possible.
Project Ideas
We have listed several possible projects for you to work on on our wiki. Each project is rated with a difficulty and lists the possible mentors for it.
Alternatively, if you have another idea about a project please write to us on the developer list and we can discuss it there.
Information for Students
You must meet our own requirements and the PSF requirements if you want to be a student with MDAnalysis this year (read all the docs behind these links!). You must also meet the eligibility criteria.
As a start to get familiar with MDAnalysis and open source development you should follow these steps:
Complete the Tutorial
We have a tutorial explaining the basics of MDAnalysis. You should go through the tutorial at least once to understand how MDAnalysis is used.
Introduce yourself to us
Introduce yourself on the mailing list. Tell us what you plan to work on during the summer or what you have already done with MDAnalysis
Close an issue of MDAnalysis
You must have at least one commit in the development branch of MDAnalysis in order to be eligible, i.e.. you must demonstrate that you have been seriously engaged with the MDAnalysis project.
We have a list of easy bugs to work on in our issue tracker on GitHub. We also appreciate if you write more tests or update/improve our documentation. To start developing for MDAnalysis have a look at our guide for developers and write us on the mailing list if you have more questions about setting up a development environment.