Jump to navigation Jump to search

Summer of Code Project Ideas

204 bytes removed, 07:16, 17 February 2016
remove notices from last year and re-format some of the student expectations
The following is distilled from the [[Projects]] page for the benefit of potential [ Google] and [ ESA] Summer of Code (SoC) students. Although students are welcome to attempt any of the projects in that page or any of their own choosing, here we offer some suggestions on what good student projects might be.
{{Note|For 2015, Octave is participating in GSoC under the [ GNU] umbrella.}}
{{Note|Octave has been selected for ESA Summer Of Code In Space ([ SoCIS]) program for 2015.
Applications for [ SoCIS] are due by end of April.}}
= Steps Toward a Successful Application =
If you like any of the projects described below , these are the steps you need to follow to apply:
* '''Help Us Get To Know You'''<br>
: If you aren't communicating with us before the application is due, your application will not be accepted.
:: '''Join the [ maintainers mailing list]''' or read the archives and see what topics we discuss and how the developers interact with each other.
:: '''Hang out in our [ IRC channel]'''. Ask questions, submit patches, show us that you are motivated and well-prepared. There will be more applicants than we can effectively mentor, so do ask for feedback on your public application to increase the strength of your proposal!
* '''Find Something That Interests You'''
: It's '''critical''' that you '''find a project that excites you'''. You'll be spending most of the summer working on it (we expect you to treat the SoC as a full-time job). But don: Don't just tell us how interested you are, show usthat you're willing and able to '''contribute''' to Octave. You can do that by [ fixing a few bugs] or interacting with us on [httpshttp://webchatsavannah.freenodegnu.netorg/patch/?channelsgroup=#octave IRCsubmitting patches] well before the deadline, in addition to regularly interacting with Octave maintainers and users on e-mail and IRC. Our experience shows us that successful SoC students demonstrate their interest early and often.
* '''Prepare Your Proposal With Us'''
: By working with us to prepare your proposal, you'll be getting to know us and showing us how you approach problems. The best place for this is your wiki Wiki user page and the [ IRC channel].
* '''Complete Your Application'''
: Fill out our '''''public''''' application template.
:: This is best done by '''[[Special:CreateAccount|creating an account at this wiki]]''' , and copying the '''[[Template:Student_application_template_public|template]]''' from its page.<br/>
:: You really only need to copy and answer the '''''public''''' part there, there is no need to showcase everything else to everybody reading your user page!
: Fill out our '''''private''''' application template.
* '''The Procedure for Contributing Changesets'''
: You will be expected to follow the same procedures as other contributors and core developers.
: You will be helping current and future Octave developers by using the same our standard style for changes, commit messages, and so on. You should also read the same [ contributingcontribution] [ guidelines] we have for everyone.
: [[Hg_instructions_for_mentors#Mercurial_Tips_for_SoC_students | This page]] describes the procedures students are expected to use to publicly display their progress in a public mercurial repo during their work.
* '''The Maintainers Mailing List'''
: Unless your primary mentor has a strong preference for some other method of communication, the IRC channel will likely be your primary means of communicating with your mentor and Octave developers.
* '''The Octave Forge Project'''
: [ Octave-Forge] is a project closely related to collection of contributed packages that enhance the capabilities of core Octave where packages reside. They are somewhat analogous to Matlab's toolboxes.
* '''Related Skills'''
: In addition, you probably should know '''some''' mathematics, engineering, or experimental science , or something of the sort.: If you've used Matlab beforeso, you probably have already been exposed to the kinds of problems that Octave is used for.
== Criteria by which applications are judged ==
* '''Applicant has demonstrated an ability to make substantial modifications to Octave'''
: The most important thing is that your application has you've contributed some interesting code samples to judge you by. It's ok 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'''
The following projects are broadly grouped by category and probable skills required to tackle each. Remember to check [[Projects]] for more ideas if none of these suit you, and your own ideas are always welcome.
{{Note|these are a suggested projects but you are welcome to propose your own projects provided you find an Octave mentor}}
== Numerical ==


Navigation menu