File!

• Make sure you search for an existing bug before you file!
• How to file bugs - you should be familiar with Bugzilla (the bug tracker) and mozilla.org's bug guidelines.
• Please read "About Networking" before you file.

Analyze!

Submitted bugs

status (UNCONFIRMED or NEW), owned by default, and untargeted

Save engineers time with 4 easy steps:

1. Check for duplicate
2. Fix summary if needed
3. Confirm "steps"
4. +clean-report keyword

"qawanted" - take over the qa of a bug

Fix!

clean-report

ready for engineering

fasttrack

(crash dataloss hang smoketest regression perf)

Testing!

• Where are the test suites? Includes Core, File and FTP.
• "testcase" keywords mark bugs that are in tests.
• cc=testcase@mail.packetgram.com contains testcase that needs to be added to test suites

I want to help with projects

• Issue management - turning the incoming flow of bugs into a precise list of problems
• Feature ownership - take qa ownership of bugs or features
• Test case development - making lists of tests for developers
• Janitorial services: bug cleanup projects
  (old milestone keywords)

Documentation

• Guide to Networking Preferences
  
• Autodial for Windows NT
• HTTP Logging
  
• Internet Keywords
• Domain Guessing
• Port Blocking
• Proxy Auto Config (.pac)
• No Proxy For configuration

Troubleshooting

• View HTTP and HTML Source