GSoC 2018 Student Application Template

(The page is not complete. Changes may be required.)

PyDy's recommended 2016 Google Summer of Code application template

Note: your final application must be submitted at https://summerofcode.withgoogle.com, so do not worry too much about the formatting of your application on the wiki, as you will have to reformat it there. You should not be too concerned with the formatting in the Google site either, as we understand that the text editor there is not the best for making things look nice formatting-wise. We are more concerned with the content of your application, and that it is readable.

Title

We have accept students under umbrella organizations, please start the title of your proposal with "PyDy - ", like "PyDy - Linearization Routines for Equations of Motion". Please use a succinct title that describes your proposal. Do not include the words "GSoC", "2018", or your name in the proposal title.

You the person

Please put this information at the top of your proposal.

• Your full name
• University / current enrollment
• Short bio / overview of your background
• How can we contact you (email, GitHub username, etc.)? This information will help us associate all of your various usernames with you.
  • Email
  • GitHub username
  • Any other user name you want us to know about

Also, please use your full real name in your profile, so that it appears in the proposal list.

You the programmer

In your project proposal let us know about your programming experience. Don't worry if you don't know SymPy, PyDy, or git. Many of our students start fresh. We will teach you what you need to know.

• What platform do you use to code? What editor do you prefer and why?
• What is your experience programming? Tell us about something you have created.
• What is your experience with Python? What are your favorite features of Python that are lacking in most other common programming languages? What, in your opinion, is the most advanced Python language feature or standard library functionality that you have used?
• What is your favorite feature of PyDy? What projects have you used it for? Demonstrate it here with a cool example.
• Have you ever used git or another version control system?

You and your project

Answer the following questions in your proposal:

• What do you want to achieve?
• What excites you about this project? Why did you choose it?
• What qualifications do you have to implement your idea? For example, if you are implementing another method for finding EoMs, what courses have you taken on the subject. If you are improving visualization methods, what other creations have you made? Why are you suited to work on this project?
• What have other people done on this idea? Has it been implemented before? (hint: it's probably been suggested already) Are there any papers or blog posts about it?
• How much time do you plan to invest in the project before, during, and after the Summer of Code? (we expect full time 40h/week during GSoC, but better make this explicit) If you plan to take any vacations over the summer, let us know about it here.
• Please provide a schedule of how this time will be spent on sub-tasks of the project over the period of the summer. While this is only preliminary, we will use it to help monitor your progress throughout the program. Also understand that during the project you will issue weekly progress reports against that plan on your blog.
• In planning your project, it is good to note where along the way you could formulate a pull request (similar to developmental milestones). These would be points where you can have a self contained and well documented and tested piece of functionality. Doing this at several points during the summer helps to keep branch merges reasonable and code reviews manageable. A big code dump at the end of the summer will likely be hard to review and merge before the project deadline.
• Do not verbatim copy text from the ideas page, or from other people's discussions about your project, but rewrite it in your own words. If you include any significant text or code from another source in your application, it must be accompanied with a proper citation. All papers or references that you use or plan to use must also be cited. Put all this in a "References" section at the bottom of your application.

You do not need to format your application as a question/answer format for the above questions, but we expect to see all of the above questions answered in your application somewhere. The Q/A format will probably be easiest.

Patch requirement

Please have a quick link to whatever patch you have submitted and was accepted and associated Github or mailing list discussions. See the patch requirements on the student instructions page here: GSoC-2018-Student-Application-Instructions

Template borrowed from our good friends at SymPy (SymPy).