Contribute to mozilla

382 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
382
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
11
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Contribute to mozilla

  1. 1. Contributing to the Mozilla Codebase
  2. 2. The Development Process :
  3. 3. Step 3 : Find some work 1. Fix your pet peeve 2. Fix bugs identified by mozilla 3. Bugs Ahoy ! 4. Use whatcanidoformozilla.org
  4. 4. Fix your pet peeve 1. Search bugzilla : For relevant keywords 2. Figure out the bugzilla component : Find where pet peeve is implemented 3. Ask for help : #introduction or #developers in irc.mozilla.org
  5. 5. Fix bugs identified by mozilla 1. Mentored Bugs Your mentor helps you in every step. 2. “Good” First Bugs Bit stale. But good starting point. 3. Student Projects Large projects, good enough for your university project.
  6. 6. Bugs Ahoy !
  7. 7. whatcanidoformozilla.org
  8. 8. 1. Gecko The engine that drives Firefox. 2. Boot2Gecko The operating system for Android phones built on web technologies. 3. Thunderbird The open source email client. C++
  9. 9. 4. Seamonkey The open source web productivity suite. 5. v8monkey Implementing the v8 API on top of Spidermonkey. 6. emscripten Creating a LLVM-to-JS system to allow porting native code to the web. C++
  10. 10. 7. SVG Project Help with the implementation and testing of Mozilla's Scalable Vector Graphics engine. 8. Windows 8 Integration The Metro-style enabled desktop browser for Windows 8. 9. MathML Display and represent math formulas on the web. C++
  11. 11. C 1. NSS The network security pieces of Firefox.
  12. 12. JavaScript 1. Firefox All of the UI is written in JS. 2. Mobile Firefox It's the Gecko engine, with an Android-specific UI. No Android device required. 3. pdf.js A PDF viewer written entirely in JavaScript.
  13. 13. JavaScript 1. Firefox All of the UI is written in JS. 2. Mobile Firefox It's the Gecko engine, with an Android-specific UI. No Android device required. 3. pdf.js A PDF viewer written entirely in JavaScript.
  14. 14. JavaScript 4. Shumway A Flash player written entirely in JavaScript. 5. The addon SDK The foundation upon which all new kick-ass addons are built. 6. Gaia The default UI for the web-based mobile operating system Boot2Gecko.
  15. 15. JavaScript 7. DXR The intelligent source code indexing system. 8. Thunderbird The open source email client. 9. Seamonkey The open source web productivity suite.
  16. 16. JavaScript 10. Web development Many large, complicated projects that use JavaScript. 11. Popcorn Create interactive media pages that seamlessly integrate video, audio, and traditional web technologies
  17. 17. JavaScript 12. Windows 8 Integration The front end for the Metro-style enabled desktop browser for Windows 8. 13. Persona Implement a new way to safely and easily sign into websites.
  18. 18. Java 1. Mobile Firefox It's the Gecko engine, with an Android-specific UI. No Android device required. 2. Rhino It's Spidermonkey in Java. Java
  19. 19. Python 1. Firefox Lots of code is generated by python scripts. 2. Web development There are many large, complicated projects written in Python.
  20. 20. Python 3. DXR The intelligent source code indexing system. 4. Tools & Automation Various projects to facilitate easier automated testing of products.
  21. 21. PHP 1. WordPress The code that runs our blogs 2. Marketplace The PHP client for Marketplace. 3. The Mediawiki-Bugzilla plugin The Bugzilla plugin for Mozilla's MediaWiki.
  22. 22. Rust Rust is an experimental, multi-paradigm, compiled programming language developed by Mozilla Research. It visually resembles the C language family, but differs significantly in syntactic and semantic details.
  23. 23. Step 4 : Fix the bug 1. Check out the Developer Guide : https://developer.mozilla.org/En/Developer_Guide 2. Ask for help : #introduction and #developers 3. Notify the docs team : Add dev-doc-needed keyword if your bug is likely to require documentation.
  24. 24. Step 5 : Get your code reviewed Once you fix the bug, attach a patch to the bug, and ask for review. Do this by setting the review flag to ?
  25. 25. Step 6 : Respond to the review The reviewer may ask to fix some issues. An r+ would mean that your bug fix is accepted into the tree.
  26. 26. Step 7 : Get the code into the tree Ask your mentor or mark your commit with a checkin-needed keyword.
  27. 27. Thank You :)

×