Firefox OS/ProgramManagement: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(programs)
(connected devices)
 
(22 intermediate revisions by 5 users not shown)
Line 1: Line 1:
==FXOS Engineering Program Management Office (PMO)==
==FXOS Engineering Program Management Office (PMO)==
<!-- This set of numbers and wikilinks is an imagemap.  It is tricky to edit by hand.  It is suggested that any errors should be corrected in the version on "[[The Club (dining club)]]" so that others can recopy to fix long standing errors.  Note hyperlinks will not go in the description - its a known bug in 2007 -->
<center> <big>'''Click the program on the graphic to view further information'''</big> </center>
<imagemap>Image:FxOS_Portfolio_.png
<imagemap>Image:EPMPortfolio1.png
rect 10 125 170 200 [[FxOS Portfolio Management|FxOS Portfolio Management]]
rect 10 125 170 225 [[Connected Devices Portfolio Management|Connected Devices Portfolio Management]]
rect 10 186 170 235 [[2.5 Program Manager|2.5 Program Manager]]
rect 10 200 170 245 [[2.5 Program Manager|2.5 Program Manager]]
rect 10 395 170 408 [[Aha Admin|Aha Admin]]
rect 10 395 170 408 [[Hackability|Hackability]]
rect 10 409 170 430 [[Hackability|Hackability]]
rect 10 409 170 430 [[Bugzilla Lite|Bugzilla Lite]]
rect 10 431 170 450 [[Bugzilla Lite|Bugzilla Lite]]
rect 10 431 170 450 [[FirefoxOS/FlyWeb|FlyWeb]]
rect 10 451 170 470 [[Wikis|Wikis]]
rect 10 451 170 470 [[Android Ports|Android Ports]]
rect 10 471 170 490 [[B2Gdroid|B2Gdroid]]
rect 171 125 320 195 [[NSEC (New Security Model)|NSEC (New Security Model)]]
rect 171 125 320 195 [[NSEC (New Security Model)|NSEC (New Security Model)]]
rect 171 196 320 215 [[Foxfooding|Foxfooding]]
rect 171 196 320 215 [[Foxfooding|Foxfooding]]
Line 23: Line 24:
rect 320 491 470 505 [[Geolocation Description|Geolocation Description]]
rect 320 491 470 505 [[Geolocation Description|Geolocation Description]]
rect 320 506 470 530 [[Bluetooth|Bluetooth]]
rect 320 506 470 530 [[Bluetooth|Bluetooth]]
rect 470 395 620 430 [[Red Tai/Red Square|Red Tai/Red Square]]
rect 470 125 620 200 [[Engineering Quality Program|Engineering Quality Program]]
rect 470 431 620 480 [[OTA (Over the Air) updates|OTA (Over the Air) updates]]
rect 470 395 620 430 [[OTA (Over the Air) updates|OTA (Over the Air) updates]]
rect 630 125 770 180 [[Privacy|Privacy]]
rect 630 125 770 180 [[Privacy|Privacy]]
rect 630 140 770 200 [[Late Customization|Late Customization]]
rect 630 140 770 200 [[Late Customization|Late Customization]]
Line 32: Line 33:
rect 630 409 770 460 [[DRM (Digital Rights Media)|DRM (Digital Rights Media)]]
rect 630 409 770 460 [[DRM (Digital Rights Media)|DRM (Digital Rights Media)]]
rect 780 125 950 180 [[Add-ons Description|Add-ons Description]]
rect 780 125 950 180 [[Add-ons Description|Add-ons Description]]
rect 780 395 950 438 [[NGA (New Gaia Archived)|NGA (New Gaia Archived)]]
rect 780 395 950 438 [[FirefoxOS/NGA|FirefoxOS/NGA]]
rect 780 439 950 450 [[Metrics Description|Metrics Description]]
rect 780 439 950 450 [[Metrics Description|Metrics Description]]
rect 780 451 950 480 [[Data|Data]]
rect 780 451 950 480 [[Data|Data]]
desc bottom-left
desc bottom-left
</imagemap>
</imagemap>


* [[FxOS Portfolio Management]]
* [[FxOS Portfolio Management]]
Line 44: Line 46:
* [[Project Alopex]]
* [[Project Alopex]]
* [[Kill Switch]]
* [[Kill Switch]]
* [[Task Continuity Description]]
* [[Firefox OS Cloud Servies]]
* [[Privacy Description]]
* [[Privacy Description]]
* [[Late Customization]]
* [[Late Customization]]
Line 67: Line 69:
* [[Performance Description]]
* [[Performance Description]]
* [[DRM (Digital Rights Media)]]
* [[DRM (Digital Rights Media)]]
* [[NGA (New Gaia Archived)]]
* [[FirefoxOS/NGA]]
* [[Metrics Description]]
* [[Metrics Description]]
* [[Web Components]]
* [[Web Components Performance]]
* [[Data]]
* [[Data]]
* [[Engineering Quality Program]]
* [[Engineering Quality Program]]
+ [[OWBCRV]]
* [[OWDCRB]]
 
 


==Bugzilla Flags==
==Bugzilla Flags==
Line 112: Line 114:
'''Who has the permission'''
'''Who has the permission'''
*  PM and EPM, engineer managers and partner peers have the access
*  PM and EPM, engineer managers and partner peers have the access
== EPM Toolbox ==
Wiki: [[Firefox_OS/EPM_Toolbox|Link]]

Latest revision as of 19:15, 18 December 2015

FXOS Engineering Program Management Office (PMO)

Click the program on the graphic to view further information
Connected Devices Portfolio Management2.5 Program ManagerHackabilityBugzilla LiteFlyWebAndroid PortsB2GdroidNSEC (New Security Model)FoxfoodingProject AlopexTVMarigoldRTL (Right to Left)EmulatorKill SwitchTask Continuity DescriptionVoiceData SyncCloud StorageNSEC (New Security Model)Geolocation DescriptionBluetoothEngineering Quality ProgramOTA (Over the Air) updatesPrivacyLate CustomizationMarketplace TVPin the WebPerformanceDRM (Digital Rights Media)Add-ons DescriptionFirefoxOS/NGAMetrics DescriptionDataEPMPortfolio1.png
About this image


Bugzilla Flags

The team will be using the following whiteboard text for tracking user stories and their priorities in Bugzilla.

Overview

  • ONE bug per user story. Implementation tasks and bugs should be marked as blocking the user story bug.
  • ALL user stories that are either committed or targeted to a release must have a bug filed.
  • If a bug is not a user story it will NOT have any of these flags in the whiteboard.

Data

  • The user story id, as found in the Product backlog spreadsheet, is written in the bug whiteboard as "ucid:{id}", eg: "ucid:Browser326".
  • The functional team that is responsible for the implementation of the user story is written as "ft:{teamname}", eg: "ft:media".

Format

  • Grammar: [ucid:{id}, {release-version}, ft:{team-id}]
  • The entire block is contained within square brackets
  • Case-insensitive. UCID and ucid are both valid.
  • Key and value are separated by a colon (no spaces).
  • Key/value pairs are separated by a space and comma.

Examples

  • [ucid:System26, 1.3, ft:systems-fe]
  • [ucid:Comms27, 1.3, ft:comms]

feature-b2g Flag

The purpose

  • The feature-b2g flag is intended to be used to help define scope for a particular release.
  • The feature-b2g flag enables us to isolate the particular engineering tasks that make up the completion of the feature in a release time frame.
  • feature-b2g version#? is defined as "this feature is being proposed for this release"
  • feature b2g- version#+ is define as "this feature has been committed (by the engineering team(s)) for this release"

How to tag

  • [meta] bugs features and all dependencies targeted for a particular release should mark feature-b2g flag.
  • The feature-b2g flag should assigned to engineering tasks falling under the user stories AND the user stories themselves.
  • feature-b2g should flag to feature work only, not polish, enhancement or refactor work. Unless there's a user story dedicated for those work in a particular release. This gives us a more stable feature-b2g bug number and better prediction/tracing.
  • You can only mark the flag for engineers assigned on your team - not partner teams.

Who has the permission

  • PM and EPM, engineer managers and partner peers have the access

EPM Toolbox

Wiki: Link