Platform/GFX/Contribute: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
No edit summary
Line 10: Line 10:


To get started, you need to do these few things, in any order:
To get started, you need to do these few things, in any order:
* Make your own build of Firefox, from the source code of the development version (mozilla-central). [https://developer.mozilla.org/En/Simple_Firefox_build This page] explains how to do that.
* '''Make your own build''' of Firefox, from the source code of the development version (mozilla-central). [https://developer.mozilla.org/En/Simple_Firefox_build This page] explains how to do that.
* Find a task to work on. [http:// Use this search] to find a mentored bug to work on. See below the list of [[#Current_projects|current projects]].
* Find a task to work on. [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=runnamed&namedcmd=GFX%20Mentor%20Bugs&list_id=1588080 Use this search] to '''find a mentored bug''' to work on. See below the list of [[#Current_projects|current projects]].
* Register an account on [https://bugzilla.mozilla.org/ Bugzilla].
* '''Register''' an account on [https://bugzilla.mozilla.org/ Bugzilla].


= Contact =
= Contact =
Line 18: Line 18:
* '''IRC channel:''' #gfx on [https://wiki.mozilla.org/IRC Mozilla IRC] (irc.mozilla.org)
* '''IRC channel:''' #gfx on [https://wiki.mozilla.org/IRC Mozilla IRC] (irc.mozilla.org)
* '''Weekly conference calls:''' we have [[Platform/GFX#Team_Meetings|weekly team meetings]] taking place over the phone/videoconference, usually on Mondays 2:30 pm Pacific time. Everyone is welcome to attend them. Dial-in details, agendas and minutes are given on each meeting's page, on that page. If you want to talk about something, please first edit the agenda.
* '''Weekly conference calls:''' we have [[Platform/GFX#Team_Meetings|weekly team meetings]] taking place over the phone/videoconference, usually on Mondays 2:30 pm Pacific time. Everyone is welcome to attend them. Dial-in details, agendas and minutes are given on each meeting's page, on that page. If you want to talk about something, please first edit the agenda.
* Once you've found a mentored bug you would like to work on, adding a comment on that bug is a good way to get in contact with the mentor.
* Once you've found a '''[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=runnamed&namedcmd=GFX%20Mentor%20Bugs&list_id=1588080 mentored bug]''' that you would like to work on, adding a comment on that bug is a good way to get in contact with the mentor.
* For the month of November, the monthly Gfx team contact is [[Platform/GFX/Meet#bjacob|bjacob]]
* For the month of November, the '''Monthly Gfx team contact''' is [[Platform/GFX/Meet#bjacob|bjacob]]
* [https://bugzilla.mozilla.org/ Bugzilla] is what we use for most development discussion.
* '''Development discussion''' mostly happens on [https://bugzilla.mozilla.org/ Bugzilla].
* For serious questions or discussion that doesn't fit on Bugzilla, there is the [https://lists.mozilla.org/listinfo/dev-platform dev-platform] mailing list.
* The '''mailing list''' to use for serious discussion that doesn't fit on Bugzilla, is [https://lists.mozilla.org/listinfo/dev-platform dev-platform].
* Don't miss the [[Platform/GFX/Meet|Meet the Gfx team]] page!
* Don't miss the [[Platform/GFX/Meet|Meet the Gfx team]] page!


Line 27: Line 27:


Here's a quick overview of the tools we're using:
Here's a quick overview of the tools we're using:
* [https://bugzilla.mozilla.org/ Bugzilla] is where most development discussion takes place. Here's some [https://developer.mozilla.org/en/Bugzilla Bugzilla documentation].
* '''[https://bugzilla.mozilla.org/ Bugzilla]''' is where most development discussion takes place. Here's some [https://developer.mozilla.org/en/Bugzilla Bugzilla documentation].
* [https://developer.mozilla.org/en/Mercurial Mercurial] is the SCM (source code management) tool we're using for [https://developer.mozilla.org/en/mozilla_source_code_%28mercurial%29 Mozilla source code].
* '''[https://developer.mozilla.org/en/Mercurial Mercurial]''' is the SCM (source code management) tool we're using for [https://developer.mozilla.org/en/mozilla_source_code_%28mercurial%29 Mozilla source code].
* [https://developer.mozilla.org/en/Mercurial_Queues Mercurial Queues] is not mandatory, but is a very useful tool to work with patches.
* '''[https://developer.mozilla.org/en/Mercurial_Queues Mercurial Queues]''' is not mandatory, but is a very useful tool to work with patches.
* Languages: Gecko source code is C++, the build-system is GNU Makefiles, unit tests are typically JavaScript/HTML.
* '''Languages:''' Gecko source code is C++, the build-system is GNU Makefiles, unit tests are typically JavaScript/HTML.
* Compilers: we currently use Visual Studio on Windows, and GCC on other platforms. We have a plan to start building with Clang/LLVM wherever we can, starting on Mac.
* '''Compilers:''' we currently use Visual Studio on Windows, and GCC on other platforms. We have a plan to start building with Clang/LLVM wherever we can, starting on Mac.
* Patch review: Once you have made a patch for a bug, attach it to the bug and [https://developer.mozilla.org/En/Developer_Guide/How_to_Submit_a_Patch#Getting_Reviews request review] for it. It's just a matter of setting 'review?' on it and selecting an appropriate reviewer.
* '''Patch review:''' Once you have made a patch for a bug, attach it to the bug and [https://developer.mozilla.org/En/Developer_Guide/How_to_Submit_a_Patch#Getting_Reviews request review] for it. It's just a matter of setting 'review?' on it and selecting an appropriate reviewer.
Confirmed users
753

edits

Navigation menu