Labs/Jetpack/Reboot/JEP: Difference between revisions

Labs/Jetpack/Reboot/JEP (view source)

197 bytes removed , 27 January 2010

1,273

edits

@@ Line 7: / Line 7: @@
 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].
+Each JEP must have a champion - usually the author - who writes the JEP, leads discussion, and attempts to build community consensus about the idea. Posting to <mozilla-labs-jetpack@googlegroups.com> is recommended.
+Here is a JEP shell that details what is required: [[Labs/Jetpack/Reboot/JEP/Shell|JEP Shell]]
 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.