Good First Bugs
Take a look through LXR, and you'll realize that Mozilla's source code is a big place. Where's a good place to start? Reports in Bugzilla can be deceptive, deceptively hard... or deceptively easy. So we've compiled a list of pointers — from the experts. There's plenty to do, and we sure could use the help. Here are some fixes that are straightforward; they just need some time and attention:
- Convert weird, ugly and inefficient method signatures to more natural C++ method
signatures. It's really improved code readability, reduced code size, and sped up
preformance. It's kind of tedious but it's extremely valuable and will help you
learn the way around the codebase. We've done a lot, but there's a lot more to do.
roc is willing to work closely with anyone with reasonable C++ experience to get
them started on this. Just send an e-mail to
originalURIsafe to use
- This needs some comment changes, then looking through all implementations of
GetOriginalURI/SetOriginalURI and ensuring they do the right thing. Minimal C++ knowledge needed.
- Switch code to using the new preference API
- There are several bugs blocking this tracking bug that cover switching to the new
nsIPrefServiceAPI for accessing preferences. The idea is to eventually get rid of the old
nsIPrefAPI. Minimal C++ knowledge needed. Mail
- Make the Personal Security Manager not reinvent the wheel
- The Personal Security Manager has some code that reads data from the network into a buffer. This code could be removed in favor of existing methods to do this in the networking library. The bug has a pointer to a patch that does this in another case and another to the code that needs changing. Some C++ knowledge needed.
- Fix charset handling for the
text/xmltype specifies some rather odd charset parameter handling. To implement this, we need to switch internal Mozilla users of text/xml to application/xml first, then make a minor change to the
XMLDocumentcode. The bug should have details. Some C++ knowledge needed. Mail
- Warn on use of
- This is a case of needing a warning when a method we don't actually implement is called. The bug has
some pointers to where to look for examples of logging warnings. Mail
Also of interest may be the list of bugs marked as [good first bug] in Bugzilla. Note, however, that these bugs may not have as much info as the bugs listed above.
Not up for coding yet? Join the Bugathon and help save Gecko engineers from imminent doom.