mozdev.org

Mozile (xhtml editing in your browser)    

resources:

Contribute

Mozile is an open source project. Everyone is welcome to contribute code, documentation, bug reports, internationalization, feature requests, etc. If you find Mozile useful and you want to make it better, please consider contributing your time and talents. Every bit of help is appreciated.

Mozile 0.8 is the focus of most new development. Mozile 0.6 is being maintained and updated to work with new Firefox versions. We continue to fix bugs and do minor maintenance the Mozile 0.7 code. Mozile 0.5 is no longer being developed.

Getting Started

All you need to contribute to Mozile is a web browser, a text editor, and a copy of the source code. There's documentation for users and developers available:

You can also take advantage of:

Report Bugs

If you find a bug, please report it.

Ideas for Improvements

Things we'd like to see in Mozile 0.8:

Got a contribution or proposal? Just send an email to our mailing list.

Submitting Patches

If you've made a change to the Mozile code that you think will be useful to other people, please send it to us. We prefer to receive patch files, made against the latest CVS source. Remember to:

The following is a sample of a small patch, adapted from the Linux From Scratch patch submission guidelines. Starting with Index: core/core.js all the lines are the result of the diff operation. The lines above that have been added by the patch submitter.

Submitted By: James A. Overton 
Date: 2006-06-14
Initial Package Version: 0.8.0
Description: This is a sample patch. This was created so that there is an
             easy reference for those submitting patches.

Index: core/core.js
===================================================================
RCS file: /cvs/mozile/www/0.8/core/core.js,v
retrieving revision 1.12
diff -u -r1.12 core.js
--- core/core.js	14 Jun 2006 15:03:52 -0000	1.12
+++ core/core.js	14 Jun 2006 18:17:32 -0000
@@ -30,6 +30,8 @@
 // Ensure the global container is present.
 if(!mozile) throw Error("The 'mozile' object should have been defined in mozile.js, but it was not.");
 
+// Magical white space fix:
+mozile.foo();
 
 /**
  * Set the version number.

Creating Patches

If you're new to CVS, the source page has information on getting started. If you're new to patches, here's an explanation of how they work.

There's a fair amount of code in our CVS repository, and compared to the total each of the changes we make is small. It would be a pain to send a copy of the entire repository every time a change is made. So there are special tools for sharing just the information about the changes: diff to find the differences in Alice's code and store them in a "patch" file, which she can email to Benjamin, and patch to take the patch file and apply the changes to Benjamin's copy of the code.

Both diff and patch come with pretty much every Unix, Linux, and Mac OS X system (although you may need to install "developer" tools). You can also get a Windows version of diffutils. A diff tool is built in to CVS command line clients. And Integrated Development Environments (IDEs) like Eclipse often include CVS support and patching tools, if you prefer to use an IDE.

Before making a patch you might consider some of this advice on good patching practice. Here's a summary:

The golden rule is that everyone is short on time, so we all do our best to make things quick and easy for each other.

Here are the steps you should usually take to create a patch file for Mozile:

Applying Patches

If you find a patch file (in our bug database or on our mailing list) which you'd like to try out, here are the general steps.

The mozile project can be contacted through the mailing list or the member list.
Copyright © 2000-2017. All rights reserved. Terms of Use & Privacy Policy.