Thanks for your interest in Summer of Code with CMUSphinx!
Summer of Code (SoC) is a program promoting open source software development by sponsoring students to work on open source projects from the comfort of their home. If you are a student interested in developing open source software, this program is for you! We do have strong requirements and huge expectation. But we sure you are capable of doing that.
Students who successfully complete SoC will receive USD $5000 for their work.
To participate in SoC as a student, you must be an individual enrolled in an accredited post-secondary institution. Sorry, no group applications are allowed. Please check Google SoC 's eligibility section for more details.
Please be sure you are familiar with answers to GSoC's frequently asked questions
If you are interested in details, feel free to ask on mailing list or on IRC channel #cmusphinx on freenode.
Also note that there are many places in the net related for GSOC. For example check GSoc student Do's and Don'ts
A good place to look for project ideas is Project Ideas. (This page is being updated constantly during the application period - Please check it frequently.) It is important to note that this list is not exclusive: if you have a good idea that is not listed, don't hesitate to apply for your project. It's probably a good idea to ask people in the CMUSphinx community if they think your idea is good, though. Note that we are accepting coding projects only, sorry, no translation or documentation projects are allowed.
It's a good idea to take the time to interact with the CMUSphinx and discuss your ideas. Hanging on irc channel #cmusphinx at freenode is a good way to get in touch with potential mentors.
Once you decide on the project you are proposing, to get a feel of the project try to fix a small bug in CMUSphinx. You can ask on irc or mailing list for a suggestion for what a suitable bug can be or find one in the project's tracker and double check about it with the mentor. You will need to download and run the code for the project and create a patch that fixes the bug. Your patch may end up being just a few lines of code, but this demonstrates a willingness to learn and get involved.
While working on your contribution, you should feel free to ask for help from the mentor or from other people in the project's IRC channel. You will need to upload your patch to the corresponding bug in the project's tracker page. It is typical that once you submit your patch, the mentor or another person who reviews it will have some feedback about what you can improve in it. Please be sure to follow up on the reviewer's feedback by attaching an updated patch until your contribution is ready to be included in the project. This kind of review process is standard for many of the changes that go in, so please don't be deterred by it. It's best to allocate time over at least a week for this process and to start as early as possible.
To warm up and learn about the project go through the CMUSphinx Tutorial For Developers
The student application period opens on March 20th at 16:00 UTC and closes April 3rd at 16:00. You have to submit your application on Google's Summer of Code website. It should contain a detailed description of your project proposal. Please follow the following plan in your proposal:
There are 3 evaluation periods this year where mentors are required to complete an evaluation of their student. After the first 4 weeks of coding, after 8 weeks of coding and then at the end (after 12 weeks of coding). The evaluation forms are shorter than previous years so they should take less time to complete.
This is the most important part
Don't just answer these questions, use your imagination and try to be clear. Don't forget to show enthusiasm.
It is never too early to start working on your SoC application! Note that SoC's positions are
'extremely' competitive. There were several projects that were on the cusp of being accepted but were not. Make sure you research the potential projects and write up a strong application. Your SoC application should be specific to your project. Potential SoC applicants may also want to read Google's advice for SoC students. Please see “Selection Process” section below for specific details of our project.
Here is one of this year's co-mentors' successful student application for 2012: https://docs.google.com/document/d/1fymC4ta29apKZDtx4mkWx1t0L58XbV_FYmlIWcDiVLo/edit
Here is what one of the org admins' successful student application looked like last year: https://docs.google.com/document/d/1NIYgCbklTCxBjk8r_NcVMzdZ-KGH1D4OtCbJiX-6H0I/edit
That may give you some idea of what to include. This time though, we ended up with a lot of extra work done early by volunteers, so we need to refactor a lot of the project ideas. Please do that in your draft applications. Don't forget to allow time to test and document your code.
We will carefully review your project, we do require some basic skills from you to be accepted. Please make sure you estimate your project properly. If you don't it's probably not worth to try. We will require you to get very deep into CMUSphinx project, think beforehand if you need it.
If your application is accepted, here are some information about how you'll integrate with our community, and what we'd like you to do:
SoC requires any code and other contributions you provide to be given under an OSI approved license, to ensure your work is available for use by anyone in the world. We will require you to use BSD license.
We are very pleased to have your help and as a courtesy are happy to attribute your work in various places, for example in blog posts. We will assume you want your name mentioned unless you suggest an alias, or the desire to remain anonymous.