FxOS Portfolio Management: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(2.6)
 
(4 intermediate revisions by one other user not shown)
Line 1: Line 1:
==In-Progress==
==In-Progress==
----
----
{| class="wikitable" style="width: 85%; margin: auto;"
{| class="wikitable" style="width: 47%; float: left"  
! style="text-align: center; font-size:22px" colspan="3" | Engineering/Technical Programs
! style="text-align: center; font-size:22px" colspan="3" | Engineering/Technical Programs
|-
|-
| [[FirefoxOS/NGA|New Gaia Architecture]]
| [[FirefoxOS/NGA|New Gaia Architecture]]
| PM: <br />
| PM:Wilfred Mathanaraj <br />
EPM:<br />
EPM:Maria Oteo <br />
EM:
EM: Francisco Jordano
! style="background:#00EC00;" | ON TARGET
! style="background:#00EC00;" | ON TARGET
|-
|-
| [[NSEC (New Security Model)]]
| [[NSEC (New Security Model)]]
| PM: <br />
EPM:Jean Gong / Aaron Wu<br />
EPM:<br />
EM: Paul Theriault
EM:
! style="background:#00EC00;" | ON TARGET
! style="background:#00EC00;" | ON TARGET
|-
|-
| [[Engineering Quality Program|Quality Program]]
| [[Engineering Quality Program|Quality Program]]
| PM: <br />
EPM: Julie McCracken <br />
EPM:<br />
EM: David Scravaglieri
EM:
! style="background:#00EC00;" | ON TARGET
! style="background:#00EC00;" | ON TARGET
|-
|}
! style="text-align: center; font-size:22px" colspan="3" | Community Engagement/Growth Programs
{| class="wikitable" style="width: 47%; float: right;"
! style="text-align: center; font-size:22px" colspan="3" | Participation/Contributor Growth
|-
|-
| [[Foxfooding]]
| [[Foxfooding]]
| PM: <br />
| PM: Peter Dolanjski <br />
EPM:<br />
EPM:Jean Gong <br />
EM:
! style="background:#00EC00;" | ON TARGET
! style="background:#00EC00;" | ON TARGET
|-
|-
! style="text-align: center; font-size:22px" colspan="3" | New Form Factor Programs
! style="text-align: center;font-size:22px" colspan="3" | Product Roadmap
|-
|-
| [[TV]]
| [[TV]]
| PM: <br />
| PM:Joe Cheng <br />
EPM:<br />
EPM:Josh Cheng <br />
EM:
EM: Evelyn Hung
! style="background:#00EC00;" | ON TARGET
! style="background:#00EC00;" | ON TARGET
|-
! style="text-align: center;font-size:22px" colspan="3" | Product Development Programs
|-
|-
| [[Pin the Web]]
| [[Pin the Web]]
| PM: <br />
| PM: Ben Francis <br />
EPM:<br />
EPM: Lindsay Saunders <br />
EM:
EM: Gregor Wagner
! style="background:#00EC00;" | ON TARGET
! style="background:#00EC00;" | ON TARGET
|}
|}
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />


----
'''Status Key'''
'''Status Key'''
{| class="wikitable"
{| class="wikitable"
Line 76: Line 92:
==Current 2.6 Release==
==Current 2.6 Release==
{| class="wikitable" style="width: 85%; margin: auto;"
{| class="wikitable" style="width: 85%; margin: auto;"
| Action/Agenda Item
| '''Action/Agenda Item'''
| Assignee(s)
| '''Assignee(s)'''
| Status
| '''Status'''
| Notes
| '''Notes'''
|-
|-
| Continuous Integration Program
| Continuous Integration Program
Line 159: Line 175:
** There is still a lot work to do, but some features should be reconsidered like A/B testing
** There is still a lot work to do, but some features should be reconsidered like A/B testing
** We need prioritization of the features, too many features and there are dependencies with platform (just confirmed with Tamara that there is only one dependency and it seems not difficult to implement, [https://bugzilla.mozilla.org/show_bug.cgi?id=1232453 1232453])
** We need prioritization of the features, too many features and there are dependencies with platform (just confirmed with Tamara that there is only one dependency and it seems not difficult to implement, [https://bugzilla.mozilla.org/show_bug.cgi?id=1232453 1232453])
|-
| NSEC
| Jason/Aaron
| New
| This week:
* Refer to Mozlando [https://docs.google.com/document/d/1OT3ktKZPYZnL2s8diXs5Dy6VXAdHXeml5wnhHRcwsBc/edit NSec weekly meeting notes]
* Spec out Pinning.
Issues:
* Persistent solution - Pinning (PT)
** Can we achieve solid persistence with service workers?
* To package or not (package format) (Ethan)
** SRI (subresource integrity)
** Standard package format (RFC 1847)
** Consider this old design document: https://docs.google.com/document/d/1ehNH83tr1D965UkJdKxhFL_Am2AfsgOxY9QYJU4zBys/edit#heading=h.sr938rgjx1vf
* Subresource integrity (SRI) security check for unsigned packaged content
We should move forward this way.
https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity
* Permission model for New Security Model (PT)
** Also looking at Alternative permission model
*** eg move some things to the web
* Marketplace
** “discontinue new security architecture”
** Product is working on a plan for the future of marketplace
** (Jean) update NSec team discontinue NSEC from Marketplace
** QA support transitioning to FxOS QA
*** Need hand over meeting with Krupa
*** [QA met with Krupa in Orlando. Looking at
their automation test suite now]
|-
| Foxfooding, Participation and Contributor Growth
| Jean/Peter
| New
| *Sessions in Orlando on improving product participation
*Discussion on foxfooding held at Mozlando with Ari re. focusing more heavily in foxfooding program. There were some strategic next steps proposed. These are tbd but will be shared once we lock these down
*Ari agreed that foxfooding is critical in the new connected devices realm where we still need a development reference device (that may or may not be a phone).
*150 devices distributed @ Mozlando
|-
| Android Ports
| Nicole/Peter
|New
| *[12/1] B2G-Installer Add-on QA started
* B2G-Installer Add-On bug dependencies need to be resourced after Orlando
* Nexus 6 done - distribution will depend on build creation
* Legal discussions happening to unblock distribution
* Releng conversation on scaling builds will happen in Orlando
|-
| B2Gdroid
| Nicole/Peter/Fabrice
| New
| * [12/15] Focus priorities to support the Alopex experience.
* [12/1] bug tracking wiki: https://wiki.mozilla.org/B2Gdroid
* 100K downloads
* [11/24] Weekly triaging every Tuesday and Thursday
* Have nightly builds and updates (still need manual work for signing)
* Highest priority for development now is to get Gi and raptor tests running.
|-
| Pin the Web
| Lindsay/Ben
|
| * [12/15]
** Mostly continuing as planned
** Some features may be cut due to dependencies on other teams with shifting priorities:
*** Pin Contact/Event at risk due to NSEC/NGA priority changes
*** Talking to Marketplace tomorrow about bug [https://bugzilla.mozilla.org/show_bug.cgi?id=1226625 1226625] (W3C Web App support) for web app suggestions
* [Previous]
** [https://www.pivotaltracker.com/n/projects/1354744 Ordered product backlog] (subject to release planning)
UX specs in progress
Working on timeline for feature complete as well as polish and QA schedules
Working on pulling the [https://wiki.mozilla.org/Pin_the_Web documentation] into one place
|-
| Add-ons
| Mars/David Durst
|
| * [12/1] - 2.6 scope will not be determined till after Orlando or Q1 due to marketplace resourcing
|-
| Control Center
| Lindsay/Ben
|
| * [https://www.pivotaltracker.com/n/projects/1354744 Ordered product backlog] (as above)
* UX spec ready
* Team is identifying platform dependencies
* User stories have been estimated and work has begun
* Issues with platform dependencies
|-
| TV
| Josh
|
| * Completed
** Remote Control http://bit.ly/1PptNy7
** Marketplace TV side install feature
*** legal discussion on icon
* On-going
**Fixing TV bugs
** FTU
** Marketplace TV and frontend integration
** iarc needs to be cleared with panasonic
* P1: [https://bugzilla.mozilla.org/show_bug.cgi?id=1214148 Bug 1214148] - AudioChannel API design doesn't fit into nested mozbrowser iframe case.
|-
| Kill Switch
| Michael
|
|* FTE changes are out of scope and will not be needed for 2.6
* Patches ready for landing will be allowed to land
* Kill Switch is needed only for commercial devices.
* Kill Switch has been a US market entry requirement
* Kill switch is a complicated enough feature that we have really reduced in complexity over the last few weeks since we dropped the red* projects
|}
|}


Latest revision as of 23:04, 18 December 2015

In-Progress

Engineering/Technical Programs
New Gaia Architecture PM:Wilfred Mathanaraj

EPM:Maria Oteo
EM: Francisco Jordano

ON TARGET
NSEC (New Security Model)

EPM:Jean Gong / Aaron Wu
EM: Paul Theriault

ON TARGET
Quality Program

EPM: Julie McCracken
EM: David Scravaglieri

ON TARGET
Participation/Contributor Growth
Foxfooding PM: Peter Dolanjski

EPM:Jean Gong

ON TARGET
Product Roadmap
TV PM:Joe Cheng

EPM:Josh Cheng
EM: Evelyn Hung

ON TARGET
Pin the Web PM: Ben Francis

EPM: Lindsay Saunders
EM: Gregor Wagner

ON TARGET




















Status Key

Color Status Key
On Target The project or deliverable is expected to meet its due date.
Challenged The project or deliverable is facing an issue that might cause it to miss its due date, but a “get well” plan has been developed to get it back on track.
At Risk or Late The project or deliverable is blocked or facing an issue that might cause it to miss its due date, and there’s no “get well” plan to get it back on track, or it is already late.
Done The project or deliverable has been completed.
On Hold The project or deliverable has been placed on hold.

Current 2.6 Release

Action/Agenda Item Assignee(s) Status Notes
Continuous Integration Program Julie McCracken On Target This week:

Testing Improvements

Test Matrix

  • The test matrix meeting held at Mozlando wasn’t well attended because of a 2.6 scope meeting scheduled at the same time, but progress was still made on the matrix. Team members developed rules for when certain testing frameworks should be used for each type of test. A little more work will be done to complete it, and then it will undergo review for feedback.

GIP to GIJ Conversions

  • 26 conversions to go, down from 37 two weeks ago. 17 are unassigned. Module owners will be getting weekly notifications to remind them of the integration tests that remain to be converted.
  • GIP to GIJ Test Conversion Bug List
  • Question came up regarding the writing of additional python tests within the QA team. Maintainability of python tests is the issue. Shouldn’t write new ones in Python. If there are shortcomings in MJS that doesn’t permit the testing, bugs should be filed.

Intermittents

  • 8 intermittents still need to be fixed but only 2 of them remain unassigned. Module owners to be alerted when identified.
  • Intermittent Failures Bugs

Tests that work on mulet but fail on device.

Marionette Improvements

  • Team members met at Mozlando and worked together on removal of python from the Marionette harness, which is expected to be completed in Q4. Effort to remove python from Marionette harness has been started.
  • Two sessions were held to provide training and assistance with Marionette testing, a Marionette 101 session, and a follow-on session for Q&A and “office hours” support. Both sessions were well attended.
  • Next steps: planning for bitbar automation work! Bitbar contract renewal in the works.

Emulator Improvements

  • Hacking session at Mozlando was successful. Assistance was provided by build and release team and automation team members. 2 bugs were closed out.
  • Module owners need to be aware that ICS is going away and that they should move their tests to KK.
  • Discussed porting of emulator to either L or M, and many pros and cons were brought up. Lack of resources was also noted. Decision made to continue working on KK issues for the time being.
Train Model Implementation/Rel Eng work Mahe New OTA Branch
  • OTA branch is set up.
  • We still need to decide who will do the uplifts . That is still tbd.
Foxfooding Program Jean/Mahe New This week:
  • Discussion on foxfooding held at Mozlando with Ari re. focusing more heavily in foxfooding program. There were some strategic next steps proposed. These are tbd but will be shared once we lock these down
  • Ari agreed that foxfooding is critical in the new connected devices realm where we still need a development reference device (that may or may not be a phone).
  • Most foxfooding bugs are prioritize, still some remaining.. Will publish 2.6 Non blocking Bugs to wiki by end of week..
  • Avoid Feature Work from foxfooding feedback
  • Need Tamara/Russ’s support for building foxfooding app to report UUID
  • need to come up with communication to foxfooders about next steps, value-add, how we plan to move forward. (Jean/Faramarz)
Architecture Change Maria New This week:
  • FE/BE and views split:
    • A meeting will be scheduled with Ari and David Bryant to prioritise and see what it makes sense to focus on after last week’s announcement. (Jan)
    • During this week the FE/BE and views split will be on standby although we will finish the move of Contacts app in NGA branch to dev-apps and the isolation of Contacts from Communications app
  • Question around settings/system app changes for architecture?
    • Francisco to experiment on settings app himself and help test/validate for a decision
    • Maybe folks working on sms can refocus on settings
    • Media apps are being followed up with Joe
      • Need to understand value for timeline
  • Web Components: We have decided not to implement any changes in Gaia regarding web components but just focusing on the fxos-components organisation (Bug 1230494). What we have done so far is:
    • Moved to a new organisation: fxos-components
    • Migrated some components from gaia-* to fxos-*: When doing so, we don’t only change the name but also:
      • Improve documentation, examples, etc…
      • Publish the components in NPM3
      • There are still some pending components… the next step is completing the migration
      • After completing the migration, we will test the end-to-end flow of using npm3 for expressing application dependencies in one app (music or camera).
      • Based on that, we will decide if it’s worth it to apply to all the gaia apps, prioritise, etc…
    • UX support: In Orlando meeting, UX want to put minimal efforts on spec until there is more clear info about target devices.
  • Data Sync
    • Stage 2: "Read-only history sync on the phone” (as part of Firefox Sync) is almost completed, just pending some bugs (specially 1232276 that it’s a priority for 2.5 Smart TV) and get the feature available to foxfooders
    • Planned 2.6 scope needs to be reconsidered.
      • Stage 3: "Read-write history sync and passwords sync on the phone"
      • Media files synchronization looks still important for connected devices but the approach that we were taking (via FileSystemProvider API) might not be valid anymore, it really depends on the product, architecture and platform choice (on hold)
      • Local and remote Backup/Restore: although it does not seem a priority, it’s on hold until there is clarity on our strategy around smartphones
      • Contacts Sync.
  • Telemetry:
    • We continue working on it but no Product Manager, last Roadmap for 2.6 [1]
    • There is still a lot work to do, but some features should be reconsidered like A/B testing
    • We need prioritization of the features, too many features and there are dependencies with platform (just confirmed with Tamara that there is only one dependency and it seems not difficult to implement, 1232453)
NSEC Jason/Aaron New This week:

Issues:

We should move forward this way. https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity

  • Permission model for New Security Model (PT)
    • Also looking at Alternative permission model
      • eg move some things to the web
  • Marketplace
    • “discontinue new security architecture”
    • Product is working on a plan for the future of marketplace
    • (Jean) update NSec team discontinue NSEC from Marketplace
    • QA support transitioning to FxOS QA
      • Need hand over meeting with Krupa
      • [QA met with Krupa in Orlando. Looking at

their automation test suite now]

Foxfooding, Participation and Contributor Growth Jean/Peter New *Sessions in Orlando on improving product participation
  • Discussion on foxfooding held at Mozlando with Ari re. focusing more heavily in foxfooding program. There were some strategic next steps proposed. These are tbd but will be shared once we lock these down
  • Ari agreed that foxfooding is critical in the new connected devices realm where we still need a development reference device (that may or may not be a phone).
  • 150 devices distributed @ Mozlando
Android Ports Nicole/Peter New *[12/1] B2G-Installer Add-on QA started
  • B2G-Installer Add-On bug dependencies need to be resourced after Orlando
  • Nexus 6 done - distribution will depend on build creation
  • Legal discussions happening to unblock distribution
  • Releng conversation on scaling builds will happen in Orlando
B2Gdroid Nicole/Peter/Fabrice New * [12/15] Focus priorities to support the Alopex experience.
  • [12/1] bug tracking wiki: https://wiki.mozilla.org/B2Gdroid
  • 100K downloads
  • [11/24] Weekly triaging every Tuesday and Thursday
  • Have nightly builds and updates (still need manual work for signing)
  • Highest priority for development now is to get Gi and raptor tests running.
Pin the Web Lindsay/Ben * [12/15]
    • Mostly continuing as planned
    • Some features may be cut due to dependencies on other teams with shifting priorities:
      • Pin Contact/Event at risk due to NSEC/NGA priority changes
      • Talking to Marketplace tomorrow about bug 1226625 (W3C Web App support) for web app suggestions
  • [Previous]

UX specs in progress Working on timeline for feature complete as well as polish and QA schedules Working on pulling the documentation into one place

Add-ons Mars/David Durst * [12/1] - 2.6 scope will not be determined till after Orlando or Q1 due to marketplace resourcing
Control Center Lindsay/Ben * Ordered product backlog (as above)
  • UX spec ready
  • Team is identifying platform dependencies
  • User stories have been estimated and work has begun
  • Issues with platform dependencies
TV Josh * Completed
  • On-going
    • Fixing TV bugs
    • FTU
    • Marketplace TV and frontend integration
    • iarc needs to be cleared with panasonic
  • P1: Bug 1214148 - AudioChannel API design doesn't fit into nested mozbrowser iframe case.
Kill Switch Michael * FTE changes are out of scope and will not be needed for 2.6
  • Patches ready for landing will be allowed to land
  • Kill Switch is needed only for commercial devices.
  • Kill Switch has been a US market entry requirement
  • Kill switch is a complicated enough feature that we have really reduced in complexity over the last few weeks since we dropped the red* projects

Status Details by Program

NSEC (New Security Model)

NSEC (New Security Model)
Status: On Target


text


Risks/Issues Mitigation/Current Status
Text Text


Last Week's Accomplishments
Text


Next Week's Activity
*Text
*Text


References
*Text
*Text


Foxfooding

Foxfooding
Status: On Target


text


Risks/Issues Mitigation/Current Status
Text Text


Last Week's Accomplishments
Text


Next Week's Activity
*Text
*Text


References
*Text
*Text


Project Alopex

Project Alopex
Status: On Target


text


Risks/Issues Mitigation/Current Status
Text Text


Last Week's Accomplishments
Text


Next Week's Activity
*Text
*Text


References
*Text
*Text


Kill Switch

Kill Switch
Status: On Target


text


Risks/Issues Mitigation/Current Status
Text Text


Last Week's Accomplishments
Text


Next Week's Activity
*Text
*Text


References
*Text
*Text


Task Continuity

Task Continuity
Status: On Target


text


Risks/Issues Mitigation/Current Status
Text Text


Last Week's Accomplishments
Text


Next Week's Activity
*Text
*Text


References
*Text
*Text


OWDCRB

OWDCRB
Status: On Target


text


Risks/Issues Mitigation/Current Status
Text Text


Last Week's Accomplishments
Text


Next Week's Activity
*Text
*Text


References
*Text
*Text


Engineering Quality Program

Engineering Quality Program
Status: On Target


text


Risks/Issues Mitigation/Current Status
Text Text


Last Week's Accomplishments
Text


Next Week's Activity
*Text
*Text


References
*Text
*Text


Privacy

Privacy
Status: On Target


text


Risks/Issues Mitigation/Current Status
Text Text


Last Week's Accomplishments
Text


Next Week's Activity
*Text
*Text


References
*Text
*Text


Late Customization

Late Customization
Status: On Target


text


Risks/Issues Mitigation/Current Status
Text Text


Last Week's Accomplishments
Text


Next Week's Activity
*Text
*Text


References
*Text
*Text


Marketplace (TV)

Marketplace (TV)
Status: On Target


text


Risks/Issues Mitigation/Current Status
Text Text


Last Week's Accomplishments
Text


Next Week's Activity
*Text
*Text


References
*Text
*Text


Pin the Web

Pin the Web
Status: On Target


text


Risks/Issues Mitigation/Current Status
Text Text


Last Week's Accomplishments
Text


Next Week's Activity
*Text
*Text


References
*Text
*Text


Add-Ons

Add-Ons
Status: On Target


text


Risks/Issues Mitigation/Current Status
Text Text


Last Week's Accomplishments
Text


Next Week's Activity
*Text
*Text


References
*Text
*Text


Hackability

Hackability
Status: On Target


text


Risks/Issues Mitigation/Current Status
Text Text


Last Week's Accomplishments
Text


Next Week's Activity
*Text
*Text


References
*Text
*Text


Bugzilla Lite

Bugzilla Lite
Status: On Target


text


Risks/Issues Mitigation/Current Status
Text Text


Last Week's Accomplishments
Text


Next Week's Activity
*Text
*Text


References
*Text
*Text


FlyWeb

FlyWeb
Status: On Target


text


Risks/Issues Mitigation/Current Status
Text Text


Last Week's Accomplishments
Text


Next Week's Activity
*Text
*Text


References
*Text
*Text


Android Ports

Android Ports
Status: On Target


text


Risks/Issues Mitigation/Current Status
Text Text


Last Week's Accomplishments
Text


Next Week's Activity
*Text
*Text


References
*Text
*Text


B2Gdroid

B2Gdroid
Status: On Target


text


Risks/Issues Mitigation/Current Status
Text Text


Last Week's Accomplishments
Text


Next Week's Activity
*Text
*Text


References
*Text
*Text


TV

TV
Status: On Target


text


Risks/Issues Mitigation/Current Status
Text Text


Last Week's Accomplishments
Text


Next Week's Activity
*Text
*Text


References
*Text
*Text


Marigold

Marigold
Status: On Target


text


Risks/Issues Mitigation/Current Status
Text Text


Last Week's Accomplishments
Text


Next Week's Activity
*Text
*Text


References
*Text
*Text


RTL

RTL
Status: On Target


text


Risks/Issues Mitigation/Current Status
Text Text


Last Week's Accomplishments
Text


Next Week's Activity
*Text
*Text


References
*Text
*Text


Emulator

Emulator
Status: On Target


text


Risks/Issues Mitigation/Current Status
Text Text


Last Week's Accomplishments
Text


Next Week's Activity
*Text
*Text


References
*Text
*Text


Data Sync

Data Sync
Status: On Target


text


Risks/Issues Mitigation/Current Status
Text Text


Last Week's Accomplishments
Text


Next Week's Activity
*Text
*Text


References
*Text
*Text


NSEC (New Security Model)

NSEC (New Security Model)
Status: On Target


text


Risks/Issues Mitigation/Current Status
Text Text


Last Week's Accomplishments
Text


Next Week's Activity
*Text
*Text


References
*Text
*Text


Geolocation

Geolocation
Status: On Target


text


Risks/Issues Mitigation/Current Status
Text Text


Last Week's Accomplishments
Text


Next Week's Activity
*Text
*Text


References
*Text
*Text


Bluetooth

Bluetooth
Status: On Target


text


Risks/Issues Mitigation/Current Status
Text Text


Last Week's Accomplishments
Text


Next Week's Activity
*Text
*Text


References
*Text
*Text


OTA (Over the Air) Updates

OTA (Over the Air) Updates
Status: On Target


text


Risks/Issues Mitigation/Current Status
Text Text


Last Week's Accomplishments
Text


Next Week's Activity
*Text
*Text


References
*Text
*Text


Performance

Performance
Status: On Target


text


Risks/Issues Mitigation/Current Status
Text Text


Last Week's Accomplishments
Text


Next Week's Activity
*Text
*Text


References
*Text
*Text


DRM (Digital Rights Media)

DRM (Digital Rights Media)
Status: On Target


text


Risks/Issues Mitigation/Current Status
Text Text


Last Week's Accomplishments
Text


Next Week's Activity
*Text
*Text


References
*Text
*Text


NGA (New Gaia Architecture)

NGA (New Gaia Architecture)
Status: On Target


text


Risks/Issues Mitigation/Current Status
Text Text


Last Week's Accomplishments
Text


Next Week's Activity
*Text
*Text


References
*Text
*Text


Metrics

Metrics
Status: On Target


text


Risks/Issues Mitigation/Current Status
Text Text


Last Week's Accomplishments
Text


Next Week's Activity
*Text
*Text


References
*Text
*Text


Retrieved from "https://wiki.allizom.org/index.php?title=FxOS_Portfolio_Management&oldid=1109964"