Difference between revisions of "Development/Summer of Code/Getting started"
m (→Get ready: adding "good first bug" label)
(→Getting feedback: slight rewording)
|Line 50:||Line 50:|
If 't enough to get you started planning your proposal, please leave a comment on the [[Talk:Development/Summer_of_Code/Getting_started|discussion]] pagewhat you're looking for and how this doc could be improved.
Revision as of 17:05, 23 February 2017
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.
Do some homework.
- Have you read about the MeB projects? Do you understand what we do and why we're excited to be contributers?
- Have you looked at the ideas pages for each project?
MetaBrainz tends to choose students who take initiative, who jump in and start doing things, who can find answers to their own questions.
At this point, you should be familiar with basic open source development tools and workflows, and your Google-fu should be excellent.
So, you've done your homework. You've looked at the ideas pages. Excellent.
- What looks interesting?
- Have you read the related tickets (including the comments)? Having done that, have you read related forum posts or blog posts, if any?
- Are the technologies in your skill set? (Or can you pick up the required skills quickly on your own?)
At this point, if you're interested in a particular project then you might seek out a mentor on IRC to discuss the project and learn more about what it entails. However, "what do I do next?" is not the right question to be asking.
MetaBrainz tends to choose students who are active community members, who get involved at all levels.
- Have you created an account?
- Have you submitted any data?
- Have you installed and tried Picard or the AcousticBrainz submission tool? Written a review on CritiqueBrainz?
- Have you said "hi" in IRC? Maybe even lurked in a dev meeting?
Do more homework:
- Have you found and cloned the relevant git repo(s) and done a successful local installation?
- Have you tried fixing a few small bugs/issues? Each project has its own specific contribution instructions, but the basic workflow is the same. Use the issue tracker to find something to work on, and use Git to submit patches.
- Looking for your first issue to work on? Try searching for issues labelled "Beginner", "Good First Bug" etc.
Get to work
The ideas pages describe problems that needs to be solved. It's up to you to come up with a solution and a plan.
This is not the part where you should be asking for help. This is the part where you show us that you understand the problem and that you have a good plan for fixing it. (When/ if you're chosen for the program, then of course mentors will be there to help.)
We strongly suggest that prospective students send drafts of their proposals to our forums before they apply on the GSoC website.
We have a template which we would like you to use when you write on the forum. If you do not add this information then we may not respond until you've added it.
If this doc isn't enough to get you started planning your proposal, please leave a comment on the discussion page. Please tell us what you're looking for and how this doc could be improved.