Development:Contributor Overview

This page will be one of the main pages of the dev-wiki; it will walk a new contributor through the process in an overview fashion, pointing to the detailed information on each part in the separate docs, e.g. building/setting up your dev environment, choosing a bug, coding, getting reviews.

Things in the lists below the text are the pages we should link to

Setting up your development environment

Text text text

• Development:Building
• Development:Building:Intel

Choosing a bug

Something that bothers you, something on good first bugs, something that needs to be fixed...

Good First Bug vs. Triage Priority

The "Good First Bugs" list is a list of "bugs" (problems or feature requests) that are good entry points for new Camino developers, not necessarily a list of the bugs that need to be fixed most urgently. A bug's priority is determined (roughly) by the severity field, the priority field (used generally by developers to prioritize lists of bugs assigned to them), the target milestone, and the blocking flags. For instance, bugs with a target milestone of Camino 1.1 are generally most important at the moment, and ones with higher severity (or a camino1.1+ or camino1.1? flag) are the most important of those.

• Bugs Targeted at Camino 1.1
• Somewhere we should have an "Unofficial" Roadmap for Developers with bugs or categories of bugs for a release, like the Firefox PRD but more humane, to supplement the "target milestone" queries--a more-official version of Sam's Roadmap or Smokey's 1.1 list
• Stuff we'd like fixed: Development:Good Bugs and Projects

Working on a bug

• When to take a bug, and how to do it (some of this is in the existing cbo dev pages)
• Bugs with status NEW whose assignee is nobody@mozilla.org, mikepinkerton@mac.com, and sfraser_bugs@smfr.org are fair game
• Ask first before taking a bug with status NEW with any other assignee, or before taking a bug with status ASSI.

• Development:Good Bugs and Projects
• Roadmap
• etc

Coding a fix

Text, text, text

• Development:Reviewing (prob needs a new page name)

Getting Code Review and Checkin

Text, text, text

• Development:Reviewing (other parts of the page, or split the page in 2)