387
edits
GSoC 2012 application: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 6: | Line 6: | ||
GNU Octave (http://www.gnu.org/software/octave/) is a free numerical computing environment largely compatible with Matlab. It is an old project, started in 1992 by [[John W. Eaton]] and used by hundreds of thousands of people worldwide as a free alternative to Matlab. | GNU Octave (http://www.gnu.org/software/octave/) is a free numerical computing environment largely compatible with Matlab. It is an old project, started in 1992 by [[John W. Eaton]] and used by hundreds of thousands of people worldwide as a free alternative to Matlab. | ||
GNU Octave has an extensive core of functions useful for numerical computations in several fields | GNU Octave has an extensive core of functions useful for numerical computations in several fields, such as numerical analysis, optimisation, signal and image processing, and control theory. In order to speed up development, increase user contributions and test code before it is included in GNU Octave's core set of functions, a sister project, Octave Forge (http://octave.sourceforge.net/), hosts many field-specific packages. | ||
=== Why is your organization applying to participate in Google Summer of Code 2012? What do you hope to gain by participating? === | === Why is your organization applying to participate in Google Summer of Code 2012? What do you hope to gain by participating? === | ||
| Line 49: | Line 49: | ||
* Evaluate your coding confidence level on the following: C (-,0,+); C++ (-,0,+); Octave/Matlab m-files (-,0,+); OpenGL (-,0,+) | * Evaluate your coding confidence level on the following: C (-,0,+); C++ (-,0,+); Octave/Matlab m-files (-,0,+); OpenGL (-,0,+) | ||
* Something about your background (CS, Physics, AI, Control, etc...). | * Something about your background (CS, Physics, AI, Control, etc...). | ||
* Why did you choose GNU Octave? | |||
=== Who will be your backup organization administrator? === | === Who will be your backup organization administrator? === | ||
| Line 60: | Line 61: | ||
=== What is your plan for dealing with disappearing students? === | === What is your plan for dealing with disappearing students? === | ||
First, make all reasonable efforts to accomodate the student and make them feel welcome. Frequent contact with the student, prompt response to student queries, periodic status reports from mentors about the contact of the student. Also encourage the student to participate in the public mailing list and IRC channel, with or without mentor. Their progress should be regularly applied to our source tree, if necessary, in a feature branch. | |||
Should this fail and the student disappears for unforeseen reasons (which we hope will be very unlikely, and nobody vanishes without good reason), make reasonable attempts to contact them first, of course, up to and including using a phone number if one was provided. If enough time has passed without response (say, two weeks without a response, after attempting all methods), begin to analyse the code they have submitted, and attempt to integrate it into our source tree. | |||
=== What is your plan for dealing with disappearing mentors? === | === What is your plan for dealing with disappearing mentors? === | ||
Distribute the workload amongst the remaining mentors. The mailing list is active enough and questions almost never go unanswered. | Distribute the workload amongst the remaining mentors. The mailing list is active enough and questions almost never go unanswered. Reassign the student to a backup mentor. Worse comes to worst, the project admin can become a mentor for the student until another backup mentor is found. | ||
This should be infrequent and we hope to prevent this to begin with by selecting mentors with proven involvement in Octave or other free projects. | |||
=== What steps will you take to encourage students to interact with your project's community before, during and after the program? === | === What steps will you take to encourage students to interact with your project's community before, during and after the program? === | ||
Invite them to IRC. Set clear expectations on the minimum frequency of email progress updates (probably every two or three days). Be nice and friendly to them. | Invite them to IRC. Set clear expectations on the minimum frequency of email progress updates (probably every two or three days). Be nice and friendly to them. | ||
Octave community | Octave community boasts developers from to academia and industry, and we believe that emergence of joint projects is not unlikely. Connections made while contributing to the Octave community represent potential career opportunities for students, and successful student interns will be encouraged to continue their collaboration. This will be achieved by actively inviting students to continue and extend participation in Octave and Octave Forge projects, depending on their interests and code submitted. | ||
=== Are you a new organization who has a Googler or other organization to vouch for you? If so, please list their name(s) here. === | === Are you a new organization who has a Googler or other organization to vouch for you? If so, please list their name(s) here. === | ||