On 2/23/06, Christopher Lenz <[EMAIL PROTECTED]> wrote: > To an outsider like myself, it looks like there's been a rush towards > a major refactoring that (pretty much) stopped somewhere along half > the way, leaving quite a number of those features that make Django > such a great framework non-functional. And there's no documentation > (and only sparse archived discussion) about how the currently broken > functionality should be fixed... otherwise I'd have contributed a > good share of patches by now. > > IMHO, what the Django community needs at this point is for someone in > the know to update the RemovingTheMagic page, and add meat to the > "What's not done yet" section. Limit the scope of the branch, point > out what areas need fixing and how those are supposed to be > approached. I'm sure the "masterplan" is somewhere in the heads of > the developers, but it needs to be communicated to users and > potential contributors if we are to test and contribute to the branch.
Hey Chris, Yeah, development has slowed down a bit for a variety of reasons -- mostly time and other distractions. But I appreciate your bringing this up: We should do a better job of communicating the status. I'll update the RemovingTheMagic wiki page with the latest status. Adrian -- Adrian Holovaty holovaty.com | djangoproject.com | chicagocrime.org --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
