GSoC 2016 application: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
Line 25: | Line 25: | ||
Once a student is selected, the mentor will work with them to come up with a detailed summer timeline, including clear expectations for progress by the midterm and final evaluation periods. | Once a student is selected, the mentor will work with them to come up with a detailed summer timeline, including clear expectations for progress by the midterm and final evaluation periods. | ||
During the summer, mentors will check in with students at least weekly to make sure they are staying on schedule and help with any obstacles that might arise. Students are also expected to regularly update their mentors and the Octave maintainers community on their progress via e-mails and blog posts. | |||
=== How will you get your students involved in your community during GSoC? === | |||
Students will be urged to participate on our IRC channel and mailing list. We will set clear expectations on the minimum frequency of email progress updates, typically every two to three days. Students will also set up a blog for longer, weekly, updates which is aggregated at http://planet.octave.org | Students will be urged to participate on our IRC channel and mailing list. We will set clear expectations on the minimum frequency of email progress updates, typically every two to three days. Students will also set up a blog for longer, weekly, updates which is aggregated at http://planet.octave.org | ||
Line 30: | Line 34: | ||
Everything should be completely open. Almost all interactions with the student should be public, e.g. contacting the mentor should happen in the public IRC channel or copy the maintainers mailing list. | Everything should be completely open. Almost all interactions with the student should be public, e.g. contacting the mentor should happen in the public IRC channel or copy the maintainers mailing list. | ||
Finally, we organize a developers' summit, OctConf, during the summer and have in previous years provided support for GSoC students to attend and present. This strengthens relationships between community members and the new students. | |||
=== How will you keep students involved with your community after GSoC? === | === How will you keep students involved with your community after GSoC? === | ||
We will typically merge their code into our codebase during or soon after the summer. GNU Octave is a project with many tester-users who give constant feedback on new features and report bugs. As participants in the mailing lists and bug tracker, students get the feeling of doing something that is useful to the community from the very start. | |||
Many of our GSoC students use Octave during the academic year or in their professional careers. As such, they are prone to stay involved with its development, even if at a lower level than during the summer. | |||
Several previous SoC students have continued with regular contributions to GNU Octave, and most remain available to help us with any problems related to the code they wrote for the project. | |||
=== Has your org been accepted as a mentoring org in Google Summer of Code before? === | === Has your org been accepted as a mentoring org in Google Summer of Code before? === | ||
Yes. | |||
=== Are you part of a foundation/umbrella organization? === | === Are you part of a foundation/umbrella organization? === | ||
Yes, we are affiliated with GNU. | |||
=== What year was your project started? === | === What year was your project started? === | ||
The main development of Octave began in 1992, with Version 1.0 released in 1994. | |||
=== Organization ID === | === Organization ID === | ||
Line 45: | Line 63: | ||
GNU Octave | GNU Octave | ||
=== Tags === | === Tags === | ||
Line 75: | Line 77: | ||
Feed: http://planet.octave.org/atom.xml | Feed: http://planet.octave.org/atom.xml | ||