Editing GSoC 2012 application

__NOTOC__

Octave's application for GSoC 2012.

=== Describe your organization ===

GNU Octave (http://www.gnu.org/software/octave/) produces 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 (ENUMERATE some?). 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 sibling project, Octave Forge (http://octave.sourceforge.net/), host many field-specific packages (ENUMERATE?).

=== Why is your organization applying to participate in Google Summer of Code 2012? What do you hope to gain by participating? ===

Octave participated with one student under the auspices of the GNU project. Due to the success of that experience, where many members of the Octave community helped mentor Daniel Kraft, we want to try again.

We are hoping to get good code from interested students and ideally establish a line of collaboration with them for the future. Also to raise awareness of Octave amongst the free software community.

Google Summer of Code represents a unique opportunity to pump up work into highly needed low level improvements to Octave, as well as high level field-specific functionality. We believe the interaction with fresh minds will bring not only new code to Octave but also will augment the developers group.

=== Did your organization participate in past Google Summer of Codes? If so, please summarize your involvement and the successes and challenges of your participation. ===

Yes, during 2012, under the GNU umbrella. The success was a completed project by a very capable student, and the challenges were that Jordi, the mentor for Daniel Kraft, did not know all the answers. Other members of the Octave community were involved in the work in the mailing list and offered advice and help as needed.

=== If your organization has not previously participated in Google Summer of Code, have you applied in the past? If so, for what year(s)? ===

This is the first time we apply as an independent organisation.

=== What Open Source Initiative approved license(s) does your project use? ===

We prefer the GPLv3+ and may use the AGPLv3+ for one side project. We can accept any GPL-compatible free license.

=== What is the URL for your Ideas page? ===

http://octave.org/wiki/index.php?title=GSoC_Project_Ideas

=== What is the main development mailing list for your organization? ===

maintainers@octave.org

=== What is the main IRC channel for your organization? ===

<tt>#octave</tt> in Freenode

=== Does your organization have an application template you would like to see students use? If so, please provide it now. ===

No... perhaps we should make one.

We could include the following items (it can be a google application form)
* What OS do you use to develop?
* Are you an Octave or Matlab (R) user?
* Evaluate your coding confidence level on the followings: C (-,0,+); C++ (-,0,+); Octave m-files (-,0,+); OpenGL (-,0,+)
* Something about their background (CS, Physics, AI, Control, etc...).

=== Who will be your backup organization administrator? ===

John W. Eaton <jwe@octave.org>

=== What criteria did you use to select your mentors for this year's program? Please be as specific as possible. ===

Their involvement in the mailing list and the quality of their past advice. Preferrably they already have code in the Octave source tree and ideally already have commit access to our source tree. Also whether they can participate in chat sessions, but this is less important.

Mentors have been chosen based on their expertise in the field of the corresponding project, either based in their past contributions to Octave or in their academic background or heir current professional activities.

=== What is your plan for dealing with disappearing students? ===

Make reasonable attempts to contact them first, of course. If enough time has passed without response (say, one week without a response), begin to analyse the code they have submitted, if any, and attempt to integrate it into our source tree.

=== 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.

=== 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 mininum frequency of emails (probably one every two or three days). Be nice and friendly to them.
Depending on their interests and code submitted, students will be put in contact with maintainers/developers of packages for Octave (Octave-Forge packages). Octave community enjoys developers related to Academy and Industry and we believe that emergence of joint projects is not unlikely. This represents potential career opportunities for students and the ones that get involved with the community will be encouraged to continue their collaboration.

=== Are you a new organization who has a Googler or other organization to vouch for you? If so, please list their name(s) here. ===

Yes, GNU can vouch for us.

=== Are you an established or larger organization who would like to vouch for a new organization applying this year? If so, please list their name(s) here. ===

No.