Mozbot/Hacking

So you want to help us hack mozbot? Excellent!

Getting Started

First, you will want to get [download.html#cvs1 the latest mozbot source from CVS]. The easiest way to get into mozbot hacking is to fix a bug. (It is a lot easier to start by poking around in code that already works rather than trying to write new code from scratch.) If you want some other ideas of something to implement, look for XXX comments in the source.

Modules

If you are interested in writing or hacking modules, take a look at the API documentation. The easiest way to write a new module is to take an existing one that does something similar to what you want to do, save it with a new name, and start ripping code out. That will also help to keep the coding style similar throughout mozbot's source. If you want to browse the source code online before contributing, you can do so using the MXR interface to CVS.

The Team

The mozbot team is a poorly defined group of people. The current module owner is Wolf. The other people involved with mozbot at the moment include:Cww, Jake, justdave, kerz, kiko, timeless, tmyoung, and zach. Some of usare also Bugzilla hackers. Mozbot development occurs primarily in #mozwebtools, and testing occurs primarily in #mozbot.

Review

Before any patch may be checked into the mozbot source, it must be reviewed by Wolf. To get a patch reviewed, you attach the patch to the relevant Bugzilla bug (if none yet exists for the issue in question, please file one), and add the review flag to your attachment. If you have any questions, feel free to ask.