15
edits
Participation/India/Android Coding Team: Difference between revisions
Jump to navigation
Jump to search
Participation/India/Android Coding Team (view source)
Revision as of 07:05, 4 October 2015
, 4 October 2015Added resource+Approach
(First pass) |
(Added resource+Approach) |
||
| Line 10: | Line 10: | ||
The Firefox for Android team is doing great work, but are focusing on continuing to evolve the product. However, they are always in need of support, not just in building out features but on improving the code base in general to make it more performant. | The Firefox for Android team is doing great work, but are focusing on continuing to evolve the product. However, they are always in need of support, not just in building out features but on improving the code base in general to make it more performant. | ||
The goal of this project is to make fennec (Firefox for Android) slimmer leaner and faster. And that we plan to achieve by the following action points | |||
* Make sure all the resources that are used in the android package are device optimized | |||
* By default load only the always used features and locales (language packs) | |||
* Make some of the features of the browser on demand which will download to the users device only when they will need it. The download will be seamless, without any user intervention | |||
One of the most | |||
== Desired Outcome == | == Desired Outcome == | ||
| Line 29: | Line 37: | ||
Engage developers in India to invest and be proud of their contributions to a Mozilla product with millions of users. Our goal is not just to make the product better, but to bring high value to those participating in the program. | Engage developers in India to invest and be proud of their contributions to a Mozilla product with millions of users. Our goal is not just to make the product better, but to bring high value to those participating in the program. | ||
The project will deal with core component bugs of gecko. So an acceptable knowledge of gecko probably is a good thing to get involved. If you want to get involved, get in touch with any team members. Roughly the process to get up and running will be to follow the following process | |||
* Get the fennec source code and setup build environment in your machine. [[Mobile/Fennec/Android#Building_Fennec|Build your first fennec]]. Of course it's nice if you can build it once before delving into the code. | |||
* Look at the open bugs [https://bugzilla.mozilla.org/showdependencytree.cgi?id=942609&hide_resolved=1 here]. Pick one (but don't start yet). And start digging up on the relevant sources on what you can learn about the relevant code. Get in touch with any team member regarding that, they may be able to help you. | |||
* Once you are sufficiently confident, start working on a patch. This step will not come easily, so ask as many question as you want to the team (soon you will be part of which) | |||
== Resources == | |||
If you are having problem setting up the developer environment on your machine. We have a pre-built VM with mozilla-central and all build tools set-up, up and running. The image build date is June 2015 so you might want to update the sources once you download it. It is a vmware/virtualbox/parallels image with minimal hardware setup configured to run the build and produce the apk. For optimal performance increase the ram more than 4GB for the guest OS. | |||
The guest os runs Ubuntu. Get in touch with any team member to get the credential to the system. | |||
Download the image from [https://goo.gl/dVX8Fx here]. | |||
== Audience == | == Audience == | ||