Changes

Jump to: navigation, search

Bugzilla:Developers

287 bytes added, 16:52, 2 February 2008
Add link to a list of [Good Intro Bug] bugs. Also reverse steps 2 and 3, since they make more sense that way.
1. [[Bugzilla:Developers:Introduction|Introduce yourself on the developers mailing list]]
2. If you don't know what you'd like to work on, look at the [[Bugzillahttp:Communicate|Get in communication with the Bugzilla developers//tinyurl.com/2mmepu list of bugs we've marked as being good for newcomers]], and talk about . If you already know what you want to dowork on, first [https://bugzilla.mozilla.org/query. This makes cgi?product=Bugzilla&resolution=---&format=advanced check if a bug has already been filed for it easy for us to tell you "Oh], weand then check that bug're already working on that, you can help!" or "Oh, the best way to do that would be..s [[Bugzilla:Priority_System|priority]]."
3. If a bug has already been filed for what you want to do, check its [[Bugzilla:Priority_SystemCommunicate|priorityGet in communication with the Bugzilla developers]], and talk about what you want to do. This makes it easy for us to tell you "Oh, we're already working on that, you can help!" or "Oh, the best way to do that would be..."
4. Check out the latest Bugzilla code from CVS. You can see instructions for how to do this on the [http://www.bugzilla.org/download/#cvs Bugzilla download page]. You always want to work against the latest CVS code of Bugzilla, not a released version, if you're writing patches that you want us to accept.
Canmove, confirm
345
edits

Navigation menu