Skip to content

Commit e790a52

Browse files
authored
Major changes, new Contribute section
1 parent 91c4eb4 commit e790a52

File tree

1 file changed

+26
-32
lines changed

1 file changed

+26
-32
lines changed

README.md

Lines changed: 26 additions & 32 deletions
Original file line numberDiff line numberDiff line change
@@ -1,45 +1,39 @@
1-
# Firefox Developer Tools
2-
31
Welcome! Firefox DevTools is a set of tools for inspecting and editing web code. We work closely with the community and are always happy to welcome new contributors.
42

53
Help us maintain an inclusive environment by following our [code of conduct](CODE_OF_CONDUCT.md).
64

7-
## Documentation
8-
9-
* [Contributor documentation](http://docs.firefox-dev.tools/).
10-
* [MDN DevTools user guides](https://developer.mozilla.org/en-US/docs/Tools).
11-
12-
## News and demos
13-
14-
We publish news and updates to two blogs:
15-
16-
* [Nightly](https://blog.nightly.mozilla.org/tag/devtools/) for features newly added to Firefox Nightly. This is where we request feedback from early adopters.
17-
* [Hacks](https://hacks.mozilla.org/category/developer-tools/) for when features reach more stable versions of Firefox.
5+
# How to Contribute
186

19-
You're more than encouraged to talk, write articles, or [make demos](https://github.com/firefox-devtools/demos) about the tools. Let us know 🙂
7+
## Code & Design
8+
- The DevTools codebase is made of HTML, CSS, and JavaScript.
9+
- Read the [contributor docs](http://docs.firefox-dev.tools/) to get started.
10+
- Check out our [Good First Bugs](https://bugs.firefox-dev.tools/?easy&tool=all) to see what’s available.
11+
- Our [UX repository](https://github.com/firefox-devtools/ux) has issues that need design ideas and critique.
12+
- Join our [Slack](https://devtools-html-slack.herokuapp.com/) to hang out and ask questions.
2013

21-
## Getting in touch
14+
## Give Feedback
15+
- On [Twitter](https://twitter.com/FirefoxDevTools), we often ask for feedback on brand new designs and prototypes.
16+
- Use [Bugzilla](https://bugzilla.mozilla.org/enter_bug.cgi?product=DevTools) to file bugs and enhancement requests.
17+
- Help us foxfood new features by using pre-release builds:
18+
- [Firefox DevEdition](https://www.mozilla.org/firefox/developer/) (based on beta, recommended for most)
19+
- [Firefox Nightly](https://www.mozilla.org/firefox/channel/desktop/#nightly) (updated twice daily)
2220

23-
* Bug reports or feature requests:
24-
* [File bugs in Mozilla's Bugzilla](https://bugzilla.mozilla.org/enter_bug.cgi?product=DevTools) (please respect the [etiquette](https://bugzilla.mozilla.org/page.cgi?id=etiquette.html))
25-
* or under each repository in [firefox-devtools](https://github.com/firefox-devtools) for code in GitHub.
26-
* Report vulnerabilities to `[email protected]`. [More info](https://www.mozilla.org/en-US/security/#For_Developers).
27-
* [List of open bugs](http://bugs.firefox-dev.tools/). Might be interesting if you want to contribute.
28-
* [DevTools forum](https://discourse.mozilla-community.org/c/devtools).
29-
* [Mailing list](https://groups.google.com/forum/#!forum/mozilla.dev.developer-tools).
30-
* [Weekly status updates](https://docs.google.com/document/d/1lxy0IzUM14dYACk_q862vVYwpU1AA4NQVrUNAm6uc-8/)
31-
* Chat:
32-
* Join the [Firefox DevTools Slack](https://devtools-html-slack.herokuapp.com/),
33-
* or IRC: `#devtools` channel on `irc.mozilla.org`.
34-
* Twitter: [@FirefoxDevTools](https://twitter.com/FirefoxDevTools).
21+
## Write
22+
- We love to see blog posts, talks, and [demos](https://github.com/firefox-devtools/demos) about DevTools! Message us on [Slack](https://devtools-html-slack.herokuapp.com/) for help.
23+
- Improve our [contributor docs](http://docs.firefox-dev.tools/) by creating a [pull request](https://github.com/mozilla/gecko-dev/tree/master/devtools), or edit our [user docs](https://developer.mozilla.org/en-US/docs/Tools).
24+
- Answer questions others have on Slack and other channels.
3525

36-
## Processes
26+
# Stay Updated
3727

38-
Most changes will be done via either the "pick a bug and send a patch" or "send a PR" processes.
28+
* [Hacks blog](https://hacks.mozilla.org/category/developer-tools/)
29+
* [Twitter: @FirefoxDevTools](https://twitter.com/FirefoxDevTools)
30+
* [YouTube: Mozilla Developer](https://www.youtube.com/channel/UCh5UlGiu9d6LegIeUCW4N1w)
31+
* [Discourse forum](https://discourse.mozilla-community.org/c/devtools)
32+
* [Mailing list](https://groups.google.com/forum/#!forum/mozilla.dev.developer-tools)
3933

40-
For substantial changes, we ask that a "request for comment" (RFC) document is provided first, so we can examine what the implications of a change will be. Here is [how to follow the RFC process](https://github.com/firefox-devtools/rfcs/).
34+
# About DevTools
4135

42-
### People and modules
36+
## People and modules
4337

4438
The tools are broadly divided into panels. Each panel has one or more owners, who mostly work(s) on that panel and are the best people to ask if you have specific questions about the code.
4539

@@ -50,7 +44,7 @@ The tools are broadly divided into panels. Each panel has one or more owners, wh
5044
* Debugger: jlast, dwalsh, loganfsmyth
5145
* DOM: honza
5246
* Font Editor: rcaliman, gl, pbro
53-
* Framework: Browser integration, toolbox and test infrastructure: bgrins, ochameau, honza
47+
* Framework: Browser integration, toolbox, and test infrastructure: bgrins, ochameau, honza
5448
* Inspector: gl, pbro, jdescottes, rcaliman, mtigley, bwerth, mikeratcliffe
5549
* JSON Viewer: honza
5650
* Memory: gregtatum

0 commit comments

Comments
 (0)