

hey! your copy of mozilla is more than four weeks old. unless you are using the latest milestone build, bug reports get rapidly less useful the older your copy is.

so if you're not running the latest milestone, we could use your help testing either that or the latest nightly build. (be warned that nightly builds are development software, and there is no guarantee that they won't fry your processor, insult your mother, or cause you to break out in a nasty rash.)
getting involved with mozilla

congratulations! you've downloaded a mozilla build. this means that you've volunteered to become part of the mozilla testing community. great! welcome aboard. helping out won't take much of your time, doesn't require special skills, and will help improve mozilla.
what needs to be done?

report bugs

    you've already downloaded a build. all you have to do is use it as your everyday browser and mail/news reader. if you downloaded a build with talkback, please turn it on when it asks. talkback reports give us really valuable data on which crashes are the most serious, and how often people are encountering them. and all you have to do is click "ok". if you find something you think is a bug, check to see if it's not already known about, and then please follow the bug submission procedure.
quality assurance

    mozilla qa has a page dedicated to ways to get involved with helping. this doesn't involve knowing how to code, although a little knowledge of html is helpful. being involved with qa is good for people wanting to get more familiar with mozilla, and there's a strong community. a particularly good way to get involved is to join the bugathon.
fix bugs

    is there some bug that really bothers you? as well as reporting it, feel free to fix it. fixing bugs in mozilla is far easier than in many other applications, because you can fix bugs (such as those in our cross-platform front end, written in xul, our xml-based user-interface language, css and javascript) using only the build you are running right now. there is no need to set up complex environments, or compile anything. we've even written a tool to make it really easy to get started - patch maker. so, if you've written web pages, you can hack on mozilla.
docs and website

    the website is currently being totally rewritten, and any help would be greatly appreciated. mozilla could also do with all sorts of documentation - see the mozilla documentation project . the nerve centre for this activity is the newsgroup netscape.public.mozilla.documentation .

community

    mozilla developers tend to hang out on irc. if you've installed chatzilla, getting connected is easy. otherwise, fire up your favorite irc client and connect to irc.mozilla.org:6667, #mozillazine (a friendly channel belonging to mozillazine.) the development channel is #mozilla, although please note that people are trying to do work in this channel, so please don't ask support questions there. other ways to get involved include reading the newsgroups and status updates .

note: mozilla.org makes these builds available for testing purposes only. we provide no end-user support.

suggestions for this page to gerv
copyright (c) 1998-2003 the mozilla organization
last modified july 21, 2003
document history
edit this page (or via cvs) 
