Labs/Jetpack/JEPs: Difference between revisions

From MozillaWiki
< Labs‎ | Jetpack
Jump to navigation Jump to search
No edit summary
(redirect to new consolidated JEP page)
 
(57 intermediate revisions by 14 users not shown)
Line 1: Line 1:
= What is a JEP? =
#REDIRECT[[Labs/Jetpack/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.
 
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].
 
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 more successful it tends to be. Jetpack module owners reserves the right to reject PEP proposals if they appear too unfocused or too broad. If in doubt, split your PEP into several well-focused ones.
 
Each PEP must have a champion -- someone who writes the PEP using the style and format described below, shepherds the discussions in the appropriate forums, and attempts to build community consensus around the idea. The PEP champion (a.k.a. Author) should first attempt to ascertain whether the idea is PEP-able. Posting to the comp.lang.python newsgroup (a.k.a. python-list@python.org mailing list) is recommended. Small enhancements or patches often don't need a PEP and can be injected into the Python development work flow with a patch submission to the Python issue tracker [6].
 
= Proposed JEPs =
 
[[Labs/Jetpack/JEP/10|JEP 10 - Clipboard 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, it's bug is marked finished, and it's status is changed to "Implemented"..

Latest revision as of 08:42, 10 May 2010

Redirect to:

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