Platform/Layout: Difference between revisions

← Older edit

Platform/Layout (view source)

Revision as of 18:36, 14 March 2024

2,054 bytes removed , 14 March 2024

modifications to merge the pages bug, backlog and triage and reduce redundant info

Vfalstad

25

edits

@@ Line 9: / Line 9: @@
 * Printing
 * SVG
+* Fonts and Typography
 = Contact Information =
 * '''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-platform Subscribe to dev-platform@lists.mozilla.org]
@@ Line 19: / Line 19: @@
 * Synchronous discussions about engineering-specific topics (bugs, patches, code reviews, architectural issues, etc.) should happen in [https://chat.mozilla.org/#/room/#layout:mozilla.org #layout on chat.mozilla.org].
-* 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.
 = Roadmap and Status =
-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.
+== Kanban Board ==
+[https://gecko.layout.team/?title=Firefox+Platform+Layout+Backlog&name=Backlog&query=status%3ANEW+priority%3AP2%2CP3+%5Blayout%3Abacklog&name=Upcoming&query=status%3ANEW+priority%3AP1+%5Blayout%3Abacklog&name=In+Progress&query=status%3AASSIGNED+%5Blayout%3Abacklog&name=Recently+Fixed&query=resolution%3AFIXED+milestone%3A77%2C78%2C79+%5Blayout%3Abacklog Our Bugzilla kanban board] is a quick way to find out what bug fixes and enhancements are upcoming or in progress.
-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.
+== Standup Notes ==
+For very detailed information, [https://docs.google.com/document/d/1BbKGHgmDjD87f6Dt4mMXrZysch5END7AoCIY1cwGSdY/edit?usp=sharing notes from the team's weekly standup meetings] are available.
-== Backlog Tracking in Bugzilla ==
+<br/>
-For more detailed backlog and development information, check the status of things in Bugzilla.
+For standup notes prior to 2024, please see the [https://wiki.mozilla.org/Platform_Layout_Archive Layout Archive]
-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.
-We use bug priorities to indicate how soon we plan to work on a bug, task or enhancement according to the following classifications (assuming the bug also has the <code>[layout:backlog]</code> whiteboard tag):
-* '''P1''' — Under active development, or planned development for the current or next release cycle.
-* '''P2''' — Near-term backlog item, can/will be worked on soon (within the next 2-3 months).
-* '''P3''' — Longer-term backlog item, planned to work on within the next year.
-* '''P4''' — N/A
-* '''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 =
@@ Line 48: / Line 34: @@
 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 =
+= Bugs and Triage =
 == Filing a Bug ==
@@ Line 62: / Line 48: @@
 * [https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&component=Layout:+Flexbox Layout: Flexbox]
 * [https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&component=Layout:+Floats Layout: Floats]
-* [https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&component=Layout:+Form Controls Layout: Form Controls]
+* [https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&component=Layout:+Form Layout: Form]
 * [https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&component=Layout:+Generated+Content,+Lists,+and+Counters Layout: Generated Content, Lists, and Counters]
 * [https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&component=Layout:+Grid Layout: Grid]
@@ Line 78: / Line 64: @@
 == 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.
+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 and backlog related bug queries.
 == Whiteboard Tags ==
@@ Line 88: / Line 74: @@
 * <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.
-We also use whiteboard tags to track bugs for longer-running projects. For more information on these projects and their associated tags, see the pages below:
-* [[Platform/Layout/Printing and fragmentation|Printing and Fragmentation Improvements]]
 = Contributing =
@@ Line 96: / Line 80: @@
 We always welcome new contributors! Here are a few things you can do to get started:
-* Read the [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Build_Instructions/Simple_Firefox_build instructions for building Firefox] on developer.mozilla.org.
+* Read through the [https://firefox-source-docs.mozilla.org/ Firefox docs], particularly the [https://firefox-source-docs.mozilla.org/contributing/contribution_quickref.html Firefox Contributor's Quick Reference Guide.]
+* Follow the [https://firefox-source-docs.mozilla.org/setup/index.html instructions for building Firefox].
 * Read the [https://wiki.mozilla.org/Gecko:Overview programmer's primer on Gecko], particularly the [https://wiki.mozilla.org/Gecko:Overview#Layout layout section].
-* Get familiar with the [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Coding_Style Mozilla code style guidelines].
+* Get familiar with the [https://firefox-source-docs.mozilla.org/code-quality/coding-style/index.html Mozilla code style guidelines].
 == Starter Bugs ==
@@ Line 105: / Line 90: @@
 * [https://www.joshmatthews.net/bugsahoy/?layout=1&dom=1&simple=1 Simple layout bugs on Bugs Ahoy!]
-* [https://mzl.la/2MVpCeL Layout bugs marked as "good-first-bug" on Bugzilla]
+* [https://mzl.la/42XIEcg Layout bugs marked as "good-first-bug" on Bugzilla]
+[[Category:Platform]]
+[[Category:Layout]]