DevTools/GetInvolved: Difference between revisions
(ffdevtools on uservoice is no longer available) |
(→Resources: Update.) |
||
| Line 66: | Line 66: | ||
* [https://developer.mozilla.org/en-US/docs/Mercurial_FAQ#How_can_I_generate_a_patch_for_somebody_else_to_check-in_for_me.3F How to format patches] | * [https://developer.mozilla.org/en-US/docs/Mercurial_FAQ#How_can_I_generate_a_patch_for_somebody_else_to_check-in_for_me.3F How to format patches] | ||
* [http://dxr.mozilla.org/mozilla-central/source/ DXR Code Search] | * [http://dxr.mozilla.org/mozilla-central/source/ DXR Code Search] | ||
* [https:// | * [https://mozilla-version-control-tools.readthedocs.io/en/latest/hgmozilla/index.html Mercurial for Mozillians] | ||
* [https://developer.mozilla.org/en-US/docs/Developer_Guide/mach mach] | * [https://developer.mozilla.org/en-US/docs/Developer_Guide/mach mach] | ||
* [http://flailingmonkey.com/bugzilla-tips-hacks-and-etiquette Bugzilla Tips, Hacks and Etiquette] | * [http://flailingmonkey.com/bugzilla-tips-hacks-and-etiquette Bugzilla Tips, Hacks and Etiquette] | ||
Revision as of 07:50, 29 September 2016
This page is the place to learn how to start contributing to the Firefox Developer Tools.
The Firefox Developer Tools are developed by the Mozilla community. We focus on building tools that make life easier for web (and mobile web) developers, addon developers, and Firefox developers. We hope the information on this page will help you become an active member of our community!
If after reading this wiki page, you still aren't sure what you're next steps are, reach out to us on IRC.
Communication
- Twitter: @FirefoxDevTools
- Mailing list: dev-developer-tools
- Blog (shared): Mozilla Hacks
- Weekly phone calls
On top of that, we make heavy use of IRC chat in our day to day development. If you haven't used IRC before, check out the guide to getting started with IRC.
We hang out in the #devtools channel at irc://irc.mozilla.org/devtools
If you have questions about a specific part of the code, here are some good people to ping:
- about:debugging: jdescottes
- Animation Inspector: pbro
- Canvas Debugger: vporof
- Console: bgrins, linclark
- Debugger: ejpbruel, jlongster
- Developer Toolbar: jwalker, mikeratcliffe
- DOM: honza
- Framework, toolbox: bgrins, jryans, honza, jlong
- Inspector: pbro, gl, zer0, tromey
- JSON Viewer: honza
- Memory: fitzgen
- Network Monitor: honza
- Performance: gtatum
- Responsive Design: jryans, gl
- Scratchpad: jdescottes
- Style Editor: gl
- Storage Inspector: mikeratcliffe
- UI/UX: helenvholmes
- Web Audio Editor: jsantell
- WebIDE: jryans, ochameau, janx
Reporting Bugs and Requesting Features
To report a bug/usability papercut/smaller feature/etc, file a bug in the Developer Tools component on Mozilla's Bugzilla.
If you have an idea for a new feature, you can post it to the mailing list where Firefox DevTools team members are available to answer questions and respond to comments.
Mentored and Good First Bugs
The firefox-dev.tools site can help you find good first bugs and/or mentored bugs.
If you want to pick one of these up, feel free to ask for help in attacking the bug right in the bug itself, in #devtools on irc.mozilla.org, or on the dev-developer-tools mailing list!
One more useful link: all open developer tools bugs might have other items you'd find interesting to work on.
Don't hesitate to ask to be mentored even on bugs that don't have a mentor assigned yet.
Hacking
If you are ready to get the source code and start working on DevTools, check out our guide to hacking DevTools.
Resources
Here's a list of resources that you may find useful for hacking on DevTools. Feel free to add more if you find things are missing!