Auto-tools/New Contributor: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
m (link to quarter of contribution (maybe should go in a different section...))
 
(23 intermediate revisions by 11 users not shown)
Line 1: Line 1:
{{Admon/important|This page has wholly superceded by the [http://ateam-bootcamp.readthedocs.org/en/latest/ A-team bootcamp] and is being kept mainly for historical reasons. }}
Welcome!  First things first, you should [[auto-tools/The_Ateam|meet the Ateam]].
Welcome!  First things first, you should [[auto-tools/The_Ateam|meet the Ateam]].


Line 4: Line 6:


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).
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 =
= IRC =
* We use [irc://irc.mozilla.org irc.mozilla.org].  We are in the #ateam channel
* We use [irc://irc.mozilla.org irc.mozilla.org].  We are in the #ateam channel
* We have many [http://irc.mozilla.org/ irc channels] at Mozilla
* There are many [http://irc.mozilla.org/ irc channels] at Mozilla
* Never used IRC? [http://quality.mozilla.org/documents-home/test-docs/getting-started-irc Here's some getting started tips].
* Never used IRC? [https://developer.mozilla.org/en-US/docs/Mozilla/QA/Getting_Started_with_IRC/ Here's some getting started] tips.


= Conference Call =
= Conference Call =
* Join our weekly (every Monday) [[Auto-tools/Meetings|status conference call]].
* Join our regular [[Auto-tools/Meetings|status conference call]].
* Be sure to say hello so we know you're there
* Be sure to say hello so we know you're there
* [[Auto-tools/New_Contributor/Quarter_of_Contribution| Quarter of Contribution, 2016]]


= Bugzilla =
= Bugzilla =
Line 27: Line 32:
* [http://developer.mozilla.org/en/docs/Mochitest Mochitest]
* [http://developer.mozilla.org/en/docs/Mochitest Mochitest]
* [http://developer.mozilla.org/en/docs/Creating_reftest-based_unit_tests Reftest]
* [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"].
* 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 [http://brasstacks.mozilla.com/orangefactor/ list of "oranges"].


= E-Mail & Mailing Lists=
= E-Mail & Mailing Lists=
Line 39: Line 44:
* Watch [http://groups.google.com/group/mozilla.dev.apps.firefox/topics m.d.a.Firefox] for Firefox front end design, questions and status
* 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 =
= DXR & Pastebin =
* To look up source in Mozilla-Central (trunk): http://mxr.mozilla.org/mozilla-central/
* To look up source in Mozilla-Central (trunk): https://dxr.mozilla.org/mozilla-central/source/
* 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.   
* To look up a specific file in our tree use this url for a base: https://dxr.mozilla.org/mozilla-central/search?q=path%3A 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.
** Pro tip: make it into a [http://www.mozilla.org/docs/end-user/keywords.html bookmark keyword in Firefox].  Then you can type "dxrf <filename>" in the URL bar.
* To "pastebin" something, [http://mozilla.pastebin.com/ paste it here] and hand the link you're given after clicking "submit" to people on IRC.
* 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 =
= Building & Build/Test Status Reporting =
* How to [https://developer.mozilla.org/en/Build_Documentation build]
* How to [https://developer.mozilla.org/en/Build_Documentation build]
* How to [https://wiki.mozilla.org/Build:TryServer use Try Server]
* How to [https://wiki.mozilla.org/Build:TryServer use Try Server]
* Watch the status on [http://tests.themasta.com/tinderboxpushlog/ "pushlog" (aka "tbpl" or "tinderbox pushlog")]
* Watch the status on [https://treeherder.mozilla.org/#/jobs?repo=try Treeherder]


= The Brief Guide to Coding =
= The Brief Guide to Coding =
* Source for [http://hg.mozilla.org/mozilla-central mozilla-central]
* Source for [http://hg.mozilla.org/mozilla-central mozilla-central]
* How to use [https://developer.mozilla.org/en/Mercurial_queues Mercurial Queues]
* [http://mozilla-version-control-tools.readthedocs.org/en/latest/hgmozilla/index.html Mercurial for Mozillians]
* [http://ateam-bootcamp.readthedocs.org/en/latest/reference/git_github.html Git for Mozillians]
* Developing and using [http://wiki.mozilla.org/Auto-tools/Python101 Python 101]
* 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
* Add "ac_add_option --enable-tests" (no quotes) to your mozconfig to enable tests
Line 60: Line 66:
* General Rule -- follow the style of the file you're editing, but no tabs. Ever.
* General Rule -- follow the style of the file you're editing, but no tabs. Ever.


[Category:New_Contributor_Landing_Pages]
[[Category:New_Contributor_Landing_Page]]

Latest revision as of 14:24, 17 June 2016

Important.png
This page has wholly superceded by the A-team bootcamp and is being kept mainly for historical reasons.

Welcome! First things first, you should 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

Conference Call

Bugzilla

Automation Harnesses

E-Mail & Mailing Lists

  • Watch our newsgroup mozilla.tools for things related to automation and tools at Mozilla.
  • Watch m.d.quality for information on testing
  • Watch m.d.Planning for project wide notices and meeting announcements
  • Watch m.d.Platform for technical discussions regarding the Gecko Platform
  • To keep abreast of the latest status on the entire project, Planet Mozilla is useful, but is a TON of data.
  • To watch the automated messages coming out of the automation, see mozilla.dev.tree-management
  • Watch m.d.a.Firefox for Firefox front end design, questions and status

DXR & Pastebin

Building & Build/Test Status Reporting

The Brief Guide to Coding

Retrieved from "https://wiki.allizom.org/index.php?title=Auto-tools/New_Contributor&oldid=1137134"