Contribuir para a base de código da Mozilla

Esta guiá-lo-á nos primeiros passos para contribuir para a Mozilla. Bem vindo, estamos muito contentes pela sua visita :) 

Precisa de ajuda?

The Mozilla community always welcomes newcomers to our midst. Se tiver dificuldades em algum lugar, pergunte na sala de chat #introduction em irc.mozilla.org. Se continuar a ter problemas, contacte Kyle Huey pelo email khuey@mozilla.com.

Que aptidões precisa?

A Mozilla é um projeto muito vasto e nós ficamos contentes por receber voluntários com diferentes aptidões.

  • Se sabe C++, por exemplo, poderá contribuir para o core do Firefox, Firefox OS e para outros produtos da Mozilla.
  • Se sabe JavaScript ou HTML/CSS, poderá contribuir para o desenvolvimento do frontend do Firefox, ou para o Gaia, a aplicação de frontend do Firefox OS.
  • Se sabe Java, poderá contribuir para o Firefox Mobile.
  • Se sabe Python, poderá contribuir para os nossos serviços web, incluíndo Firefox OS ou o Persona.
  • Se sabe Make, shell, Perl or Python, poderá contribuir para o desenvolvimento do nosso sistema.
  • Se sabe C, poderá contribuir para as nossas bibliotecas low-level e third-party que nós usamos como parte da base de código da Mozilla.
  • Há muitas mais maneiras de contribuir para a missão da Mozilla sem saber programação. Se quer participar nas áreas de design, suporte, tradução, testes, ou outros tipos de contribuição, veja a página Volunteer Oportunities.

Se por acaso ainda não sabe código mas quer aprender? Também é bom, o programa Webmaker is for you, and there are more resources available on the Mozilla Developer Network!

Passo 1 - Construir o Firefox, Firefox OS, Thunderbird e outras aplicações

If you wish to contribute to Firefox, Thunderbird or Firefox OS, follow our set of simple instructions to build Firefox, or to build Thunderbird, or to build Firefox OS. This is straightforward, but may take some time, so you may want to move on to the next steps while it builds. More build instructions can be found here.

For other products, you may not need to build anything.

Step 2 - Understand how contributing to Mozilla works

See Mozilla Firefox: Development Process. Thunderbird operates a similar process.

Step 3 - Find something to work on

Fix your pet peeve

If there's something you'd like to fix about Firefox, Thunderbird or your other favourite Mozilla application, this can be a good place to start. There are a number of ways to do this:

Find a bug we've identified as being good for newcomers

Mozilla developers label certain bugs as being an easy bug to get newcomers acquainted with our processes:

  • Mentored bugs (or the alternative, less usable interface) have a mentor who commits to helping you every step of the way. Generally, there should be enough information in the bug to get started. Whenever you need help, contact the mentor over IRC, in the bug itself, or by email. When you've completed the bug, they will help you get your code into the tree.
  • "Good" first bugs may be a little stale, but at some point in their lives we considered that they would be a good first step for newcomers to Mozilla. We are in the process of migrating these bugs to mentored bugs, but more recent "good first bugs" may be good starting points if there are no appropriate mentored bugs.
  • Student Projects are larger projects, such as might be suitable for a university student for credit. Of course, if you are not a student, you should still feel free to fix one of these bugs. We maintain two lists, one for projects based on the existing codebase, one for implementing new applications.

Step 4 - Fix the bug

We leave this in your capable hands. We have some resources to help you here too:

If the bug you're fixing is likely to require an update to developer documentation once it's fixed, be sure to add the dev-doc-needed keyword to the bug (or ask someone to do it, if you don't have editbugs privileges on Bugzilla). This puts the bug on the radar of our documentation team to ensure that once the bug is resolved, the documentation will be updated appropriately. If you don't mark the bug, your work might go unnoticed by the docs team! You can mark the bug with this keyword at any time; you don't need to wait until it's actually fixed.

Of course, our documentation is a wiki; you can really help by updating the documentation yourself. Even if you're not comfortable with your writing skills, keep in mind that our helpful, happy documentation gnomes will follow along behind you and clean up for you.

Step 5 - Get your code reviewed

Once you fix the bug, attach a patch to the bug, and ask for review. Do this by clicking the Details link on your attachment, then setting the review flag to ? and entering the reviewer's bugzilla ID in the text field that appears (either their email address of the :UniqueName they provide). It is very important to attach a bugzilla ID, or the request will be missed. So how do you figure out the right person to ask for a review?

  • If you have a mentored bug, ask your mentor, they will know or can find out easily.
  • Run hg blame and look at the people who have touched the function's you've worked on - they will be a good candidate.
  • The bug itself may contain a clear indication of the best person to ask for a review.
  • Are there related bugs on similar topics? In that case, the reviewer in those bugs might be a good choice.
  • We have an out of date list of modules which lists peers and owners for the module, some of whom will be a good reviewer. In the worst case, set the module owner as the reviewer, and ask them in the comment to pick someone better if they don't have time.

Step 5b - Follow it up

If you've asked for review, but the reviewer hasn't said anything for a few days, don't be afraid to ping them. Just add a comment to the bug saying 'review ping?', and another a few days later if they still haven't responded. If they don't respond after that, ask for help in #introduction or #developers.

Step 6 - Respond to the review

Often, a reviewer will ask for changes, perhaps minor, perhaps major. In either case, fix what the reviewer asks for; if you're unsure how, be sure to ask! Attach the new patch to the bug again, and ask for review again from the same reviewer. If they give you an r+ that means that your bug is accepted into the tree!

Step 7 - Actually get the code into the tree

Since you don't yet have the ability to push the code into the tree, you should ask somebody for help. If you have a mentor, ask them. If not, ask the reviewer. If the reviewer is too busy, mark that a commit is needed by adding the checkin-needed keyword. A friendly person should be along within a few days and push the code to the repository, and they will mark the bug as fixed.

Step 8 - Repeat

Congratulations, you've fixed your first bug. Now go back to step 3 and repeat. Now that you've got your first bug in, you should request level 1 access to the repository so that you can push to rhw tryserver and get automated feedback about your changes on multiple platforms. After fixing a nontrivial number of bugs, you should request level 3 access so that you can push your own code after it has been r+ed.

More information

We're in the process of improving information on this page for newcomers to the project. We'll be integrating some information from these pages soon, but until then you may find them interesting in their current form:

Document Tags and Contributors

Contributors to this page: rogerio
Last updated by: rogerio,