JEP

Introduction

JEP stands for Jetpack Enhancement Proposal. A JEP is a proposal for an enhancement to the Jetpack add-ons development platform. JEPs are a mechanism for collecting ideas and influencing Jetpack development.

JEPs are not the only mechanism for influencing Jetpack development, and they're often not the best one. Consider proposing and discussing new APIs and enhancements to existing ones in the Jetpack discussion group without writing a JEP, since most changes can be proposed, discussed, agreed upon, and implemented without the heavyweight formal process of a JEP. Other options include:

• File bug reports
• Go ahead and implement APIs that don't need to be in the core Jetpack library (or for which it's not clear whether or not they belong in the core), then distribute them to add-on developers via your own website (or, once available, via FlightDeck).

Process

To champion a JEP, assign it the next available integer and create a wiki page for it prefixed with JEP-. Reference the page in the list below.

Proposals

• DOM Window for add-ons
• Packageless
• Add-on URLs
• Linker
• [SDK in Firefox](JEP SDK in Firefox)
• Metadata
• Collections
• Content scripts
• Disposable
• Library structure
• Add-on Building Add-on
• Panel positioning
• Places API
• Add-on UI Integration
• Add on debugger