43
edits
(→Communication: Participate in Spec Development: Make the communication bit of spec development a bit more fleshed out) |
(→Writing Patches and asking for Code Reviews: Added Landing A Patch section) |
||
(One intermediate revision by one other user not shown) | |||
Line 47: | Line 47: | ||
You can participate in their development through their corresponding GitHub repository (e.g., watching the entire repository, subscribing to relevant issues, filing new issues, etc.). Feel free to chime in as you please and share your views, but confer with colleagues before expressing opinions on behalf of Mozilla. | You can participate in their development through their corresponding GitHub repository (e.g., watching the entire repository, subscribing to relevant issues, filing new issues, etc.). Feel free to chime in as you please and share your views, but confer with colleagues before expressing opinions on behalf of Mozilla. | ||
=== Mechanics: WebIDL === | === Mechanics: Web IDL (WebIDL) === | ||
[https://heycam.github.io/webidl/ Web IDL] defines the APIs that Firefox exposes to JavaScript content. | |||
' | MDN's [https://developer.mozilla.org/en-US/docs/Mozilla/WebIDL_bindings WebIDL bindings] has detailed information on the setup in Firefox. | ||
=== Mechanics: Testing === | === Mechanics: Testing === | ||
Line 117: | Line 115: | ||
=== Submitting | === Submitting A Patch For Review === | ||
We use Phabricator for code reviews. Check out the [https://moz-conduit.readthedocs.io/en/latest/phabricator-user.html user guide]. | We use Phabricator for code reviews. Check out the [https://moz-conduit.readthedocs.io/en/latest/phabricator-user.html user guide]. | ||
=== Landing A Patch === | |||
== Doing Code Reviews == | == Doing Code Reviews == |
edits