Bugzilla Products

From MozillaWiki
Jump to navigation Jump to search

This is a list of all the bugzilla.mozilla.org products, alphabetically, with their descriptions and the links to more information that their descriptions contain.

Products on main "enter bug" page

These products were decided at some point to be the most commonly used by contributors who are new to Bugzilla. The simplified "enter bug" page lets the user pick a top level area first before being presented with the many possible actual products and their components.

This list is being used for tracking progress on rewriting the product descriptions and adding "more info" links for each one. It may also be useful for people new to Bugzilla or who are managing bugs -- contributing as Bugmasters -- who need to learn the landscape of Mozilla development.

Basic "Enter bug" page: https://bugzilla.mozilla.org/enter_bug.cgi

Core

Shared components used by Firefox and other Mozilla software, including handling of Web content (Gecko, HTML, CSS, layout, scripts, images, networking, etc.).

Firefox

Firefox Desktop. The Mozilla Foundation's web browser.

FirefoxOS

FirefoxOS, or Boot2Gecko (B2G) is Mozilla's operating system built on web standards.

Firefox for Android

Firefox for Android is a mobile version of Firefox for Android devices.

Firefox for Metro

Firefox for Metro is Mozilla's version of Firefox for Windows.

Toolkit

The Mozilla Toolkit is a set of APIs, built on top of Gecko, which provide advanced services to XUL applications. These services include Profile Management, Chrome Registration, Browsing History, Extension and Theme Management, Application Update Service, and Safe Mode.

Marketplace

Mozilla's website (marketplace.firefox.com) to bring personalized discovery, worldwide distribution, and easy payments to the largest platform for app development: the Web.

Thunderbird

Email client originally developed by the Mozilla Foundation and now maintained by its community.

SeaMonkey

An all-in-one internet application suite, including web browser, e-mail and newsgroup client, and HTML composer.

Mozilla Localizations

Translation, spelling and other errors in language packs and localized builds

Mozilla Services

For bugs in Firefox Sync, Firefox Home, metrics, Health Report, Server, Share, and other services.

Other Products

(This link leads to the long list of products in the section below.)


Products as listed in Other Products page


Add‑on SDK

The software development kit for building Firefox add-ons.

addons.mozilla.org

====Air Mozilla:====  The Air Mozilla site (http://air.mozilla.com) and supporting infrastructure, including video conferencing. More info: Air Mozilla wiki page

Android Background Services

Native Android services, including those bundled with Fennec.

  • Android Sync: For all bugs in the Android/Native Fennec version of Firefox Sync.
  • Build & Test: Jenkins, testing, Git, and build infrastructure for Android Sync.
  • Firefox Health Report Service: The Android-native component for managing Firefox Health Report submissions.
  • Homepage Promos: Android client code for the homepage snippet promos feature in Firefox for Android.
  • Product Announcements: Android client code for the Product Announcements feature in Firefox for Android.
  • More info: https://wiki.mozilla.org/Android/Services

AUS

The Application Update Service is used by client software to check for updates to application software.

Boot2Gecko

  • Bluetooth: Bluetooth support in Boot2Gecko/Firefox OS
  • Builds: For problems or requests regarding device or desktop build packaging or automation.
  • Gaia: For bugs related to the Boot2Gecko user interface and apps.
  • Gaia::Bluetooth File Transfer: Any issues related to bluetooth in Gaia directly related to the system itself.
  • Gaia::Browser: Gaia's browser app.
  • Gaia::Calculator: Gaia's calculator application.
  • Gaia::Calendar: Gaia calendar app, protocol issues, features, bugs etc.
  • Gaia::Camera: Gaia's camera application.
  • Gaia::Clock: Gaia's clock application.
  • Gaia::Contacts: Gaia's contacts application.
  • Gaia::Cost Control: Gaia's cost control application.
  • Gaia::Dialer: Gaia's dialer application.
  • Gaia::E-Mail: Gaia E-mail Application. New bugs should include the information requested at wiki.mozilla.org/Gaia/Email/RequiredBugInfo.
  • Gaia::Everything.me: Any issues related to Everything.me integration across the homescreen and system wrapper.
  • Gaia::First Time Experience: Gaia's first time experience app.
  • Gaia::FMRadio: Gaia's FM radio application.
  • Gaia::Gallery: Gaia's gallery application.
  • Gaia::Homescreen: Bugs related to Gaia's Homescreen app that should focus on issues involving the different grids of icons.
  • Gaia::Keyboard: Any issues related to Gaia's keyboard.
  • Gaia::Music: Gaia's music application.
  • Gaia::PDF Viewer: Gaia's PDF viewer application.
  • Gaia::Settings: Bugs related to Gaia's Settings app.
  • Gaia::SMS: Gaia's SMS application.
  • Gaia::System: Bugs related to any piece of Gaia's system app, which includes - window management, wrapper logic for everything.me, notifications, dialogs, etc.
  • Gaia::System::Lockscreen: Any issues related to Gaia's lockscreen.
  • Gaia::Video: Gaia's video application.
  • General: For bugs in Boot2Gecko / B2G / Firefox OS that are not more specifically Gecko or Gaia (user interface) bugs.
  • Hardware: As part of the B2G Test Drivers (dogfooding) program, we are requiring people to submit bugs here to request hardware (phones).
  • Vendcom: The vendor requests to generate the authority for the listed accounts due to everyone of them needs to modify issues, not only monitor.
  • Wifi: WiFi support in Boot2Gecko/Firefox OS

Bugzilla

The Bugzilla bug-tracking system (more info) note: This is not the place to request configuration, permission, or account changes to this installation of Bugzilla (bugzilla.mozilla.org). File such changes under the appropriate component in the bugzilla.mozilla.org product.

  • Administration: Administration of a bugzilla installation, including editcomponents.cgi, editgroups.cgi, editkeywords.cgi, editparams.cgi, editproducts.cgi, editusers.cgi, editversions.cgi, sanitycheck.cgi
  • Attachments & Requests: For problems with attachment creation/management and request creation/management. attachment.cgi, request.cgi
  • Bug Import/Export & Moving: Importing bugs into Bugzilla, exporting bugs from Bugzilla, and moving bugs between Bugzillas. importxml.pl
  • Bugzilla-General: Anything that doesn't fit in the other components, or spans multiple components.
  • bugzilla.org: The Bugzilla Project website (http://www.bugzilla.org/) and issues with any mailing lists served under the bugzilla.org domain. This component does not include The Bugzilla Guide.
  • Creating/Changing Bugs: Creating, changing, and viewing bugs. enter_bug.cgi, post_bug.cgi, show_bug.cgi, process_bug.cgi
  • Database: General issues with the database interface drivers for Bugzilla. End-user facing bugs should almost never go here. Compatibility issues that affect one database but not another should go here. Driver issues found by developers that affect database access should go here. Everything else should generally go in some other appropriate component.
  • Dependency Views: Viewing trees of dependent bugs, either as text or graphically. showdependencytree.cgi, showdependencygraph.cgi

Documentation: The bugzilla documentation, including anything in the docs/ directory and The Bugzilla Guide.

  • Email Notifications: Anything to do with email sent by Bugzilla about bugs. Bugzilla/BugMail.pm
  • Extensions: Issues related to the Bugzilla extensions system. This is for bugs about the extensions system or extensions that ship with Bugzilla (such as BmpConvert or the Example extension). Bugs about third-party extensions should not be filed here-- usually third-party extensions have their own bug tracker.
  • Incoming Email: Everything related to bug creation and editing by email, using email_in.pl (or the contrib/bug_email scripts in old versions of Bugzilla).

Installation & Upgrading: The installation process of Bugzilla. This includes checksetup.pl and whatever else it evolves into

  • QA Test Scripts: Bugs about missing or broken automatic test scripts used by the Bugzilla QA team should come here. This includes all Selenium, RPC and configuration scripts located at http://bzr.mozilla.org/bugzilla/qa/. For bugs related to the test suite released with Bugzilla, see the "Testing Suite" component.
  • Query/Bug List: Anything to do with searching for bugs and viewing the buglists. query.cgi and buglist.cgi
  • Reporting/Charting: Getting reports from Bugzilla. reports.cgi, duplicates.cgi
  • Testing Suite: The Bugzilla Test Suite, for finding problems with Bugzilla.
  • User Accounts: Anything about managing a user account from the user's perspective. userprefs.cgi, saved queries, creating accounts, changing passwords, logging in, etc.
  • User Interface: General issues having to do with the user interface. This includes both presentation (how it looks) and behavior (how it works) but not functionality (what it does), which should be filed in a function-specific component like Email Notifications or in Bugzilla-General. Examples of bugs you might file here include "column label "Pri" is confusing" and "take anonymous users to the simple query page by default" but not "need way to filter for requests with no requestee". As a general rule, bugs that affect only a single Bugzilla web page or can be fixed with changes just to templates probably go in this component, while bugs that affect multiple pages or fixes to Perl code probably go somewhere else.
  • WebService: For issues and bugs in the WebService interface. xmlrpc.cgi, Bugzilla/WebService/*.pm
  • Whining: Periodic mailed reports from Bugzilla. whine.pl, editwhines.cgi

bugzilla.mozilla.org

For issues relating to the bugzilla.mozilla.org website, also known as BMO. More info: BMO wiki pages.

Calendar

The Mozilla Calendar project (more info)

Camino

Camino is a native Mac OS X browser-only project (more info)

CCK

Community Tools

Suite of tools that helps make it easier for people to get involved in the Mozilla Project.

Composer

Next-generation gecko-based standalone HTML/XHTML authoring tool

Core

Shared components used by Firefox and other Mozilla software, including handling of Web content (Gecko, HTML, CSS, layout, scripts, images, networking, etc.).


The components of core as listed in Bugzilla don't map perfectly to the Module owners. So it seems worth it to put links to individual component wiki pages if applicable, into the component descriptions in BMO.


  • Build Config

For core build config issues

  • Canvas: 2D

Bugs with the HTML5 <canvas> element, its XUL sibling, and related rendering contexts.

  • Canvas: WebGL

Bugs with the WebGL Canvas Context.

  • CSS Parsing and Computation

Bugs in the handling of CSS stylesheets and the computation of style from CSS stylesheets and HTML attributes.

For bugs in the rendering, see the Layout components.

  • Disability Access APIs

Description: This component relates to bugs in our support for accessibility APIs on the various platforms. Accessibility APIs allow 3rd party products, such as screen readers used by visually impaired users, to communicate with our content and UI. The APIs we support specifically are MSAA on Windows and ATK on UNIX/Linux (Apple has not yet published specs for an accessibility API on OS X). This component is not for keyboard, focus or any accessibility bugs other than those relating to the APIs we export.

  • DMD

Issues relating to DMD (dark matter detector), the tool for verifying memory reporters.

  • Document Navigation

Docshell acts as the glue that initiates and monitors document loading and associates documents to their view for rendering. Previously called Webshell.

  • DOM

For bugs in DOM support which do not fit into any other DOM Component. This is the right component for issues with <base href=""> and xml:base. (More info) https://developer.mozilla.org/en-US/docs/Hacking_Mozilla_DOM

  • DOM: Apps

Bugs related to Gecko's navigator.mozApps DOM API

  • DOM: Core & HTML

This component includes all functionality related to JavaScript manipulation of window, document and navigator objects that are available in Navigator 4.x and earlier, and that was never defined by the W3C.

  • DOM: CSS Object Model

For bugs in our DOM Style support. http://www.w3.org/TR/DOM-Level-2-Style/

Examples of appropriate bugs: document.styleSheets doesn't hold missing file:// stylesheets; crash setting element.style.color to 'red'.

This is not the place for most style bugs unless they involve scripting. See the Style System and Layout components.

  • DOM: Device Interfaces

This component covers WebAPIs exposing device interfaces for communication, networking, multimedia, etc. https://wiki.mozilla.org/WebAPI

  • DOM: Events

For bugs in our DOM Events support. This component deals with event bubbling, event handling, and interfaces such as UIEvent. http://www.w3.org/TR/DOM-Level-2-Events/

Examples of appropriate bugs: cannot cancel 'submit' event; crash when handling a DOMNodeInserted event after inserting a node into anonymous content.

  • DOM: IndexedDB

This component covers the IndexedDB implementation in Gecko. https://developer.mozilla.org/en/IndexedDB

  • DOM: Workers

This component covers the Web Workers implementation in Gecko.

  • Drag and Drop

Description: Problems with drag and drop functionality anywhere in the applications.

  • Editor

For bugs in Mozilla's embeddable editor. http://www.mozilla.org/editor/ If you're encountering a bug with text or rich text editing elsewhere within Gecko-based products, such as within Mail/News, the Location bar, or a dialog box, file it here.

Examples of appropriate bugs: After inserting a image, selecting Undo crashes Composer; After deleting a word, the caret disappears.

  • Embedding: APIs

The embedding API is the set of functions that an external application uses to host an instance of the layout engine within itself. The embedded layout engine provides services for rendering web content (HTML, XML, CSS, etc).

  • Embedding: GRE Core

Gecko Runtime Environment is the minimum set of files which are required for running applications written to embed the Gecko browsing engine. It contains the core xpcom libraries, nspr library, a set of key XPCOM components and other supporting files.

  • Embedding: Mac

Covers issues and bugs specific to embedding in Mac Carbon or Cocoa applications.

  • Embedding: MFC Embed

For problems with the mfcEmbed application or the mfcEmbed components

  • Embedding: Packaging

This module is comprised of the makefiles and scripts in embedding/config which are used to build the dist/Embed package. Several embedding applications are built from the contents of dist/Embed as well as the packaged version of MfcEmbed.

  • Event Handling

Any strangeness with keyboard typing, mouse actions, focus changes.

  • File Handling

For issues dealing with helper applications, and guessing Content Types when they aren't specified/known (ftp:, file:, jar:, but generally not http:). This component does not cover: backend networking issues, such as those covered by Networking: FTP or Networking: File, nor does it cover the Download Manager which has its own component in Toolkit.

  • Find Backend

The description in bugzilla is seriously, 

<blink>Component description needed</blink>

Cannot bear to edit that. It should stay that way forever!

  • Gecko Profiler

The backend to the built-in profiler which can be used in order to get profiling information from within Gecko.

  • General

For bugs in Core which do not fit into other more specific Core components

  • Geolocation

The geolocation API and framework enables reporting a physical location, in cooperating with a location provider (such as a GPS).

  • GFX: Color Management

qcms and other issues relating to Mozilla's color management implementation.

  • Graphics

Mapping of cross platform rendering interfaces to Cairo APIs.

  • Graphics: Layers

The graphics subsystem that implements hardware-accelerated (and software) composition of layers of content.

  • Graphics: Text

Text and font support in Gecko, including text shaping and font selection.

  • Hardware Abstraction Layer (HAL)

For bugs in the Hardware Abstraction Layer (HAL) code regardless of the backend. Example of appropriate bugs: implementation of a new feature for a backend, fixing a bug for a specific backend or general bugs regarding HAL.

  • History: Global

This is the global history which tracks all URLs that a user has visited, across all sessions of the browser. This also includes the history window and link coloring. Examples of appropriate bugs: Chrome URLs incorrectly added to global history, Reproducible crash when sorting by Title in History window, misbehaviour in the History sidebar tab.

  • HTML: Form Submission

This component is for bugs with HTML form submission. For example, "hidden controls don't get submitted to the server".

  • HTML: Parser

This system consumes content from the web, parses, validates and builds a content model (document)

  • Identity

Persona / BrowserID Gecko and Firefox integration

  • Image Blocking

For bugs about (un)blocking images from servers.

  • ImageLib

ImageLib decodes GIF, JPEG and PNG images, and provides the decoded data to the Compositor for display. If Firefox or Seamonkey can display an image when loaded separately from the page, ImageLib is working, and the actual imaging bug exists elsewhere within Firefox or Seamonkey.

Examples of appropriate bugs: PNG gAMA chunk ignored; Crashes on GIF w/corrupted frame(merr-01.gif); or PNGs and JPEGs aren't displayed on FreeBSD.

  • Installer: XPInstall Engine

For bugs in the underlying cross-platform installation technology. If you encounter an installation failure via a web page, it probably belongs here. Content developers should also report failures of the XPInstall API to this component.

Examples of appropriate bugs: Installer not installing all files; FinalizeInstall() doesn't check or return error codes; or Text from XPInstall confirmation dialog needs revision.

  • Internationalization

Internationalization is the process of designing and developing a software product to function in multiple locales. This process involves identifying the locales that must be supported, designing features which support those locales, and writing the code needed.

  • IPC

Inter-process communication mechanism used to isolate plugins and content in separate processes, also known as the Electrolysis project. See https://wiki.mozilla.org/Content_Processes for more details.

  • Java to XPCOM Bridge

For bugs with the interoperability between XPCOM components and Java objects.

  • JavaScript Engine

The interpreter engine for the core JavaScript language, independent of the browser's object model. File ONLY core JavaScript language bugs in this category. For bugs involving browser objects such as "window" and "document", use the "DOM" component. For bugs involving calls between JavaScript and C++, use the "XPConnect" component.

  • jemalloc

For bugs relating to improving and integrating jemalloc.

Crashes in jemalloc are usually someone else's fault. Please file the bugs based on the caller instead of in this component.

  • js-ctypes

js-ctypes is a ffi (Foreign Function Interface) component for JS/XPCOM. js-ctypes allows developers to call functions in dlls/shared libraries directly from JavaScript without the need to create binary XPCOM wrappers.

  • Keyboard: Navigation

Covers keyboard shortcuts, access keys/accelerators, and navigation by using the keyboard (not the mouse or other input device).

Examples: Ctrl+W not closing the browser window under Windows. Command+N not opening a new browser window under Mac OS. Alt+left arrow not going to the previous page under Linux. Alt not accessing the menu or access keys under Windows. Also, the debate as to use Alt or Ctrl under linux as the keyboard accelerator key for shortcuts. Requests for additional keyboard shortcuts.

  • Layout

For triage, reduction, and reassignment to other layout components.

  • Layout: Block and Inline

Core layout and geometry for basic block and line elements. For example, margin collapsing bugs, border rendering bugs, and bugs with the inline box model belong here.

  • Layout: Floats

Issues with CSS floats or left/right aligned images. For example, bugs with the 'float' and 'clear' properties belong here.

  • Layout: Form Controls

For problems with HTML Form Elements: buttons, images, edit fields, passwords, file controls, submit buttons, selects, and textareas. NOT for file upload dialog problems, those belong in XP Toolkit/Widgets.

  • Layout: HTML Frames

For rendering and layout issues with frames (<iframe>, <frame> and <frameset> elements in HTML).

  • Layout: Images

Bugs related to the layout of images. Use ImageLib for issues with the decoding of images.

  • Layout: Misc Code

For code-level bugs in things like the pres shell, etc.

  • Layout: R & A Pos

Relative, Absolute, and Fixed positioning, except when printing. If you don't know what this is then please don't move bugs here, instead select "Layout".

  • Layout: Tables

For bugs in the CSS and HTML table layout and rendering code. For example bugs with the HTML 'rules' attribute or the CSS 'border-collapse' property belong here.

  • Layout: Text

For problems with enumerating and rendering system fonts, glyph substitution, fallbacks when specified font not available and legibility. Bugs with the CSS 'font' properties belong here.

  • Layout: View Rendering

Painting problems. If the object is in the right place, but doesn't paint correctly, it's a view system bug. If it paints OK, but in the wrong place, then it belongs in another Layout component. Bugs with the 'opacity', 'z-index', 'overflow', and 'clip' properties usually belong in this component. (In terms of code, this covers the view/ and gfx/src/nsBlender* directories.)

  • Localization

Localization is the process of adapting software for a specific international market; this process includes translating the user interface, resizing dialog boxes, replacing icons and other culturally sensitive graphics (if necessary) as well as customizing features.

  • mach

For bugs related to the "mach" command-line tool.

  • MathML

Mathematical Markup Language

  • MFBT

File bugs here for headers, macros, data structures, methods, and other functionality which should be available to SpiderMonkey and to all Gecko code, implemented in the mfbt/ source directory.

  • mozglue

For issues in the Android glue, the custom dynamic linker or other parts of the mozglue library.

  • Nanojit

JIT Compiler Infrastructure shared by Mozilla's TraceMonkey compiler and Adobe's Tamarin compiler.

  • Networking

For bugs in Mozilla's modular networking library (aka "Netlib" or "Necko".) The networking library supplies the software interface that Mozilla uses to access physical transports (e.g. the Internet and local drives), perform URL resolutions, and handle a variety of networking protocols.

Examples of appropriate bugs: URLs with backslash not fetched; URLs starting with a single slash turn into http:///; Cannot access authenticated FTP site.

  • Networking: Cache

For bugs in the cache, which stores recently accessed data for more rapid access. Includes the disk cache, memory cache, and all cache preferences.

Examples of appropriate bugs: Implement compression of network cache data; or Implement partial HTTP caching.

  • Networking: Cookies

A general mechanism which server side connections (such as CGI scripts) can use to both store and retrieve information on the client side of the connection. This refers to HTML cookies; little blobs of data we store and share with sites

  • Networking: DNS

For bugs in Mozilla's implementation of DNS (Domain Name Service)

  • Networking: Domain Lists

Requests for changes to the TLD whitelist for IDN (registry representatives only) or the Public Suffix List

  • Networking: File

For bugs in Mozilla's File IO code. This component deals with File specific issues like writing to disk, reading local files, etc Related problems with file:// protocol may also be addressed here.

  • Networking: FTP

For bugs in Mozilla's FTP code. This component deals with FTP specific issues like downloading, directory formats, problems with FTP login, or resuming partial downloads, etc.

Examples of appropriate bugs- Problems with multiple occurrences of files in directory listings, corruption in downloading certain files via FTP, etc.

  • Networking: HTTP

For bugs in Mozilla's HTTP networking code. This component deals with HTTP specific issues like pipelining, keep-alive, HTTP proxies, 1.1 issues, redirects, authentication (basic), etc.

Examples of appropriate bugs: Problems with proxy authentication; HTTP redirects looping indefinitely, etc.

  • Networking: JAR

For bugs relating to the jar protocol handler, .jar file handling, and .jar directory browsing.

  • Networking: WebSockets

For bugs in Mozilla's web sockets implementation, especially protocol and network-related issues. Issues which are specific to the web sockets DOM interface may be better classified as Core::DOM.

  • Permission Manager

For bugs related to the permission manager but not the permission management. Example of appropriate bugs: permissions in the database are ignored or removing permission doesn't work. Example of inappropriate bugs: feature F should use permission P or any user interface related bugs.

  • Plug-ins

Bugs in core Mozilla code that supports registering and using plug-ins. For bugs in specific plugins, please file those bugs under Plugins.

  • Preferences: Backend

For bugs in libPref, the backend library that reads, parses, and writes preferences to the user's hard disk. Unless you're a Mozilla developer, your bug probably doesn't belong in this component.

Examples of appropriate bugs: prefs.js on the mac has non-mac style line endings; Large libpref string causes dialogs to crash on Linux; or JS Error at startup reading prefs file on migrated profile.

Core Graveyard

Data Safety

Tracking issues regarding handling of user data for maximal user benefit, in accordance with our privacy principles.

Datazilla

Datazilla is a system for managing and visualizing application performance data. The project includes a database, web service, and several user interfaces. The source code repository, https://github.com/mozilla/datazilla/, and documentation, http://datazilla.readthedocs.org, can be found at these locations. The primary project data managed by datazilla includes Talos performance data. Datazilla web services for individual projects are deployed at specific uri paths: https://datazilla.mozilla.org/stoneridge/ (stoneridge project) and https://datazilla.mozilla.org/talos/ (talos project).

Derivatives

Developer Documentation

Requests for new developer documentation or for corrections to existing developer documentation on the Mozilla Developer Network wiki. Both open web and Mozilla-specific documentation are maintained here.

Directory

The Lightweight Directory Access Protocol (LDAP) project (more info)

Documentation

Extend Firefox

For issues related to the Extend Firefox contest, web site, etc. Finance:  For track signature requests (offer letters, banking documents, contracts, PO requests)

Fennec Graveyard

Firefox

The Mozilla Foundation's next-generation web browser.


Firefox Affiliates

The Firefox Affiliates program is a great way to share your love of Mozilla Firefox. Host Firefox buttons on your site and climb your way to fame on the Affiliates leaderboard.

Firefox for Android

Boot2Gecko (B2G) is Mozilla's complete operating system built on web standards

Firefox for Metro

Firefox Graveyard

Firefox Health Report

For all bugs involving collection, submission, analysis and user-facing features (about:healthreport) as part of the Firefox Health Report product

Grendel

Input

The feedback tool for Firefox

  • Backend: General Backend Issues
  • Code Quality: Tasks related to code quality and general betterness.
  • Dashboard: Bugs with the Input Dashboard
  • Frontend: HTML/CSS/JS issues
  • General: For bugs not related to any specific component.
  • GrouperFish: Bugs related to GrouperFish
  • Search: Bugs related to Search
  • Sites: Bugs related to Sites
  • Submission: Bugs related to feedback submission
  • Themes: Bugs related to Themes

Internet Public Policy

The Mozilla Internet Public Policy group works to build products that make the Web more robust and take action when the web’s DNA is threatened.

JSS

Network Security Services for Java - a Java interface to NSS (more info)

L20n

Next-generation localization architecture (more info)

Legal

Mozilla Corporation Legal Team.

MailNews Core

Mail and news components common to Thunderbird and SeaMonkey

MailNews Core Graveyard

Marketing

Marketing and business-related ideas and projects (more info)

Marketplace

Mozilla's website (marketplace.firefox.com) to bring personalized discovery, worldwide distribution, and easy payments to the largest platform for app development: the Web.

  • Admin Tools: Problems and enhancements concerning tools and pages for app administration.
  • API: Issues and feature requests related to Marketplace APIs.
  • Code Quality: Coding standards and organization, minor notices/warnings/errors, refactoring
  • Consumer Pages: For problems with the user-facing portion of marketplace.mozilla.org. This includes Homepage, Apps details page, Account settings etc
  • Developer Pages: For issues with the Developer pages (Submission, Management and Documentation) of Apps.
  • General: If you are not clear where to file your bug/request, file here.

Integration: This component is for all tracking bugs for integration of Marketplace with Gaia, Identity and other products.

  • Payments/Refunds: Problems and enhancements concerning App purchase and refunds.
  • Reference Apps: Bugs relating to apps Mozilla maintains but does not ship with Gaia. These are apps on the Marketplace that also serve as a best practice reference for Open Web Apps.
  • Reviewer Tools: Problems and enhancements concerning tools and pages for app reviewers.
  • Search: Problems and enhancements concerning Marketplace search.
  • Security: Problems and enhancements concerning Marketplace security.
  • Statistics: Problems and enhancements concerning the developers' Statistics Dashboard or related scripts.
  • Validation: Bugs and feature requests concerning app validation.

Minimo

Mozilla Communities

Individual Mozilla communities, such as those formed around a country or localization, have components in this product for tracking community issues.

Mozilla Corporation

Internal issues regarding the Mozilla Corporation

Mozilla Developer Network

For bugs and requests related to management of the Mozilla Developer Network.

Mozilla Grants

Grants from the Mozilla Foundation.

Mozilla Labs

For bugs and requests related to management of Mozilla Labs and related projects.

Mozilla Labs Graveyard

Mozilla Localizations

Mozilla Messaging

Mozilla Metrics

Internal Mozilla Corp. database to house statistical/market data

Mozilla PR

Internal issues for the Mozilla Press Relations department

Mozilla QA

For bugs and requests related to management of Mozilla QA related projects.

Mozilla QA Graveyard

Mozilla Reps

More info about MozillaReps can be found on http://wiki.mozilla.org/ReMo

Mozilla Services

mozilla.org

The administration of the Mozilla Project and its servers (Website content bugs will belong in the www.mozilla.org product)

mozillaignite

A joint project with Mozilla and the National Science Foundation (NSF) where we're looking to help people make apps that utilize the capability of the 1gb network that genie provides and improve peoples lives.

NSPR

The Netscape Portable Runtime - Mozilla's cross-platform portability layer (more info)

NSS

Network Security Services - a cross-platform security library (more info)

Other Applications

Other Applications Graveyard

Pancake

For bugs related to Pancake

Petri

Petri is a Mozilla PaaS/IaaS offering (more info)

Penelope

Eudora meets Thunderbird (more info)

Plugins

For problems with third party plugins (NPAPI), AntiVirus applications and Firewalls. This product is for enabling collaboration between mozilla.org and third party software vendors. Vendors will be recognized, and able to mark bugs as fixed with references to their software versions.

Privacy

Privacy and policy, including privacy reviews, data data release proposals, and modifications to privacy policies. Bugs and feature requests in software should be filed against those products. (info)

quality.mozilla.org

For issues relating to the quality.mozilla.org website, also known as QMO.

Rhino

An implementation of JavaScript in Java (more info)

SeaMonkey

Servo

Skywriter

Mozilla Skywriter is a product, designed in Mozilla Labs, that proposes an open, extensible, web-based framework for code editing that aims to increase developer productivity, enable compelling user experiences, and promote the use of open standards.

  • More info:
  • Add-ons & Plugins: Bugs and feature requests related to extensions of the Mozilla Skywriter platform.
  • Collaboration: Bugs and feature requests related to the Mozilla Skywriter collaboration feature.
  • Command Line: Bugs and feature requests related to the Mozilla Skywriter command line.
  • Documentation: Bugs and feature requests related to documentation of Mozilla Skywriter.
  • Editor: Bugs and feature requests related to the Mozilla Skywriter editor.
  • Embedded: Bugs and feature requests related to embedded-specific tools and APIs.
  • File Explorer: Bugs and feature requests related to the Mozilla Skywriter file explorer.
  • General: General bugs and feature requests for Mozilla Skywriter. Uncategorized bugs should go here.
  • Infrastructure: Bugs and feature requests related to administration of bespin.mozillalabs.com and other developer resources for Mozilla Skywriter.
  • Key Bindings: Bugs and feature requests related to key bindings within Mozilla Skywriter.
  • Search: Bugs and feature requests related to searching within Mozilla Skywriter.
  • Server: Bugs and feature requests related to the Mozilla Skywriter server backend.

Syntax Highlighting: Bugs and feature requests related to syntax highlighting within Mozilla Skywriter.

  • Thunderhead: Bugs and feature requests related to the Thunderhead toolkit.
  • User Interface: Bugs and feature requests related to the user interface of Mozilla Skywriter.
  • Version Control: Bugs and feature requests related to the Mozilla Skywriter version control feature.

Snippets

The about:home snippet service is a simple, highly-cached content management service. It is intended to assemble and deliver content snippets to the about:home page in Firefox. The content delivered is determined by details about the installation of Firefox requesting content - including mainly details about the browser's build, locale, platform, and distribution channel, but not the person using the browser.

Socorro

For issues with the Socorro server which accepts and processes Breakpad crash reports.

support.mozilla.org

For bugs and requests related to management of the Sumo, sometimes known as support.mozilla.org.

support.mozilla.org Graveyard

support.mozillamessaging.com

For bugs and requests related to management of the Mozilla Messaging "Knowledge Base (KB)"- known as "SuMoMo."


Talkilla

For bugs related to Talkilla

Tamarin

Next-generation JavaScript 2 virtual machine (more info)


Tech Evangelism

For reporting web pages that need to be upgraded to support web standards and Gecko-based browsers. And for reporting add-ons that exhibit common problems that make Firefox run sub-optimally. (more info)


Testing

For bugs related to automated testing of Mozilla client code (Firefox, Thunderbird, Fennec, Gecko, etc) (More info)

Testopia

Testopia is a test case management system that sits on top of Bugzilla.

Thunderbird

Toolkit

The platform toolkit underlying Mozilla's "Aviary"-style applications. (More info)

Tracking

For tracking bugs that cross multiple products and services

Untriaged Bugs

Web Apps

Web Apps are applications that run on any device, and can be distributed through any store or directly by the developer.

Webmaker

The Mozilla Foundation's project to build a generation of web makers (more info)

Webtools

For bugs in the tools that mozilla.org uses. This includes web-based tools like MXR, Bonsai, and Tinderbox but not Bugzilla (see above). It also includes bugs in tools such as mozbot.

Webtools Graveyard

Websites

For issues with content of Websites managed by Mozilla that do not have their own Bugzilla products.

Websites Graveyard

www.mozilla.org

For issues with content on www.mozilla.org http servers (but not the functioning of the servers) (more info)

Retrieved from "https://wiki.mozilla.org/index.php?title=Bugzilla_Products&oldid=658558"