Platform/UI Team: Difference between revisions
(Adding cliffhanger.) |
(Starting to formulate the team...) |
||
| Line 1: | Line 1: | ||
The Platform group now has a UI Team. | |||
=Purpose= | |||
As Gecko has grown and changed, teams to work on it (or the products it supports) have naturally formed in order to specialize in particular things. | |||
The UI of Firefox Desktop, for example, is for the most part managed by the Firefox Desktop team. | |||
The Platform teams and Firefox teams are co-dependent, but oftentimes priorities between the two groups do not line up perfectly. If Platform has a goal to ship some new feature that requires UI, and the Firefox team has no cycles to help develop the UX or UI, then it that feature will often languish. | |||
The purpose of this team is to attempt to service the UI requests of the various teams under platform, either as consultants, or implementors, or a combination of both. | |||
The team is well integrated and in constant communication with the other front-end teams in order to ensure that as a whole we are not working at cross-purposes. | |||
=People= | |||
* Mike Conley (:mconley) - Lead | |||
* Dale Harvey (:daleharvey) | |||
=Process= | |||
Until further notice, this team will function in roughly the following way: | |||
# Work is selected from the queue <p>We might solicit help from higher levels in the Platform org in order to help us determine what work is most important to begin</p> | |||
# The project is evaluated and defined <p>In particular, answers to the following questions must be formulated:</p> | |||
## Is this work truly necessary as requested? If so, why? | |||
## What does "done" look like, and how do we evaluate it? (This could be as simple as closing a set of bugs, or some performance or Telemetry number crossing a certain threshold, etc) | |||
## How will we test what we build? | |||
## | |||
=Participation= | |||
=Putting Work into the Queue= | |||
* TBD | |||
=Present Projects= | |||
* TBD | |||
Revision as of 04:55, 27 May 2016
The Platform group now has a UI Team.
Purpose
As Gecko has grown and changed, teams to work on it (or the products it supports) have naturally formed in order to specialize in particular things.
The UI of Firefox Desktop, for example, is for the most part managed by the Firefox Desktop team.
The Platform teams and Firefox teams are co-dependent, but oftentimes priorities between the two groups do not line up perfectly. If Platform has a goal to ship some new feature that requires UI, and the Firefox team has no cycles to help develop the UX or UI, then it that feature will often languish.
The purpose of this team is to attempt to service the UI requests of the various teams under platform, either as consultants, or implementors, or a combination of both.
The team is well integrated and in constant communication with the other front-end teams in order to ensure that as a whole we are not working at cross-purposes.
People
- Mike Conley (:mconley) - Lead
- Dale Harvey (:daleharvey)
Process
Until further notice, this team will function in roughly the following way:
- Work is selected from the queue
We might solicit help from higher levels in the Platform org in order to help us determine what work is most important to begin
- The project is evaluated and defined
In particular, answers to the following questions must be formulated:
- Is this work truly necessary as requested? If so, why?
- What does "done" look like, and how do we evaluate it? (This could be as simple as closing a set of bugs, or some performance or Telemetry number crossing a certain threshold, etc)
- How will we test what we build?
Participation
Putting Work into the Queue
- TBD
Present Projects
- TBD