3. If a bug has already been filed for what you want to do, check its [[Bugzilla:Priority_System|priority]].
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]].
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.
[Bugzilla: Patches|Make a patch]]
Submitting_Patches| Submit your patch in Bugzilla]]
Review| Ask for review]]
Once your bug has passed review , the reviewer will ask for "approval". When approval is granted, you or the reviewer can commit the patch to CVS.
10 . [[Bugzilla:Committing_Patches|Commit your patch]], or get somebody else to commit it for you.
== Articles and Policies ==