4. Check out the latest Bugzilla code from CVS. You can see instructions for how to do this on the [http://www.bugzilla.org/download/#cvs Bugzilla download page]. You always want to work against the latest CVS code of Bugzilla, not a released version, if you're writing patches that you want us to accept.
5. Write some code. Make sure that you follow the [http://www.bugzilla.org/docs/developer.html Developer's Guide]. If you're new, you don't have to read the whole thing. Just read the [http://www.bugzilla.org/docs/developer.html#general General Guidelines], the [http://www.bugzilla.org/docs/developer.html#perl-style Style] section, and any other part that you think applies to the code that you're writing. Make sure that your patch is [[Bugzilla:Simple_Patches|as simple and small as possible]].
6. Test your patch. Make sure it works, and run ./runtests.pl in the Bugzilla directory. Also use [http://validator.w3.org the HTML validator] to make sure your code generates valid HTML, if you modified any of Bugzilla's HTML.