Labs/Jetpack: Difference between revisions
< Labs
Jump to navigation
Jump to search
Dandonkulous (talk | contribs) No edit summary |
Dandonkulous (talk | contribs) No edit summary |
||
Line 21: | Line 21: | ||
|} | |} | ||
== Jetpack | == Jetpack Platform Info == | ||
* [[Labs/Jetpack/Reboot/Architecture Overview|Architecture Overview]] | |||
* [[Labs/Jetpack/Reboot/Glossary|Glossary]] | |||
* [[Labs/Jetpack/Reboot/FAQ|FAQ]] | |||
== Jetpack Production Info == | |||
* [[Labs/Jetpack/Process|Development Process]] | * [[Labs/Jetpack/Process|Development Process]] | ||
* [[Labs/Jetpack/Release|Release Process]] | * [[Labs/Jetpack/Release|Release Process]] |
Revision as of 19:07, 17 February 2010
Jetpack Mission
Provide an extension development environment for the Mozilla platform that empower anyone to create powerful extensions with a set of extensible, robust APIs using the language of the web - HTML, CSS, and JavaScript.
Jetpack Long-Term Vision & Dependencies - Draft
Firefox 3.6.1 - 3.7 | Firefox 4.0 | |
Extension Manager | No-Restart API | Jetpack Installation API |
Firefox Platform | Chrome Object Wrappers | Jetpack runtime integrated to Firefox |
Security | Basic security model in place | |
Dev Tools | Command-line SDK & Web-based tool - FlightDeck | Enhancements to existing tools |
Packages | Generative development enabled via FlightDeck | |
Distribution | Jetpacks are bundled as XPIs w/ embedded Jetpack runtime in each | Jetpacks are distributed in a native package format |
Jetpack Platform Info
Jetpack Production Info
- Development Process
- Release Process
- Release Schedule
- Jetpack Security Philosophy
- Jetpack Binary Components
- Jetpack Localization
Jetpack Reboot
JEPs - Jetpack Extension Proposals
Building a Jetpack
Getting Involved
- Jetpack Google Group
- Official Weekly Meeting
- Jetpack's Source Code
- Join on the Jetpack IRC channel: #jetpack at irc.mozilla.org
- Report a Bug
- Jetpack Ambassador Program
Historical Notes on Jetpack Platform Development
- Initial investigation into the capabilities used by top add-ons today, and in particular, which de facto API calls they rely upon.