1,860
edits
GSoC 2015 application: Difference between revisions
Add categories.
(Add categories.) |
|||
| (7 intermediate revisions by 2 users not shown) | |||
| Line 53: | Line 53: | ||
JordiGH | JordiGH | ||
=== If you chose "veteran" in the | === If you chose "veteran" in the checkbox, please summarize your involvement in Google Summer of Code and the successes and challenges of your participation. Please also list your pass/fail rate for each year. === | ||
Our first year in GSoC as an independent organization was 2014 and we had 3 participating students, who pursued work in approximate matrix factorization, efficient handling of sparse matrices, and finite element methods for solving partial differential equations. While there were some challenges related to mentor availability in one case, all 3 of the students passed and made contributions which have been incorporated into Octave. We also had one student enrolled under [http://sophia.estec.esa.int/socis/ ESA Summer of Code in Space (SoCiS)] who successfully improved Octave's ordinary differential equation solvers. | Our first year in GSoC as an independent organization was 2014 and we had 3 participating students, who pursued work in approximate matrix factorization, efficient handling of sparse matrices, and finite element methods for solving partial differential equations. While there were some challenges related to mentor availability in one case, all 3 of the students passed and made contributions which have been incorporated into Octave. We also had one student enrolled under [http://sophia.estec.esa.int/socis/ ESA Summer of Code in Space (SoCiS)] who successfully improved Octave's ordinary differential equation solvers. | ||
In addition, we also mentored GSoC and SoCiS students on the years 2011, 2012, and 2013 under the umbrella of the GNU project. In total, counting both GSoC and SoCiS, we have mentored a total of 16 students. | In addition, we also mentored GSoC and SoCiS students on the years 2011, 2012, and 2013 under the umbrella of the GNU project. In total, counting both GSoC and SoCiS, we have mentored a total of 16 students. Students working with us have made valuable contributions which are live and in our main source tree. These contributions improving Octave's usability and functionality in many different areas, from low-level instrument control and just-in-time compilation, to new algorithms for processing N dimensional images and least-squares spectral analysis. The Octave GUI started as a GSoC project and its further refinement has been the major feature of the last Octave release. Several of the students continued their involvement with the project and the community, four have become core developers, and two have become mentors for new students. | ||
The challenges include managing very diverse problem domains and finding people who are competent in all of them. We have not had trouble keeping students interested, although we have seen lulls in their productive output at times, which were always thankfully remedied with a little prodding. | |||
Summarizing, we have previously mentored a total of 16 summer students, all of them having educational experiences which created useful code for the project and community. Because of this, we believe that Octave is a suitable organization for GSoC with the capability to mentor students and benefit from their contribution. | |||
=== If you chose "new" in the dropdown above, have you applied in the past? If so, for what year(s)? === | === If you chose "new" in the dropdown above, have you applied in the past? If so, for what year(s)? === | ||
| Line 68: | Line 72: | ||
Google Summer of Code represents a unique opportunity to bring new perspectives to the Octave community. As a somewhat older project, we benefit from having new and younger contributors among our developers. We have been able to retain several GSoC participants as contributors to the Octave project and we hope to improve in the future by engaging more effectively with students during both the application and mentoring processes, setting clear standards for what is required for acceptance, and maintaining those standards throughout the project. | Google Summer of Code represents a unique opportunity to bring new perspectives to the Octave community. As a somewhat older project, we benefit from having new and younger contributors among our developers. We have been able to retain several GSoC participants as contributors to the Octave project and we hope to improve in the future by engaging more effectively with students during both the application and mentoring processes, setting clear standards for what is required for acceptance, and maintaining those standards throughout the project. | ||
=== What is the URL for your Ideas page? === | === What is the URL for your Ideas page? === | ||
| Line 83: | Line 79: | ||
=== What is the main development mailing list for your organization? === | === What is the main development mailing list for your organization? === | ||
octave-maintainers@gnu.org (https:// | octave-maintainers@gnu.org (https://lists.gnu.org/mailman/listinfo/octave-maintainers) | ||
=== What is the main IRC channel for your organization? === | === What is the main IRC channel for your organization? === | ||
| Line 92: | Line 88: | ||
We have about 10 contributors who are potential mentors. They have participated in previous | We have about 10 contributors who are potential mentors. They have participated in previous | ||
SoC projects, either as students or | SoC projects, either as students or mentors, and are all active participants in the Octave community. All | ||
have previously contributed code, have commit access to either the Octave or | have previously contributed code, have commit access to either the Octave or | ||
Octave Forge source tree, and are active in the mailing lists. Many also keep a | Octave Forge source tree, and are active in the mailing lists. Many also keep a | ||
| Line 104: | Line 100: | ||
=== What is your plan for dealing with disappearing students? === | === What is your plan for dealing with disappearing students? === | ||
Disappearing students haven't been a problem for us in previous years. To prevent disappearances, we aim to make all reasonable efforts to accommodate | Disappearing students haven't been a problem for us in previous years. To prevent disappearances, we aim to make all reasonable efforts to accommodate students and make them feel | ||
welcome. We will engage students frequently by email and IRC, provide prompt response to student queries, | welcome. We will engage students frequently by email and IRC, provide prompt response to student queries, | ||
and expect periodic reports from mentors about the project status. We will also | and expect periodic reports from mentors about the project status. We will also | ||
encourage the | encourage the students to participate on the public mailing list and IRC channel, | ||
with or without the mentor. Their progress should be regularly applied to our source | with or without the mentor. Their progress should be regularly applied to our source | ||
tree, if necessary in a side branch. All of these have shown to be effective | tree, if necessary in a side branch. All of these have shown to be effective | ||
with students. | with students. | ||
Should this fail and a student disappears | Should this fail and a student disappears (which we | ||
hope will be very unlikely, since it has never happened before and nobody | hope will be very unlikely, since it has never happened before and nobody | ||
vanishes without good reason), make | vanishes without good reason), make | ||
| Line 160: | Line 156: | ||
No. | No. | ||
[[Category:Summer of Code]] | |||
[[Category:2015]] | |||