Firefox/Metro: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 7: Line 7:
The goal of this project is to produce a Minimum Viable Product (MVP) that can be release to the public
The goal of this project is to produce a Minimum Viable Product (MVP) that can be release to the public


===Scope===
<h3>Scope</h3>
Still being finalized.
<p>Still being finalized.
 
</p>
* [[Firefox/Metro/Queries|Metro Bugzilla Queries]]
<ul><li> <a href=http://scrumbu.gs/p/FireFox-Metro/backlog/</a>
<ul><li> <a href="Firefox/Metro/Queries">Metro Bugzilla Queries</a>
</li></ul>


==Duration==
==Duration==

Revision as of 05:56, 17 January 2013

Firefox Metro

To produce and maintain a version of Firefox that is able to function as the default browser on Windows 8 Metro.

Goal

The goal of this project is to produce a Minimum Viable Product (MVP) that can be release to the public

Scope

Still being finalized.

  • <a href=http://scrumbu.gs/p/FireFox-Metro/backlog/</a>
    • <a href="Firefox/Metro/Queries">Metro Bugzilla Queries</a>

    Duration

    Initial estimation being developed.

    Information is being complied here: [1].

    Risks

    • Rendering and graphics, specificly OMTC
      • This area was a significant issue for Fennec so it will be monitored.
      • We have no data on how long this work is likely to take and it's hard to estimate.
      • First wave of refactoring done by 30th of December 2012 (bug 804893)
      • Mitigation: Monitor next milestone and report on progress
    • Sharing data between the desktop and the metro experience will happen via sync
    • High Resolution Support may be an issue and should be investigate.
      • See a list of touch screen devices with HiDPI specified here.
    • Themed/hoverable anonymous scrollbars for content
      • bug 636564
      • This work is an important component of mixed use (mouse/touch) scrolling working / scrollbar control display. Originally started for new OSX support but never completed.
      • Metro related bugs : bug 775718, bug 777610

    Communication

    Communication Type Mechanism Audience
    Announcements dev-planning and metro lists. metro@mozilla.org is the email address for the second list. all
    General discussion metro list devs
    IRC #windev all
    User Experience Meeting Monday at 1pm PT (4pm ET)
    • Dial-in: Audio-only conference# conf 99736
      • People with Mozilla phones or softphones please dial x4000 Conf# conf 99736
      • US/Toll-free: +1 800 707 2533, (pin 4000) Conf# conf 99736
      • US/California/Mountain View: +1 650 903 0800, x4000 Conf# conf 99736
      • US/California/San Francisco: +1 415 762 5700, x4000 Conf# conf 99736
      • US/Oregon/Portland: +1 971 544 8000, x4000 Conf# conf 99736
      • CA/British Columbia/Vancouver: +1 778 785 1540, x4000 Conf# conf 99736
      • CA/Ontario/Toronto: +1 416 848 3114, x4000 Conf# conf 99736
      • UK/London: +44 (0)207 855 3000, x4000 Conf# conf 99736
      • FR/Paris: +33 1 84 88 37 37, x4000 Conf# conf 99736
      • 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
    • Vidyo: Yuan Wang Vidyo Room
    • IRC: #windev
    • Meeting Notes: Metro User Experience Meeting Notes
    		 devs
    Engineering Triage Meeting Wednesday at 1pm PT (4pm ET)
    • Dial-in: Audio-only conference# 99136
      • People with Mozilla phones or softphones please dial x4000 Conf# 99136
      • US/Toll-free: +1 800 707 2533, (pin 4000) Conf# 99136
      • US/California/Mountain View: +1 650 903 0800, x4000 Conf# 99136
      • US/California/San Francisco: +1 415 762 5700, x4000 Conf# 99136
      • US/Oregon/Portland: +1 971 544 8000, x4000 Conf# 99136
      • CA/British Columbia/Vancouver: +1 778 785 1540, x4000 Conf# 99136
      • CA/Ontario/Toronto: +1 416 848 3114, x4000 Conf# 99136
      • UK/London: +44 (0)207 855 3000, x4000 Conf# 99136
      • FR/Paris: +33 1 84 88 37 37, x4000 Conf# 99136
      • 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
    • Vidyo: Jim Mathies Vidyo Room
    • IRC: #windev
    		 devs
    Engineering Team Meeting Thursday at 1pm PT (4pm ET)
    • Dial-in: Audio-only conference# 99136
      • People with Mozilla phones or softphones please dial x4000 Conf# 99136
      • US/Toll-free: +1 800 707 2533, (pin 4000) Conf# 99136
      • US/California/Mountain View: +1 650 903 0800, x4000 Conf# 99136
      • US/California/San Francisco: +1 415 762 5700, x4000 Conf# 99136
      • US/Oregon/Portland: +1 971 544 8000, x4000 Conf# 99136
      • CA/British Columbia/Vancouver: +1 778 785 1540, x4000 Conf# 99136
      • CA/Ontario/Toronto: +1 416 848 3114, x4000 Conf# 99136
      • UK/London: +44 (0)207 855 3000, x4000 Conf# 99136
      • FR/Paris: +33 1 84 88 37 37, x4000 Conf# 99136
      • 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
    • Vidyo: Jim Mathies Vidyo Room
    • IRC: #windev
    • Meeting Notes: Metro Engineering Meeting Notes Etherpad
    		 devs

    Progress Reports

    2012

    People

    Project Champion
    • Johnathan Nightingale (johnath@mozilla.com) (A)
    Program Management
    • Martin Best (mbest@mozilla.com) (R)
    • Erin Lancaster (elancaster@mozilla.com) (R)
    Product
    • Asa Dotzler (asa@mozilla.com) (A)
    UX
    • Yuan Wang (yuan@mozilla.com) (A)
    • Stephen Horlander (shorlander@mozilla.com)(R)
    Engineering Oversight
    • Mark Finkle (mfinkle@mozilla.com) (A)
    Dedicated Engineering
    • Tim Abraldes (tabraldes@mozilla.com) (R)
    • Brian R. Bondy (bbondy@mozilla.com) (R)
    • Matt Brubeck (mbrubeck@mozilla.com) (A)
    • Mark Finkle (mfinkle@mozilla.com) (A)
    • Sam Foster (sfoster@mozilla.com) (R)
    • Jim Mathies (jmathies@mozilla.com) (A)
    • Ally Naaktgeboren (ally@mozilla.com) (R)
    • Frank Yan (fyan@mozilla.com) (R)
    Graphics Team Support
    • Manager - Joe Drew (jdrew@mozilla.com) (I)
    • Dev - Bas Schouten (bschouten@mozilla.com) (A)
    Accessibility
    • Manager - David Bolter (dbolter@mozilla.com) (I)
    Localization
    • Axel Hecht (axel@mozilla.com) (I)
    Services Engineering
    • Manager - Mike Connor (mconnor@mozilla.com) (I)
    Servieces
    • Manager - Mark Mayo (mmayo@mozilla.com) (I)
    Incoming Bug Triage
    • ?
    QA
    • Bob Moss (bmoss@mozilla.com) (I)
    • Juan Becerra (jbecerra@mozilla.com) (A?)
    • Jason Smith (jsmith@mozilla.com) (R?)
    Security
    • ?
    Privacy
    • Sid Stamm (sstamm@mozilla.com) (C)
    Releng
    • Armen Zambrano Gasparnian (armenzg@mozilla.com) (R)
    Marketing
    • Laura Forrest (lforrest@mozilla.com) (I)
    Legal
    • Manager - Harvey Anderson (handerson@mozilla.com) (I)
    • James Murdock (jmurdock@mozilla.com) (R)

    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

    See reference section for RACI roles system for more information.

    Iterations

    Firefox Metro will be broken down into 3 week cycles called "Iterations". Each iteration will kick off with a planning meeting and full report on progress sent out to stakeholders. The goal of this process is to provide a structure that allows for review of status, dependencies, new requirements, and facilitate task coordination between development groups.

    Any bug that is expected to be worked on during a particular milestone will be marked with a whiteboard tag formatted like the following example: 

     "[metro-it1]"

    The number will increment each time a new iteration starts and we will attempt to have the majority of engineering tasks schedule for the next 2 iterations. With that said, there are many demands on the engineering teams and changes to the plan could occur at any time so expectations should be tempered accordingly. To request a bug, feature, or user story to be planned in an upcoming milestone, add "[metro-it?]" to the whiteboard and it will be reviewed in the next iteration kick off meeting.

    Here are the dates we will use for the next few iterations:

    • [metro-it1] - November 19th, 2012 - December 7th, 2012
    • [metro-it2] - December 10th, 2012 - January 11th, 2013
      • This is longer due to holiday and the impact it's having on the regular train model
    • [metro-it3] - January 14th, 2013 - February 1st, 2013
    • [metro-it4] - February 4th, 2013 - February 22nd, 2013
    • [metro-it?] - request to be scheduled.

    References

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