Before you start
- Do not contact potential mentors privately. Not via email, nor via private messages. Your application for GSoC needs to be done in public.
- You must tell us what you wish to do! Please do not appear in our IRC channel and expect us to tell you what to do. You need to find the inspiration for your project and create a proposal from your own ideas. We will not tell you what to do. This is a test to see if you can think for yourself!
- If you are starting to work on your application during the second week of the application process, you've already missed your opportunity to apply. We require very detailed proposals and we insist that you work with our community to improve your application. You cannot do this in the last week and then hope to be accepted -- there isn't enough time. Please don't waste your time and ours!
When filling out your application, please copy the rest of this page into your application and fill out as much information as you can. The Google software doesn't really give us a lot of space for a template, so we've had to pare it down to a minimum which is below:
We require very detailed proposals and we insist that you work with our community to improve your application. Tell us everything about your proposed project. Include diagrams to help us understand your proposal. If you propose anything that requires a database schema you need to show us the proposed schema. The same applies to UI changes/additions -- we need to see mock-ups. If you provide no mock-ups, schemas or supporting diagrams, you won't be accepted.
As part of applying for SoC we require that you take your idea and propose it to the MetaBrainz developer community. Please propose the idea and then respond to any questions that may arise. Improve your proposal based on the feedback you receive from the community. If you cannot get the community to support your idea your chances for getting your proposal accepted are very slim. Finally, in order to have your GSoC application be accepted by MetaBrainz you MUST interact with your potential mentor and submit one bug fix or new feature that is related to your proposal. You will need to create a schedule of how you plan to spend your time. A weekly breakdown with a few milestones is best.
Do you have Github, Twitter or any other public profiles you think we might find interesting? Have you contributed to other Open Source projects or created projects on your own? If so, which projects and can we see some of your code? Do you plan to have a job or study during the summer in conjunction with Summer of Code?
There is other information we'd love to know about you -- please consider adding this to your application:
- Tell us about the computer(s) you have available for working on your SoC project!
- When did you first start programming?
- What type of music do you listen to? (Please list a series of MBIDs as examples.)
- If applying for a BookBrainz project: what type of books do you read? (Please list a series of BBIDs as examples. (And feel free to also list music you listen to!))
- What aspects of the project you're applying for (e.g., MusicBrainz, AcousticBrainz, etc.) interest you the most?
- Have you ever used MusicBrainz to tag your files?
- Have you contributed to other Open Source projects? If so, which projects and can we see some of your code?
- If you have not contributed to open source projects, do you have other code we can look at?
- What sorts of programming projects have you done on your own time?
- How much time do you have available, and how would you plan to use it?