282
edits
Fgnievinski (talk | contribs) (→Implement classdef classes: adding info from GSoC proposal comment) |
(→Steps Toward a Successful Application: added criteria based on discussions with mentors) |
||
Line 49: | Line 49: | ||
: In addition, you probably should know '''some''' mathematics, engineering, or experimental science or something of the sort. | : In addition, you probably should know '''some''' mathematics, engineering, or experimental science or something of the sort. | ||
: If you've used Matlab before, you probably have already been exposed to the kinds of problems that Octave is used for. | : If you've used Matlab before, you probably have already been exposed to the kinds of problems that Octave is used for. | ||
== Criteria by which applications are judged == | |||
These might vary somewhat depending on the mentors and coordinators for a particular Summer of Code, but typically the main factors considered would be: | |||
* '''Importance of the project to Octave developers and the user community''' | |||
: If it already appears here as a project idea, chances are that someone cares about it. You can also ask in the mailing lists and IRC to gauge interest. | |||
* '''Applicant shows understanding of topic''' | |||
: Your application should make it clear that you're reasonably well versed in the subject area and won't need all summer just to read up on it. | |||
* '''Applicant shows understanding of and interest in Octave development''' | |||
: The best evidence for this is previous contributions and interactions. | |||
* '''Well thought out, adequately detailed, realistic project plan''' | |||
: "I'm good at this, so trust me" isn't enough. You should desribe which algorithms you'll use and how you'll integrate with existing Octave code. You should also prepare a full timeline and goals for the midterm and final evaluations. | |||
<noinclude>[[Category:Summer of Code]]</noinclude> | <noinclude>[[Category:Summer of Code]]</noinclude> |
edits