154
edits
Changes
Add a variety of information on bugzilla whiteboard tags and contributor resources
The Platform Layout Team is primarily responsible for [http://en.wikipedia.org/wiki/Gecko_%28layout_engine%29 Gecko's] style system and layout engine. We strive to build and maintain an engine that is both high-performance and standards-compliant, while providing support for features unique to Firefox.
* SVG
* '''Matrix/Riot.IM''': [https://chat.mozilla.org/#/room/#layout:mozilla.org #layout on chat.mozilla.org]
* '''Slack''': #layout on Slack (MoCo employees only)
* '''E-mail''': [https://lists.mozilla.org/listinfo/dev-tech-layout platform Subscribe to dev-tech-layoutplatform@lists.mozilla.org]
* Synchronous discussions about engineering-specific topics (bugs, patches, code reviews, architectural issues, etc.) should happen in Matrix[https:/Riot/chat.mozilla.org/#/room/#layout:mozilla.org #layout on chat.mozilla.IMorg].
* Synchronous discussions about team operations, announcements, strategy, roadmap, and other banter tend to happen in Slack (private to Mozilla employees and NDA'd contributors), unless such communications can ''and should'' be made public.
This [https://trello.com/b/k1vqA7Kk/firefox-layout-project-tracking project tracker on Trello] contains all work-in-progress and backlog items that the team is considering for the near future. Note that this list is subject to change at any time.
For more detailed information, [https://docs.google.com/document/d/1ySAAbTiLGonljjkM01ZIyz1P_W1A2dk5Cj_oi-550mo/edit notes from the team's weekly standup meetings] are available.
We use the <code>[layout:backlog]</code> tag in the whiteboard field on bugs, tasks and enhancements to track work items that are either under active development, or being considered for development within the next year.
* '''P5''' — No plans to work on this item, but will accept contributor patches.
=== Commonly-Used Backlog Queries === * [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&classification=Other&priority=P1&resolution=---&status_whiteboard_type=allwordssubstr&product=Core&component=CSS%20Parsing%20and%20Computation&component=CSS%20Transitions%20and%20Animations&component=DOM%3A%20CSS%20Object%20Model&component=Layout&component=Layout%3A%20Block%20and%20Inline&component=Layout%3A%20Columns&component=Layout%3A%20Flexbox&component=Layout%3A%20Floats&component=Layout%3A%20Form%20Controls&component=Layout%3A%20Generated%20Content%2C%20Lists%2C%20and%20Counters&component=Layout%3A%20Grid&component=Layout%3A%20Images%2C%20Video%2C%20and%20HTML%20Frames&component=Layout%3A%20Positioned&component=Layout%3A%20Ruby&component=Layout%3A%20Scrolling%20and%20Overflow&component=Layout%3A%20Tables&component=Layout%3A%20Text%20and%20Fonts&component=Print%20Preview&component=Printing%3A%20Output&component=Printing%3A%20Setup&component=SVG&status_whiteboard=%5Blayout%3Abacklog All P1 Backlog Items] = Release Notes ==
We publish [https://wiki.mozilla.org/Platform/Layout/ReleaseNotes notes and lists of all fixed layout bugs] for a given release. These release notes call out items of particular importance (new features, webcompat fixes) that may be helpful for web content authors.
= Bugs and Bugzilla =
== Filing a Bug ==
* [https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&component=SVG SVG]
== Bug Triage Process & Guidelines == If you're curious about how we triage and prioritize bugs, please visit [[Platform/Layout/Triage|our triage page]] for more information. This page includes information about our triage process and guidelines, as well as useful triage-related bug queries. == Whiteboard Tags == We use the following strings (tags) in the whiteboard field on bugs in Bugzilla to track important metadata: * <code>[layout:backlog]</code>: Indicates the bug is in our backlog, and is either under active development, or planned development for the coming year (see bug priority for approximate timeline).* <code>[layout:triage-discuss]</code>: Indicates that we plan to discuss this bug in more detail at one of our internal, bi-weekly triage meetings. Usually this is set if the severity level is disputed, or in question, or other triage details of the bug are unclear.
If you're looking for a good first bug to fix, the following resources may help:
