Development/Summer of Code/2011

From MusicBrainz Wiki
< Development‎ | Summer of Code
Revision as of 03:06, 14 March 2009 by PavanChander (talk | contribs) (Possible typo? (Imported from MoinMoin))
Jump to navigationJump to search

Ideas for Google's Summer of Code

The MetaBrainz Foundation has applied as a Google Summer of Code organization in 2009. This will allow MusicBrainz hackers to apply for the Summer of Code program and if accepted, get paid for hacking on MusicBrainz.

This page lays out various ideas for projects that people can take on during their Summer of Code. If you have your own ideas for Summer of Code, please add them at the bottom of this page.

All applications for Summer of Code must pass a community review process where the proposer must clearly define their idea and present it to the community at large. Proposers must be/become active members of the community and must adapt their proposals according to community feedback. If the community does not approve of the project, the project will not be accepted by MetaBrainz Foundation. If your project makes it into the final round of consideration for acceptance, be ready for an interview and possibly even an entrace test to verify the skills claimed on your Summer of Code application.

Furthermore, all projects must develop new features for MusicBrainz. Proposals for replacing existing and working projects for the sake of making them more open will not be accepted. Proposals for extending existing projects with new features have a much greater chance at being accepted.

We strongly encourage students to delve into MusicBrainz and provide their own ideas for Summer of Code. We're listing a few projects here that we care about greatly, but we're more excited to hear what students want to do!

Wanted Proposals

  • [ Add new ideas here ]

Proposals NOT wanted

We are not interested in Mentoring the following projects:

  • Creation of new tagging applications: We would much rather see proposals that extend the PicardQT tagger and help along with its development. See the PicardQT section above.
  • Acoustic fingerprinting projects: We have an excellent partner in MusicIP who provides our current fingerprinting technology. Submitting a proposal to replace MusicIP is not going to be accepted since we are very happy with our current arrangement for acoustic fingerprinting.
  • Artist-artist collaborative filtering: We have a third party that has volunteered to work on this for us pro bono.

More ideas

If you have more ideas for the Summer of Code, please add them here.

  • Add ISRC (and ISWC?) support to MusicBrainz - this would involve working multiple parts of MusicBrainz: libdiscid (C), Picard (python) and mb_server (perl). Would be very interested in seeing this work done and I am willing to mentor the work - NicholasHumfrey
  • Collaborative similarity, along the lines of tags, as well as similarity cloud-link charts, between artists, labels, or releases. (This artist sounds like that artist, this label tends to release the same types of music as that label, this release is quite like this other release, etc). Maybe even tracks? Personally, I like the implementation in the Gazelle code, where anyone can add a similar artist, but then others can both up and down vote that similarity, something like the Slashdot karma system, with the similarity ranking between two objects influencing how high in the list they are, and how large they appear in the cloud. -- BrianSchweitzer 04:14, 13 March 2009 (UTC)
    • Hopefully this isn't what you mean by artist-artist collaborative filtering, ruaok? -- BrianSchweitzer 04:15, 13 March 2009 (UTC)
  • Works and Work Elements :) -- BrianSchweitzer 04:14, 13 March 2009 (UTC)
  • I'm just wondering what section "See the PicardQT section above." refers to; please remove this note when appropriate. -- PavanChander 03:06, 14 March 2009 (UTC)