Editing GSoC 2012 application
Jump to navigation
Jump to search
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 5: | Line 5: | ||
=== Describe your organization === | === Describe your organization === | ||
GNU Octave | GNU 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. | ||
=== 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? === | ||
Octave participated | 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. | ||
=== Did your organization participate in past Google Summer of Codes? If so, please summarize your involvement and the successes and challenges of your participation. === | === 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 | 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)? === | === If your organization has not previously participated in Google Summer of Code, have you applied in the past? If so, for what year(s)? === | ||
Line 30: | Line 25: | ||
=== What is the URL for your Ideas page? === | === What is the URL for your Ideas page? === | ||
http://octave.org/wiki/index.php?title=GSoC_Project_Ideas | http://octave.org/wiki/index.php?title===GSoC_Project_Ideas | ||
=== What is the main development mailing list for your organization? === | === What is the main development mailing list for your organization? === | ||
Line 41: | Line 36: | ||
=== Does your organization have an application template you would like to see students use? If so, please provide it now. === | === Does your organization have an application template you would like to see students use? If so, please provide it now. === | ||
=== Who will be your backup organization administrator? === | === Who will be your backup organization administrator? === | ||
Uhhh... let me ask. | |||
=== What criteria did you use to select your mentors for this year's program? Please be as specific as possible. === | === 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. | |||
=== What is your plan for dealing with disappearing students? === | === 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? === | === 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. | ||
=== 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 mininum frequency of emails (probably one every two or three days). Be nice and friendly to them. | |||
=== 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. === | ||
Yes, GNU can vouch for us. | 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. === | === 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. | No. | ||