Let me suggest that there are many who have at times felt frustrated how contributions or suggestions are managed in Django. Some of them seem to have walked away or just don't participate in discussions any longer. The same applies to several other large open source projects, the Linux kernel and it's mailing list being a prime example.
However, the frustration was mostly justified *before* Django 1.0 came out and the the semi-official DVCS mirrors took off. It was hard to keep patches updated - the internal APIs were in flux and Subversion was and is not flexible enough (even with svnmerge.py) to make branchy development painless. The frustration stemmed from too much change and no tools for managing it. In my opinion, neither of the problems apply as of now. Maintaining your own branches on GitHub or BitBucket off the corresponding Django SVN mirrors is easy and effortless, so it's time to put the grudges behind and happily fork and branch Django on the DVCS sites whenever there's a need for something missing from or broken in the official trunk - and, what's perhaps even more important, give back by shepherding the corresponding tickets in Django trac (keeping them up to date, improving them according to other's suggestions etc). "Relax," as CouchDB puts it :) Best, Mart Sõmermaa --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
