Summer of Code - Getting Started: Difference between revisions

no edit summary
No edit summary
Line 6: Line 6:


* '''Get to Know Us'''<br>
* '''Get to Know Us'''<br>
:If you aren't communicating with us before the application is due, your application will not be accepted.
: If you aren't communicating with us before the application is due, your application will not be accepted.
* '''Find Something that Interests You'''<br>
:: Join the maintainers mailing list or read the archives and see what topics we discuss and how the developers interacti 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 you are excited about.  You'll be spending most of the summer working on it (we expect you to treat the GSoC as a full-time job).  But don't just tell us how interested you are, show us.  You can do that by fixing a few bugs or interacting with us on IRC well before the deadline.  Our experience shows us that successful GSoC students demonstrate their interest early and often.
: It's critical that you find a project that you are excited about.  You'll be spending most of the summer working on it (we expect you to treat the GSoC as a full-time job).  But don't just tell us how interested you are, show us.  You can do that by fixing a few bugs or interacting with us on IRC well before the deadline.  Our experience shows us that successful GSoC students demonstrate their interest early and often.
* '''Prepare Your Proposal with Us'''<br>
* '''Prepare Your Proposal with Us'''
: By working with us to prepare your propsal, you'll be getting to know us and showing us how you approach problems.  The best place for this is your wiki user page and the IRC channel.
: By working with us to prepare your propsal, you'll be getting to know us and showing us how you approach problems.  The best place for this is your wiki user page and the IRC channel.
* '''Apply'''<br>
* '''Complete Your Application'''
: Fill out our '''''public''''' application template.<br>
: 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/>
:: 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!
:: 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.<br>
: Fill out our '''''private''''' application template.
:: This is best done by copying the '''[[Template:Student_application_template_private|template]]''' from its page and '''adding the required information to your application at Google (melange)''' or at '''ESA'''.<br>
:: This is best done by copying the '''[[Template:Student_application_template_private|template]]''' from its page and '''adding the required information to your application at Google (melange)''' or at '''ESA'''.<br>
:: Only the organization admin and the possible mentors will see this data.  You can still edit it after submitting until the deadline!
:: Only the organization admin and the possible mentors will see this data.  You can still edit it after submitting until the deadline!
* '''Hang out in our IRC channel'''<br>
: 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!


<noinclude>[[Category:Summer of Code]]</noinclude>
== Things You'll be Expected to Know or Quickly Learn ==
 
= General Guidelines =


Octave is mostly written in C++ and its own scripting language that is mostly compatible with Matlab. There are bits and pieces of Fortran, Perl, C, awk, and Unix shell scripts here and there. In addition to being familiar with C++ and Octave's scripting language, successful applicants will be familiar with or able to quickly learn about Octave's infrastructure:
Octave is mostly written in C++ and its own scripting language that is mostly compatible with Matlab. There are bits and pieces of Fortran, Perl, C, awk, and Unix shell scripts here and there. In addition to being familiar with C++ and Octave's scripting language, successful applicants will be familiar with or able to quickly learn about Octave's infrastructure.  You can't spend the whole summer learning how to build Octave or prepare a changeset and still successfully complete your project.


* '''The Build System'''
* '''The Build System'''
Line 51: 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.
<noinclude>[[Category:Summer of Code]]</noinclude>


= Suggested projects =
= Suggested projects =