DevTools/DevProcess
Developer Tools Development Process
The Web Console feature in Firefox 4 was developed like any other Firefox feature and lives in mozilla-central. Post-Firefox 4 developer tools will generally start life as Jetpacks, so they will be easier for web developers to contribute to and use as samples and starting points for their own tools.
Bug Tracking and Code Review
Regardless of where the code lives, we will use Bugzilla for tracking our bugs and features. Any projects of ours that have their source hosted on GitHub will not use the GitHub bug tracker.
Projects that are hosted on GitHub will use the GitHub code review ("pull request") functionality for reviews. To make it easy for people to follow along at home, links will be created from the relevant bugs in Bugzilla to the pull requests that take care of them. Atul has written a command line tool that can take care of this for you (link?).
Developer tool reviews will be performed by (who?). We'd like to maximize the value of the review per time spent, so we want to avoid a lot of back and forth. Reviewers should give an r+ (with changes as noted in the comments) as long as the patch is not in need of significant rework.
Of course, if we find bugs creeping into the patches post-review, we'll re-evaluate this.
Where to Find the Code
Authoritative repositories for the tools will live on GitHub in the Mozilla organization: http://github.com/mozilla
The Developer Tools SDK will live (where?).
Current devtools repositories:
- Skywriter – Embeddable, customizable browser-based code editor
Parts that Ship with Firefox
TBD: how are parts frozen and baked into the product? How does iteration on these happen after?