Improve the Software .

Melody is powered by a powerful cast of characters comprised of several languages and technologies. These include:

• Core Perl code
• Core PHP code (for dynamic rendering of published blogs)
• Default application templates (MTML: HTML + MT template tags)
• Application UI stylesheets (CSS)
• Application UI Javascript
• Blog-side themes (CSS + MTML)
• Perl and/or PHP-based plugins
• POD-formatted documentation
• Perl-based automated testing

If you are familiar with any one of these, you can (and, dare we say, should!) contribute to the core Melody software. Here's how...

Read the Melody Contributor Guidelines

The Melody Contributor Guidelines are an essential read for every contributor. They are the roadsign for the lost, the sturdy handrail down the slippery set of stairs, the oasis of "Oh!" in a vast desert of "Huh?!".

Download the code

In order to contribute, you have to get the source code. Although we strongly suggest that code contributors (especially frequent contributors) learn the basics of Git (the version control software we use), it's really important to us that anyone who has something to contribute be able to do so without barriers that might otherwise keep them on the sidelines.

Git-savvy

For those of you who are familiar with Git or want to be, everything you need to know to be a rock star Melody contributor can be found in the Development Start Guide.

Regardless of whether your new to all of this or an old hand, we sincerely welcome and appreciate all of your contributions and the fact that you're a part of our community.

Git-challenged

If Git gives you the willies, you can actually download one of the latest Melody developer snapshots in either tar/gzip and zip format. Once you have it downloaded and installed, you can make your changes and then get them to us using the following method:

1. Create a patchfile by performing a recursive diff between your Melody application directory and a pristine copy of it. Don't be scared! It's actually much easier than it sounds. The nice folks in IRC or the mailing list will be happy to help you with this.
2. Create a new case in LightHouse, attaching your patch file and any new or changed binary assets (e.g. images) to the case.
3. In the case, explain fully what you did so that the reviewer can easily understand

And that's it! You've contributed. Congratulations and make sure to pick up your Awesome Merit Badge on the way out!