Re: Procedure for large contrib apps

2007-03-30 Thread Jacob Kaplan-Moss
On 3/30/07, Gulopine <[EMAIL PROTECTED]> wrote: > So once it's ready, would I create a ticket to make that proposal, or > just suggest it here? Here, probably. The ticket system is good for relatively uncontroversial changes, but new contrib apps might be controversial, so it's best to put it her

Re: Procedure for large contrib apps

2007-03-30 Thread Gulopine
On Mar 30, 11:02 am, "Jacob Kaplan-Moss" <[EMAIL PROTECTED]> wrote: > It seems a general consensus is forming over handling this sorts of > "contributed" subframeworks: create them as third-party projects -- I > highly recommend Google's code hosting athttp://code.google.com/-- > develop them sepa

Re: Procedure for large contrib apps

2007-03-30 Thread Jacob Kaplan-Moss
On 3/30/07, Gulopine <[EMAIL PROTECTED]> wrote: > On the flipside, this certainly qualifies as "non-trivial", so does it > need thorough discussion on this list before submitting a ticket? I'm > not sure on this one, since it doesn't modify any existing Django > code. I plan on bringing it up here

Procedure for large contrib apps

2007-03-30 Thread Gulopine
In working on my first major Django project, I've developed a few subframeworks for Django that are greatly enhancing the project, and I think many others would get good use out of them. Unlike my only thus- far submitted app, however, these are considerably complex. In addition to models.py, one