Mobile/Get Involved: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
== Get Involved ==
= Get Involved =


'''This is page is under construction, do not share it just yet!'''
'''This is page is under construction, do not share it just yet!'''
Line 7: Line 7:
== Contributing ==
== Contributing ==


Firefox Mobile is developed by a community of developers, designers, QA engineers, and more. We're currently focused on making Firefox rock on Android phones and tablets. We're always looking for new contributors to join us!
Firefox Mobile is developed by the Mozilla community. We're currently focused on making Firefox rock on Android phones and tablets. We're always looking for new contributors to join us!


If you still feel that you don't know where to start after reading this page, feel free to ping us on IRC, we can probably give you some ideas. We're always looking for ways to improve this page to make it easier to start contributing to Firefox Mobile. Suggestions and general feedback are more than welcome.
If you still feel that you don't know where to start after reading this page, feel free to [[#Communication|ping us]] on IRC, we can probably give you some ideas. We're always looking for ways to improve this page to make it easier to start contributing to Firefox Mobile. Suggestions and general feedback are more than welcome.


=== Hacking ===
=== Hacking ===
Line 16: Line 16:


If you're interested in hacking on the UI bits of Firefox Mobile, the front-end team has prepared a [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=prod%3Afennec%20sw%3Amentor%20kw%3Ahelpwanted&list_id=1448137 list of bugs] that are good for first-time contributors. Each bug report in this list has an assigned mentor (see "Whiteboard" field). The mentor will help you get the necessary information to understand the issue, point out relevant parts of the code to look at, etc.
If you're interested in hacking on the UI bits of Firefox Mobile, the front-end team has prepared a [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=prod%3Afennec%20sw%3Amentor%20kw%3Ahelpwanted&list_id=1448137 list of bugs] that are good for first-time contributors. Each bug report in this list has an assigned mentor (see "Whiteboard" field). The mentor will help you get the necessary information to understand the issue, point out relevant parts of the code to look at, etc.
Before starting to work on bug, it's a good idea to add a comment to the bug report letting the mentor know that you want to work on it. If you're unsure whether to take a certain bug or not, you can always [[#Communication|talk to us]].


=== Testing ===
=== Testing ===
Line 21: Line 23:
If you want to help us finding issues on latest Fennec releases, a good way to start is joining the [http://quality.mozilla.org/ QA team] during the test days that focused on Mobile topics. Keep an eye on their [http://quality.mozilla.org/events/ events page] to know about future test days.
If you want to help us finding issues on latest Fennec releases, a good way to start is joining the [http://quality.mozilla.org/ QA team] during the test days that focused on Mobile topics. Keep an eye on their [http://quality.mozilla.org/events/ events page] to know about future test days.


However, you don't have to wait for the test days to start helping. Feel free to [https://bugzilla.mozilla.org/enter_bug.cgi?product=Fennec report bugs] or to directly talk to us on IRC about the bugs you find. The [https://developer.mozilla.org/en/bug_writing_guidelines bug writing guidelines] has useful information on how to file accurate bug reports.
However, you don't have to wait for the test days to start contributing. Feel free to [https://bugzilla.mozilla.org/enter_bug.cgi?product=Fennec report bugs] or to directly talk to us on IRC about the bugs you find. The [https://developer.mozilla.org/en/bug_writing_guidelines bug writing guidelines] has useful information on how to file accurate bug reports.


== Communication ==
== Communication ==


The simplest way to keep in touch with the Mobile team is to hang out on the #mobile channel at irc.mozilla.org. We're always there, in different timezones. If you're looking for people from specific areas, or looking for your mentor, here are a few nicks you can ping:
The simplest way to keep in touch with the Mobile team on a daily basis is to hang out on the #mobile channel at irc.mozilla.org. We're always there, in different timezones. If you want to talk to people from specific areas or have any questions, here are a few people you can ping:


  * Front-end: bnicholson, lucasr, mfinkle, mbrubeck, sriram, vingtetun, wesj
  * Front-end: bnicholson, lucasr, mfinkle, mbrubeck, sriram, vingtetun, wesj

Revision as of 17:10, 7 October 2011

Get Involved

This is page is under construction, do not share it just yet!

This page is the place to learn how to start contributing to Firefox Mobile, also known as Fennec. We hope this page will help you become an active member of our community. If you're looking for other ways to contribute to Mozilla, have a look at Mozilla's global page for new contributors.

Contributing

Firefox Mobile is developed by the Mozilla community. We're currently focused on making Firefox rock on Android phones and tablets. We're always looking for new contributors to join us!

If you still feel that you don't know where to start after reading this page, feel free to ping us on IRC, we can probably give you some ideas. We're always looking for ways to improve this page to make it easier to start contributing to Firefox Mobile. Suggestions and general feedback are more than welcome.

Hacking

Setting up a development environment for Firefox Mobile is relatively easy. Just follow our build instructions and you'll be ready to start hacking after a couple of hours—mostly waiting for everything to compile.

If you're interested in hacking on the UI bits of Firefox Mobile, the front-end team has prepared a list of bugs that are good for first-time contributors. Each bug report in this list has an assigned mentor (see "Whiteboard" field). The mentor will help you get the necessary information to understand the issue, point out relevant parts of the code to look at, etc.

Before starting to work on bug, it's a good idea to add a comment to the bug report letting the mentor know that you want to work on it. If you're unsure whether to take a certain bug or not, you can always talk to us.

Testing

If you want to help us finding issues on latest Fennec releases, a good way to start is joining the QA team during the test days that focused on Mobile topics. Keep an eye on their events page to know about future test days.

However, you don't have to wait for the test days to start contributing. Feel free to report bugs or to directly talk to us on IRC about the bugs you find. The bug writing guidelines has useful information on how to file accurate bug reports.

Communication

The simplest way to keep in touch with the Mobile team on a daily basis is to hang out on the #mobile channel at irc.mozilla.org. We're always there, in different timezones. If you want to talk to people from specific areas or have any questions, here are a few people you can ping:

* Front-end: bnicholson, lucasr, mfinkle, mbrubeck, sriram, vingtetun, wesj
* Platform: blassey, Cwiiis, dougt, gcp, snorp
* QA: AaronMT, kbrosnan, nhirata, tchung
* Design: briandils, ibarlow, madhava