Help Wanted: Difference between revisions

From MusicBrainz Wiki
Jump to navigationJump to search
m (3 revision(s))
m (→‎Benefits: updating old about/team links)
 
(7 intermediate revisions by 7 users not shown)
Line 1: Line 1:
[[MusicBrainz]] has built up a large community to help accomplish our ambitions, but we still need all kinds of help! We need more volunteers to edit the data, [[How To Vote|vote]] on pending edits, document existing software, and test new features. However we also have a great need for software developers to help integrate new features into MusicBrainz.


⚫
If you do not have all the skills listed in a section, and would like to pick up the remaining skills, then working on MusicBrainz might be the right way to do that. As long as you can self direct your learning, we can help point you in the right direction and get you up and moving.
[[MusicBrainz]] has great ambitions, and already gets tons of support from the community that has built up around the project. We need all kinds of help: Editing the data, [http://www.musicbrainz.org/mod/search/pre/new.html voting on other people's edits], documenting existing software and testing new features. However, we really need software developers and testers to develop the next great [[MusicBrainz]] feature. If you think [[MusicBrainz]] is cool and you're a motivated hacker/tester and hack on software for fun, [mailto:helpwanted@musicbrainz.org please let us know]!


== Benefits ==
⚫
If you have most, but not all the skills required we'd be willing to help you learn the missing skills. We're looking for self motivated people willing to learn new things and to challenge the status quo. All of our positions have the following benefits:
⚫
* Undying gratitude of the [[MusicBrainz]] community
⚫
* Your name in [[User:MusicBrainzBio|lights]]
⚫
* Excellent resume fodder
⚫
* [mailto:yourname@musicbrainz.org yourname@musicbrainz.org] mail address


⚫
* Undying gratitude of the MusicBrainz community
⚫
=Open Positions and Tasks=
⚫
* Your name in [[meb:team|lights]]
⚫
* Excellent resume fodder
⚫
* yourname@musicbrainz.org email address


== Open Tasks ==
⚫
The list of open tasks is kept on our [[Bug Tracker|BugTracker]], and on [[MusicBrainz Development|MusicBrainzDevelopment]], and they change quite frequently.


⚫
The list of open tasks is kept on our [[Bug Tracker]], and on [[MusicBrainz Development]], and they change quite frequently.
==Web Developer==


⚫
== Open Positions ==
⚫
If you do not have all the skills listed in a section, and would like to pick up the remaining skills, then working on [[MusicBrainz]] might be the right way to do that. As long as you can self direct your learning, we can help point you in the right direction and get you up and moving. Our web developers need the skills listed below:
⚫
* Mid-level to experienced perl hacker
* mod_perl experience
* [http://masonhq.com/ HTML::Mason] experience
⚫
* Know [http://w3.org/XML XML] and/or [http://w3.org/RDF RDF]
* SQL Experience, [http://www.postgresql.org/ PostgreSQL] is our poison of choice.


==Client Developer==
=== MusicBrainz Server Developer ===


Our client developers need to have these skills:
Our web developers need the skills listed below:
⚫
* Mid-level to experienced perl hacker
⚫
* Experienced C/C++ or Python programmer
* Catalyst, Template Toolkit, Moose experience
* Experience writing [http://www.wxwindows.org/ wxWindows] applications.
⚫
* Know [http://w3.org/XML XML] and/or [http://w3.org/RDF RDF]
⚫
* Linux lovers preferred, Mac OS X devotees welcome, Win32 Python hackers needed!
* Know [http://w3.org/XML XML] and/or [http://w3.org/RDF RDF]
* SQL Experience, [http://www.postgresql.org/ PostgreSQL] is our poison of choice.


=== PyMusicBrainz2 Developer (Python client library) ===
==Software Tester==


We're looking for a maintainer for our Python interface to our [[XMLWebService]]:
We currently do not have any volunteers focusing on testing. We could really use someone who would be willing to take on the task of putting together a test plan for the [[MusicBrainz]] projects and creating the needed tools/scripts to put the test plan into action.
⚫
* Experience with Python
* Testing web applications, normal applications or software APIs
* General understanding of Web Services.
* Regression test experience
⚫
* Linux lovers preferred, Mac OS X devotees welcome, Win32 Python hackers needed!
⚫
* Experience with Linux / Apache / Perl
* Know XML.


The immediate task at hand is to add support for Release Groups to pymb2.
⚫
[[Category:To Be Reviewed]] [[Category:WikiDocs Page]] [[Category:Communication Forum]] [[Category:Development]]

=== libdiscid Developer (C based Audio CD identification client library) ===

We're looking for a maintainer for our discid library:
⚫
* Experienced C programmer
* Experience writing/maintaining a C library
* Linux lovers preferred, Mac OS X devotees welcome, Win32 Python hackers needed!
* Experience with CD-ROMs, ISRCs

The immediate task at hand is to add support for reading ISRCs and barcodes from CD-TEXT.

== Contact us ==

If you think MusicBrainz is cool, you're a motivated hacker/tester and hack on software for fun, and you're interested in any of these volunteer positions:
* Send an email to <code>helpwanted [at] musicbrainz [dot] org</code>, or
* Join us in IRC on <code>irc.freenode.net</code> channel <code>#metabrainz</code>.

⚫
Keep in mind that we're looking for self motivated people willing to learn new things and to challenge the status quo.

⚫
[[Category:WikiDocs Page]] [[Category:Communication Forum]] [[Category:Development]] [[Category:To Be Reviewed]]

Latest revision as of 16:20, 26 August 2016

MusicBrainz has built up a large community to help accomplish our ambitions, but we still need all kinds of help! We need more volunteers to edit the data, vote on pending edits, document existing software, and test new features. However we also have a great need for software developers to help integrate new features into MusicBrainz.

If you do not have all the skills listed in a section, and would like to pick up the remaining skills, then working on MusicBrainz might be the right way to do that. As long as you can self direct your learning, we can help point you in the right direction and get you up and moving.

Benefits

  • Undying gratitude of the MusicBrainz community
  • Your name in lights
  • Excellent resume fodder
  • yourname@musicbrainz.org email address

Open Tasks

The list of open tasks is kept on our Bug Tracker, and on MusicBrainz Development, and they change quite frequently.

Open Positions

MusicBrainz Server Developer

Our web developers need the skills listed below:

  • Mid-level to experienced perl hacker
  • Catalyst, Template Toolkit, Moose experience
  • Know XML and/or RDF
  • SQL Experience, PostgreSQL is our poison of choice.

PyMusicBrainz2 Developer (Python client library)

We're looking for a maintainer for our Python interface to our XMLWebService:

  • Experience with Python
  • General understanding of Web Services.
  • Linux lovers preferred, Mac OS X devotees welcome, Win32 Python hackers needed!
  • Know XML.

The immediate task at hand is to add support for Release Groups to pymb2.

libdiscid Developer (C based Audio CD identification client library)

We're looking for a maintainer for our discid library:

  • Experienced C programmer
  • Experience writing/maintaining a C library
  • Linux lovers preferred, Mac OS X devotees welcome, Win32 Python hackers needed!
  • Experience with CD-ROMs, ISRCs

The immediate task at hand is to add support for reading ISRCs and barcodes from CD-TEXT.

Contact us

If you think MusicBrainz is cool, you're a motivated hacker/tester and hack on software for fun, and you're interested in any of these volunteer positions:

  • Send an email to helpwanted [at] musicbrainz [dot] org, or
  • Join us in IRC on irc.freenode.net channel #metabrainz.

Keep in mind that we're looking for self motivated people willing to learn new things and to challenge the status quo.

Retrieved from "https://wiki.musicbrainz.org/index.php?title=Help_Wanted&oldid=70681"