Google Summer of Code: 2014
General PulseAudio Information
Feel free to contact us on IRC or via the mailing list (see the links above). We don't bite! (Note about IRC: there's no guarantee of a fast response. Some of us are present on the channel 24/7, but that doesn't mean that we pay attention all the time. So if you contact us via IRC and you don't get a quick reply, don't think that we're ignoring you, just hang around on the channel until you get an answer or try again later.)
- Arun Raghavan (Ford_Prefect on IRC, arun AT SPAMFREE accosted DOT net) (admin)
- Tanu Kaskinen (tanuk on IRC, tanuk AT SPAMFREE iki DOT fi) (mentor)
- Peter Meerwald (pmeerw on IRC, pmeerw AT SPAMFREE pmeerw DOT net)
Once you've decided which project idea suits you the best (pick an idea from the list below or one of your own), write up a proposal. Having the following bits will likely help make a coherent proposal:
- A description of the project
- A break-down of the tasks involved and possibly what you will not be covering (more detail is good)
- A schedule that describes how much you expect those tasks to take time (if a task takes much more than a couple of weeks, it should probably be split into subtasks)
- A short note about yourself
- Any other notes such as prior open source contributions (not required, but a bonus), why you think your proposal should be selected, etc. (keep this short as well!) The application that you submit is only one factor when we think whether you should be accepted instead of someone else. You can greatly improve your chances of getting selected by demonstrating in practice that you have the necessary skills and that you're a nice person to work with. Join the mailing list and the IRC channel and be active. Pick some suitably small task to work on (nothing wrong with big tasks either, if you have lots of free time). Ask questions and send patches. There's a list of "easy" bugs that can be useful when thinking what to work on.
Project Title (template)
Problem statement: What problem does this project solve?
Suggested solution: A rough outline of what needs to be done. If this is very detailed, this inevitably ends up being copied as the project plan (not necessarily verbatim), which makes it impossible to judge whether the student knows what he or she is talking about. I'm not sure if this is a huge problem, though. Ideally, the student capability would mostly be judged based on the pre-selection contributions.
Contacts: List of people to talk about this idea, mark potential mentors distinctly.
Necessary background: What skills are required/beneficial?
Potential mentors: List of people who volunteer to mentor this project.