Google Code-in/Mentors: Difference between revisions
From MusicBrainz Wiki
Jump to navigationJump to search
(→Administrators: Add bitmap.) |
(→Mentors: Fixing sampsyo's timezone; http://chatlogs.metabrainz.org/brainzbot/musicbrainz/msg/3411933/) |
||
Line 26: | Line 26: | ||
: MusicBrainz editor with the very most accepted edits of all time! Will mostly be mentoring tasks related to MusicBrainz editing. |
: MusicBrainz editor with the very most accepted edits of all time! Will mostly be mentoring tasks related to MusicBrainz editing. |
||
; [[User:asampson|sampsyo]] ([https://musicbrainz.org/user/Adrian%20Sampson @MusicBrainz], sampsyo @ IRC; UTC- |
; [[User:asampson|sampsyo]] ([https://musicbrainz.org/user/Adrian%20Sampson @MusicBrainz], sampsyo @ IRC; UTC-0800) |
||
: Author and primary developer of [http://beets.radbox.org/ beets] and will mostly mentor tasks related to this. |
: Author and primary developer of [http://beets.radbox.org/ beets] and will mostly mentor tasks related to this. |
||
Revision as of 23:54, 25 November 2015
Here is a short introduction to the various mentors for MetaBrainz' Google Code-in 2015.
Administrators
- Freso (@MusicBrainz, @BookBrainz, Freso @ IRC; UTC+0100)
- Official MetaBrainz Community Manager (yes, that's his actual job), all-round MetaBrainz knowledge
- reosarevok (@MusicBrainz, reosarevok @ IRC; UTC+0200)
- Master of Style and overall MusicBrainz guy; has the 2nd most number of applied edits to MusicBrainz of all time!
- Roman (@MusicBrainz, Gentlecat @ IRC; UTC+0100)
- One of the primary developers of CritiqueBrainz, AcousticBrainz, and the MetaBrainz and ListenBrainz websites in addition to being one of the official (ie., paid) MusicBrainz developers.
- Michael (@MusicBrainz, bitmap @ IRC; UTC-0600)
- Senior/lead developer of MusicBrainz; official MusicBrainz developer.
Mentors
- Wieland "Mineo" Hoffmann (@MusicBrainz, Mineo @ IRC; UTC+0100)
- Developer of everything that even remotely looks like Python, but mostly Picard.
- d4rkie/ Mihai (@MusicBrainz, Nyanko-sensei / D4RK-PH0ENiX @ IRC; UTC+0900)
- Occasional editor, mainly editing Japanese artists.
- David Saunders (@MusicBrainz, drsaunders @ IRC; UTC-0500)
- MusicBrainz editor with the very most accepted edits of all time! Will mostly be mentoring tasks related to MusicBrainz editing.
- sampsyo (@MusicBrainz, sampsyo @ IRC; UTC-0800)
- Author and primary developer of beets and will mostly mentor tasks related to this.
- Alex / caller#6 (@MusicBrainz, CallerNo6 @ IRC; PST (UTC-0800))
- Occasional editor, sometimes involved in Style and documentation.
- Ben / LordSputnik (@BookBrainz, @MusicBrainz, LordSputnik @ IRC; UTC+0000)
- Lead developer of BookBrainz, with experience of Node.js, Python, beets and mutagen. Started out editing MusicBrainz.
- Sean / Leftmost (@BookBrainz, @MusicBrainz, Leftmost @ IRC; UTC-0700)
- Also lead developer of BookBrainz, contributing developer for MusicBrainz.
I want to be a mentor too!
Great! Read https://gist.github.com/Freso/315f0ac13a1303fcb91e first to be sure. Still want to be a mentor? Alright! If you are already involved in any of the MetaBrainz projects, just go ahead and poke Freso in #metabrainz on IRC. If you're not, the below are some highly suggested tasks to get you familiar with the various MetaBrainz projects:
- Read How to Contribute (MusicBrainz) - this one is mandatory!
- Add at least one release that isn't in the database yet
- Write a review for at least one album or concert on CritiqueBrainz (if the concert or album isn't in MusicBrainz yet; add it)
- Tag some of your music files with MusicBrainz Picard and play around with its settings.
- Submit AcoustIDs for the album(s)/release(s) you added earlier.
- Analyse the music from the album(s)/release(s) you have and submit that analysis to AcousticBrainz
- (If you have a Last.FM account) Go to ListenBrainz and import your Last.FM data.
- ...
You should preferably be able to do the above with only little tuition from #musicbrainz and #metabrainz or you might need to invest more time than what is available before Dec. 7th if you wish to be a mentor.
Note: Even doing all the above tasks and more, you are still not guaranteed to become a mentor. Stick around during and after the GCI and become known in the community and you will have a much better shot next year!