Auto-tools/New Contributor: Difference between revisions

Jump to navigation Jump to search

Auto-tools/New Contributor (view source)

Revision as of 05:04, 20 June 2015

5,033 bytes removed ,  20 June 2015
→‎IRC: I fixed the 404 error for the landing page url of "Never used IRC? Here's some getting....." document. I found it that the page was throwing 404 error as it was pointing to erroneous QMO domain page whereas the actual page was at MDN domain.
(→‎IRC: The landing page url of "Never used IRC?" I updated to fix the 404 error. It was redirected to erroneous QMO domain instead of actual MDN domain.)
(→‎IRC: I fixed the 404 error for the landing page url of "Never used IRC? Here's some getting....." document. I found it that the page was throwing 404 error as it was pointing to erroneous QMO domain page whereas the actual page was at MDN domain.)
Line 1: Line 1:
Welcome!  First things first, you should [[auto-tools/The_Ateam|meet the Ateam]].


This will look like a lot, but the good news is that you don't need to understand or even use all this to be effective. So, "Don't Panic".
Just bookmark this page and refer back to it as needed.  I've structured it like a task list, so when you see someone say something like "Flag that patch on the orange for review" you can come here and figure out what people are talking about (or just ask them).
The best way to get in touch with people, or to get a better idea of the projects is to talk to us over on the #ateam channel in [[#IRC|IRC]]!
= IRC =
* We use [irc://irc.mozilla.org irc.mozilla.org].  We are in the #ateam channel
* There are many [http://irc.mozilla.org/ irc channels] at Mozilla
* Never used IRC? [https://developer.mozilla.org/en-US/docs/Mozilla/QA/Getting_Started_with_IRC/] Here's some getting started tips.
= Conference Call =
* Join our weekly (every Monday) [[Auto-tools/Meetings|status conference call]].
* Be sure to say hello so we know you're there
= Bugzilla =
* We track everything in bugzilla.  We also do some work around bugzilla.
* Create yourself an account: [http://bugzilla.mozilla.org http://bugzilla.mozilla.org]
* Learn to use it: [http://people.mozilla.org/~johnath/bugzilla/BugzillaForHumans.ogv Bugzilla For Humans How-To video]
* Use Quicksearch to [https://bugzilla.mozilla.org/page.cgi?id=quicksearch.html search bugzilla]
* [https://wiki.mozilla.org/Bugzilla:Review Ask for a review of your work.]
* [https://developer.mozilla.org/en/What_to_do_and_what_not_to_do_in_Bugzilla What may I change in Bugzilla?]
= Automation Harnesses =
*  The automated testing [http://developer.mozilla.org/en/docs/Mozilla_automated_testing overview]
* [http://developer.mozilla.org/en/docs/Writing_xpcshell-based_unit_tests XPCShell]
* [http://developer.mozilla.org/en/docs/Mochitest Mochitest]
* [http://developer.mozilla.org/en/docs/Creating_reftest-based_unit_tests Reftest]
* [https://developer.mozilla.org/en/Mozmill Mozmill]
* [https://developer.mozilla.org/en-US/docs/Mozilla/QA/Marionette Marionette]
* What is an "orange" test? It's a test that fails intermittently.  They are called "oranges" because they turn our status reporting orange.  View current [https://bugzilla.mozilla.org/buglist.cgi?status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=orange&resolution=DUPLICATE&resolution=--- list of "oranges"].
= E-Mail & Mailing Lists=
* Watch our newsgroup [http://groups.google.com/group/mozilla.tools/topics mozilla.tools] for things related to automation and tools at Mozilla.
* Watch [http://groups.google.com/group/mozilla.dev.quality/topics?lnk=srg m.d.quality] for information on testing
* Watch [http://groups.google.com/group/mozilla.dev.planning/topics?lnk=srg m.d.Planning] for project wide notices and meeting announcements
* Watch [http://groups.google.com/group/mozilla.dev.platform/topics?lnk=srg m.d.Platform] for technical discussions regarding the Gecko Platform
* To keep abreast of the latest status on the entire project, [http://planet.mozilla.org Planet Mozilla] is useful, but is a TON of data.
* To watch the automated messages coming out of the automation, see [http://groups.google.com/group/mozilla.dev.tree-management mozilla.dev.tree-management]
* Watch [http://groups.google.com/group/mozilla.dev.apps.firefox/topics m.d.a.Firefox] for Firefox front end design, questions and status
= MXR & Pastebin =
* To look up source in Mozilla-Central (trunk): http://mxr.mozilla.org/mozilla-central/
* To look up a specific file in our tree use this url for a base: http://mxr.mozilla.org/mozilla-central/find?text=&string= and add the file name to it. 
** Pro tip: make it into a [http://www.mozilla.org/docs/end-user/keywords.html bookmark keyword in Firefox].  Then you can type "mxrf <filename>" in the URL bar.
* To "pastebin" something, [http://pastebin.mozilla.org/ paste it here] and hand the link you're given after clicking "submit" to people on IRC.
= Building & Build/Test Status Reporting =
* How to [https://developer.mozilla.org/en/Build_Documentation build]
* How to [https://wiki.mozilla.org/Build:TryServer use Try Server]
* Watch the status on [https://treeherder.mozilla.org/#/jobs?repo=try Treeherder]
= The Brief Guide to Coding =
* Source for [http://hg.mozilla.org/mozilla-central mozilla-central]
* How to use [https://developer.mozilla.org/en/Mercurial_queues Mercurial Queues]
* Developing and using [http://wiki.mozilla.org/Auto-tools/Python101 Python 101]
* Add "ac_add_option --enable-tests" (no quotes) to your mozconfig to enable tests
* Get a [http://www.mozilla.org/MPL/boilerplate-1.1/ MPL license block] for a new file
* [http://developer.mozilla.org/en/docs/JavaScript_style_guide Javascript Style Guide]
* [http://www.mozilla.org/hacking/mozilla-style-guide.html General Coding Style]
* General Rule -- follow the style of the file you're editing, but no tabs. Ever.
[[Category:New_Contributor_Landing_Page]]
Moingshaikh
36

edits

Retrieved from "https://wiki.allizom.org/Special:MobileDiff/1080993"

Navigation menu