DevTools/GetInvolved: Difference between revisions
(Added firefox-dev.tools link) |
(Updated the contact list as per https://docs.google.com/spreadsheets/d/10i30CFUPJM7snz0xX3czFJeBh2tNwjwjtI409DQw3x0/edit#gid=0) |
||
| Line 19: | Line 19: | ||
If you have questions about a specific part of the code, here are some good people to ping: | If you have questions about a specific part of the code, here are some good people to ping: | ||
* '''Canvas Debugger''': vporof | * '''about:debugging''': janx | ||
* '''Console''': | * '''Animation Inspector''': pbro | ||
* '''Debugger''': | * '''Canvas Debugger''': vporof | ||
* '''Developer Toolbar''': jwalker | * '''Console''': bgrins, linclark | ||
* ''' | * '''Debugger''': ejpbruel, jlongster | ||
* '''Inspector''': | * '''Developer Toolbar''': jwalker, mikeratcliffe | ||
* '''Memory''': fitzgen | * '''Framework, toolbox''': bgrins, jryans, honza, jlong | ||
* '''Network Monitor''': | * '''Inspector''': pbro, gl, zer0, tromey | ||
* '''Performance''': vporof | * '''JSON Viewer''': honza | ||
* '''Responsive Design''': jryans, | * '''Memory''': fitzgen | ||
* '''Scratchpad''': fitzgen | * '''Network Monitor''': honza | ||
* '''Style Editor''': | * '''Performance''': jsantell, vporof | ||
* '''Responsive Design''': jryans, gl | |||
* '''Scratchpad''': fitzgen | |||
* '''Style Editor''': gl | |||
* '''Storage Inspector''': mikeratcliffe | * '''Storage Inspector''': mikeratcliffe | ||
* '''Web Audio Editor''': jsantell | |||
* '''Web Audio Editor''': jsantell | * '''WebGL Shader Editor''': vporof | ||
* '''WebGL Shader Editor''': vporof | * '''WebIDE''': jryans, ochameau, janx | ||
* '''WebIDE''': jryans | |||
== Reporting Bugs and Requesting Features == | == Reporting Bugs and Requesting Features == | ||
Revision as of 12:26, 7 March 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
- Feedback channel: http://mzl.la/devtools
- 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: janx
- Animation Inspector: pbro
- Canvas Debugger: vporof
- Console: bgrins, linclark
- Debugger: ejpbruel, jlongster
- Developer Toolbar: jwalker, mikeratcliffe
- Framework, toolbox: bgrins, jryans, honza, jlong
- Inspector: pbro, gl, zer0, tromey
- JSON Viewer: honza
- Memory: fitzgen
- Network Monitor: honza
- Performance: jsantell, vporof
- Responsive Design: jryans, gl
- Scratchpad: fitzgen
- Style Editor: gl
- Storage Inspector: mikeratcliffe
- Web Audio Editor: jsantell
- WebGL Shader Editor: vporof
- 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 (or want to see what ideas have been submitted so far and their status), you can propose it on uservoice.
Otherwise, you can also suggest larger features by posting them to the mailing list where we can flesh the feature out as a community.
Mentored and Good First Bugs
The firefox-dev.tools site can help you find good-first and/or mentored bugs (alternatively, you can find these list on bugzilla: good-first, mentored).
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!