Labs/Jetpack/JEPs: Difference between revisions

From MozillaWiki
< Labs‎ | Jetpack
Jump to navigation Jump to search
(New JEP added)
No edit summary
Line 1: Line 1:
= What is a JEP? =
JEP stands for Jetpack Enhancement Proposal. A JEP is a design document providing information to the Jetpack community, or describing a new feature for Jetpack or its processes or environment. The JEP should provide a concise technical specification of the feature and a rationale for the feature.
We intend JEPs to be the primary mechanisms for proposing new features, for collecting community input on an issue, and for documenting the design decisions that have gone into Jetpack. The JEP author is responsible for building consensus within the community and documenting dissenting opinions.
Because the JEPs are maintained on the Mozilla Wiki, the revision history is the historical record of the feature proposal.
The JEP process begins with a new idea for Jetpack. It is highly recommended that a single JEP contain a single key proposal or new idea. The more focused the JEP the better.
Each JEP must have a champion -- someone who writes the JEP, shepherds the discussions in the appropriate forums, and attempts to build community consensus around the idea. The JEP champion (a.k.a. Author) should first attempt to ascertain whether the idea is JEP-able. Posting to <mozilla-labs-jetpack@googlegroups.com> is recommended. Small enhancements or patches can generally be put directly into the Jetpack development flow with a patch submission to the [http://bit.ly/5Qq83 Jetpack Bugzilla instance].
Once (or before) a JEP has been accepted by the Jetpack module owners, it is recommended to also make a reference implementation of the JEP and link to it from the JEP's header.
''The idea and description of JEPs is borrowed directly from the Python community, often word for word, and their use of [http://www.python.org/dev/peps/pep-0001/ PEPs].''
= Documentation =
Once a JEP is accepted and implemented, its API is documented at Jetpack's official documentation home, the [https://developer.mozilla.org/en/Jetpack Mozilla Developer Center].  Note that documentation is not the same thing as a proposal; in particular, JEPs may describe functionality that has not yet been implemented or functionality that is undergoing development.
= Proposed JEPs =
* [[Labs/Jetpack/JEP/10|JEP 10 - Clipboard Support]]
* [[Labs/Jetpack/JEP/10|JEP 10 - Clipboard Support]]
* [[Labs/Jetpack/JEP/11|JEP 11 - Simple Persistent Storage]]
* [[Labs/Jetpack/JEP/11|JEP 11 - Simple Persistent Storage]]
Line 52: Line 30:
* [[Labs/Jetpack/JEP/38|JEP 38 - IconJet]]
* [[Labs/Jetpack/JEP/38|JEP 38 - IconJet]]
* [[Labs/Jetpack/JEP/39|JEP 39 - DNS support]]
* [[Labs/Jetpack/JEP/39|JEP 39 - DNS support]]
= Accepted JEPs =
To become an accepted JEP, ready for implementation, either Atul Varma or Aza Raskin must approve the JEP. At that time, the status will be changed from "Proposed" to "Accepted" and a tracking bug will be created.
= Implemented JEPs =
After an accepted JEP has been implemented, its bug is marked finished, and its status is changed to "Implemented".

Revision as of 19:31, 17 February 2010

Retrieved from "https://wiki.allizom.org/index.php?title=Labs/Jetpack/JEPs&oldid=202924"