Labs/Jetpack/Reboot/JEP/Shell

JEP Shell - Example JEP

• Champion: Testy McTest - mctest@mozilla.com
• Status: Accepted/Pre-production
  • Status field can be Proposed or Accepted
    • Accepted detail flags are: Blocked, In-Queue, Pre-production, Production, Active, Deprecated
    • Proposed detail flags are: Needs Review, Under Review, Needs Revision, Declined
• Type: Core
  • Type field can be Core or API

Proposal

• What will it do?
• What does it enable internally/externally?
• How hard is it to implement?

Key Issues

• What are the most important items that need to be tackled in the JEP?
• What are areas that need further groups participation to solidify?

Dependencies & Requirements

• Are there any Firefox platform bugs blocking it?
• Does other Jetpack platform code need to be modified or added?
• Does its implementation affect any other projects or code?
• What is needed in the feature?
• What are some ideas on development/implementations paths?

Internal Methods

• What methods, mechanisms, or resources does this provide internally within the Jetpack platform code.

API Methods

• What are the pretty API wrapped methods externally exposed to Jetpack developers?