Firefox/Metro: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
 
(762 intermediate revisions by 9 users not shown)
Line 1: Line 1:
<h2> Overview </h2>
=Firefox for Windows 8 Touch=
<p>To produce and maintain a version of Firefox that is able to function as the default browser on Windows 8 Metro.
<p> </p>
</p>
 
<h2> Metro Bug Queries </h2>
==Production Summary==
<h3>Features</h3>
 
<ul><li> <a href="http://btfy.me/839cjw">Bugs Nominated as Required for MVP</a>
Metro Firefox is not planned to be released as part of main stream Firefox.
<ul><li> Nominations are currently done by adding "[metro-mvp?]" in the whiteboard field.
Development can continue on the project branch located at: https://hg.mozilla.org/projects/metro/
</li></ul>
 
</li></ul>
<p> </p>
<ul><li> <a href="http://btfy.me/hfqm7t">Open Minimum Viable Product Features</a>
'''Note:'''  Next update on Monday March 17 following the conclusion of Iteration 30C-29A-28B.3
<ul><li> MVP features are marked with "[metro-mvp]" in the whiteboard and have the keyword "Features" set.
<p> </p>
</li></ul>
At the conclusion of Iteration IT-30C-29A-28B.2:
</li></ul>
* Points Completed:  '''47'''
<ul><li> <a href="http://btfy.me/8f32gt">Open Minimum Viable Product Bugs</a>
* Bugs Resolved:  '''17'''
<ul><li> MVP bugs are marked with "[metro-mvp]" in the whiteboard.
* Team Velocity:  '''56'''
</li></ul>
* Velocity Range:  '''46 - 68'''
</li></ul>
<p> </p>
<ul><li> <a href="http://btfy.me/8hfdx3">All Minimum Viable Product Features (Open &amp; Closed)</a>
* '''Previous Performance''' - [https://wiki.mozilla.org/Firefox/Metro/DevelopmentSummary View Archive]
<ul><li> MVP features are marked with "[metro-mvp]" in the whiteboard and have the keyword "Features" set.
 
</li></ul>
==Development Update==
</li></ul>
<p> </p>
<ul><li> <a href="http://btfy.me/dvtwqf">All Minimum Viable Product Bugs (Open &amp; Closed)</a>
'''Note:'''  Next update on Monday March 17 following the conclusion of Iteration 30C-29A-28B.3
<ul><li> MVP bugs are marked with "[metro-mvp]" in the whiteboard.
<p> </p>
</li></ul>
At the conclusion of Iteration IT-30C-29A-28B.2:
</li></ul>
<p> </p>
<ul><li> <a href="http://btfy.me/9vcwh6">All Minimum Viable Product Bugs with UIWanted set</a>
* Team completed 47 points across 17 bugs which resulted in a median velocity of 56 points per iteration.
<ul><li> MVP bugs are marked with "[metro-mvp]" in the whiteboard
** Team velocity decreased by 1 point (57 to 56) from the previous iteration.
</li><li> "uiwanted" keyword is used to call attention to bugs requiring UI development.
<p> </p>
</li></ul>
* At a median velocity of 56, there is a 90% likelihood that the actual velocity for the upcoming iteration will fall between 46 and 68.
</li></ul>
** There was no change in the velocity range from the previous iteration.
<h3>Level of Effort</h3>
<p> </p>
<p>Convention
* 35 points of work was not completed during Iteration IT-30C-29A-28B.2 and carried over.
</p>
** 27 points of work is Engineering related and 8 points is UX related.
<ul><li> Use "[LOE:*]" in the white board tag, replace the star with the following values
<p> </p>
<ul><li> S - small. task is 1 week or less.
* Team accomplished a 57% point closure rate during Iteration IT-30C-29A-28B.2.
</li><li> M - medium. task is up to 3 weeks.
<p> </p>
</li><li> L - large. task will take more than 3 weeks.
* Given the current median velocity there is a 90% likelihood that between 46 and 68 points of work, with a median value of 56, can be completed in the final iteration of the 30C-29A-28B release cycle.
</li><li>&#160;? - Missing a time estimate
<p> </p>
</li></ul>
* The remaining amount of work for the 30C-29A-28B release cycle totals 77 points for the final iteration:  [https://wiki.mozilla.org/Firefox/Metro#Release_Plan View Release Plan]
</li></ul>
<p> </p>
<ul><li> <a href="http://btfy.me/7h9kd6">All Open Minimum Viable Product Bugs With Estimate Wanted</a>
* Given the volume of work remaining and our current velocity range, 9 - 31 points of work may carry over to the 31C-30A-29B release cycle.
<ul><li> MVP bugs are marked with "[metro-mvp]" in the whiteboard
<p> </p>
</li><li> LOE requests are marked with "[LOE:?]" or "[LOE:-]"
 
</li></ul>
==Product Backlog==
</li></ul>
<p> </p>
<h2> Meeting Times &amp; Communication Channels</h2>
All work related to the ongoing development and maintenance of the Firefox for Windows 8 Touch Product are collected and prioritized in the Product Backlog. The goals of the Product Backlog are to:
<h3>Communication</h3>
* Enable work to be prioritized so that the team is always working on the most important features.
<p>IRC:
* Support continual planning as the product emerges so the plan matches reality.
</p>
* Improve forecasts so that the stakeholders make the best decisions about the direction of the product.
<ul><li> #windev
<p> </p>
</li></ul>
'''Product Backlog:'''  [https://bugzilla.mozilla.org/show_bug.cgi?id=861680 View Bugzilla]
<p>MailingLists:
<bugzilla>
</p>
    {
<ul><li> dev-metro@lists.mozilla.org
        "include_fields": "id, summary, whiteboard",
</li><li> fx-team@lists.mozilla.com
        "blocks": "861680"
</li></ul>
    }
<h3>Team Meeting</h3>
</bugzilla>
<p>Thursday at 1pm PT (4pm ET)
<p> </p>
</p><p>Location: Jim Mathies Vidyo Room
 
</p><p>Dial-in:
==Release Plan==
</p>
<p> </p>
<pre class="_fck_mw_lspace">  US/International: +1 650 903 0800 x92 Conf# 99136
The Release Plan is a guideline that reflects expectations about which features from the Product Backlog will be implemented and when they are completed across multiple iterations for specific target releases. It also serves as a base to monitor progress with the ongoing development of the product.  The Release Plan is not static and will be revisited and updated at the conclusion of each iteration.
  US toll free: +1 800 707 2533 (pin 369) Conf# 99136
<p> </p>
  Canada: +1 416 848 3114 x92 Conf# 99136
'''30C-29A-28B Release Cycle'''
</pre>
<p> </p>
<p>Back Channel: #windev
* '''For IT-30C-29A-28B.1:'''
</p><p>Meeting Notes: <a href="https://etherpad.mozilla.org/metro-meeting-notes">Metro Meeting Notes Etherpad</a>
** With a median velocity of 59 points per iteration there is a 90% likelihood that between 141 and 204 points of work, with a median value of 177, can be completed over the three iterations of the 30C-29A-28B release cycle.
</p><p><br />
*** Bugs Resolved - 27
</p>
*** Points Completed - 46
<h3>User Experience Meeting</h3>
<p> </p>
<p>Monday at 1pm PT (4pm ET)
* '''For IT-30C-29A-28B.2:'''
</p><p>Location: Yuan Wang Vidyo Room
** With a median velocity of 57 points per iteration there is a 90% likelihood that between 92 and 136 points of work, with a median value of 115, can be completed over the two remaining iterations of the 30C-29A-28B release cycle.
</p><p>Dial-in:
*** Bugs Resolved - 17
</p>
*** Points Completed - 47
<pre class="_fck_mw_lspace">  US/International: +1 650 903 0800 x92 Conf# 99736
<p> </p>
  US toll free: +1 800 707 2533 (pin 369) Conf# 99736
* '''For IT-30C-29A-28B.3:'''
  Canada: +1 416 848 3114 x92 Conf# 99736
** There is a 90% likelihood that between 46 and 68 points of work, with a median value of 56, can be completed in the final iteration of the 30C-29A-28B release cycle.
</pre>
*** Bugs Resolved - Updated on March 17
<p>Back Channel: #windev
*** Points Completed - Updated on March 17
</p><p>Meeting Notes: https://firefox-ux.etherpad.mozilla.org/20
<p> </p>
</p>
'''Central 30 - Release: Jun 10, 2014'''
<h2> MoCo Team Members </h2>
<p> </p>
<p>Project Champion
<bugzilla>
</p>
    {
<ul><li>&#160;?
        "include_fields": "id, summary, status, whiteboard",
</li></ul>
        "whiteboard": "r=ff30"
<p>Product
    }
</p>
</bugzilla>
<ul><li> Asa Dotzler (asa@mozilla.com)
<p> </p>
</li></ul>
'''Aurora 29 - Release: Apr 29, 2014'''
<p>UX
<p> </p>
</p>
<bugzilla>
<ul><li> Yuan Wang (yuan@mozilla.com)
    {
</li><li> Stephen Horlander (shorlander@mozilla.com)
        "include_fields": "id, summary, status, whiteboard",
</li></ul>
        "whiteboard": "r=ff29"
<p>Metro Engineering
    }
</p>
</bugzilla>
<ul><li> Tim Abraldes (tabraldes@mozilla.com)
 
</li><li> Brian R. Bondy (bbondy@mozilla.com)
'''Beta 28 - Release: March 18, 2014'''
</li><li> Matt Brubeck (mbrubeck@mozilla.com)
<p> </p>
</li><li> Mark Finkle (mfinkle@mozilla.com)
<bugzilla>
</li><li> Sam Foster (sfoster@mozilla.com)
    {
</li><li> Jim Mathies (jmathies@mozilla.com)
        "include_fields": "id, summary, status, whiteboard",
</li><li> Ally Naaktgeboren (ally@mozilla.com)
        "whiteboard": "r=ff28"
</li><li> Frank Yan (fyan@mozilla.com)
    }
</li></ul>
</bugzilla>
<p>Graphics Team Support
<p> </p>
</p>
 
<ul><li> Bas Schouten (bschouten@mozilla.com)
==Iteration Backlog==
</li></ul>
<p> </p>
<p>Localization
The Iteration Backlog is a collection of Work that the team has committed to implement, test and deliver in a two-week iteration.
</p>
<p> </p>
<ul><li> Axel Hecht (axel@mozilla.com)
'''Current Iteration:'''  IT-30C-29A-28B.3 - Monday March 03 - Friday March 14
</li></ul>
<p> </p>
<p>Accessibility
<bugzilla>
</p>
    {
<ul><li> David Bolter (dbolter@mozilla.com)
        "include_fields": "id, summary, status, assigned_to, whiteboard",
</li></ul>
        "id": "784042, 818671, 858206, 881938, 904960, 942024, 951465, 953012, 961587, 962140, 963669, 963733, 966363, 967403, 967793, 968916, 972574, 974413, 976849, 977546, 977814, 977827, 979007, 979124, 979405"
<p>Program Management
    }
</p>
</bugzilla>
<ul><li> Martin Best (mbest@mozilla.com)
<p> </p>
</li></ul>
 
<p>Services
==Definition of Done==
</p>
The Definition of Done ensures a '''potentially shippable''' product increment is released at the conclusion of a release cycle.
<ul><li> Mike Connor (mconnor@mozilla.com)
<p> </p>
</li></ul>
Potentially Shippable Guidelines:
<p>Incoming Bug Triage
* Means Tested and Verified
</p>
* Does Not Mean Cohesive
<ul><li>&#160;?
<p> </p>
</li></ul>
'''Tested and Verified'''
<p>QA
* QA will be flagged to test work marked as 'Resolved' within the iteration.
</p>
* Any defects found will 'Reopen' the work subject to testing.
<ul><li> Juan Becerra (jbecerra@mozilla.com)
* If QA does not discover any defects the work will be marked as 'Verified'.
</li><li> Jason Smith (jsmith@mozilla.com)
* Only 'Verified' work will merge into a build at the conclusion of the release cycle.
</li></ul>
<p> </p>
<p><br />
'''Product Increment'''
Security
* A potentially shippable product increment means compliance with the work's individual acceptance criteria and not the full story under development.
</p>
<p> </p>
<ul><li>&#160;?
 
</li></ul>
==Bugzilla==
<p>Privacy
<p> </p>
</p>
The following format is used to maintain consistency in how bugs are filed:
<ul><li> Sid Stamm (sstamm@mozilla.com)
* p= (point value assigned to the bug)
</li></ul>
* s= (the iteration the bug is being developed in)
<p>RelEng
* r= (the target release of the bug under development)
</p>
* [story] (collection of related bugs required for the completion of a feature)
<ul><li> Armen Zambrano Gasparnian (armenzg@mozilla.com)
<p> </p>
</li></ul>
 
<p>Marketing
==Communication==
</p>
<p> </p>
<ul><li> Laura Forrest (lforrest@mozilla.com)
===General===
</li></ul>
<p> </p>
<p>Legal
* '''Mailing list:''' [https://mail.mozilla.org/listinfo/metro Metro List]
</p>
* '''IRC Channel:''' [irc://irc.mozilla.org/windev #windev]
<ul><li> Harvey Anderson (handerson@mozilla.com)
* '''Intranet:'''  [https://intranet.mozilla.org/Metro View Metro Page]
</li><li> James Murdock (jmurdock@mozilla.com)
<p> </p>
</li></ul>
 
===Iteration Planning/Status Meeting===
<p> </p>
* '''Time:'''  Mondays - '''1:00 PM''' Pacific, '''4:00 PM''' Eastern
* '''Duration:'''  1 hour
* '''[[Vidyo]] Room:'''  "Marco Mucci"
* '''Etherpad:''' [https://metro.etherpad.mozilla.org/ View MoPad]
{{Conf|9860}}
<p> </p>
 
===Iteration Performance Reports===
<p> </p>
* '''Iteration IT-30C-29A-28B.2:  Mon 2/17/14 - Fri 2/28/14''' - [https://wiki.mozilla.org/Firefox/Metro/IT-30C-29A-28B.2StatusReport View Performance Report]
* '''Previous Reports''' - [https://wiki.mozilla.org/Firefox/Metro/Iteration_Performance_Reports View Archive]
<p> </p>
 
==People==
 
{| class="wikitable fullwidth-table"
! Role !! Contacts !!
|-
| Project Champion ||
* Johnathan Nightingale (johnath@mozilla.com) (A,C,I)
|-
| Program/Project Management Oversight ||
* Sheila Mooney (smooney@mozilla.com) (A,C,I)
|-
| Program Management ||
* Marco Mucci (mmucci@mozilla.com) (R)
|- 
| Product Manager ||
* Chad Weiner (cweiner@mozilla.com) (A,C,I)
* Karen Rudnitski (krudnitski@mozilla.com) (A,C,I)
|-
| UX/Design ||
* Yuan Wang (yuan@mozilla.com) (R)
* Michael Maslaney (mmaslaney@mozilla.com) (R)
|-
| Dedicated Engineering ||
* Tim Abraldes (tabraldes@mozilla.com) (R)
* Brian R. Bondy (bbondy@mozilla.com) (R)
* Matt Brubeck (mbrubeck@mozilla.com) (R)
* Sam Foster (sfoster@mozilla.com) (R)
* Jim Mathies (jmathies@mozilla.com) (R)
* Ally Naaktgeboren (ally@mozilla.com) (R)
* Rodrigo Silveira (rsilveira@mozilla.com) (R)
* Marina Samuel (msamuel@mozilla.com) (R)
* Stephen Pohl (spohl@mozilla.com) (R)
* Aleh Zasypkin (azasypkin@mozilla.com) (R)
|-
| Graphics Team Support ||
* Manager - Milan Sreckovic (msreckovic@mozilla.com) (C,I)
* Dev - Kartikaya Gupta (kats@mozilla.com) (R)
* Dev - Botond Ballo (bballo@mozilla.com) (R)
|-
| Localization ||
* Axel Hecht (axel@mozilla.com) (R)
|-
  | QA ||
* Juan Becerra (jbecerra@mozilla.com) (R)
|-
| Services Integration ||
* Mike Connor (mconnor@mozilla.com) (I)
|-
| Privacy ||
* Sid Stamm (sstamm@mozilla.com) (A,C,I)
|-
| Release Management ||
* Bhavana Bajaj (bbajaj@mozilla.com) (C,I)
|-
| Marketing ||
* Laura Forrest (lforrest@mozilla.com) (I)
|-
| Legal ||
* Manager - Harvey Anderson (handerson@mozilla.com) (A,C,I)
* James Murdock (jmurdock@mozilla.com) (A,C,I)
|-
| Feedback ||
* Tyler Downer (tdowner@mozilla.com) (A,C,I)
* Manager - Matt Grimes (mgrimes@mozilla.com) (I)
|-
|}
 
The letters following each name stand for:
* R = Responsible for deliverable
* A = Accountable for the final decision making on some aspect of the project
* C = Needs to be consulted on key topics
* I = Needs to be kept informed
<p> </p>
 
==References==
<p> </p>
* Metro Preview Release - [https://wiki.mozilla.org/Firefox/Metro/MetroPreviewRelease View Release Proposal]
* Metro Test Day - [https://wiki.mozilla.org/Firefox/Metro/MetroTestDay View Test Plan]
* Mozmill Automated Testing:  [https://wiki.mozilla.org/Firefox/Metro/QA/Mozmill View Bug List]
* Developer documentation, build instructions: [[Firefox/Windows 8 Integration]]
* Metro Work Week I:  [https://wiki.mozilla.org/Firefox/Metro/WorkWeekI View First Work Week Event]
* Metro Work Week II:  [https://wiki.mozilla.org/Firefox/Metro/WorkWeekII View May 13 - May 17 Work Week Event]
* Metro Work Week III:  [https://wiki.mozilla.org/Firefox/Metro/WorkWeekIII View January 6 - January 10 Work Week Event]
* Asa's curated list of [https://wiki.mozilla.org/Firefox/Metro/Devices Non-sucky Windows 8 touch devices]
* Blockers:  [https://wiki.mozilla.org/Firefox/Metro/blockers View Queries]
<p> </p>

Latest revision as of 09:27, 21 April 2014

Firefox for Windows 8 Touch

Production Summary

Metro Firefox is not planned to be released as part of main stream Firefox. Development can continue on the project branch located at: https://hg.mozilla.org/projects/metro/

Note: Next update on Monday March 17 following the conclusion of Iteration 30C-29A-28B.3

At the conclusion of Iteration IT-30C-29A-28B.2:

  • Points Completed: 47
  • Bugs Resolved: 17
  • Team Velocity: 56
  • Velocity Range: 46 - 68

Development Update

Note: Next update on Monday March 17 following the conclusion of Iteration 30C-29A-28B.3

At the conclusion of Iteration IT-30C-29A-28B.2:

  • Team completed 47 points across 17 bugs which resulted in a median velocity of 56 points per iteration.
    • Team velocity decreased by 1 point (57 to 56) from the previous iteration.

  • At a median velocity of 56, there is a 90% likelihood that the actual velocity for the upcoming iteration will fall between 46 and 68.
    • There was no change in the velocity range from the previous iteration.

  • 35 points of work was not completed during Iteration IT-30C-29A-28B.2 and carried over.
    • 27 points of work is Engineering related and 8 points is UX related.

  • Team accomplished a 57% point closure rate during Iteration IT-30C-29A-28B.2.

  • Given the current median velocity there is a 90% likelihood that between 46 and 68 points of work, with a median value of 56, can be completed in the final iteration of the 30C-29A-28B release cycle.

  • The remaining amount of work for the 30C-29A-28B release cycle totals 77 points for the final iteration: View Release Plan

  • Given the volume of work remaining and our current velocity range, 9 - 31 points of work may carry over to the 31C-30A-29B release cycle.

Product Backlog

All work related to the ongoing development and maintenance of the Firefox for Windows 8 Touch Product are collected and prioritized in the Product Backlog. The goals of the Product Backlog are to:

  • Enable work to be prioritized so that the team is always working on the most important features.
  • Support continual planning as the product emerges so the plan matches reality.
  • Improve forecasts so that the stakeholders make the best decisions about the direction of the product.

Product Backlog: View Bugzilla

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 406 [1] => Not Acceptable ) ) 1

Release Plan

The Release Plan is a guideline that reflects expectations about which features from the Product Backlog will be implemented and when they are completed across multiple iterations for specific target releases. It also serves as a base to monitor progress with the ongoing development of the product. The Release Plan is not static and will be revisited and updated at the conclusion of each iteration.

30C-29A-28B Release Cycle

  • For IT-30C-29A-28B.1:
    • With a median velocity of 59 points per iteration there is a 90% likelihood that between 141 and 204 points of work, with a median value of 177, can be completed over the three iterations of the 30C-29A-28B release cycle.
      • Bugs Resolved - 27
      • Points Completed - 46

  • For IT-30C-29A-28B.2:
    • With a median velocity of 57 points per iteration there is a 90% likelihood that between 92 and 136 points of work, with a median value of 115, can be completed over the two remaining iterations of the 30C-29A-28B release cycle.
      • Bugs Resolved - 17
      • Points Completed - 47

  • For IT-30C-29A-28B.3:
    • There is a 90% likelihood that between 46 and 68 points of work, with a median value of 56, can be completed in the final iteration of the 30C-29A-28B release cycle.
      • Bugs Resolved - Updated on March 17
      • Points Completed - Updated on March 17

Central 30 - Release: Jun 10, 2014

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 406 [1] => Not Acceptable ) ) 1

Aurora 29 - Release: Apr 29, 2014

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 406 [1] => Not Acceptable ) ) 1


Beta 28 - Release: March 18, 2014

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 406 [1] => Not Acceptable ) ) 1

Iteration Backlog

The Iteration Backlog is a collection of Work that the team has committed to implement, test and deliver in a two-week iteration.

Current Iteration: IT-30C-29A-28B.3 - Monday March 03 - Friday March 14

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 406 [1] => Not Acceptable ) ) 1

Definition of Done

The Definition of Done ensures a potentially shippable product increment is released at the conclusion of a release cycle.

Potentially Shippable Guidelines:

  • Means Tested and Verified
  • Does Not Mean Cohesive

Tested and Verified

  • QA will be flagged to test work marked as 'Resolved' within the iteration.
  • Any defects found will 'Reopen' the work subject to testing.
  • If QA does not discover any defects the work will be marked as 'Verified'.
  • Only 'Verified' work will merge into a build at the conclusion of the release cycle.

Product Increment

  • A potentially shippable product increment means compliance with the work's individual acceptance criteria and not the full story under development.

Bugzilla

The following format is used to maintain consistency in how bugs are filed:

  • p= (point value assigned to the bug)
  • s= (the iteration the bug is being developed in)
  • r= (the target release of the bug under development)
  • [story] (collection of related bugs required for the completion of a feature)

Communication

General

Iteration Planning/Status Meeting

  • Time: Mondays - 1:00 PM Pacific, 4:00 PM Eastern
  • Duration: 1 hour
  • Vidyo Room: "Marco Mucci"
  • Etherpad: View MoPad
  • Dial-in: Audio-only conference# 9860
    • People with Mozilla phones or softphones please dial x4000 Conf# 9860
    • US/Toll-free: +1 800 707 2533, (pin 4000) Conf# 9860
    • US/California/Mountain View: +1 650 903 0800, x4000 Conf# 9860
    • US/California/San Francisco: +1 415 762 5700, x4000 Conf# 9860
    • US/Oregon/Portland: +1 971 544 8000, x4000 Conf# 9860
    • CA/British Columbia/Vancouver: +1 778 785 1540, x4000 Conf# 9860
    • CA/Ontario/Toronto: +1 416 848 3114, x4000 Conf# 9860
    • UK/London: +44 (0)207 855 3000, x4000 Conf# 9860
    • FR/Paris: +33 1 84 88 37 37, x4000 Conf# 9860
    • Gmail Chat (requires Flash and the Google Talk plugin): paste +1 650 903 0800 into the Gmail Chat box that doesn't look like it accepts phone numbers
    • SkypeOut is free if you use the 800 number

Iteration Performance Reports

People

Role Contacts
Project Champion
  • Johnathan Nightingale (johnath@mozilla.com) (A,C,I)
Program/Project Management Oversight
  • Sheila Mooney (smooney@mozilla.com) (A,C,I)
Program Management
  • Marco Mucci (mmucci@mozilla.com) (R)
Product Manager
  • Chad Weiner (cweiner@mozilla.com) (A,C,I)
  • Karen Rudnitski (krudnitski@mozilla.com) (A,C,I)
UX/Design
  • Yuan Wang (yuan@mozilla.com) (R)
  • Michael Maslaney (mmaslaney@mozilla.com) (R)
Dedicated Engineering
  • Tim Abraldes (tabraldes@mozilla.com) (R)
  • Brian R. Bondy (bbondy@mozilla.com) (R)
  • Matt Brubeck (mbrubeck@mozilla.com) (R)
  • Sam Foster (sfoster@mozilla.com) (R)
  • Jim Mathies (jmathies@mozilla.com) (R)
  • Ally Naaktgeboren (ally@mozilla.com) (R)
  • Rodrigo Silveira (rsilveira@mozilla.com) (R)
  • Marina Samuel (msamuel@mozilla.com) (R)
  • Stephen Pohl (spohl@mozilla.com) (R)
  • Aleh Zasypkin (azasypkin@mozilla.com) (R)
Graphics Team Support
  • Manager - Milan Sreckovic (msreckovic@mozilla.com) (C,I)
  • Dev - Kartikaya Gupta (kats@mozilla.com) (R)
  • Dev - Botond Ballo (bballo@mozilla.com) (R)
Localization
  • Axel Hecht (axel@mozilla.com) (R)
QA
  • Juan Becerra (jbecerra@mozilla.com) (R)
Services Integration
  • Mike Connor (mconnor@mozilla.com) (I)
Privacy
  • Sid Stamm (sstamm@mozilla.com) (A,C,I)
Release Management
  • Bhavana Bajaj (bbajaj@mozilla.com) (C,I)
Marketing
  • Laura Forrest (lforrest@mozilla.com) (I)
Legal
  • Manager - Harvey Anderson (handerson@mozilla.com) (A,C,I)
  • James Murdock (jmurdock@mozilla.com) (A,C,I)
Feedback
  • Tyler Downer (tdowner@mozilla.com) (A,C,I)
  • Manager - Matt Grimes (mgrimes@mozilla.com) (I)

The letters following each name stand for:

  • R = Responsible for deliverable
  • A = Accountable for the final decision making on some aspect of the project
  • C = Needs to be consulted on key topics
  • I = Needs to be kept informed

References

Retrieved from "https://wiki.mozilla.org/index.php?title=Firefox/Metro&oldid=966846"