1,852
edits
Summer of Code - Getting Started: Difference between revisions
Jump to navigation
Jump to search
→Criteria by which applications are judged: Overhaul.
(→Steps Toward a Successful Application: More overhauling.) |
(→Criteria by which applications are judged: Overhaul.) |
||
| Line 56: | Line 56: | ||
== Criteria by which applications are judged == | == Criteria by which applications are judged == | ||
These might vary somewhat depending on the mentors and | These might vary somewhat depending on the mentors and SoC program, but typically the main factors considered would be: | ||
* '''Applicant has demonstrated an ability to make substantial modifications to Octave''' | * '''Applicant has demonstrated interest in Octave and an ability to make substantial modifications to Octave''' | ||
*: The most important thing is that you've contributed some interesting code samples to judge | *: The most important thing is that you've contributed some interesting code samples to judge your skills. It's OK during the application period to ask for help on how to format these code samples, which normally are Mercurial patches. | ||
* '''Applicant shows understanding of topic''' | * '''Applicant shows understanding of topic''' | ||
*: Your | *: Your proposal 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. | ||
* '''Well thought out, adequately detailed, realistic project plan''' | * '''Well thought out, adequately detailed, realistic project plan''' | ||
*: "I'm good at this, so trust me" isn't enough. | *: "I'm good at this, so trust me" isn't enough. In your proposal, you should describe which algorithms you'll use and how you'll integrate with existing Octave code. You should also prepare a project timeline and goals for the midterm and final evaluations. | ||
= Suggested projects = | = Suggested projects = | ||