Hacking on Mozilla

This is where to find what you need to know in order to check code in to mozilla's CVS repository. If you've never built mozilla before, then you should start by looking at the source code and building it.

People actively hacking mozilla can be given write access to our CVS repository. Anyone checking into the repository whether they're a net developer or Netscape engineer must do their part to keep the tree alive. This means knowing what to check in and when to check it in. Above all, it means making sure your code builds before its checked in, even on other platforms. After your checkin, it's your responsibility to make sure tinderbox builds your code sucessfully and to be available to help fix any problems that might arise.

Make sure your code is cross-platform no matter what kind of machine happens to sit on your desk. Don't break the build. If it breaks anyway, fix it.

Sign the Form

To get write access to the CVS tree, you'll need to fill out the CVS Contributor Form. Please keep our lawyers happy.

C/C++ Portability Guidelines

One of our primary design considerations is that our code work on a wide variety of platforms. Follow these guidelines and maybe one day you'll find your code running on really marginal platforms like your cable box or cell phone.

Follow the Tree Rules

We have a build process that's been in place at Netscape since Communicator 4.0. It's flexible, works with a minimum of human intervention and has scaled to work with hundreds of engineers. This process works and will continue to work if people follow these simple rules.

Use Bonsai Effectively

Bonsai can be used to find all sorts of information about the tree. As someone checking in code to the tree, you must use bonsai to find out news about the tree, such as whether it's open and whether there are any planned closures.

Happy hacking!