DevTools/GetInvolved: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Reorder framework list to match priorities)
(Removed the list of resources. This was just a random list of links (some of them to blog posts) that I think was just plain confusing, surely not helping.)
Line 45: Line 45:
To report a bug/usability papercut/smaller feature/etc, [https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&component=Developer%20Tools file a bug in the Developer Tools component] on Mozilla's Bugzilla.
To report a bug/usability papercut/smaller feature/etc, [https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&component=Developer%20Tools file a bug in the Developer Tools component] on Mozilla's Bugzilla.


If you have an idea for a new feature, you can [[#Communication|post it to the mailing list]] where Firefox DevTools team members are available to answer questions and respond to comments.
Please be aware that we have a [https://bugzilla.mozilla.org/page.cgi?id=etiquette.html Bugzilla Etiquette].
 
If you have an idea for a new feature, you can [[#Communication|post it to the mailing list]] or discuss on the [https://discourse.mozilla-community.org/c/devtools DevTools Discourse category]


== Mentored and Good First Bugs ==
== Mentored and Good First Bugs ==
Line 62: Line 64:


If you are ready to get the source code and start working on it, check out our [[DevTools/Hacking|guide to working on DevTools]].
If you are ready to get the source code and start working on it, check out our [[DevTools/Hacking|guide to working on DevTools]].
== Resources ==
Here's a list of resources that you may find useful. Feel free to add more if you find things are missing!
* [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]
* [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]
* [http://flailingmonkey.com/bugzilla-tips-hacks-and-etiquette Bugzilla Tips, Hacks and Etiquette]
* [http://blog.margaretleibovic.com/post/36893756730/bugzilla-101 Bugzilla 101]
* [http://www.mozilla.org/hacking/commit-access-policy/ Commit access policy]
* [http://mozillians.org Mozillians Directory]
* [https://wiki.mozilla.org/ReleaseEngineering/TryServer Try Server]
* [https://wiki.mozilla.org/DevTools/Hacking Coding for DevTools]

Revision as of 11:12, 16 March 2017

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, add-on 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 your next steps are, reach out to us on IRC.

Communication

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, ochameau
  • Animation Inspector: gl, pbro, daisuke
  • Canvas Debugger: <unmaintained>
  • Console: bgrins, nchevobbe
  • Debugger: jlast
  • Developer Toolbar: jwalker, mikeratcliffe
  • DOM: honza
  • Framework: Browser integration, toolbox and test infrastructure: jryans, bgrins, ochameau, honza
  • Inspector: gl, pbro, zer0, jdescottes, tromey
  • JSON Viewer: honza
  • Memory: gregtatum
  • Network Monitor: honza, rickychien, gasolin
  • Performance: gregtatum
  • Remote protocol and server infrastructure: jryans, ochameau
  • Responsive Design Mode: jryans, zer0
  • Scratchpad: jdescottes
  • Shader Editor: <unmaintained>
  • Style Editor: gl
  • Storage Inspector: mikeratcliffe
  • Themes: bgrins, ntim
  • Web Audio Editor: <unmaintained>
  • WebIDE: jryans, ochameau

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.

Please be aware that we have a Bugzilla Etiquette.

If you have an idea for a new feature, you can post it to the mailing list or discuss on the DevTools Discourse category

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.

Working on the code

If you are ready to get the source code and start working on it, check out our guide to working on DevTools.

Retrieved from "https://wiki.allizom.org/index.php?title=DevTools/GetInvolved&oldid=1165837"