If you think you'd like to contribute, you can access the sources in our git repository as explained here. Then come share your ideas (and/or patches) in the Developer Forum. You can also browse existing defects or enhancement requests in the Issue Tracker to see if there's work that needs to be done. You can also ask and answer questions on the relatively new users mailing list.
Getting the Code
Source code is available via anonymous git as follows:
> git clone git://beet.git.sourceforge.net/gitroot/beet/beet ./beet
The following tools are required to build beet:
EasyAnt is a gestating build system, based on Ant and Ivy. Get the latest (at least 0.7) from the EasyAnt download page. We use some optional components, so get one of the "*-full" binaries. Create a directory called "easyant", unpack the archive into it, then follow these installation instructions to configure your build environment.
You can use easyant to execute a complete build from the command line:
/beet> easyant release
This will generate jars and release packages in the directory target/repository. Subsequent calls to "verify" will perform incremental recompiles. If you want to do a full rebuild, run a clean first:
/beet> easyant clean
You can get a complete (long) list of available targets with the -p option,
/beet> easyant -p
Beet is developed using Eclipse 3.5 ("Galileo"). Project files are included in source control, so you can easily import them into your Eclipse workspace if you wish. The included project files require you to have installed the IvyDE plugin. If you do not want to install IvyDE, you will just have to add the third-party jars from the release package to your project classpath. You can configure IvyDE to use the included ivysettings.xml file, beet/src/build/ant/ivysettings-eclipse.xml.