Development/Summer of Code/Application Template

From MusicBrainz Wiki
< Development‎ | Summer of Code
Revision as of 17:25, 17 February 2016 by Chirlu (talk | contribs) (Clarify wording)
Jump to navigationJump to search

Before you start

IMPORTANT NOTE: 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 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.

Personal information

IRC nick:

Do you have Twitter or any other public profiles you think we might find interesting?


Tell us more about your proposed project! Where can we find any diagrams or other things that will help us understand your proposal better? 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 of these. If you provide no mock-ups, schemas or supporting diagrams, you're unlikely to get your application accepted.

(This section of your proposal needs to be at least three times as large and detailed as the rest of the application. If you leave this section blank or only put a few sentences here, we will ignore your proposal.)

As part of applying for SoC we require that you take your idea and propose it to the MusicBrainz developer community here: Please propose your 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. If you fail to get community feedback for your project idea, we will not accept your project!

In order to have your GSoC application be accepted by MusicBrainz you must interact with your potential mentor and submit one bug fix or new feature that is related to your proposal. This is intended to get you set up with the right development tools before the project starts. This doesn't have to be anything very significant -- all we're looking for is a demonstration that you've installed and at least worked with the relevant code to some degree. We suggest contacting potential mentors listed in our ideas page for suggestions on what to work on for this requirement.

Finally, you will need to create a schedule of how you plan to spend your time. A weekly breakdown with a few milestones is usually the best way to create a schedule.

If your proposal does not include all of the required items above, we will ignore your proposal.

Detailed information about yourself

  • 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.)
  • What aspects of MusicBrainz 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?
  • Do you plan to have a job or study during the summer in conjunction with Summer of Code?