Bugzilla:Developers: Difference between revisions

Bugzilla:Developers (view source)

287 bytes added , 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.

canmove, Confirmed users

345

edits

@@ Line 3: / Line 3: @@
 . [[Bugzilla:Developers:Introduction|Introduce yourself on the developers mailing list]]
-. [[Bugzilla:Communicate|Get 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..."
+. If you don't know what you'd like to work on, look at the [http://tinyurl.com/2mmepu list of bugs we've marked as being good for newcomers]. If you already know what you want to work on, first [https://bugzilla.mozilla.org/query.cgi?product=Bugzilla&resolution=---&format=advanced check if a bug has already been filed for it], and then check that bug's [[Bugzilla:Priority_System|priority]].
-. If a bug has already been filed for what you want to do, check its [[Bugzilla:Priority_System|priority]].
+. [[Bugzilla:Communicate|Get 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..."
 . 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.