-
Notifications
You must be signed in to change notification settings - Fork 80
Google Summer of Code 2019 Student Application
-
Contact information. Please provide your email address, GitHub username, and approximate physical location.
-
Why do you like Ruby, and why do you want to work on SciRuby?
-
What do you like about science and why? What area do you like best?
-
Describe your experience with the following: Ruby, C, C++, other languages.
-
Describe your educational background (school, degree plan, major, past degrees, research area, publications, etc.).
-
Have you offered any pull requests for SciRuby or contributed in other ways? Please provide links, if possible. Past contributions are required, and must be in the form of code. Documentation contributions are also beneficial.
-
What other commitments do you have this summer aside from GSoC? What obstacles do you foresee this summer as far as contributing the full forty hours per week during the GSoC period?
-
Are you planning any fun vacations this summer?
-
How many classes are you taking this summer?
-
Do you have any other employment this summer?
-
Please talk a bit about any past GSoC projects in which you have participated. If you've done GSoC before, how could we reach your mentor(s)?
-
Please propose a project you would like to work on. Successful proposals will require advanced planning, communication with the project administrators and mentors, and likely a great deal of research on specific methods for achieving your project goals (e.g., what algorithms will you use? What frameworks?). A good place to start is the Ideas Page. You should also consider lurking on our IRC channel (#sciruby on FreeNode), various Gitter channels (check repo pages) and slack (https://sciruby-slack.herokuapp.com/). Participation in listserv discussions is strongly recommended.
-
Please provide a specific timeline for your project from application period until pencils-down. What benchmarks will you set for yourself? The greater the detail on this question and the previous, the better.
-
What is one long-term vision for something you'd like scientific software to be able to do. Think big picture, not necessarily realistic in the short term.
-
What are your hobbies, aside from coding? Tell us a little about yourself that isn't reflected in the rest of your application. What do you want to do with your life (if you have any idea)?
-
What else do you think we should have asked but didn't? Propose a question of your own and answer it here.