Difference between revisions of "Development/Summer of Code/Getting started"

From MusicBrainz Wiki
(I have more questions…: Use Communication instead of Contact Us. More links. Only one parenthesis.)
(So how do I get involved with the project?: Add link to Development/Summer of Code instead of linking straight to current year's proposals, as I want to try and keep the page "timeless".)
Line 10: Line 10:
  
 
First off, read [[How to Contribute]]. Then get familiar with the editing process, at least to a cursory degree. Check open bugs, feature requests, etc. at http://tickets.musicbrainz.org/ and just dig in.
 
First off, read [[How to Contribute]]. Then get familiar with the editing process, at least to a cursory degree. Check open bugs, feature requests, etc. at http://tickets.musicbrainz.org/ and just dig in.
 +
 +
Information from previous years and a link to the page with idea for the current years can be found at [[Development/Summer of Code]].
  
 
== I have more questions… ==
 
== I have more questions… ==
  
 
Great! The [[Communication]] page describes how to reach other MusicBrainz contributors via [[Communication/Mailing Lists|mailing lists]] or [[Communication/IRC|IRC]] (musicbrainz-devel@/#musicbrainz-devel respectively for most GSoC related topics).
 
Great! The [[Communication]] page describes how to reach other MusicBrainz contributors via [[Communication/Mailing Lists|mailing lists]] or [[Communication/IRC|IRC]] (musicbrainz-devel@/#musicbrainz-devel respectively for most GSoC related topics).

Revision as of 12:56, 5 February 2015

So you're looking to apply for Google Summer of Code, GSoC, and you find the idea of MusicBrainz or some other project under the MetaBrainz umbrella intriguing. But where do you go now? How do you get started? This document intends to guide you along that path.

Let's get started!

First off, you really want to study this flow chart:
GSoC flowchart.png
Got that? Alright. Let's move on.

So how do I get involved with the project?

First off, read How to Contribute. Then get familiar with the editing process, at least to a cursory degree. Check open bugs, feature requests, etc. at http://tickets.musicbrainz.org/ and just dig in.

Information from previous years and a link to the page with idea for the current years can be found at Development/Summer of Code.

I have more questions…

Great! The Communication page describes how to reach other MusicBrainz contributors via mailing lists or IRC (musicbrainz-devel@/#musicbrainz-devel respectively for most GSoC related topics).