Hi, One more update about the WSGI related improvements for Django:
I have created a Mercurial branch to keep track of these changes and keep them synchronized with trunk: http://bitbucket.org/Gustavo/django-wsgi/ Even though I know it's late for 1.2 at this point, please keep in mind that part of these enhancements were supposed to be a high priority for the 1.2 release [1] (GSoC-2). This branch implements more features than the official http-wsgi-improvements branch and is complete/working. And again, I am willing to help you with anything you need to get it merged, such as writing docs and discussing the implementation further. I hope to see these improvements in v1.3 then, even if it's not my implementation. Cheers, - Gustavo. [1] http://code.djangoproject.com/wiki/Version1.2Features#Highpriority On Wed, 2009-10-28 at 08:24 +0800, Russell Keith-Magee wrote: > On Tue, Oct 27, 2009 at 10:49 PM, Gustavo Narea > <gustavona...@2degreesnetwork.com> wrote: > > > > Hi there. > > > > Over the last week I've been working to improve WSGI support in Django > > and I have sent a few patches which have not received the feedback I > > expected to have, so I wanted to ping you. ;-) > > In the interests of good community relations, I want to clarify the > feedback you should be expecting. > > Just because you've uploaded a patch doesn't mean you're going to get > immediate feedback. We're all volunteers, so our time is limited - > sometimes, this means that patches don't get triaged for a while. > Patience is required. > > On top of that, we've just finished our feature discussion phase, and > we have nominated the features that are a high priority for the > project [1]. These are the features that will be receiving development > priority over the next few months. Features that aren't on this list > aren't going to get the immediate attention of the core team. > > The feature list isn't completely locked off, though. Any feature with > a complete patch is potentially on the list for inclusion. However, > any feature that isn't on the list will require: > > 1) A champion in the core team to commit the code > 2) A design and implementation that has been approved by the community > (as evidenced by discussion on django-dev) > > That means you're going to need a member of the core team who is > excited about this possible feature. I can't speak for the other > members of the core team, but personally, this isn't a big itch. I can > certainly see how it could be useful, but I've already committed to > some big-ticket items that are much higher priorities for me > personally. > > So - you need to have some patience. If you can't get a core developer > engaged as a result of this thread, you may need to wait until the > v1.3 feature discussion phase, which will open as soon as v1.2 is > finalized. Alternatively, you could help out with the features that we > have already agreed upon for v1.2, and maybe try to leverage the karma > you gain from doing that work into support for your WSGI patch. > > [1] http://code.djangoproject.com/wiki/Version1.2Features > > Yours, > Russ Magee %-) > > --~--~---------~--~----~------------~-------~--~----~ > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To post to this group, send email to django-developers@googlegroups.com > To unsubscribe from this group, send email to > django-developers+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en > -~----------~----~----~----~------~----~------~--~--- > -- Gustavo Narea. Software Developer. 2degrees - the collaboration service for sustainable business. http://www.2degreesnetwork.com/ -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
