Glossary: Difference between revisions

← Older edit

Glossary (view source)

Revision as of 16:44, 2 January 2024

3,968 bytes added , 2 January 2024

Asknot - whatcanidoformozilla.org does not longer exist.

Manuel Bucher

Confirmed users

436

edits

@@ Line 5: / Line 5: @@
 ==A==
 ;[https://wiki.mozilla.org/Add-ons/Terminology Add-ons]
-Bits of code that you can install to customize Firefox.
+:Bits of code that you can install to customize Firefox.
 ;All Hands
 : All MoCo and MoFo staffers plus key volunteers - also sometimes the all-mofo meetings that happen before the moco work weeks
 ;amo
 : [http://addons.mozilla.org/ addons.mozilla.org] - the central repository of mozilla addons.
-;asknot
-: A web tool to find out contribution areas. [http://whatcanidoformozilla.org whatcanidoformozilla.org]
 ==B==
@@ Line 29: / Line 27: @@
 : In software a bug is an error in the program. Anything filed on bugzilla is also called a bug, even though we use it for purposes other than pointing out errors (like budget requests). (compare ''Github Issue'')
 ;Bugs Ahoy!
-: A [https://www.joshmatthews.net/bugsahoy/ website] for contributors to directly find unassigned ''Bugzilla'' bugs matching their interests. (Complementary to ''asknot''.)
+: A [https://www.joshmatthews.net/bugsahoy/ website] for contributors to directly find unassigned ''Bugzilla'' bugs matching their interests.
 ;Bug report
 : The detailed description accompanying a bug or the act of reporting the bug itself. (Sometimes just called ''bug'')
 ;Bugzilla
-: A tool to keep track of bugs. (Compare ''bmo'') Used synonymous with BMO
+: A tool to keep track of bugs. (Compare ''bmo'') Used synonymous with BMO, but probably shouldn't be.  [https://www.bugzilla.org/ Bugzilla] is used by many companies on their own websites, BMO is Mozilla's specific instance of it.
+;busted
+: Colloquial term for a broken build or tool.
 ==C==
 ;cbt
 : [[Contribute/Archive/Community Building Team|Community Building Team]]. Now been replaced by Participation team.
+;central
+: Refers to the main source code repository [https://hg.mozilla.org/mozilla-central/ mozilla-central].
 ;Channel
 : The way people see your work. (e.g. The snippet, social media, the Mozilla homepage)
-;Chemspill
+;[[Release Management/Chemspill|Chemspill]]
-: When something is wrong with the Firefox release, so that we have to create a new release and ship it to all users (instead of waiting for the normally scheduled next release). Usually this is caused by a security or stability problem, and as the name implies there is a degree of panic and distress (but it's not uncommon for these to happen). The result is called a point-release.
+: Short for "chemical spill", this is historically intended to mean "something is wrong with the Firefox release, so that we have to create a new release and ship it to all users as soon as possible, instead of waiting for the normally scheduled next release". More recently, "Chemspill" has come to denote any urgent problem in our products that requires an immediate company-wide effort in response. This isn't a term we use lightly, so when somebody says "this is a chemspill" you should put aside whatever you're doing and figure out how to help.
 ;Chop wood
 :Do practical work
+;CI
+: Short for [https://en.wikipedia.org/wiki/Continuous_integration continuous integration]. The process of continually building, testing and deploying changes as they are submitted.
 ;CommSquared
 : [[CommSquared|Community Communications]] program
@@ Line 58: / Line 62: @@
 ;Discourse
 : A modern web based communication forum. Checkout [https://discourse.mozilla-community.org/ discourse.mozilla-community.org]
+;Doorhanger
+: Arrow panels anchored to the browser chrome UI that ask the user to make a decision e.g. would you like to share your location with example.com?
 ==E==
 ;e10s
-:Short for [[Electrolysis]]
+:Short for [[Electrolysis]] (e, ten letters, s)
 ;[[Electrolysis]]
 :An effort to increase security by splitting off the content rendering from the main Firefox process.
@@ Line 94: / Line 100: @@
 ;Heroku
 : A platform for temporarily hosting a given piece of code before it is shipped to staging or production, usually for testing or demonstrating.
+;hg
+: The binary used by the version control system [https://www.mercurial-scm.org/ Mercurial]. Often used in a sentence as short form for "mercurial".
 ;Hive
 : [[Webmaker/Hive|Hive]] is A city-based network of educators, technologists, and other stakeholders championing web literacy through connected learning in communities around the world.  Networks are the innovation incubators for the global MLN network.  For example, much of the Clubs curriculum originated in Hive networks: http://hivelearningnetworks.org
@@ Line 100: / Line 108: @@
 ==I==
+;i18n
+:Short for [https://developer.mozilla.org/en-US/docs/Glossary/I18N Internationalization] (i, eighteen letters, n)
 ;inbound
 : [https://hg.mozilla.org/integration/mozilla-inbound/ A repository] where changes to Firefox usually land first. Changes are batched up and moved to mozilla-central several times a day, so long as everything is building and testing well.
 ;IRC
-: [[IRC|Internet Relay Chat]] is a communication tool used by Mozillians to communicate
+: [[IRC|Internet Relay Chat]] is a communication tool previously used as the primary public chat mechanism before being replaced with [[Matrix]].
 ==K==
@@ Line 113: / Line 123: @@
 ==L==
 ;l10n
-: [[L10n|Localization]] is the translation of Mozilla products to various languages.
+: [[L10n|Localization]] is the translation of Mozilla products to various languages.  (l, ten letters, n)
+;lint
+: A [https://en.wikipedia.org/wiki/Lint_(software) lint program] is something that automatically checks for style problems in code, and helps enforce consistent style. See also [https://wiki.mozilla.org/DevTools/CodingStandards Coding Standards]
 ==M==
+;mach
+: A command line dispatcher. [https://firefox-source-docs.mozilla.org/python/mach/index.html Mach] has a binary of the same name that lives at the root of the main repository. Other tools that live in-tree can register an entry point making 'mach' a single point of entry for a large variety of tasks that can be performed in the repository (such as running builds and tests). The name 'mach' comes from 'machen', the German word for do.
 ;Maker Party
 : Month-long summer campaign to activate, engage, and/or level-up users new and old by supporting them in planning small- and large-scale maker events that tie into MLN tools, curricula, and/or philosophies; often themed and sets up calls-to-action for the following year. [https://teach.mozilla.org/events/ teach.mozilla.org/events/]
 ;Mana
 : The  name for land that you need to control to cast spells or summon  creatures in Magic the Gathering. They are Swamps/black, Forests/green,  Plains/White, Water/blue and Mountains/red and colorless.  Also where a bunch of HR documents are stored - a wiki that is not available to the public.
+;Matrix
+: [https://matrix.org/ Matrix] is an open, lightweight protocol for decentralized, real-time communications. After a long evaluation period, Mozilla switched to Matrix from [[IRC]] as the preferred open discussion platform.
+;MAU
+: Monthly active user
 ;MCWS
 : [[MCWS|Mozilla Community Web Support]] - working group providing support for community webs services.
 ;MDN
 : [[MDN|Mozilla Developer Network]] - online resource for Web developers; lives at. [https://developer.mozilla.org/ developer.mozilla.org]
+;Mercurial
+: The primary [https://en.wikipedia.org/wiki/Version_control version control system] (vcs) [https://mozilla-version-control-tools.readthedocs.io/en/latest/hgmozilla/ used at Mozilla]. Most of Mozilla's source code is hosted on [https://www.mercurial-scm.org/ Mercurial] servers.
 ;MLN
-: Mozilla Learning Network
+: [https://learning.mozilla.org/en-US/ Mozilla Learning Network] – now-defunct web literacy educational initiative by Mozilla Foundation
 ;MoCo
 : Mozilla Corporation is a wholly owned subsidiary of the Mozilla Foundation that coordinates and integrates the development of products.
@@ Line 137: / Line 157: @@
 : Crew aboard the first New Hire Onboarding Program of November, 2015. [https://mozillians.org/group/mozicorns/ mozillians.org/group/mozicorns]
 ;mozilla-central
-: [https://hg.mozilla.org/mozilla-central/ The repository] where most Firefox development happens, and which builds Firefox Nightly.
+: [https://hg.mozilla.org/mozilla-central/ The repository] where most Firefox development happens, and which builds Firefox Nightly. Often referred to as "central" or "m-c".
 ;Mozilla Clubs
 : Local groups that meet regularly to learn the Web, a part of the Mozilla Learning Network. [https://teach.mozilla.org/clubs/ teach.mozilla.org/clubs/]
@@ Line 157: / Line 177: @@
 ;needinfo
 : A https://bugzilla.mozilla.org user can submit a <code>needinfo</code> request another bugzilla user to ask a question about a bug. Mozilla uses <code>needinfo</code> instead of assigning a bug to ask a question, as one would do in Jira.
+;Nightly
+: [https://www.mozilla.org/en-US/firefox/channel/desktop/#nightly Pre-release versions of Firefox] that are built directly from mozilla-central, for testing and development. Firefox Nightly is generally stable enough for everyday use though the occasional bug is expected.
 ==O==
+;Ongoing versions
+: The last version number for each release channel of Firefox. (ESR, Release, Beta, Nightly)
 ;OpenNews
 : A joint project of Mozilla and the Knight Foundation that supports the community of news developers, designers, and data reporters helping journalism thrive on the open web. Runs the Knight-Mozilla Fellowships, Source, SRCCON, and associated programs. https://opennews.org/
+;Orange
+: Synonymous for a failing task in CI (because it gets coloured orange in [https://treeherder.mozilla.org/#/jobs?repo=mozilla-central treeherder]). Tasks that only fail occasionally are known as 'intermittent oranges', but this term is often shortened to just 'orange'.
 ;Outreachy
 : formerly the outreach program for women, (https://www.gnome.org/outreachy/) now a paid internship program for under-represented groups in tech sponsored by several open source organizations, including Mozilla.
@@ Line 171: / Line 197: @@
 ;Patch
 : A specific code contribution by programmers submitted as a text file.
+;PHD
+: A "Product Hypothesis Document": a template for proposing experiments for [https://wiki.mozilla.org/Firefox/Shield Shield]
 ;Point-release
 : A point release is when, for instance, Firefox 30 is released, then there is a problem and Firefox 30.1 must be released (instead of waiting for the regularly scheduled 6 week iteration that leads to Firefox 31). See also ''chemspill''
@@ Line 187: / Line 215: @@
 ;QA
 : Quality assurance. [https://quality.mozilla.org/ quality.mozilla.org]
+;QBR
+: Quarterly Business Review. A quarterly presentation by teams to the Leadership Team
 ==R==
@@ Line 225: / Line 255: @@
 ==T==
+;Taskcluster
+: The continuous integration (CI) system used and [https://docs.taskcluster.net/docs developed by Mozilla].
 ;TLDR
-: usually TL;DR, meaning 'too long; didn't read;' used as a tag for a summary above lengthy text.
+: Usually TL;DR, meaning 'too long; didn't read;' used as a tag for a summary above lengthy text. Also the name of an internal weekly newsletter.
 ;Trains
-: Firefox development happens primarily in the mozilla-central repository, which is used to build Firefox Nightly. The "trains" are how Nightly turns into Beta, and Beta turns into Release. If a change "rides the trains" that means it is distributed as part of this normal cycle of Nightly to Beta to Release. See also Uplift.
+: Riding the trains: the process by which a Firefox desktop feature or fix rolls out to release: from Nightly, to Beta, to Production. See also Uplift.
 ;Triage
-: the process of deciding what the next step for a new bug is. In Firefox, there are [https://bugzilla.mozilla.org/page.cgi?id=triage_owners.html triage owners] responsible for making these decisions, and they follow [[Bugmasters/Process/Triage|our triage process]].
+: The process of deciding what the next step for a new bug is. In Firefox, there are [https://bugzilla.mozilla.org/page.cgi?id=triage_owners.html triage owners] responsible for making these decisions, and they follow [[Bugmasters/Process/Triage|our triage process]].
+;Tree
+: Informal term referring to a branch of source code (e.g mozilla-central, mozilla-beta, etc). Saying something is "in-tree" means its source code lives in mozilla-central.
+;Treeherder
+: The [https://treeherder.mozilla.org/#/jobs?repo=mozilla-central main dashboard] used to view results from continuous integration (CI). The name 'Treeherder' is both a reference to The Lord of the Rings (Ents) and the fact that it is used to manage all of Mozilla's "trees".
 ==U==
 ;Uplift
 : When a patch lands on mozilla-central in Nightly, it will normally get to users after Nightly turns to Beta, then Beta turns to Release. If the patch is "uplifted" then it is moved from Nightly/mozilla-central to the current Beta.
+==V==
+;vcs
+: Short for [https://en.wikipedia.org/wiki/Version_control version control system].
 ==W==
@@ Line 249: / Line 289: @@
 ;Yammer
 : Previously used as a communications tool by Mozilla staff. Replaced by https://mozilla.slack.com/.
+See also: [[Acronyms]]