577
edits
| Line 11: | Line 11: | ||
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. | 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 the comp.lang.python newsgroup (a.k.a. python-list@python.org mailing list) 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 -- 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 the comp.lang.python newsgroup (a.k.a. python-list@python.org mailing list) 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]. | ||
= Proposed JEPs = | = Proposed JEPs = | ||
edits